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.

KSQL

Confluent uses beacons in KSQL to collect information about KSQL including the version, the duration and frequency of operation, the deployment mode (e.g., server, embedded, remote CLI, local CLI).  KSQL sends this data using an encrypted connection to Confluent servers every 24 hours.  When KSQL 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 KSQL product and inform users whether there are running the latest version of KSQL.

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

Proactive Support

Confluent uses beacons in Kafka brokers to collect information about the Kafka broker including the version of Kafka, the version of Confluent Enterprise, a unique broker identifier that is valid for the runtime of the broker, and a unique identifier for the Kafka cluster.  The Kafka broker sends this data using an encrypted connection to Confluent servers every 24 hours.  When Kafka broker 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 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 broker configuration and restarting the broker. See the Confluent Enterprise documentation for further information.

Confluent Enterprise 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.

We use cookies to understand how you use our site and to improve your experience. Click here to learn more or change your cookie settings. By continuing to browse, you agree to our use of cookies.