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

Standard internal error counter for all exporters? #1278

Closed
RichiH opened this Issue Dec 30, 2015 · 6 comments

Comments

Projects
None yet
2 participants
@RichiH
Copy link
Member

RichiH commented Dec 30, 2015

I think it would make sense to have a canonical metric for internal error counting of all exporters. This would allow easy monitoring when scrape happens upon a partially misconfigured or otherwise non-ideal target.

This is partially motivated by prometheus/snmp_exporter#16

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Dec 30, 2015

There's so many ways that an exporter can fail that this isn't practical. For example that issue is a user configuration error, which is different from the target having an error which is different from a failure.

At most we can offer only general guidance.

@RichiH

This comment has been minimized.

Copy link
Member Author

RichiH commented Dec 30, 2015

While I readily agree that there is a myriad of reasons, the point is that this would allow me to look at anything that is not zero.

@RichiH

This comment has been minimized.

Copy link
Member Author

RichiH commented Dec 30, 2015

#1169 is somewhat related to this.

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Dec 30, 2015

#1169 is to cover a failure of the exporter itself to handle a failure.

@RichiH

This comment has been minimized.

Copy link
Member Author

RichiH commented Dec 30, 2015

Correct. One is for failures that could be handled/ignored, one is for the ones which could not.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 24, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.