For creating and managing events, you need to understand the Event Model, Event, and Acknowledgement concepts.

Event Model

An EventModel serves as a template or blueprint modelling the different types of events that might occur on a System or Component.

For example, these can be device warnings, errors, or maintenance events. If an EventModel is configured to be attached to a Component, it may optionally be limited to a specific ComponentModel.

DRIVR understands two types of events: RANGED and SINGLE_POINT.

• RANGED is an EventModel blueprint that contains a time range specified by dedicated "time" and "end time" timestamps.
• SINGLE_POINT is an EventModel which contains a single timestamp.

EventModels have a severity which can be one of ERROR, INFO, SUCCESS, or WARNING.

Event

An Event is an actual instance of an EventModel which is attached to a specific System or Component. Depending on the attached EventModel's type, it has a "start time" and "end time" timestamp or only one specific "time" element.

For example, if a system is unsuccessful to upgrade its software, an event will be sent to DRIVR and a user can then be notified about the issue.

They have a status of ACTIVE or RESOLVED, which is automatically populated depending on the RANGED or SINGLE_POINT event type.

• SINGLE_POINT event types do not have a status set.
• RANGED event types are set from ACTIVE to RESOLVED when they are updated with an "end time" timestamp.

Acknowledging Events

Acknowledging an Event signifies that it has been noticed or addressed. Events support manual acknowledgment, allowing users to track who has seen the event and is actively working to resolve or manage it.