aLTeReGo ✭✭✭✭✭

Was the original alert acknowledged? The acknowledgement of an alert will stop the escalation process.

Orion will allow you to define multiple hosts that resolve to the same IP once per-polling engine. Meaning if you have three additional pollers you can add the same host four times (one on the primary, and one on each additional polling engine).

I would suggest using the web based report writer, rather than the legacy Win32 based Report Writer. [Settings -> Manage Reports]. The following PDF should help get you started. http://www.solarwinds.com/documentation/Orion/docs/WebConsoleReportingGuide.pdf The following video is also an excellent way to get up to speed…

I believe the section of the Administrators Guide available at the link below is what you're looking for. http://www.solarwinds.com/NetPerfMon/SolarWinds/OrionCorePageHelp.02.198.htm

Have you assigned the "Windows Server 2003-2012 Services and Counters" template to the node? Is the "Page File Usage" component the only one in this template that is not working properly?

SAM's Oracle User Experience Monitor generates synthetic database queries against the Oracle Database Server from the Orion Server. SAM does not capture or collect real-user transaction information generated from the clients themselves.

You probably have have the floppy drive selected in Orion under Volumes. Uncheck the floppy drive and it should stop.

Chrissmail, I believe the feature you're looking for was released as an application template on Thwack. Below are links to the Linux/Unix and Windows Log Parser Application Templates. Log Parser Unix/Linux Log Parser Windows

There are no known issues adding HTTP or HTTP User Experience Monitors (or any other SAM Component Monitor Type for that matter) to an Orion group. You may want to consider opening a support case so we can look through your diagnostics to determine what's causing the issue in your environment.

This thread had become too unwieldy at 78 pages in length, spanning across a decade, where most of the submissions had been implemented many years ago. I recently reviewed each and every posting in this thread, verified what had been implemented in-product, and which had not as yet been. I then logged any outstanding…

I believe the following section of the Administrator's Guide should get you pointed in the right direction. * http://www.solarwinds.com/documentation/en/flarehelp/sam/default.htm#orionapmagconfigurejmx.htm

It sounds like those performance counters are missing from the server you're monitoring. Try opening Perfmon.exe on the server being monitored and look for the ASP.NET category. If it's not, then I recommend rebuilding the performance counters on that host by running "lodcrt /r" from the command line.

I posted some reports in the Content Sharing Zone that aren't exactly what you're looking for, but they're pretty close. They should at least point you in the right direction. The reports I'm referring to are listed below. APM Component Monitors that are not Inheriting from their Original Template APM Component Monitors…

I can tell you that it's unlikely you'll get a public response from Solarwinds about what's coming in future versions and when. They're generally pretty tight lipped about such things. However you might have success contacting your account manager.

At this time SAM cannot return the specific query that is the longest running, or the query that has a lock on a table. We are working on some improvements to SAMs database monitoring capabilities but they're primarily centered around MSSQL, not DB2.

There should be no harm in restarting the Agent service on those hosts. I would certainly give that a try before rebooting the host. It sounds like there may have been an upgrade to a newer .NET Framework version on those hosts via Windows Update and the machines are pending a reboot to apply those changes. That's just a…

I'm seeing the same problem. In fact I think everyone running 8.5.1 is experiencing this issue. See this thread

The audit messages cannot be extended to note precisely what was changed within an assigned application or template, but based on the examples above you can tell these were specific assigned applications and not the template itself since they have the name of the host they're assigned to in the event message.

You could increase the polling frequency

In theory the Win32_ComputerSystem UserName is only populated when someone is directly logged into the console. You could write a script to detect if that value is not null.

Why not use the Unmanage Scheduling Utility for the purposes of unmanaging the node from 5:01pm - 8:59am?

What version of SAM are you running and where did you get the template from?

How are the users authenticating? If these are domain accounts users will need to specify their login credentials in the domain\username format.

SAM most definitely supports the monitoring of Linux/Unix hosts and the applications that running on them. The Orion platform however (SAM included) cannot be installed on a Linux/Unix operating system. Orion/SAM are Windows only applications.

Node credentials are not available for ICMP, SNMP, or Agent managed nodes.

This was one of the features added to SAM 5.2 which has been officially released.

Have you installed the appropriate RAID management software for the LSI controller on the Precision workstation? It is this software which is responsible for publishing the storage subsystem health via SNMP. It just so happens that this software is installed by default with OMSA, but it's very likely not included in the…

Have you tried adding these using the "Component Monitor Wizard" under [Settings - SAM Settings] and selecting Windows Performance Counters?

It sounds like you downloaded the Additional Poller Installer for a different Orion Platform version through the Customer Portal. Instead, you will need to download and run the Scalability Engines Installer from the web interface of your Orion server. it is located under [Settings > Polling Engines > Download Installer Now]

Without more details it's difficult to say for certain, but I believe the problem you describe above is resolved in SAM 6.2.2.