This will be great. I'm testing right now with my PC as an RP, but we have a control PC at our NOC as well. So once I get the Alerts configured and subscribed correctly, "server" setup will go there.
I hit a couple snags on CLI testing, for anyone else who has similar issues.
Server side
C:\Program Files (x86)\Growl for Windows\growlnotify.com /a:"Orion" /t:"A Network Node is Down!" /host:10.154.100.1 /pass:"mypass" "Test"
1) Notification failed: 201 - The response failed to be read successfully due to a network problem.
- check Allow network notifications
2) Notification failed: 400 - Invalid key hash
- add password to Security- Password Manager.
3) Notification failed: 401 - Application not registered
- added /r:"General Notification" to syntax
Alas, "Notification sent successfully..."
Moving onto subscriber side, and Alert Trigger Actions. Any additional info on Alert Triggers would be great. Obviously people are interested in this. Our NOC will appreciate a desktop notification, I know. Thanks RichardLetts and please continue adding when you have time.