The CloudBees Analytics Plugin collects anonymized telemetry and usage metrics to help you get more value from your CloudBees investment. By enabling this plugin, your team gains access to personalized recommendations, data-driven insights, and faster troubleshooting support.
| Data collection is enabled by default, but you can disable it at any time. For CloudBees CI, refer to Enable or disable data collection for the CloudBees Analytics Plugin to disable it. |
CloudBees takes data privacy very seriously. Here’s how CloudBees ensures privacy while delivering value:
-
Anonymization: Identifying data such as names, job names, URLs, and instance IDs are anonymized.
-
Event data: Telemetry data includes aggregated metrics (for example, the number of job runs and feature usage) and is associated at the organization level, not individual users.
-
Insights without individual inspection: Recommendations are based on anonymized patterns. For example, CloudBees knows that builds are being run, but not who ran them. Similarly, CloudBees knows Role-Based Access Control (RBAC) is in use, but does not track specific permissions or access.
CloudBees does not inspect analytics/telemetry data at an individual level. Instead, our focus is on organization-wide trends to provide actionable insights.
The telemetry data allows CloudBees to:
-
Proactively identify underutilized features and help you unlock their value
-
Compare adoption trends and offer tailored suggestions to improve DevOps efficiency
-
Support capability assessments and Quarterly Business Reviews (QBRs)
-
Help accelerate issue resolution by understanding your unique usage patterns
All data collected is anonymized and aggregated, ensuring your privacy is protected. The goal is to enhance your experience and outcomes with CloudBees, in addition to improving our products.
Data collected with every event
The following data is sent with every event that is captured:
| Description | Anonymized |
|---|---|
Instance ID |
Yes |
Product name |
No |
Product version |
No |
Organization licensed to use the product |
No |
Specific data
The names of events and the specific data captured with those events vary according to installed plugins. The exact event and property names used by this system are automatically recorded in CloudBees CI.
To view event and property names:
-
Sign on to the controller.
-
Select Manage Jenkins in the left pane.
-
Select Configure System.
-
Scroll down to Usage Statistics.
-
Select the ? icon for the Help make CloudBees better by sending telemetry and metrics to evaluate patterns of usage checkbox.
-
Select the see details link in the expanded help text to view all the events your controller is currently configured to send.
Enable or disable data collection for the CloudBees Analytics Plugin
To enable or disable data collection for each operations center and controller:
-
Navigate to .
-
Under Usage Statistics, toggle Help make CloudBees
<product name>better by sending telemetry and metrics to evaluate patterns of usage.The <product name>depends on the product that you are using.Alternatively, you can disable the data collection by adding the
-Dcom.cloudbees.analytics.gatherer.Sender.disabled=truesystem property to your launch scripts. -
If enabling data collection, ensure your instance has connectivity to
https://api.segment.io/for product usage reporting. For more information, refer to Required URLs to allowlist.To test connectivity, run the following command from your operations center and controllers:
nc -zv api.segment.io 443 # or curl -v https://api.segment.io/ 2>&1 | grep 'Connected to api.segment.io'If there is connectivity, the output should appear similar to the following:
Connection to api.segment.io port 443 [tcp/https] succeeded! # or * Connected to api.segment.io (...) port 443 (#0)If you get no response or the command hangs, check with your IT/networking team to allow connectivity.