Question #246005 on Graphite changed:
https://answers.launchpad.net/graphite/+question/246005
Tim Zehta posted a new comment:
Troubleshooting Graphite can be a bother. Determining where a problem
lies requires verification of the data at all of the points of
communication. The best tool I've found for this is ngrep:
sudo ngrep -lqd any ping tcp dst port 2003
The following one-line command finds ping metrics submitted over TCP to
Graphite and highlights them using grep:
match='ping'; sudo ngrep -lqd any "${match}" tcp dst port 2003 | grep -F
--color=tty "${match}"
Changing the protocol and port allows easy inspection of metrics sent to a
statsd listener, from carbon-aggregator to carbon-cache, etc.
See the man page for more information:
http://manpages.ubuntu.com/manpages/precise/en/man8/ngrep.8.html
--
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 : graphite-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~graphite-dev
More help : https://help.launchpad.net/ListHelp
