I tried this in my lab, and I was able to build filters and rules that would fire with multiple wildcards in the AIR console. What version of LEM are you running?
Thought I'd add more details on what I did to make sure it matched what you wanted.
First, I created this rule, with pre-, mid- and suffix wildcards. The rule ought to match my laptop anytime a process starts and stops.
Then I created this filter to look for my rule:
Again, to be sneaky, the filter has wildcards at the beginning, in the middle and at the end. It should still match when my rule "Wildcards" fires, though.
So, filter on and:
As you can see, the Wildcards filter (with Wildcards) see the Wildcard Rule (which has wildcards) is working and showing that the Rule is working too. It's Wildcard inception!
I had some other issues with the upgrade where I had to create new queries instead of use my old ones. Freezing issues and such. Maybe these just need to be recreated. I was able to modify these so that they worked by separating out the statements instead of using the multiple wildcards. I bet it has to do with it being an old rule on the new upgrade. I'm sure if I create a new rule instead of edit the old one, the multiple wildcards will start working.
I had a call with support about the freezing issues and they said the old nDepth queries wouldn't work with the new version; this is where I get my assumption that this would have at least some issues with my multiple wildcard rules not working on the old rules.
Thanks for taking a look at this though.