More of a presentation layer configuration gripe: I’d like better ways for scrape targets to be able to describe and ship their own indicators and PromQL queries, see also https://github.com/pivotal/monitoring-indicator-protocol/wiki I want to spend less time fiddling with “in-house custom-built dashboards” and just let apps and services declare what queries they think are important and have that auto-register.
I've seen ideas like this before. IMO, it shouldn't be in-line with the scrape. That would be too noisy. But a separate standard API method might be useful for target-level monitoring metadata.
Another difficulty I see with this kind of idea, is that every target would be hinting at metrics. But which target of possibly 1000s is the right one to trust with the truth about the queries to run. It doesn't take into account job level or organization level info.
one of the responses says
this sounds like a great idea!
I've seen ideas like this before. IMO, it shouldn't be in-line with the scrape. That would be too noisy. But a separate standard API method might be useful for target-level monitoring metadata.
Another difficulty I see with this kind of idea, is that every target would be hinting at metrics. But which target of possibly 1000s is the right one to trust with the truth about the queries to run. It doesn't take into account job level or organization level info.