[collectd] Are metric values point in time snapshots or ....?
Hi, When Collectd emits metrics, say every 10 seconds, does it simply take a snapshot of various metric values at that point in time, or does it keep track of metric values during that 10 second interval and compute averages and such that it then emits? Thanks, Otis -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr & Elasticsearch Support * http://sematext.com/ ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Issue with Collectd plugin for Apache ssl
Hi Tien, I'm confused please see below: On Thu, May 29, 2014 at 9:45 PM, Tien Nguyen Manh < tien.nguyenm...@sematext.com> wrote: > Thank Toni, > > I finally make it work, but with one of the following changes > 1. Add ServerAlias localhost to my virtualhost config OR > 2. Use serverUrl https://127.0.0.1/server-status. > So you CAN get Apache stats with Collectd using the above URL after you added "ServerAlias localhost"? And what about WITHOUT "ServerAlias localhost"? Do you have ServerAlias localhost in your config? if possible could you > sent your config? > > I think there are something wrong in collectd, because without above > change, i still can see server-status page in my browser (chrome, firefox) > as well as in lynx or culr -k > Are you asking why you can get to Apache stats without the above changes, but not with Collectd? In other words, why you had to add the above changes to Apache config before Collectd could get to the Apache stats? Just trying to clarify the questions. I'm not sure what the answer is. Maybe Toni or one of the other Collectd experts will know. Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ > On Thu, May 29, 2014 at 5:56 PM, Toni Moreno > wrote: > >> I'm using this config in the apache plugin and I've added to the collectd >> distribution the ca-bundle.crt contained in openssl package ( located at >> /etc/pki/tls/certs/ca-bundle.crt in RHEL 5.6) >> >> >> URL "https://localhost:443/server-status?auto"; >> VerifyPeer false >> VerifyHost false >> CACert "/opt/collectd/etc/ca-bundle.crt" >> >> >> I hope this issue can help you. >> >> >> >> 2014-05-29 12:32 GMT+02:00 Tien Nguyen Manh > >: >> >> Hi, >>> >>> I am using collectd 5.1.0 on ubuntu 13.10, libgnutls-dev >>> 2.12.23-1ubuntu4.2 >>> >>> I found one error in syslog while collectd try to conntect to >>> https://localhost/server-status >>> >>> *May 28 09:02:52 localhost kernel: [ 2140.169515] collectd[22500]: >>> segfault at 0 ip 7f5622e09b99 sp 7f561f447920 error 4 in >>> libgnutls.so.26.22.6[7f5622d95000+b6000]* >>> >>> I attached the output of collectd trace. At the end of that trace, it >>> connect to some resource but got Timeout error several times, then it stop. >>> >>> Regards, >>> Tien >>> >>> >>> On Thu, May 29, 2014 at 10:34 AM, Otis Gospodnetic < >>> otis.gospodne...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> Which version of Collectd? OS? GNU TLS? >>>> Any errors in Collectd log? >>>> What about running Collectd with strace, does that show anything? >>>> >>>> Otis >>>> -- >>>> Performance Monitoring * Log Analytics * Search Analytics >>>> Solr & Elasticsearch Support * http://sematext.com/ >>>> >>>> >>>> On Tue, May 27, 2014 at 10:50 PM, Tien Nguyen Manh < >>>> tien.nguyenm...@sematext.com> wrote: >>>> >>>>> Hello, >>>>> >>>>> I have issue config Collectd Apache plugin for Apache running on https >>>>> with status page >>>>> https://localhost/server-status >>>>> >>>>> Here is my collectd config part for Apache plugin >>>>> >>>>> LoadPlugin apache >>>>> >>>>> >>>>> URL "https://localhost/server-status?auto"; >>>>> #User "www-user" >>>>> #Password "secret" >>>>> VerifyPeer false >>>>> VerifyHost false >>>>> # CACert "/etc/ssl/certs/ssl-cert-snakeoil.pem" >>>>> #Server "apache" >>>>> >>>>> >>>>> >>>>> Collectd can't access Apache server-status page, there are no logs for >>>>> apache, while it still produce logs for CPU, mem, ... >>>>> >>>>> I tested fetching status page with curl successfully by command >>>>> >>>>> curl -k https://localhost/server-status >>>>> Total Accesses: 2 >>>>> Total kBytes: 5 >>>>> CPULoad: .00501855 >>>>> Uptime: 4583 >>>>> ReqPerSec: .000436395 >>>>> BytesPerSe
Re: [collectd] Issue with Collectd plugin for Apache ssl
Hi, Which version of Collectd? OS? GNU TLS? Any errors in Collectd log? What about running Collectd with strace, does that show anything? Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Tue, May 27, 2014 at 10:50 PM, Tien Nguyen Manh < tien.nguyenm...@sematext.com> wrote: > Hello, > > I have issue config Collectd Apache plugin for Apache running on https > with status page > https://localhost/server-status > > Here is my collectd config part for Apache plugin > > LoadPlugin apache > > > URL "https://localhost/server-status?auto"; > #User "www-user" > #Password "secret" > VerifyPeer false > VerifyHost false > # CACert "/etc/ssl/certs/ssl-cert-snakeoil.pem" > #Server "apache" > > > > Collectd can't access Apache server-status page, there are no logs for > apache, while it still produce logs for CPU, mem, ... > > I tested fetching status page with curl successfully by command > > curl -k https://localhost/server-status > Total Accesses: 2 > Total kBytes: 5 > CPULoad: .00501855 > Uptime: 4583 > ReqPerSec: .000436395 > BytesPerSec: 1.11717 > BytesPerReq: 2560 > BusyWorkers: 2 > > What is wrong with my collectd config? > is -k option in curl equivalent to VerifyPeer false in collectd-apach > config? > > Thanks, > Tien > > > ___ > collectd mailing list > collectd@verplant.org > http://mailman.verplant.org/listinfo/collectd > > ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] collectd Digest, Vol 104, Issue 9
This is the first time I hear about this. Have more info? Which version, which distro, how frequent, etc.? Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Mon, May 26, 2014 at 7:31 PM, Stuart Cracraft wrote: > What are people doing about the > crashing collectd problem besides > restarting and core-file collecting? > > > > ___ > collectd mailing list > collectd@verplant.org > http://mailman.verplant.org/listinfo/collectd > ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] write_http behaviour on POST failure?
Thanks Mark! Would it make sense to improve that plugin and let it fall-back to writing to disk, say by using one of the csv output plugins, in case of failure? Even if nothing in Collectd itself is able to pick up that data and re-send it at a later time, it would allow others to put things like file tailing agents there that, should any data be written to disk, could pick it up and resend it. Thoughts? Thanks, Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Thu, Dec 12, 2013 at 6:30 AM, Marc Fournier wrote: > Hello, > > Excerpts from Otis Gospodnetic's message of 2013-12-12 04:41:46 +0100: > > Hi, > > > > What does https://collectd.org/wiki/index.php/Plugin:Write_HTTP do when > the > > destination (there data is being POSTed) is either not up or returns a > > non-200 or times out or ... ? > > > > Is the data dropped and lost? > > Or is it written somewhere to be sent later? > > It will be lost. An error will be emitted if you have logging enabled. > > Marc > ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
[collectd] write_http behaviour on POST failure?
Hi, What does https://collectd.org/wiki/index.php/Plugin:Write_HTTP do when the destination (there data is being POSTed) is either not up or returns a non-200 or times out or ... ? Is the data dropped and lost? Or is it written somewhere to be sent later? Thanks, Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Patch for collecting global average CPU on linux boxes.
Sounds good to me. Thanks for sharing! Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Mon, Nov 18, 2013 at 3:30 AM, Toni Moreno wrote: > Hi Otis. > > I think this approach is much better in very big servers ( I usually work > in servers with up to 40 cores ) and is easier to parse a single line on > /proc/stats than calculate 40* 8 ( metrics/core) averages values. > > It also makes to have simpler config files ( avoiding average plugin). > > I will do a pull request in next days on this week. > > Thanks a lot !! > > > 2013/11/16 Otis Gospodnetic > >> Hi Toni, >> >> Would it be better to issue a PR at >> https://github.com/collectd/collectdinstead? >> >> Q: why is this approach better than using the aggregate functionality? >> >> Thanks, >> Otis >> -- >> Performance Monitoring * Log Analytics * Search Analytics >> Solr & Elasticsearch Support * http://sematext.com/ >> >> >> On Wed, Nov 6, 2013 at 8:24 AM, Toni Moreno wrote: >> >>> Hi. >>> >>> I've been working on get global average CPU , from the cpu plugin better >>> than use the "aggregate" to get the same values. >>> >>> I've attached a patch for the cpu plugin. >>> >>> with this patch you will get a new "plugin-instance" named "global" , >>> with % average of all cpu cores . >>> >>> I've obtained these values from the same proc file that cpu plugin uses >>> for the other cores. >>> >>> NOTE: This patch is only for linux. >>> >>> >>> I hope you can enjoy it >>> >>> >>> ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Metric manipulation plugins
Hi Pierre, I can't answer your Collectd-specific questions, but I'm wondering why block-based approach is needed? If Collectd outputs data every 10 seconds, for example, isn't the value written out every 10 seconds already aggregated in some way? Thanks, Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Sun, Nov 3, 2013 at 5:04 AM, Pierre-Yves Ritschard wrote: > Hi list, > > Right now in collectd we have read, write, notification and logging plugins > which cover most our use cases. > > I think the model falls short when implementing plugins like aggregation, > chaining or threshold. It seems as though we are missing an intermediate > endpoint to plug in metric manipulation when collection windows end. > > As some of you may know I've been playing with a lib which implements > generic metric manipulation, with a simple language (example syntax: > https://gist.github.com/pyr/7070364) > > Now that the syntax is well implemented in a contained library, I'm looking > for ways to implement it. I see two ways that "mangling" plugins might want > to interact with collectd: > > - in a streaming fashion: processing metrics as they come in > - in a block fashion: processing a full window of collected metrics > > Writing a streaming mangling plugin is an easy task, the "aggregation" > plugin is such an example, it registers a read plugin then marks the metrics > it generates with an attribute to avoid looping. filter_chains also > implement a similar mechanism allowing simple streaming handling. > > Writing block handling plugins is much more difficult, there doesn't seem to > be an idea of a full metric window event. So writing such plugins now need > to be done in one of two ways: > > - accumulate metrics and trigger processing at regular intervals > - accumulate metrics and trigger processing when enough events have been > input > > My current design expects a full window of metrics, it is a "pure" function > which for a specific window of metrics and configuration syntax will output > the same window of metrics augmented with a sink (a destination write > plugin) and potentially a state. > > This approach has the drawback of forcing accumulation at some point, which > might be a problem on aggregation instances but will be negligible on > node-local instances (actually given the in-memory size of metrics, it would > take a very busy aggregation instance to make this noticeable / > problematic). > > The simplest way of implementing this seems to be queuing up metrics in the > sent to the write plugin and scheduling processing when the read function is > called (waiting for a small delay to leave time for other read plugins to > submit their metrics). > > My current questions are: > > - are collectd users at large interested by an all-encompassing mangling > plugin (superseding the functionality found in chains, thresholds and > aggregatio plugins) ? > - would most people prefer a configuration that integrates in the main > collectd.conf ? It seems a bit unwieldy to me but could be doable > - is there a way I missed to accumulate metrics between poll intervals in a > sound way ? > > Thanks for your help putting this together! > - pyr > > > > ___ > collectd mailing list > collectd@verplant.org > http://mailman.verplant.org/listinfo/collectd > ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Patch for collecting global average CPU on linux boxes.
Hi Toni, Would it be better to issue a PR at https://github.com/collectd/collectdinstead? Q: why is this approach better than using the aggregate functionality? Thanks, Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Wed, Nov 6, 2013 at 8:24 AM, Toni Moreno wrote: > Hi. > > I've been working on get global average CPU , from the cpu plugin better > than use the "aggregate" to get the same values. > > I've attached a patch for the cpu plugin. > > with this patch you will get a new "plugin-instance" named "global" , > with % average of all cpu cores . > > I've obtained these values from the same proc file that cpu plugin uses > for the other cores. > > NOTE: This patch is only for linux. > > > I hope you can enjoy it > > > > > -- > > Att > > Toni Moreno > > 699706656 > > > > *Si no quieres perderte en el olvido tan pronto como estés muerto y > corrompido, * > > *escribe cosas dignas de leerse, o haz cosas dignas de escribirse.* > > > > *Benjamin Franklin* > > ___ > collectd mailing list > collectd@verplant.org > http://mailman.verplant.org/listinfo/collectd > > ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Bundling plugins (e.g. Plugin:Redis)
Thank you Andrés and Marc, all clear! :) Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Tue, Nov 12, 2013 at 6:41 AM, Andrés J. Díaz wrote: > Hi Otis, > > The main problem with the redis problem, as they said, is the dependency > with credis library. When I create the first version of redis plugin, redis > was not too popular like today is, and there were no a lot of libraries to > choose. > > I submit a couple of PR to switch the credis dependency to libhiredis one, > which is available in a lot of linux distributions (debian, ubuntu, > centos...). I hope that octo can merge the PR into the master branch. > > The PR for use libhiredis is here: > https://github.com/collectd/collectd/pull/464 > And a bonus in my fork (branch hiredis): > https://github.com/ajdiaz/collectd/tree/hiredis > you have a fully functional version of collectd 5.4 with libhiredis > (including also a custom query feature). > > Br, > Andrés > > > On 1 November 2013 21:11, Otis Gospodnetic > wrote: >> >> Hi, >> >> I'm trying to trace https://collectd.org/wiki/index.php/Plugin:Redis . >> This plugin doesn't appear to be included in any Collectd package out >> there. But some others, like mysql or ngingx, seem to be included. >> >> In case of https://collectd.org/wiki/index.php/Plugin:Redis - I >> actually don't even see where to go to get this plugin, if it's >> available somewhere else, where one would grab it and compile it on >> their own. >> >> How come some plugins are not included? >> >> Thanks, >> Otis >> -- >> Performance Monitoring * Log Analytics * Search Analytics >> Solr & Elasticsearch Support * http://sematext.com/ >> >> ___ >> collectd mailing list >> collectd@verplant.org >> http://mailman.verplant.org/listinfo/collectd > > ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Bundling plugins (e.g. Plugin:Redis)
Hi Tom, Yup, that makes sense. Thank you for taking the time to explain this. :) Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Fri, Nov 1, 2013 at 11:52 PM, Tom Throckmorton wrote: > On 11/01/2013 04:11 PM, Otis Gospodnetic wrote: >> Hi, >> >> I'm trying to trace https://collectd.org/wiki/index.php/Plugin:Redis . >> This plugin doesn't appear to be included in any Collectd package out >> there. But some others, like mysql or ngingx, seem to be included. >> >> In case of https://collectd.org/wiki/index.php/Plugin:Redis - I >> actually don't even see where to go to get this plugin, if it's >> available somewhere else, where one would grab it and compile it on >> their own. > > The plugin needs to be enabled at build time, by passing --enable-redis > to the configure script, but you'll also need to meet the deps first: > > https://collectd.org/wiki/index.php/Plugin:Redis#Dependencies > > ...so, credis will need to be installed/available for your build. > > This is the general pattern for building all of the plugins. > >> How come some plugins are not included? > > Not all plugins are included in the packages you may be using, because > the depedencies required to build them aren't a standard part of the > build environment and weren't available at build time, or really > *should* be built against a particular version, or require a dependency > that can't be distributed with the source, and therefore *must* be built > by you (the Java and GenericJMX plugins are this way, from what I > recall, because they need to be built against a particular jdk). > > In the case where the deps are available to the builder (perhaps a > standard part of the build system, or distro), it's likely the plugins > will be be built. That's why you get MySQL and nginx plugins, because > those are more generally available. > > Make sense? > > -tt > > >> >> Thanks, >> Otis >> -- >> Performance Monitoring * Log Analytics * Search Analytics >> Solr & Elasticsearch Support * http://sematext.com/ >> >> ___ >> collectd mailing list >> collectd@verplant.org >> http://mailman.verplant.org/listinfo/collectd >> > ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
[collectd] Bundling plugins (e.g. Plugin:Redis)
Hi, I'm trying to trace https://collectd.org/wiki/index.php/Plugin:Redis . This plugin doesn't appear to be included in any Collectd package out there. But some others, like mysql or ngingx, seem to be included. In case of https://collectd.org/wiki/index.php/Plugin:Redis - I actually don't even see where to go to get this plugin, if it's available somewhere else, where one would grab it and compile it on their own. How come some plugins are not included? Thanks, Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] Python collectd package
Hi, A few years ago I asked the same thing. The same with Java plugin. I remember not really being able to find them in Collectd packages. We were going to make use of them for SPM, and in fact we did use the Java plugin for a while, but we stopped doing that because we couldn't count everyone to have Collectd with Java support. The same for Python. Otis -- Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Mon, Oct 7, 2013 at 4:22 PM, Billy Kettler wrote: > Where can I find the Python collectd package for the Python plugin? There > doesn't appear to be one included with the collectd source and the package > on PyPI is for writing to the network plugin. > > http://collectd.org/documentation/manpages/collectd-python.5.shtml > > Thanks in advance. > > - > Billy Kettler > Nexenta | Senior Solutions Engineer > E: william.kett...@nexenta.com > P: 1.512.695.0485 > > > ___ > collectd mailing list > collectd@verplant.org > http://mailman.verplant.org/listinfo/collectd > ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
Re: [collectd] VMware Guest SDK plugin for Collectd 5
Mmm, nice!
Re:
"
+The VMware plugin collects information exposed to a guest virtual machine
+running on a VMware hypervisor through the VMware Guest SDK.
"
Where could I get some info about what specific information this is?
Is that all the stuff on
http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.dcadmin.doc_41/vsp_dc_admin_guide/performance_metrics/c_performance_metrics.html
?
Thanks,
Otis
--
Solr & ElasticSearch Support
http://sematext.com/
On Tue, Apr 9, 2013 at 1:45 AM, Keith Chambers wrote:
> I'm a little late replying here... hopefully better off late than never.
>
> At Cisco, we use this VMware plugin with WebEx Social. It's been deployed
> on 1000s of VMs without a single issue.
>
> Please by all means create a pull request. I've been meaning to do it but
> just swamped. Here is a cut/paste of the patch we apply during our RPM
> build.
>
>
> diff -Nur a/AUTHORS b/AUTHORS
> --- a/AUTHORS 2012-04-02 07:48:45.630039048 +
> +++ b/AUTHORS 2012-04-02 07:55:31.746064457 +
> @@ -73,6 +73,9 @@
> Edward “Koko” Konetzko
> - fscache plugin.
>
> +Edward Muller
> + - vmware plugin.
> +
> Fabian Linzberger
> - Percentage aggregation for `collectd-nagios'.
>
> @@ -91,6 +94,9 @@
> Jérôme Renard
> - varnish plugin.
>
> +Keith Chambers
> + - vmware plugin.
> +
> Luboš Staněk
> - sensors plugin improvements.
> - Time and effort to find a nasty bug in the ntpd-plugin.
> diff -Nur a/configure.in b/configure.in
> --- a/configure.in 2012-04-02 07:48:45.628039167 +
> +++ b/configure.in 2012-04-02 08:10:50.437126429 +
> @@ -4132,6 +4132,39 @@
> fi
> # }}}
>
> +# --with-libvmware {{{
> +with_libvmware_cflags=""
> +AC_ARG_WITH(libvmware, [AS_HELP_STRING([--with-libvmware@<:@=PREFIX@:>@],
> [Path to libvmware.])],
> +[
> +if test "x$withval" != "xno" && test "x$withval" != "xyes"
> +then
> +with_libvmware_cflags="-I$withval"
> +with_libvmware="yes"
> +else
> +with_libvmware="$withval"
> +fi
> +],
> +[
> +with_libvmware="yes"
> +])
> +if test "x$with_libvmware" = "xyes"
> +then
> +SAVE_CFLAGS="$CFLAGS"
> +CFLAGS="$CFLAGS $with_libvmware_cflags"
> +
> +AC_CHECK_HEADERS(vmGuestLib.h, [with_libvmware="yes"],
> [with_libvmware="no (vmGuestLib.h not found)"])
> +
> +CFLAGS="$SAVE_CFLAGS"
> +fi
> +if test "x$with_libvmware" = "xyes"
> +then
> +BUILD_WITH_LIBVMWARE_CFLAGS="$with_libvmware_cflags"
> +AC_SUBST(BUILD_WITH_LIBVMWARE_CFLAGS)
> +#AC_DEFINE(HAVE_LIBVMWARE, 1, [Define if libvmware is present and
> usable.])
> +fi
> +AM_CONDITIONAL(BUILD_WITH_LIBVMWARE, test "x$with_libvmware" = "xyes")
> +# }}}
> +
> # pkg-config --exists 'libxml-2.0'; pkg-config --exists libvirt {{{
> with_libxml2="no (pkg-config isn't available)"
> with_libxml2_cflags=""
> @@ -4500,6 +4533,7 @@
> plugin_users="no"
> plugin_uptime="no"
> plugin_vmem="no"
> +plugin_vmware="no"
> plugin_vserver="no"
> plugin_wireless="no"
> plugin_zfs_arc="no"
> @@ -4528,6 +4562,7 @@
> plugin_tcpconns="yes"
> plugin_thermal="yes"
> plugin_uptime="yes"
> + plugin_vmware="yes"
> plugin_vmem="yes"
> plugin_vserver="yes"
> plugin_wireless="yes"
> @@ -4877,6 +4912,7 @@
> AC_PLUGIN([uuid],[yes],[UUID as hostname plugin])
> AC_PLUGIN([varnish], [$with_libvarnish], [Varnish cache statistics])
> AC_PLUGIN([vmem],[$plugin_vmem], [Virtual memory statistics])
> +AC_PLUGIN([vmware], [$with_libvmware],[VMware client statistics])
> AC_PLUGIN([vserver], [$plugin_vserver],[Linux VServer statistics])
> AC_PLUGIN([wireless],[$plugin_wireless], [Wireless statistics])
> AC_PLUGIN([write_graphite], [yes], [Graphite / Carbon output
> plugin])
> @@ -5090,6 +5126,7 @@
> libupsclient . . . . $with_libupsclient
> libvarnish . . . . . $with_libvarnish
> libvirt . . . . . . . $with_libvirt
> +libvmware . . . . . . $with_libvmware
> libxml2 . . . . . . . $with_libxml2
> libxmms . . . . . . . $with_libxmms
> libyajl . . . . . . . $with_libyajl
> @@ -5208,6 +5245,7 @@
> uuid . . . . . . . . $enable_uuid
> varnish . . . . . . . $enable_varnish
> vmem . . . . . . . . $enable_vmem
> +vmware . . . . . . . $enable_vmware
> vserver . . . . . . . $enable_vserver
> wireless . . . . . . $enable_wireless
> write_graphite . . . $enable_write_graphite
> diff -Nur a/README b/README
> --- a/README 2012-04-02 07:48:45.630039048 +
> +++ b/README 2012-04-02 07:56:13.919061500 +
> @@ -309,6 +309,10 @@
> - varnish
>Various statistics from Varnish, an HTTP accelerator.
>
> +- vmware
> + The VMware plugin collects information exposed to a guest virtual
> + machine running on a VMware hypervisor through the VMware Guest SDK.
> +
> - vmem
>Virtual memory statistics, e. g. the number of page-ins/-outs or the
>number of pagefaults.
> diff -Nur a/sr
Re: [collectd] Java plugin can't find our classes
Hi, For SPM (which makes use of Collectd, see http://sematext.com/spm/index.html) we developed a Java plugin for Collectd. We found so many Linux distros didn't include the Java bindings with Collectd package that we eventually dropped it. Otis -- Performance Monitoring - http://sematext.com/spm/index.html On Tue, Feb 26, 2013 at 12:15 AM, Lindsay Holmwood wrote: > To be honest, I think the lack of use is because people prefer to > write native C plugins (as it fits collectd's paradigm more closely) > over using the Java bindings, rather than the Java bindings being poor > quality. > > That said, there is a distinct lack of development documentation and > examples for Java, so it's a bit of a chicken and egg problem. :-) > > On 26 February 2013 06:12, Nicholas Sterling wrote: > > Lindsay, thanks for responding. We'll give that a shot. > > > > The fact that the plugin isn't much used concerns me some, but I suppose > we > > can always write to a socket... > > > > Nicholas > > > > > > > > > > ___ > > collectd mailing list > > collectd@verplant.org > > http://mailman.verplant.org/listinfo/collectd > > > > -- > w: http://holmwood.id.au/~lindsay/ > t: @auxesis > > ___ > collectd mailing list > collectd@verplant.org > http://mailman.verplant.org/listinfo/collectd > ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
[collectd] Including custom collectd conf without breaking definitions in parent conf
Hi, Over at https://apps.sematext.com/ we run a performance monitoring service that, in part, depends on Collectd. I am hoping somebody here can guide me in the right direction around the best way to add custom collectd.conf to an existing Collectd setup. When people set up our metrics agent we want to enable a certain number of existing Collectd plugins - things like cpu, disk, load... - so we can gather this via Collectd's csv output. But ideally we would not just overwrite their collectd.conf for obvious reasons. I know we could: * plant our own /etc/collectd.d/spm-collectd.conf * use "Include "/etc/collectd.d/spm-collectd.conf" from the parent conf * have the same LoadPlugin and directives in both parent and included conf But my worry is that if in our custom /etc/collectd.d/spm-collectd.conf we override something from the parent conf, then we'll break it. For example, imagine if in the included conf we say: DataDir "/our/custom/log/location/here/will/OVERRIDE/the/parent" Is there anything one can do to avoid breaking plugin directives defined in the parent conf? Thanks, Otis -- Solr & ElasticSearch Support http://sematext.com/ ___ collectd mailing list collectd@verplant.org http://mailman.verplant.org/listinfo/collectd
