Telemetry

radkit-service sends a select amount of telemetry information to the cloud, that will provide some insights into the frequency at which features are being used by which installation, without revealing any device specific information.

For older RADKit-service installations that did not had end-to-end encryption enabled, this information was readily available to the RADKit cloud. Now, with end-to-end encryption enabled, this information is send separately as part of telemetry.

Specifically, we send telemetry messages when:

• a new RPC request is incoming: together with the name of the RPC request endpoint (e.g., “start-interactive-terminal”), and the ID of the client that is initiating the RPC request.

• an RPC request terminates: together with the same fields as for “new RPC request incoming”.

• a new incoming end-to-end encrypted session, together with the TLS version.

• end of end-to-end encrypted session, together with the duration of this connection.

Further, all telemetry includes: - the current RADKit version - the service_id for which the service was enrolled - the public IP address used for connecting to the cloud

Telemetry can be disabled using the telemetry.enable setting.