Skip to content

/prometheus

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

Metric for warnings #1586

Closed
RichiH opened this Issue Apr 25, 2016 · 3 comments

Comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@RichiH @beorn7
@RichiH
Copy link
Member

RichiH commented Apr 25, 2016 •
edited

To catch #1585 and others, there should be counters for every warning and error. Optionally, having a timestamp for when a certain warning or error last happened might be useful.
@beorn7

This comment has been minimized.

Sign in to view
Copy link
Member

beorn7 commented Apr 25, 2016

For the case of #1585 , there is prometheus_local_storage_out_of_order_samples_total. A timestamp is not really needed as you can see where the last counter increment happened.
@beorn7

This comment has been minimized.

Sign in to view
Copy link
Member

beorn7 commented Apr 25, 2016

This is meant to be included for other warnings and errors in #1479 . I have updated that issue and hereby declare this one a dupe.

@beorn7 beorn7 closed this Apr 25, 2016

@beorn7 beorn7 added the duplicate label Apr 25, 2016

@lock

This comment has been minimized.

Sign in to view
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.