> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/integrations/integrations-overview/datadog-agent.md). # Datadog Agent Datadog monitors applications and servers, by collecting metrics, logs, and other events in a central service. To collect metrics, Datadog uses an open-source data collection agent built in Go. Usually, a Datadog user would install the collection agent on their servers or other cloud infrastructure. You can install the Datadog agent in your Release account by following this guide. ## Create a Datadog account On the Datadog website, click the **Free Trial** button to sign up for a new Datadog account. ![Select your Datadog region](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-9242e1b1fc051389d8f9e28c1f24c635947a5a56%2Fdatadog-select-region.png?alt=media\&token=2d2f5de7-89e7-4785-ac3f-491ffbe7b8ae) While creating your Datadog account, make sure to select the `EU1` region only if your Release cluster's region name starts with `eu`, for example, `eu-west-1`. Select the Datadog `US1-FED` region if you're using AWS GovCloud for your cluster. Note: Release automatically configures the agent to use EU or GOV, based on your cluster location. If you need to update the agent to use a specific site, please contact support. ## Copy your Datadog API key ![Datadog API key](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-a0ecc8f0327587ca9cc323f71dbc6f092057a6b4%2Fdatadog-api-key.png?alt=media\&token=7140a365-c731-4de0-adb5-ece72f97749e) Your Datadog API key is a 32 character random string. During the Datadog setup process, copy your API key from one of the integration options. You can always find your Datadog API key in Datadog's settings, under your [organization settings](https://docs.datadoghq.com/account_management/api-app-keys/) in Datadog. Copy the API key to your clipboard. ## Set up the Datadog integration in Release In Release, navigate to **Configuration**, then to **Integrations**. Click on **Datadog** in the list of available integrations to open the Datadog agent setup dialog.. ![](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-c5c158708b7d794092e44af3a2fb4e09381c6b7b%2Favailable-integrations.png?alt=media) ![Paste the Datadog API key and save](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-a9e1217a11dd28a0ea65a694bd46fa43a40cb4a5%2Fconfigure-datadog.png?alt=media) Paste the API key you copied earlier, then click **Save Integration**. Release will now install the Datadog agent in all active clusters in your Release account. ## Enable or disable the Datadog agent in your clusters If you would like to manually disable the Datadog agent in any of your Release clusters, navigate to **clusters** in your account settings, and open your cluster's settings. In the right sidebar, click **enable Datadog agent** or **disable Datadog agent**. ![Enable Datadog](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-3ea48bac90acc2f7de5a8ee756ad9ff2db1c34ac%2Fenable-datadog.png?alt=media) Visit your Datadog dashboard to see whether the change has applied. You should notice your cluster tracking metrics if you enabled the agent, or no longer tracking metrics if you disabled the agent. {% hint style="info" %} The button to disable or enable Datadog for a cluster will only show up after \[setting up the Datadog integration as shown above]\(#set-up-the-datadog-integration-in-releasehub). {% endhint %} ## Next steps Once the Datadog agent is live, read our guide on [Monitoring your Release clusters using Datadog](/guides-and-examples/advanced-guides/monitoring-your-release-clusters.md) ## Troubleshooting and common misconfigurations If you do not see any metrics in Datadog after installing the agent in Release, rule out the following common issues. ### Incorrect Datadog API key Datadog has multiple different keys and passwords, but the one to use for agents is the organization-wide API key. Make sure the key entered in Release matches your Datadog organization API key exactly. ### No nodes in your clusters If you're installing Datadog on a cluster with no enabled nodes, the status will update to show that it is installed, but there will be no resources to run the agent. Make sure your Release cluster has at least one node available. ### Region mismatch Make sure to use the `EU1` Datadog region only if you're using an AWS or GCP region that starts with `eu`. ### Logged into a different Datadog or Release account Just as with AWS, some organizations use multiple Datadog accounts across their different projects. Make sure you copied the API key from the correct account, and that you were logged into the correct Release account when you set up your integration. ### Viewing the agent logs in Kubernetes If you're not seeing any logs or metrics in Datadog, you can view the logs for your Datadog agent in Release. Use the Release command line interface on your local machine to tail the agent containers' logs. You'll need to install and set up the Release CLI, then run the following command to view the most recent log entries. Replace the account ID and cluster name. ```bash release clusters exec --account 2222 --cluster release-222222 -- kubectl logs --namespace kube-system --selector app=datadog-agent-customer ``` If you need help resolving any errors between the agent installed Release and Datadog, contact your technical account manager at Release. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.release.com/integrations/integrations-overview/datadog-agent.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.