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 Mar 15, 2021. It is now read-only.
Due to nature of UDP protocol data could be silently dropped if reached specific limits.
As the data/metrics are dropped silently usually we alerted by teams noticing missing metrics.
One idea discussed is to put some ignorable/optional metric indicating the number of bytes or metrics sent over the wire so FFWD agent could detect the loss and emit a metric to be alerted on.
The text was updated successfully, but these errors were encountered:
Well, I wanted more datapoint from teams that are experiencing the problem.I doubt anybody is sending 25MB in the packet. I think the packets drop before reaching UDP max. I noticed, but I am not certain, that anything higher than 2048 bytes is being dropped.
I will look into the issue when I get a chance.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Due to nature of UDP protocol data could be silently dropped if reached specific limits.
As the data/metrics are dropped silently usually we alerted by teams noticing missing metrics.
One idea discussed is to put some ignorable/optional metric indicating the number of bytes or metrics sent over the wire so FFWD agent could detect the loss and emit a metric to be alerted on.
The text was updated successfully, but these errors were encountered: