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
instead, creating various bogus databases in storage engine (graphite)
Looks like there's correlation between how many lines are received at UDP:8125 and frequency of the above behavior (the faster data are sent, the more often concatenation happens).
Is it possible to prevent the above from happening?
The text was updated successfully, but these errors were encountered:
I realise I'm asking you to cast your mind back well over a year, but did this work for you @stayen? With the recent revival of this project I'm wondering if this is still something we should be looking at.
I noticed that statsd at times concatenates data received at UDP:8125 (default port) before processing it. I.e., if I send sequence of data like
statsd may process single concatenated line
example.filesInFolder:1|cexample.listFolderTR:4|msexample.httpSendTR:8|msexample.httpSend:1|c
instead, creating various bogus databases in storage engine (graphite)
Looks like there's correlation between how many lines are received at UDP:8125 and frequency of the above behavior (the faster data are sent, the more often concatenation happens).
Is it possible to prevent the above from happening?
The text was updated successfully, but these errors were encountered: