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.

Naming of variables...

See original GitHub issue

I noticed that there variables like this:

jenkins_node_NODE_builds
jenkins_node_NODE_builds_count
jenkins_node_NODE_builds_sum

Variables like this are problematic. I suspect it’s what “dropwizard metric” creates, but generally it would be better if NODE was in a label.

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:14 (3 by maintainers)

Top GitHub Comments

2reactions

markyjackson-tauliacommented, Oct 9, 2018

@markyjackson-taulia is there a workaround ? I’m not able to scrape metrics with default_ prefix as well.

I can see about a work around in the next release if that is ok I am going to re open this so I can track against it

1reaction

wjoelcommented, Oct 9, 2018

For what it’s worth, we added an option to disable those metrics in our fork at https://github.com/cognitedata/metrics-plugin/pull/1 - it’s not the best way to do it, I’m sure, but works for us. Those additional metrics were a major issue, since we use the Kubernetes plugin and therefore get a lot of “computers” as Jenkins sees it.

I hope it will be useful to someone, even if it only ends up being used as inspiration for a proper fix.