Skip to main content

​
Event types and tags

Events are generated when specific actions happen in your fleet, and are tracked using Event tags that are attached to each event. Those event tags define what the event was, and which SIMs it happened for. System-generated event tags begin and end with underscores, for example _DATALIMIT_ or _DEVICE_123456_, and are reserved for system use. The following event types can be monitored and alerted on: Some legacy event tags may still be present in old events such as _SOCKETAPI_, _JSONSTRING_, _SIMPLESTRING_, _SMS_, _SMSOVERIP_, _RESTAPI_, but are no longer supported.

​
Generic event tags

Each event has tags applied that give additional context about which SIMs were affected by the event. These tags are used to identify which SIMs an event was created for. You can create alerts using these event tags to receive notifications for specific SIMs or groups of tagged SIMs that you want to monitor. Only one of these identifying tags can be added to an alert, however, so if you want to monitor multiple SIMs with one alert then you should tag those SIMs and create an alert that monitors that tag (e.g. _TAG_123456_).

​
Event message fields

Each event also has a default message that is sent with the event to notification recipients. The default message body and content includes the following default fields:

​
Field reference

  • received: ISO8601-formatted UTC timestamp when the event was received by the Hologram Cloud.
  • tags: Array of topics that the message belongs to.
  • device.name: Human-readable name of the device, as specified in the Hologram Dashboard.
  • device.id: Integer device ID.
  • data: Base64-encoded representation of the data payload.
  • authtype: Method by which the message sender authenticated with the Hologram Cloud.
  • errorcode: 0 for messages processed successfully.
  • source: Source ID from the credentials used to send the event. Some data sources use a different authentication method so this field may not always be present.

​
Referencing field contents

You can reference the contents of the default message fields in your alert notification messages using variables, as outlined in the Event variables in alerts guide. The data field is base64-encoded. If the message body is a string or JSON object, the decoded content can be referenced using <<decdata>>.