Prior to this release, an Eagle client always listens for events emitted by its corresponding service. This release adds a configuration parameter - serviceName.client.listenforevents - to control whether events should be listened for or not. The default value of this parameter is true

Prior to this release, an Eagle client always listens for alerts emitted by its corresponding service. This release adds a configuration parameter - serviceName.client.listenforalerts - to control whether alerts should be listened for or not. The default value of this parameter is true

Prior to this release, an Eagle client always listens for heartbeats emitted by its corresponding service. This release adds a configuration parameter - serviceName.client.listenforheartbeats - to control whether heartbeats should be listened for or not. The default value of this parameter is true.

Note: This parameter only takes effect if the client is not configured to use heartbeats to track service reachability. If the client is configured to use heartbeats to track service reachability, then the client will listen for heartbeats regardless of the value set in this configuration parameter

There are several configuration properties in an Eagle service that start with "nv.service.". This will cause issues when merging configuration file and colocating apps in the same VM. Consequently, this release changes all Eagle service properties should to start with the service name.