Change Details

Since it doesn't look like varnishncsa logging limits (or udp packet size) are going to be fixed any time soon the EL client should not send events that we know are going to come in truncated. At the time of serializing the URL we should count characters and 1) send a console warning 2) Do not send "too long" events.

Since it doesn't look like varnishncsa logging limits (or udp packet size) are going to be fixed any time soon the EL client should not send events that we know are going to come in truncated. At the time of serializing the URL we should count characters and 1) send a console warning 2) Do not send "too long" events. Even when we move the entry point to varnishkafaka (for which limits are different) we should not assume in the clients that events are "unbounded" as they are not, sendBeacon, for example, has a high limit but a limit none the less (I think is 64K)

Since it doesn't look like varnishncsa logging limits (or udp packet size) are going to be fixed any time soon the EL client should not send events that we know are going to come in truncated. At the time of serializing the URL we should count characters and 1) send a console warning 2) Do not send "too long" events. Even when we move the entry point to varnishkafaka (for which limits are different) we should not assume in the clients that events are "unbounded" as they are not, sendBeacon, for example, has a high limit but a limit none the less (I think is 64K)