v1.6.2

Changed the default behavior of the PerfCounterReporter Service to include appropriate restart logic to better accommodate Windows Hosts that have transient resource (e.g. network) availability issues at host boot time.

v1.6.1

Added additional network and physical/logical disk counters that are available as a part of PerfCounterReporter's default configuration.

v1.6.0

PerfCounterReporter is now published as a 64-bit application so that it can retrieve performance counters from 64-bit services that do not redundantly publish counters that can be accessed by both 32
and 64 bit applications.

Please see the note in the project's README - https://github.com/signalfx/PerfCounterReporter/blob/master/README.md - if you still need to run PerfCounterReporter on a legacy 32-bit version of Windows.

v1.5.2

Includes new out-of-the-box Network Interface Counters:

\Network Interface()\Bytes Received/sec
\Network Interface()\Bytes Sent/sec
\Network Interface(*)\Current Bandwidth

v1.5.1

Rebuild of the installation package to include additional out-of-the-box performance counters that are very useful for monitoring Microsoft IIS Web Servers

v1.5.0

Added support for non-interactive installs (and uninstalls)

Command line parameters can also now be passed to interactive installs (which simplifies the configuration process and eliminates a post-install step of modifying PerfCounterReporter's configuration file).

v1.0.1

• Fixed a bug that can cause the "\SignalFx\UsedMemory" performance counter
  to potentially never be updated. This causes the value of your Windows Host's "signalfx.usedmemory" metric to always be reported to SignalFx with a zero value.

• Added 2 new system counters to the default counterset to provide a better indicator of overall
  system performance and to help better detect underlying hardware failure situations. The resulting metrics are viewable inside of SignalFx as:

                                    processor.interrupts_sec
                                    system.system_calls_sec
  

NOTE: If you are upgrading to v1.0.1 from a release prior to v1.0.0 please make sure that you read the notes associated with the v1.0.0 release to make sure that you understand the implications of upgrading to a 1.x release.

v.1.0.0

[2016-09-13] v1.0.0: -- Updated .MSI package to include the latest and greatest Metrics.NET.SignalFX.dll file as well as updated IIS performance counters.

---

[2016-09-13] v1.0.0: -- “sf_source” dimension now reported as “host”

In this release, we have updated the name of the dimension that is used to report the hostname of the server being monitored, from “sf_source” to “host”. We did this in order to ensure consistency among SignalFx agents, and in order to clarify the intended meaning of the dimension.

If you are upgrading to PerfCounterReporter v1.0.0 from a previous version, any custom SignalFx charts and detectors that you have built will need to be modified to include the new dimension name. Modify charts, detectors, and dashboards that use data from PerfCounterReporter as follows:

• If a chart or detector contains a plot that uses “sf_source” in a filter or analytics function, change the filter or analytics function of that plot to use values of “host” instead.
  To maintain continuity of metrics from before and after this upgrade, first clone the affected plot, then change “sf_source” to “host” in the new plot. If your chart also contains a timeseries expression that refers to the old plot, clone the expression, then modify any letter references in the clone to refer to the new plot instead of the old one.
• If a dashboard uses “sf_source” in a dashboard variable, create a new dashboard variable that uses “host”. Optionally, delete the dashboard variable that uses “sf_source”.

v0.5.1

Rebuilt the PerfCounterReporter installer with a refreshed Metrics.NET.SignalFX.dll file to pull in recent bug fixes (see the Metrics.NET.SignalFX repo at https://github.com/signalfx/Metrics.NET.SignalFX for more details on these bug fixes)

v0.5.0

Updated dependencies within the .msi to the latest and greatest

The assembly within the .msi is now strong-named

Fixed various issues with the .msi installing and the PerfCounterReporter service starting on 4.6.x versions of .NET Framework