code0Vörr AIContactGuides
Book a Demo
Guides/Shankh/Getting Started

Set up alerting

Cloud Integration · VörrIntermediate7 min

Set alerting up last, once there is somewhere for its alerts to go. AWS has native discovery and alert setup in Shankh; Grafana, Jenkins and SigNoz are connected as Vörr connectors; anything else sends to the private webhook.

AdminCloud Integration, including alert-management credentials, requires Admin access.

Check where your source belongs

Setup pathSources
Native Shankh setupAWS
Vörr connectorGrafana, Jenkins, SigNoz
Private webhookOther compatible or custom payloads

Webhook sources do not currently use Shankh's native discovery, automatic alert setup or drift checking.

Connect a Vörr connector

  1. Open Vörr.
  2. Select Add connectors.
  3. Connect the required source and complete its configuration.
  4. Return to Shankh and confirm the source is available in your alerting setup.

Enter AWS alert-management credentials

  1. Open Cloud Integration.
  2. Enter the alert-management credentials for the AWS account.
  3. Save the credentials.
  4. Confirm the account's resources become available for selection.
Permissions vary by provider. Follow the permissions explicitly documented for your provider rather than a generic minimum set.

The credentials are stored encrypted in Frigga's database.

Choose the cloud, service and metrics

  1. Open the cloud account in Cloud Integration.
  2. Check the services Shankh discovered on it.
  3. Open a service to get its available metrics.
  4. Enable the metrics that should produce alerts.
  5. Set the threshold for each severity.
  6. Review the workspace assignment.
  7. Preview the alert configuration.
  8. Deploy the configuration.

Only the metrics the cloud actually exposes for that service are offered — the list comes from the account, not from a fixed catalogue.

Set a severity threshold

  • A threshold can include metric, operator, value, severity, evaluation period, datapoints required to alarm, and statistic or percentile where supported.
  • Use values that match the service and environment, not values copied from an unrelated service.
  • Make the evaluation window long enough to survive normal spikes.
  • Match the severity to how urgently a human needs to act.
  1. Select the metric to evaluate.
  2. Set whether a higher or lower value is a breach.
  3. Enter the threshold value.
  4. Assign the severity for that breach.
  5. Set the evaluation window.
  6. Set the number of periods that must breach before an alert fires.
  7. Save and deploy.

Verify the deployment

  1. Confirm the deployed configuration appears against the service.
  2. Confirm the workspace assignment matches the team that owns the service.
  3. Trigger or wait for a real breach, then confirm an incident appears in Incidents.

If no incident appears, work through the end-to-end test.