| Warning |
|---|
Advanced level feature |
...
: skills with Apache configuration and SSL are required. See the 'Current Issues' section below for details of problems you may encounter if you enable this feature. |
| Table of Contents |
|---|
In opEvents 3.3.0, we have introduced realtime events to push updates as they happen to the GUI.
...
Sometimes, the real time updates cannot be continued, for example if you reverse the sort order of the Date column, so the following is displayed:
Currently Supported Screens
- Current Events
- Events
Checking Redis Status
Under Help → Redis Info you will find debug information about the configured Redis Instance
Redis Issues
For any reason the opEvents log or the Redis status is showing an error please see our page on debugging Redis Redis and Opmantek Applications
Apache Config Changes
HTTPS Realtime Events
When connecting over ssl you will need the web-socket connect to also be secured as the browser cannot run mixed content, secured page and unsecured socket connection. We can use Apache and the optional module proxy_wstunnel to terminate the secured connection and then proxy the connection to the OMKD web server.
The minimum supported Apache Version is 2.4.6, We recommend you use a virtual host and the provided Apache configuration 04omk-proxy.conf under Redhat: /etc/httpd/conf.d/04omk-proxy.conf Debian: /etc/httpd/conf-enabled/04omk-proxy.conf is not currently setup for virtual hosts. Removing the provided 04omk-proxy.conf requires you have basic understanding on editing Apache config. NOTE: Re-installing, or upgrading opEvents will restore this file, so it will need to be removed once again after a re-install.
Debian 9
Enable proxy_wstunnel
Enable these modules to support proxying of the websockets.
...
| Code Block |
|---|
sudo systemctl restart apache2 |
Enable proxy_wstunnel
Next you will need to edit /etc/httpd/conf-enabled/04omk-proxy.conf
...
| Code Block |
|---|
sudo systemctl restart apache2 |
RedHat 7 & Centos 7
yum install mod_ssl
Enable proxy_wstunnel
Edit /etc/httpd/conf.modules.d/00-proxy.conf
...
| Code Block |
|---|
sudo systemctl restart httpd |
Debugging Web Socket connections
If you see this error it means the browser cannot connect to the webserver, at this current point you will need to use the Browsers developments tools to access the Javascript Console
...
| Code Block |
|---|
httpd -t -D DUMP_MODULES | grep proxy_wstunnel_module |
Current Issues
The following are known issues encountered when enabling this feature and will be addressed in a future release:
- 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.
...
- Node Context Links are not rendered with realtime events
...
- .
- Search form on main opEvents page does not work.
See Also
Events Pane in the Node View - enabling websocket when using SSL or TLS
...