Skip to main content
An alert watches for events in your fleet, such as a SIM reaching its data limit or falling back to another profile, and sends you an email or webhook when one occurs. Every alert has three parts:
  • Alert type: the kind of event to watch for. Each type matches one or more event tags.
  • Scope: every SIM in your organization, one SIM, or every SIM with a specific tag.
  • Notification: an email or a webhook, with message contents you can customize using event variables.
Events are always recorded in Event history, whether or not an alert is set up for them. An alert only adds the notification.

​
How to create an alert

1

Open the Alerts page

Navigate to the Event monitoring section in the main menu and open the Alerts page.To create an alert for a single SIM, you can instead open the SIM’s Alerts tab. The alert starts out limited to that SIM.
2

Choose an alert type

Click Create alert and choose the type of event you want to be notified about. See Alert types below.
3

Name the alert

In Alert details, give the alert a name that will help you recognize it later, like “Canada roaming - Data limit reached”.
4

Set the alert rules

In Alert rules, choose any options for the alert type, such as which messaging events to watch. Then decide whether to limit the alert to a SIM or tag. With Limit to SIM or tag off, the alert is sent for every SIM in your organization.
5

Optionally, tag matching events

In Modify event, turn on Add custom tag to add your own identifier to events this alert matches. See Add a custom tag.
6

Choose how to be notified

In Notification, choose Email or Webhook and fill in the details. See Notification methods.
7

Save the alert

Review the preview at the top of the form, which summarizes the event, scope, and notification, then click Save. Click Back to choose a different alert type.

​
Alert types

Note: Conductor configuration change and the Conductor profile change option appear only for organizations with Conductor.

​
Alert type options

Some alert types let you narrow which events trigger the alert:
Under IMEI to check, choose IMEI change, IMEI TAC change, or both. A TAC change means the SIM is likely in a different model of modem, and is always accompanied by an IMEI change.
Under Profile change type, choose one:
  • Fallback event: the SIM fell back to another profile after losing connectivity, using Outage Protection™.
  • Manual profile change: a user switched the enabled profile.
  • System profile change: a Hologram system process, such as a migration, switched the enabled profile.
  • Conductor profile change: a Conductor configuration switched the enabled profile.
To be notified about more than one type, create an alert for each.
Choose one of Outbound SMS (sent from the SIM), Inbound SMS (sent to the SIM), Inbound SMS delivered, and Inbound message (TCP/UDP sent to the SIM).

​
Limit an alert to a SIM or tag

By default, an alert is sent for every SIM in your organization. Turn on Limit to SIM or tag to narrow it:
  • Add SIM by device ID limits the alert to one SIM. You can find a SIM’s device ID on its Status and Device tabs.
  • Add tag limits the alert to every SIM with that tag when the event occurs.
An alert can be limited to one SIM or one tag. To watch a group of SIMs with one alert, tag them and limit the alert to that tag. Behind the scenes, this adds a _DEVICE_XXX_ or _TAG_XXX_ event tag to the alert, and the alert only triggers for events that carry every tag on it.

​
Add a custom tag

Turn on Add custom tag in Modify event to add your own identifier to events that match the alert, such as a customer or project code. Custom tags can’t begin or end with an underscore, which is reserved for system tags.

​
Notification methods

Every alert sends either an email or a webhook. Both support event variables to customize what’s sent.

​
Email

​
Webhook

See Webhook configuration for header and payload details, and Troubleshooting alerts and webhooks if notifications don’t arrive.

​
Manage existing alerts

All of your organization’s alerts are listed on the Alerts page. Each alert shows its event type, scope, and notification method, and a Status switch to turn it on or off without deleting it. A SIM’s Alerts tab lists the alerts that apply to it, including global alerts and alerts for its tags. Alerts created with older event types that are no longer supported are marked with a warning. See Why does my alert say “No longer supported”?. This includes Socket API events, events with custom tags, heartbeat events, and deprecated notification methods. If your organization uses data limits or data warning thresholds, we recommend creating a global alert for each. These recommendations will show up in both the organization and SIM alerts pages.

About alerts and event monitoring

How alerts work, and the notification methods they support.

Event types and tags

Every event tag, and the fields events contain.

Use variables from events in alerts

Customize email and webhook contents with data from the event.

Forward messages to email with an alert

A step-by-step example.
Limited access: Some functionality in your dashboard is restricted to roles with access.