Test Alert Rule

POST /alerts/{alert_rule_id}/test

Dry-run evaluation, no side effects.

Shares _measure with the sweep, so what this previews is what the evaluator would do — a preview computed by a second code path is a preview of something else.

Role floor

Requires admin or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Parameters

Name	In	Type		Notes
alert_rule_id	path	string (uuid)	required	—

Responses

Status	Description	Body
200	Successful Response	AlertRuleTestResult
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

curl -X POST https://your-deployment.example.com/alerts/{alert_rule_id}/test \
  -H "Authorization: Bearer $COBRE_TOKEN"

Response — AlertRuleTestResult

Field	Type		Notes
rule_id	string (uuid)	required	—
metric	error_rate | success_rate | failure_count | run_count | avg_latency_ms | p95_latency_ms | cost | token_total | queue_depth | suspension_age | queued_without_workers | provider_credit_remaining | providers_unreachable	required	—
value	number | null	required, nullable	—
breached	boolean	required	—
skipped	string | null	required, nullable	—