You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
Daily Activations - Knowing new_uaid for a session indicates if the uaid is a reconnect or new.
DIU’s - Daily Inactive Users, to know one, I'd need to see that for all the users sessions for a day, there were no messages.
It's possible to get both of these by alternatively logging when a new uaid is issued, and logging 'hello' for a uaid_hash, which would let me group them to see there were no Ack's. That's likely just as efficient, but correlating commands issued per 'session', and other per-session stats would be hard to evaluate. As such, it'd be easier to do analysis on a Session logging statement that had it all.
A side-effect of this is that long-lived connections get a bit.... weird. This shouldn't be that bad for our stats, as the max typical life span of a connection right now is around 50 minutes.
The text was updated successfully, but these errors were encountered:
Logs a summary of session statistics when a client drops its client
connection. Also cleans up several places where the PushState had
its uaid set but not its uaid_obj or uaid_hash.
Closes#448
Logs a summary of session statistics when a client drops its client
connection. Also cleans up several places where the PushState had
its uaid set but not its uaid_obj or uaid_hash.
Closes#448
Logs a summary of session statistics when a client drops its client
connection. Also cleans up several places where the PushState had
its uaid set but not its uaid_obj or uaid_hash.
Closes#448
Logs a summary of session statistics when a client drops its client
connection. Also cleans up several places where the PushState had
its uaid set but not its uaid_obj or uaid_hash.
Closes#448
A new metric statement should be added when the client drops its connection, that logs some session statistics for the user-session.
Example logging message:
This is needed for the following KPI's:
It's possible to get both of these by alternatively logging when a new uaid is issued, and logging 'hello' for a uaid_hash, which would let me group them to see there were no Ack's. That's likely just as efficient, but correlating commands issued per 'session', and other per-session stats would be hard to evaluate. As such, it'd be easier to do analysis on a Session logging statement that had it all.
A side-effect of this is that long-lived connections get a bit.... weird. This shouldn't be that bad for our stats, as the max typical life span of a connection right now is around 50 minutes.
The text was updated successfully, but these errors were encountered: