Monitor settings & groups
Edit, pause, clone and delete monitors, organise them with groups and tags, run bulk actions, and set notification preferences and quiet hours.
This page covers how you manage monitors once they exist: editing settings, pausing, cloning and deleting, organising monitors with groups and tags, bulk actions, and the workspace-wide settings on the On-call & escalation page that apply to every monitor.
For the settings of each monitor type, see the type's own page, for example HTTP & keyword monitors or Heartbeat & cron monitors.
Edit a monitor#
Open the editor in either of two ways:
- From the monitor list (Monitors): open the monitor's ⋮ menu and choose Edit monitor.
- From the monitor's page: click Edit.
The editor shows every option the New monitor dialog has for that type:
| Section | What you can change |
|---|---|
| Name | Up to 255 characters |
| Target | URL, host, port, cron expression and so on, depending on the type |
| Check interval | From your plan's fastest interval up to 15 minutes. Not shown for heartbeat monitors |
| Group | The monitor's group, or No group |
| Escalation policy | Default policy or one of your escalation policies. Called Who gets alerted in the Add new monitor dialog |
| Tags | Up to 20 tags |
| Request and validation / Check options | Type-specific advanced settings: timeouts, thresholds, assertions, and Detection timing |
| Alert on these HTTP errors | HTTP and API monitors only. Unticked error classes still mark the check failed, but don't send notifications |
Click Save changes. If you close the editor with unsaved edits, SutramX asks before discarding them.
If some saved settings are outside your current plan's limits (for example an interval faster than your plan allows after a downgrade), the editor says which values it adjusted, and saving applies them.
The check locations are changed separately with the Locations button on the monitor's page. See Regions & confirmation.
Alert on these HTTP errors#
For HTTP and API monitors you can choose which kinds of failure send alerts. All are ticked by default.
| Group | Error classes |
|---|---|
| Connection | Connection Refused, Connection Reset, DNS resolution failed, Network unreachable |
| Timeouts | Timeout Connect, Timeout Read, Timeout Total |
| TLS | Ssl Expired, Ssl Hostname Mismatch, Ssl Self Signed, Ssl Revoked, Untrusted certificate chain, Certificate not yet valid |
| Response | Status 4xx, Status 5xx, Status Unexpected, Keyword Not Found, Response Too Large, Invalid Response Body, Response time exceeded |
| Redirects | Redirect Loop, Redirected while redirects are off, Redirect to insecure HTTP |
| Blocking | Blocked by bot protection (WAF), Rate limited (HTTP 429), Target not allowed |
| Our side | Checker error (inconclusive, our side) |
An unticked class still fails the check and can still open an incident, so your history and uptime stay honest. The incident shows its alert was held back by an alert filter.
Monitor actions#
Each monitor's ⋮ menu in the list has:
| Action | What it does |
|---|---|
| Edit monitor | Opens the editor |
| Alert recipients… | Opens the monitor's alert recipients so you can choose who gets alert emails. See How alerting works |
| Maintenance | Opens Maintenance windows |
| Edit tags… | Changes the monitor's tags |
| Status pages… | Shows or removes the monitor on your status pages |
| Clone… | Creates a copy with the same settings. You choose the Name of the copy |
| Move to group… | Moves the monitor to another group, or to No group |
| Pause / Resume | Stops or restarts checks |
| Reset statistics… | Deletes the monitor's history (see below) |
| Delete… | Deletes the monitor |
The monitor's own page also has Run check now (not for heartbeat monitors), Pause / Resume, Edit, and a menu with Send test notification, Alert recipients…, Schedule maintenance…, Reset statistics… and Delete monitor….
Pause and resume#
- A paused monitor runs no checks and sends no alerts. It shows Paused in the dashboard and on status pages.
- Paused time is left out of uptime.
- A paused heartbeat monitor ignores pings.
- Resuming counts against your plan's monitor limit and uses at least your plan's fastest interval. If you resume a monitor whose interval is now faster than your plan allows, the interval is raised to the plan minimum.
If your plan changes and you have more monitors than it allows, SutramX pauses the extra monitors instead of deleting them. Upgrade to resume them.
Reset statistics#
Reset statistics… permanently deletes the monitor's check history, uptime and response-time data, and its incidents. The monitor and its settings stay. This can't be undone.
Delete#
Deleting a monitor removes it, its check history and its incidents. This can't be undone. Export what you need first; see Reports & exports.
Monitor groups#
Groups organise related monitors, for example everything for one client, product or environment. Groups appear as tabs above the monitor list: All, one tab per group, and Ungrouped when some monitors have no group.
Groups are used across SutramX:
- Alert emails that go to everyone responsible for a set of monitors.
- Maintenance windows and quiet hours scoped to whole groups.
- The Recipients page (Alerts → Recipients), which lists monitors by group so you can choose who is notified.
Create a group#
- On Monitors, click New group next to the group tabs.
- Enter a Name (up to 255 characters, unique in the workspace).
- Optionally add Alert emails.
- Click Create group.
You can also create a group while creating a monitor: choose + Create new group… in the Group list.
Group alert emails#
Alert emails get down and recovery alerts for every monitor in the group, in addition to your normal recipients.
- Comma-separated, up to 20 addresses.
- Alerts are only sent to verified addresses. New addresses get a one-time confirmation email; teammates with a verified account email are verified automatically.
- Only the workspace owner can change a group's alert emails. Other members can create and rename groups.
Rename, change or delete a group#
Select the group's tab and click the manage button next to it ("Rename, change alert emails or delete …"). To delete, choose What happens to the monitors:
- Delete group only: monitors keep running and become ungrouped.
- Delete group and N monitors: the monitors, their check history and incidents are permanently deleted.
Either way, the group's alert emails stop receiving group alerts, and the group is removed from any maintenance windows or quiet hours that referenced it.
Move monitors between groups#
Use Move to group… on a single monitor, or select several monitors and use Move to group in the bulk action bar.
Tags#
Tags are free-form labels for filtering and automation, for example production, client-acme or payments.
- Up to 20 tags per monitor, each 1–32 characters.
- Tags are lower-cased. In the dashboard, spaces become hyphens.
- Add tags in the Tags field when creating or editing a monitor, with Edit tags… on one monitor, or with Add tags / Remove tags in bulk.
- Filter the monitor list by tag with Filter by tag, or click a tag on a monitor. The filter is kept in the page address (
/dashboard?tag=payments), so you can bookmark it.
Find monitors#
Above the list you can:
- Search monitors by name, URL or host, type, cron expression or tag.
- Filter by status: All, Up, Down, Degraded, Blocked, Inconclusive, Paused, Pending or Maintenance, with a count for each.
- Filter by tag.
- Sort by Status (down first), Name (A–Z), Uptime (lowest first) or Response time (slowest first).
- Toggle Down first to keep failing monitors at the top whatever the sort.
Bulk actions#
- Tick the monitors you want, or tick Select all on this page.
- Choose an action in the bulk action bar: Pause, Resume, Add tags, Remove tags, Move to group or Delete.
- Click Clear selection when you're done.
Deleting more than one monitor asks you to type DELETE to confirm.
Bulk actions apply to up to 500 monitors at a time. Through the API:
curl -X POST https://api.sutramx.com/monitors/bulk \
-H "Authorization: Bearer $SUTRAMX_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"action": "add_tags",
"ids": ["7c9e6679-7425-40de-944b-e07fc1f90ae7", "1b4e28ba-2fa1-11d2-883f-0016d3cca427"],
"tags": ["production"]
}'action | Extra field |
|---|---|
pause, resume, delete | None |
add_tags, remove_tags | tags (required) |
move_group | group_id (required; null removes the group) |
On-call & escalation settings#
On-call & escalation (in the sidebar under Alerts) holds workspace-wide settings that apply to all monitors. It has these sections:
| Section | What it is for |
|---|---|
| Notification Preferences | Turn kinds of notification on or off for the workspace (below) |
| On-Call Rotation Scheduling | Who is on call when. See Escalation & on-call |
| Escalation Policies | Multi-step alert routing. See Escalation & on-call |
| Quiet Hours & Deployment Windows | Recurring periods when alerts are held back (below) |
| Runbook Automation | Checklists attached to incidents. See Incidents |
| Escalation & Delivery Analytics | How alerts were delivered over a period |
Changes to notification preferences, on-call schedules, escalation policies and quiet hours need the workspace owner. Members can view them.
Notification preferences#
| Switch | Effect when off |
|---|---|
| Monitor Down Alerts | Down alerts are not sent for any monitor. Incidents still open and show the alert was held back by notification preferences |
| Monitor Recovery Alerts | Recovery emails stop. Recovery notices still go to connected channels such as Slack and PagerDuty, so they can close their alerts |
| Weekly Reports | The weekly summary email stops |
| SSL Certificate Expiry | Certificate-expiry emails stop |
| Maintenance Alerts | Maintenance reminder, start and end emails stop. Chat channels still get start and end notices |
Below the switches, Weekly Report Preview and History shows this week's checks, failed checks and incidents, when the last report was sent and when the next one is due.
Quiet hours and deployment windows#
Quiet hours hold back alerts at the same times every day or week, for example overnight for a non-critical service, or during a regular deploy slot. Unlike a maintenance window, monitors don't show Maintenance and uptime is not adjusted.
To create one, fill in Create Suppression Window and click Create Window:
| Field | What it does |
|---|---|
| Window name | For example Night quiet hours |
| Type | Quiet hours or Deployment window. Both hold back alerts; the type is shown on incidents |
| Timezone | Time zone of the start and end times |
| Start time / End time | Daily times. An end before the start runs overnight, for example 22:00 to 06:00. The same start and end covers the whole day |
| Days of week | Leave all unselected to apply every day. For overnight windows, pick the day the window starts |
| Applies to | All monitors, Selected monitors or Selected groups |
While a window is active, down, recovery and escalation notifications for monitors in scope are held back. If a monitor is still down when the window ends, its down alert is sent then. Each window can be Enabled or Disabled, edited or deleted.
Common questions#
Can I change a monitor's type? No. Create a new monitor of the other type, then delete the old one.
Why can't I pick a faster interval? The fastest interval depends on your plan. See Plans & limits.
I changed a group's alert emails and got a permission error. Only the workspace owner can change alert recipients. Ask the owner, or see Team members & roles.
Related
Last updated . Something unclear or missing on this page? Tell us at support@sutramx.com.