disk fixed default without clearing all disk cfg ?

[David Givens]

Hi all,

We used the fixed_default setup to push a standard set if disk thresholds and qos metrics to collect.
We would like to change a no to a yes (qos_disk_usage = no) for a disk metric, which is set in the fixed_default section.

The way this config works is, to my understanding, only pushes out the fixed_default settings out once to each discovered disk. I order to get this to apply the clear switch needs to be pushed to <fixed> disks, which would clear all current disk thresholds. Which would be an issue for use due to customer thresholds applied.

When we update the <fixed_default> overwrite using a package, the change is reflected in this section only and not inherited by the <fixed> disks due to them not being new mounts.

So, my question is, can the <fixed_default> be applied to <fixed> disks without clearing the thresholds first ?

Example config including clear section:

<disk> overwrite
   interval = 15 min
   samples = 2
   <alarm> overwrite
      active = yes
   <connections> overwrite
     active = no
     level = minor
     message = Network connection not as expected
   </connections>
   <fixed> clear
   </fixed>
   </alarm>
   <fixed_default> overwrite
      qos_disk_usage = no
      <error> overwrite
         active = yes
         threshold = 5
         message = DiskError
      </error>
      <warning> overwrite
         active = yes
         threshold = 15
         message = DiskWarning
      </warning>
   </fixed_default>
</disk>

Thanks

[Garin Walsh]

Do the disks fit a well defined set?

For instance, standard windows drives C:, D:, E:, F: ?

You could then create a package that contains a file that looks like:
<disk>
   <alarm>
      <fixed>
         <C:\> edit
            qos_disk_usage = yes
         </C:\>
         <D:\> edit
            qos_disk_usage = yes
         </D:\>
         <E:\> edit
            qos_disk_usage = yes
         </E:\>
         <F:\> edit
            qos_disk_usage = yes
         </F:\>
      </fixed>
   </alarm>
</disk>

The "edit" directive only changes the value if the key exists so if you deploy this to a server that only has one C: drive, the D, E, and F stanzas get ignored.

There is also a tool that Luc C. created that will generate the commands to do this but I'm not sure if it is sensitive to what's already in place.

You could also script this using the controller get_probe_config/set_probe_config callbacks