Security events
Eventing is the most essential concept in any security system. Events are data records expressing an occurrence and its context. For example, the occurrence may be the presence of an object in video or the press of a button, and the context may be the data describing that object or the press of that button.
In YourSixOS, events are emitted by several resource types; virtual and physical. Examples of physical resources include devices
and barriers
. Examples of virtual resources include alarm groups
and sites
.
Each event-emitting resource type has it's own topic, and each event type has its own code. An example is the device:disconnected
event; it's emitted on the device topic, and the event code is disconnected. See the event catalog for more information on available topics and event types.
Events are utilized in three ways:
Logs: Events can be logged, meaning that they're indexed and stored in the cloud. After they've been logged, they can be viewed and searched in multiple ways.
Notifications: Events can be used to trigger notifications. A notification is, as the name suggests, the propagation of an event to a recipient. A recipient can be a user, a shared email inbox or a central station.
Terminology
Occurrence
An occurrence is the capture of a statement of fact during the operation of a security system. For example, an occurrence can be the press of an button input peripheral.
Event
An event is the data record expressing an occurrence and its context. Events are routed from the event producer, on a topic matching the event producers entity type, to the utilizing consumers: logs and notifications.
A single occurrence may result in more than one event.
Topic
Topics are categories of events. Categorization is needed as different event-producing resources types hold different attributes.
For example; all events on the device
topic carry information about the device that emitted the event and that device's parent site. The device
events also include information about their parent alarm group if the device is part of one. The events emitted on the alarmgroup
topic carry information about that alarm group, and the site it belongs to. An alarmgroup
event does not carry information about a device, because such information does not apply as devices are part of alarm groups and not vice versa. In other words, an event from an inner layered resource will carry information about its surrounding resources.
Pipeline flow and context diagram
The diagram below depicts how events flow from various virtual and physical resources into their respective topics. On the topics, utilization rules are used to subscribe to specific set of events matching certain criteria. From the configured utilization rules the events are either forwarded as notifications or logged
As the diagram depicts, eventing is an organization-wide concept that is not limited to a particular site.