Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.adrian.secureagentics.ai/llms.txt

Use this file to discover all available pages before exploring further.

Alerts notify you or your team when something noteworthy happens to one of your AI agents — a policy violation, an anomaly, a rate limit breach, or an agent going offline. You can route alert notifications to email, Slack, or any webhook-compatible endpoint.

​
Alert types

TypeWhen it fires
policy_violationAn event from an agent was blocked by an assigned policy.
anomaly_detectedSecureagentics detects unusual agent behavior (high error rate, token spike, traffic anomaly).
agent_downAn agent that was previously sending events has stopped sending them for longer than the configured threshold.
rate_limit_exceededAn agent hits the threshold defined in a rate_limit policy.
A single alert rule can cover multiple alert types. For example, you can create one alert that fires on both policy_violation and rate_limit_exceeded and sends notifications to the same Slack channel.

​
Create an alert

1

Open the Alerts page

In the Secureagentics dashboard, navigate to Alerts. You will see a list of existing alert rules for your organization.
2

Start a new alert

Click New Alert in the top-right corner.
3

Choose the alert type

Select one or more alert types from the Trigger section: policy_violation, anomaly_detected, agent_down, or rate_limit_exceeded.Optionally, scope the alert to a specific agent by selecting it from the Agent dropdown. Leave this set to All agents to monitor your entire fleet.
4

Select the notification channel

Under Notification channel, choose Email, Slack, or Webhook.
  • Email: Enter one or more recipient addresses.
  • Slack: Paste your Slack incoming webhook URL. See the Slack documentation for how to create an incoming webhook.
  • Webhook: Enter any HTTPS endpoint. Secureagentics will POST a JSON payload to this URL when the alert fires.
5

Save the alert

Click Save Alert. The alert is active immediately. You can test it from the Alerts list page (see Test an alert below).

​
Notification channels

​
Email

Enter a comma-separated list of email addresses in the Destination field. Secureagentics sends a plain-text email with the alert type, agent name, and a link to the relevant event in the dashboard.

​
Slack

Provide a Slack incoming webhook URL as the destination. Secureagentics posts a formatted message to the target channel including the alert type, agent ID, and a summary of the triggering event.

​
Webhook

Provide any publicly accessible HTTPS endpoint. Secureagentics sends an HTTP POST request to that URL with a JSON body each time the alert fires. Your endpoint must return HTTP 200 within 10 seconds, or Secureagentics retries delivery up to three times with exponential backoff.
Webhook endpoints must use HTTPS. HTTP destinations are not accepted. If your endpoint uses a self-signed certificate, contact support to arrange an exception.

​
Webhook alert payload format

When an alert fires and the channel is webhook, Secureagentics sends the following JSON body to your destination URL: 
{
  "alert_id": "alr_2a3b4c5d6e7f8g9h",
  "alert_name": "policy-violations-webhook",
  "alert_type": "policy_violation",
  "agent_id": "agt_01hx9z3k2m4n5p6q7r8s9t0u",
  "timestamp": "2026-05-04T10:42:11Z",
  "details": {
    "event_id": "evt_09jk2l3m4n5o6p7q",
    "event_type": "prompt",
    "policy_id": "pol_07ab1c2d3e4f5g6h",
    "policy_name": "max-100-prompts-per-minute",
    "reason": "rate_limit_exceeded"
  }
}
FieldTypeDescription
alert_idstringID of the alert rule that fired.
alert_namestringHuman-readable name of the alert rule.
alert_typestringThe type of alert: policy_violation, anomaly_detected, agent_down, or rate_limit_exceeded.
agent_idstringThe ID of the agent that triggered the alert.
timestampstringISO 8601 timestamp when the alert fired.
detailsobjectContext specific to the alert type. For policy_violation, includes event_id, event_type, policy_id, and reason.

​
Test an alert

You can send a test notification to verify your channel is configured correctly before any real events occur.
1

Find the alert in the Alerts list

Navigate to Alerts in the dashboard. Locate the alert rule you want to test.
2

Send a test notification

Click the … menu on the alert row and select Send test notification. Secureagentics immediately sends a synthetic payload to the configured destination.
3

Confirm delivery

Check your email inbox, Slack channel, or webhook endpoint logs to confirm the test notification arrived. The test payload uses the same format as a live alert, with "alert_type": "test" in the body to distinguish it from real events.
Test notifications count as a delivery attempt but do not appear in the Events timeline or audit logs, since no real agent event triggered them.