https://github.com/bodgit/graphite-stomp-tools
A set of tools for getting Graphite data in and out of STOMP message brokers
https://github.com/bodgit/graphite-stomp-tools
Last synced: 3 months ago
JSON representation
A set of tools for getting Graphite data in and out of STOMP message brokers
- Host: GitHub
- URL: https://github.com/bodgit/graphite-stomp-tools
- Owner: bodgit
- Created: 2013-08-06T13:29:32.000Z (almost 12 years ago)
- Default Branch: master
- Last Pushed: 2013-11-15T10:17:16.000Z (over 11 years ago)
- Last Synced: 2025-03-05T04:34:01.873Z (4 months ago)
- Language: C
- Size: 211 KB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
graphite-stomp-tools
====================
(This was sat in a branch of https://github.com/bodgit/graphite-amqp-tools however as I'm using this in production it made sense to break it out as its own separate project.)
Basically gluing libevent2, https://github.com/bodgit/libevent-stomp and https://github.com/bodgit/libevent-graphite together to make the following daemons that should be reasonably efficient and have low memory usage:
* graphite-enqueue - provides the graphite TCP line receiver protocol and forwards all received messages on to a given STOMP destination.
* graphite-dequeue - does the opposite, receives messages from a given STOMP source and posts them on to a given graphite TCP line receiver.
* graphite-rewrite - reads from a STOMP source, applies PCRE rewrite rules to the metric names and sends back to a given STOMP destination. Useful for removing the need to use carbon-aggregator if all you need to do is rewrite metrics, such as those fed from collectd.
All daemons can use SSL to connect to the STOMP server and also periodically send their own various statistics to a given graphite TCP destination.