Prefix is no longer a required directive
While useful, the user should not be required to provide a prefix.
Having the hosts as the top level containers may make sense in some
environments. The current format is "${prefix}${hostname}${postfix}" so
be careful to add dots where needed.
Also updated docs to reflect this change.
While useful, the user should not be required to provide a prefix.
Having the hosts as the top level containers may make sense in some
environments. The current format is "${prefix}${hostname}${postfix}" so
be careful to add dots where needed.
Also updated docs to reflect this change.
Allow the user to append a string to the hostname
The user should be able to append a string to the hostname to provide
better organization if they wish. The directive used to set this option
is Postfix.
The user should be able to append a string to the hostname to provide
better organization if they wish. The directive used to set this option
is Postfix.
Make the dot substitution char configurable
Set the character used as the substitute in host and datasource names in
the collectd configuration block. The directive used to set this option
is DotCharactor and its default is '_' (underscore).
Set the character used as the substitute in host and datasource names in
the collectd configuration block. The directive used to set this option
is DotCharactor and its default is '_' (underscore).
Mangle dots on the type instance, not ds name
Must be getting tired...
Oops. Use the new string and free it when done
Merge branch 'master' of github.com:jssjr/collectd-write_graphite
Converts . to _ in datasource names
This came up during testing with the ntp plugin. The ds_name was being
sent with an ip in the string. This will prevent the result from nesting
in the carbon store.
This came up during testing with the ntp plugin. The ds_name was being
sent with an ip in the string. This will prevent the result from nesting
in the carbon store.
Don't require a named backend
Naming a backend adds no value to the configuration and only serves to
complicate things. Multiple unamed carbon backends are still allowed.
Documentation updated to reflect the change.
Naming a backend adds no value to the configuration and only serves to
complicate things. Multiple unamed carbon backends are still allowed.
Documentation updated to reflect the change.
Modify whitepsace
Optimize strlen() calls out
Move send buffer size to the top of the file
Remove fold markers
move sources
free name appropriately
add config example and move host definitation out of <Carbon> attribute
initial sync from private repo