Professor
EmployeeOK, so this is a complete bodge / kludge, but what if you set the "exclude.volumes" (etc) property/properties at a high group level so it exists on all relevant resources by inheritance? (E.g. at "Devices by Type/Windows Servers" or equivalent)
The value can either be blank (if that works - TEST FIRST!) or a value that is never going to match a real instance name and therefore never going to exclude anything.
You're then free to add subgroup or resource-specific values to the same prop name, where appropriate, to target those specifics you don't want.
ProfessorYeah, adding all the exclude properties to the root group with a value that will never match should work (empty value will not). But then I would need to add ALL the exclude properties I create (which can grow over time) to the group and would be applied to each device. It is a kludge I would like to avoid, but should work.
It would just be nice to have something like the No* categories (like NoPing, NoSnmpIf, etc) where you can just apply it when needed. Just that this would be for Instances instead of whole DataSources.
