npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@instana-integration/jenkins

v1.0.0

Published

The integration package is used to support Jenkins monitoring. Once imported into your Instana environment, it enables monitoring of Jenkins jobs, builds, and system health through dashboards, alerts, etc. provided in this package.

Readme

@instana-integration/jenkins

The integration package is used to support Jenkins monitoring. Once imported into your Instana environment, it enables monitoring of Jenkins jobs, builds, and system health through dashboards, alerts, etc. provided in this package.

Dashboards

Below are the dashboards that are currently supported by this integration package.

| Dashboard Title | Description | |----------------------------|--------------------------------------------------| | Jenkins Runtime Monitoring | Dashboard for monitoring Jenkins Jobs & Overview |

Metrics

Semantic Conventions

Below are the Jenkins metrics that are currently supported by this integration package. These metrics are collected using the OpenTelemetry Jenkins receiver:

| Metric Name | Description | Unit | Type | |-------------------------------------------|------------------------------------------|--------------|-------| | jenkins.executors | Total number of executors | Count | Gauge | | jenkins.jobs.count | Total number of jobs | Count | Gauge | | jenkins.job.health_score | Health score of a job (0-100) | Score | Gauge | | jenkins.job.status | Status of a job (0=failed, 1=successful) | Status | Gauge | | jenkins.job.last_build.duration | Duration of the last build | Milliseconds | Gauge | | jenkins.job.last_build.estimated_duration | Estimated duration of the last build | Milliseconds | Gauge | | jenkins.job.last_build.age | Time since the last build | Milliseconds | Gauge | | jenkins.queue.size | Number of jobs in queue | Count | Gauge |

Resource Attributes

Below are the resource attributes that are currently supported by this integration package.

| Attribute Key | Type | Description | |---------------------|--------|-----------------------------------------------------------------| | service.name | string | This attribute is used to identify the Jenkins service. | | service.instance.id | string | This attribute is used to identify a specific Jenkins instance. |

Events

Below are the events that are currently supported by this integration package.

| Event Name | Description | |------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| | Jenkins Executor Exhaustion | Detects when Jenkins executors are fully utilized, which may cause build queuing and delays in CI/CD pipelines. | | Failed Jenkins Job | Detects when a Jenkins job has failed, which requires immediate attention to fix the build issues. | | Long Running Jenkins Build | Detects when a Jenkins build is taking significantly longer than expected, which may indicate performance issues or build process problems. | | Low Jenkins Job Health Score | Detects when a Jenkins job has a low health score, which may indicate recurring build failures or other issues with the job. | | Old Jenkins Job Build | Detects when a Jenkins job hasn't been built in a long time, which may indicate abandoned jobs or configuration issues. | | Unusual Jenkins Job Count | Detects when there is an unusually high number of Jenkins jobs, which may indicate unauthorized job creation or configuration issues. |

Installation and Usage

With Instana CLI for integration package management, you can manage the lifecycle of this package, such as downloading the package and importing it into Instana. You can find the available binaries for the CLI on different platforms on the release page of this project. Select the binary from the latest release that matches your platform to download, then rename it to stanctl-integration. You should now be able to run it on your local machine.

Downloading the package:

$ stanctl-integration download --package @instana-integration/jenkins

Importing the package into Instana:

$ stanctl-integration import --package @instana-integration/jenkins \
  --server $INSTANA_SERVER \
  --token $API_TOKEN \
  --set servicename=$SERVICE_NAME \
  --set serviceinstanceid=$SERVICE_INSTANCE_ID
  • INSTANA_SERVER: This is the base URL of an Instana tenant unit, e.g. https://test-example.instana.io, which is used by the CLI to communicate with Instana server for package lifecycle management.
  • API_TOKEN: Requests against the Instana API require valid API tokens. The API token can be generated via the Instana user interface. For more information, please refer to Instana documentation.
  • SERVICE_NAME: Logical name of the service.
  • SERVICE_INSTANCE_ID: The string ID of the service instance. The ID helps to distinguish instances of the same service that exist at the same time (e.g. instances of a horizontally scaled service).