Notifications
SquaredUp can alert you when the health state of any monitor changes by sending notifications.
Simply add a new notification destination in Settings > Notifications, configure any settings needed in your target system, and create notification rules from the Monitors page.
The supported integrations are:
The Settings > Notifications page allows you to manage your notification destinations. You are able to Add, Edit, Pause and Delete destinations.
Destinations can also be added from the Monitors page. You can use the Monitors page to set up notification rules, see Setting notification rules for more information. You cannot Edit, Pause and Delete destinations from the Monitors page.
Once you have added destinations, they will be shown in a table on the Settings > Notifications page. The table shows the number of workspaces and rules using the destination. Clicking on the Workspace number displays which workspaces are using the destination, and how many rules in the workspace are using the destination.
Adding a destination

Sending alerts to a Microsoft Teams channel is simple to configure:
Go to the Teams channel and select the Connectors option.
From the list of connectors, choose the Incoming Webhook connector and add it to the channel.
Give the webhook connector a name and icon. It makes sense to use a SquaredUp name and icon to make it clear that the alerts are coming from SquaredUp.
Click Create and you should be given a webhook URL.
Copy the webhook URL and then click Done.
Now use the webhook URL to configure the destination in SquaredUp:
In SquaredUp browse to Settings and then click Notifications.
Click Add Destination and then select the destination where the notifications should be sent to from the list of integrations.
Display Name:
Enter a name for your destination. This helps you to identify this destination in the list of your destinations.
URL:
Paste the webhook URL to configure the destination in SquaredUp.
Test:
Use the Test button to send a test notification and check that it is working as expected.

There are two ways to configure notifications:
The API approach is more complex to configure, but more flexible. In particular, it allows notifications to be sent to multiple Slack channels, whereas a Slack webhook is tied to a specific Slack channel.
If you are likely to configure multiple SquaredUp notification destinations to target different Slack channels, the API approach may be preferable. If you are only targeting a single Slack channel, the webhook approach should suffice.
Slack API
You will need to create a Slack app. Go to https://api.slack.com/apps and click on Create New App.
Choose From scratch, specify a name for the app and the Slack workspace that hosts the Slack channels you want to send notifications to.
Configure the app icon and description. You can use whatever name, description and icon you would like, but it makes sense for them to refer to SquaredUp so that users can clearly see where the notifications are originating from.
Select Add features and functionality and then choose the Permissions option.
Configure the chat:write permission to Send messages as @squaredup_alerts.
Configure the chat:write.public permission to Send messages to channels.
Click Install to Workspace.
You should now be given a token.
Now use the token to configure the destination in SquaredUp:
In SquaredUp browse to Settings and then click Notifications.
Click Add Destination and then select the destination where the notifications should be sent to from the list of integrations.
Display Name:
Enter a name for your destination. This helps you to identify this destination in the list of your destinations.
Token:
Paste the API token in here.
You can use the same token to configure multiple SquaredUp destinations, each targeting a different Slack channel.
Slack channel:
Enter the destination Slack channel for messages to be delivered to.
You can specify public or private Slack channels, but for private channels the Slack app you created must be added to the Slack channel (type
/invite
in the Slack channel).Test:
Use the Test button to send a test notification and check that it is working as expected.
In Slack, when you click the View button in the notification you may get a warning triangle beside it. To fix this, add
https://api.squaredup.com/api/slack_interaction
as the Interaction URL.
Slack Webhook
You will need to create a Slack app. Go to https://api.slack.com/apps and click on Create New App.
Choose From scratch, specify a name for the app and the Slack workspace that hosts the Slack channels you want to send notifications to.
Configure the app icon and description. You can use whatever name, description and icon you would like, but it makes sense for them to refer to SquaredUp so that users can clearly see where the notifications are originating from.
Go to Incoming Webhooks and enable the Activate Incoming Webhooks option.
Click Add new Webhook to Workspace and choose the Slack channel you want to target.
Copy the URL.
Now use the webhook URL to configure the destination in SquaredUp:
In SquaredUp browse to Settings and then click Notifications.
Click Add Destination and then select the destination where the notifications should be sent to from the list of integrations.
Display Name:
Enter a name for your destination. This helps you to identify this destination in the list of your destinations.
URL:
Paste the webhook URL to configure the destination in SquaredUp.
Test:
Use the Test button to send a test notification and check that it is working as expected.
In Slack, when you click the View button in the notification you may get a warning triangle beside it. To fix this, add
https://api.squaredup.com/api/slack_interaction
as the Interaction URL.

