Skip to main content
OpenEye Knowledge Base

Alerts

OpenEye Web Services (OWS) Alerts grant insight into operational events at recorder locations, help ensure recorders are operating properly, and provide valuable business intelligence based on customer or employee activity. Alerts data can be viewed via interactive reports online or configured to notify in real time via email.
Overview

OWS Alerts work by defining Rules for system Events. Each time a recorder loses connection or a sensor is triggered, it is registered as an event in the server software. These events are transmitted to the cloud as part of their lightweight connection to OWS. There, the events are compared against the Alert Rules defined by the user, and, if they meet the conditions of the rule, an Alert is generated. Read more about the differences between Events, Rules and Alerts.

EventThis is defined as dispatches sent from recorders to OWS when a specific action has occurred. OWS will track events and generate an Alert based on the event threshold set in an alert rule.

Rules: Otherwise known as a set of user-defined parameters, will then filter out significant Events from insignificant ones. OWS will generate an alert based on the threshold set for the tracked events. It is crucial to configure Rules correctly to avoid being flooded with unimportant Alerts.

Alert: This is created when an Event or Events meets the parameters outlined in a Rule. If part of the Rule definition includes sending an email, one will be sent to the defined users. If the Rule’s parameters are properly configured, only important Events will be reported.

NotificationsCommunication about Alerts can be set and are received by various methods including Email Alert, Push Alert, and Client Alert.

Active Alerts: A way to display and manage critical alerts generated by OWS. Users can tag any alert rule as an Active Alert. Active Alerts are displayed as a widget seen on every page of OWS and are listed in the new Active Alerts Dashboard. Active Alerts can be managed or cleared directly from the dashboard. Email notifications are labeled as “Active” for easy filtering.

Alert Types
  • Health and Storage Retention Alerts: Health and Storage Retention Alerts help identify when something is affecting the ability of hardware to capture or record video.
  • Motion and Sensor Alerts: Motion Alerts are sent when movement is detected by a camera during a specified time period, and Sensor Alerts are sent when a sensor connected to a recorder is triggered.
  • Analytics and Analytics Queue Alerts: For cameras preconfigured to send analytic events, an alert can be sent based on specifically defined audio or video events within a selected time period.
  • Access Control and Door Access Alerts: An Access Control Alert identifies when there is a trouble event identified with a door. Door Access Alert identifies when an attempt is made to access an area.
  • Intrusion and Intrusion Sensor Alerts: An Intrusion Alert or Intrusion Sensor Alert identifies when a sensor event is received from an intrusion system.
Best Practices
  • All Health Alerts should be deemed active.
  • Mark Automatically include all recorders in this Alert Rule so that any future recorders that are added will be included in the alert.
  • After working through the left-hand menu to create a new rule, work your way back up the menu to check your work.
  • OWS can push alerts directly to third-party central stations.
  • OWS can tie an alert to the state of an Access panel. This gives flexibility to customers with floating closing and opening times.
Best Practices Channel Partners
  • Channel Partners can add alert rules to all accounts at one time in the Accounts/Recorders Tab.
  • Channel Partners should include their internal support team to receive active alerts so they can proactively attend to any issues.
  • Was this article helpful?