With Tray, you build
IconAutomations
IconIntegrations
and
IconAgents
that connect Datadog across your business systems and teams.
Icon

Use cases

Datadog + Tray

Datadog is where infrastructure and application health lives: monitors firing on metric thresholds, logs capturing runtime behavior, events marking deployments and anomalies, and dashboards giving teams visibility across services. What it doesn't do is coordinate the work that follows an alert, provision access, open a ticket, notify finance of a cost spike, or close the loop across the systems a signal touches.

Tray bridges the gap, turning monitor alerts and threshold events into multi-step workflows that read from Datadog, apply logic, and write to every system that needs to respond.

See how different teams use Tray to take action from Datadog.

What you can do with Tray

  • Engineering

    Engineering

    If you work in engineering, these are common ways teams use Tray with Datadog to connect monitor alerts and metric signals to deployment, incident, and resolution workflows.

    • Open tickets from monitor alerts: Create a linked issue automatically when a monitor transitions to an alert state, with threshold and service context pre-populated
    • Trigger rollback workflows on metric spikes: Detect error rate or latency threshold breaches via webhook and kick off a rollback or deployment hold upstream
    • Attach log search results to incidents: Query Datadog logs at alert time and append matching entries to the incident record for faster triage
  • IT

    IT

    If you work in IT, these are common ways teams use Tray with Datadog to keep monitor states, service health, and operational records in sync.

    • Sync monitor states to your ITSM: Create or update ITSM records when monitors fire or recover, keeping service health aligned across tools
    • Mute monitors during maintenance windows: Trigger monitor mutes automatically when change records are approved in your ITSM, and unmute on completion
    • Audit monitor configurations on a schedule: Pull monitor definitions periodically and sync them to a configuration store for change tracking and compliance
  • Security

    Security

    If you work in security, these are common ways teams use Tray with Datadog to route security signals into response workflows and keep access governed.

    • Route security events to your SIEM: Push Datadog events flagged as security-relevant to your SIEM or SOAR platform for correlation and case creation
    • Trigger access reviews from anomaly events: When a Datadog event signals unusual access or behavior, open an access review task in your ITSM automatically
    • Enforce RBAC on monitor access: Sync role and permission changes in Datadog with your identity provider when users are added or removed from roles
  • DevOps

    DevOps

    If you work in DevOps, these are common ways teams use Tray with Datadog to connect observability signals to on-call, deployment, and reliability workflows.

    • Page on-call from webhook alerts: Forward Datadog webhook events to your on-call platform when monitors breach SLO thresholds
    • Publish timeseries metrics from CI/CD pipelines: Write deployment and build metrics into Datadog as custom timeseries points to track release health over time
    • Resolve monitors after automated remediation: Mark monitors as resolved programmatically once a remediation workflow confirms the fix is in place
  • Finance

    Support

    If you work in finance, these are common ways teams use Tray with Datadog to connect cost and usage signals to budget tracking and reporting workflows.

    • Alert on cost metric thresholds: When a custom cost or usage metric monitor fires, notify the owning team and log the event to your financial reporting system
    • Export metric summaries for chargeback reporting: Pull active metric metadata and timeseries data on a schedule and push it to your data warehouse or finance tool
    • Track infrastructure spend changes via events: Query Datadog events tied to provisioning or scaling actions and sync them to your FinOps platform for cost attribution
  • Product

    Product

    If you work in product, these are common ways teams use Tray with Datadog to connect service health and usage signals to roadmap, feedback, and customer health workflows.

    • Flag customer-impacting incidents to your CRM: When a monitor affecting a production service fires, cross-reference affected accounts and update customer health records automatically
    • Sync deployment events to product analytics: Push Datadog deployment events to your product analytics platform to correlate releases with usage changes
    • Generate weekly reliability summaries: Pull monitor states and event history on a schedule and post a structured summary to your team channel or project tool
Slack Logo
Tray Logo
Icon

Automations

Automations with Datadog and Tray

Tray receives Datadog alert events via webhook, triggering workflows the moment a monitor fires or recovers. Workflows can also run on schedules to poll monitor states, query event history, or pull metric metadata for reporting and auditing.

Once triggered, workflows apply branching logic against monitor thresholds, service tags, and alert states, call connected systems to enrich context or drive parallel actions, and write results back, opening tickets in Jira, paging responders in PagerDuty, posting alerts in Slack, or updating records in ServiceNow when monitors recover. They can also be exposed as agent tools.

