<!--startmeta
custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/collectors/apps.plugin/integrations/windows_services.md"
meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/apps.plugin/metadata.yaml"
sidebar_label: "Windows Services"
learn_status: "Published"
learn_rel_path: "Collecting Metrics/Collectors/Operating Systems"
keywords: ['windows', 'services', 'processes', 'os', 'host monitoring']
message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE"
endmeta-->

# Windows Services


<img src="https://netdata.cloud/img/windows.svg" width="150"/>


Plugin: apps.plugin
Module: services

<img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" />

## Overview

This integration monitors resource utilization grouped by Windows Service.

It auto-discovers running Windows services via the Service Control Manager and groups each service's process tree to aggregate CPU, memory, I/O, and other metrics per service. Processes not belonging to any service are grouped under 'not-services'.

This collector is only supported on the following platforms:

- windows

This collector supports collecting metrics from multiple instances of this integration, including remote instances.


### Default Behavior

#### Auto-Detection

All running Windows services are automatically discovered. No configuration is needed.

#### Limits

The default configuration for this integration does not impose any limits on data collection.

#### Performance Impact

No additional SCM query overhead. The service list is already queried by apps.plugin for process naming. Per-iteration work involves walking parent chains to assign service names.

## Setup


### Prerequisites

No action required.

### Configuration

#### Options

Service charts are enabled by default. Use the `without-services` (or `no-services`) command line option to disable them.



#### via File

There is no configuration file.

##### Examples
There are no configuration examples.



## Alerts

There are no alerts configured by default for this integration.



## Metrics

Metrics grouped by *scope*.

The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.




### Per windows service

These metrics refer to the Windows Service.

Labels:

| Label      | Description     |
|:-----------|:----------------|
| service | The display name of the Windows service. |

Metrics:

| Metric | Description | Dimensions | Unit | windows |
|:------|:------------|:----------|:----|:---:|
| service.cpu_utilization | Windows Service CPU utilization (100% = 1 core) | user, system | percentage | • |
| service.mem_usage | Windows Service memory RSS usage | rss | MiB | • |
| service.vmem_usage | Windows Service virtual memory size | vmem | MiB | • |
| service.mem_page_faults | Windows Service memory page faults | minor | pgfaults/s | • |
| service.swap_usage | Windows Service swap usage | swap | MiB | • |
| service.disk_logical_io | Windows Service disk logical IO | reads, writes | KiB/s | • |
| service.fds_open | Windows Service open handles | handles | fds | • |
| service.processes | Windows Service processes | processes | processes | • |
| service.threads | Windows Service threads | threads | threads | • |
| service.uptime | Windows Service uptime | uptime | seconds | • |
| service.uptime_summary | Windows Service uptime summary | min, avg, max | seconds | • |
