thoth-station / thoth-application

Thoth-Station ArgoCD Applications
GNU General Public License v3.0
12 stars 22 forks source link

[13pt] Create reports out of prescriptions #1949

Open fridex opened 3 years ago

fridex commented 3 years ago

Is your feature request related to a problem? Please describe.

As Thoth administrator, I would like to know statistics about prescriptions - the open-source database for Python projects. To support this, I would like to have periodic reports that show insights about the database.

Describe the solution you'd like

Create a periodic job that introspects thoth-station/prescriptions and aggregates relevant information about the open-source database about Python projects. A very first implementation can give insights about:

Later, we can extend the stats to cover also information about Python package indexes, static source code analysis and its use and such.

goern commented 3 years ago

is that something that we want to show in a grafana dashboard?

fridex commented 3 years ago

is that something that we want to show in a grafana dashboard?

I don't know what presentation layer would suite this the most - might be grafana dashboards or an e-mail report. @pacospace will know more.

goern commented 3 years ago

let's start with a dashboard.

/sig observability /priority important-soon /triage accepted

sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

fridex commented 2 years ago

/remove-lifecycle stale

sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

harshad16 commented 2 years ago

/lifecycle frozen

VannTen commented 2 years ago

Most of these should be easily doable by cloning the repo and doing some find tricks:

If we go the metrics routes (promql ones), most "change" metrics should not be added as is, but derived from counter / gauge.

harshad16 commented 2 years ago

Suggestions:

Acceptance criteria:

xtuchyna commented 2 years ago

So there is no need to create metrics workflows for this inside mi then, @VannTen @harshad16 ?

VannTen commented 2 years ago

I don't know what mi does exactly, so I'm not in the best position to answer. But if we're talking about prescriptions and agree that thoth-station/prescriptions is the canonical source, yeah, there should not be metrics elsewhere on the same data.

harshad16 commented 2 years ago

We wanted to explore the front of metrics and see if that would be suitable for this. With MI can go do Prometheus metrics?

xtuchyna commented 2 years ago

Hey @harshad16 , sorry to bother but not sure what you meant by

With MI can go do Prometheus metrics?

Please let me know! thxx

harshad16 commented 2 years ago

ah typo, i meant can we do the Prometheus metrics with MI for the details insight list in the description?