Have there been any updates to the variables available in the syslog alerting mechanism? I notice in the Orion syslog viewer, there is a field called "CAPTION", but I can't seem to find any corresponding variable to use in an e-mail alert.
bcole, the ${CAPTION} variable is taken from the Orion Nodes db, not the Syslog db, and displayed in the Syslog Viewer, but for some reason this macro is not available to use in email alerts, you can only use the syslog specific variables. You could try the ${DNS} or ${HOSTNAME} macros which are available for syslog email alerts. However, I have not been able to get them to correctly. All email alerts just display the IP Address. This is still the case in Orion v9. I believe it is because the action to send the email is completed before the reverse DNS lookup of the sending device's IP Address, and so the server cannot populate email with the hostname quickly enough.
I raised this with Solarwinds support, and their only suggestion was to configure all our network devices to include the hostname in the syslog message that they send (there are cisco IOS & CatOS commands to do this). However, all this means is that the hostname is in the main syslog "message" that is sent. There is no way that the Orion Syslog Server can then pull this hostname alone out of the message. So essentially the only way of displaying the sending devices hostname in the subject of an email, is to use these commands on your Cisco devices, and use the ${MESSAGE} macro in the email subject! i.e. the entire syslog message in the email subject. Needless to say we have not implemented this, as it is far from ideal. We will continue to use CiscoWorks for syslog alerting, either until Solarwinds decide to fix this, or we find an alternative solution.
I'm not holding my breath though! They seem to be more concerned with adding shiny new icons and chart graphics than fixing these far more imperative issues.
That is what I figured with the $CAPTION. Obviously if Solarwinds is doing the DB lookup now, it shouldn't be too difficult to add.
I tested with the reverse DNS and it does seem to work. I am not thrilled with populating DNS with all the IP addresses for all my network devices.
Thanks for the information.