Set up Host Monitoring on Windows

This page describes how to install and configure the Splunk AppDynamics Infrastructure Collector to monitor non-Kubernetes® Windows hosts. The Splunk AppDynamics Infrastructure Collector uses the Cisco AppDynamics Distribution of OpenTelemetry Collector to transport data. 

To configure the Splunk AppDynamics Infrastructure Collector to monitor Kubernetes Windows hosts, see Cisco AppDynamics Collectors Settings.

Before You Begin

Before installing Host Monitoring, ensure that you meet the following requirements:

• You have a supported Windows environment. Host Monitoring has been verified to work with the following Windows environments:

  Windows Software	CPU Architecture
  Windows Server 2016 Windows Server 2019 Windows Server 2022	64-bit x64-based processor
  Windows 10 Pro Windows 11 Pro	64-bit x64-based processor

• You have access to the following ports:
  • 4317 (to receive OTLP data over gRPC)
  • 4318 (to receive OTLP data over HTTP)
  • 8888 (to receive self-telemetry metrics)
  • 13133 (Health Check extension)

  • 55679 (zPages extension)

  • 9182 (Windows Exporter)
    

    

    If these ports conflict with your existing ports, see Configure Listening Ports.

• You have allowlisted the package management URL and the Cisco AppDynamics Distribution of OpenTelemetry Collector endpoint.

Install Host Monitoring for Windows

The instructions to install Host Monitoring for Windows are documented on the Databases and Hosts page of the Cisco Cloud Observability user interface. 

To navigate to the Databases and Hosts user interface page:

1. Log into the Cisco Cloud Observability UI.
2. Use the left-hand navigation panel to navigate to Configure > Databases and Hosts.
3. Follow the instructions on the Databases and Hosts user interface page to install Host Monitoring.

Host Monitoring for Windows installs the following services:

Configuration Options

Cisco AppDynamics Infrastructure Collector

Host Monitoring reads configurations from the following variables set in the C:\Program Files\AppDynamicsAppDynamics Infra Manager\conf\manager_config.yml file:

Cisco AppDynamics Distribution of OpenTelemetry Collector

Host Monitoring reads configurations from the following variable set in the C:\Program Files\AppDynamics\AppDynamics Distribution of OpenTelemetry Collector\otel-config.yaml file:

Update the Configuration File

To update the configuration of a service:

1. Open the configuration file(s) mentioned in Install Host Monitoring for Windows. Update the Configuration Options.

2. Restart the service using the following command: 

   net stop appdinfracol /yes 
   net start appdinfracol /yes 

   BASH

Check the Status of a Service

To check the status of a service, run the following command: 

C:\> sc query <service name>

Configure Listening Ports

By default, the Cisco AppDynamics Distribution of OpenTelemetry Collector listens to the following ports:

• 4317 (to receive OTLP data over gRPC)
• 4318 (to receive OTLP data over HTTP)
• 8888 (to receive self-telemetry metrics)
• 13133 (Health Check extension)
• 55679 for (zPages extension)

If these ports conflict with your existing ports, change the ports by updating the C:\Program Files\AppDynamics\AppDynamics Distribution of OpenTelemetry Collector\otel-config.yaml file. If only local traffic is allowed, the local address 0.0.0.0 can be configured to localhost.

The following snippet displays where to update the ports in the C:\Program Files\AppDynamics\AppDynamics Distribution of OpenTelemetry Collector\otel-config.yaml file:

extensions:
  health_check:
    endpoint: "0.0.0.0:<HEALTH_CHECK_EXTENSION_PORT>"
  zpages:
    endpoint: "0.0.0.0:<ZPAGES_PORT>"

receivers:
  otlp:
    protocols:
      http:
        endpoint: "0.0.0.0:<PORT_FOR_OTLP_HTTP>"
      grpc:
        endpoint: "0.0.0.0:<PORT_FOR_OTLP_GRPC>"

service:
  telemetry:
    metrics:
      address: "0.0.0.0:<PORT_FOR_SELF_TELEMETRY_METRICS>"

Next Steps

When Host Monitoring services are run, they automatically pull metrics associated with the host resources and populate the Observe page with entity-centric pages. You can now Observe Host Monitoring Entities in the Cisco Cloud Observability UI.

This document contains references to third-party documentation. Splunk AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.

Third party names, logos, marks, and general references used in these materials are the property of their respective owners or their affiliates in the United States and/or other countries. Inclusion of such references are for informational purposes only and are not intended to promote or otherwise suggest a relationship between Splunk AppDynamics and the third party.