v0.1.17
Two major new features in this release:
1) More data in healthcheck policy to help keep track of OPA state
#163: Updated the healthcheck policy to add more data about the current synchronization state of OPAL. The new data format is described in the original issue (#154).
2) Add broadcaster keepalive task
#177: Add broadcaster keepalive task to prevent broadcast backbone from closing the session
We have seen a behavior in our demo environment - where Postgres closes a db session used for broadcaster notifications after no messages were broadcasted for several days.
We are adding a safeguard here (a keepalive task) so that if in a live environment there is no traffic for a long period of time - the session will be kept alive due to the keepalive messages triggering a NOTIFY event, which in turn will also keep the LISTEN sessions alive due to traffic going through.
3) Added OPAL server statistics tracking about connected clients and topics
OPAL server can now keep track of connected clients and display a statistics API.
The feature was suggested in #155 and was added in #169
Check out this docker compose config on how to turn the statistics feature. The new statistics endpoint is https://opalserver.com/statistics
.
Thanks @obsd for these excellent new features and thanks @hongbo-miao for opening the issues and helping us spec these features!