From collectd Wiki
Revision as of 01:10, 28 November 2010 by Octo (talk | contribs) (Drop privileges: New section.)

Jump to: navigation, search


Life goes on. Which features are planned in future releases? This page is more a list of ideas than a fixed plan for the future, but it may give you an idea where the journey is going. If you want to contribute but don't know what is to be done, simply drop us a short mail and we'll get you started.

This file is not automatically generated and may thus be out of date from time to time. To give you an idea how fresh this information is please take a look at its history.

Implemented features

The following features have been implemented and will be released with the next minor version. You can check out our Git repository to test these features. They can be found in the master branch. Any feedback and bug reports are welcome!

Varnish plugin

Jérôme Renard has implemented a plugin which reads statistics from Varnish, a caching proxy server for web applications. His code is available from jeromer/collectd. —octo 11:17, 9 June 2010 (UTC)

Redis plugin

A new Redis plugin has been written by Andrés J. Díaz. It connects to one or more Redis databases and queries statistics such as commands received, memory allocated and connected clients. The code was merged into the master branch on August 17.

Write Redis plugin

A plugin for writing collectd data to a Redis database was written by Florian Forster. It was merged into the master branch on August 17.


Andrés J. Díaz has written a patch that introduces a global timeout_g variable rather than the hard-coded default (two). The patch has been sent to the mailing list on December 17, 2009.

AMQP plugin


Sebastien Pahl has written a write plugin which sends values via the Advanced Message Queuing Protocol (AMQP). It is using librabbitmq to do so. The code is available from the amqp branch on github.

  • I've rebase the code to the master branch and contacted Sebastien for some feedback. —octo 13:26, 4 August 2010 (UTC)
  • Sending and receiving data via AMQP is now possible. Possible future todos:
    • Use the parsetree interface of YAJL to parse received JSON data. Currently, the parsetree code has not yet been merged into YAJL's master branch.
    • Possibly rename the AMQP plugin to Write AMQP. For consistency's sake it might be best to rename the CSV plugin, RRDtool plugin and RRDCacheD plugin, too. —octo 06:55, 18 August 2010 (UTC)
      • No, since the AMQP plugin can send and receive values, renaming the plugin is not appropriate. —octo 20:43, 4 September 2010 (UTC)
  • Merged to the master branch. Parsing JSON still not possible, though. —octo 08:42, 6 November 2010 (UTC)

LPAR plugin

Aurélien Reynaud has sent a patch for an Logical Partitions (LPAR) plugin to the mailing list on August 10. It collects information about the (a?) virtualization infrastructure of AIX. —octo 07:23, 18 August 2010 (UTC)

Planned features

The following features are actively being worked upon. They are in various stages of completion and may or may not make it into the next release. They should have a contact (name) associated with them, so people who are interested can contact the person working on a feature. Please don't add email addresses of other people without their permission. If you want to contact a person below, please look for the email address using the mailing list archives.

Plans for 5.0

Backwards incompatible changes have been collected on the Version 5.0/Plans page. Make sure every point raised there has either been addressed or has actively been dismissed (i.e. not forgotten about).

perfmon output

Dave McLellan is looking into a text output plugin which creates perfmon compatible output (last contact: April 15th, 2009). See also: #output_text_plugin

Library for binary network protocol

Write a library for the binary network protocol, so that external applications have an easier job interfacing with collectd. The new authentication and encryption feature (added in version 4.7) makes this even more desirable. Octo is working on it.

  • Sending plain and signed network packets is now possible. The code is available from the ff/netlib branch. --octo 06:51, 18 August 2010 (UTC)
  • Sending encrypted packages is now possible, too. —octo 13:37, 19 August 2010 (UTC)

FreeSWITCH plugin

See also: ldr/collectd-freeswitch

Plugin which connects to FreeSWITCH, a free IP-telephony software, issues commands periodically and parses the returned output. The plugin was originally written by Leon de Rooij and is currently available from the ldr/freeswitch branch.

Match and target for meta data

It'd be nice to match values by the meta data attached to it and to attach or re-set meta data for values. At least something simple (see the MARK match and target in ip_tables) would be nice.

Event infrastructure

Add an EVENT command to the UnixSock plugin. This command can be used to count events, such as page loads and the like. The goal is to make it possible for applications to implement statistics collection with the minimum of overhead. powdahound is looking into it.

NetCmd plugin

The UnixSock plugin is limited to UNIX domain sockets. It'd be great if it was possible to access this infrastructure from remote hosts, for example for receiving values. Some initial code lives in the ff/netcmd branch but isn't ready yet. The idea is basically to take the UnixSock plugin and make it possible to use network sockets, too. Several people have expressed interest in picking that up, but so far no progress has been made. It's safest to keep development cycles short and provide many small patches as soon as possible.

Erlang plugin

octo is working on an Erlang plugin. The plugin implements a C-node which can communicate with Erlang processes using message-passing. The code is available in the ff/erlang branch.

