How Dynatrace monitors Windows Server 2003

While OneAgent continues to offer best-in-class monitoring of Windows environments, operational and security policies within some enterprises don't allow for installation of OneAgent. In addition, some enterprises run older versions of Windows (e.g., Windows Server 2003) that aren't supported by OneAgent. OneAgent-based monitoring of Windows hosts is however always a feasible option—Dynatrace provides remote infrastructure monitoring of Windows hosts via the Windows Management Instrumentation (WMI) ActiveGate extension.

The extension queries each Windows host every minute for key metrics, properties, and events. The ingested data provides Dynatrace with near real-time visibility into host performance and enables us to present actionable insights using automatically generated visualization tools, dashboards, info-graphics, and reports.

Prerequisites

  • Dynatrace SaaS version 1.156 or above
  • ActiveGate version 1.155 or above
  • Windows Server host(s) which support WMI
  • A User account belonging to the Performance Monitor user group

Interested in monitoring your older Windows hosts with Dynatrace?

If you're interested in exploring this monitoring option for your Windows environments, please reach out to your Dynatrace contact or complete this form to receive additional information and next steps.

Installation

ActiveGate Installation (if necessary)

  1. Navigate to Deploy Dynatrace > Set up remote monitoring, select your preferred OS and follow the instructions to install both the ActiveGate and the ActiveGate plugin module

WMI Extension Installation

  1. Obtain the WMI plugin zip file and unzip it to the plugin_deployment directory.
  2. Restart the Dynatrace Remote Plugin Module service.
  3. Return to the ActiveGate installation instructions and click the Upload ActiveGate plugin link at the bottom of the page.
  4. Click the Upload plugin button and upload the unzipped file through the Dynatrace UI.
  5. Enter the endpoint information requested for connecting to WMI hosts:
  • Endpoint name: Meaningful and descriptive name
  • User: A user account that belongs to the “Performance Monitor" user group
  • Password: The password for said account
  • Hostname/IP: Hostname/IP and port of the server. Examples: 192.168.55.180[:1414], 192.168.55.181[:1414]
  • Comma-separated list of the processes to monitor: Comma-separated list of processes to monitor.

WMI

Metrics

The IP address of all network interfaces and the ports used by the services is automatically captured, as are the following metrics:

Properties (per host)

  • Hostname
  • Domain/IP address(es)
  • Uptime
  • Number of logical processors
  • Number of enabled cores
  • Processor name
  • Current/Max clock speed
  • Windows version/build
  • Machine Architecture
  • Manufacturer/Model

Availability (per host)

  • Polling successful (Y/N)

CPU (per host)

  • Total load

Memory (per host)

  • Utilization
  • Per network (per host)
  • Bandwidth
  • Bytes sent/received
  • Sent packets discarded/errors
  • Received packets discarded/errors
  • Output queue length

Per logical disk (per host)

  • Percent free space
  • Free MB
  • Disk read/write latency
  • Disk read/write queue length
  • Disk read/write bytes per second

Processes (max 100 /host)

  • CPU utilization
  • Memory footprint
  • Thread count
  • Page faults
  • IO read/write