New Relic's Windows services integration collects data about the services running on your Microsoft Windows hosts and sends it to our platform. You can check the state and start mode of each service, find out which hosts are running a service, set up for services, and more.
Our integration is bundled with the Windows infrastructure agent. If you're monitoring Windows hosts on New Relic, you only need to enable the integration to get Windows services data into our platform.
Why it matters
Microsoft Windows services are the Windows equivalent of daemons in Unix and Linux: long-running executables that can be started, stopped, paused, and restarted without a graphical interface. Knowing which services are enabled, or their state or health, is essential when monitoring Windows infrastructure.
With our Windows services integration you can:
- Check all your Windows services, their state (running, stopped, etc.), start mode (auto, manual, etc.), and other service metadata.
- See which hosts are running specific Windows services.
- Set alerts based on any Windows services that you are monitoring using New Relic.
- Install the Windows Services Quickstart or create your own to track your Windows services.
one.newrelic.com > All capabilities > Dashboards: You can use the Microsoft Windows services integration metrics to create tables for your services.
Compatibility and requirements
Our integration is compatible with all Windows versions supported by the New Relic agent.
You must have version 1.12.1 or higher for our infrastructure monitoring agent installed on a supported host. The x86 Windows versions are not yet supported.
Install and activate
To install the Windows services integration:
Change the directory to the integrations folder:bash$cd C:\Program Files\New Relic\newrelic-infra\integrations.d\
Copy the sample configuration file:bash$copy winservices-config.yml.sample winservices-config.yml
winservices-config.ymlfile as described in the configuration settings and save it.
Update your integration
The Windows services integration is bundled with the infrastructure monitoring agent. To update the integration, update the agent to the latest version.
Configure the integration
To enable the integration, edit and save the
- Add the name of the services you want to monitor to
By default, no service is included. To include and filter services, you must edit
Also, the configuration option
inventory_source is not compatible with the integration.
Here's an example of the Windows services integration configuration with both a regex pattern matching all services named
win32.* and a direct match for the
Set up an alert
You can create Windows services using NRQL conditions to get notified about state changes of the services you wish to monitor. Here are two examples of alert conditions that use Windows services data:
How it works
To get data from Windows hosts, our Windows services integration uses a reduced version of the Prometheus exporter for Windows, which exposes Prometheus metrics on the port specified in the agent configuration. The integration collects these metrics, transforms them into entities, filters them, and then sends them to New Relic.
The Windows services integration collects Service Functions data using the Windows Prometheus exporter. It then transforms and filters the data before sending it to New Relic.
The Windows services integration provides the following data:
This integration creates dimensional metrics, which return the numeric status supplied by the Win32_Service class. Enumeration of these metrics into readable string values is provided under the
Start mode of the service. Possible values are:
State of the service. Possible values are:
The Windows services integration sends the following metadata to New Relic:
display_name: Name of the service as viewed in the services snap-in.
process_id: Process identifier of the service.
run_as: Account name under which a service runs. Depending on the service type, the format of the account name may be
Username@DomainName(UPN). The value is taken from the
StartNameattribute of the
Win32_Serviceclass, which can be
NULL(in that case, the label is reported as an empty string).
service_name: Unique identifier of the service.
NULL, the service is logged on under the
LocalSystemaccount. For kernel or system-level drive, it runs with a default object name created by the I/O system based on the service name, for example,