You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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).
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.
The text was updated successfully, but these errors were encountered: