Exclude specific Filesystems from Filesystem out of space warning

[toprockRS]

Hi there,

I´m trying to optimize our symptoms that they fit our needs.

We have some applications where they need an USB Dongle for Licencing but this dongle is displayed as a 100% filled NTFS Filesystem. So every of these reports as an urgent problem because this this is full.

What is the best way to build a symptom that is not interested in drive Z: for example?

Regards

Johannes

[mark_j]

You're specifically looking to exclude the instantiation "Z:\" of the attribute that represents 100%.

Today, we've got 4 out of the box symptoms for the Guest File System Usage % instantiations. Here they are:

These symptoms have the metric selected 'generally' and the symptom option is selected 'Evaluate on instanced metric'. Now, you may ask yourself, why is this? This is checked so that each and every instantiation of this metric is evaluated. This let's us evaluate every instantiation without creating a symptom for EVERY SINGLE instantiation, which would be every possible drive letter and mount point, A-Z. So you'd need to create 26 Symptoms (A-Z) to do the job of one symptoms with the 'eval on instant metric' box checked.

So OK.. you want to exclude Z:\. We'd accomplish this by unchecking the instantiation button, and then creating individual symptoms for EVERY SINGLE instantiation, C:\, D:\, E:\, F:\, " " " " " " ". Then adjust the associated Alerts to use these new symptoms and fire for 'ANY' of them being true.

Not ideal, but this is what you'd want to do. If you don't want the bazooka approach (out of the box) of targeting all instantiations, you'll need to pick up a sling shot and go pick off your instantiations one by one. I'd suggest you find some catchy music and get started in the GUI, or check out the API and do the bulk Symptom creation that way.

Enjoy..

[toprockRS]

Thanks for that.

I was hoping that there is a faster solution on that but as you said, i will go and configure this one by one.

Problem is that I can´t select most of the drive letters from within the Edit Symptom GUI

Solution for that ?

Regards

Johannes

[mark_j]

Sure. Click "Select object" and select an object (VM in your case) that you want to use to populate the metric picker. Specifically, find a VM that has the instantiated drive letter you're looking for.

[toprockRS]

Hi Mark,

so i tried this and created a bunch of Symptoms via API but then i detected a problem.

We not only have Windows but Linux as well and to exclude a specific Mountpoint would cause me to create a symptom for each and every Mountpoint that exist all over our infrastructure.

Same is with Windows. So we do have some Filesystems mounted as shown in the screenshot.

So is there any easier solution that is more robust for future changes? Should i open a Feature Request on this? It would be great to configure this directly from within the VM View so that this will get pushed into a now Policy that can be attached to other Elements as well.

Regards

Johannes

[mark_j]

There's no other way around it today. You cannot exclude specific instantiations from symptoms. I'd say go ahead and feature req it.

[mark_j]

One thought would be to isolate the system with a ###/ drive you want to exclude and block the default alert/symptom that does all instantiations. Then create another policy that has the custom symptom/alerts. This way, you only need to create new custom symptoms/alerts for the drive mounts from the system you want to exclude the ####/drive on.. maybe just a handful.

[toprockRS]

That was what i was thinking about but we have 500 Systems with a Drive for Pagefile and they are all different in their other drives so this helps only for some Machines but not all of them.

Regards

Johannes