This repository has been archived by the owner. It is now read-only.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
some additions for collectd 5.0.0 #2
Merged
Conversation
added 2 commits
Jul 9, 2011
… each metric, and types.db metric name lookups
|
Hmm.. I didn't see this pull request until now, sorry! |
jordansissel
added a commit
that referenced
this pull request
Aug 26, 2011
some additions for collectd 5.0.0
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Hi,
I'm currently implementing/testing collectd 5.0.0, and wanted to use this script to get the data into graphite (obviously). It was a bit broken and required a fix to the putval_re regex since the timestamps now have millisecond precision (also I made it greedier at the end of the line). Also, I hacked in support for multiple values being sent in the same metric, and then naming those individual values based on a types.db lookup. I've tested this and it works in my environment, but, I haven't written javascript since 1999 and I also did not put too much thought into the structure or variable names...so if there is a cleaner/more concise way to re-write any of this, feel free!
Thanks!
Don Johnson