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-
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 o
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?
-scott
_
ese trigger rrd creations on the client but not on the server.
-scott
Date: Tue, 22 Nov 2011 10:05:01 +0100
From: colle...@faxm0dem.org
To: collectd@verplant.org
Subject: Re: [collectd] exec/unixsock metrics not being sent to the
server
Message-ID: <2022090501.gb8...@ccswissrp.in2p
On Mon, Nov 21, 2011 at 12:42:04PM -0800, Scott Dworkis wrote:
> >but for my exec and unixsock metrics, i only see them on the
> >client. i feel like i'm doing something wrong?
Did you add new entries to types.db?
___
collectd mailing list
collectd@ve
resend, i think last message failed because i had not yet subscribed.
sorry if this ends up being a dup.
-scott
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
mem
