> For the complete documentation index, see [llms.txt](https://docs.sola.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sola.security/integrations/data-sources/datadog.md).

# Datadog

Connect Sola and Datadog to get security insights

## Overview <a href="#overview" id="overview"></a>

The Datadog integration connects data from your Datadog account to your Sola workspace, making it easy to search and find answers to your specific use cases.

With the Datadog integration, you can:

* Gain visibility into monitored hosts and AWS integration resources connected to your Datadog environment.
* Track monitors and log-based metrics configured to alert when specific thresholds are crossed.
* Monitor user accounts, roles, and permissions to understand access across your Datadog organization.
* Review dashboards and service level objectives used to track key metrics over time.
* Track detection pipeline health, including disabled rules, narrowed security filters, broad suppressions, and notification routing gaps that could cause findings to go unnoticed.
* Audit API and application key hygiene, including unused keys and keys still held by terminated or disabled users.
* Review role assignments, SAML-to-role mappings, and organization-wide authentication settings, including SSO enforcement and IP allowlisting.
* Identify critical asset definitions and correlate entity and threat intelligence context during investigations.

{% hint style="warning" %}
**Your data can only be retrieved, never modified.**

Once connected, your data is securely stored, and access is restricted to retrieving configurations and metadata only. Authentication methods ensure secure delegation of permissions while maintaining data integrity.
{% endhint %}

## Set up Datadog data source integration with Sola <a href="#set-up-wiz-data-source-integration-with-sola" id="set-up-wiz-data-source-integration-with-sola"></a>

{% columns %}
{% column width="58.333333333333336%" %}
Go to ***Integrations*** > [***Data Sources***](https://app.sola.security/integrations/data-sources) > click ***New data source*** > select ***Datadog***.

*The Sola wizard will take you through the steps.*
{% endcolumn %}

{% column width="41.666666666666664%" %} <a href="https://app.sola.security/integrations/data-sources?integration=DATADOG" class="button primary">Set up Datadog -></a>
{% endcolumn %}
{% endcolumns %}

### Connect Datadog to Sola

To connect Datadog, you'll need a Datadog account with permissions to create API and Application keys, and your Datadog API domain (US or EU).

{% tabs %}
{% tab title="API Credentials" %}
This method uses a Datadog API key and Application key to securely grant Sola read-only access to your Datadog services and resources.
{% endtab %}
{% endtabs %}

***

## FAQs

### What is the difference between the Datadog integrations?

Sola offers two Datadog integrations:

* [Datadog](/integrations/data-sources/datadog.md): a data source covering infrastructure and observability data, hosts, monitors, user accounts, roles, and dashboards. Data is synced on a schedule and stored in tables in your Sola workspace.
* [Datadog Cloud SIEM](/integrations/data-sources/datadog-cloud-siem.md): a real-time data source covering Datadog's security-specific data, security signals, logs, audit events, Cloud Security posture findings, and incidents. Data is queried directly from Datadog in real time, reflecting current state, nothing is copied or stored in Sola.

Use Datadog for visibility into your Datadog monitoring and infrastructure setup. Use Datadog Cloud SIEM for Datadog's security product line and want real-time access to signals and incidents. You can connect both.


---

# 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.sola.security/integrations/data-sources/datadog.md?ask=<question>&goal=<user_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.