Skip to content

Commit

Permalink
Updated changelog for v3.0.0
Browse files Browse the repository at this point in the history
  • Loading branch information
NatalieWolfe committed Mar 6, 2018
1 parent 5a89e45 commit 6b1a2fb
Show file tree
Hide file tree
Showing 2 changed files with 49 additions and 0 deletions.
24 changes: 24 additions & 0 deletions Migration Guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,30 @@
This guide is intended to help with upgrading major versions of the Node Agent.
This information can also be found on [our documentation website][upgrade-doc].

## Upgrading to Agent v3

### Breaking Changes

**Removed SSL configuration**: The agent will always connect to New Relic
servers using TLS to encrypt communications. The `ssl` configuration value and
`NEW_RELIC_USE_SSL` environment value are ignored. If set to any value other
than `true`, a warning is logged and the value is ignored.

**Request parameters now prefixed with `request.parameters.`**: Any request
parameters, such as route (`/user/:userId`) or query (`/user?userId=123`)
parameters will now be prefixed with `request.parameters.` when collected. For
example, the route parameter from `/user/:userId` would be collected as
`request.parameters.userId`.

Any Insights dashboards, Alerts, or other NRQL queries using these attributes
must be updated to look for the new attributes instead.

### Released Feature Flags

* `send_request_uri_attribute`: This feature is no longer configurable.

--------------------------------------------------------------------------------

## Upgrading to Agent v2

### Breaking Changes
Expand Down
25 changes: 25 additions & 0 deletions NEWS.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,29 @@

### 3.0.0 (2018-03-06):

* Removed the `ssl` configuration option.

TLS is now always used in communication with New Relic Servers. The `ssl`
configuration value and `NEW_RELIC_USE_SSL` environment value are no longer
used. Setting either value to anything other than `true` will result in a
warning.

* Security bulletin [NR18-05](https://docs.newrelic.com/docs/accounts-partnerships/new-relic-security/security-bulletins/security-bulletin-nr18-06):

Fixes issue introduced in 2.8.0 where the agent may have captured all
transaction attributes, even with High Security Mode enabled on the account.
This may have included sensitive data attached to transactions.

* All request parameters now prefixed with `request.parameters.`.

Previously request parameters such as route and query parameters were added
as attributes without any name changes. For example `/foo?bar=value` would add
the attribute `bar` to the transaction. Now this attribute would be named
`request.parameters.bar`.

Any Insights dashboards, alerts, or other NRQL queries using these attributes
must be updated to use the new attribute names.

### 2.9.1 (2018-03-05):

* Security bulletin [NR18-05](https://docs.newrelic.com/docs/accounts-partnerships/new-relic-security/security-bulletins/security-bulletin-nr18-06):
Expand Down

0 comments on commit 6b1a2fb

Please sign in to comment.