lsjostro/prometheus-plugin

Jenkins Prometheus Plugin

Jenkins Prometheus Metrics Plugin

About

Jenkins Prometheus Plugin expose an endpoint (default /prometheus) with metrics where a Prometheus Server can scrape.

Metrics exposed

Currently only metrics from the Metrics-plugin and summary of build duration of jobs and pipeline stages

Environment variables

PROMETHEUS_NAMESPACE Prefix of metric (Default: default).

PROMETHEUS_ENDPOINT REST Endpoint (Default: prometheus)

Building

mvn hpi:hpi

Author / Maintainer

Lars Sjöström

Credits

fabric8io team. Open.source.ftw++!

prometheus-plugin's Issues

Can this repository be considered abandoned?

Since this repository moved to the Jenkins org, can this be considered abandoned?

Deleting this repo or pointing from readme would make it easier for consumers find the more recent fork.

Massive CPU spike from threads not completing

Hello,

I am seeing a massive CPU spike when I install the plugin (near 100% CPU utilization). I noticed that there are many prometheus threads running in the background continuously (20+). After uninstalling the plugin it drops back down to idle.

Plugin giving a 504 after 60seconds

Hello.
I have installed the prometheus-plugin on my Jenkins server (Jenkins version 2.7.20.2).
However when I try to hit /prometheus my browser tries for a minute and then gets a 504 The server didn't respond in time.

Any ideas why this maybe happening?

Cheers

Error introduced between 2.0.8 and 2.0.10

Hi,

We recently updated this plugin to 2.0.10 and now we see this error in the journalctl -u telegraf logs:

telegraf[7915]: 2021-04-20T13:52:30Z E! [inputs.prometheus] Error in plugin: error reading metrics for http:///prometheus/: reading text format failed: text format parsing error in line 1394: second TYPE line for metric name "jenkins_node_builds", or TYPE reported after samples

I've tested this with a different installation of telegraf to the same jenkins intance and it reports the same error.

I've tested using the same telegraf and an instance of jenkins where the plugin has not been upgraded and there is no error.

This suggests the upgrade version is the culprit.

Any thoughts?

Cheers
Phill