Uptime Robot Integration Guide
Uptime Robot is an uptime monitoring service. It provides a simple interface for users to quickly set up a ping based monitor for their systems. TaskCall's Uptime Robot integration offers downtime notices to be routed to the correct teams and levels of escalation so they can be addressed immediately.
Pointers
- The integration is between a TaskCall service and Uptime Robot.
- Incidents will automatically resolve in TaskCall when systems being monitored are back up.
- This integration only allows alerts to be received in TaskCall from Uptime Robot.
In TaskCall
- Go to Configurations > Integrations and click New Integration.
- Select the Uptime Robot integration.
- Give the integration a name and configure how incidents will be created. Only the Default Service field is required. The rest are optional.
- Incidents (Optional)
- TaskCall automatically maps incoming payloads with internal attributes to create incidents. However, this can be customized in the Incidents tab. Constant values can be included alongside placeholders to dictate which attributes should map to the Incident Title, Description, Tags, Snapshots and Vendor URL. To insert a placeholder use double curly braces.
For example, if you enter {{ alert.title }} in the Incident Title field, TaskCall will look for an attribute called "title" nested inside another attribute called "alert" in the incoming payload. If the nested attribute exists, its corresponding value will be pulled from the payload and inserted. If the nested attribute does not resolve successfully, TaskCall will fall back to the default mapping.
If you are unsure, please leave the fields empty. TaskCall will use the default mapping to create the incident for you. - Select the Urgency level the incident should be created at.
- Select the option to Group similar alerts together if you would like follow up triggers from the same alert source to be grouped into the same incident. If you leave this option unchecked, then a new incident will be created for every trigger. (This behavior is specific to new triggers; not updates to an alert.)
- Click Next to move on to the Services tab.
- TaskCall automatically maps incoming payloads with internal attributes to create incidents. However, this can be customized in the Incidents tab. Constant values can be included alongside placeholders to dictate which attributes should map to the Incident Title, Description, Tags, Snapshots and Vendor URL. To insert a placeholder use double curly braces.
- Services (Required)
- Select the Default Service incidents should be sent to. To route incidents to different services instead, set Map With Attribute to the attribute to route by using a placeholder. Then, map each value it can take to the service that should receive it.
For example, to route by a region attribute sent in the payload, set Map With Attribute to {{ region }}, then map US to one service and EU to another, and so on.
- Click Next to move on to the Authorization tab.
- Select the Default Service incidents should be sent to. To route incidents to different services instead, set Map With Attribute to the attribute to route by using a placeholder. Then, map each value it can take to the service that should receive it.
- Authorization (Optional)
- The Authorization tab allows a Bearer Token and an IP Allowlist be added if you would like to restrict who is able to send alerts to this integration. If you are unsure, this can be skipped.
- Once done, click Save.
- Copy the Integration Url that is issued for the integration. This will be used to set up the notification in Uptime Robot.
In Uptime Robot
Pricing Plans
This integration requires a webhook. Uptime Robot offers Webhooks only on the Team and Enterprise pricing plans. Hence, although the integration is free to use in TaskCall and is available on all plans, you will need to be on the correct paid plan in Uptime Robot according to their policy.
- Go to Integrations & API > Webhooks. Click the Add button to add a new webhook.
- Paste the integration url you copied over from TaskCall in the Webhook URL field. Select the option to send default variables As POST parameters. Click the edit button next to the POST value. Select the option to Send as JSON (application/json) and paste the following JSON payload in the text field.
{
"monitor_id": "*monitorID*",
"monitor_url": "*monitorURL*",
"monitor_name": "*monitorFriendlyName*",
"alert_type": "*alertType*",
"alert_name": "*alertTypeFriendlyName*",
"alert_details": "*alertDetails*",
"alert_duration": "*alertDuration*",
"alert_datetime": "*alertDateTime*",
"ssl_expiry_date": "*sslExpiryDate*",
"ssl_expiry_days_left": "*sslExpiryDaysLeft*"
}
- Select all the events (Down events, Up events, SSL & Domain expiry) in the Events to notify about section.
- Click Create Integration.
Although you may not be able to name your webhook in Uptime Robot when creating it, you will be able to edit the name to something more meaningful like TaskCall once it is created.
After the webhook gets created, you can connect it to any monitor and receive notifications in TaskCall.