collectd.df.df_complex collectd.df.percent_bytes https://github.com/signalfx/integrations/tree/master/collectd-df
Accepting into Beta 2 program, and assigning to Emma for review.
Hi Shirly Collectd's decription of the df plugin includes the following statement: not all "partitions" are of interest. For example /proc and /dev usually don't get filled and their "size" doesn't make a lot of sense. That's why the DF plugin offers to select only specific devices, mount points or filesystem types. It then describes the various config options. Do we use the defaults? Thanks Emma
Hi Shirly Can you please check whether the following is a bug: According to your documentation, we have two df metrics: collectd.df.df_complex collectd.df.percent_bytes According to signalfx, there are 6: gauge.df_complex.free.md gauge.df_complex.reserved.md gauge.df_complex.used.md gauge.percent_bytes.free.md gauge.percent_bytes.reserved.md gauge.percent_bytes.used.md Pls. let me know whether to document according to signalfx schema.
(In reply to Emma Heftman from comment #4) > Hi Shirly > > Can you please check whether the following is a bug: > > According to your documentation, we have two df metrics: > collectd.df.df_complex > collectd.df.percent_bytes > > According to signalfx, there are 6: > > gauge.df_complex.free.md > gauge.df_complex.reserved.md > gauge.df_complex.used.md > gauge.percent_bytes.free.md > gauge.percent_bytes.reserved.md > gauge.percent_bytes.used.md > > Pls. let me know whether to document according to signalfx schema. No. There is no bug. We have the free / used / reserved as the collectd.type_instance.