aLTeReGo ✭✭✭✭✭

Perhaps the best and easiest way to answer those questions is with some simple examples that demonstrate how to gather application or component availability via SQL. Application Availability SELECT TOP 10000 APM_ApplicationAvailability.PercentAvailability AS ApplicationAvailability,APM_AlertsAndReportsData.ApplicationName…

Not at this time, though a Linux Agent is something currently on our roadmap.

We're currently tracking this as a feature request internally under FB96264. This is on our road map, but I cannot as yet speak to time frames.

Generally the authentication method is not the issue. Rather it's the RADIUS server being down/unavailable, or the back end authenticator (active directory, etc.) that is inaccessible, down, or otherwise unreachable. For these scenarios, creating a separate RADIUS profile that uses PAP authentication and using SAM's RADIUS…

borgan wrote: Somehow I missed your post RE: Enhanced Node status back in March. In short, the feature looks very good and should be a long-awaited improvement to how node status is treated in Orion. I could not comment in the referenced post, so please permit me to post a couple of comments/questions here: 1. Did I miss…

It sounds as though you may be polling too frequently that the rest of the components within the template cannot complete the polling cycle before the next one begins. I suggest increasing the polling value to the default 5 minutes to see if that eliminates these random alerts from occurring.

Either of the two application templates below should be exactly what you're looking for. Note: These application templates require SAM 5.0 and will not work with earlier versions of APM.

You will likely not be able to use the Component Monitor Wizard for this metric since it currently only looks at the root\CIMv2 namespace. You can however add your own custom WMI component monitor and specify the namespace manually, appending "nv" to the end, then specifying the query you'd like returned.

WMI would be preferred

These would need to be done individually as there is no way to change credentials en masse to just targeted select number of assigned applications that use that credential. Updating the credential itself as I described above is the simplest method that is used normally when password changes occur, or a new dedicated…

Can you please try upgrading to SAM 6.0.2 and testing with "sa" or equivalent credentials? If neither of these resolve the issue, please enable debug logging, gather a SolarWinds diagnostic, and open a case with support. We'll need this information to properly diagnose the issue.

If the script was not written/designed to be run and executed locally from the Orion server against a remote host, then the script would need to be modified to run remotely or wrapped in PowerShell using WinRM.

Please note that when running the "test" email you can't select which hardware sensor the test message is sent for, and the trigger condition filters don't apply to test emails. What you are seeing is likely expected behavior. I recommend enabling the alert and see if it triggers for the node that shows the hard drive in a…

Have you verified that the credentials you are using in SAM for that monitor have adequate permissions to execute that script? Also, have you tried assigning any other application templates to this node that use the Linux/Unix script monitor? Can you verify those are working as intended?

If you're only concern is with application up/down status then simply remove the warning and critical thresholds defined in the monitor. E.G ensure the highlighted fields below are blank for this TCP Port component monitor.

Why is that? If you're concerned about SNMP service restarts triggering false alarms then you can switch your polling method to WMI for Windows Nodes. For Linux/Unix hosts you can easily write a quick bash script monitor in SAM that returns the output of the uptime command. Neither of these options would be dependant upon…

What version of SAM are you running? The "isServer" property was newly added in the SAM 6.2 release.

Only integers or bolian metrics can be monitored by SAM. The items shown in the screenshot above that are not available for selection are string values.

We do have a template available in the Content Exchange. As for the errors you are receiving it's likely that the Apache status page has not been properly configured on that host (try going to http://ipAddressofApacheServer/status) or that the account you are using does not have permissions required to execute the script.…

Both the Notes and Description field can be used as part of an Alert Trigger.

Just to note, only one of the three databases listed are for Orion. That one being "SolarWindsOrion". The other two are related to SQL's built-in Reporting Services.

The SQL Server 2005-2008 Performance (SQL) Template requires read access to the following tables/views * sys.dm_os_performance_counters * sys.dm_db_partition_stats * sys.dm_db_index_physical_stats * sys.dm_exec_requests

Can I recommend downloading the latest WPM 2.0 release from your customer portal and giving that a try. There's no requirement to upgrade your production install of SeUM if you don't want. You can install WPM 2.0 on a lab machine for 30 days simply for testing. What you're really testing is if the latest Recorder version…

The instructions are likely outdated and don't reflect changes made to the Database Manager in NPM 10.4, SAM 5.2 and newer releases. For newer releases you will need to download and install the SQL Management Studio and follow the steps outlined in this document.

The email is sent via SMTP. Retrieving the email delivery confirmation receipt is done using MAPI. This is why I recommended you verify that you can connect to that mailbox using the MAPI User Experience monitor, and that you have either the CDO, or Microsoft Outlook installed on the APM server.

Several of these templates for Exchange 2010 have been updated recently to support cross domain/forest monitoring where no trusts exist. Perfect for MSP style monitoring where each customer is in their own unique domain.

Likely the easiest way to monitor for this condition would be to alert on the event generated in the Windows Event Log when this occurs. Another possibility is to see if the Windows Performance Counters for the mail store disappear when it's dismounted. In that case you could simply monitor any performance counter related…

How did you verify the OID, and which OID did you verify? Another option you may want to consider is changing the node polling method from SNMP to WMI.

Fair point, however the names you are seeing are the slot names, not the names of the servers installed (unless of course you spend the time updating the slot names to match the names of the servers installed, then maintaining that as blades are added/moved/removed from the chassis). This would be a fairly trivial…

You'll need to download the attached report and copy it to the Orion server in the Report Directory. Normally located in "C:\Program Files (x86)\SolarWinds\orion\Reports". Next, add a new "Report from Orion Report Writer" resource to the "Node Details" view. Lastly, edit the newly added resource and select the "Group…