Jenkins infrastructure performance extension
- Latest Dynatrace
- Extension
- Published Oct 27, 2025
Monitor Jenkins infrastructure for performance and health.
Get started
Overview
This Dynatrace extension collects metrics related to Jenkins jobs, builds, nodes, and overall system health, enabling users to gain insights into their Jenkins infrastructure.
By combining all relevant data into pre-configured dashboards, this extension facilitates alerting and event tracking.
This extension depends on observability signals that are pushed to Dynatrace from Jenkins, using the Dynatrace Jenkins Plugin In order to use this extension, you need to:
- Deploy the Dynatrace Jenkins Plugin on your Jenkins tenant and set it up to forward signals to Dynatrace.
- Activate this extension on your Dynatrace tenant to report on the metrics in context. This extension does not need an Active Gate, nor OneAgent.
Use cases
- Monitor the health, performance, and availability of your Jenkins infrastructure.
- Analyze trends and baselines of Jenkins job execution times, build success rates, and resource utilization.
- Raise alerts on anomalies detected in Jenkins KPIs, such as failed builds or node offline events.
- Enable essential monitoring for their Jenkins infrastructure with ease.
- Seek a dedicated out-of-the-box dashboard for Jenkins monitoring.
- Are aware that foundational Jenkins infrastructure monitoring provided by this extension is not the same as an integrated CI/CD pipeline observability.
- Monitor Jenkins jobs, builds, and nodes for performance and availability.
- Track Jenkins system health, including memory usage, thread counts, and disk space.
This extension doesn't address the CI/CD pipeline observability needs. It delivers Jenkins infrastructure monitoring basics.
If you're looking for an integrated CI/CD pipeline observability, see Dynatrace pipeline observability section. This resource will guide you through the software development lifecycle (SDLC) concepts and how Dynatrace supports ingest and analysis of the SDLC events for the insights and automated remediation of issues.
Activation and setup
Deploy the Dynatrace Jenkins plugin on Jenkins
- Follow instructions on the Dynatrace Jenkins Plugin to download the plugin files.
- Upload from the Jenkins web UI > Manage Jenkins > Plugins > Advanced > Deploy Plugin. Or directly on the controller.
- Set your Dynatrace Tenant URL and an Access token with log and metric ingest scopes (
logs.ingestandmetrics.ingestscopes are required).
Note that you may choose to build your own version of the plugin from the source, instead of using the already-built HPI file. Follow instructions on the Dynatrace Jenkins Plugin.
Activate the Jenkins extension on Dynatrace
Once data is flowing to Dynatrace, you can activate the Jenkins Extension on your Dynatrace Tenant to enable dashboard and Unified Analysis screens (no Active Gate is required).
Details
The Dynatrace Jenkins Plugin is built with the Jenkins Plugin SDK, runs on your Jenkins, and pushes metrics to Dynatrace via API. It is a required source of data that this extension uses.
This extension delivers dashboards, screens and metrics metadata that bring context to the signals received from the Jenkins plugin.
Licensing and cost
An estimated formula for DDU consumption of the extension is:
14 * 525.6 DDUs/year
DDU cost above does not include any possible Log events or Custom events triggered by the extension. For more information on this, please visit the DDU log event cost and DDU custom event cost pages.
Feature sets
When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
