aLTeReGo ✭✭✭✭✭

Have you applied hotfix 3? Also, I can only locate one open support case, number 00300222 related to discovery. If you have another open support case related to high resource consumption, what is that case number?

You can try mapping values to an Enumeration as the image below demonstrates. I can't say I've every tried mapping an entire OID but it's worth a try.

Have you taken a look at my Liebert CRAC Universal Device Poller Template?

Yes. That would be the appropriate place to request this feature.

pratikmehta003 wrote: i see the same.. but still the available poller in GUI doesnt seem to work, its not capturing the accurate results for CPU and Memory.... Have you tried using the Poller checker tool against that device? The Poller Checker Tool is located under 'C:\Program Files…

acf6276 wrote: ALTeRego any update on CORE-11585? Looking specifically for the Cisco 5520 WLC that was listed on page 3 of this. Thanks! These have not yet been added. The request simply came too late in the previous release to be included.

If that's the case then I would recommend opening a case with support so we can troubleshoot this issue further.

You will first need to enable the mod_status module on your Apache server before this template will be able to collect information.

WHen polling through the vCenter, the protocol used is the VMware web services API. When polling the ESX hosts directly, the protocol to collect hardware health information specifically is CIM. The VMware API is still used to collect all other information from the ESX host.

Viewing the full details of the Windows Event Log Message that's found is a feature that's been included in the latest SAM 5.2 beta. If you're an existing APM/SAM customer under active maintenance you can sign-up here to participate in the beta. We'd love to get your feedback on this feature. To learn more about what's new…

Including the Message/content information from the Windows Event Log monitor as part of an alert is currently a feature request we're tracking internally as FB55680. In the meantime I would recommend naming the component monitor something meaningful such as the EventID or something similar. Alternatively you can use the…

It would appear they may have missed something, such as resetting the status for roll-up calculation. I would encourage you to reopen your case with support.

silverbacksays​ I'm sorry to hear that you've stumbled into a really bad place with the HA beta. Unfortunately the situation you describe is a known issue in the beta, of which only you and I have thus far had the misfortune of encountering. Unfortunately there is really no easy recovery path in HA Beta 1 once you're in…

This is the difference between the "Top 10 Nodes by Average CPU Load" resource and the "Top XX Nodes by Average CPU Load" resource. The 'Top XX' resource has an "Edit" button, where the 'Top 10' does not.

Which IP address is used for polling (real/physical or VIP) is determined by the Windows operating system itself. This can however be controlled by defining the which IP address is used for each. The IP with the highest order matching bits to the destination IP will always be used as the the source IP. Which IP address is…

It sounds like you don't have the PowerShell folder under IIS, or you've removed the default site altogether. Can you open the IIS Manager and confirm that your IIS site structure looks the same as the one below.

Not yet. serena is the Product Manager for VMAN and she's always eager to hear what customers are looking for in her product.

The suggestion to use the Agent meant that you would need to manually download the Agent installer MSI and install it on that machine. If you can't poll that machine via WMI from the Orion server, then you're also not going to be able to push an Agent to it either. Deploy the agent manually to a Windows computer

I haven't seen WMI timeouts once SP3 I agree that the situation has gotten better since SP3, but I'm still experiencing timeouts on WMI monitors as well. I've increased my timeouts as high as 300 seconds, but I still continue to have timeouts. The problem always solves itself on the next polling cycle leaving our response…

Within the script body you will see [string] $url = "https://$hostname/owa/" on line 18. Try replacing "$hostname" with the fully qualified domain name you would use to access OWA from the Orion server if you were to access it using Internet Explorer. Be sure to validate there are no certificate errors when accessing this…

AppInsight for IIS, which is part of the SAM 6.2 beta, includes native Application Pool monitoring.

I know I can't solve everyones needs, but iReasoning has a great replacement for the Solarwinds MIB Viewer, and MIB Walk utilities called the iReasoning MIB Browser. This program will do simple SNMP gets, get next, sets, MIB Walks, and get subtree, all in one nice little utility. The program also supports SNMPv3. Just…

There are now application templates for monitoring MySQL replication status * MySQL Replication (Windows) * MySQL Replication (Linux and Unix)

SAM has similar functionality using the ODBC User Experience Monitor in the case of MySQL. The returned value must however be in numeric format, which can be achieved by performing the string match as part of the query and returning a numeric value as the result to SAM. 

You may consider changing the node polling method from WMI to SNMP for nodes that exhibit this behavior.

Nothing as of yet, but there also hasn't been a new release of SAM since this request was logged.

I suggest giving Petr's suggestion below a try. If that doesn't resolve the issue please open a case with support.

In the latest SAM 5.5 beta it is now possible to specify separate and unique credentials for both the SMTP [Send] and POP3/IMAP4/MAPI [Receive] actions in all mail users experience monitors. If you'd like to participate in the latest SAM beta you can sign-up here to download to give it a try.

dfairles‌, please re-open your case with support and post your active case number here. We are thus far unable to reproduce this issue internally and would like to work with you to determine the cause and potentially work towards a resolution.

Hotfix 6 states that it's applicable to additional polling engines, so I'm not sure exactly why you're receiving that error. I would recommend running Active Diagnostics on the polling engines and opening a case with support so we can determine the cause of the issue.