aLTeReGo ✭✭✭✭✭

If you can believe it, the advanced alert below doesn't work either. What now?

And who caught you in that situation? I don't wanna talk about. Let's just pretend this never happened

I'm not sure why you are using multiple nested conditions. I would just use a single condition - Trigger when all the following apply. I understand what you're saying but this is part of a larger advanced alert that was working. I copied the alert and removed all the other conditions (pictured above) and the alert still…

The Poller is obviously up since the last database update was 5 seconds ago. The issue as I stated above appears to be a clock sync issue between the poller and the SQL server.

The document at the link below should help you get the MAPI User Experience monitor properly configured. http://www.solarwinds.com/documentation/apm/docs/Configuring_and_Integrating_MAPI.pdf

How are you currently monitoring the mounted status of your mailbox database? Possibly the simplest, most straightforward way would be to use a MAPI User Experience monitor. This will allow you to monitor all the way down to the mailbox in the mailbox database.

Thanks for bringing this to our attention . There appears to be an issue with Thwack that is preventing it from being publicly published. We're looking into it now and hope to have it resolved soon. In the meantime you'll be happy to know that this template is already included with SAM 5.0.1 and greater. If you upgrade to…

It sounds like what your looking for is some sort of SNMP proxy server. This is probably possible using a socks 5 proxy but there is nothing inherent in the Engineers Toolset that will allow you to proxy SNMP request through a centralized server.

You can monitor the server's CPU and have it alert when the CPU is over say 50% for longer than 15min and then send you an email which includes the top processes running that are consuming the most CPU at the time of the alert. These alerts are available out-of-the-box for CPU, Memory, and Virtual Memory.

familyofcrowes, can you open a case with support and post the case number here? I'll ensure your case is handled appropriately. 

You are not getting the brush off. I am looking into this issue. That's terrific news. Now that this issue is in your very capable hands I feel much better.

SNMP Components require that the node is also managed via SNMP and that the same SNMP credentials are used for the node as the SAM SNMP Component Monitor. The SNMP port may be different, but the credentials and therefore the SNMP versions used must be identical.

I managed to solve the table not showing up. Strange as it might sound I had to add the device type to a device type specific view, instead of the default node details view. Not sure why, but it shows up now. The issue that I'm having now is when this table displays on the Web interface, there are two columns displaying…

There is obviously something wrong with WMI on that particular host. It may simply need its WMI repository repaired/rebuilt or it may need certain DLL"s re-registered with the operating system. Either way, the following WMI troubleshooting guide should walk you through repairing the most common WMI related issues. *…

Have you considered adding an additional condition to the trigger only to alert on the 'C:\' drive?

The functionality provided by the "Exchange 2010-2013 Database Availability Group" Template is now natively included as part of AppInsight for Exchange, which is available in the SAM 6.1 release, currently in beta.

Screenshots can be posted as image files (GIF/JPF/PNG) by clicking the "Options" tab of your posting and uploading the image file. It may however be easier to open a case with support so we can troubleshoot this issue properly.

Not all charts have been updated to the new charting library yet. This chart happens to be one of the charts that still utilizes the legacy chart library. We will be updating these resources throughout subsequent releases until all charts are available using the new chart library.

Note that the issue Deltona​ describes above is addressed when using the Linux Agent.

The following post explains how the WIndows operating system chooses the source IP in a VIP configuration * Which IP address is used as the source? - SolarWinds Worldwide, LLC. Help and Support As mesverrum​ stated, I've written a post on how to force the source IP address to use the VIP, using the Windows Scheduled Task…

What version of SAM are you running? There are some issues that were fixed in SAM 6.1.1 specific to the Linux/Unix/Nagios script monitors that may be related to the issue you are experiencing. I recommend downloading SAM 6.1.1 from your customer portal and upgrading to see if that resolves the issue.

In the Administration guide SolarWinds recomends to mantain the sql server on a physical, do you know why?? Is there some problems if both (orion and sql) are in diferents servers?? Quite the contrary. Whenever possible you should separate the functions of the SQL database server, from the Orion application server. I…

Have you tried rebuilding performance counters on the host where they aren't appearing by running "lodctr /r" from the command line?

You actually don't even need the SDK. if you deploy the Agents via Group Policy or through some other software distribution mechanism like SolarWinds Patch Manager or Microsoft SCCM, the Agents will self-register with the Orion server and automatically become managed nodes.

Lukas is partially correct. You would use the Oracle User Experience Monitor in SAM instead of the SQL User Experience monitor your Oracle servers, but SAM does include an out-of-the-box template for monitoring your Oracle database servers.

I'm glad to hear that I'm not alone, but there must be a better way to resolve this then to reinstall. It might be time to open a support ticket. I guess I was just hoping I wouldn't have to, and that someone else had already gone though the trouble and could share the fix. If I get anything back I'll update this posting

Yes, but this would need to be done by creating a component monitor for the process you want monitored using the "Browse for Component Monitors" wizard under [Settings -> SAM Settings] as pictured below. The fields available in the wizard correspond to the same fields seen in Task Manager on the right.

The Agent is likely trying to connect to the SMTP server using an interface that IIS is not bound to, or is not allowed to relay. That would be my guess. Check your SMTP server bindings as well as the relay settings and ensure the IP addresses of the server itself are allowed to relay and that it is bound to the IP address…

The retries are consecutive not concurrent, with no delay. E.G. Once the poll fails, it will immediately retry. 

That is correct.