Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Server & Application Monitor (SAM). Hybrid Cloud Observability and SAM are built on the self-hosted SolarWinds Platform.

SolarWinds Platform 2017.3

This SAM application monitor template assesses the status of Windows services related to SolarWinds Platform servers running SolarWinds Platform 2017.3.

This template is no longer included in fresh installations of SAM but is still available in THWACK. It contains mostly service, process, and counters that don't change much between SolarWinds Platform versions. (Recommended) Use the latest SolarWinds Platform server template instead; see SolarWinds application monitor templates.

Prerequisites

WMI access to the target server.

Credentials

Windows Administrator on the target server.

Component monitors

SolarWinds Platform Module Engine

Returns the CPU and memory usage of the SolarWinds Platform Module Engine service. This service is used to talk to the database.

SolarWinds Information Service

Returns the CPU and memory usage of the SolarWinds Information Service (SWIS) is used by websites to talk to the SolarWinds Platform database. This service is also responsible for how the polling engines talk to each other.

SolarWinds Information Service V3

Returns the CPU and memory usage of the SolarWinds Information service V3. This service is used by websites to talk to the database. This service is also responsible for how the polling engines to each other.

SolarWinds JMX Bridge

Returns the CPU and memory usage of the SolarWinds JMX Bridge service that supports the monitoring of Java application servers such as WebSphere, WebLogic, or Apache Tomcat via JMX.

By default, this monitor is disabled.

JMX monitoring is disabled if FIPS mode is enabled on the SolarWinds Platform server.

SolarWinds Trap Service

Returns the CPU and memory usage of the SolarWinds Trap service. This service is responsible for catching and logging trap events.

File Count Monitor - JET Files

Returns the number of JET files in C:\Windows\Temp. Excessive JET files can block new database connections and halt polling so this monitor should be less than 65,530. These files can be deleted. They usually stay in the system only if an application that uses them accessed a database that crashed so files were not properly deleted.

No more than 65 KB of JET files should be stored in the C:\Windows\Temp folder.

MSMQ Messages in Queue

The total number of Message Queuing messages that currently reside in the selected queue. When the Data Processor receives more results into MSMQ than it can process and pass to the Standard Poller, MSMQ continues growing. The size of MSMQ should be near 0 most of the time. Some spikes may appear, but the Data Processor must be able to clean up the MSMQ quickly, otherwise it may not be able to handle database blackouts or maintenance. (Standard Poller performance is affected by DB performance significantly.)

Before using this counter, you should set the correct instance beginning with: <HOSTNAME>\private$\solarwinds\collector\processingqueue
where <HOSTNAME> is the hostname (without < >) of the target server. For example: APMhost

By default, the instance is set to: <HOSTNAME>\private$\solarwinds\collector\processingqueue\solarwinds.node.hardwarehealth.wmi

All available instances can be found by running the perfmon utility and searching for “Messages in Queue” counter in the “MSMQ Queue” category.

This monitor is disabled by default. Enable through the component monitor settings.

Perfmon DPPL Avg. Time to Process Item

Returns the time needed to process one item. If this number is 1, it means you are able to process one item per second. 0.01 means 100 items per second. The returned value should be as low as possible.

Perfmon DPPL Waiting Items

Returns items in the queue pulled from the message queue but waiting for other results to be processed. This should be less than 40. If this number is holding at or above 40, this may indicate issues concerning DB response time, performance issues, or many down elements.

MSMQ Folder Size

Returns the MSMQ folder size. This monitor should be less than 800 MB. MSMQ maximum size is 1GB. If the 1GB limit is reached, polling will stop working correctly.

To increase the MSMQ size, open Computer Management > Features > Messaging Queuing. Right-click and change MSMQ Messaging 1 GB Limit to 1.5 GB.

See this SolarWinds Success Center article for additional information: Microsoft Message Queue Fills Directory with Orphaned Files.

Process Monitor - SWJobEngineWorker2.exe

Returns the number of Job Engine worker processes and its CPU and memory usage. A value of 10 or lower is acceptable. If the returned value is 100 or greater, there may be problems with jobs hanging.

Job Engine v2: Jobs Queued

Returns the number of jobs waiting for execution due to insufficient resources. This value should be zero at all times.

Job Engine v2: Jobs Lost

Returns the number of lost jobs. This value should be zero at all times.

Job Engine v2: Jobs Running

Returns the number of jobs currently running.

Job Engine v2: Worker Processes

Returns the number of worker processes used. A value of 10 or lower is acceptable. If the returned value is 100 or greater, there may be problems with jobs hanging.

Job Scheduler v2: Average Execution Delay

Returns the average delay, in milliseconds, between the time when the job is supposed to be executed and the time that it actually is executed. This value should be less than 100,000.

Job Scheduler v2: Results Notified Error

Returns the number of errors that occurred when sending the results back. This value should be zero at all times.