There are currently several alert reply options (ack/close/rea/etc.) that a user can choose from. Add the ability for the admin to add more reply options and associate them with a script or something like an http post to a URL, swql update statement, etc. (or all of the above) that would allow custom handling of the reply outside the product. If the user chose a custom option, the action/script would be executed to handle it.
This would allow the ability to do such ?useful? things as:
- Add a "ticket" response, that could be scripted to gather information from Orion/other systems and create a ticket.
- Add a "maintenance" response, allowing the user, who may be getting flooded with alerts on a device, to request the device stop sending alerts. The response coudl be caught, the host name and user parsed out, and the node handled accordingly. If the alert came from SolarWinds a script could be run to put the device into unmanaged status, if another system generated the alert (via email, etc) some other maintenance action could be taken.
- Add a "more information" options ( like "ping" or "owner", etc.) that would run a script and query for information (ping the device, pull the owner from SolarWinds custom properties, etc) and send another notification back to the user with the information
Optionally: Make the options take arguments (or at least handle spaces?), so the user could choose "maintenance 60" and the processing script wodul know to set the node into unmanaged state for now + 60 min.
Optionally: And the ability to catch/process *all* replies with custom actions/code, so if a user "acks" an alert you can process it (and possibly make a ticket so an ack = ack + ticket)
Optionally: Make any option have the custom reply to "ack" or "close", or execute any of the current built in actions so a "ticket" reply would also ack/close/etc.