-
-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to stop reporting deleted resources in Prometheus scrape endpoint #1923
Comments
Btw, thanks for Promitor @tomkerkhove - it's really helpful. I understand the FAQ recommends we enable Prometheus metric timestamps - however, this is not an option for us. A few hours after a resource is deleted, our Prometheus systems with remote-write begin reporting |
Thank YOU for using Promitor! Always happy to hear feedback or list you as an end-user. I'm not sure how I can fix this, though, as once it's reported it is still around. I will ask in our depending library. Update: prom-client-net/prom-client#177 |
This is coming as per prom-client-net/prom-client#177 and prom-client-net/prom-client#178 so then we can do a more proper clean-up. However, we would need to check if this is an opt-in or not given others who use timestamps might want to keep them around. |
This is now supported (see prom-client-net/prom-client#178 & prom-client-net/prom-client#177) |
This should be done through a feature flag where the default should be to just keep the metric; to avoid breaking changes. |
First, need to upgrade to latest versions of Prometheus.Client packages #1772 |
Yup |
Proposal
Add a setting to stop reporting deleted resources in Prometheus scrape endpoint.
From https://docs.promitor.io/faq#how-does-promitor-handle-deleted-resources
Reporting metrics for deleted resources:
promitor_scrape_error
metric, as the metric returns1
for any deleted resourcesAn option to stop reporting metrics for deleted resources would resolve the above issues.
Component
Scraper
Contact Details
No response
The text was updated successfully, but these errors were encountered: