bhilgenkamp_botw

Looks like I need to upgrade to PowerShell 6 to get a -NoProxy option

I really like the idea of a pool as it would allow some automatic failover in the event of a failure. Just this week I had a player randomly stop working and had to work with SolarWinds support to fix it (they were unable to determine the root cause and simply had me re-install the player). We lost all availability…

Thanks Steven. Are there any plans to integrate this into the reporting tool? Searching Thwack shows this being a request for years for thing like circuit utilization, etc. The reporting as-is doesn't seem to be beneficial to anyone outside of those wanting to track SLAs for 24x7 availability/utilization.

That was the issue. Thanks!

What is the proper usage of this monitor? The SolarWinds Online Help for File Age Monitor didn't really have a lot of information in it or at least not enough in it for me to apply to this scenario. If I use an asterisk to look for all files it give me an illegal characters error. I do not know the filenames ahead of time…

There is an option to treat a down interface as "unplugged" if you edit the interface properties, though I don't know what the parent node status will show in this case. Might be worth trying.

When you say pages do you mean views? If so how do you give a user the ability to modify a single view?

I would like to modify this so that it can be ran as a monthly report for all of our MPLS interfaces to see where we may need to increase bandwidth. I imagine the easiest way to do this would be to only include interfaces that do not have a private IP address (192.168.0.0-192.168.255.255, 172.16.0.0-172.31.255.255,…

After further troubleshooting I've found I'm being blocked by our firewall to the DMZ servers. I have rules in place for the WMI ports but not RPC. I was under the impression that these were all access via WMI. Thanks!

Is it possible to add the current CPU load to this chart?

From what I can tell the only options for routing status are up and down so I'd think you would see the issue as well if you were affected. I don't have any criteria set to specify BGP or EIGRP but the only false alerts we get are for BGP so restricting the alert to those protocols shouldn't change the behavior we're…

Heh yeah it doesn't exactly instill confidence when it does this. For what it's worth this has been happening to me since well before 12.x

I totally agree with the "why is this still configured part" but I guess my main question was why does SolarWinds seemingly at random fire off the alerts when the status hasn't changed on the down neighbor?

Which tables need to be backed up?

Thanks, but looking for a way to bulk export them all at once, or as a scheduled task if possible.

I think this will still give me troubles as the page itself that SolarWinds emails out hasn't completely loaded. Since the charts seem to be JavaScript my guess is that SolarWinds thinks the page has completely loaded (which technically is true) and fires off the email.

I'm looking forward to the new web based alerts and will be upgrading soon.

Are there any plans to incorporate this into the normal method of creating alerts from the web interface?

I came across this post trying to convert the exact same thing and your solution works great. Is there any way to make the node names clickable in the chart?

I did not explain that correctly and have modified my post. The console will be logged in to, but must remain locked.

I tried this and it didn't work. I moved on to Guac's suggestion and was able to make it work right away so I didn't troubleshoot this method anymore.

I do have SAM but was hoping to stay away from using scripts since the SNMP credentials would need to be stored in the script. If that's the only option so be it, but was hoping for a solution using a custom poller.

From what I can tell, this just exports text only results. I need charts like the screenshots I posted in the initial post.

Mark, thanks for the tip. This won't quite work for us as not all servers are in groups, some servers we don't want to monitor, etc. but I'm sure this wil be valuable info to others looking into this issue.

This is a pretty poor option that requires us to keep a list of all server names/IPs in a list that be added to the discovery. There really needs to be an option for "all current nodes" or something so that this can actually be automated to some extent.

Feature request here

Were you able to find a resolution for this?

Thanks yaquaholic, knowing that it *can* work helped. I did some more packet captures and found that it does seem to be working but is trying to go out the corporate proxies here. Long story short the site I'm trying to monitor can't go through the proxies, so I'll need to figure that out.

I have the same issue - is there any way to stop users from doing this?

Yes, that is an option now in the discovery settings: