Events

The following table shows the properties of a generic event. These properties are included in all events:

PropertyTypeDescription
idLong (64-bit integer)A unique numeric identifier of the event. If multiple events with same id are received (for example, due to transmission errors), these should be treated as duplicates by the receiver.
timestampTimestamp (UTC)Date/time when this event occurred.
event_typeJSON objectType of the event (see Event type object).
descriptionStringHuman readable description of the event
event_severityJSON objectSeverity of the event (see Event severity object).
alertBooleanEvent is a candidate to be alerted to a user.
event_sourceJSON objectSource of the event (see Event source object).
organisationJSON objectOrganization associated with the event (see Organization object).
userObjectUser details (see User object).
endpointJSON objectDevice details (see Endpoint object).
simJSON objectSIM details (see SIM object).
imsiJSON objectIMSI details of that SIM (see IMSI object). In the case of multi-IMSI configuration, events only show the most recently active IMSI.
detailObjectOptional additional information (see Detail object).

Depending on the event type, some properties don’t apply. For example, network-related events (for example, a device connected to the network) contain endpoint, SIM, and IMSI data. The detail object have the mobile network operator (MNO) details but won’t contain user data. Meanwhile, events affecting a user (for example, authentication issues) contain user and trusted device data but no network-related data.

Example - SIM data available:

1"sim": {"sim_id" : "..."}

Example - SIM data not available:

1 "sim": null

Event type object

PropertyTypeDescription
idIntegerUnique identifier of the event type.
descriptionStringDescription of the event type.

The following table describes currently available event types (event_type):

IDDescription
0Generic
1Update location
2Update GPRS location
3Create PDP Context
4Update PDP Context
5Delete PDP Context
6User authentication failed
7Application authentication failed
8SIM activation
9SIM suspension
10SIM deletion
11Endpoint blocked
12Organisation blocked
13Support Access
14Multi-factor Authentication
15Purge location
16Purge GPRS location
17Self-Signup
18Quota threshold reached
19Quota used up
20SMS quota threshold reached
21SMS quota used up
22CloudConnect TGW Resource Share created
23CloudConnect TGW available
24CloudConnect VPN breakout available
25CloudConnect TGW breakout terminated
26CloudConnect VPN breakout terminated
27CloudConnect Connection State Changed
28OpenVPN connect
29OpenVPN disconnect
30OpenVPN authentication
31Organisation updated
32Billing configuration updated
33Platform package updated
34Data plan updated
35Payment
36User invited
37Password reset requested
38Order submitted
39Order updated
40User verification requested
41User verified
42Endpoint enabled
43Endpoint disabled
44SIM issued
45SIM factory test
46User deleted
47User federation activated
48SIM registration
49Device offline
50SIM Released
51SIM Assigned
52Data quota enabled
53Data quota disabled
54SMS quota enabled
55SMS quota disabled
56Data quota assigned
57Data quota deleted
58SMS quota assigned
59SMS quota deleted
60Data quota expired
61SMS quota expired
62Default inclusive volume updated
63Monthly order limit threshold reached
64Monthly order limit reached
65Endpoint data traffic limit warning
66SMS MO P2P limit reached
67User switched workspaces
68Reset connectivity
69SIM migration
70Endpoint limit extension

Event history is stored for 30 days.

Event severity object

PropertyTypeDescription
idIntegerUnique identifier of the event severity.
descriptionStringDescription of the event severity.

The following table describes currently available event severities (event_severity):

IDDescription
0Info
1Warn
2Critical

Event source object

PropertyTypeDescription
idIntegerUnique identifier of the event source.
descriptionStringDescription of the event source.

The following table describes currently available event sources (event_source):

IDDescription
0Network
1Policy Control
2API

Organization object

PropertyTypeDescription
idIntegerUnique identifier of the organization.
nameStringName of the organization.

User object

PropertyTypeDescription
idIntegerUnique identifier of the user.
usernameStringUsername (for example, email address).
nameStringActual name of the user.

Endpoint object

PropertyTypeDescription
idIntegerUnique identifier of the device.
nameStringConfigured name of the device.
ip_addressStringIP address assigned to the device.
tagsStringTags assigned to the device.
imeiString16-digit long code indicating the International Mobile Equipment Identity - Software Version.
Differs from a standard IMEI in that the last two numbers identify the software/firmware version.

SIM object

PropertyTypeDescription
iccidStringIntegrated circuit card identifier without the final Luhn checksum digit
msisdnStringMobile Station International Subscriber Directory Number (MSISDN).
production_dateTimestamp (UTC)Date and time the SIM chip was produced.
idIntegerUnique identifier of the SIM.

IMSI object

PropertyTypeDescription
idIntegerUnique identifier of the IMSI.
imsiStringInternational Mobile Subscriber Identity (IMSI).
import_dateTimestamp (UTC)Date and time the IMSI was provisioned.

Detail object

Some events may contain additional data added as a nested object called detail. This object includes specific information depending on the event type, event source, and event severity (for example, the country, details about CloudConnect, trusted device data, etc.).

Events with event type Network (id = 0) may contain detailed information about the mobile network operator (MNO):

PropertyTypeDescription
idIntegerUnique identifier of the MNO.
nameStringName of the MNO.
countryJSON objectCountry of the MNO (see Country object).
pdp_contextJSON objectPDP context details (see PDP context object).
volumeJSON objectVolume consumed in a PDP context (see Volume object).
tapcodeJSON arrayList of the MNO tap codes (see Tap code array).
mncJSON arrayList of mobile network codes (MNC) of the MNO (see MNC array).
session_idStringSession UUID for correlating PDP context events and usage record objects.

Events with event type API (id = 2) may contain information from the API.

The following table shows examples:

