이 가이드에서는 Agent 6 설치에 대해 다룹니다. Datadog에서는 최신 기능을 위해 Agent 7을 설치하거나 업그레이드할 것을 권장합니다. 최신 버전의 Agent 설치에 대한 자세한 내용은 최신 Agent 설치 지침을 따르세요. 이전 버전에서 Agent 7로 업그레이드하는 방법은 Datadog Agent v7로 업그레이드를 참조하세요.
Datadog Agent는 DD_SYSTEMDAEMON_INSTALL=true 및 DD_SYSTEMDAEMON_USER_GROUP=username:groupname를 지정하여 시스템 전체 LaunchDaemon으로 설치할 수 있습니다. MY_API_KEY를 Datadog API 키로 변경하세요.
/opt/datadog-agent/etc/datadog.yaml에 다음 줄을 추가하고 MY_API_KEY를 Datadog API 키로 바꿉니다.
api_key: MY_API_KEY
site: datad0g.com
Agent 관리하기
Agent를 관리하려면 다음을 사용하세요.
단일 사용자 설치의 경우 시스템 트레이에서 Datadog Agent 앱
시스템 전체 LaunchDaemon 설치의 경우 launchctl
datadog-agent명령. 바이너리는 /usr/local/bin에 있습니다.
/opt/datadog-agent/etc/conf.d.에서 통합을 활성화하거나 비활성화합니다.
Windows
릴리스 6.11.0부터 Windows Agent의 핵심 및 APM/트레이스 컴포넌트는 ddagentuser 계정에서 실행되며 LOCAL_SYSTEM 계정에서 실행되는 대신 설치 시 생성됩니다. Datadog Agent 버전 6.x에서 6.11 이상으로 업그레이드하는 경우 업그레이드하기 전에 Windows Agent 사용자 문서를 확인하세요.
업그레이드하지 않고 이전 구성을 사용하지 않으려면 예제 구성을 복사하고 Agent를 설치하세요. MY_API_KEY를 Datadog API 키로 바꿉니다.
sudo sh -c "sed 's/api_key:.*/api_key: MY_API_KEY/' /etc/datadog-agent/datadog.yaml.example > /etc/datadog-agent/datadog.yaml"
Datadog 지역을 설정합니다.
sudo sh -c "sed -i 's/# site:.*/site: datad0g.com/'
/etc/datadog-agent/datadog.yaml"
Agent 사용자의 권한이 올바른지 확인합니다.
sudo sh -c "chown dd-agent:dd-agent /etc/datadog-agent/datadog.yaml && chmod 640 /etc/datadog-agent/datadog.yaml"
Agent를 시작합니다.
sudo systemctl restart datadog-agent.service
원스텝 설치
원스텝 명령은 Datadog Agent용 APT 패키지를 설치하고 비밀번호를 묻는 메시지를 표시합니다. Agent가 시스템에 아직 설치되어 있지 않고 설치 후 자동으로 시작되지 않도록 하려면 Agent를 실행하기 전에 DD_INSTALL_ONLY=true를 명령 앞에 추가하세요.
If you’re not upgrading and do not want to use an old configuration, copy the example config into place and install the Agent. Replace MY_API_KEY with your Datadog API key:
sudo sh -c "sed 's/api_key:.*/api_key: MY_API_KEY/' /etc/datadog-agent/datadog.yaml.example > /etc/datadog-agent/datadog.yaml"
Configure the Datadog region:
sudo sh -c "sed -i 's/# site:.*/site: datad0g.com/' /etc/datadog-agent/datadog.yaml"
Ensure the Agent user’s permissions are correct::
sudo sh -c "chown dd-agent:dd-agent /etc/datadog-agent/datadog.yaml && chmod 640 /etc/datadog-agent/datadog.yaml"
Start the Agent:
Amazon Linux 2.0:
sudo systemctl restart datadog-agent.service
Amazon Linux 1.0:
sudo initctl start datadog-agent
One-step install
The one-step command installs the YUM packages for the Datadog Agent and prompts you for your password.
If the Agent is not already installed on your machine and you don’t want it to start automatically after the installation, prepend DD_INSTALL_ONLY=true to the command before running it.
If you have an existing Agent configuration file, existing values are retained during the update.
You can configure some of the Agent options during the initial install process. For more information, check the install_script configuration options.
Run the following command, replacing MY_API_KEY with your Datadog API key:
If you’re not upgrading and do not want to use an old configuration, copy the example config into place and install the Agent. Replace MY_API_KEY with your Datadog API key:
sudo sh -c "sudo sh -c "sed 's/api_key:.*/api_key: .*/api_key: MY_API_KEY/' /etc/datadog-agent/datadog.yaml.example > /etc/datadog-agent/datadog.yaml"
Configure the Datadog region:
sudo sh -c "sed -i 's/# site:.*/site: datad0g.com/' /etc/datadog-agent/datadog.yaml"
Ensure the Agent user’s permissions are correct::
sudo sh -c "chown dd-agent:dd-agent /etc/datadog-agent/datadog.yaml && chmod 640 /etc/datadog-agent/datadog.yaml"
Start the Agent:
Centos or Red Hat 7 and higher:
sudo systemctl restart datadog-agent.service
Centos or Red Hat 6:
sudo initctl start datadog-agent
One-step install
The one-step command installs the YUM packages for the Datadog Agent and prompts you for your password.
If the Agent is not already installed on your machine and you don’t want it to start automatically after the installation, prepend DD_INSTALL_ONLY=true to the command before running it.
If you have an existing Agent configuration file, existing values are retained during the update.
You can configure some of the Agent options during the initial install process. For more information, check the install_script configuration options.
Run the following command, replacing MY_API_KEY with your Datadog API key:
If you’re not upgrading and do not want to use an old configuration, copy the example config into place and install the Agent. Replace MY_API_KEY with your Datadog API key:
sudo sh -c "sudo sh -c "sed 's/api_key:.*/api_key: .*/api_key: MY_API_KEY/' /etc/datadog-agent/datadog.yaml.example > /etc/datadog-agent/datadog.yaml"
Configure the Datadog region:
sudo sh -c "sed -i 's/# site:.*/site: datad0g.com/' /etc/datadog-agent/datadog.yaml"
Ensure the Agent user’s permissions are correct::
sudo sh -c "chown dd-agent:dd-agent /etc/datadog-agent/datadog.yaml && chmod 640 /etc/datadog-agent/datadog.yaml"
Restart the Agent:
sudo systemctl restart datadog-agent.service
One-step install
The one-step command installs the YUM packages for the Datadog Agent and prompts you for your password.
If the Agent is not already installed on your machine and you don’t want it to start automatically after the installation, prepend DD_INSTALL_ONLY=true to the command before running it.
If you have an existing Agent configuration file, existing values are retained during the update.
You can configure some of the Agent options during the initial install process. For more information, check the install_script configuration options.
Run the following command, replacing MY_API_KEY with your Datadog API key:
If you’re not upgrading and do not want to use an old configuration, copy the example config into place and install the Agent. Replace MY_API_KEY with your Datadog API key:
sudo sh -c "sudo sh -c "sed 's/api_key:.*/api_key: .*/api_key: MY_API_KEY/' /etc/datadog-agent/datadog.yaml.example > /etc/datadog-agent/datadog.yaml"
Configure the Datadog region:
sudo sh -c "sed -i 's/# site:.*/site: datad0g.com/' /etc/datadog-agent/datadog.yaml"
Ensure the Agent user’s permissions are correct::
sudo sh -c "chown dd-agent:dd-agent /etc/datadog-agent/datadog.yaml && chmod 640 /etc/datadog-agent/datadog.yaml"
Restart the Agent:
sudo systemctl restart datadog-agent.service
One-step install
The one-step command installs the YUM packages for the Datadog Agent and prompts you for your password.
If the Agent is not already installed on your machine and you don’t want it to start automatically after the installation, prepend DD_INSTALL_ONLY=true to the command before running it.
If you have an existing Agent configuration file, existing values are retained during the update.
You can configure some of the Agent options during the initial install process. For more information, check the install_script configuration options.
Run the following command, replacing MY_API_KEY with your Datadog API key:
업그레이드하지 않고 이전 구성을 사용하지 않으려면 예제 구성을 복사하고 Agent를 설치하세요. MY_API_KEY를 Datadog API 키로 바꿉니다.
sudo sh -c "sudo sh -c "sed 's/api_key:.*/api_key: .*/api_key: MY_API_KEY/' /etc/datadog-agent/datadog.yaml.example > /etc/datadog-agent/datadog.yaml"
Datadog 지역을 구성합니다
sudo sh -c "sed -i 's/# site:.*/site: datad0g.com/' /etc/datadog-agent/datadog.yaml"
Agent 사용자의 권한이 올바른지 확인합니다.
sudo sh -c "chown dd-agent:dd-agent /etc/datadog-agent/datadog.yaml && chmod 640 /etc/datadog-agent/datadog.yaml"
Restart the Agent:
sudo systemctl restart datadog-agent.service
원스텝 설치
The one-step command installs the latest BFF package for the Datadog Agent and prompts you for your password if necessary. Agent가 시스템에 아직 설치되어 있지 않고 설치 후 자동으로 시작되지 않도록 하려면 Agent를 실행하기 전에 DD_INSTALL_ONLY=true를 명령 앞에 추가하세요.
Ensure that the Datadog Agent has the correct permissions:
sudo sh -c "chown dd-agent:dd-agent /etc/datadog-agent/datadog.yaml && chmod 660 /etc/datadog-agent/datadog.yaml"
Stop the Agent service:
sudo stopsrc -s datadog-agent
Verify the Agent service has stopped:
sudo lssrc -s datadog-agent
Restart the Agent service:
sudo startsrc -s datadog-agent
Cloud and containers
Run the Datadog Agent directly in your Kubernetes cluster to start collecting your cluster and applications metrics, traces, and logs. You can deploy the Agent with a Helm chart, the Datadog Operator or directly with a DaemonSet. For more information about installing the Datadog Agent on different distributions, see the Kubernetes distributions documentation.
Installing the Datadog Agent
To install the chart with a custom release name RELEASE_NAME:
This chart adds the Datadog Agent to all nodes in your cluster using a DaemonSet. Soon after installation, Datadog begins to report hosts and metrics data in your account.
Enabling log collection
To enable log collection with Helm, update your datadog-values.yaml file with the following log collection configuration:
The one-step installation command runs a signed Docker container which embeds the Datadog Agent to monitor your host. The Docker integration is enabled by default, as well as Autodiscovery in automatic configuration mode.
You must not run more than one Datadog Agent per node. Running multiple Agents may result in unexpected behavior.
For a one-step install, run the following command. Replace MY_API_KEY with your Datadog API key:
If the one-step installation command does not work, it’s possible that your system mounts the cgroup directory in an unexpected place or does not use CGroups for memory management. CGroups are required for the Docker check to succeed. To enable CGroups, see the Setup documentation.
If CGroups are enabled, but the check is failing because of an unexpected cgroup directory location:
Run mount | grep "cgroup type tmpfs" to retrieve the location of the cgroup directory.
Replace the first occurrence of /sys/fs/cgroup in the one-step installation command with the location of the cgroup directory.
Send custom metrics with DogStatsD
By default, DogStatsD only listens to localhost. To listen to DogStatsD packets from other containers:
Add -e DD_DOGSTATSD_NON_LOCAL_TRAFFIC=true to the container’s parameters.
Bind the container’s statsd port to the hosts’s IP by adding the -p 8125:8125/udp option to the container’s parameters.
Configure your client library to send UDP packets to the hosts’s IP.
Running CoreOS Container Linux is supported with the Docker runtime. For installation instructions, see Docker.
To run CoreOS Tectonic on Kubernetes, see Kubernetes.
Starting with version 6.1, the Datadog Agent supports monitoring OpenShift Origin and Enterprise clusters. Depending on your needs and the security constraints of your cluster, three deployment scenarios are supported:
The Datadog Agent BOSH release only works on Ubuntu and Red Hat stemcells.
Upload the Datadog Agent release to your BOSH Director:
# BOSH CLI v1bosh upload release https://cloudfoundry.datadoghq.com/datadog-agent/datadog-agent-boshrelease-latest.tgz
# BOSH CLI v2bosh upload-release https://cloudfoundry.datadoghq.com/datadog-agent/datadog-agent-boshrelease-latest.tgz
Configure Datadog as an addon in your runtime config. Replace MY_API_KEY with your Datadog API key::
# runtime.yml---releases:- name:datadog-agentversion:$UPLOADED_VERSION# e.g. 1.0.5140addons:- name:datadogjobs:- name:dd-agentrelease:datadog-agentproperties:dd:use_dogstatsd:yesdogstatsd_port:18125# Many Cloud Foundry deployments have their own StatsD listening on port 8125api_key:MY_API_KEYtags:["my-cloud-foundry-deployment"]# optional. Add any tags you wish# Optionally, enable any Agent Checks here# integrations:# directory:# init_config: {}# instances:# directory: "."
Install the Datadog Ansible collection from Ansible Galaxy on your Ansible server:
ansible-galaxy collection install datadog.dd
The Datadog Ansible collection is also available through the Red Hat Automation Hub where it is officially certified by Red Hat.
Installing the collection is recommended. If needed, you can also install Datadog using the standalone role.
To deploy the Datadog Agent on hosts, add the Datadog role and your API key to your playbook. Replace MY_API_KEY with your Datadog API key:
- hosts:serverstasks:- name:Import the Datadog Agent role from the Datadog collectionimport_role:name:datadog.dd.agentvars:datadog_api_key:"MY_API_KEY"datadog_agent_major_version:6datadog_site:"datad0g.com"
To ensure that the Agent can group your hosts together, only use node hostnames that the Datadog Agent is tracking. You can check what hostnames the Agent is tracking using the following command:
sudo datadog-agent status
Specific Agent checks
To use a specific Agent check or integration on one of your nodes, you can use the datadog_checks variable. Here is an example for the process check:
- hosts:serverstasks:- name:Import the Datadog Agent role from the Datadog collectionimport_role:name:datadog.dd.agentvars:datadog_api_key:"MY_API_KEY"datadog_agent_major_version:6datadog_site:"datad0g.com"datadog_checks:process:init_config:instances:- name:sshsearch_string:['ssh','sshd']- name:syslogsearch_string:['rsyslog']cpu_check_interval:0.2exact_match:trueignore_denied_access:true
You can find more examples of the Agent role usage on the GitHub repo for the standalone role.
Metrics and events
To get metrics and events on Datadog after Ansible runs, see the Ansible callback project’s GitHub page.
Starting with version 2.9.0, the datadog_agent module supports both Windows and Linux nodes. Previous versions of the datadog_agent module only support Linux nodes.
Requirements:
Requires Puppet Open Source version >= 4.6 or Puppet Enterprise version >= 2016.4
Install the Agent
Install the datadog_agent module from the Puppet Forge on your Puppet server:
For fresh installs, run the module install command:
puppet module install datadog-datadog_agent
If the module is already installed, upgrade it:
puppet module upgrade datadog-datadog_agent
To deploy the Datadog Agent on nodes, add this parametrized class to your manifests. Replace MY_API_KEY with your Datadog API key:
To ensure that the Agent can group your hosts together, only use node hostnames that the Datadog Agent is tracking. You can check what hostnames the Agent is tracking using the following command:
sudo datadog-agent status
Enable reporting to Datadog on your Puppet server:
Add the following parameters to /etc/puppet/puppet.conf:
Run Puppet on your Puppet server to install all necessary dependencies.
Restart your Puppet server to begin receiving Puppet data in Datadog.
Specific Agent checks
To use a specific Agent check or integration on one of your nodes, see the relevant integration manifest for a code sample. Here is an example for the elasticsearch integration:
If you are using Berkshelf, add the cookbook to your Berksfile:
cookbook 'datadog', '~> 4.0'
If you’re not using Berkshelf, install the cookbook in to your repository using Knife:
knife cookbook site install datadog
Set the Datadog-specific attributes in either a role, environment, or another recipe. Replace MY_API_KEY with your Datadog API key:
node.default['datadog']['api_key'] = "MY_API_KEY"
# Use an existing application key or create a new one for Chef
node.default['datadog']['application_key'] = "Generate Application Key"
# Enable install for Agent version 6
node.default['datadog']['agent_major_version'] = 6
# Set the Datadog site
node.default['datadog']['site'] = "datad0g.com"
The Datadog Saltstack formula only supports Debian-based and RedHat-based systems.
The following instructions add the Datadog formula to the base Salt environment. To add it to another Salt environment, replace references to base with the name of your Salt environment.
Install using gitfs_remotes
Install the Datadog formula in the base environment of your Salt Master node, using the gitfs_remotes option in your Salt Master configuration file (by default /etc/salt/master):
fileserver_backend:- roots# Active by default, necessary to be able to use the local salt files we define in the next steps- gitfs# Adds gitfs as a fileserver backend to be able to use gitfs_remotesgitfs_remotes:- https://github.com/DataDog/datadog-formula.git:- saltenv:- base:- ref:3.0# Pin here the version of the formula you want to use