The emnify system generates several types of events. These events allow you to track notable system occurrences based on behavior and provide information about lifecycle transitions and configuration changes.
Event history is stored for 30 days.
Some common use cases for events on emnify include:
Each event is represented by an object based on the generic Event Object and its associated properties.
Depending on the event type, some generic properties may not apply, and some events may have additional custom fields to provide information about what happened.
For an overview of the specific events generated by our platform, see Event types.
Events are distinguished by three severity levels:
Find more information in the API reference.
Every event is triggered by one of three available event sources:
Any events triggered in the emnify Portal will show API as the event source, because the Portal is an interface that uses the API under the hood.
Find more information in the API reference.
Device status management events include information about who performed the action. When viewing these events in the Portal, click on an event row to see the Action performed by field, which displays the user’s name, email, and user ID.
User information is available for actions performed through the Portal or API with user credentials. Actions authenticated with application tokens don’t include user details.
There are three main ways you can access and trigger events:
More information on these systems and how they compare is available on the Work with events page.