List failing Drata monitoring tests
Automatically list failing Drata monitoring tests on drata.com. List the Drata monitoring tests that are currently failing in production, each with its failing resources or people: name, account, region and severity, plus how many findings and exclusions it has. Needs a Drata session. Read-only: it changes nothing in Drata.
Input
workspaceId optionalDrata workspace id. Defaults to the workspace the app opens.
includeFindings optionalAlso fetch the failing resources (findings) of each failing test.
Default: trueOutput
tests requiredfailingCount requiredcheckedAt optionalFAQ
Drata whoami (signed-in account)
Report which Drata account this browser is signed in as: the user id, email, first and last name, roles, account type, and the workspace and region the app opened. Being signed out is reported as a normal answer (loggedIn false), not an error, so it can be used to check a session before running other Drata scripts.
Retest a monitor (Drata)
Re-runs one Drata monitoring test right away (the "Test now" button) instead of waiting for the daily check, then waits for the new result and returns the status before and after, with the failing and excluded resource counts. Takes the test number shown in the Drata UI (e.g. 7 for "Only Authorized Employees Change Code"). Requires being signed in to Drata.
Exclude a Drata monitoring finding
Exclude one failing resource (a repository, a person, a cloud resource) from a Drata monitoring test, with the written justification Drata shows auditors in its audit packages. Give the test page URL, the resource exactly as listed in the test's findings, and the reason. Needs a Drata session. It changes your compliance results, and undoing it is done from the test's Exclusions tab.
