Second TYPE line for metric name "jenkins_node_builds" or TYPE reported after samples
See original GitHub issueHi,
I’m facing a quite similar problem reported in the following closed issues:
- https://github.com/jenkinsci/prometheus-plugin/issues/245
- https://github.com/jenkinsci/prometheus-plugin/issues/250
I’m using the latest version of this plugin available on Jenkins (2.0.10
) and I can only replicate this issue with versions >= 2.0.9
.
I know there is a version 2.0.11
but seems there are no related changes there.
Is this a real bug or I’m doing something wrong? If it’s a bug, is anyone working on it?
Version report
Jenkins and plugins versions report:
Jenkins: 2.303.2
OS: Linux - 4.9.0-11
---
ace-editor:1.1
ant:1.12
antisamy-markup-formatter:2.4
apache-httpcomponents-client-4-api:4.5.13-1.0
authentication-tokens:1.4
blueocean:1.25.1
blueocean-autofavorite:1.2.4
blueocean-bitbucket-pipeline:1.25.1
blueocean-commons:1.25.1
blueocean-config:1.25.1
blueocean-core-js:1.25.1
blueocean-dashboard:1.25.1
blueocean-display-url:2.4.1
blueocean-events:1.25.1
blueocean-git-pipeline:1.25.1
blueocean-github-pipeline:1.25.1
blueocean-i18n:1.25.1
blueocean-jwt:1.25.1
blueocean-personalization:1.25.1
blueocean-pipeline-api-impl:1.25.1
blueocean-pipeline-editor:1.25.1
blueocean-pipeline-scm-api:1.25.1
blueocean-rest:1.25.1
blueocean-rest-impl:1.25.1
blueocean-web:1.25.1
bootstrap4-api:4.6.0-3
bootstrap5-api:5.1.1-1
bouncycastle-api:2.25
branch-api:2.7.0
build-timeout:1.20
caffeine-api:2.9.2-29.v717aac953ff3
checks-api:1.7.2
cloudbees-bitbucket-branch-source:2.9.11
cloudbees-disk-usage-simple:0.10
cloudbees-folder:6.16
command-launcher:1.6
credentials:2.6.1
credentials-binding:1.27
display-url-api:2.3.5
durable-task:1.39
echarts-api:5.2.1-2
email-ext:2.84
extended-read-permission:3.2
favorite:2.3.3
font-awesome-api:5.15.4-1
git:4.9.0
git-client:3.10.0
git-server:1.10
github:1.34.1
github-api:1.133
github-branch-source:2.11.3
gradle:1.37.1
handy-uri-templates-2-api:2.1.8-1.0
htmlpublisher:1.27
jackson2-api:2.13.0-230.v59243c64b0a5
jaxb:2.3.0.1
jdk-tool:1.5
jenkins-design-language:1.25.1
jjwt-api:0.11.2-9.c8b45b8bb173
jquery-detached:1.2.1
jquery3-api:3.6.0-2
jsch:0.1.55.2
junit:1.53
ldap:2.7
lockable-resources:2.12
logstash:2.5.0205.vd05825ed46bd
mailer:1.34
matrix-auth:2.6.8
matrix-project:1.19
metrics:4.0.2.8
momentjs:1.1.1
okhttp-api:3.14.9
pam-auth:1.6
pipeline-build-step:2.15
pipeline-github-lib:1.0
pipeline-graph-analysis:1.11
pipeline-input-step:2.12
pipeline-milestone-step:1.3.2
pipeline-model-api:1.9.2
pipeline-model-definition:1.9.2
pipeline-model-extensions:1.9.2
pipeline-rest-api:2.19
pipeline-stage-step:2.5
pipeline-stage-tags-metadata:1.9.2
plain-credentials:1.7
plugin-util-api:2.5.0
popper-api:1.16.1-2
popper2-api:2.10.2-1
prometheus:2.0.10
pubsub-light:1.16
resource-disposer:0.16
role-strategy:3.2.0
scm-api:2.6.5
script-security:1.78
snakeyaml-api:1.29.1
sse-gateway:1.24
ssh-credentials:1.19
ssh-slaves:1.33.0
sshd:3.1.0
statistics-gatherer:2.0.3
structs:1.23
timestamper:1.13
token-macro:266.v44a80cf277fd
trilead-api:1.0.13
variant:1.4
workflow-api:2.47
workflow-basic-steps:2.24
workflow-cps:2.94
workflow-cps-global-lib:2.21
workflow-durable-task-step:2.40
workflow-job:2.42
workflow-multibranch:2.26
workflow-scm-step:2.13
workflow-step-api:2.24
workflow-support:3.8
ws-cleanup:0.39
- What Operating System are you using (both controller, and any agents involved in the problem)?
OS: Linux - 4.9.0-11
Reproduction steps
- Launch telegraf with the following configuration
...
[[inputs.prometheus]]
urls = ["myurl/prometheus/"]
username = "myuser"
password = "mypassw"
...
- Start running jobs and we’ll receive the following error:
[inputs.prometheus] Error in plugin: error reading metrics for URL/prometheus/: reading text format failed: text format parsing error in line 1774: second TYPE line for metric name "jenkins_node_builds", or TYPE reported after samples
I only have the error when the metrics for master
are displayed
# HELP jenkins_node_builds Generated from Dropwizard metric import (metric=jenkins.node.builds, type=com.codahale.metrics.Timer)
# TYPE jenkins_node_builds summary
jenkins_node_builds{node="master",quantile="0.5",} 0.108072807
jenkins_node_builds{node="master",quantile="0.75",} 0.108072807
jenkins_node_builds{node="master",quantile="0.95",} 0.108072807
jenkins_node_builds{node="master",quantile="0.98",} 0.108072807
jenkins_node_builds{node="master",quantile="0.99",} 0.108072807
jenkins_node_builds{node="master",quantile="0.999",} 0.108072807
Results
(from the previous reports)
Expected result:
# HELP jenkins_node_builds Generated from Dropwizard metric import (metric=jenkins.node.builds, type=com.codahale.metrics.Timer)
# TYPE jenkins_node_builds summary
jenkins_node_builds{node="master",quantile="0.5",} 0.108072807
jenkins_node_builds{node="master",quantile="0.75",} 0.108072807
jenkins_node_builds{node="master",quantile="0.95",} 0.108072807
jenkins_node_builds{node="master",quantile="0.98",} 0.108072807
jenkins_node_builds{node="master",quantile="0.99",} 0.108072807
jenkins_node_builds{node="master",quantile="0.999",} 0.108072807
jenkins_node_builds_count{node="master"} 1.0
jenkins_node_builds{node="test3",quantile="0.5",} 0.0
jenkins_node_builds{node="test3",quantile="0.75",} 0.0
jenkins_node_builds{node="test3",quantile="0.95",} 0.0
jenkins_node_builds{node="test3",quantile="0.98",} 0.0
jenkins_node_builds{node="test3",quantile="0.99",} 0.0
jenkins_node_builds{node="test3",quantile="0.999",} 0.0
jenkins_node_builds_count{node="test3"} 0.0
Actual result:
# HELP jenkins_node_test3_builds Generated from Dropwizard metric import (metric=jenkins.node.test3.builds, type=com.codahale.metrics.Timer)
# TYPE jenkins_node_test3_builds summary
jenkins_node_builds{node="test3",quantile="0.5",} 0.0
jenkins_node_builds{node="test3",quantile="0.75",} 0.0
jenkins_node_builds{node="test3",quantile="0.95",} 0.0
jenkins_node_builds{node="test3",quantile="0.98",} 0.0
jenkins_node_builds{node="test3",quantile="0.99",} 0.0
jenkins_node_builds{node="test3",quantile="0.999",} 0.0
jenkins_node_builds_count{node="master"} 1.0
# HELP jenkins_node_builds Generated from Dropwizard metric import (metric=jenkins.node.builds, type=com.codahale.metrics.Timer)
# TYPE jenkins_node_builds summary
jenkins_node_builds{node="master",quantile="0.5",} 0.108072807
jenkins_node_builds{node="master",quantile="0.75",} 0.108072807
jenkins_node_builds{node="master",quantile="0.95",} 0.108072807
jenkins_node_builds{node="master",quantile="0.98",} 0.108072807
jenkins_node_builds{node="master",quantile="0.99",} 0.108072807
jenkins_node_builds{node="master",quantile="0.999",} 0.108072807
jenkins_node_builds_count{node="test3"} 0.0
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
second HELP line for metric name - Google Groups
I'm in the process of updating an application which exported metrics via JMX beans exposed by the jmx javaagent to use a native...
Read more >Query functions - Prometheus.io
An open-source monitoring system with a dimensional data model, flexible query language, efficient time series database and modern alerting approach.
Read more >Key concepts - VictoriaMetrics
Label-value pairs are always of a string type. VictoriaMetrics data model is schemaless, which means there is no need to define metric names...
Read more >Collect metrics - .NET | Microsoft Learn
Create an example application; View metrics with dotnet-counters ... Threading; class Program { static Meter s_meter = new Meter("HatCo.
Read more >Micrometer Metrics - Quarkus
Meter names, for example, should be created and named using dots to separate ... The most common types of meters supported by monitoring...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I promise to look at this on Sunday of this week.
Cc @nsakovich @NARSimoes @lmmc @sakhi-arya
We are facing the exact same issue, is there any workaround available for now until there is a fix pushed for this?