Anything that does not match the class, will have no action (in action you set the mirror session).
Now, this can be more tricky, you can define a class-1 for matching say
1.1.1.1 to 2.2.2.2 for https, and a class-2 that will match anything but what is in class-1.
In the policy you ca have:
policy test
10 class ip class1 action mirror 1
20 class ip class2 action mirror 2
In mirror session 1 you define the tunnel destination for server1
In mirror session 2 you define the tunnel destination for server2
As long as you do not mirror to the switch CPU, you can keep it for years, as mirrored traffic is processed directly by the ASIC line-rate,
including the ERSPAN for GRE encapsulation.
Just be careful about the BW available for the destination receiving mirrored traffic. If you mirrored a VLAN collecting 10x ports of 10G,
you won't be able to mirror this volume to a desitnation behind 10G port: obvious BW limitation.