WebhookAlertExporter posts a small JSON alert whenever an evaluated event’s action is one you choose, by default block and escalate. SlackAlertExporter is the same exporter with the body shaped for Slack incoming webhooks. Both use only the standard library and are importable from agentegrity or agentegrity.exporters.alerts.
Register one on an adapter and every evaluated event that reaches the configured action is posted:
Constructor
str
required
Webhook endpoint. Each alert is POSTed with
Content-Type: application/json.set[str] | None
default:"{'block', 'escalate'}"
Actions that trigger an alert. Possible actions are
pass, alert, escalate and block. Keyword-only.float
default:"5.0"
Per-request timeout in seconds. Keyword-only.
What triggers an alert
on_event looks at the event’s evaluation result. Events without one (for example post_tool_use_failure or subagent_start) never alert. For evaluated events, the exporter alerts when the overall action (the most severe action across the layers) is in alert_on. on_session_start does nothing.
Payload
WebhookAlertExporter sends this body:
SlackAlertExporter sends a body with a single text field: one line that names the action (in bold), the adapter, the event type, the tool when there is one, the composite score, the failing layers and the session id.
The {"text": ...} shape is also accepted by Discord- and Teams-compatible endpoints that take Slack-style payloads. To post a different shape, subclass WebhookAlertExporter and override _format(alert) to return the body you want.
Alerts carry the verdict and nothing else. Prompts, tool arguments, tool output and layer details are never included.
Delivery
Alerts go on a queue of up to 200 and are posted in order by one background daemon thread. A full queue drops the alert and logsalert queue full; dropping <action> alert. A failed POST is logged as alert delivery failed (...); dropping on the agentegrity.exporters.alerts logger, with no retry. on_session_end calls flush(), which waits up to 5 seconds for queued alerts to go out; you can call flush(timeout=...) yourself.
describe() returns the exporter type and the URL with its query string removed, so a token passed as a query parameter does not appear in the session summary.
Calling it directly
Like every exporter, the callbacks are coroutines andon_event takes an event in its dict form (FrameworkEvent.to_dict()), which is what adapters pass. To replay events an adapter already recorded: