Send alert evidence to on-call owners
Connect
SPIRITT
DatadogDatadog
Put signals to work
SPIRITT investigates metrics, logs, and traces, builds monitoring systems, and coordinates the response. Give it a reliability mission, from protecting an API to keeping on-call coverage current.
What you can do with Datadog.
Investigation with evidence
Connect failing monitors to service dependencies, log patterns, and traces so responders get a focused investigation, not another alert summary.
Coverage that gets built
Turn service requirements into Datadog monitors, synthetic API tests, SLOs, and dashboards that make reliability targets actionable.
Coordinated response
Bring current on-call ownership into Slack and issue tracking, with maintenance downtime and routing rules aligned to your operating plan.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the reliability, monitoring, or on-call operations you want to delegate.
02
Connect Datadog
Connect Datadog with access to the telemetry and monitoring objects your mission needs, plus permission for any configuration changes.
03
Delegate an outcome
Give SPIRITT a service, reliability goal, and operating rules. It builds the monitoring workflow, investigates exceptions, and coordinates follow-through.
Hand over a mission.
Choose a mission. Make it yours.
Put Datadog to work.
Give reliability an operator
Questions
Datadog, with SPIRITT.
01What can SPIRITT create or change in Datadog?+
SPIRITT can create and update monitors and dashboards, create SLOs and synthetic API tests, submit custom metrics, and record events. It can also create downtime, mute or unmute monitors, and manage supported On-Call schedules, escalation policies, and routing rules.
02What access does a Datadog mission need?+
Access should match the mission: telemetry investigation needs the relevant metrics, logs, traces, and service data; configuration work also needs permission to change the selected objects. On-Call work requires access to the relevant teams, users, schedules, and routing configuration.
03Can SPIRITT investigate across logs, metrics, and traces?+
Yes. It can query metric time series, search and aggregate logs, search traces, aggregate span data, and retrieve service dependencies. These sources support evidence-based investigations that distinguish observed failures from possible causes without treating correlation as proof.
04Can it route Datadog alerts into Slack and issue tracking?+
Yes. SPIRITT can create a Datadog webhook and update selected monitors to reference it, then build a receiving workflow that coordinates Slack and tools such as Jira or Linear. Registering a webhook alone does not subscribe every monitor; the monitor reference is a separate configuration step.
05What useful software can SPIRITT build around Datadog?+
It can build a service health console, a release comparison tool, an alert intake service, or a custom business-metric collector. Datadog supplies the telemetry and monitoring objects while SPIRITT builds the interface, scheduled operation, and cross-tool follow-through around them.
06How is SPIRITT different from a Datadog monitor?+
A Datadog monitor evaluates configured conditions and sends notifications. SPIRITT can build and tune those monitors, investigate the surrounding telemetry, retrieve on-call ownership, and carry findings into engineering work. It operates the broader workflow rather than replacing Datadog's monitoring engine.