This issue occurs when the notification filter uses the "object" type filter along with multiple custom groups,
and test notification fails with the following error: "Object's '<Affected resource Name>' resource kind doesn't match any of the specified descendant resource kinds condition(s)."
Aria Operations 8.17.X
Aria Operations 8.18.X
This is a known issue in Aria Operations 8.17.X and later versions.
This is a known issue that has been resolved in VMware Aria Operations version 8.18.2
Workaround:
Instead of using a single notification rule with the "object" type filter and multiple custom groups, create separate notification rules for each resource. In each rule, specify the exact resource kind and any relevant custom groups.