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 was archived by the owner on May 6, 2024. It is now read-only.
We are facing a weird situation in which after a while we start seeing corrupted metrics. Let's say we have metrics such as company.prefix.metric-one and company.prefix.metric-two. We typically send multi-metric packets.
After some hours, we get things such as compafix.metric-one, company.pref.metric-two, company.prefix.metric-one-two, etc...
I have checked the network MTU and we made sure that all of our packets do not exceed it. Actually, we didn't have this issue before using statsd-proxy (but we needed to scale and Etsy's statsd-proxy is not as good as this one).
Hi!
We are facing a weird situation in which after a while we start seeing corrupted metrics. Let's say we have metrics such as
company.prefix.metric-oneandcompany.prefix.metric-two. We typically send multi-metric packets.After some hours, we get things such as
compafix.metric-one,company.pref.metric-two,company.prefix.metric-one-two, etc...I have checked the network MTU and we made sure that all of our packets do not exceed it. Actually, we didn't have this issue before using
statsd-proxy(but we needed to scale and Etsy'sstatsd-proxyis not as good as this one).Any ideas of what might be going on?