Project Metamorphosis: Wir präsentieren die Event-Streaming-Plattform der nächsten GenerationMehr Erfahren

More Information Regarding Confluent Data Collection

Control Center

Confluent uses beacons in Control Center to collect information about Control Center, including the version, license ID for subscription customers, and the duration and frequency of operation. Control Center sends this data using an encrypted connection to Confluent servers every hour. When Control Center sends this data to Confluent servers, it sends the IP address of our Customer along with this information.

The IP address is immediately pseudonymised using a hyperloglog algorithm before it is stored. https://en.wikipedia.org/wiki/HyperLogLog. The resulting hyperloglog data is in a form that cannot be attributed to a specific Customer without the use of additional information. Confluent employs technical and organizational measures to prevent reconstituting of the IP address or reversal of pseudonymization that would allow attribution of the data to a specific individual, including not collecting or keeping separate any additional information that may be used for attribution. Confluent stores the pseudonymized data for 2 years.

The resulting pseudonymised data is used by Confluent on behalf of its Customers to maintain and improve Control Center and Confluent Enterprise.

Customers may choose to disable transmission of this data to Confluent at any time by setting `confluent.support.metrics.enable=false` in the Control Center configuration and restarting Control Center.  See the Confluent Enterprise documentation for further information.

ksqlDB

Confluent uses beacons in ksqlDB to collect information about ksqlDB including the version, the duration and frequency of operation, the deployment mode (e.g., server, embedded, remote CLI, local CLI).  ksqlDB sends this data using an encrypted connection to Confluent servers every 24 hours.  When ksqlDB sends this data to Confluent servers it sends the IP address of our Customer along with this information.

The IP address is immediately pseudonymised using a hyperloglog algorithm before it is stored. https://en.wikipedia.org/wiki/HyperLogLog. The resulting hyperloglog data is in a form that cannot be attributed to a specific Customer without the use of additional information. Confluent employs technical and organizational measures to prevent reconstituting of the IP address or reversal of pseudonymization that would allow attribution of the data to a specific individual, including not collecting or keeping separate any additional information that may be used for attribution.  Confluent stores the pseudonymized data for 2 years.

The resulting pseudonymised data is used by Confluent on behalf of its Customers to maintain and improve the ksqlDB product and inform users whether there are running the latest version of ksqlDB.

Customers may choose to disable transmission of this data to Confluent at any time by setting `confluent.support.metrics.enable=false` in the ksqlDB configuration and restarting ksqlDB. See the Confluent Enterprise documentation for further information.

Proactive Support

Proactive Support is a component and feature of Confluent Platform. When telemetry is enabled, it communicates technical data to Confluent about Customer’s Confluent Platform environment, as further described below. When Proactive Support is enabled for a specific Confluent Platform component, beacons in Kafka brokers collect information about the Kafka broker including the version of Kafka, runtime performance metrics, the version of Confluent Platform, a unique broker identifier that is valid for the runtime of the broker, and a unique identifier for the Kafka cluster (collectively referred to as “Proactive Support Data”).  The Kafka broker sends Proactive Support Data using an encrypted connection to Confluent servers.

Confluent Platform 5.5 and Earlier

In Confluent Platform version 5.5 and earlier, the IP address of Customer is sent along with Proactive Support Data.

The IP address is immediately pseudonymised using a hyperloglog algorithm before it is stored. https://en.wikipedia.org/wiki/HyperLogLog. The resulting hyperloglog data is in a form that cannot be attributed to a specific Customer without the use of additional information. Confluent employs technical and organizational measures to prevent reconstituting of the IP address or reversal of pseudonymization that would allow attribution of the data to a specific individual, including not collecting or keeping separate any additional information that may be used for attribution.  Confluent stores the pseudonymized data for 2 years.

The resulting pseudonymised data is used by Confluent on behalf of its Customers to maintain and improve Confluent Enterprise.

In Confluent Platform version 5.5 and earlier, telemetry is enabled by default. Customers may choose to disable transmission of this data to Confluent at any time by setting `confluent.support.metrics.enable=false` in the broker configuration and restarting the broker. See the Confluent Platform documentation for further information.

Confluent Platform customers may choose to enable collection of more information about the Kafka broker and reporting it to Confluent by setting `confluent.support.customer.id’ to their assigned customer ID in the broker configuration and restarting the broker. The additional information includes bytes written to the broker, bytes read from the broker, incoming and outgoing bytes rate, number of topics and partitions in the cluster, broker configuration with some fields filtered out (such as SSL related configs, host name, etc.). This additional data is used by Confluent on behalf of its Customers to improve customer support and reduce time to support ticket resolution.

Proactive Support – Confluent Platform 6.0 and Later

In Confluent Platform version 6.0 and later, Proactive Support Data is used by Confluent to proactively support its customers by providing proactive alerting regarding potential issues and faster issue diagnosis when support tickets are submitted, and to maintain and improve Confluent’s products and services.

For Proactive Support Data to be sent to Confluent, customers must enable the transmission via configuration flags in the Confluent Platform component for which a customer wishes to receive Proactive Support. See the Confluent Platform documentation for further information or contact Confluent technical support regarding the enablement of such flags. Customer may choose to stop sending Proactive Support Data at any time by removing the applicable configuration flags. However, Confluent will not be able to proactively support any Confluent Platform component for which such flags are removed.