Axemere.ai

Alert Channels

Alert Channels define where Axemere sends notifications when notable events occur: policy denials, approval requests, budget thresholds, or gateway health changes. Configure them once; reference them in policies or let the system use them for automatic alerts.

Axemere Console — Alert Channels

Supported channel types

ChannelWhat you need
SlackAn incoming webhook URL from your Slack workspace
Microsoft TeamsAn incoming webhook URL from a Teams channel
Google ChatA webhook URL from a Google Chat space
DiscordA webhook URL from a Discord channel
EmailOne or more email addresses

Adding a channel

  1. Go to console.axemere.ai/analytics/alerts
  2. Click Add Channel
  3. Select the channel type
  4. Enter the webhook URL (or email addresses for Email channels)
  5. Give the channel a name (e.g. ops-slack, security-team-email)
  6. Click Save

The console sends a test notification immediately after saving so you can verify delivery.

Channel configuration

Slack and Microsoft Teams

Paste the incoming webhook URL provided by Slack or Teams. Axemere sends a formatted card with the alert type, affected workload, and a link to the relevant console page.

For Slack: generate a webhook at [Your workspace] → Settings → Apps → Incoming Webhooks.

For Teams: generate a webhook via Channel → Connectors → Incoming Webhook.

Google Chat

Paste the webhook URL from your Google Chat space (Space settings → Apps & integrations → Manage webhooks). Axemere sends a formatted card with the alert details.

Discord

Paste the Discord webhook URL (Channel Settings → Integrations → Webhooks → New Webhook → Copy Webhook URL). Axemere sends a plain-text formatted message.

Email

Enter one or more email addresses (comma-separated). Axemere sends HTML-formatted alert emails from noreply@axemere.com.

When alerts are sent

Axemere sends notifications to configured channels for:

EventTrigger
Approval requestA policy require_approval rule fires; reviewers are notified
Budget thresholdSpend approaches or crosses a configured cap
Gateway offlineA connected node stops sending heartbeats
Credential errorA request fails due to an invalid or expired provider API key
High risk scoreA request's composite risk score exceeds 0.7
QuarantineA workload is quarantined due to anomalous behavior

System-level infrastructure alerts (Cloud SQL, load balancer) are delivered separately to operations team channels and are not configurable from the console.

Referencing channels in policies

Alert channels can be referenced in require_approval policy rules to notify specific channels when an approval is needed:

rules:
  - id: gate-high-cost
    conditions:
      - field: action.params.model
        op: in
        value: ["gpt-4o", "claude-3-5-sonnet-20241022"]
    effect: require_approval
    approval:
      reviewers: ["admin@yourcompany.com"]
      alert_channel: ops-slack   # channel name from the console
      expiry_minutes: 60

When this rule fires, Axemere sends an approval request notification to the ops-slack channel in addition to emailing the listed reviewers.

Managing channels

  • Test: Click the test icon next to any channel to re-send a test notification
  • Edit: Click the channel name to update it. The webhook URL field is never shown or prefilled; Axemere doesn't return it after creation, so retain your own copy if you need it. Leave the field blank to keep the current webhook URL, or enter a new one to replace it. The email list is not a secret and does prefill for editing.
  • Delete: Remove a channel when it is no longer needed; policies referencing it will fall back to email-only notification

Next steps