You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

In opEvents 3.3.0, we have introduced 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


Apache Config Changes

HTTPS Realtime Events

If you are using opEvents with https there are a few changes needed to proxy websockets to the opEvents web-server.

You will need to enable proxy_wstunnel and modify the OMK provided Apache virtual host.

Debian

If you are running a debian based linux os please enable these apache modules

a2enmod proxy
a2enmod proxy_http
a2enmod proxy_wstunnel

CentOS

Edit /etc/httpd/conf.modules.d/00-proxy.conf

All modules related to proxying websockets are listed in this configuration file, please uncomment:


LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_wstunnel modules/mod_proxy_wstunnel.so


Then restart Apache

sudo systemctl restart httpd


Proxy the webscocket

Locate the Opmantek Apach2 virtual host in /etc/apache2/conf-enabled/04omk-proxy.conf

We need to tell the omk server application the connection is being proxied and the client has connected over https, Find  RequestHeader and change from 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.


  • No labels