aLTeReGo ✭✭✭✭✭

Happy to oblige! 

The list of previously entered email addresses are available via the drop down, eliminating the need to re-key them in when creating new alerts. There is however no way of defining a single email address that applies to any/all alert actions that contain email notifications en masse. Nor can this be done for the alert…

We are kicking around some ideas to improve the Thwack feature request process that should help mitigate this issue. In this example all Orion products support groups so where do customers post feature enhancement requests? It doesn't make sense to post them in each product's respective forum since there's no easy way to…

 That looks to be the installer for the additional web server. That's what I was afraid of... (grumbles, and picks up the phone to call customer service again)

Not to sound ungrateful but how would you like me to troubleshoot the NetPerfMonService service hangs?

SAM's HTTP User Experience Monitor supports both Basic and NTLM website authentication.

From the SAM 5.0.1 Release Notes: An issue concerning incorrect data appearing in a hardware alert email has been fixed. Note: In order for this to be resolved, you must delete the current hardware alert that is not working from the Advanced Alert Manager. Once deleted, re-run the configuration wizard (Select Database) to…

Is the LSI MegaRAID controller by chance a Dell PERC controller? Also, is Dell's OpenManage Server Administrator installed on that server? If this is truly a LSI branded (not Dell rebranded PERC) controller, then SAM's native Hardware Health monitoring will not be able to monitor the status of this controller, or the hard…

I know the official position is that Orion does not have 2008 support yet but will it run on it? Probably not. There are some major changes between 2003 and 2008 that break Orion. We'll get that support in the first half of 2009. Denny, I don't suppose 9.1 added support for Server 2008?

Do you have a back-up you can share with us? I'll give you a backup copy of our database. Email me directly with instructions of where you'd like me to put the file. I'm warning you it's not small.

3000 component monitors isn't that many, but the errors you're seeing are indicative of a polling engine that may be overloaded. I agree that if the memory isn't being consumed and the system isn't paging adding more memory won't resolve the issue. The CPU may in fact be the bottleneck. I'll look into escalating your case…

This sounds like a very likely culprit. Keep us posted if this ends up resolving the issue. It's very likely to help other users who might also encounter this problem in the future.

It's located under the 'Monitoring Settings' step.

There are a couple of other ways this can be accomplished. If timing isn't your primary concern then simply configuring the application template polling interval to poll once every 86400 seconds (once a day) should do the trick. Unfortunately with this method you have no ability to control when the application is polled,…

The device may not support SNMP GET-BULK methods properly. I would recommend following the steps outlined in the KB article below to see if that helps. * SolarWinds Knowledge Base :: Problems in SAM with SNMP Process Monitors failing One other snag... when I'm making my template I'm adding in an "SNMP Monitors" for each…

The limited information available here makes troubleshooting this issue very difficult. Please open a case with support.and we will work with you to identify the case of this unknown status.

I was asking for which individual component monitors are showing as unknown status?

Can you summarize you findings and post them to the SAM Beta forum so we can investigate this further?

What does your Orion configuration look like? Is this a dedicated Orion server? How many nodes & elements are you monitoring? What are the hardware specs for the server? Response time can be heavily influenced by a machine under heavy strain. For instance high CPU utilization or heavy network interface usage. You might…

This is because the ${DNS} macro isn't available under the Hardware Sensor property category of the Advanced Alert Manager. I suggest using ${NodeName} instead. If you need the fully qualified domain name you could either update the node's caption accordingly, or append the domain name to the macro. E.G.…

The node whose name is obscured by the red box in your screenshot, is it managed via WMI? If the node is managed via SNMP or ICMP there are no node credentials which can be inherited by the application.

How are you accessing the Application Details view? To be presented with the option to configure the server this must be done through the "All Applications" resource as pictured below. Clicking on the "Microsoft Exchange" AppInsight Application that's in an "Unknown" state from the "All Applications" resource should then…

If you've changed the Command Line script arguments to execute a local copy of the script, the contents of the script body are irrelevant and can be safely ignored. While this field cannot be empty, the only requirement is that a single character exist in this field. The only time this script body is referenced is when…

Note the status for this value are listed below, as well as what I believe their mapping to Orion status is from memory. In your UnDP above it does in fact appear that you are seeing the "nonCritical(4)" status which maps to a "Warning" condition in Orion. This would explain the yellow bars you are seeing in the…

Is TCP Port 17777 open from the Additional Poller to the Main Orion Server?

Case #105117

Yes. Simply enter the full URL of the website you want to monitor into the URL field. This will function regardless of what node the component is assigned to. However if you want to avoid associating a random URL like "http://www.google.com" with say your Exchange server for fear it will confuse others, I suggest creating…

That is likely the reason for this error as Orion itself is not aware of the manual configuration changes made to IIS.

As a workaround you could use List Resources in Web Node Management or System Manager to unassign the CPU&Memory poller from that node (since we apparently can't pull that info from that node anyway). Then run "DELETE FROM CPULoad WHERE NodeID=49" to get rid of the data. Wow that worked like a charm! Thanks for the help. I…

Correct. That is the recommended limit per-polling engine. SAM 6.2+ supports upwards of 150,000 components per-Orion instance. Stacked pollers can be used to achieve 20,000 components per-server.