Summary

We want to provide a metrics rest api for mrplow app in a way that external users or other application can monitor both the status of the system and the status of the application.

Background

What is the motivation for these changes? What problems will this solve? Include graphs, metrics, etc. if relevant.

• Other third party processes (i.e. Airflow) might want to monitor Mr Plow status and how is using the current pod resources.

Goals

What are the outcomes that will result from these changes? How will we evaluate success for the proposed changes?

• Show and measure Mr Plow performance in a given interval of time
• Show bytes transferred and received in Mr Plow from the database in a timeframe
• See the impact of Mr Plow in the current system/pod in term of resource in a given time frame

Non-Goals

To narrow the scope of what we're working on, outline what this proposal will not accomplish.

• Reset the time counters performance counters in MrPlow app.
• Provide statistics outside a time frame.

Proposed Solution

Describe the solution to the problems outlined above. Include enough detail to allow for productive discussion and comments from readers.

The solution is made up of two parts: