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
We're logging lots of different sized events - some tiny, some huge. We ran into an issue with Seq refusing to accept a large batch of events which occurred because lots of large events were submitted in a single batch.
Rather than reducing the batch count, it would be great to have the the option to also batch by request size. This option would allow many smaller events to be sent at once (say 1000 per batch) and larger events to be sent in smaller batches.
Event with the changes in dev branch to drop large events, it's possible individual events may not exceed _eventBodyLimitBytes.Value but when batched will exceed's Seq's Raw Event Payload Limit.
By batching based on request size, the likelihood of events being dropped would be much lower.
The text was updated successfully, but these errors were encountered:
We're logging lots of different sized events - some tiny, some huge. We ran into an issue with Seq refusing to accept a large batch of events which occurred because lots of large events were submitted in a single batch.
Rather than reducing the batch count, it would be great to have the the option to also batch by request size. This option would allow many smaller events to be sent at once (say 1000 per batch) and larger events to be sent in smaller batches.
Event with the changes in dev branch to drop large events, it's possible individual events may not exceed
_eventBodyLimitBytes.Value
but when batched will exceed's Seq's Raw Event Payload Limit.By batching based on request size, the likelihood of events being dropped would be much lower.
The text was updated successfully, but these errors were encountered: