Inspect the telemetry payload

Print the exact report your install would send to the Omnia license server, without sending it.

Prerequisites

• kubectl access, including exec, to the namespace the operator runs in.

Steps

1. Run the operator binary with --print-telemetry inside the running operator pod. The examples use the namespace omnia-system and a release named omnia; substitute your install namespace and your Deployment name (<release>-controller-manager).

   kubectl exec -n omnia-system \
     deploy/omnia-controller-manager -- /manager --print-telemetry

2. Read the JSON on stdout. It is the full request body: cluster_fingerprint, license_id (registered installs only), version, and a telemetry object. See the Install telemetry reference for the meaning of each field.

3. Read the status line on stderr. It says whether the periodic reporter is enabled for this install.

4. To see the version the periodic reporter sends, add --product-version=<appVersion>, using the chart’s appVersion. Without it, version reads dev, because the command does not inherit the running operator’s flag.

   kubectl exec -n omnia-system \
     deploy/omnia-controller-manager -- /manager --print-telemetry --product-version=<appVersion>

To capture only the payload, redirect stderr:

kubectl exec -n omnia-system \
  deploy/omnia-controller-manager -- /manager --print-telemetry 2>/dev/null

Verify

The command exits after printing. The status line on stderr reads telemetry status: ENABLED for this install when the periodic reporter is on, or telemetry status: DISABLED for this install (OMNIA_TELEMETRY_ENABLED=false) when it is off. When it is off, the JSON on stdout is a preview of what would be sent if you re-enabled it.

Related pages

• Install telemetry reference
• Disable install telemetry