Skip to content

Alerts by email, Slack and webhook

Alerts reach you from the first minute, with nothing to set up: your own verified email address is one press away on Alerts in the command centre. Xovris adds Slack for you after one approval in Slack - Do it yourself instead: add Slack or a webhook on Alerts whenever you like.

Terminal window
curl -s -X POST https://api.xovris.ai/v1/webhooks/ENDPOINT_ID/test \  -H "authorization: Bearer $XOVRIS_TOKEN"
Add a webhook endpoint

This works in Xovris today. Start free and it is yours from your first sign-in.

Each alert carries the exact error, what it means, the cause once it is found and what Xovris is already doing about it. One cause pages you once: if one fault breaks fifty sites, you get one alert with the fifty held and counted, and an unrelated critical alert still reaches you on its own.

Email is built in. A message counts as delivered only when the mail provider reports it, and a late message says so – with when it happened and when it arrived. Every email carries a one-click unsubscribe.

Connect Slack and choose the channel. A test alert shows Slack’s own acceptance before you rely on it. Each incident keeps one thread, updated as it moves – evidence found, a fix started, the fix proven – and if Slack stops accepting alerts, the alert reaches you by email and says why.

What Slack lets Xovris fix

  • To post alerts and their updates in the channel you choose.
  • To join the public channel you picked, so you never have to invite the app yourself.

Can read

  • See public channel names – To let you pick a channel by name.
  • See private channels the app is in – To let you pick a private channel the app was invited to.
  • See who people are, to mention the right person – To mention the person who owns the alert.
  • Match members by email address – To match your Xovris members to their Slack accounts.
  • Read messages in public channels the app is in – To find an alert's own thread again after a restart, so an update is never posted twice or lost.
  • Read messages in private channels the app is in – The same thread check, in a private channel you invited the app to.

Can change

  • Post alerts in channels the app is in – To post alerts and their updates in the channel you choose.
  • Join public channels – To join the public channel you picked, so you never have to invite the app yourself.

To take it back: Remove the Xovris app from your Slack workspace; Xovris reads the revocation and falls back to email.

Alerts, incidents, fixes and changes reach any HTTPS endpoint you own as signed Standard Webhooks – see Webhooks.

  • Routes send each alert to the right people by application, environment, severity or owner. The default route always stays in place, so an alert always reaches someone, and the command centre shows where an alert would go.
  • Maintenance windows hold alerts while you work and always end; a check that is still failing afterwards alerts at once.
  • Quiet hours hold non-critical alerts until the morning digest; a critical alert still reaches you straight away.

You can acknowledge an alert from its own page, in the command centre or in Slack. Acknowledging, closing a linked ticket or closing the incident by hand never marks it recovered – only the check that failed, passing again, does.

Ask Xovris

Open the full page

Your data is never used to train our AI. How your data is kept

A problem is called fixed only once it works again. How each fix is checked

XOVRIS LTD, registered in England and Wales, company number 17499910. Registered office: 66 Paul Street, London EC2A 4NA.