Alerts and SLOs with Venn

Create, tune, mute, and delete alerts and SLOs by conversation, with every new alert reviewed by you before it goes live.

Alerts

The full alert lifecycle works conversationally:

• "Alert me when the error rate in checkout passes 5 per minute": Venn drafts the alert (condition, thresholds, destinations) and opens the alert create form pre-filled for your review. You save it through the normal flow.

• "List my alerts", "what does the checkout-errors alert do?"

• "Mute the disk-space alert for now", "unmute it"

• "Update the threshold on checkout-errors to 10 per minute"

• "Delete the old staging alert": available once your administrator has enabled delete tools (they are off by default); deletions then still require your explicit approval before anything is removed.

Alert destinations (Slack, email, webhooks, and more) can also be set up with Venn's help: it stages the destination configuration and opens the create wizard pre-filled. If the destination needs a secret such as a webhook token, you enter that in the form yourself; Venn never asks for secrets in chat.

SLOs

• "Create an SLO for the payments API: 99.9 percent availability over 30 days"

Venn drafts the SLO (objective, indicator, window, targets) and opens the multi-step SLO form pre-filled, marked as AI-prefilled, for you to review and save.

SLOs in Ascent are availability-based today. Latency-based SLIs are not supported yet, and Venn will steer you toward an availability objective if you ask for one.

A note on alerts created by SIEM detections

When a SIEM detection built with Venn includes an alert, that alert is created disabled with no destination. Enable it and pick destinations when you are ready. This prevents a drafted detection from paging anyone by accident.