Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > Server & Application Monitor (SAM) > Server & Application Monitor (SAM) Getting Started Guide > Monitor > Monitor your operating system

Monitor your operating system

Created by Chris.Moyer, last modified by Anthony.Rinaldi_ret on Aug 23, 2016

Views: 1,300 Votes: 1 Revisions: 6

SolarWinds SAM provides a number of preconfigured application templates that you can use to monitor business-critical applications.

SolarWinds recommends deploying a single template, making necessary edits to customize it to your environment, and then deploying the edited template on all similar applications. You can also obtain a template from the thwack community for an application not shipped with SAM.

The following example shows how to apply the Windows Server 2003-2012 template to monitor the operating system.

The Windows Server 2003-2012 template monitors the following components:

  • Service: Distributed Transaction Coordinator
  • Service: Security Accounts Manager
  • Service: Remote Registry
  • Total Available Memory (MB)
  • Page File Usage
  • Disk Queue Length
  • Virtual Memory
  • % Processor Time
  • Service: Server
  • Service: Plug and Play
  • Pages per second
  • Logical Disk: Average Disk Queue Length
  • Physical Disk: Average Disk Queue Length

Before you begin

  • Ensure you have both WMI access and Windows Administrator credentials on the server you want to monitor.

Windows Performance Counters use Remote Procedure Call (RPC) for communication which uses TCP port 445. If testing fails once the template has been assigned to a node, you can use the WMI protocol.

Apply a template to a node

  1. From the Web Console, click Settings > All Settings > SAM Settings.
  2. Under Application Monitor Templates, click Manage Templates.
  3. Locate the template and click Assign to Node.

    File:Success_Center/New_Articles/SAM-Getting-Started-Mindtouch/040/030/Add-template-to-node.png

  4. Select the Windows nodes you want to monitor for the operating system on the left pane, click the green arrow to move it to the right pane, and click Next.

    File:Success_Center/New_Articles/SAM-Getting-Started-Mindtouch/040/030/wilbur-selectnodes.png

  5. Choose the credentials, and click Assign Application Monitors.

    File:Success_Center/New_Articles/SAM-Getting-Started-Mindtouch/040/030/wilbur-selectnodes-1.png

  6. On the Finish panel, click Done.

    It will take several minutes for the initial poll to complete and resources to display data.

View the application data

Click My Dashboards > SAM Summary to view the All Applications resource. The All Applications resource is an excellent method for monitoring and troubleshooting software. When software has been ruled out as the problem, check the hardware health.

File:Success_Center/New_Articles/SAM-Getting-Started-Mindtouch/040/030/wilbur-allapps.png

 
Last modified

Tags

Classifications

Public