Find plugins

2.0.3Minimum Jenkins requirement: 2.60.3ID: influxdb

⚠️ Older versions of this plugin may not be safe to use. Please review the following warnings before using an older version:

Jenkins Plugin Jenkins.io Build Status Jenkins Plugin Installs


Collects data from various other Jenkins plugins and sends metrics to InfluxDB. It's also possible to write custom data inside pipeline jobs to be sent.

⚠️ From version 1.13 onwards different plugins are listed as optional dependencies. In order to get rid of mandatory dependency errors, InfluxDB plugin must be re-installed.

⚠️ Breaking changes in 2.0

  • From version 2.0 onwards "selectedTarget" is a mandatory parameter for pipelines and "target" parameter is no longer supported.
  • Configuration As Code: the configuration needs to be changed from `influxDbPublisher` to `influxDbGlobalConfig`.
  • Might cause issues when creating new targets in pipelines. The InfluxDbPublisher instance is now under jenkinsci.plugins.influxdb.InfluxDbStep.DescriptorImpl.

Supported Metrics

  • All metrics
    • Build number
    • Project Name
    • Project Path
  • jenkins_data
    • Build health
    • Build status message
    • Build time
    • Build Agent name
    • Job duration
    • Build result
    • Build result ordinal (0=Stable, 1=Unstable, 2=Failure, 3=Not built, 4=Aborted, 5=Unknown (for pipelines))
    • Successful build boolean
    • Last stable build number (or 0 if never)
    • Last successful build number (or 0 if never)
    • Tests failed (unit test results from JUnit Plugin)
    • Tests skipped (unit test results from JUnit Plugin)
    • Tests total (unit test results from JUnit Plugin)
    • Time in queue (from Metrics plugin)
    • Build scheduled time
    • Build start time
    • Build measured time
  • cobertura_data
    • Package coverage %
    • Class coverage %
    • Line coverage %
    • Branch coverage %
    • Amount of packages
    • Amount of source files
    • Amount of classes
  • rf_results
    • Test case name
    • Suite name
    • Duration
    • Amount of suites
    • Amount of passed tests
    • Amount of failed tests
    • Amount of total tests
    • Pass percentage of all tests
    • Amount of passed critical tests
    • Amount of failed critical tests
    • Total amount of critical tests
    • Pass percentage of critical tests
  • suite_result
    • All the same data as for rf_results, except:
      • Pass percentage for all tests
      • Pass percentage of critical tests
      • Test case name
  • tag_point
    • All the same data as for rf_results, except:
      • Pass percentage of all tests
      • Pass percentage of critical tests
      • Test case name
      • Suite name
      • Amount of suites
    • Extra data for this measurement:
      • Tag name
  • testcase_point
    • All the same data as for rf_results, except:
      • Amount of suites
      • Amount of total tests
      • Pass percentage of critical tests
      • Total amount of critical tests
      • Pass percentage of all tests
  • jacoco_data
    • Package coverage %
    • Class coverage %
    • Line coverage %
    • Branch coverage %
    • Method coverage %
    • Instruction coverage %
  • performance_data
    • Total amount of errors
    • Percentage of errors
    • Average sample duration
    • Max/min sample duration
    • Size of samples
    • Total count of samples
    • 90 percentile
  • sonarqube_data
    • Amount of major/minor/critical/blocker/info issues
    • Lines of code
    • Build display name
  • changelog_data
    • Affected files
    • Commit authors
    • Commit messages
    • Commit count
  • perfpublisher_summary
    • Number of total/executed/not-executed/passed/failed/success/true-false tests
    • Best compile time test value/name
    • Worst compile time test value/name
    • Average compile time
    • Best performance test value/name
    • Worst performance test value/name
    • Average performance
    • Best execution time test value/name
    • Worst execution time test value/name
  • perfpublisher_metric
    • Metric name
    • Average value for metric
    • worst value for metric
    • best value for metric
  • perfpublisher_test
    • Test name
    • Was test successful/executed
    • Test message
    • Compile time
    • Execution time
    • Performance
  • perfpublisher_test_mnetric
    • Test name
    • Metric name/value/relevancy


Create a database in InfluxDB and a user with access rights. In Jenkins, go to Manage Jenkins > Configure System > InfluxDB Targets and click "Add". Provide the database information. The "URL" parameter requires the whole URL of the InfluxDB database, including the http(s):// and the database port. Also, provide the retention policy you want the data to be stored in InfluxDB (e.g. 15m or 2d for 15 minutes or 2 days respectively). By default, the retention policy is infinite. Exceptions generated by the InfluxDB plugin can also be ignored by deselecting the "Expose Exceptions" checkbox.

In your job, select "Publish build data to InfluxDB" from the post-build actions.

Select the InfluxDB target you wish to publish the data to.

From the Advanced tab you can choose to set a custom prefix for your project_name field, a custom project name to be used instead of the default job name and custom fields and tags for your jenkins_data metric.


The plugin can be called either by using the influxDbPublisher() or step function. The influxDbPublisher format is only supported from version 1.21 onwards.

Pipeline syntax

