I think you need to leverage SCOM capability for Grouping
objects. So create a Group of Datastores, you can use pattern-matching so that only Datastores with certain name are included in the Group.
And also note, that overrides are applied in a hierarchy, like this -
1. MP default as shipped by Veeam
2. Override for the whole Class (e.g. override for ALL datastores) will win over the default configuration
3. Override for a Group e.g. Group of Datastores I mentioned above - this will win over the 'class' override
4. Override for a specific named instance e.g. a specific Datastore - this will win over the 'group' override
So, you could for example, use a Class override to globally disable the Veeam Monitor for all datastore class, with an override.
Then you could use a Group override to re-enable the Veeam Monitor, for a group of datastores, also maybe with a new threshold.
Then further, you could use a Specific Instance override to re-enable the Monitor for a specific named datastore, with yet another different threshold.
Above method gives you flexibility to run the same Monitor with different options on different objects.
Note that the overrides are all set in the same override dialog (as in Rodi's screenshots) - the hierarchy is imposed by the target you choose (Class, Group, or Instance)
We have a great Whitepaper from MVP Cameron Fuller on Veeam on this topic - https://www.veeam.com/wp-manage-scom-using-groups.html
. The WP is not new, but these methods have not changed in SCOM for several versions now, so it's still valid.
If you do need more help in setting up the groups and configuring overrides - just let us know!