New Relic's Windows services integration collects data about the services running on your 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 alerts for services, and more.
Our integration is bundled with the Windows infrastructure agent. If you are monitoring Windows hosts on New Relic, you only need to enable the integration to get Windows services data into our platform.
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, their state, and their status 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.), status (OK, error, degraded), and start mode (auto, manual, etc.), including service metadata.
- See which hosts are running specific Windows services.
- Set alerts based on any Windows services that you are monitoring using New Relic.
- Create dashboards to track your Windows services.
one.newrelic.com > Dashboards: You can use the Windows services integration metrics to create tables for your services.
Our integration is compatible with all Windows versions supported by the New Relic agent.
You must have the New Relic infrastructure agent version 1.12.1 or higher installed on a supported host. The x86 Windows versions are not yet supported.
To install the Windows services integration:
Change the directory to the integrations folder:cd C:\Program Files\New Relic\newrelic-infra\integrations.d\
Copy of the sample configuration file:copy winservices-config.yml.sample winservices-config.yml
winservices-config.ymlfile as described in the configuration settings and save it.
The Windows services integration is bundled with the infrastructure monitoring agent. To update the integration, update the agent to the latest version.
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 is an example of the Windows services integration configuration:
You can create Windows services alerts using NRQL conditions to get notified about status or state changes of the services you wish to monitor. Below are two examples of alert conditions that use Windows services data:
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 sent them to New Relic.
The Windows services integration collects Windows Management Instrumentation (WMI) 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:
Start mode of the service. Possible values are:
State of the service. Possible values are:
Status of the service. Possible values are:
The Windows services integration sends the following metadata to New Relic:
windowsService.displayName: Name of the service as viewed in the services snap-in
windowsService.entityName: Composed of hostname plus service name
windowsService.hostname: Name of the host where the integration is running
windowsService.name: Unique identifier of the service
windowsService.processId: Process identifier of the service
windowsService.runAs: 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).
NULL, the service is logged on under the
LocalSystemaccount or, 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,
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.