SikurdHelp
Open Sikurd

See your first alert

Trigger a test alert and verify routing end-to-end.

Once an instance is connected and polling, Sikurd will fire real alerts whenever it sees a problem. To verify your routing pipeline is working before anything breaks for real, fire a test alert.

Fire a test alert

  1. Go to Instances → click an instance.
  2. Scroll to the Quick actions card on the right.
  3. Click Simulate alert.
  4. Pick a severity (Critical / Warning / Info), a type (e.g. "Trunk Down"), and submit.

Sikurd fires the alert through your full routing chain just like a real one would: push, email, PSA, Slack, AI voice — whatever you have configured for that severity.

What you should see

  • An email to the email you signed up with.
  • A push notification if you've granted mobile permission on this device.
  • A row in Dashboard → Alerts with the alert open and the routing badge ("Sent: Push, Email, Slack").

If you have PSA configured, you'll also see a fresh ticket in your ConnectWise / Autotask / HaloPSA / Syncro queue.

Resolve it

Test alerts behave exactly like real ones. To dismiss:

  1. Open the alert row in Dashboard → Alerts.
  2. Click Resolve.
  3. (If PSA is on) The PSA ticket auto-closes.

Set up the rest of routing

The default routing is push + email to the owner. Once you have a team:

  • Alert routing matrix lets you decide, per alert type + severity, which channels fire (Mobile, Email, PSA, Slack, Teams, Webhook, AI voice call). Walkthrough →
  • Escalation policies decide who gets paged if no one acknowledges. Walkthrough →

Next

You've got the basics. From here, dip into:

  • Workflows overview — every page in the product gets its own walkthrough.
  • FAQ — short answers to the things most operators ask.