Julius Volz

Oops. No, I forgot about that. I will become the Python expert until tomorrow somehow.

Yeah, TL;DR of that article: If you have just have a binary success/failure situation that you want to track, use two different metrics, one for the failures, one for the...

Hi! @roidelapluie helpfully pointed me at this issue. Just to let you know, there are two implementations of the UI in Prometheus: * The legacy UI that is using Go-side...

@gracewehner We don't have a properly tracked effort for it yet on the Prometheus side, as it's more of a loose aspiration of a couple of folks so far who...

My currenct inclination would also be to keep scrape errors and OOO/duplicate sample errors out of logging and just put them in the web UI instead. Each target could keep...

>> Add some logScrapeFailToInfo option to flags or configuration > > We already suffered from flags fatigue in Prometheus 1.x. At Google there were flags that allowed you to tune...

Sorry for the issue radio silence here - I've just been plowing through things myself over the last half year because that was the easiest for me, but now the...

Thanks! Yeah, I think your PR is the right approach as a short-term workaround. Long-term it would make sense to rethink how we create, ingest, and query the test data...

Yep! That's pretty much the plan, see https://promlabs.com/blog/2022/10/25/promlabs-and-chronosphere-open-source-the-promlens-query-builder. We just need to figure out a good way how to share the relevant bits of the code. There's still good reason...

That will mainly need updating of one query example here: https://github.com/prometheus/promlens/blob/main/app/src/pages/PromLens.tsx#L17-L106 The official demo server is pretty outdated (2.27). @SuperQ Any chance to get it updated? :)