Resolve Alert Incident

POST /alerts/incidents/{incident_id}/resolve

Role floor

Requires member 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
incident_id	path	string (uuid)	required	—

Responses

Status	Description	Body
200	Successful Response	AlertIncidentView
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/incidents/{incident_id}/resolve \
  -H "Authorization: Bearer $COBRE_TOKEN"

Response — AlertIncidentView

Field	Type		Notes
id	string (uuid)	required	—
alert_rule_id	string (uuid)	required	—
status	open | acknowledged | resolved	required	—
severity	info | warning | critical	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	—
comparator	gt | gte | lt | lte	required	—
threshold	number	required	—
triggered_value	number	required	—
last_value	number | null	required, nullable	—
resolved_value	number | null	required, nullable	—
opened_at	string (date-time)	required	—
acknowledged_at	string (date-time) | null	required, nullable	—
resolved_at	string (date-time) | null	required, nullable	—
last_notified_at	string (date-time) | null	required, nullable	—
notification_count	integer	required	—
context	object	required	—