- Documentation
- Red Hat Advanced Cluster Security for Kubernetes
- Telemetry
- Opting out of Telemetry history bug_report picture_as_pdf
- About
- Release notes
- RHACS Cloud Service
- Service description
- Getting started with RHACS Cloud Service
- Default resource requirements for RHACS Cloud Service
- Recommended resource requirements for RHACS Cloud Service
- Setting up RHACS Cloud Service with Red Hat OpenShift secured clusters
- Creating a RHACS Cloud Service instance on Red Hat Cloud
- Creating a project on your Red Hat OpenShift secured cluster
- Generating an init bundle for secured clusters
- Applying an init bundle for secured clusters
- Installing the RHACS Operator for RHACS Cloud Service
- Installing secured cluster services from RHACS Cloud Service
- Configuring the proxy for secured cluster services in RHACS Cloud Service
- Verifying installation of secured clusters
- Setting up RHACS Cloud Service with Kubernetes secured clusters
- Creating a RHACS Cloud Service instance for Kubernetes clusters
- Generating an init bundle for Kubernetes secured clusters
- Applying an init bundle for Kubernetes secured clusters
- Installing secured cluster services from RHACS Cloud Service on Kubernetes clusters
- Verifying installation of secured clusters
- Architecture
- Installing
- High-level RHACS installation overview
- Default resource requirements for RHACS
- Recommended resource requirements for RHACS
- Installing RHACS on Red Hat OpenShift
- Installing Central services for RHACS on Red Hat OpenShift
- Configuring Central configuration options for RHACS using the Operator
- Generating and applying an init bundle for RHACS on Red Hat OpenShift
- Installing Secured Cluster services for RHACS on Red Hat OpenShift
- Configuring Secured Cluster services options for RHACS using the Operator
- Verifying installation of RHACS on Red Hat OpenShift
- Installing RHACS on other platforms
- Uninstalling Red Hat Advanced Cluster Security for Kubernetes
- Configuring
- Adding custom certificates
- Adding trusted certificate authorities
- Reissuing internal certificates
- Adding security notices
- Enabling offline mode
- Enabling alert data retention
- Exposing the RHACS portal over HTTP
- Configuring automatic upgrades for secured clusters
- Configuring automatic removal of nonactive clusters
- Configuring a proxy for external network access
- Generating a diagnostic bundle
- Configuring endpoints
- Monitoring
- Enabling audit logging
- Configuring API tokens
- Using declarative configuration
- Inviting users to your RHACS instance
- Operating
- Viewing the dashboard
- Using the Compliance Operator
- Managing Compliance
- Evaluating security risks
- Using admission controller enforcement
- Managing security policies
- Default security policies
- Managing network policies
- Build-time network policy tools
- Auditing listening endpoints
- Reviewing cluster configuration
- Examining images for vulnerabilities
- Verifying image signatures
- Managing vulnerabilities
- Responding to violations
- Using deployment collections
- Searching and filtering
- Managing user access
- Using the system health dashboard
- Using the administration events page
- Integrating
- Integrating with image registries
- Integrating with CI systems
- Integrating with PagerDuty
- Integrating with Slack
- Integrating by using generic webhooks
- Integrating with QRadar
- Integrating with ServiceNow
- Integrating with Sumo Logic
- Integrating with Google Cloud Storage
- Integrating by using the syslog protocol
- Integrating with Amazon S3
- Integrating with Google Cloud Security Command Center
- Integrating with Splunk
- Integrating with image vulnerability scanners
- Integrating with Jira
- Integrating with Email
- Integrating with cloud management platforms
- Integrating using short-lived tokens
- Backup and restore
- Upgrading
- roxctl CLI
- Troubleshooting Collector
- Troubleshooting Central
- Telemetry
- Support
×
Opting out of Telemetry
The decision to opt out of telemetry should be based on your specific needs and requirements, as well as any applicable regulations or policies that you need to comply with.
Consequences of disabling Telemetry
In Red Hat Advanced Cluster Security for Kubernetes (RHACS) version 4.0, you can opt out of Telemetry. However, telemetry is embedded as a core component, so opting out is strongly discouraged. Opting out of telemetry limits the ability of Red Hat to understand how everyone uses the product and which areas to prioritize for improvements.
Disabling Telemetry
If you have configured Telemetry by setting the key in your environment, you can disable Telemetry data collection from the Red Hat Advanced Cluster Security for Kubernetes (RHACS) user interface (UI).
Procedure
-
In the RHACS portal, go to Platform Configuration > System Configuration.
-
In the System Configuration header, click Edit.
-
Scroll down and ensure that Online Telemetry Data Collection is set to Disabled.