Configure Servers for Windows

For the latest, most advanced host monitoring, check out New Relic Infrastructure.

Servers for Windows includes a Configuration utility shortcut in the Windows Start menu's New Relic Server Monitor folder. Use the Configuration utility to:

  • Stop or restart the Servers for Windows monitoring service.
  • Create labels and categories to manage groups of servers.
  • Use SSL when communicating with the New Relic collector.
  • Specify a different logging level.
  • Configure a proxy URL by using the HTTP proxy address, user name, and password.

General settings

Server monitor configuration: Proxy
Windows Start Menu > All Programs > New Relic > Server Monitor > Server Monitor Configuration Tool: Use the configuration tool to stop or restart the monitoring service, manage labels and categories, change network security settings, and other functions.

Field definitions for the configuration utility's General settings include:

  • License key: The 40-character license key provided to you by New Relic.
  • Labels: A dictionary of label names and values for categories that will be applied to the data sent from this agent. May also be expressed as a semicolon delimited string of colon-separated pairs; for example, Environment:Prod;Data Center:Primary.
  • Use SSL: Indicates whether or not to use SSL for communication with the New Relic collector (default: false). Certain rare cases may require you to modify the SSL certificate settings below.

Proxy settings

The configuration tool's Proxy tab provides settings to instruct Servers for Windows to connect to New Relic via HTTP proxy. Possible formats include:

  • Host address: Fully qualified hostname (for example, foo.bar.com)
  • IP address: xxx.xxx.xxx.xxx (for example, 111.222.333.444)

Optional: To specify a port, append a port suffix to the Host address; for example, foo.bar.com:443. If you do not specify a port, it uses the default 80.

Support settings

You can use the Support tab during a support session to help provide diagnostic information and adjust the logging level. Fields include the Collector address, Host name, and Log level.

Increasing the logging level for extended periods of time can result in excessive events being stored in the Windows Event store.

Firewall configuration

Servers for Windows requires your firewall to allow an outgoing connection to New Relic's networks on TCP port 80 (or port 443 if you configure the agent to use SSL). To test the outgoing connection and incoming response, use the built-in Windows tools such as the BITS service in Windows, along with accompanying client-side tools.

Here are some examples, including how to validate the results. After the command runs successfully, mongrel.txt will contain mongrel ==> up (true).

Pre-Windows 7

For versions before Windows 7: Open cmd.exe and type:

bitsadmin /transfer testnr /download http://collector.newrelic.com/status/mongrel

To validate the results, go to C:\path\to\users\home\mongrel.txt.

Windows 7

For Windows 7: Open Windows Powershell and type:

Start-BitsTransfer  -Source http://collector.newrelic.com/status/mongrel -destination mongrel.txt
Post-Windows 7

For versions after Windows 7: Open Windows Powershell and type:

    Start-BitsTransfer  -Source http://collector.newrelic.com/status/mongrel -destination mongrel.txt

For more help

Additional documentation resources include:

Discuss New Relic Servers in the New Relic Online Technical Community! Troubleshoot and ask questions, or discuss Servers for Linux or Servers for Windows in detail.

If you need additional help, get support at support.newrelic.com.