Servers for Windows Release Notes

Servers for Windows Release Notes

2016, May 25 - 14:57 Download

Bug fixes

  • Fixed issue where Windows Server Monitor installation could prevent the .NET Agent from executing or accessing the appropriate registry keys.
2015, November 16 - 13:44

New features

  • Support for AWS EC2 Integration. By installing this release on their AWS Windows servers, users in our AWS beta program can send tags, metadata, and machine status information to the New Relic Servers UI, allowing them to better manage their servers.

Fixes

  • Fixed security bug where unprivileged (non-admin) users can access the server monitor's registry settings
2014, December 2 - 12:30

Bug Fixes:

  • Correctly report CPU utilization for multiple CPU systems.

    Fixed an issue where systems with multiple cores were incorrectly reporting utilization of the first CPU instead of the aggregate of all CPUs.

2014, November 21 - 14:45

Notes:

  • Add ability to set the sampling rate for collecting process metrics.

    This feature is to help users with a known issue concerning very large PIDs. A warning message is logged for users who may need to change the sampling rate. If you see the message "Process sampling is taking over 15 seconds." please contact New Relic support for help.

Bug Fixes:

  • Fix an issue where the Windows Server Monitor would drop data during network outages.

    During a network outage, the server monitor will cache data points and send them to the collector once the network has been restored. Note that restarting the service during the outage will cause metrics to be lost.

2014, November 11 - 16:36

Bug Fixes

  • Provides work-around for an issue where servers with very large PIDs would consume growing amounts of CPU when gather process metrics.
2014, October 20 - 16:25

Notes

  • Set labels for your server directly in your configuration. By setting the labels attribute, you can configure your server to register a set of labels. Labels can be used for filtering, roll-ups, and more to come.
2014, April 29 - 19:55

Notes

Fixes

  • Fixes an issue where the Windows WMI service causes high CPU usage on some systems when data is gathered from the server.
2014, March 25 - 21:42

Fixes

  • Changed service to be delayed start.
  • Fixes an issue where the server monitor would shut down unexpectedly and not successfully restart itself.
  • Fixes an issue where the service would not correctly startup after a server restart.
2014, January 25 - 00:15

Fixes

  • Fixes a bug where memory metrics were not being collected because the memory bank label string was blank.
2014, January 16 - 23:08

Fixes

  • Fix for no memory data appearing in the New Relic user interface.
2013, December 23 - 06:44

Fixes

  • This release will (once again) correctly restart when told to by the New Relic service.
  • In this release we have removed the service dependency on DNS Client. Although we do need to resolve host names we don't have a dependency on that service to run.
  • Adding support for Teamed NICs in 2012 Server and Windows 8.
2013, December 6 - 19:39

New Features

  • New KB articles.

    We're happy to say that we're starting to capture known releases as a series of knowledge base articles. In addition to allowing you to search and browse them we also include links to them in the Windows Event Log. When a known issue is detected and encountered we will write a log entry that references the KB article that you can use to understand and most often fix the underlying issue. We hope that this helps track down and correct the issue as fast as possible.

    To get started browsing these articles please open your browser to our new trouble-shooting section at http://docs.newrelic.com/docs/windows-server-monitoring/

Improvements

  • New logging added

    In this release we've added diagnostics to detect if process performance counters have been disabled. If you're not seeing process metrics then check the event log or our knowledge base for instructions on how to enable this.

Fixes

  • Fix for monitor not reporting the correct version numbers for Windows 8.1 and Windows 2012 R2 Server.

    Previous versions of the monitor would not correctly report the version numbers for operating systems post-Windows 8. This release will now correctly report it as 6.3.xxx

  • Fix for monitor not reporting correct disk space usage.

    A bug in 3.0.101.0 caused the monitor to cache disk space usage instead of updating it periodically. This release now updates and reports the usage accurately.

2013, November 22 - 00:32

Improvements

  • The known issues documentation has been updated to include information regarding our required .NET 4 patch level.

https://docs.newrelic.com/docs/windows-server-monitoring/windows-server-monitor-known-issues

Fixes

  • The WSM service now tries to detect missing but required .NET 4 patches. If the required ones are not installed it will write this information to the Event Log and gracefully shut down.
  • Network adapters that have multiple IP addresses are now supported.
2013, November 8 - 21:03

New Features

  • To make it easier to access logs, the Windows Server Monitor now logs to the Windows Event Log. Also, a custom event viewer view is now installed to make it easier to isolate events.
  • To enhance security, the Windows Server Monitor now connects to New Relic using SSL by default.
  • A custom event viewer view for Windows Server Monitor events is installed to make it easier to see what has been logged to the Event Log.
  • There are now Alerts in RPM for notifying when the monitoring service has not provided metrics (i.e. stopped running) for a given amount of time.

Fixes

  • Server swap memory metrics are now correctly reported.
  • Changes to your license no longer cause the monitoring service to terminate.
  • Network failures no longer cause the monitoring service to terminate.
2012, August 27 - 22:35

The first GA release of Windows Server Monitoring.

This version of the agent is fully compatible with Windows Server 2003 and 2008, and provides monitoring of CPU, Memory, Network IO, and Disk IO, as well as detailed information about process activity.

This release fixes several known issues that were present in pre-release beta versions of the agent, including a small memory leak.