Skip to content
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

No way to distinguish between target related metrics and exporter metrics #106

Closed
dmitry-sinina opened this issue Nov 29, 2024 · 1 comment

Comments

@dmitry-sinina
Copy link

dmitry-sinina commented Nov 29, 2024

According to documentation some metrics like idrac_exporter_build_info and idrac_exporter_scrape_errors_total relates not to scraped target but to exporter itself. With provided prometheus relabeling config instance label will be added to such metrics so instead of one idrac_exporter_scrape_errors_total we will have this metric for every target.

It would be great to export all target related metrics with label target and exporter related metrics without such label. Also in this way any additional relabeling on prometheus side will be not required.

@mrlhansen
Copy link
Owner

Hi @dmitry-sinina

The idrac_exporter_scrape_errors_total is target specific (the number of scrape errors for the specific target). The idrac_exporter_build_info is indeed the same for all targets. However, I do not see any real value in changing the exporter because of a single metric being repeated for every target. You normally have this kind of information from every target anyway, it's just in this case it comes from the same binary (but some people do run one instance of the exporter per target).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants