Define URL Root

When creating alert trigger actions you get the option to add a URL back to the node or componant (or whatever). The root of the URL is always http://solarwindsserver:80/. Is there somewhere where I can define this value? I would love to make it https://monitor.mydomain.org/. Force this to https and to the aliased DNS entry.

Thanks, John

Find more posts tagged with

acknowledgeurl

advanced_alert

advanced_alert_setup_question

Accepted answers

All comments

dfairles

I would like to know how to do this also. We front our Solarwinds Web server with a BigIP load Balancer.

qle

I'm not aware of any configuration option to change this. However, I believe you can make a change directly to the database to accommodate this. It should go without saying that this won't be supported by SolarWinds and the standard disclaimer: I'm not responsible for any damage that occurs with this change or if you're able to make cows fly over the moon...blah blah blah. Take the necessary precautionary measures (i.e. backup).

Anyway, in the database table called Websites, you'll see one or more entries. Find the entry that has solarwindsserver as the ServerName.

Change the ServerName to monitor.mydomain.org
If IPAddress is set to a specific IP Address, you'll probably want to change that as well
Obviously, for Port, you'll want to change that to 443
Finally, change SSLEnabled to 1

I don't know if the changes take effect immediately or if specific services need to be restarted or if the server simply needs to be rebooted.

This should all work according to the modify orion alert manager variables thread. However, there has been at least one report of problems with this according to the HTTP vs HTTPS frustration. It's unknown whether the values will revert back if a patch or update is installed.

Good luck and if you try this, please let us know how it works out for you.

foonly

After going through a few upgrades, our Top Talker alerts stopped working. One of the things I found was that the Configuration Wizard had added a 2nd WebSiteID (actually, WebsiteID 3), without the FQDN, but with IP and port 443, SSLEnabled=0, Type: primary.

The original row had website id 2, the server name with FQDN, IP, port 443, SSLEnabled, Type:additional.

I changed the website id 2 to be Type: primary, and deleted the website id 3.

Top talkers are now top talking to us again.

I think the Configuration Wizard needs to allow the idea of HTTPS only, with real certificates, as many government sites require this. This should not have to be a SQL hack.

=seymour=

dfairles

Bumping this:

configuration wizard does not take into account the additional web server as well.