New question #231930 on Graphite: https://answers.launchpad.net/graphite/+question/231930
I have a setup where I aggregate metrics from multiple hosts. I use carbon aggregator (over UDP) for this, which passes the aggregated metrics to carbon-cache. Here's the relevant part of carbon.conf [cache] LINE_RECEIVER_INTERFACE = 0.0.0.0 LINE_RECEIVER_PORT = 2003 ENABLE_UDP_LISTENER = False UDP_RECEIVER_INTERFACE = 0.0.0.0 UDP_RECEIVER_PORT = 2003 PICKLE_RECEIVER_INTERFACE = 0.0.0.0 PICKLE_RECEIVER_PORT = 2004 [aggregator] LINE_RECEIVER_INTERFACE = 0.0.0.0 LINE_RECEIVER_PORT = 2023 ENABLE_UDP_LISTENER = True UDP_RECEIVER_INTERFACE = 0.0.0.0 UDP_RECEIVER_PORT = 2023 PICKLE_RECEIVER_INTERFACE = 0.0.0.0 PICKLE_RECEIVER_PORT = 2024 DESTINATIONS = 127.0.0.1:2004 The aggregation rules are defined in aggregation-rules.conf. Now this setup works perfectly fine when I test locally (carbon cache and agg both running on machine A, clients running on machines B and C talking to the aggregator port over UDP). It does not work when I run it on EC2 - no data is aggregated, no data from individual hosts is logged. I've gone over the usual possible EC2 problems checklist that's applicable in such a situation (ports are open etc). After some digging around (looking at the aggregator logs and starting it in debug mode) it looks like data is reaching the aggregator over UDP, but not being passed to the carbon cache. The carbon cache by itself is logging data when it's sent directly to it. Is there any other way to debug this? -- You received this question notification because you are a member of graphite-dev, which is an answer contact for Graphite. _______________________________________________ Mailing list: https://launchpad.net/~graphite-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~graphite-dev More help : https://help.launchpad.net/ListHelp
