There's no metrics exported for online and offline sessions in KC currently and that is pretty needed by business
What
Two gauges were added for onlineSessionCount and offlineSessionCount. Updates are done when LOGIN or LOGOUT events are catch and only for client where event happened, which reduces load on the system
Why
There's already one PR, which does the same, but from my point of view capturing of sessions is done incorrectly there and will definitely add extra load on a server as metrics are pushed on each event.
How
When LOGIN, CLIENT_LOGIN or LOGOUT event is catch we retrieve info of event's client sessions and push out metrics.
Verification Steps
Login with several customers into KC
Observe new metrics on /realms/{realm}/metrics endpoint
Logout with some customers from KC
Observe updated metrics on /realms/{realm}/metrics endpoint
Checklist:
[x] Code has been tested locally by PR requester
[x] New test cases are added
[ ] Changes have been successfully verified by another team member
Motivation
There's no metrics exported for online and offline sessions in KC currently and that is pretty needed by business
What
Two gauges were added for onlineSessionCount and offlineSessionCount. Updates are done when LOGIN or LOGOUT events are catch and only for client where event happened, which reduces load on the system
Why
There's already one PR, which does the same, but from my point of view capturing of sessions is done incorrectly there and will definitely add extra load on a server as metrics are pushed on each event.
How
When LOGIN, CLIENT_LOGIN or LOGOUT event is catch we retrieve info of event's client sessions and push out metrics.
Verification Steps
Checklist:
Progress
Additional Notes
-