simplesurance / jenkins-exporter Goto Github PK

Throttle the number of API requests that are made to retrieve per-stage metrics.
If metrics for a lot of builds are retrieved, sending tons of requests to the jenkins-server in a loop could generate too much load.
Ideally the number of requests are configurable via a parameter.

I had installed ur binary and tried to run it like below

./jenkins-exporter-linux_amd64 -jenkins-url -jenkins-user= -jenkins-password= -jenkins-job-whitelist=

While the server starts, I don't see any entry related to jenkins job

When multiple builds run for the same job, it can happen that build N finishes before build N-1.
If the jenkins-exporter retrieves an unfinished build it removes it from the result, if a following build already has finished, it's build number is recorded as highest seen buildnr and all previous builds are ignored.

This caused that metrics for builds are often not recorded.

Sometimes the result of a build is "success" but some stage statuses are still "in progress".
This causes that metrics for those stages won't be recorded.
This might also cause that the overall runtime metrics for a build are wrong because they are recorded while the build is still running.

A successful build result surprisingly can not be used to determine if a build has finished, find another value that can be queried instead.

It is not an issue but like to know the below
you have any idea about working on total number of builds, successful builds, failed builds and killed builds

it will be helpful for all if you do so

Hi, is there already a dashboard available to visualize the metrics? With grafana for example?