PropertyTypeDescription
trusted_deviceJSON objectTrusted device of the user (see Trusted device object).
support_usernameStringUsername of the support user.
support_user_orgJSON objectOrganization of the support user (see Organization object).
target_usernameStringUsername of the target user.

PDP context object

The PDP context is a data connection that allows the device to transmit IP data over the network. The PDP context object contains information about the devices’ connection:

PropertyTypeDescription
pdp_context_idIntegerUnique identifier of this PDP context.
tariff_profile_idIntegerUnique identifier of the tariff profile assigned to the device.
tariff_idIntegerUnique identifier of the tariff used by the device.
ratezone_idIntegerUnique identifier of the coverage area used by the device.
operator_idIntegerUnique identifier of the operator used by the device.
sacIntegerService Area Code (SAC).
racIntegerRouting Area Code (RAC).
regionStringRegion where the data plane is located.
rat_typeIntegerRadio Access Type (RAT). Corresponding IDs listed below.
nsapiIntegerNetwork Service Access Point Identifier (NSAPI).
mccStringMobile Country Code (MCC).
mncStringMobile Network Code (MNC).
lacIntegerLocation Area Code (LAC).
ggsn_control_plane_ip_addressStringIP address of the GGSN/PGW control plane.
ggsn_data_plane_ip_addressStringIP address of the GGSN/PGW data plane.
sgsn_control_plane_ip_addressStringIP address of the SGSN/SGW control plane.
sgsn_data_plane_ip_addressStringIP address of the SGSN/SGW data plane.
breakout_ipStringIP address used for Internet breakout.
ue_ip_addressStringIP address assigned to the device.
imeisvStringInternational Mobile Equipment Identity - Software Version (IMEISV).
gtp_versionStringGPRS Tunnelling Protocol (GTP) version. This value is either 1 or 2.
tunnel_createdTimestamp (UTC)Date and time the PDP context was created.
ciIntegerCell Identification (CI).
apnStringAccess Point Name (APN).
tx_teid_control_planeIntegerTunnel Endpoint IDentifier (TEID) of the receiving control plane.
tx_teid_data_planeIntegerTunnel Endpoint IDentifier (TEID) of the receiving data plane.
rx_teidIntegerTunnel Endpoint IDentifier (TEID) of the sending entity.
imsiStringInternational Mobile Subscriber Identity (IMSI). The unique number identifying the active IMSI of the SIM.

Radio Access Type (RAT) IDs correspond to the following values:

IDValue
13G
22G
3WLAN
4GAN
5HSPA+
64G
8NB-IoT
9LTE-M
105G

Country object

PropertyTypeDescription
idIntegerUnique identifier of the country.
nameStringName of country.
country_codeStringNumeric country code.
mccStringMobile Country Code (MCC).
iso_codeStringISO code.

Volume object

PropertyTypeDescription
volume.rxDecimal(14,6) (up to 6 decimal places)Downstream volume in MB.
volume.txDecimal(14,6) (up to 6 decimal places)Upstream volume in MB.
volume.totalDecimal(14,6) (up to 6 decimal places)Total volume.

Tap code array

PropertyTypeDescription
idIntegerUnique identifier of this tap code.
tapcodeStringTap code assigned to the mobile network operator (MNO).

MNC array

PropertyTypeDescription
idIntegerUnique identifier of the mobile network code (MNC).
mncStringMNC assigned to the mobile network operator (MNO).

Trusted device object

PropertyTypeDescription
idIntegerUnique identifier of the trusted device.
operating_systemStringOperating system of the trusted device.
browserStringBrowser of the trusted device.
activation_dateTimestamp (UTC)Activation date of the trusted device.

Example event

Sample event showing PDP context deletion:
For more examples, see the API specification for /api/v1/event.

1[
2 {
3 "timestamp": "2015-07-16 12:07:09",
4 "alert": true,
5 "description": "PDP Context deleted.",
6 "id": 69535,
7 "event_type":{
8 "description": "Delete PDP Context",
9 "id": 4
10 },
11 "event_source": {
12 "name": "Network",
13 "id": 0
14 },
15 "event_severity": {
16 "description": "INFO",
17 "id": 0
18 },
19 "organisation": {
20 "name": "Organisation_Name",
21 "id": 2
22 },
23 "endpoint": {
24 "name": "Monitoring201",
25 "tags": "Monitoring",
26 "ip_address": "10.199.6.39",
27 "imei": null,
28 "id": 69
29 },
30 "sim": {
31 "iccid": "8988317000000000100",
32 "production_date": "2014-12-17 13:26:13",
33 "id": 110
34 },
35 "imsi": {
36 "imsi": "901430000000114",
37 "import_date": "2014-12-17 13:26:08",
38 "id": 110
39 }
40 }
41]

Compatibility notes

The Event Bus is under active development.

It is regularly updated for performance and quality improvements so that users of the platform may gain rich insights into event data when using the Event API or the Data Streamer. Users who have built custom integrations should expect that additional data may be added in the future. Mature and tested libraries designed for parsing or reading JSON should be used for custom integrations to ensure compatibility.

Event data properties

Data types are referred to in the following sections to assist with integration or database schemas. They should be interpreted as follows:

TypeDescription
INTEGERAn integer value usually used for entity IDs, won’t exceed 32-bit values.
LONG (64 bit integer)For event IDs, a long value should be expected.
BOOLEANtrue or false
STRINGA string value enclosed in " " double quotation characters.
DECIMAL(14,6)Used for data volume measurements (volume.total, volume.tx, volume.rx) with 6 decimal places.
DECIMAL(14,10)Cost calculation (cost property) may have up to 10 decimal places.
TIMESTAMPTimestamp property in UTC enclosed in " double quotation characters.