You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠️ Please verify that this feature request has NOT been suggested before.
I checked and didn't find similar feature request
🏷️ Feature Request Type
API
🔖 Feature description
As the tags feature is very useful in storing additional data about monitors, I have realized that it would provide extra value if those tags were exposed to the Prometheus compatible metrics endpoint at /metrics.
In my case, the use case would be to provide a severity label on the monitors so that it could then be used to alter the severity of the Prometheus alert. There are some monitors I'd like Prometheus to alert on at lower than critical severity which is the default.
It could also be useful in other scenarios
✔️ Solution
Expose tags as labels or meta-labels with the __ prefix so that users could use the relabeling process to keep/rename/drop tags as needed.
I think the meta-metric approach would be best and is something that various native service discovery mechanisms already provide in Prometheus.
❓ Alternatives
Perhaps meta labels could also be exposed for enabled notification channels, which for some users could be useful in deciding which alerts are critical or not. For example, if the monitor notification channel A is enabled, then it would also mean the Prometheus alert needs to have a higher severity (which can be achieved through relabels).
📝 Additional Context
No response
The text was updated successfully, but these errors were encountered:
🏷️ Feature Request Type
API
🔖 Feature description
As the tags feature is very useful in storing additional data about monitors, I have realized that it would provide extra value if those tags were exposed to the Prometheus compatible metrics endpoint at
/metrics
.In my case, the use case would be to provide a severity label on the monitors so that it could then be used to alter the severity of the Prometheus alert. There are some monitors I'd like Prometheus to alert on at lower than critical severity which is the default.
It could also be useful in other scenarios
✔️ Solution
Expose tags as labels or meta-labels with the __ prefix so that users could use the relabeling process to keep/rename/drop tags as needed.
I think the meta-metric approach would be best and is something that various native service discovery mechanisms already provide in Prometheus.
❓ Alternatives
Perhaps meta labels could also be exposed for enabled notification channels, which for some users could be useful in deciding which alerts are critical or not. For example, if the monitor notification channel A is enabled, then it would also mean the Prometheus alert needs to have a higher severity (which can be achieved through relabels).
📝 Additional Context
No response
The text was updated successfully, but these errors were encountered: