[DRBD-user] [External] Re: DRBD Grafana Dashboard

Rohn Wood Rohn.Wood at askallegiance.com
Wed May 5 19:52:11 CEST 2021

> ,...). But that plugin is more realistic than a dedicated Telegraf one I'd say.

That sounds fair.


-----Original Message-----
From: drbd-user-bounces at lists.linbit.com <drbd-user-bounces at lists.linbit.com> On Behalf Of Roland Kammerer
Sent: Tuesday, May 4, 2021 12:03 AM
To: drbd-user at lists.linbit.com
Subject: Re: [DRBD-user] [External] Re: DRBD Grafana Dashboard

On Fri, Apr 30, 2021 at 08:53:35PM +0000, Rohn Wood wrote:
> So, the 800 pound Gorilla in the room wonders if there might be a
> parallel effort for the telegraf agent?

Hm, at least there has not been any customer requests for that, and quite frankly it is the first time I've ever heard of it, but I'm also not really into metrics. But as it looks like Prometheus is too big for them to ignore it, so you might be lucky with that:


All in all I don't think there are any plans, and if that input plugin works then one should use that. Technically it would be almost trivial to recycle the Prometheus components (data caches, ...) and just generate the Telegraf output I guess.

Seeing that Telegraf can also process json, that was a plugin I always had on my mind when I started drbd-reactor. Like a event triggered version of `drbdsetup status --json`. That one might come in handy for all sorts of things that want to process DRBD events as json or anything else that Rust's serde can serialize. I did not do that so far because it obviously needs deciding on a representation of the data. And I'm not sure (actually I am) if I like the one drbdsetup uses (i.e., lists where it actually is a hashmap, very weird key names,...). But that plugin is more realistic than a dedicated Telegraf one I'd say.

Regards, rck
Star us on GITHUB: https://urldefense.com/v3/__https://github.com/LINBIT__;!!FEyU5bU!RNRpXTIdHuW270rddbZdT-R9I7DByQ4hfF1eqTOfEG11COVwn1bHJ1vfGfV16TYeaqwp8A$
drbd-user mailing list
drbd-user at lists.linbit.com
The information contained in this email is proprietary, confidential and only for the use of the intended recipient. If you are not the intended recipient, note that any disclosure, distribution, or copying of this email is strictly prohibited. If you have received this email in error, please destroy it and notify us immediately at the number noted above.

More information about the drbd-user mailing list