Simon Pasquier

One example in https://github.com/prometheus-operator/prometheus-operator/issues/5050 for having "group annotations" was to identify the origin of a group of alerts (e.g. "link to the [mixins source](https://github.com/prometheus/prometheus/tree/main/documentation/prometheus-mixin)"). I guess people could come with...

/skip @bparees sorry to bother you again, would you mind adding the `/approve` label too?

@jsha it looks like a transient error on the Travis side. I've restarted it and it's all green now.

Which version are you running? How much have you increased the timeout? Have you checked the server's logs?

In general we avoid labels with unbounded values because it could increase labels cardinality dramatically and also because instrumentation practices recommend that all label values are exposed (series that come...

IIUC the `Output` field could vary a lot with check scripts. Eg if the check is running `ping -c1 foo.example.com`, the output will be different (almost) every time. Of course...

It seems like the information isn't exposed indeed. The closest metric would probably be `consul_catalog_service_node_healthy` (only exposed with the `--consul.health-summary` flag since it needs an additional call to the Consul...

Right now there's no way that the exporter can report a service or node in maintenance because a health check from the API can only be `passing`, `warning` or `critical`....

The request sounds reasonable to me. It should probably be opt-in though. WDYT?

Apologies for the very belated answer. Would you be able to rebase?