Whether code-manager will wait for all deploys to finish or error to return a response

Whether the deploy is a dry-run

List of environments requested to deploy

List of deploy requests

Total time elapsed for all deploys to finish or error

List of total wait times for deploys specifying --wait option

Name of environment deployed

Time needed for r10k to run

Time spent committing to file sync

Time elapsed for all environment hooks to run

List of individual environment deploys

Backup and Restore information:

Whether user used --force option when running restore

Scope of restore

Time in seconds for various restore functions

Time to check for disk space to restore

Time to stop PE related services

Time to restore PE file system components

Time to migrate PE configuration for new server

Time to configure PE on newly restored master

Time to update PE classification for new server

Time to deactivate the old Master of Masters node

Time to restore the pe-orchestrator database

Time to restore the pe-rbac database

Time to restore the pe-classifier database

Time to restore the pe-activity database

Time to restore the pe-puppetdb database

Total time to restore

List of puppet backup restore jobs

Whether user used --force option when running puppet-backup create

Whether user used --dir option when running puppet-backup create

Whether user used --name option when running puppet-backup create

Scope of backup

Time in seconds for various back up functions

Time needed to estimate backup size, disk space needed, and disk space available

Time to create file system backup

Time to back up the pe-orchestrator database

Time to back up the pe-rbac database

Time to back up the pe-classifier database

Time to back up the pe-activity database

Time to back up the pe-puppetdb database

Time to compress archive file to backup directory

Time to back up PE related classification

Total time to back up

List of puppet-backup create jobs

Puppet Server performance information:

Total number of JRuby instances

Maximum number of active JRuby instances

Maximum number of requests per JRuby instance

Average number of instances not in use over the process’s lifetime

Average wait time to lock the JRuby pool

Average time the JRuby pool held a lock

Average time an instance spent handling requests

Average time spent waiting to reserve an instance from the JRuby pool

Number of requests that timed out while waiting for a JRuby instance

Amount of memory the JVM starts with

Maximum amount of memory the JVM is allowed to request from the operating system

If PE is installed using an Amazon Web Services Marketplace Image:

The marketplace name

Marketplace image billing mode (bring your own license or pay as you go)

While in use, the console collects the following information:

Pageviews

Link and button clicks

Page load time

User language

Screen resolution

Viewport size

Anonymized IP address

The console does not collect user inputs such as node or group names, user names, rules, parameters, or variables

The collected data is tied to a unique, anonymized identifier for each master and your site as a whole. No personally identifiable information is collected, and the data we collect is never used or shared outside Puppet, Inc.

How does sharing this data benefit you?

We use the data to identify organizations that could be affected by a security issue, alert them to the issue, and provide them with steps to take or fixes to download. In addition, the data helps us understand how people use the product, which helps us improve the product to meet your needs.

How does Puppet use the collected data?

The data we collect is one of many methods we use for learning about our customers. For example, knowing how many nodes you manage helps us develop more realistic product testing. And learning which operating systems are the most and the least used helps us decide where to prioritize new functionality. By collecting data, we begin to understand you as a customer.

Opt out during the installation process

To opt out of data collection during installation, you must use text-mode installation. Text-mode installation uses the pe.conf file to set parameters and values needed for the install.

If you prefer to use one of the non-text-mode installation methods, you can opt out of data collection after installation.

Follow the instructions for a monolithic text-mode install or a split text-mode install.

When you edit the pe.conf file, set the puppet_enterprise::send_analytics_data variable to false:

"puppet_enterprise::send_analytics_data": false

Follow the rest of the text-mode installation instructions.

By running Puppet with this setting, you will be opted out of data collection.