Björn Rabenstein
Björn Rabenstein
@charleskorn could you update https://github.com/prometheus/prometheus/blob/main/docs/configuration/unit_testing_rules.md accordingly? Then we can merge this, and then https://github.com/prometheus/prometheus/pull/13662 can be adjusted on top of this.
Maybe that was an omission even before. Or maybe you cannot use the query fail assertions with the `promtool` rules test? But I hope you can. Essentially, the unit test...
Picking this up during our bug scrub. @darshanime are you still up to adding a test?
@mustafain117 did you close this for a specific reason? If you saw some technical blocker, it would be good to know. If you closed it because you were frustrated waiting...
Thank you very much. Good to know that you weren't left alone in the dark here.
I tagged people that have discussed #12120 as reviewers.
@roidelapluie @codesome @gotjosh @juliusv could you have a look? Or at least let us know if you have noticed this PR, but you don't have time to get to it...
Precisely because scrape failures are normal, we need a way to routinely track the reasons that does not require to set the whole server into debug-logging mode (because that's something...
Along similar line is the problem of out-of-order and duplicate timestamps. It currently involves restarting the server with debug-level logging and wait for the incident to happen again. I'd also...
Debug logs are for debugging Prometheus. What we need to address in case of tracking the error messages of failed scrapes or the time series that get duplicate or out-of-order...