graphite-dev team mailing list archive

[Sumeet Grover <question242463@xxxxxxxxxxxxxxxxxxxxx>]

New question #242463 on Graphite:
https://answers.launchpad.net/graphite/+question/242463

We have observed the corruption of graphite metric names on our system. E.g. metric1.sub_class2.sub_class3.metric when sent into graphite, is 'splitting' up and we're observing distorted resultant metric hiearchies. E.g.:
- sub_class2.metric
- subc_class3.metric

Etc. 

We have verified that our messages being sent into Graphite, all contain correct metric names. However, so far, we have only identified two potential causes:

1. We observed some processes sending in non-numeric values in messages. E.g.
$message = "metric1.sub_class2.sub_class3.metric HELLO 1390220929"
By looking at Carbon daemon logs, we noticed that these messages were 'ignored' by the daemon. The logs said something like:
"invalid line received from client 127.0.0.1:52608, ignoring"

2. The second potential cause we observed was that during the time when metric names got split up inside Graphite, creating corrupted metric name hierarchies, the system was receiving over 220,000 messages, even though the RAM usage was less than 96MB. 

QUESTION:
- Has anyone else also observed this corruption / splitting up of metric names within Graphite? 

We'd highly appreciate if you have observed the same problem.

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.