The only mandatory parameter is selectedTarget, which is the "Description" for your target in the global configuration.

influxDbPublisher(selectedTarget: 'myTarget'[, any other parameters you want to use])
step([$class: 'InfluxDbPublisher',
        selectedTarget: 'myTarget',
        customPrefix: null,                             // OPTIONAL
        customProjectName: null,                        // OPTIONAL
        customData: null,                               // OPTIONAL
        customDataMap: null,                            // OPTIONAL
        jenkinsEnvParameterTag: 'KEY=' + env.PARAM,     // OPTIONAL, custom tags
        jenkinsEnvParameterField: 'KEY=' + env.PARAM,   // OPTIONAL, custom fields
        measurementName: 'myMeasurementName',           // OPTIONAL, custom measurement name. Replaces default "jenkins_data" and "jenkins_custom_data"

customData and customDataMap are custom data generated during the build and not by the plugin, so they are not available in the snippet generator.

❗️ NOTE! Up to release 1.10.3, pipeline was configured with the use the url and database.

step([$class: 'InfluxDbPublisher',
       target: ',jenkins_db',
       customPrefix: null,
       customProjectName: null,
       customData: null,
       customDataMap: null,

This form of configuration is not supported from version 1.11 onwards.

Pipelines don't have post-build actions, so the build result, build ordinal, and the build success boolean will default to "?", 5, and false respectively, unless set manually before calling InfluxDbPublisher. Only the build result needs to be set manually, as the boolean value and ordinal are set based build result. Also, the build status will appear as "?" and the build duration might be a little off, because the build is not actually finished. If you want to get those pieces of information you need to configure the plugin separately on each job as a post-build action. The jobs can be run with, for example, the Build Pipeline Plugin to get data from all jobs to InfluxDB. Alternatively, you can insert the information in your build manually inside your Groovy script.

try {
    // Build things here
    if (currentBuild.result == null) {
        currentBuild.result = 'SUCCESS' // sets the ordinal as 0 and boolean to true
} catch (err) {
    if (currentBuild.result == null) {
        currentBuild.result = 'FAILURE' // sets the ordinal as 4 and boolean to false
    throw err
} finally {
    influxDbPublisher selectedTarget: 'myTarget'

Create a target in pipeline

From version 1.19 onwards, you can create and remove targets in pipelines directly.

// Get InfluxDB plugin descriptor (version < 2.0)
def influxdb = Jenkins.instance.getDescriptorByType(jenkinsci.plugins.influxdb.DescriptorImpl)

// version >= 2.0
def influxdb = Jenkins.instance.getDescriptorByType(jenkinsci.plugins.influxdb.InfluxDbStep.DescriptorImpl)

// Create target
def target = new jenkinsci.plugins.influxdb.models.Target()

// Set target details
// Mandatory fields
target.description = 'myNewTarget'
target.url = 'http://influxdburl:8086'
target.username = 'myUsername'

// version < 2.0
target.password = 'myPassword'

// version >= 2.0
hudson.util.Secret password = hudson.util.Secret.fromString('myPassword')
target.password = password

target.database = 'myDatabase'

// Optional fields
target.exposeExceptions = true // default = true
target.jobScheduledTimeAsPointsTimestamp = true // default = false
target.usingJenkinsProxy = true // default = false
target.retentionPolicy = '1d' // default = 'autogen'

// Add a target by using the created target object

// Write stuff to InfluxDB
influxDbPublisher selectedTarget: 'myNewTarget'

// Remove a target by using the target description field value

Custom Data

You can create custom data in Jenkins pipelines. Custom data can be written to Influx like this:

def myDataMap = [:]
myDataMap['myKey'] = 'myValue'
InfluxDbPublisher selectedTarget: 'myTarget', customData: myDataMap

This adds the key myKey with a value myValue to a measurement called jenkins_custom_data.

You can also create your own measurements with customDataMaps:

def myDataMap1 = [:]
def myDataMap2 = [:]
def myCustomDataMap = [:]
myDataMap1['myMap1Key1'] = 11 // first value of first map
myDataMap1['myMap1Key2'] = 12 // second value of first map
myDataMap2['myMap2Key1'] = 21 // first value of second map
myDataMap2['myMap2Key2'] = 22 // second value of second map
myCustomDataMap['series1'] = myDataMap1
myCustomDataMap['series2'] = myDataMap2
influxDbPublisher selectedTarget: 'myTarget', customDataMap: myCustomDataMap

That script creates 2 measurements: series1 and series2. It adds keys myMap1Key1 and myMap1Key2 with values 11 and 12 respectively to series1 and myMap2Key1 and myMap2Key2 with values 21 and 22 respectively to series2.

You can also set tags for your custom measurements with either customDataTags or customDataMapTags. Tags added with customDataTags are added to the measurement jenkins_custom_data. If you use customDataMapTags you must use the same map keys as the measurement names in customDataMap.


Create a pull request to the development branch. No pull requests are merged directly to master. Comment your changes sufficiently and create appropriate tests.

If you have an idea for a new feature or you want to report a bug, please use the Jenkins issue tracker.

ArchivesGet past versions

Previous Security Warnings