Support Prometheus Metrics for Observability #24840
Replies: 7 comments 1 reply
|
Renovate is not a React app nor a server like Express, so I'm not sure that proposed package would be appropriate. e.g. their Usage is: |
|
Ah, well then I'll remove that recommendation, but stand by the feature request. |
|
Implementation proposal:
|
That might be useful for Mend Renovate app (offline processing, I guess), but Renovate OSS runs as a batch job and Prometheus is unlikely to be able to scrape all the metrics before it exits. Pushing metrics to a Prometheus Pushgateway may be more appropriate: prometheus.io/docs/practices/instrumentation/#batch-jobs |
|
OTEL is push based. True, the additional Prometheus exporter is only useful for long running instances. |
This comment has been minimized.
This comment has been minimized.
|
@secustor Would the renovate project be open for a PR to support this? Renovate would be ideally suited to push metrics to a Prometheus Pushgateway.
One use case: We need metrics to check whether Renovate could fetch updates for all repositories. Currently, this is only possible by checking or parsing logs. There already exists a tool (https://github.com/raffis/renovate-metrics) that does this by reading Renovate's logs, but it would be better to do this inside the application instead of log piping. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
What would you like Renovate to be able to do?
As far as I can tell Renovate doesn't support prometheus metrics for consumption into what Renovate is doing. It would be very useful to be able to measure, how many PRs is it opening, is it failing to open PRs, timeouts or failure to authenticate to github, etc. as a metric so they can be alerted on.
If you have any ideas on how this should be implemented, please tell us here.
No
Is this a feature you are interested in implementing yourself?
No
All reactions