[collectd] exec/unixsock metrics not being sent to the server

[Scott Dworkis]

has something to do with an empty plugin name.  using a dummy plugin name 
works (if you're inclined as i am to discount the plugin feature and 
isolate instance namespaces in filename prefixes instead of directories).

i.e. i now plan to send all my metrics like:

PUTVAL myhost.fq.dn/dummy/gauge-myname N:2299366

previously i was trying to send metrics like this, which was NOT working:

PUTVAL myhost.fq.dn//gauge-myname N:2299366

i.e., gauge is a defined type on both client and server, so that's not the 
problem.  the problem seems to be the empty plugin name.  not a big deal, 
just my own stumble and observation.

-scott

On Mon, 5 Dec 2011, Sage Weil wrote:

> On Fri, 18 Nov 2011, Scott Dworkis wrote:
>> both client and server are writing rrds.  on bot client and server i see rrds
>> for for plugins:
>>
>> cpu
>> df
>> disk
>> entropy
>> interface
>> irq
>> load
>> memory
>> processes
>> swap
>> users
>> cpu
>>
>> but for my exec and unixsock metrics, i only see them on the client.  i feel
>> like i'm doing something wrong?
>
> This sounds like the same problem I emailed about last month.  I suspect
> that if you add the types you are using for exec and unixsock to types.db
> on the server it should work.  The network plugin doesn't seem to pass
> type information.
>
> sage
>