- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
이 가이드에서는 Agent 6 설치에 대해 다룹니다. Datadog에서는 최신 기능을 위해 Agent 7을 설치하거나 업그레이드할 것을 권장합니다. 최신 버전의 Agent 설치에 대한 자세한 내용은 최신 Agent 설치 지침을 따르세요. 이전 버전에서 Agent 7로 업그레이드하는 방법은 Datadog Agent v7로 업그레이드를 참조하세요.
다음 명령을 실행하여 MY_API_KEY
를 Datadog API 키로 바꿉니다.
DD_AGENT_MAJOR_VERSION=6 DD_API_KEY=MY_API_KEY DD_SITE="${site}" bash -c "$(curl -L https://install.datadoghq.com/scripts/install_mac_os.sh)"
Agent는 로그인 시 실행됩니다. 시스템 트레이에서 비활성화할 수 있습니다.
Datadog Agent는 DD_SYSTEMDAEMON_INSTALL=true
및 DD_SYSTEMDAEMON_USER_GROUP=username:groupname
를 지정하여 시스템 전체 LaunchDaemon으로 설치할 수 있습니다. MY_API_KEY
를 Datadog API 키로 변경하세요.
DD_SYSTEMDAEMON_INSTALL=true DD_SYSTEMDAEMON_USER_GROUP=username:groupname DD_AGENT_MAJOR_VERSION=6 DD_API_KEY=MY_API_KEY DD_SITE="datad0g.com" bash -c "$(curl -L https://install.datadoghq.com/scripts/install_mac_os.sh)"
Agent는 시스템 시작 시 실행됩니다. 루트가 아닌 유효한 사용자 및 해당 그룹은 DD_SYSTEMDAEMON_USER_GROUP
변수를 사용하여 제공되어야 합니다. 에이전트 프로세스는 이 사용자 및 그룹에서 실행됩니다.
시스템 전체 LaunchDaemon 설치에서는 시스템 트레이 앱이 지원되지 않습니다.
/opt/datadog-agent/etc/datadog.yaml
에 다음 줄을 추가하고 MY_API_KEY
를 Datadog API 키로 바꿉니다.api_key: MY_API_KEY
site: datad0g.com
Agent를 관리하려면 다음을 사용하세요.
launchctl
datadog-agent
명령. 바이너리는 /usr/local/bin
에 있습니다./opt/datadog-agent/etc/conf.d.
에서 통합을 활성화하거나 비활성화합니다.
릴리스 6.11.0부터 Windows Agent의 핵심 및 APM/트레이스 컴포넌트는 ddagentuser
계정에서 실행되며 LOCAL_SYSTEM
계정에서 실행되는 대신 설치 시 생성됩니다. Datadog Agent 버전 6.x에서 6.11 이상으로 업그레이드하는 경우 업그레이드하기 전에 Windows Agent 사용자 문서를 확인하세요.
사용 가능한 모든 버전의 Windows 설치 프로그램 링크는 JSON 형식으로 제공됩니다.
datadog-agent-6-latest.amd64.msi
를 열어 설치 프로그램을 Administrator로 실행합니다.
.MY_API_KEY
를 Datadog API 키로 바꿉니다.start /wait msiexec /qn /i datadog-agent-6-latest.amd64.msi APIKEY="MY_API_KEY" SITE="datad0g.com"
Start-Process -Wait msiexec -ArgumentList '/qn /i datadog-agent-6-latest.amd64.msi APIKEY="MY_API_KEY" SITE="datad0g.com"'
HOSTNAME
및 TAGS
는 선택적 값입니다. 사용 가능한 모든 옵션은 Windows Agent 설명서를 참조하세요.
Azure에 Agent를 설치하려면 Microsoft Azure 설명서를 따르세요.
원스텝 명령은 Datadog Agent용 APT 패키지를 설치하고 비밀번호를 묻는 메시지를 표시합니다.
DD_INSTALL_ONLY=true
를 명령 앞에 추가하세요.Agent를 설치하려면 다음 명령을 실행하고 MY_API_KEY
를 Datadog API 키로 바꾸세요.
DD_API_KEY=MY_API_KEY DD_SITE="datad0g.com" bash -c "$(curl -L https://s3.amazonaws.com/dd-agent/scripts/install_script_agent6.sh)"
HTTPS를 통해 다운로드하고 curl
과 gnupg
를 설치할 수 있도록 APT를 설정합니다.
sudo apt-get update
sudo apt-get install apt-transport-https curl gnupg
시스템에 Datadog Debian 리포지토리를 설정하고 Datadog 아카이브 키링을 만듭니다.
sudo sh -c "echo 'deb [signed-by=/usr/share/keyrings/datadog-archive-keyring.gpg] https://apt.datadoghq.com/ stable 6' > /etc/apt/sources.list.d/datadog.list"
sudo touch /usr/share/keyrings/datadog-archive-keyring.gpg
sudo chmod a+r /usr/share/keyrings/datadog-archive-keyring.gpg
curl https://keys.datadoghq.com/DATADOG_APT_KEY_CURRENT.public | sudo gpg --no-default-keyring --keyring /usr/share/keyrings/datadog-archive-keyring.gpg --import --batch
curl https://keys.datadoghq.com/DATADOG_APT_KEY_06462314.public | sudo gpg --no-default-keyring --keyring /usr/share/keyrings/datadog-archive-keyring.gpg --import --batch
curl https://keys.datadoghq.com/DATADOG_APT_KEY_C0962C7D.public | sudo gpg --no-default-keyring --keyring /usr/share/keyrings/datadog-archive-keyring.gpg --import --batch
curl https://keys.datadoghq.com/DATADOG_APT_KEY_F14F620E.public | sudo gpg --no-default-keyring --keyring /usr/share/keyrings/datadog-archive-keyring.gpg --import --batch
curl https://keys.datadoghq.com/DATADOG_APT_KEY_382E94DE.public | sudo gpg --no-default-keyring --keyring /usr/share/keyrings/datadog-archive-keyring.gpg --import --batch
Debian 8 이하를 실행하는 경우 키링을 /etc/apt/trusted.gpg.d
에 복사하세요.
sudo cp -a /usr/share/keyrings/datadog-archive-keyring.gpg /etc/apt/trusted.gpg.d/
로컬 APT 리포지토리를 업데이트하고 Agent를 설치합니다.
sudo apt-get update
sudo apt-get install datadog-agent datadog-signing-keys
(선택 사항) Agent 5.17 이상에서 업그레이드하는 경우 기존 Agent 5 구성을 가져옵니다.
sudo -u dd-agent -- datadog-agent import /etc/dd-agent /etc/datadog-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
를 명령 앞에 추가하세요.
MY_API_KEY
를 Datadog API 키로 바꿔서 다음 명령을 실행합니다.
DD_API_KEY=MY_API_KEY bash -c "$(curl -L https://raw.githubusercontent.com/DataDog/dd-agent/master/packaging/datadog-agent/source/install_agent.sh)"
HTTPS를 통해 다운로드하고 curl
과 gnupg
를 설치할 수 있도록 APT를 설정합니다.
sudo apt-get update
sudo apt-get install apt-transport-https curl gnupg
시스템에 Datadog Debian 리포지토리를 설정하고 Datadog 아카이브 키링을 만듭니다.
sudo sh -c "echo 'deb [signed-by=/usr/share/keyrings/datadog-archive-keyring.gpg] https://apt.datadoghq.com/ stable 6' > /etc/apt/sources.list.d/datadog.list"
sudo touch /usr/share/keyrings/datadog-archive-keyring.gpg
sudo chmod a+r /usr/share/keyrings/datadog-archive-keyring.gpg
curl https://keys.datadoghq.com/DATADOG_APT_KEY_CURRENT.public | sudo gpg --no-default-keyring --keyring /usr/share/keyrings/datadog-archive-keyring.gpg --import --batch
curl https://keys.datadoghq.com/DATADOG_APT_KEY_06462314.public | sudo gpg --no-default-keyring --keyring /usr/share/keyrings/datadog-archive-keyring.gpg --import --batch
curl https://keys.datadoghq.com/DATADOG_APT_KEY_C0962C7D.public | sudo gpg --no-default-keyring --keyring /usr/share/keyrings/datadog-archive-keyring.gpg --import --batch
curl https://keys.datadoghq.com/DATADOG_APT_KEY_F14F620E.public | sudo gpg --no-default-keyring --keyring /usr/share/keyrings/datadog-archive-keyring.gpg --import --batch
curl https://keys.datadoghq.com/DATADOG_APT_KEY_382E94DE.public | sudo gpg --no-default-keyring --keyring /usr/share/keyrings/datadog-archive-keyring.gpg --import --batch
Ubuntu 14 이하를 실행하는 경우 키링을 /etc/apt/trusted.gpg.d
에 복사하세요.
sudo cp -a /usr/share/keyrings/datadog-archive-keyring.gpg /etc/apt/trusted.gpg.d/
로컬 APT 리포지토리를 업데이트하고 Agent를 설치합니다.
sudo apt-get update
sudo apt-get install datadog-agent datadog-signing-keys
(선택 사항) Agent 5.17 이상에서 업그레이드하는 경우 기존 Agent 5 구성을 가져옵니다.
sudo -u dd-agent -- datadog-agent import /etc/dd-agent /etc/datadog-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
sudo initctl start datadog-agent
원스텝 명령은 Datadog Agent용 YUM 패키지를 설치하고 비밀번호를 묻는 메시지를 표시합니다.
DD_INSTALL_ONLY=true
를 명령 앞에 추가하세요.MY_API_KEY
를 Datadog API 키로 바꿔서 다음 명령을 실행합니다.
DD_API_KEY=MY_API_KEY DD_SITE="datad0g.com" bash -c "$(curl -L https://s3.amazonaws.com/dd-agent/scripts/install_script_agent6.sh)"
For Amazon Linux 2022 installations on Agent version <= 6.39. The Agent requires the libxcrypt-compat
package:
dnf install -y libxcrypt-compat
On an x86_64 host, set up the Datadog YUM repo by creating /etc/yum.repos.d/datadog.repo
with the following configuration:
[datadog]
name=Datadog, Inc.
baseurl=https://yum.datadoghq.com/stable/6/x86_64/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://keys.datadoghq.com/DATADOG_RPM_KEY_CURRENT.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_4F09D16B.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_B01082D3.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_FD4BF915.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_E09422B3.public
On an arm64 host, set up the Datadog YUM repo by creating /etc/yum.repos.d/datadog.repo
with the following configuration:
[datadog]
name=Datadog, Inc.
baseurl=https://yum.datadoghq.com/stable/6/aarch64/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://keys.datadoghq.com/DATADOG_RPM_KEY_CURRENT.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_4F09D16B.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_B01082D3.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_FD4BF915.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_E09422B3.public
If upgrading from Agent 5 or 6, delete the obsolete RPM GPG key:
sudo sh -c 'if rpm -q gpg-pubkey-4172a230-55dd14f6 >/dev/null; then rpm --erase gpg-pubkey-4172a230-55dd14f6; fi'
Update your local yum repo and install the Agent:
sudo yum makecache
sudo yum install datadog-agent
Optionally, if upgrading from Agent 5.17 or higher, import your existing Agent 5 configuration:
sudo -u dd-agent -- datadog-agent import /etc/dd-agent /etc/datadog-agent
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:
sudo systemctl restart datadog-agent.service
sudo initctl start datadog-agent
The one-step command installs the YUM packages for the Datadog Agent and prompts you for your password.
DD_INSTALL_ONLY=true
to the command before running it.Run the following command, replacing MY_API_KEY
with your Datadog API key:
DD_UPGRADE=true DD_SITE="datad0g.com" bash -c "$(curl -L https://s3.amazonaws.com/dd-agent/scripts/install_script_agent6.sh)"
Set up the Datadog YUM repo by creating /etc/yum.repos.d/datadog.repo
with the following configuration:
[datadog]
name=Datadog, Inc.
baseurl=https://yum.datadoghq.com/rpm/x86_64/
enabled=1
gpgcheck=0
repo_gpgcheck=1
gpgkey=https://keys.datadoghq.com/DATADOG_RPM_KEY_CURRENT.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_4F09D16B.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_B01082D3.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_FD4BF915.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_E09422B3.public
Note: The repo_gpgcheck=0
option is a workaround for a bug in DNF.
If you’re upgrading from Agent 5 or a previous version of Agent 6, delete the obsolete RPM GPG key:
sudo sh -c 'if rpm -q gpg-pubkey-4172a230-55dd14f6 >/dev/null; then rpm --erase gpg-pubkey-4172a230-55dd14f6; fi'
Update your local yum repo and install the Agent:
sudo yum makecache
sudo yum remove datadog-agent-base
sudo yum install datadog-agent
Optionally, if upgrading from Agent 5.17 or higher, import your existing Agent 5 configuration:
sudo -u dd-agent -- datadog-agent import /etc/dd-agent /etc/datadog-agent
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:
sudo systemctl restart datadog-agent.service
sudo initctl start datadog-agent
The one-step command installs the YUM packages for the Datadog Agent and prompts you for your password.
DD_INSTALL_ONLY=true
to the command before running it.Run the following command, replacing MY_API_KEY
with your Datadog API key:
DD_UPGRADE=true DD_SITE="datad0g.com" bash -c "$(curl -L https://s3.amazonaws.com/dd-agent/scripts/install_script_agent6.sh)"
Set up the Datadog YUM repo by creating /etc/yum.repos.d/datadog.repo
with the following configuration:
[datadog]
name=Datadog, Inc.
baseurl=https://yum.datadoghq.com/rpm/x86_64/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://keys.datadoghq.com/DATADOG_RPM_KEY_CURRENT.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_4F09D16B.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_B01082D3.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_FD4BF915.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_E09422B3.public
If you’re upgrading from Agent 5 or a previous version of Agent 6, delete the obsolete RPM GPG key:
sudo sh -c 'if rpm -q gpg-pubkey-4172a230-55dd14f6 >/dev/null; then rpm --erase gpg-pubkey-4172a230-55dd14f6; fi'
Update your local yum repo and install the Agent:
sudo yum makecache
sudo yum remove datadog-agent-base
sudo yum install datadog-agent
Optionally, if upgrading from Agent 5.17 or higher, import your existing Agent 5 configuration:
sudo -u dd-agent -- datadog-agent import /etc/dd-agent /etc/datadog-agent
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
The one-step command installs the YUM packages for the Datadog Agent and prompts you for your password.
DD_INSTALL_ONLY=true
to the command before running it.Run the following command, replacing MY_API_KEY
with your Datadog API key:
DD_API_KEY=MY_API_KEY bash -c "$(curl -L https://raw.githubusercontent.com/DataDog/dd-agent/master/packaging/datadog-agent/source/install_agent.sh)"
Set up the Datadog YUM repo by creating /etc/yum.repos.d/datadog.repo
with the following configuration:
[datadog]
name=Datadog, Inc.
baseurl=https://yum.datadoghq.com/rpm/x86_64/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://keys.datadoghq.com/DATADOG_RPM_KEY_CURRENT.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_4F09D16B.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_B01082D3.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_FD4BF915.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_E09422B3.public
If you’re upgrading from Agent 5 or a previous version of Agent 6, delete the obsolete RPM GPG key:
sudo sh -c 'if rpm -q gpg-pubkey-4172a230-55dd14f6 >/dev/null; then rpm --erase gpg-pubkey-4172a230-55dd14f6; fi'
Update your local yum repo and install the Agent:
sudo yum makecache
sudo yum install datadog-agent
Optionally, if upgrading from Agent 5.17 or higher, import your existing Agent 5 configuration:
sudo -u dd-agent -- datadog-agent import /etc/dd-agent /etc/datadog-agent
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
The one-step command installs the YUM packages for the Datadog Agent and prompts you for your password.
DD_INSTALL_ONLY=true
to the command before running it.Run the following command, replacing MY_API_KEY
with your Datadog API key:
DD_API_KEY=MY_API_KEY DD_SITE="datad0g.com" bash -c "$(curl -L https://s3.amazonaws.com/dd-agent/scripts/install_script_agent6.sh)"
Set up the Datadog YUM repo by creating /etc/zypp/repos.d/datadog.repo
with the following configuration:
[datadog]
name=Datadog, Inc.
baseurl=hhttps://yum.datadoghq.com/suse/stable/6/x86_64
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://keys.datadoghq.com/DATADOG_RPM_KEY_CURRENT.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_4F09D16B.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_B01082D3.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_FD4BF915.public
https://keys.datadoghq.com/DATADOG_RPM_KEY_E09422B3.public
If you’re upgrading from Agent 5 or a previous version of Agent 6, delete the obsolete RPM GPG key:
sudo sh -c 'if rpm -q gpg-pubkey-4172a230-55dd14f6 >/dev/null; then rpm --erase gpg-pubkey-4172a230-55dd14f6; fi'
Update your local zypper repo and install the Agent:
sudo zypper refresh
sudo rpm --import https://keys.datadoghq.com/DATADOG_RPM_KEY_CURRENT.public
sudo rpm --import https://keys.datadoghq.com/DATADOG_RPM_KEY_4F09D16B.public
sudo rpm --import https://keys.datadoghq.com/DATADOG_RPM_KEY_B01082D3.public
sudo rpm --import https://keys.datadoghq.com/DATADOG_RPM_KEY_FD4BF915.public
sudo rpm --import https://keys.datadoghq.com/DATADOG_RPM_KEY_E09422B3.public
sudo zypper install datadog-agent
(선택 사항) Agent 5.17 이상에서 업그레이드하는 경우 기존 Agent 5 구성을 가져옵니다.
sudo -u dd-agent -- datadog-agent import /etc/dd-agent /etc/datadog-agent
업그레이드하지 않고 이전 구성을 사용하지 않으려면 예제 구성을 복사하고 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
를 명령 앞에 추가하세요.
MY_API_KEY
를 Datadog API 키로 바꿔서 다음 명령을 실행합니다.
DD_API_KEY=MY_API_KEY DD_SITE="datad0g.com" ksh -c "$(curl -L https://raw.githubusercontent.com/DataDog/datadog-unix-agent/master/scripts/install_script.sh)"
To install the Agent while keeping your existing configuration, run the following command:
DD_UPGRADE=true DD_SITE="datad0g.com" ksh -c "$(curl -L https://raw.githubusercontent.com/DataDog/datadog-unix-agent/master/scripts/install_script.sh)"
For a full list of the available installation script environment variables, see Basic Agent Usage for AIX.
Download the preferred BFF from the datadog-unix-agent repo releases.
Install the artifact as root with installp
:
installp -aXYgd datadog-unix-agent-latest.powerpc.aix..bff datadog-unix-agent
If you don’t have an existing configuration file, copy the example config into place. 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"
Datadog 지역을 구성합니다
sudo sh -c "sed \'s/# site:.*/site: datad0g.com/\' /etc/datadog-agent/datadog.yaml > /etc/datadog-agent/datadog.yaml.new && mv /etc/datadog-agent/datadog.yaml.new /etc/datadog-agent/datadog.yaml"
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
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.
To install the chart with a custom release name RELEASE_NAME
:
Add the Datadog Helm repository:
helm repo add datadog https://helm.datadoghq.com
Fetch the latest version of newly added charts:
helm repo update
Create an empty values.yaml
file, and override any of the default values if desired. See the Datadog helm-charts
repo for examples.
Deploy the Datadog Agent, replacing MY_API_KEY
with your Datadog API key:
With Helm v3+:
helm install RELEASE_NAME -f datadog-values.yaml --set datadog.site='datad0g.com' --set agents.image.tag='6' --set datadog.apiKey=MY_API_KEY datadog/datadog
With Helm v1 or v2:
helm install -f datadog-values.yaml --name RELEASE_NAME --set datadog.site='datad0g.com' --set agents.image.tag='6' --set datadog.apiKey=MY_API_KEY datadog/datadog
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.
To enable log collection with Helm, update your datadog-values.yaml
file with the following log collection configuration:
datadog:
logs:
enabled: true
containerCollectAll: true
Then upgrade your Datadog Helm chart:
helm upgrade -f datadog-values.yaml RELEASE_NAME datadog/datadog
Follow the dedicated APM setup documentation to learn how to collect your application traces in a Kubernetes environment.
For information on available Agent features, see the Kubernetes documentation.
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.
For a one-step install, run the following command. Replace MY_API_KEY
with your Datadog API key:
On Amazon Linux v2:
docker run -d --name dd-agent -v /var/run/docker.sock:/var/run/docker.sock:ro -v /proc/:/host/proc/:ro -v /cgroup/:/host/sys/fs/cgroup:ro -e DD_API_KEY=MY_API_KEY -e DD_SITE="datad0g.com" gcr.io/datadoghq/agent:6
On other operating systems:
docker run -d --name dd-agent -v /var/run/docker.sock:/var/run/docker.sock:ro -v /proc/:/host/proc/:ro -v /sys/fs/cgroup/:/host/sys/fs/cgroup:ro -e DD_API_KEY=MY_API_KEY -e DD_SITE="datad0g.com" gcr.io/datadoghq/agent:6
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:
mount | grep "cgroup type tmpfs"
to retrieve the location of the cgroup
directory./sys/fs/cgroup
in the one-step installation command with the location of the cgroup
directory.By default, DogStatsD only listens to localhost. To listen to DogStatsD packets from other containers:
-e DD_DOGSTATSD_NON_LOCAL_TRAFFIC=true
to the container’s parameters.-p 8125:8125/udp
option to the container’s parameters.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:
To install OpenShift, see the Kubernetes installation instructions. The Kubernetes integration targets OpenShift 3.7.0+ by default. For older versions of OpenShift, you must complete additional installation steps. For more information, see the OpenShift integration documentation.
Upload the Datadog Agent release to your BOSH Director:
# BOSH CLI v1
bosh upload release https://cloudfoundry.datadoghq.com/datadog-agent/datadog-agent-boshrelease-latest.tgz
# BOSH CLI v2
bosh 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-agent
version: $UPLOADED_VERSION # e.g. 1.0.5140
addons:
- name: datadog
jobs:
- name: dd-agent
release: datadog-agent
properties:
dd:
use_dogstatsd: yes
dogstatsd_port: 18125 # Many Cloud Foundry deployments have their own StatsD listening on port 8125
api_key: MY_API_KEY
tags: ["my-cloud-foundry-deployment"] # optional. Add any tags you wish
# Optionally, enable any Agent Checks here
# integrations:
# directory:
# init_config: {}
# instances:
# directory: "."
Add the runtime to your runtime config:
# BOSH cli v1
bosh update runtime-config runtime.yml
# BOSH cli v2
bosh update-runtime-config runtime.yml
Redeploy any existing deployments:
# BOSH cli v1
bosh deployment myDeployment.yml
bosh -n deploy
# BOSH cli v2
bosh -n -d myDeployment deploy myDeployment.yml
Installing the Agent with Ansible requires Ansible version 2.10 or higher.
Before you can use the Datadog Ansible Collection to manage Windows hosts, you must install the ansible.windows
collection:
ansible-galaxy collection install ansible.windows
Before you can use the Datadog Ansible Collection to manage openSUSE/SLES hosts, you must install the community.general
collection:
ansible-galaxy collection install community.general
Install the Datadog Ansible collection from Ansible Galaxy on your Ansible server:
ansible-galaxy collection install datadog.dd
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: servers
tasks:
- name: Import the Datadog Agent role from the Datadog collection
import_role:
name: datadog.dd.agent
vars:
datadog_api_key: "MY_API_KEY"
datadog_agent_major_version: 6
datadog_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
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: servers
tasks:
- name: Import the Datadog Agent role from the Datadog collection
import_role:
name: datadog.dd.agent
vars:
datadog_api_key: "MY_API_KEY"
datadog_agent_major_version: 6
datadog_site: "datad0g.com"
datadog_checks:
process:
init_config:
instances:
- name: ssh
search_string: ['ssh', 'sshd']
- name: syslog
search_string: ['rsyslog']
cpu_check_interval: 0.2
exact_match: true
ignore_denied_access: true
You can find more examples of the Agent role usage on the GitHub repo for the standalone role.
To get metrics and events on Datadog after Ansible runs, see the Ansible callback project’s GitHub page.
datadog_agent
module supports both Windows and Linux nodes. Previous versions of the datadog_agent module only support Linux nodes.Install the datadog_agent
module from the Puppet Forge on your Puppet server:
module install command
:puppet module install datadog-datadog_agent
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:
node "db1.mydomain.com" {
class { "datadog_agent":
api_key => "MY_API_KEY",
datadog_site => "datad0g.com",
agent_major_version => 6,
}
}
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
:
[master]
report = true
reports = datadog_reports
pluginsync = true
[agent]
report = true
pluginsync = true
In your manifest, add the puppet_run_reports
option to your Puppet server. For example:
node "puppet" {
class { "datadog_agent":
api_key => "MY_API_KEY",
datadog_site => "datad0g.com",
agent_major_version => 6,
puppet_run_reports => true,
}
}
Run Puppet on your Puppet server to install all necessary dependencies.
Restart your Puppet server to begin receiving Puppet data in Datadog.
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:
node "elastic-node1.mydomain.com" {
class { "datadog_agent":
api_key => "MY_API_KEY",
datadog_site => "datad0g.com",
agent_major_version => 6,
}
include "datadog_agent::integrations::elasticsearch"
}
Refer to the GitHub repository of the module for more examples and advanced use cases.
Add the Datadog cookbook:
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"
Upload the updated cookbook to your Chef server:
berks upload
# or
knife cookbook upload datadog
knife cookbook list | grep datadog &&
echo -e "e[0;32mdatadog cookbook - OKe[0m" ||
echo -e "e[0;31mmissing datadog cookbook - OKe[0m"
Add the cookbook to your node’s run_list
or role
:
"run_list": [
"recipe[datadog::dd-agent]"
]
Wait for the next scheduled chef-client
run.
For more information and examples, see the Agent GitHub repository.
base
Salt environment. To add it to another Salt environment, replace references to base
with the name of your Salt environment.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_remotes
gitfs_remotes:
- https://github.com/DataDog/datadog-formula.git:
- saltenv:
- base:
- ref: 3.0 # Pin here the version of the formula you want to use
Restart your Salt Master service:
systemctl restart salt-master
or
service salt-master restart
mkdir -p /srv/formulas && cd /srv/formulas
git clone https://github.com/DataDog/datadog-formula.git
file_roots
of your Salt Master configuration file (by default /etc/salt/master
):file_roots:
base:
- /srv/salt/
- /srv/formulas/datadog-formula/
Add the Datadog formula to your top file (by default /srv/salt/top.sls
):
base:
'*':
- datadog
Add a datadog.sls
pillar file to your pillar directory (by default /srv/pillar/
) and add your API key. Replace MY_API_KEY
with your Datadog API key:
datadog:
config:
api_key: MY_API_KEY
install_settings:
agent_version: <AGENT6_VERSION>
Add the datadog.sls
pillar file to the top pillar file (by default /srv/pillar/top.sls
):
base:
'*':
- datadog
To use a specific Agent check or integration on one of your hosts, you can use the checks variable. Here is an example for the directory integration:
datadog:
config:
api_key: MY_API_KEY
install_settings:
agent_version: <AGENT6_VERSION>
checks:
directory:
config:
instances:
- directory: "/srv/pillar"
name: "pillars"
Refer to the formula GitHub repository for logs configuration, check examples, and advanced use cases.
Follow the instructions in the Agent GitHub repository to build the Agent 6 .deb
and .rpm
packages on Linux with Docker.
Alternatively, you can build the Agent binary for version 6 following the Getting Started instructions.
추가 유용한 문서, 링크 및 기사: