Re: [collectd] Grouping the output of collectd in graphite
Does replace support capture groups? For instance, I’d like to rename hostname from server.domain.com to domain.server (so things are better organized on the graphite side). Vaughn Wernersbach BIDS Trading, L.P. 111 Broadway, Suite 1603 | New York, NY 10006 T: 212.618.2071 | F: 212.618.2031 | C: 732.397.8344 | E: vaughn.wernersb...@bidstrading.com<mailto:vaughn.wernersb...@bidstrading.com> From: collectd [mailto:collectd-boun...@verplant.org] On Behalf Of Giovanni Torres Sent: Wednesday, January 27, 2016 9:17 AM To: Jerry Lombardo Cc: collectd@verplant.org Subject: Re: [collectd] Grouping the output of collectd in graphite On Tue, Jan 26, 2016 at 10:13 PM Jerry Lombardo mailto:jl4...@columbia.edu>> wrote: Hey, Thanks for the reply. I'm trying to get the 500 directories (one for each host under the graphite root ) into one directory. Replace doesn't look to be doing that. I posted a screen shot of what I am looking at now, it's cropped but if i could get all of these sorted under a sub dir it would beat digging through the whole list to find what I want https://gyazo.com/1182b05ead2a12dc9ee33273af316b33 It depends on how you want your values structured in this single directory. . Are you using only the SNMP plugin? . Are you using other collectd plugins? Collectd will send to carbon->whisper->graphite-web. You will want to replace the values before sending off to carbon. Replace does work, but again, it depends on what name structure you have now and what you want it to be. The screenshot only shows the top level directory, i.e. the hostnames. It would be helpful to see the subdirectories under a hostname. The target_replace examples are scarce. I have a simple setup using the CPU and Interface plugin, with the CSV plugin for output to a local directory. Before: └── localhost ├── cpu └── interface-eth0 I put the following test configuration in place, which replaces my 'localhost' hostname with a different host name, 'all_hosts': LoadPlugin match_regex LoadPlugin target_replace Host "^localhost.*" Host "\\" "all_hosts" Target "write" # This should be default, but putting in for backwards compatibility Target "write" After: . ├── all_hosts │ ├── cpu │ └── interface-eth0 └── localhost ├── cpu └── interface-eth0 The idea here is to replace the values before they make it into the global cache. Hope that helps. Giovanni ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Preventing collectd high memory usage
Hi André Luiz da Silva! Thanks for the suggestion. I’ll keep switching to UDP in mind, though I’m inclined to stick with TCP if at all possible (largely to minimize the required changes to my environment). All - Anyone have info on using CollectInternalStats? Still need to know what value to set WriteQueueLimitHigh to and having collectd tell me definitely seems like the best bet. Vaughn Wernersbach BIDS Trading, L.P. 111 Broadway, Suite 1603 | New York, NY 10006 T: 212.618.2071 | F: 212.618.2031 | C: 732.397.8344 | E: vaughn.wernersb...@bidstrading.com<mailto:vaughn.wernersb...@bidstrading.com> From: André Luiz da Silva [mailto:andresilvalu...@gmail.com] Sent: Monday, December 14, 2015 11:18 AM To: Vaughn Wernersbach Cc: collectd@verplant.org Subject: Re: [collectd] Preventing collectd high memory usage Hi, Wenersbach! Did you try to send your metrics over UDP instead of TCP? It's just a suggestion if you have a reliable network. Regards. Em 14/12/2015 1:54 PM, "Vaughn Wernersbach" mailto:vaughn.wernersb...@bidstrading.com>> escreveu: Hi, In order to limit high memory usage (one of my servers hit 94% for collectd) I’m interested in enabling the WriteQueueLimitHigh<https://collectd.org/documentation/manpages/collectd.conf.5.shtml#writequeuelimithigh_highnum> option, but I don’t know what value to use. The docs suggest enabling CollectInternalStats<https://collectd.org/documentation/manpages/collectd.conf.5.shtml#collectinternalstats_false_true>, and that the “write_queue” plugin instance reports the info from CollectInternalStats that I’m looking for. However, I don’t see any “write_queue” plugin nor do I see anything relevant being written by my existing write plugins (syslog and graphite) after enabling CollectInternalStats. • How do I obtain data written collected when setting CollectInternalStats to true? • Alternately, are there any guidelines for setting the values of WriteQueueLimitHigh? Vaughn Wernersbach BIDS Trading, L.P. 111 Broadway, Suite 1603 | New York, NY 10006 T: 212.618.2071 | F: 212.618.2031 | C: 732.397.8344 | E: vaughn.wernersb...@bidstrading.com<mailto:vaughn.wernersb...@bidstrading.com> ___ collectd mailing list collectd@verplant.org<mailto:collectd@verplant.org> http://mailman.verplant.org/listinfo/collectd ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
[collectd] Preventing collectd high memory usage
Hi, In order to limit high memory usage (one of my servers hit 94% for collectd) I'm interested in enabling the WriteQueueLimitHigh<https://collectd.org/documentation/manpages/collectd.conf.5.shtml#writequeuelimithigh_highnum> option, but I don't know what value to use. The docs suggest enabling CollectInternalStats<https://collectd.org/documentation/manpages/collectd.conf.5.shtml#collectinternalstats_false_true>, and that the "write_queue" plugin instance reports the info from CollectInternalStats that I'm looking for. However, I don't see any "write_queue" plugin nor do I see anything relevant being written by my existing write plugins (syslog and graphite) after enabling CollectInternalStats. * How do I obtain data written collected when setting CollectInternalStats to true? * Alternately, are there any guidelines for setting the values of WriteQueueLimitHigh? Vaughn Wernersbach BIDS Trading, L.P. 111 Broadway, Suite 1603 | New York, NY 10006 T: 212.618.2071 | F: 212.618.2031 | C: 732.397.8344 | E: vaughn.wernersb...@bidstrading.com<mailto:vaughn.wernersb...@bidstrading.com> ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
