Custom URL or FQDN for NPM Console and Alert Variable

Wooohoooo.... just upgraded to 12.1, and look what's in the settings!  Thanks to everyone who voted, and thanks to SolarWinds for listening.

I don't think I'm doing this right. the FQDNis orion.adntx.com but the WebsiteID of 1 is gone now (it had the server's name). Thinking I need to get that back? IDK.

This seems to work now and we don't have to change anything in the database.

Alert Details:  http://<yourserver>/Orion/NetPerfMon/ActiveAlertDetails.aspx?NetObject=AAT:${N=Alerting;M=AlertObjectID}

Just upgraded to 12, and struggled to find this workaround.
Really frustrating to have all of the alerts handing out bad URLs after an upgrade.

You don't need to reboot, but you have to shutdown and restart the Orion services.

We have been struggling with the same thing as @unitof and @jessmwku with an alerting link on the web server.  The default link tries to go to the main poller and just fails.  For now, we just send them to the main alerts page and not the exact alert due to the link not working.

Three years and several releases later and this basic usability feature is still not available even in the shiny new NPM 12.

Sighs.

We are experiencing this same issue, trying to use the AlertID as a global unique variable for our ticketing system to read to open and close tickets related to the same device going down/up. Did you ever have any luck with this issue?

I've set up a similar email template as derik.pfeffer‌'s for alerts, where I manually write my link prefixes and append a variable to the end, but I'm currently fighting with the ${N=Alerting;M=AlertID} variable. It seems I should be able to use it in the context http://custom.url.com/Orion/NetPerfMon/ActiveAlertDetails.aspx?NetObject=AAT:${N=Alerting;M=AlertID} to create a link to the Alert Details in a triggered alert email, but ${N=Alerting;M=AlertID} always, always, always returns 126. Doesn't matter if it's a real triggered alert or a simulated one. ${N=Alerting;M=AlertID} always gives me the string 126. Any ideas?

All,

Another option and one I like to use with my Clients is HTMP formatted Alert Emails. This allow multiple link options within the same Alert. Example is an Interface goes down, I can provide links to the Interface and Node Details views and one to the Alerts Page. In some cases I have also included links to external items like Ticketing Systems, Carrier or Service Provider, etc..There might even be an internalvs. external linkto access your web console basd on where you are working form, so this allows that support as well.

<b>Interface:</b>${Caption}
<b>Status:</b>${Status}

<a href="http://FQDN of your Orion//Orion/Interfaces/InterfaceDetails.aspx?NetObject=I:${InterfaceID}">Click Here to access Interface Details View</a>

<b>Node:</b>${Node.Caption}
<b>Status:</b> ${Node.Status}
<b>Department:</b>${Node.Department}

<a href="http://FQDN of your Orion/Orion/NetPerfMon/NodeDetails.aspx?NetObject=N:${NodeID}">Click Here to access Node Details View</a>

Best Regards,

Derik Pfeffer

Loop1 Systems: SolarWinds Training and Professional Services

• LinkedIN: Loop1 Systems
• Facebook: Loop1 Systems
• Twitter: @Loop1Systems