aLTeReGo ✭✭✭✭✭

I believe that Capacity Forecasting functions precisely as you describe above, which would make the calculations inaccurate for a period of time after adding additional capacity, be that disk storage, memory, CPU htz in virtual machines, or increasing circuit bandwidth. I have logged this internally for investigation under…

It depends on what exactly your issue is. If your Orion server is unstable shortly after upgrading to NPM 12.3 or any other Orion Platform 2018.2 releases, then the first place to start would be to change 'SolarWinds.Orion.InformationServiceClient' from Streamed to Buffered by following the instructions provided by kasaff…

This file is being locked by something. The simplest solution is to reboot the server and then re-run the Configuration Wizard immediately thereafter. That has worked for several others. In the meantime, I'm digging into what is causing this file to become locked.

You can execute perl on the Orion server itself and utilize the perl SSH module to connect to a remote host and execute an action. Baring that, you would need NCM (Network Configuration Manager) to have this functionality native to the Advanced Alert Manager in Orion. NCM extends Orion's Advanced Alert Manager with the…

This feature has been implemented natively into AppInsight for SQL included in the Server & Application Monitor (SAM) 6.0 RC available now! Sign-up here and try it for yourself!

danbran​'s suggestion, while powerful, is a bit advanced. A much simpler approach would be to exclude the volume(s) you don't want to alert on in the Trigger Condition of your existing alert. Below is an example where the alert triggers for any volume not named 'C:\ Label: 2EC5DBDA'. Once you've excluded this volume from…

Stay tuned and keep your eyes peeled here on Thwack. We should have more information on this topic very soon.

That worked perfectly, thanks.

And any suggestions on sizing SAM for this? Approximately 3200 Servers, we already have sized VM at 250 Sockets. Are the 3200 Servers ESX hosts or virtual machines? We've successfully completed SAM performance and scalability tests internally with over 500 ESX hosts per-poller without issue.

Understood, but as bluefunelemental‌ can attest, the information needed to make such an association predictably and reliably is not exposed through the vendor's SNMP MIBs. 

Which request specifically as this thread covers both features that have been implemented since posting and ones that have not as yet.

Count Statistic as Difference is available as an option for MySQL. You are correct the Tomcat Server Monitor components do not support the 'Count Statistic as Difference' option, since it's not applicable to any of the metrics returned by those components.

rsfh is correct. There are actually three buttons for the Real-Time Process Explorer already on the Node Details page. However, you must have some application template assigned to the node that collects these statistics for these resources to appear on the Node Details page. I recommend creating an application template…

These Agents are improperly reporting that they require a reboot, but no action is required. The agents should all be functioning properly. Note this issue is resolved in the forthcoming SAM 6.2.3 service release, which should be available soon.

As always Petr.Vilem‌ is correct. The only thing of note that I will add is if the agent is operating normally then a reboot is not required. We are tracking this as a bug internally under OA-137, whereby the agent is improperly reporting that the server requires a reboot. This will be addressed in a forthcoming release of…

Correct. We were unable to address this in the SAM 5.0 release but we're still tracking this request. We're currently planning a major overhaul of application template editing where we hope to address this.

There is also an existing open feature request to improve the handling of "Reserve Space" when monitoring NET-SNMP devices in Orion.

Symbolic links and mount points in Windows are very different. SAM can monitor mount points natively for nodes that are managed via WMI, but symbolic links are an NTFS attribute that most applications are unaware of.

Mapped network shares are mounted under the user context of the account which mapped the drive. These drives are not shown/available at the system level for all users to see. This is what allows multiple users to log into the same Windows server simultaneously and map the same drive letter to different servers and paths.…

Nice. That's pretty creative.

I would recommend restarting the SNMP Service on the monitored server. If that doesn't resolve the issue, upgrading the the latest version of the HP Insight Manager Agent usually solves this problem. It's more a matter of re-registering DLL's that fixes the issue, but this usually only occurs after an upgrade or a complete…

Custom Properties have never been available for use in the HTTP/HTTPS User Experience Monitors. The ${Node.SysName} is the real name of the node as polled via SNMP or WMI. The editable version of this value for use as a friendly name is ${Node.Caption}

Since information regarding the mount point/s is not contained within the CIM_DataFile class the File Monitors in SAM will not work. I recommend posting a feature request to all support for Windows mount points in the file monitors in a future release of SAM.

The multiple object chart was deprecated with the introduction of the Custom Chart resource in the SAM 6.1 release. I would recommend swapping those Multiple Object Chart resources with the new Custom Chart resource and see if that improves your page load times.

This is because min/max/average candlestick charts are a poor choice for multi-series data, as the result is almost always a visually undecipherable mess.

Have you considered using the Universal Device Poller in NPM to Poll .1.3.6.1.2.1.1.1? This should return the processor information in the following format. Hardware: x86 Family 6 Model 15 Stepping 11 AT/AT COMPATIBLE - Software: Windows Version 5.2 (Build 3790 Multiprocessor Free) Which translates into a Core 2 Duo E6320…

Sounds like you're simply adding a new (unconfigured) PowerShell Script Monitor rather than copying an existing one as outlined in the post below. Re: How to copy Component monitors that exist in one template to another custom template 

We do have a working example of the hardware health summary resource in the recently released SAM 5.2 beta. If you'd like to check it out I'd recommend signing up to participate in the beta here.

If pressing the "Configure Server" button rectifies the issue then it's very likely the configuration on the Exchange server is changing somehow. This is known to occur in some circumstances when certain cumulative rollup packages are installed on the Exchange server. Other than manual intervention or (possibly) group…

Excellent! I'm glad that worked for you. These settings may need to be adjusted based on the size of the Exchange environment being monitored and is not required for most Exchange environments. This however is excellent knowledge we will get incorporated into a KB article ASAP. Thanks for following back up on the status of…