aLTeReGo ✭✭✭✭✭

I can't say for sure based solely on the screenshot provided, but have you ensured that all Exchange mailbox servers in the DAG are monitored by AppInsight for Exchange? Some information is only available from the active/mounted copy of the database. As such all Exchange mailbox servers in the DAG must be monitored by…

The issue sounds like it's more likely related to DNS name resolution than the actual performance of the website itself. SAM's HTTP/HTTPS User Experience Monitors measure the total experience time, inclusive of all aspects of the connection. This includes resolving the DNS hostname in the URL provided, no differently than…

This issue is resolved in the latest hotfix for Orion Platform 2017.3. The fix was also included in Orion Platform 2018.2.

The latest release of High Availability, included in Orion Platform 2017.3, supports multi-subnet failover for WAN/DR deployments. This allows you to have two members of the same pool in different subnets. Multi-Subnet Failover (WAN/DR) Deployment

Have you upgraded to SAM 6.1.1? Most issues related to the "Configure Server" button were addressed in that release.

Have you tried configuring the agent to use the same TCP port as the port forwarder when creating the package so they match?

First we'll need a better understanding of what exactly you installed. Which of the two following screenshots does the product you installed look like? STM/Storage Manager (AKA Storage Profiler) SRM/Storage Resource Monitor

Which application template specifically are you having difficulty with. There are several in the Server & Application Monitor Content Exchange.

I believe is correct. The issue here is that the monitored volume probably doesn't exist anymore. Either it was dismounted, removed from the server, or renamed. To avoid these alerts you can add the [Volume 'Status' is not equal to 'Unknown'] to the trigger condition of the alert that is notifying you.

Hmm.. That shouldn't be a problem. I'm going to ask that you put the monitored application in SAM into debug mode and reproduce the issue by unmanaging, then remanaging the application. Then collect a SolarWinds Diagnostic. Open a case with support and provide them the diagnostics so we can take a look at what's going on.

Denny, what if there was some sort of event log entry or such that simply stated that another polling cycle has begun before the previous polling cycle completed? I think that would be helpful and address peoples concerns of just "not knowing" if their missing data.

SAM includes out-of-the-box remediation actions for restarting sites and application pools in IIS which can be used as trigger actions in response to issues identified by WPM.

* Reports

Sounds like you have the following highlighted option enabled in the Configuration Wizard. This tells IIS to handle the Authenitcaiton, rather than Orion. Orion utilizes Forms based authentication which is what you see when you click 'cancel' to the Windows Auth prompt.

This is a known issue that is addressed in the SAM 6.2 release, currently in beta.

Yes, the Oracle User Experience Monitor can be used to query the Oracle database and gather information that can then be displayed, trended, alerted, or reported upon in Orion.

I'm sorry you weren't able to get your issue resolved through support. I do have some workarounds that might significantly reduce the volume of traffic that APM is generating. For starters you can monitor Windows processes and services via SNMP instead of WMI. SNMP is extremely lightweight and makes very efficient use of…

That worked like a charm! Thanks for all your help.

You don't have the option to manage custom properties through the Orion web interface because you are running NPM 10.3 and SAM 5.0.1. You will need to upgrade to at least NPM 10.4 and SAM 5.2 before this option will be available to you in the Orion web interface. By the looks of things, you're at least a year or two behind…

rob.hock is correct. Without more context it's difficult to provide assistance. The custom properties that you describe are not native to Orion. Either you or someone else in your organization created these Custom Properties and understand their use in your environment. Those of us in the forum will need a more detailed…

This can also be done as a native WMI monitor provided the query returns a numeric value, such as that processes CPU or memory usage.

This again likely has to do with the limited permissions of the system account that the Job Engine runs under. It could also be running into issues with UAC. One of our Script Gurus may be best suited to help answer your questions.

Under some conditions I've seen limits hit with the number of WMI querys that can be executed simultaneously against a single host. The result looked very similar to the one you describe here. It's extremely unlikely, and I'm not sure anyone has ever reported an issue where this was found to be the cause. This is just…

SAM 6.1, recently released includes Web Service monitoring for both restful API's such as JSON, and SOAP.

A subsidiary of the Orion Platform

Moved to the Virtualization Manager forum and summoning the great and powerful serena as this is likely the result of a change in VMAN. SAM/NPM include a VMAN light edition which shares the same bits as the full-fledged VMAN application.

Windows Scheduled Tasks does not use WMI. It uses RPC. This may explain why Windows Scheduled Task monitoring is working and AppInsight for SQL is not. AppInsight for SQL gathers roughly 90% of its information via SQL, and the other remaining 10% via WMI. It sounds like WMI is not working on that machine. You may want to…

If you are receiving this error then at least one Orion module installed on your main server does not meet the minimum supported versions required to perform the installation. The most common reason why this error is seen is that an RC version was installed and never upgraded to the final GA build. If you were to proceed…

kpmarcin wrote: Disadvantages to Linux Agent: - Requires open network port to incoming connections, which includes running scripts and is based on OpenSSL (possible vulnerabilities in the future) This is not correct. When the Agent is running in 'Active' mode (AKA: Agent Initiated Mode) the Agent has no listening ports,…

Why not simply unmanage the Site/AppPools you don't care about and adjust (or remove) default thresholds to reduce the amount of alert noise you receive? There are a lot of things monitored automatically as part of an AppInsight, but most have some degree of user override control to prevent alert storms on things you don't…