Datadog integration
Enrich service tickets with Datadog observability data and automate host, monitor, and incident management directly from your service workflows.
What it connects
- Organization users and service accounts, including their assigned roles and active status, so STLabs can correlate access and ownership with infrastructure events.
- Monitored infrastructure hosts with platform details, tags, and real-time reporting status across your entire environment.
- Alerting monitor configurations, their current state, thresholds, owning teams, and alert history, so STLabs knows what is being watched and whether it is firing.
- RBAC roles and organizational teams so STLabs can map Datadog permissions and group ownership to the right responders and approval chains.
What it automates
- Silence a noisy or under-maintenance host so alerts are suppressed during planned work, and re-enable monitoring when the window closes.
- Create or update alerting monitors to add new coverage or adjust thresholds as part of a change or incident workflow, without leaving STLabs.
- Schedule a downtime window on any monitor group before a maintenance event, then cancel it automatically when the change is confirmed complete.
- Open or update a Datadog incident record to kick off a coordinated response, and post a timestamped event to the audit trail as key milestones are reached.
In practice
A change request for a database migration is approved. STLabs automatically schedules a Datadog downtime window for the affected monitors, suppressing false alerts during the maintenance period and canceling the window once the change ticket is closed.
An on-call engineer opens a P1 ticket for a service degradation. STLabs pulls the current state of all related Datadog monitors and the list of affected hosts, surfacing them inline so the responder has full context before they start investigating.
A new microservice is deployed through a change workflow. STLabs creates a Datadog monitor for the service's error rate and latency based on a standard template, ensuring observability coverage is in place from day one.
A host is flagged for emergency patching. STLabs mutes the host in Datadog to prevent alert noise during remediation, posts a deployment event to mark the start of the change, and unmutes the host automatically when the ticket moves to resolved.
