Agent Flare
New announcements from Dash: Incident Management, Continuous Profiler, and more! New announcements from Dash!

Agent Flare

If you are running Agent 5.3+, you can send necessary troubleshooting information to the Datadog support team with one flare command.

flare gathers all of the Agent’s configuration files and logs into an archive file. It removes sensitive information including passwords, API keys, Proxy credentials, and SNMP community strings. Confirm the upload of the archive to immediately send it to Datadog support.

The Datadog Agent is completely open source, which allows you to verify the code’s behavior. If needed, the flare can be reviewed prior to sending since the flare prompts a confirmation before uploading it.

In the commands below, replace <CASE_ID> with your Datadog support case ID if you have one, then enter the email address associated with it.

If you don’t have a case ID, just enter your email address used to login in Datadog to create a new support case.

AIXdatadog-agent flare <CASE_ID>
Dockerdocker exec -it datadog-agent agent flare <CASE_ID>
macOSdatadog-agent flare <CASE_ID> or via the web GUI
CentOSsudo datadog-agent flare <CASE_ID>
Debiansudo datadog-agent flare <CASE_ID>
Kuberneteskubectl exec <POD_NAME> -it agent flare <CASE_ID>
Fedorasudo datadog-agent flare <CASE_ID>
Redhatsudo datadog-agent flare <CASE_ID>
Susesudo datadog-agent flare <CASE_ID>
Sourcesudo datadog-agent flare <CASE_ID>
WindowsConsult the dedicated Windows documentation
HerokuConsult the dedicated Heroku documentation

Dedicated containers

When using Agent v7.19+ and using the Datadog Helm Chart with the latest version or a DaemonSet where the Datadog Agent and Trace Agent are in separate containers, you will deploy an Agent Pod containing:

  • One container with the Agent process (Agent + Log Agent)
  • One container with the process-agent process
  • One container with the trace-agent process
  • One container with the system-probe process

To get a flare from each container, run the following commands:


kubectl exec -it <agent-pod-name> -c agent -- agent flare <case-id>


kubectl exec -it <AGENT_POD_NAME> -c process-agent -- agent flare <CASE_ID> --local


kubectl exec -it <AGENT_POD_NAME> -c trace-agent -- agent flare <CASE_ID> --local


kubectl exec -it <AGENT_POD_NAME> -c system-probe -- agent flare <CASE_ID> --local
Dockerdocker exec -it dd-agent /etc/init.d/datadog-agent flare <CASE_ID>
macOSdatadog-agent flare <CASE_ID>
CentOSsudo service datadog-agent flare <CASE_ID>
Debiansudo service datadog-agent flare <CASE_ID>
Kuberneteskubectl exec <POD_NAME> -it /etc/init.d/datadog-agent flare <CASE_ID>
Fedorasudo service datadog-agent flare <CASE_ID>
Redhatsudo service datadog-agent flare <CASE_ID>
SUSEsudo service datadog-agent flare <CASE_ID>
Sourcesudo ~/.datadog-agent/bin/agent flare <CASE_ID>
WindowsConsult the dedicated Windows documentation

Note: If you are using a Linux based system and the service wrapper command is not available, consult the list of alternatives.

Kuberneteskubectl exec <POD_NAME> -it datadog-cluster-agent flare <CASE_ID>

Further Reading