Skip to main content

Datadog

1. Set up kube-state-metrics​

Skip this step if: kube-state-metrics is already set up with your Datadog installation. To verify this, check if there's data in the graph for an example metric kubernetes_state.container.ready in the metric Explorer.

Actions: Follow these instructions to set up kube-state-metrics in your Datadog agent. Reload your cluster agent with the updated configuration.

Verify: Use the Explorer link above to ensure data appears in the graph.

2. Ensure Datadog collects cluster names​

Skip this step if: Datadog collects the Kubernetes cluster's name. To verify this, check if there's data in the graph for an example metric system.cpu.user, which uses the kube_cluster_name field.

Actions: If the cluster name is N/A, then it can be added in one of two ways:

  • (Easiest) Ensure your Datadog agent is updated to a version that supports automatic cluster name detection (v6.11 or later), as described here.
  • Or, manually set the clusterName field in the helm chart used to install Datadog:
# For a new installation
helm install datadog-agent -f datadog-values.yaml --set datadog.clusterName=my_cluster_name --set targetSystem=linux datadog/datadog

# For updating an existing installation
helm upgrade datadog-agent -f datadog-values.yaml --set datadog.clusterName=my_cluster_name --set targetSystem=linux datadog/datadog

Verify: Use the Explorer link above to ensure data appears in the graph.

3. Create access keys​

  • Click here to create an API key by hitting the + New Key button.
  • Click here to create an Application key by hitting the + New Key button.
    • Optional: if possible, edit the Scope of this key to only include timeseries_query, since Flightcrew doesn't need access to anything else.