Open fridex opened 3 years ago
is that something that we want to show in a grafana dashboard?
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.
let's start with a dashboard.
/sig observability /priority important-soon /triage accepted
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
/remove-lifecycle stale
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
/lifecycle frozen
Most of these should be easily doable by cloning the repo and doing some find tricks:
find -name '*.yaml'
find -type d -mindepth 2 -maxdepth 2
find -name '*.yaml' -exec grep 'type:' {} + | cut -d : -f 3 | sort | uniq -c
find -name '*.yaml' -printf '%h\n' | rev | cut -d / -f 1 | rev | sort | uniq -c
If we go the metrics routes (promql ones), most "change" metrics should not be added as is, but derived from counter / gauge.
Suggestions:
Acceptance criteria:
So there is no need to create metrics workflows for this inside mi
then, @VannTen @harshad16 ?
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.
We wanted to explore the front of metrics and see if that would be suitable for this. With MI can go do Prometheus metrics?
Hey @harshad16 , sorry to bother but not sure what you meant by
With MI can go do Prometheus metrics?
Please let me know! thxx
ah typo, i meant can we do the Prometheus metrics with MI for the details insight list in the description?
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.