...
the issue here is that you can not further choose the publisher based on details within the alert event.
based on current functionality, each user can have its own policy to define which alert they want for their job, as a policy with its publisher, but the issue here is that it will create too many policies unnecessarily where all the policy differs by minor additional condition for the user ( ex; jobName in this case).
solution 1)
write a custom pre-publisher that takes input on what field to match and how to customize the event or publisher info before actually passing it on to the publisher.
solution 2)
modify the current parent publishers class to take custom filter class, that can do filtering or populate the correct information for publisher before the event publisher actually sends the alert.
use-case for ex: hadoop job alert can be configured to send to the registered owner of the job, where catching the alert generally can be the job of alert engine but sending it to appropriate notification channel can be done afterwardsas part of publisher.