aLTeReGo ✭✭✭✭✭

I will work with Jiri and Lukas to create an Advanced Alert for this scenario and post it to Thwack. Based on feedback we may consider adding it to the next release of SeUM as well. However this type of logic in the Advanced Alert Manager though the pick list is not something that's currently possible for any Orion product…

Hmm. It may a subtle change in behavior in SAM 6.2 (that's what I'm running). Another possibility is that this is different based on browser. I'm running Google Chrome.

As outlined in the following article this vulnerability is only exploitable on servers with listening ports encrypted using specific versions or configurations of OpenSSL. In the case of SAM, OpenSSL is used as a client (not a server) for the Linux/Unix/Nagios Script Monitors which utilize SSH to connect to those remote…

Is the user account that you're trying to login with in a different domain or forest than the Orion server is member of?

This is an odd one I can't say I have a good answer for, only more questions. Instead of peppering you with more questions I'm going to suggest you open a case with support so we can get to the root cause of this much quicker.

Is it at all possible the database has run out of space?

We've created the following KB article that outlines the steps necessary to allow a non-Windows administrator to monitor Windows servers. http://knowledgebase.solarwinds.com/kb/questions/3304/How+to+create+a+non-administrator+user+for+APM+polling.

Unfortunately not. This too would be a feature request. I suggest posting these to the Ideas section of Thwack so other users can vote for these features.

From looking at the case notes it looks like the issue with the cache is becoming corrupted or timing out somehow. The next time it happens go to the Admin section of the website there is a clear web cache button. If that doesn't resolve your issue I recommend opening a case with support.

Why not just use Orion's syslog server? It's definitely a whole lot easier to setup for what you're trying to do.

I have a lot of fingers in a lot of different pies these days. Too numerous to keep count of most the time, or so it seems.

Without reviewing your diagnostics it's mostly guesswork... I mean they're educated guesses but guesses none the less. My recommendation is to open a case with support so we can review your diagnostics and determine the issue.

This template should be used only in "Remote Host" execution mode unless of course the files are located locally on the Orion server itself. Also, have you assigned this application template three times to monitor three files, or have you duplicated the components within the template to monitor different files? Duplicating…

32bit WMI is limited to returning processes memory values up to 4GB. To resolve this, edit the AppInsight for SQL application and change the "Platform to run polling job on" from "x86" to "x64". This will then return the correct value for 64bit processes which utilize more than 4GB of RAM.

Alert, and Alert Macro migration should be a seamless and transparent operation, and has been for thousands of customers. There can be however the occasional hiccup with the migration process. Re-running the Configuration Wizard in most instances resolves the problem. Many of the new issues identified with the new Web…

Then it's not a bug. It's an "accidental feature"

That sounds inline with some ideas we're kicking around now. You may want to check out the following thread. * Are you interested in improved support for log file monitoring?

I recommend you use the SSL Expiration monitor now built into APM. You can find more information regarding it in this Thwack thread.

Probably the best way to troubleshoot this issue would be through support but either which way we'll need you to provide us with a MIB walk of both servers using this tool. This will allow us to see what OIDs are available for polling. As a troubleshooting measure I would recommend uninstalling and re-installing the…

Hey, you're right! My poller reports being "down" in the web interface... Now the question is why? I'm open to suggestions...

Any Service name starting with "SolarWinds" should be monitored.

Yes, in that particular instance you are correct. If multiple conditions of this component's alert trigger were true, then alert would only fire once. If the 'Filecount' trigger was true and remained as such for many hours/days/weeks, the alert would remain active. If during that time the 'SymbolicLinkCount' trigger was…

Correct. This change should be applied to all Orion web consoles. Both the primary Orion server and any additional web servers you might have.

This appears to have only been requested once before‌ back in 2008, suggesting that perhaps OPC usage isn't very common. At least not amongst the 150,000+ Thwack community members. I would suggest posting this as a feature request so others within the community can vote on this idea.

Is there a mechanism for stopping alerts after a certain time frame, i.e send email repeatedly every 30 minutes for 4 hours then stop sending emails? No. The only way the alert will stop is if the Trigger Condition is no longer true, or if the alert if acknowledged. If your concern is duplicate emails, then simply ensure…

This issue should be resolved in the SAM 5.0.1 service release that's available in your customer portal. The SAM 5.0.1 release notes at available here. 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…

Upon further investigation it appears the Volume Type string value is returned by the operating system being polled. So this is not a bug, but rather the actual value as polled from the device. Due to this inconsistency in how different operating systems report volume type I recommend using the solution I posted above for…

Based on the screenshot you provided the issue appears to be the "SQL Server" service itself, which obviously can't be true or the many of the other application components would be in an unknown state. There are a couple of things you can try which might resolve this issue. * Delete the application and re-enable AppInsight…

Are you running any Additional Pollers or Additional Web Servers in your environment?