Ah, you're asking about SolidFire-side filtering... That's not possible, everything is sent if it's enabled.
That seems quite unusual, IMO, to filter at Source. In any case, it can't be done with SolidFire.
Your choices are probably just two: (a) see if you can filter on the server/agent, or (b) set up a SNMP trap forwarder (e.g. Linux container) where you could filter and drop the trap before forwarding.
In both cases you would have to be able to distinguish the fault or event from events that you normally want to alert on.
> However, when the volume is scheduled to be purged on the Solidfire side, the trap is raised because there is no volume
This sounds strange. If you can send a sample of this to me offline, I'd like to know how this happens.