Skip to main content

​
What this check does

DSALTA lists Datadog incidents (GET /api/v2/incidents) and checks for incidents that are still open or unresolved.
This check also runs on 1 other integration — see Reported incident should be closed for the full list.
Passes when: No reported Datadog incident remains open or unresolved.

​
Why this matters

Open incidents represent unresolved risk and must be driven to closure.

​
How to fix

Resolve open Datadog incidents
  1. Sign in to Datadog and open Service Management → Incidents from the left navigation.
  2. Set the list filter to State: Active so only the unresolved incidents keeping this test red are shown.
  3. Open an incident whose underlying issue has already been fixed and read its Timeline to confirm the remediation is complete.
  4. In the incident header, change Status from Active to Resolved, and fill in any fields your workflow marks required — typically Severity, Root cause, and a resolution summary.
  5. Save the incident and confirm it drops off the State: Active view.
  6. In DSALTA, open Data Library → Incidents and confirm the Datadog-sourced records now show a resolved status.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Data Library → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.