The event buffer in the UI's events page has a capacity of just 500 messages.
On a normal browsing session, lots of sticky_session_reused and proxy_request_routed events are emitted.
The solution I propose it to have different buffers for the different classes of events, so that info events only push out other info events without hiding errors and warnings (e.g., 500 for info, 500 for warning, 500 for error).
We can think about this and discuss if other alternatives may be applicable.
Let me know what you think @antoncxx, it'd be wonderful to figure this out before deployment so we can have a proper error and warning collection we can use to debug.
P.S.: I'm adding more warning and error events emission in another PR myself, so don't worry about that
The event buffer in the UI's events page has a capacity of just 500 messages.
On a normal browsing session, lots of
sticky_session_reusedandproxy_request_routedevents are emitted.The solution I propose it to have different buffers for the different classes of events, so that info events only push out other info events without hiding errors and warnings (e.g., 500 for info, 500 for warning, 500 for error).
We can think about this and discuss if other alternatives may be applicable.
Let me know what you think @antoncxx, it'd be wonderful to figure this out before deployment so we can have a proper error and warning collection we can use to debug.
P.S.: I'm adding more warning and error events emission in another PR myself, so don't worry about that