Sign in
latestOpenAPI 3.1.02026-08-223321,1001.6 MB

2134ebffd1ef

Cron Triage

Triage a cron-sourced alert for the organization identified by config_name.

Args: request: CronTriageRequest identifying the organization (by config name), the triggering alert, and the reporting user. m2m_token: Bearer-authenticated machine token (validated by get_jwt_token_from_bearer); this endpoint does not check its claims beyond requiring a valid token.

Returns: CronTriageResponse describing the outcome of the triage flow.

post/cron/triage

Request body

user_idstring nullable
user_uuidstring nullable
user_emailstring required
config_namestring required
user_messagestring required
incident_timestring required
incident_timezonestring required
alert_source_idstring required
alert_namestring required
alert_descriptionstring required
alert_source_linkstring nullable
alert_tagsstring[]
anomaly_status'suppressed' | 'analyzed' | 'anomalous' | 'noise' required

Enum for anomaly status values.

Used to track whether an alert has been analyzed and deemed anomalous or noise.

mode'rca' | 'chat' | 'triage' | 'alert_story'
alert_idstring nullable
monitor_idstring nullable
trigger_type'manual' | 'auto-trigger' | 'slack_mention' | 'slack_dm' | 'slack_investigate_command' | 'slack_channel_join_auto_trigger' | 'slack_message_auto_trigger' | 'topology_explore' | 'alert_chat' | 'alert_event_manual_investigate' | 'alert_event_anomaly_detected_investigate' | 'proactive_followup' | 'alert_story' | 'alert_summary' | 'api' | 'mcp' | 'channel_agent' | 'deep_wiki' | 'autoresearch' | 'incident_monitor_postmortem'

Response

Successful Response

successboolean required