Added flask-monitoringdashboard app

[iambibhas]

Implemented flask-monitoringdashboard This app gives us some metrics about HTTP requests on the endpoints we choose. Couple of pros are -

• it's possible to track requests per user with this if the user is logged in
• it's possible to track request time per endpoint per version with this. The version could be a manually set version number or the deployed git commit ID. So it's possible to compare endpoint performance per release.

[jace]

What is the performance impact of this extension?

[iambibhas]

@jace it writes to a second db. I tried load testing locally using ab, didn't find much difference in performance. Any better way to measure that you can think of? This seems to be essentially what the clients for 3rd party services do. They make HTTP requests and this is writing to db.

[jace]

When does it write? In the same request response cycle, or in a background job? Writing to a second db will still freeze the request until the database finishes committing.

[jace]

We can't use SQLite in production as there are multiple worker processes competing for control over this file.

[iambibhas]

By default it uses sqlite and creates this file. I moved it to postgres.

[jace]

Config should be stored in the instance folder.

[jace]

Group by event session, not user.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Bibhas seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}