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.

Sign up for GitHub

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

Jump to bottom

[FIRING] Lots of scrape_samples_scraped lost Now ~ 2.83k, 24h ago ~ 27.96k. #422

Closed
hellais opened this issue Jan 23, 2020 · 1 comment
Closed

[FIRING] Lots of scrape_samples_scraped lost Now ~ 2.83k, 24h ago ~ 27.96k. #422

hellais opened this issue Jan 23, 2020 · 1 comment
Labels
incident

Comments

@hellais
Copy link
Member

hellais commented Jan 23, 2020 •
edited
Loading

We are seeing since today this alert:

[FIRING] Lots of `scrape_samples_scraped` lost
Now ~ 2.83k, 24h ago ~ 27.96k.

This previously was a signal for: #343, but at a cursory glance metrics from hosts seem to be collected properly.

@SuperQ do you have other points for stuff we should be looking at to investigate this and verify if it's indeed a problem?

This is the definition of the alert:

sysadmin/ansible/roles/prometheus/files/alert_rules.yml

Line 125 in 6dcea6e

- alert: ScrapeSamplesLoss

@hellais
Copy link
Member Author

hellais commented Jan 23, 2020

It turned out that doing aa5e846 had the uninstended consequence of breaking the rule in 78af081#diff-eaac1fdadca0a783965b2593ce5845f1R138 which broke all monitoring.

I have fixed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
incident
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hellais