Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Option to disable per-node metrics

See original GitHub issue

We are using docker slaves in Jenkins, which get random names. As a consequence, more and more series pile up in the database with names like jenkins_node_docker_76eb8f041ea67_builds_count. Would be nice if these metrics could be disabled, or if a label/tag was used instead.

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:6

Top GitHub Comments

2reactions

LuboVargacommented, Jul 11, 2018

Imho labe is must. According prometheus best practice it have to be like: `jenkins_node_builds_count{nodename=“docker_76eb8f041ea67”}…

0reactions

midnightconmancommented, Oct 26, 2020

I am not sure how you guys have your prometheus setup, but I drop these metrics at scrape time via something like this:

    - action: drop
      regex: ^jenkins_node_.+_builds$
      sourceLabels:
      - __name__
    - action: drop
      regex: ^jenkins_node_.+_builds_count$
      sourceLabels:
      - __name__
    - action: drop
      regex: ^label_jenkins_.*$
      sourceLabels:
      - __name__

I would recommend doing the same, until we get some traction on this feature / bug request.