Datadog Agent deployment troubleshoot

Last updated: December 13, 2024

This article guides you through the troubleshoot of the Datadog Agent on Qovery using a Helm chart.

Important Considerations

  1. Environment Variables: Ensure that you're using "Override as file" for environment variables in your Helm chart configuration. "Override as arguments" may not be properly injected.

  2. Cluster Name: The clusterName value must comply with Datadog's regex pattern: ^([a-z]([a-z0-9\-]*[a-z0-9])?\.)*([a-z]([a-z0-9\-]*[a-z0-9])?)$. Valid examples include "web-dev" or "web.dev".

  3. TLS Verification: If you encounter hostname determination errors, disable TLS verification for the kubelet by setting kubelet.tlsVerify: false in your configuration.

  4. APP_KEY: Include appKey: qovery.env.DD_APP_KEY in your configuration if you enable the Cluster Agent metrics provider (clusterAgent.metricsProvider.enabled: true).

Troubleshooting

Invalid Cluster Name

If you receive an error about an invalid clusterName, ensure that the value complies with Datadog's regex pattern mentioned above.

Hostname Determination Error

If you encounter the error "Error while getting hostname, exiting: unable to reliably determine the host name", disable TLS verification for the kubelet as shown in the configuration example above.

Deployment Conflicts

Remember that Qovery allows only one deployment at a time per environment. This includes all services (apps, Helm charts, databases, etc.). If you need to deploy multiple services simultaneously, use the "Deploy All Services" API endpoint.

Additional Resources