Icon

Integrations

Integrations with Datadog and Tray

Datadog sits at the center of your observability stack, aggregating metrics, logs, and events from infrastructure, applications, and cloud services. Tray extends that layer across the rest of your stack: workflows carry monitor alerts and metric signals into ITSM platforms, on-call tools, security systems, data warehouses, and any system that needs to act when something changes in your environment.

Datadog integration capabilities

Integrate Datadog with 700+ applications plus any system with an API using our HTTP connector. These domains reflect how teams work in Datadog.

Create, update, and act on monitor states across your stack.

  • Create and validate monitors: Define monitors with threshold and notification settings as part of governed provisioning workflows
  • Mute and unmute monitors: Suppress notifications programmatically during maintenance windows or automated remediation runs
  • Resolve and delete monitors: Close resolved monitors or clean up stale definitions as part of lifecycle management workflows
  • Search and list monitors: Query monitor state and metadata to drive triage logic or feed reporting pipelines downstream
Icon

Agents

Build agents with Datadog and Tray

Tray agents turn Datadog observability data into action. They ground on approved context such as monitor states, events, and metric timeseries, then call governed tools across your stack to respond to alerts, update records, and coordinate remediation in real time. Every outcome writes back to Datadog and connected platforms, so teams can ask, act, and audit in one continuous flow.

Ground agents with the observability context they need to act accurately

  • Object scope: Access monitor states and configurations, event history, active metrics, log search results, and user and role data within the permissions of your configured credentials
  • Freshness: Query monitor states and events at run time; metric timeseries and log searches can be scoped by time range, tag, or service

Frequently Asked Questions

Find answers to common questions about our products and services.

How does Tray authenticate with Datadog?

Tray connects using an API key and Application key from your Datadog account, with region set to US or EU to match your Datadog site.

How does Tray receive alerts from Datadog?

Tray supports Datadog webhook triggers. Configure a webhook in your Datadog account pointing to your Tray workflow URL, and workflows fire the moment a monitor alert or recovery event is sent.

Which Datadog objects does the connector support?

The connector supports monitors, events, metrics (timeseries and metadata), logs, users, roles, and permissions. Operations include create, read, update, delete, mute, unmute, resolve, search, and query across those objects.

Can workflows write data back into Datadog?

Yes. Workflows can create events, submit custom timeseries metric points, update metric metadata, resolve monitors, and manage users and roles from within any workflow or agent run.

How do approvals work for sensitive operations?

Workflows can require human sign-off before executing operations like monitor deletion, role assignments, or bulk user changes, routed through Slack, email, or any connected channel.

How do teams start small and scale with Datadog + Tray?

Most teams start with a single webhook trigger from a Datadog monitor and connect it to one downstream system, such as opening a ticket or paging an on-call responder. From there, branching logic, enrichment steps, and additional destinations can be added incrementally.

FAQs

Tray supports Datadog webhook triggers. Configure a webhook in your Datadog account pointing to your Tray workflow URL, and workflows fire the moment a monitor alert or recovery event is sent.

What comes standard with Tray

Whether your systems, data, or models run in the cloud or on-premises, Tray connects them in one secure platform. Every connection, workflow, and agent operates under IT governance with encryption, audit logging, and access controls built in. Security teams can trust that all integrations comply with enterprise network and authentication policies.

Universal connectivity

  • Prebuilt connectors: 700+ connectors plus a universal HTTP connector for any REST API
  • Custom connectors: Build custom connectors that behave like native ones
  • Connect anywhere: Cloud or on-prem systems supported

Learn more about our connectivity options

On-premises connectivity

  • Connect securely: Access on-premises systems, whether first-party or third-party
  • Meet network requirements: Connect through approved configurations that align with enterprise security policies
  • Enterprise protocols: Support multiple on-premises security standards for safe integration

Learn more about on-premises connectivity

Authentication management

  • Secure credentials: Collect and store authentications with full encryption
  • Encrypted data: Protect all data at rest and in transit
  • Role-based control: Partition credentials by workspace and access level

Learn more about authentication management

Security and governance

  • Certified compliance: SOC 2 Type II, GDPR, CCPA, HIPAA
  • End-to-end protection: Encryption, detailed audit logs, scoped connections, and OAuth scopes

Learn more about security and governance