No configuration is required within ServiceNow. However, you may want to create a specific user within ServiceNow to use with the SquaredUp destination. The user will appear as the caller on ServiceNow incidents that are created by SquaredUp. The user will need permission to create and add comments to incidents. Permission to change the state of incidents (e.g. mark as resolved) is not required.
Configure the destination in SquaredUp:
In SquaredUp browse to Settings and then click Notifications.
Click Add Destination and then select the destination where the notifications should be sent to from the list of integrations.
Display Name:
Enter a name for your destination. This helps you to identify this destination in the list of your destinations.
Username:
Enter your ServiceNow username.
Password:
Enter your ServiceNow password.
URL:
Enter the URL of your ServiceNow instance.
Test:
Use the Test button to send a test notification and check that it is working as expected.

This option allows any webhook (HTTP POST endpoint) to be used to send notifications.
An example would be to use a third-party service like https://apify.com/ to send an email.
The JSON body of the webhook request is totally customizable, using inserts to specify elements of the notification – including the name of the monitored entity (e.g. SquaredUp Workspace name), the previous and new health states, and a link back to the SquaredUp app.
This is an example of the JSON body:
{
"text": "{{stateSymbol}} {{name}} changed from {{oldState}} to {{newState}}.",
"link": "{{link}}"
}
This is just an example, and will need to be edited to match the requirements of the particular webhook being used. For example, this JSON is in the structure required for sending emails through apify.com:
{
"subject": "{{stateSymbol}} {{name}} has changed from {{oldState}} to {{newState}}.",
"html": "Hi there t<p>{{stateSymbol}} The health of <b><a href='{{link}}'>{{name}}</a></b> has changed from <b>{{oldState}}</b> to <b>{{newState}}</b>.<p style='color:blue;font-size:0.9em''><em>Brought to you by SquaredUp Alerts™</em>",
"to": "sue.bloggs@squaredup.com"
}
The SquaredUp destination configuration requires the webhook URL and JSON:
In SquaredUp browse to Settings and then click Notifications.
Click Add Destination and then select the destination where the notifications should be sent to from the list of integrations.
Display Name:
Enter a name for your destination. This helps you to identify this destination in the list of your destinations.
URL:
Paste the webhook URL to configure the destination in SquaredUp.
Body:
Enter the JSON body for the channel.
Test:
Use the Test button to send a test notification and check that it is working as expected.
Setting notification rules
You can create notification rules that specify which state changes should trigger a notification to a destination. Notification rules are created on the Monitors page. Notification rules are made up of two parts:
Trigger – the list of entities (e.g. tile monitors) whose health state change can trigger a notification to a selected destination.
Integration – the supported list of endpoints upon which a destination is configured.
To configure the notification rule in SquaredUp:
Browse to Monitors, and then select Add notification rule.
Select the Trigger for your notification. By default, this is set to All monitors in this workspace. Click on the Trigger to change it, available options are:
This workspace state only – notify when the workspace changes health state.
All monitors in this workspace – notify when any monitor within the workspace changes health state. The notification message will include details of the monitor that has changed state, as well as details of the state change.
Selected monitors in this workspace – notify when specific monitors within the workspace change health state. Functions the same as All monitors in this workspace, but allows you to only trigger on a subset. For example, only on database monitors.
Click Save.
Select the integration that you want to use from the list.
You will see a list of all destinations that have been added for the selected integration. If your desired destination is not listed, select + Add destination. See Adding a destination.
Once you have added the destination, click Save.
Saved notification rules are displayed in a table on the Monitors page. The table shows the Status, Trigger and Destination for each notification rule in the selected workspace.
You can create as many notification rules for each workspace as you like.
A notification rule is listed as either Active or Disabled. A notification rule is Disabled if the destination is paused or deleted via the Settings > Notification page.
While it won’t be listed as disabled, a notification rule will also cease to function if it has been set to trigger when monitors change health state but the workspace no longer contains any monitors (or the specific monitors the rule was monitoring are deleted).
Comments
0 comments
Please sign in to leave a comment.