ankra alerts
Manage where Ankra delivers alerts and platform notifications. Destinations are the endpoints notifications are sent to: a webhook URL (Slack, Microsoft Teams, Discord, PagerDuty, or any custom receiver) or a Slack/Teams channel the Ankra bot posts to directly. Routes decide which notifications reach which destination, filtered by kind, severity, cluster, and source, so the whole alerting setup can live in scripts and CI next to the rest of your platform configuration.ankra alerts destinations
Manage the organisation’s alert destinations. A destination is either a webhook URL or a channel-based Slack/Teams destination that carries a channel id instead of a URL (list the channels the Ankra bot can post to with ‘ankra alerts destinations channels’). Webhook URLs are shown masked on every read.ankra alerts destinations channels
List the channels the Ankra bot can post to, for use with ‘ankra alerts destinations create--channel-id’. Both providers are shown
unless --provider narrows it to one.
A provider whose workspace or tenant is not connected to the organisation
reads “not connected”; one whose bot service is not configured on this
platform reads “not available”. Neither is an error.
ankra alerts destinations create
Create an alert destination. Pass--url for a webhook destination, or --channel-id for a channel-based
Slack or Teams destination (find ids with ‘ankra alerts destinations
channels’); a Teams channel also needs --teams-tenant-id. --type records
which receiver the destination targets (slack, teams, discord, pagerduty,
custom; default slack) and selects the default payload format;
--template-file overrides the payload with your own template.
ankra alerts destinations delete
Delete an alert destination. Routes that pointed at it stop delivering; remove or re-point them with ‘ankra alerts routes’.ankra alerts destinations get
Show one alert destinationankra alerts destinations list
List the organisation’s alert destinations, 20 per page. Filter by name with--search and by state with --enabled or --disabled. The
ID column is what routes and the other destination commands take.
ankra alerts destinations test
Send a sample notification to a stored destination and report whether the receiver accepted it. A failed delivery exits non-zero so CI can gate on it; the details are still printed (or emitted with -o json).ankra alerts destinations test-url
Send a sample notification to an ad-hoc webhook URL, optionally with a custom payload template, without creating a destination. A failed delivery exits non-zero.ankra alerts destinations update
Update an alert destination. Only the flags you pass are changed; the rest keep their current values.ankra alerts ingest-credentials
Ingest credentials are the per-credential secrets an external Alertmanager or log monitor uses to deliver alerts into Ankra. A credential is pinned to one cluster (scope cluster), carries the platform’s own alerts with no pin (scope platform), or does both from a self-hosting cluster (scope mixed). The token is minted once, in the portal, and never shown again. These commands never touch it: a rebind moves the pin or the scope on the existing credential, so the notifier keeps delivering.ankra alerts ingest-credentials list
List the organisation’s alert ingest credentials with the cluster each one is pinned to. A pin whose cluster is deleted, archived, slated for deletion or gone shows as BROKEN: the notifier still delivers, but its alerts have no cluster to land on until the credential is rebound.ankra alerts ingest-credentials rebind
Rebind an ingest credential: pin it to another cluster, unpin it, or change its scope. The token is untouched, so the notifier keeps delivering through the same credential. Pass--cluster with a cluster name to pin, --unpin to clear the pin, and
--scope with cluster, platform or mixed. A platform-scoped credential
carries no pin; a mixed one must keep one.
ankra alerts routes
Manage the organisation’s notification routes. A route sends notifications matching every filter it sets (kind, severity, cluster, source) to one destination; a route with no filters matches everything. Routes are evaluated in ascending priority, mode “exclude” withholds matches instead of delivering them, and--stop-on-match ends the
walk at that route so lower-priority routes never see the notification.
ankra alerts routes create
Create a notification route to a destination. Every filter is optional; a route with none matches every notification. Kinds include execution_failed, resource_deployment_failed, resource_health_degraded, alert_trigger_fired, gitops_sync_failed, agent_offline, security_new_severe_cves, and the other platform notification kinds; severities are critical, warning, and info.ankra alerts routes delete
Delete a notification routeankra alerts routes list
List notification routesankra alerts routes preview
Resolve a hypothetical notification against the organisation’s routing rules and, with--alert-id, that alert’s own destinations, and print the
destinations it would reach with the reason each one matched.
Nothing is delivered and nothing is changed - this is a dry run.
Pass --alert-id whenever you preview an alert firing. A destination reached
by both the alert’s own list and a routing rule is delivered to once, and
without the alert id the preview cannot tell you which rule that affects.