In opEvents 3.3.0 We have introduction realtime events to push updates as they happen to the GUI.
Currently this is an opt in feature and requires setting opevents_realtime_gui to true
When a new event is created, either after parsing or via create event the event details are pushed onto a queue.
Updates to the event as it passes through the EventAction pipeline and the key or keys "priority" "acknowledged" "action_checked" "notes" "status" changes, these updates will be pushed into the queue.
Currently Supported Screens
Current Events
Events
Checking Redis Status
Under Help → Redis Info you will find debug information about the configured Redis Instance
HTTPS Realtime Events
Find and change http to https
RequestHeader set X-Forwarded-Proto "https"
Above <Location "/omk"> add the following line, if you are using other languages please change "en" to your specified language.
ProxyPass "/en/omk/opEvents/ws/events" ws://localhost:8042/en/omk/opEvents/ws/events
Current Issues
Event partial updates over websockets eg {id:abc, acknowledged:1} have no group check, meaning if you have a user with only group access of "DataCenter" their browsers websocket would receive partial updates from events their group permission would not allow access to. As the users browsers doesn't have the original event the partial update will not be shown to the user. This is planned to be fixed in the next release.
Node Context Links are not rendered with realtime events, This is planned to be fixed in the next release.