Datadog application telemetry

Lifecycle can add standard Datadog labels to deployed workloads. Datadog uses these labels to correlate application logs, metrics, and traces with a service and environment.

This is application workload telemetry. It is different from pseudonymous Lifecycle CLI usage telemetry.

Understand the label values

For a Service that does not use native Helm, Lifecycle puts these labels on the Deployment and its pod template:

It also sets DD_ENV, DD_SERVICE, and DD_VERSION from these pod labels when the application does not set those variables.

Add labels to a native Helm chart

Lifecycle cannot add labels to an arbitrary native Helm chart. The chart must put them on the pod template. For example, a chart can define these values:

Then, pass the Lifecycle values through that chart’s values contract:

Use the value names that your chart defines. Keep the labels on the pod template. Datadog agents observe pods, not only the parent Deployment object.

Rendered-value check

1. Deploy the chart through Lifecycle.
2. Examine the rendered workload and pod labels.
3. Make sure that the Environment ID and Service name values exist.
4. Make sure that the values do not contain credentials or other sensitive data.
5. Query the related tags in your organization’s Datadog account.

If a field is empty, examine the chart’s value names and the generated Helm values for that Environment.