Expert54 minutes ago, Lewis Beard said:Customers/PRIORITY ONE BANK/Network Devices*
Customers/PRIORITY ONE BANK/Network Devices/*
The difference between these two is just that the first will match on any children of "Customers/PRIORITY ONE BANK" where the name starts with "Network Devices"
The second will match any children of "Customers/PRIORITY ONE BANK/Network Devices" no matter what the child group name is.
As you're testing out your filter, I'd use a "Resource Group Inventory" report. Some of the other groups require you to specify datasources and instances, which play into the filter and may explain why you're getting no data when using the simple filters i quoted here.
That said, I've not seen (and I just tried a few ways i supposed might have worked and failed) a way to exclude certain objects the way you're doing it.
This is why I usually recommend an independent group structure for reporting/dashboarding. What I mean is, create a group with those resources minus those two servers and focus the report on that new group. It shifts the logic from the report to the group. You can create the group manually (ugh) or dynamically. What makes those two servers different? Could you tag those two servers with a property, then get all servers without that property (or without a value of false)? If the original group is a static group, you should be able to use system.staticgroups like this:
join(system.staticgroups,",") =~ "Customers/PRIORITY ONE BANK/Network Devices" && !includeInReport == "false"
If the original group is a dynamic group, just append the following to the original group's rule to make the appliesto for the new dynamic group:
<<original group's appliesto>> && !includeInReport == "false"
Just add a property called "includeInReport" to server1 and server2 with a value of "false".