InnoDB addon to MySQL plugin

Morten Hanshaugen is working on adding InnoDB statistics to the MySQL plugin. Last contact was on January 27th via email.

SNORT plugin

Benjamin Petrin is working on a plugin that will gather statistics from SNORT, an open source network intrusion prevention and detection system.

WPAR plugin

Manuel Luis Sanmartín Rozada has sent patches for a workload partitioning (WPAR) plugin for AIX to the mailing list on July 20th. —octo 13:40, 4 August 2010 (UTC)

The patches are now available from the octo/collectd/ms/wpar branch on Github. —octo 14:02, 4 August 2010 (UTC)

MongoDB plugin

There's a MongoDB plugin by Ryan Cox available from ryancox/collectd. The changes have since been rebased to the octo/collectd/rc/mongodb branch on Github. —octo 00:07, 4 November 2010 (UTC)

Write MongoDB plugin

A write plugin for MongoDB has been developed by Akkarit Sangpetch. The current version is available from the octo/collectd/as/mongodb branch on Gibhub. —octo 00:07, 4 November 2010 (UTC)

ZeroMQ plugin

Julien Ammous is working on a communication plugin which uses ØMQ (aka. ZeroMQ) as transport mechanism. Apparently it works, but it'd be great if it was merged with the the ff/netlib branch (see: #Library for binary network protocol) before including it in master. The code lives in the zeromq branch on Github. —octo 08:12, 5 November 2010 (UTC)

Lua plugin

Julien Ammous started writing a plugin which will eventually allow users to write plugins in the scripting language Lua. The code is available from the ja/lua branch and schmurfy/collectd/lua. —octo 08:02, 26 November 2010 (UTC)

Wishlist / Ideas

The following is a list of ideas we had but so far nobody has stepped up to implement them. Feel free to add your own “cool stuff” :)

RRDtool plugin: Type-specific configuration

This would allow to keep interesting data longer and less interesting data only for a short time. Also seasonal data could be added. It's not reasonable to add seasonal data to all RRD files, because it operates on unconsolidated primary datapoints (thus taking up a lot of disk space) and you can't specify one seasonal period that fits all kinds of data. A discussion of this feature can be found in the mailinglist's archive.

Maybe an option that can be passed to write functions by the Chains mechanism would be a good idea for implementing this.

Distributed setups

Make it possible to have several "servers" with shared storage. When one server dies another one takes its place, so that you don't have gaps in your statistics. This is probably best implemented as a match that matches only those values the host is responsible for. A really simple first step is available in form of the Hashed match as of version 4.9. Adding automatic fail-over would be a nice second step.

A solution for non-shared storage is probably even harder to implement and likely not worth the effort.

This can be done with DRBD together with Linux HA. A lot of solutions based on this thechnologies works very reliable in production environments.

Embed more scripting languages

Ruby and Lua come to mind.

Parrot is now at version 1.0 and provides a stable API. Thread- and reentrant-safety is not quite there yet, but it may be worth keeping on eye on.

Store to RDBMS

Being able to store values in an RDBMS would be nice. Bob Cotton has put together some SQL for PostgreSQL and a Perl based plugin to store values into it. This could serve as a starting point as a C based plugin with the same SQL backend.

See also:

Query wprobe

wprobe is a interface to query/manage wireless links, written by the guys over at OpenWrt.

See also:

output_text plugin

Sebastian has suggested a output_text plugin that can write values to arbitrarily formatted (text-)files. See also: #perfmon_output

Apache plugin: Per virtualhost stats

mod_watch gives access to stats like: 8190 539056 20965428 4813 4813 0 14.520 0 4286618408 8190 539056 20965428 4813 4813 0 14.520 0 4286618408

Why not to use it?

Couldn't find a hopepage for this project. Where does it live? Is it still alive? -- octo 21:16, 22 September 2009 (UTC)

pf (packetfilter) plugin

pf is a firewall available on OpenBSD and FreeBSD. There are quite a lot of counters which should be available (packets/seconds, octets/seconds, by states, tables, ...). Some munin plugins for reference : pf_bytes, pf

Per-plugin interval configuration

It'd be great to be able to update the interval for each plugin separately. The syntax could be something like the following:

# foobar is updated every 42 seconds.
<LoadPlugin "foobar">
  Interval 42
# qux is updated with the global default interval.
LoadPlugin "qux"

Drop privileges

A couple of plugins require special privileges. It'd be great if we could find a way to allow these plugins to do their job without requiring collectd to run with privileges.

Under Linux, a solution might be to use capabilities(7) to deal with this problem: Assign the collectd binary the permission to a certain capability, for example to open a raw socket. The plugin can then active this capability if needed. For example:

setcap cap_net_raw=p $prefix/bin/collectd

For other UNIXes, this solution is not applicable. In order to drop privileges in the traditional UNIX way, plugins such as the Ping plugin would need to live in a separate process space, since it needs to open new sockets whenever the address of a pinged hostname changes.