Alerts and notifications

SignalSitter sends incident and recovery events to a callback endpoint. An endpoint is an HTTPS URL your own system runs, one person reached through WhooshBang, or everyone in your organization reached through WhooshBang. Set up the endpoint once, then choose which monitors use it.

Add a callback endpoint

1. Go to Settings > Callback endpoints.
2. Enter an Endpoint alias: 1 to 64 letters, digits, hyphens or underscores, starting with a letter or digit. Monitors and publish headers use this name.
3. Under Where should incidents go?, choose A URL your own system operates.
4. Enter the Destination URL: a public HTTPS address with no username, password or #fragment.
5. Press Create endpoint.
6. Press Copy the signing secret and store it with your receiver. It’s shown once. Then press I have stored it, hide this secret.

Your receiver uses the secret to check that each delivery came from SignalSitter. See the REST API guide for the delivery format.

Send alerts to people through WhooshBang

WhooshBang delivers alerts to a person’s own messenger. SignalSitter issues no signing secret for these endpoints and asks nobody for a credential. Each person connects their own messenger under Notifications (below). Anyone who hasn’t connected one isn’t reached.

1. Go to Settings > Callback endpoints and enter an Endpoint alias.
2. Under Where should incidents go?, choose one:
   • A person, reached through WhooshBang. In Who to notify, leave it blank to notify yourself, or enter another member’s SignalSitter user identifier. They stop receiving alerts if they leave the organization.
   • Everyone in this organization, reached through WhooshBang. Whoever belongs to the organization when an incident happens is notified.
3. Leave WhooshBang notifier blank unless WhooshBang told you to use a particular notifier.
4. Press Create endpoint.

Caution

Send a test delivery on a WhooshBang endpoint sends a real message. On an Everyone in this organization endpoint, it reaches everyone who has connected a messenger, and nothing on it says it’s a test.

Manage an endpoint

Button	What it does
Send a test delivery	Sends a test and shows the response status. Changes nothing.
Change destination	Points the endpoint at a new URL. The signing secret stays the same.
Change WhooshBang destination	Changes Who to notify or the notifier on a person endpoint.
Change WhooshBang notifier	Changes the notifier on an Everyone in this organization endpoint.
Rotate secret	Issues a new secret, shown once. The old one keeps working for a short overlap. URL endpoints only.
Make organization default	Monitors that use the default deliver here. Clear organization default undoes it.
Switch off	Stops deliveries without deleting anything. Switch on starts them again. A switched-off endpoint can’t be the default.
Delete	Permanent. Monitors still pointed at it report it was deleted.

Note

Creating, changing and deleting endpoints needs the owner or admin role. Everyone can see them.

Choose where a monitor’s alerts go

1. Open the monitor and go to Settings.
2. Under Callback destination, pick one:
   • Use organization default
   • a named endpoint (any endpoint that’s switched on)
   • Do not send callbacks
3. Press Save callback destination.

Effective destination now shows where alerts will go. You can also pick a Callback destination when you create the monitor.

Get your own alerts on your phone

Connect your own messenger so WhooshBang endpoints can reach you. You don’t need a WhooshBang account.

1. Go to Settings > Notifications.
2. Press the connect button for your messenger, such as Connect Telegram.
3. Finish connecting in the window that opens.

If the settings stop working, press Open notification settings again. Nothing you’ve already connected changes.

Next

• Incidents: see every delivery and request a redelivery.