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
Currently it seems as though you can only disable metrics by their name. I would like to disable metrics by a label match.
For instance in our environment I only am interested in master branch, so I would like to drop metrics, for instance that have jenkins_job="systems/terraform/PR.*"
I don't believe this would work using the regex capability today.
prometheus_jenkins_builds_stage_duration_milliseconds_summary_created(?!.master).
Currently I am dropping the metrics on relabel on the prometheus.yml side.
The text was updated successfully, but these errors were encountered:
We had this request a couple of times. I understand that this could be a useful feature but the labels are calculated when the metric is calculated.
Therefore there's not much benefit in terms of workload. It would just be a truncation of the output while the metric itself would still be calculated by Jenkins. There would be quite a litlle refactoring to archive this. I'll keep this ticket open - but do not expect immediate results (low on time right now)
Ah I somehow missed it in searching issues. No worries. Like I said I have managed to mitigate it via relabeling/drop before prometheus ingestion. Overall awesome work on the project - kudos to you and the contributors around.
What feature do you want to see added?
Currently it seems as though you can only disable metrics by their name. I would like to disable metrics by a label match.
For instance in our environment I only am interested in master branch, so I would like to drop metrics, for instance that have jenkins_job="systems/terraform/PR.*"
I don't believe this would work using the regex capability today.
prometheus_jenkins_builds_stage_duration_milliseconds_summary_created(?!.master).
Currently I am dropping the metrics on relabel on the prometheus.yml side.
The text was updated successfully, but these errors were encountered: