Solutions by app
Datadog tracks monitors, metrics, logs, and events across your entire cloud infrastructure. Tray connects Datadog so alert states and metric thresholds trigger coordinated workflows across your stack, and agents can query monitors, search logs, and act on signals with context from every connected system.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Integrate Datadog with 700+ applications plus any system with an API using our HTTP connector. These domains reflect how teams work in Datadog.
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.
Find answers to common questions about our products and services.
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.
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.
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.
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.
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.
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.
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.
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.