Datadog integration

    Updated 7 October 2026

    Connect Datadog so Operate can start investigations from Datadog alerts and read the related logs alongside your database and code.

    Prerequisites

    • A running Operate instance with a public URL so Datadog can deliver webhooks.
    • API key with logs_read_data and monitors_write scopes, plus an App key, site, and service name.

    Setup

    In Operate, go to Settings, Integrations, Log Providers, Datadog. Enter the API key, App key, site, and service name. A verify step checks the credentials before saving. Details are in the setup guide.

    What Datadog contributes

    Alert webhooks start investigations. Datadog logs become evidence that Operate correlates with database queries and git history, so a latency alert can be traced to a specific query and the commit that changed it.

    Output

    A .patch file plus the evidence behind the finding. An engineer reviews and applies it.

    Limitations

    • The documented scopes include monitors_write. Confirm your security review accepts that scope before connecting.
    • Only the Datadog service you configure is read.
    • Findings depend on what your logs record.

    Frequently Asked Questions

    Which Datadog scopes are needed?

    API key with logs_read_data and monitors_write scopes, plus an App key, site, and service name.

    Sources

    Checked on 7 October 2026.