See how your logging is configured
| Capability | What your team gains |
|---|---|
| Log monitors and notification routing | Review whether log monitors are configured to notify someone and whether active downtime mutes them. |
| Log archives | See archive destination types and Datadog's reported upload status to help identify archiving problems. |
| Datadog Agents | Review whether the Agents listed by Datadog Fleet report log collection as enabled on their hosts. |
Put it to work
Start with the logging question your team needs to answer: are log monitors configured to alert, are archives working, and are Agents configured to collect logs? Bring the collected evidence into your Boundera review and use it to guide the next investigation or implementation task.
The connection also identifies missing permissions and unavailable collections, helping your team see where evidence is missing. Keep your Datadog setup in place while Boundera brings its configuration evidence into the wider security workflow.
Connect the scope your team needs
Choose the Datadog site that hosts your organization and connect an API key with a scoped application key. Grant read access for monitors, log archives and hosts according to the evidence you want to collect. Data availability depends on your site's features and permissions.
The connection is read-only: it collects evidence without changing your Datadog configuration.
See Boundera in action
Walk through your Datadog connection and the logging evidence it brings into Boundera.