-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple Collector instances #39
Comments
Yes, Gentoo uses that way for it's init.d network scripts That said, I think the preferred solution would be to setup the config file to use subkeys Example [MemcachedCollector] [[Identifier A]] [[Identifier B]] I feel that would be much easier for systems like bcfg2 or chef to manage. Would that work for your usage? |
Yes, this would work fine. I browsed over the current collectors, and I saw that at leas one uses sub-sections in their configuration. Maybe a special named section would be required for named instances? I have pushed a commit to the same branch as an example. |
I think this should do the trick really well. Please let me know if you run into any issues at all. Thanks! |
just a note for future readers who are looking for something like this and find this in a search: this is NOT supported syntax for current (june 2014) diamond. :-) |
So, do I understand it correctly: there is no way to monitor more than one instance of a service unless the author of a collector invented a special syntax for defining multiple sources of metrics? :-( |
As of now, that is correct. A PR that implements a generic solution would be welcome |
Hi,
Today I was trying to setup Diamond to collect data from several servers, each containing multiple instances of memcached.
I cannot see how to accomplish this right now, as the collectors are added to a dict with their class name as key.
I have created a branch in my fork with a solution: https://github.com/pablolb/Diamond/tree/multiple-collector-instances.
But maybe you have a workaround or you'd prefer a better way to solve this...?
In the first commit (pablolb@f2397aa) I scan collectors config directory and schedule new instances of the collector.
In the second commit, I use MemcachedCollector as an example as how this can be used... I've seen this used in Genttoo network scripts I think (using symlinks and interpreting the actual name)
pablo@localhost collectors $ cat MemcachedCollector.conf
The text was updated successfully, but these errors were encountered: