Windows Server Metrics to KloudMate Using Host Metrics Receiver

7min
This section explains how to collect metrics from Windows Server and ingest them into KloudMate using Open Telemetry.
In this method, the OpenTelemetry hostmetrics receiver is used. The Host Metrics receiver generates metrics about the host system scraped from various sources. This is intended to be used when the collector is deployed as an agent.
Step 1: Prerequisites:
Ensure that you have a Windows server running. 
Step 2: Install the Open Telemetry Collector on Windows Server
1. Download the OpenTemetry Collector for Windows:
Go to the official Open Telemetry website 
Choose and download the correct version of the OpenTelemetry Collector for Windows. Windows releases are packaged as gzipped tarballs (.tar.gz). Every Collector release includes an otelcol.exe executable that you can run after unpacking. 
2. Run the installer:
Locate the downloaded installer executable 
Right-click on the installer file and select "Run as administrator."
Follow the installation wizard's instructions to complete the installation.
Step 3: Create an OpenTelemetry Configuration YAML File
Create a YAML configuration file using a text editor like Notepad and customize the configuration YAML file based on your requirements. 
Configure the host metrics receiver on the OpenTelemetry configuration file to send metrics. 
YAML
receivers:
  hostmetrics:
    collection_interval: 60s
    scrapers:
      cpu:
        metrics:
          system.cpu.utilization:
            enabled: true
      load:
        cpu_average: true
      memory:
        metrics:
          system.memory.utilization:
            enabled: true
      filesystem:
       # The below file system type only useful with AWS EC2 metrics
       # include_fs_types:  
       #   match_type: strict
       #   fs_types: [ext3, ext4] 
        metrics:
          system.filesystem.usage:
            enabled: true
          system.filesystem.utilization:
            enabled: true

      disk: {}
      network: {}
      process:
        metrics:
          process.cpu.utilization:
            enabled: true
          process.cpu.time:
            enabled: false
        # Mute various errors reading process metrics running locally in docker.
        # Delete for production deployments.
        mute_process_exe_error: true
        mute_process_user_error: true
        mute_process_io_error: true

receivers:
  hostmetrics:
    collection_interval: 60s
    scrapers:
      cpu:
        metrics:
          system.cpu.utilization:
            enabled: true
      load:
        cpu_average: true
      memory:
        metrics:
          system.memory.utilization:
            enabled: true
      filesystem:
       # The below file system type only useful with AWS EC2 metrics
       # include_fs_types:  
       #   match_type: strict
       #   fs_types: [ext3, ext4] 
        metrics:
          system.filesystem.usage:
            enabled: true
          system.filesystem.utilization:
            enabled: true

      disk: {}
      network: {}
      process:
        metrics:
          process.cpu.utilization:
            enabled: true
          process.cpu.time:
            enabled: false
        # Mute various errors reading process metrics running locally in docker.
        # Delete for production deployments.
        mute_process_exe_error: true
        mute_process_user_error: true
        mute_process_io_error: true
﻿
Step 4: Configure the processor part to detect resource information from the host and append or override the resource value in telemetry data with this information.
AWS EC2:
Optional: To retrieve AWS EC2 instance tags along with logs and metrics, you need to associate an IAM role with the EC2 instance that includes the EC2:DescribeTags policy. The processor below needs to be added:
Text
processors:
  batch:
    send_batch_size: 5000
    timeout: 10s

  resourcedetection/ec2:
    detectors:  ["ec2"]
    ec2:
      tags:
        - ^tag1$
        - ^tag2$
        - ^label.*$ 
        - ^Name$

  resource:
    attributes:
      - key: service.name
        action: insert
        from_attribute: ec2.tag.Name
      - key: service.instance.id
        action: insert
        from_attribute: host.id
processors:
  batch:
    send_batch_size: 5000
    timeout: 10s

  resourcedetection/ec2:
    detectors:  ["ec2"]
    ec2:
      tags:
        - ^tag1$
        - ^tag2$
        - ^label.*$ 
        - ^Name$

  resource:
    attributes:
      - key: service.name
        action: insert
        from_attribute: ec2.tag.Name
      - key: service.instance.id
        action: insert
        from_attribute: host.id
﻿
Azure Virtual Machines: 
Text
processors:
  batch:
    send_batch_size: 5000
    timeout: 10s

  resourcedetection/azure:
    detectors: ["azure"]
    azure:
      tags:
        - ^tag1$
        - ^tag2$
        - ^label.*$
        - ^Name$

  resource:
    attributes:
      - key: service.name
        action: insert
        from_attribute: azure.vm.name
      - key: service.instance.id
        action: insert
        from_attribute: host.id
processors:
  batch:
    send_batch_size: 5000
    timeout: 10s

  resourcedetection/azure:
    detectors: ["azure"]
    azure:
      tags:
        - ^tag1$
        - ^tag2$
        - ^label.*$
        - ^Name$

  resource:
    attributes:
      - key: service.name
        action: insert
        from_attribute: azure.vm.name
      - key: service.instance.id
        action: insert
        from_attribute: host.id
﻿
Step 5: Set up the KloudMate Backend on the exporter part of the OpenTelemetry configuration file and configure the pipeline. 
YAML
exporters:
  otlphttp:
    endpoint: 'https://otel.kloudmate.com:4318'
    headers:
      Authorization: xxxxxxxx  # Use the auth key

service:
  pipelines:
    metrics:
      receivers: [hostmetrics]
      processors: [batch, resourcedetection/ec2, resource] # Apply the resourcedetection
      exporters: [otlphttp]

exporters:
  otlphttp:
    endpoint: 'https://otel.kloudmate.com:4318'
    headers:
      Authorization: xxxxxxxx  # Use the auth key

service:
  pipelines:
    metrics:
      receivers: [hostmetrics]
      processors: [batch, resourcedetection/ec2, resource] # Apply the resourcedetection
      exporters: [otlphttp]
﻿
Step 6:  Commands to follow
Run the following command in the command prompt or PowerShell to generate the telemetry data from where otelcol.exe was downloaded. Mention correct path to the  yaml file.
Text
./otelcol.exe –config ‘<path>/otelcol.yaml

./otelcol.exe –config ‘<path>/otelcol.yaml
﻿
﻿
﻿
﻿
Did this page help you?
Windows Server Metrics to KloudMate Using Prometheus Node Exporter
Kubernetes Monitoring With KloudMate