If you don't hear from the community, open a support ticket.
From Tech Support:
Unfortunately triggering an alert based on a single service going 'down' with this Custom Poller is not possible at the moment.
To trigger on a single service going down would require an alert trigger based on the contents of the CustomPollerLabels table as this is where the names of the services are stored. Creating a trigger condition based on the value of a label is not currently possible.
Example extract from CustomPollerLabels table:
CustomPollerAssignmentID RowID Label
10dbd6d0-947d-4437-9ab6-6d6beea760b7 184.108.40.206.220.127.116.11.18.104.22.168.108.49 apache11-ssl1
10dbd6d0-947d-4437-9ab6-6d6beea760b7 22.214.171.124.126.96.36.199.188.8.131.52.108.50 apache11-ssl2
These are used in NPM to create the labels for custom poller status' in the Web Console table.
This is why it is listed on your Orion NPM as 'CSSsvcState - Label' and 'CSSsvcState' on the table view. Orion NPM does not see the value of 'CSSsvcState - Label' as being a service that can go up/down, but simply as a label for the custom poller. The variable status of the Custom poller is the 'CSSsvcState', and this is what can be alerted on.
The only Custom Poller trigger conditions can only trigger based on the contents of the CustomPollers and CustomPollerStatus tables. As the label is not stored in either of these tables it cannot be used as a trigger condition.
This will be possible in a future release of Orion as Advanced Alerts is a feature that is currently being developed. The Advanced Alert will allow you to create alerts based on the contents of any table.
So what’s on tap next for Orion NPM
I will also forward this to the development team as a feature request, as the more requests for features, the more priority is put on the development of those features.
Thanks, Mike, for the update.