[ Datadog ] How to check the Agent's status and troubleshoot issues

Print

(blue star) Check Agent status

  • Check Agent status
    - Check whether the Agent is currently up or down. 

OS

Command

Linux

CentOs/Redhat

sudo systemctl status datadog-agent

sudo status datadog-agent

Ubuntu/Debian

sudo service datadog-agent status

Windows

Go to Task Manager > Services and check the status of services starting with "datadog". 

Kubernetes

kubectl exec -it <POD_NAME> -- s6-svstat /var/run/s6/services/agent/

(blue star) Check data collection status

  • Check data collection status
    - If the Agent is up but data is not being collected, check the collection status. 

OS

Command

Linux

sudo datadog-agent status

Windows

  • Run the following command in cmd:
    "%ProgramFiles%\Datadog\Datadog Agent\bin\agent.exe" status

  • check the Status Datadog Agent Manager > Status > General, Collector

Kubernetes

kubectl exec -it <POD_NAME> -- agent status

(blue star)Check Agent logs

  • Check Agent logs
    - If the Agent keeps shutting down after a restart, or if there are no abnormalities in the collection status, check for any ERROR entries in the logs. 

OS

PATH

Linux

/var/log/datadog/

Windows

C:\ProgramData\Datadog\logs

(blue star) Restart Agent

  • Restart Agent
    - When changing Agent settings or if an issue occurs, restart the Agent. 

OS

Command

Linux

CentOs/Redhat

sudo systemctl restart datadog-agent

sudo restart datadog-agent

Ubuntu/Debian

sudo service datadog-agent restart

Windows

  • Run the following command in cmd:
    "%ProgramFiles%\Datadog\Datadog Agent\bin\agent.exe" status

  • Datadog Agent Manager > Restart Agent

  • Right-click the Datadog icon in the Windows tray > Restart 

Kubernetes

kubectl delete pod <AGENT POD NAME>

(blue star) Send Flare

If it's difficult to identify the cause, please send a Flare. 

  • First, change the log_level in datadog.yaml from info to debug

플랫폼

PATH

AIX

/etc/datadog-agent/datadog.yaml

Linux

/etc/datadog-agent/datadog.yaml

macOS

~/.datadog-agent/datadog.yaml

Windows

%ProgramData%\Datadog\datadog.yaml

###########################
## Logging Configuration ##
###########################

## @param log_level - string - optional - default: info
## @env DD_LOG_LEVEL - string - optional - default: info
## Minimum log level of the Datadog Agent.
## Valid log levels are: trace, debug, info, warn, error, critical, and off.
## Note: When using the 'off' log level, quotes are mandatory.
#
log_level: 'debug'
  • Restart the Agent.

OS

Command

Linux

CentOs/Redhat

sudo systemctl restart datadog-agent

sudo restart datadog-agent

Ubuntu/Debian

sudo service datadog-agent restart

Windows

  • Run the following command in cmd:
    "%ProgramFiles%\Datadog\Datadog Agent\bin\agent.exe" status

  • Datadog Agent Manager > Restart Agent

  • Right-click the Datadog icon in the Windows tray > Restart

Kubernetes

kubectl delete pod <AGENT POD NAME>

  • Wait 5–10 minutes after restarting, then send the Flare: 

플랫폼

Command

Linux

sudo datadog-agent flare <CASE_ID>

Windows

  • Run the following command in cmd:
    "%ProgramFiles%\Datadog\Datadog Agent\bin\agent.exe" flare <CASE_ID>

  • Datadog Agent Manager > Flare > Enter Case ID and Email, then Submit 

Kubernetes

kubectl exec -it <POD_NAME> -- agent flare <CASE_ID>

- The Case ID entered in the Flare must be the ticket number from Datadog.
Before sending the Flare, register the issue on the Support Portal and obtain a ticket number.
- Enter the email as monitoring_admin@sk.com.

  • After the Flare is successfully sent, change the log_level back to info and restart the Agent.
    If Flare sending fails, attach the generated Flare file to the ticket on the Support Portal.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.