Send alerts where you work
Alerts are part of Vaicoa Pro and Vaicoa Team. PagerDuty targets need Vaicoa Team.
Vaicoa sends an alert when one of its alert rules fires and when it resolves. Push reaches your phone at once, the email digest keeps a record, and alert targets put alerts into your own tools.
The digest and targets carry warnings and critical alerts only, and never muted alerts.
Push notifications
Section titled “Push notifications”Push needs a team on Pro or Team, signed in on the phone, and your permission.
The first time you sign in to such a team, the app offers to turn notifications on, then iOS asks. Later: Settings → Notifications → Enable notifications. Critical alerts are time-sensitive and are delivered during Focus modes.
- Settings → Notifications → Send test notification sends a test to every device signed in to your account.
- A device receives alerts for every team you have signed in to on it. Tapping one from another team switches to that team. Leaving a team stops its alerts; signing out stops all push to the device.
- A resolved notification replaces the firing one.
Email digest
Section titled “Email digest”One address per team gets a list of the alerts that started and resolved since the previous digest. There is no email per alert.
-
In the portal, open Alerts. This needs the Administrator role.
-
Under Email digest, choose Send alert emails to from the verified addresses of the team’s members. There is one recipient, to limit how many copies of your alerts exist.
-
Choose How often: Every 4 hours, Once a day (morning) (the default) or Once a week (Monday morning). Optional: Which alerts → Critical alerts only.
-
Save. To stop the digest, choose No alert emails.
The daily digest goes out at 07:00 UTC, the weekly one on Monday at 07:00 UTC, the four-hourly one four hours after the last. An empty period sends no email. Every digest also lists what is still firing, so a long-running problem appears in each one. An alert appears once when it starts and once when it resolves; one that did both between two digests is one line. The plain-text email links each alert to the app and is written in the recipient’s language, from their portal profile.
Alert targets
Section titled “Alert targets”A target sends each alert to your own tools the moment it starts or resolves. Pro has one target, Team up to five, each with its own Which alerts.
-
In the portal, open Alerts and choose Add Webhook under Delivery targets.
-
Enter a Name. The portal shows only a target’s scheme and host, so the name tells targets apart.
-
Paste Send alerts to this URL: an https endpoint that accepts a JSON
POST, your own or a bridge in front of a chat service. Use the final URL; redirects are not followed. -
Choose What we send: Standard payload, or Coding-agent brief for an endpoint that feeds an agent. If the endpoint expects a credential, fill in Authentication header (optional) and Header value.
-
Save, and store the signing secret in your receiver. It is shown once.
-
Send a test event. The result appears on the page.
The URL and header value are stored encrypted and never shown again. Issue a new signing secret replaces the secret. After 20 failed attempts in a row, one a minute, a target switches itself off until you choose Switch it back on. Every field, the payload and the signature check: Alert webhook reference.
PagerDuty (Vaicoa Team only). Add an Events API v2 integration to your PagerDuty service. In the portal, choose Add PagerDuty, the Service region and the Integration routing key. Each alert episode opens one incident with its severity and closes it on resolve. On Pro, point a webhook at a bridge instead.
Private push topic
Section titled “Private push topic”A team also has a private push topic that alerts are delivered over. The portal’s Alerts page does not show the topic itself yet, and explains why. It offers Issue a new topic, for example when someone leaves the team. The change takes about ten minutes, and alerts keep arriving during it.
When your plan changes
Section titled “When your plan changes”A plan change never deletes a target. If the new plan allows fewer, the oldest keep working and the page says which are paused; they resume when the plan allows them. A PagerDuty target on Pro receives nothing. A free account can save a recipient and one target, but nothing is sent.