Logging is here!

Agent Troubleshooting

If you ended up at this page and have not yet installed the Datadog Agent, go to the dedicated Agent integration page for installation instructions. If you just installed the Agent, it might take a few moments before you start seeing metrics appear. The first place you should check for metrics is the Metrics Explorer.

If you think you might be experiencing issues, the first thing to do is run the info command and check the Agent logs.

If you’re still unsure about the issue, you may reach out to Datadog support team along with a flare of your Agent.

Get more logging from the Agent

To enable the full debug mode:

  1. Modify your local datadog.yaml file (see this page to locate this configuration file on your instance)

  2. Replace # log_level: INFO with log_level: DEBUG (make sure to get rid of # to uncomment the line)

  3. Restart your Datadog Agent (see that page to find the restart command depending on your OS)

  4. Wait a few minutes to generate some logs. Look here to find the location of the logs.

Obtaining debug logs from the container Agent

This process covers Agent v6 only, for Agent v5 refer to the dedicated documentation on how to collect more logs with the Datadog container Agent v5

Set the DD_LOG_LEVEL=debug environment variable when starting your Agent.

If your container is already running:

  1. To avoid that your process is restarted by S6, run:

    rm /var/run/s6/services/agent/finish

  2. Then stop the Agent:

    s6-svc -d /var/run/s6/services/agent/
    
  3. Restart then the Agent with debug log level by running:

    DD_LOG_LEVEL=debug agent start
    

Send a flare

If you are running the 5.3 version (or higher) of the Agent, you’re able to send all necessary troubleshooting information to our 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.
Since the Datadog Agent is completely open source, you can verify the code’s behavior. You can also review the archive prior to sending as the flare prompts a confirmation before uploading it.

In the commands below, replace <CASE_ID> with your Datadog support case ID, if you don’t specify a case ID, the command asks for an email address that is used to login in your organization and creates a new support case.

Platform Agent v5 Agent v6
Linux sudo /etc/init.d/datadog-agent flare <CASE_ID> sudo -u dd-agent -- datadog-agent flare <CASE_ID>
Docker docker exec -it dd-agent /etc/init.d/datadog-agent flare <CASE_ID> docker exec -it datadog-agent agent flare <CASE_ID>
Docker (Alpine) docker exec -it dd-agent /opt/datadog-agent/bin/agent flare <CASE_ID>
MacOS x datadog-agent flare <CASE_ID> datadog-agent flare <CASE_ID> or web web GUI
CentOS sudo service datadog-agent flare <CASE_ID> sudo datadog-agent flare <CASE_ID>
Debian sudo service datadog-agent flare <CASE_ID> sudo datadog-agent flare <CASE_ID>
Kubernetes kubectl exec <pod-name> -it /etc/init.d/datadog-agent flare <CASE_ID> kubectl exec <pod-name> -it agent flare <CASE_ID>
Fedora sudo service datadog-agent flare <CASE_ID> sudo datadog-agent flare <CASE_ID>
Redhat sudo service datadog-agent flare <CASE_ID> sudo datadog-agent flare <CASE_ID>
Suse sudo service datadog-agent flare <CASE_ID> sudo datadog-agent flare <CASE_ID>
Source sudo ~/.datadog-agent/bin/agent flare <CASE_ID> sudo datadog-agent flare <CASE_ID>
Windows Consult our dedicated windows doc Consult our dedicated windows doc

FAQ

Further Reading