aLTeReGo ✭✭✭✭✭

Have you tried using the Custom Table resource?

Your existing rules in the legacy Win32 Syslog and Traps applications are not migrated to Orion Log Viewer. You will need to recreate these rules manually if you choose to utilize Log Viewer with Orion. For what it's worth, I've done this a few times myself. It took me less than 2min on average to rewrite each rule. While…

To be fair joedissmeyer​ I'm glad to hear that resolved your issue but what you describe should not be occurring. The agent should be performing the same job it would from the Orion server, simply on the agent instead. If you continue to encounter problems with either the HTTP or HTTPS User Experience Monitors and the…

It sounds like the scripts aren't exiting properly. If you enable debug mode on the assigned application you should be able to read the logs to see what's going on with the SSH session. You may also want to configure the idle timeout setting for SSH sessions on the server.

You can accomplish what you're trying to do by changing the "Status When Process is Not Running" to "Not Running" rather than "Down", then create a specific alert for this process when it's "Up", since its normal expected behavior is 'Not Running'.

If you install Log Analyzer, it will fall back to the free Log Viewer after the 30 day evaluation expires.

It looks as though you haven't installed Log Viewer yet. Is that correct?

Correct, that is the SQL query. This query can be run through SQL Studio as shown below if the Orion Report Writer is not available.

Syslog and Trap data collected via the Legacy Syslog & Trap receivers should be purged automatically as part of nightly maintenance based upon their configured retention settings.

Thank you for bringing this to our attention. We'll definitely look into it. Tracking this internally as FB85749.

I just confirmed this report works without issue on SAM 6.2.2. I'm not sure where you're seeing that error or why. Ensure you have placed the file in the "C:\Program Files (x86)\SolarWinds\Orion\Reports" on the Orion server itself. You can then access the report through the Windows Report Writer application, or view the…

The severity level shown by SAM should mirror that of the vSphere client. SAM does not provide the ability to override this status, but you do have the flexibility of controlling the alerts you receive through the Advanced Alert Manager by filtering or requiring the condition to be sustained for a period of time before…

So the alert is triggered and you are notified, but you want to continue to be notified until the condition no longer occurs? E.G. value returns to zero. Is that correct?

Absolutely! In fact, even better as Orion Log Viewer uses Orion's web based alert manager!

The VMWare API is still reporting this disk as being in a degraded state. We've seen this issue reported a few times before and it's relatively easy for support to demonstrate this if you open a case. This issue has been acknowledged by VMware, but I believe the only reliable workaround that exists today is to poll the…

Have you tried starting with any of the following application templates? * Log Parser (PowerShell) * Log Parser (powershell) w/Message Returned * Log Parser (PowerShell).apm-template‌ * Log Parser (VBScript).apm-template * Log Parser (Perl) * Log Parser (PERL) HPUX

If Job Engine results are larger than 80KB (by default) then the results are written temporally to disk to save processing power. Those files are temporary and transitory and do not need to be backed up.

The combination of Network Performance Monitor and Server & Application Monitor should replace NNM and HPOM functionality.

Have you looked through the list of Script Macros? I believe you're looking for the ${USER} and ${PASSWORD} variables.

It is currently not possible to reset SAM's Windows Event Log Monitor based upon a different event. You can however vote for this idea at the link below. *

A virtual hostname is not required in a same subnet HA deployment. It's completely optional. You can instead create a static DNS entry for the VIP if you prefer, or access the Orion web interface using the VIP itself if you'd rather enter the IP address into your browser to access the web interface.

You may need to set thresholds for counters according to your environment. It is recommended to monitor counters for some period of time to understand potential value ranges and then set the thresholds accordingly. For more information, see http://knowledgebase.solarwinds.com/kb/questions/2415. .

What is the make/model of the device you are trying to monitor? This information is available via SAM's Asset Inventory for Dell, HP, and IBM/Lenovo servers.

There are a few different ways to handle this in Orion today. The simplest method is to add date/time filter exclusions to any historical report as pictured below. The other method, which is more flexible is to use the Unmanage Scheduling Utility to unmanage nodes/applications/etc during their maintenance windows on a…

Alerts can be exported individually to XML files. You can also use the Report Writer to create a report for configured alerts, but I have not yet found a way to create a report based on trigger actions.

The template we designed to be applied to all nodes in the cluster, not the VIP so you should alert on any of the Windows Event Log Monitors in the template. You can then include the node name variable as part of the alert so you know which member of the cluster is having issues. In SAM 5.2 we've greatly enhanced the…

What you describe above can easily be accomplished using Custom Properties.

I'm not sure I'm following you. Are you using the Windows Server 2003-2008 templates included in APM? The default template doesn't include monitoring either the "Server" service or the "Computer Browser" service. While the "Server" service is very important, below is the description for the "Computer Browser" service…

The TFTP server is listening on all adapters. If you run (netstat -an | find "69") at a command prompt you should see the following. UDP 0.0.0.0:69 *:* The 0.0.0.0:69 means that UDP port 69 is open on all adapters.

Make sure you're adding the node via WMI, then do a "List Resources" on the node. AppInsight for SQL should be listed. If it is not it may be because the SQL server is part of a cluster. If that's the case the Cluster VIP should be added as a node in Orion.