aLTeReGo ✭✭✭✭✭

If you're finding these Alert Macros are not working for you please verify that the "Property to Monitor" under the "Trigger Condition" tab is set to "APM:Component". Several of these macros are not available for "APM: Application".

I believe the issue is that in the Advanced Alert your selected property to monitor is "APM:Application" and not "APM:Component". When "APM:Component" is selected you will have options for returning the results of multi-value scripts as pictured below.

It may be that as part of the recording you will need to use a logoff method provided by the application to properly terminate the session. Alternatively, if these sessions are reclaimed automatically after a period of time you might ask if the number of connections can be increased, or reduce the number of locations or…

If there is no subscriber then it's likely because the RabbitMQ service can't connect to the other member in the pool. Also note that RabbitMQ is used only for Pub/Sub communication. It is not used at all as temporary storage for monitoring or statistic collection. I recommend you double check that all the appropriate…

It's very likely not a bug, but rather the hardware vendor agent software is still installed and operating on these virtual machines. I would recommend to your client to uninstall Dell OpenManage, HP Insight Manager, or IBM Director agents from those virtual machines, as they're continuing to consume resources while…

You can rename the HTTP component by editing the template itself as pictured below.

Correct, this is functioning as designed. If at the time when the error occurs there is no defined action to take, then no action is performed. Having an action defined that allows for these alerts to be sent in the future does not mean they remain queued up until that time. The only way this would work in your scenario is…

The following post should walk you through the process Understanding Java Remote JMX - Initial Setup/Config Overview There is also an excellent guide available here > Configuring and Integrating JMX.pdf

Hardware Health of Cisco UCS Blade Chassis is a function of NPM, not SAM. To enable UCS monitoring check "UCS manager credentials" under "Additional Monitoring Options" when adding the node as pictured below.

SAM 6.3 Beta 2 is now available which includes a Linux Agent for Node, Volume, Interface, and Application monitoring. This agent should address many of the shortcomings associated with monitoring Linux host via SNMP, up to and including properly calculating volume usage statistics referenced in this thread. If you already…

If it's a Windows host, you'll also want to verify your credentials. You may want to try manually changing one of these nodes over to WMI to test the credentials on this particular host. Another option is to install the Agent on those servers.

Adding, deleting and modifying nodes/interfaces/resources is not Web based, neither is the configuration on the alerting engine. All map related tasks are console as well. Database management and maintenance, backup, syslog alert configuration, and Network Discovery are also not web based. In all much of the product is…

Is it possible that you have something that is archiving your IIS logs? This component will go into an unknown state if it is unable to find the current IIS Log. What is the error message text/description for this component when it goes into an "Unknown" state? Below are two examples of what this might look like.

The following reports should get you pointed in the right direction Current Monitored Applications_Services.OrionReport Credentials Used By APM Component Monitors APM Component Monitors that are not Inheriting from their Original Template APM Component Monitors Whose Credentials are not Inherited from the Original Template

You are correct that the keys must be provided in PEM format. There are a number of online tutorials that outline how to use OpenSSL to convert the certificate from one format to another. There are also a number places online that will do this conversion for you. * SSL Converter - Convert SSL Certificates to different…

Sounds less like a credentials issue than a problem with the definition of the process monitor. The component is stating that the process defined is not running on the node being monitored. I would suggest trying again using the Real-Time Process Explorer instead.

I would recommend polling the ESX host directly rather the though the vCenter. This can be accomplished under the Virtualization settings in Orion. [Settings -> All Settings -> VMware Settings] Select the ESX host and click 'Poll Through' from the top menu and select 'Poll ESX server directly'. This may resolve this issue.

The following reports I posted to the Content Exchange should answer those questions, and probably more. * Credentials Used By APM Component Monitors * Credentials Used By WMI Nodes * APM Component Monitors Whose Credentials are not Inherited from the Original Template * APM Component Monitors that are not Inheriting from…

You haven't inadvertently applied KB3002657 to your servers have you? * RPC and MS KB3002657

SAM 5.0 does not include a hardware health summary resource. This is actually something we're currently working on.In the meantime some customer have opted to create hardware reports and embed these as resources of their summary view. Also, there are out of the box alerts for hardware monitoring which should bubble up any…

Yes, you can monitor your AS/400 using the Comtek AS/400 agent. An example template is available at the link below. * COMTEK AS/400

SolarWinds Failover Engine supports Disaster Recovery deployment configurations.

You can poll the server itself for Hardware Health then you don't need to have duplicate nodes.

This may be a bug with the RPC Fetching Method. Please open a case with support so we can gather diagnostics that will help us determine the cause of the issue.

Have you tried using WMI instead of RPC? Another option if you know this event exists in the event log on one of your servers already is to use the Real-Time Event Log Viewer, select the event, and click "Start Monitoring". When walking through the wizard, the message text will be pre-populated for you already. Simply…

I'm afraid SAM has never shipped a SQL 2000 template. A quick rummage through the Content Exchange only turned up the following. * SQL 2000 Database sizes, with Powershell My recommendation would be to apply one (or both) of the following SQL 2005 templates to see if either of those work at all. I'm afraid I no longer have…

SAM is not OSS, therefore the source code is not publically available.

The permissions outlined within the template are applicable only to Agentless polling methods. The Agent requires no elevated privileges for monitoring once it's installed. 

There is very limited information on this error but from what little I was able to find it sounds like it may be an issue related to impersonation with PowerShell v5. If you are running PowerShell v5 please try and revert back to an earlier version to see if that resolves the issue.

The "Manage as Node" button is only available for individual nodes. By default however all Agents are managed as nodes in Orion without needing to click the "Manage as Node" button under "Manage Agents".