Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v8.5.0 #948

Merged
merged 3 commits into from
Oct 12, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
74 changes: 45 additions & 29 deletions NEWS.md
Original file line number Diff line number Diff line change
@@ -1,37 +1,53 @@
### v8.4.0 (2021-09-28)

### v8.5.0 (2021-10-12)

* Added full support for Fastify v2 and v3. Fastify instrumentation is now GA.
* Removed fastify feature flag.
* Instrumented Fastify routes by wrapping `addHook`.
* Added middleware mounting for fastify v3.
* Fixed capturing of mount point for middleware naming.
* Fixed the WebFramework spec definitions for Fastify middleware and route handlers to properly retrieve the IncomingMessage from a request object.
* Added proper definition to middleware handlers so that the relationship to consecutive middleware and route handler are siblings and not direct children.

* Added experimental instrumentation for the [undici](https://github.com/nodejs/undici) http client behind a feature flag.

To enable undici support, add the following into your config: `{ feature_flag: { undici_instrumentation: true } }`. The support for undici client is Node.js 16.x as it takes advantage of the [diagnostics_channel](https://nodejs.org/dist/latest-v16.x/docs/api/diagnostics_channel.html). Lastly, you must be using [v4.7.0+](https://github.com/nodejs/undici/releases/tag/v4.7.0) of the undici client for any of the instrumentation to work.

Note: There are currently some state issues if requests to an app are made with keep alive and you have multiple undici requests being made in parallel. In this case, set feature_flag: `{ undici_async_tracking: false }` which avoids these state issues at the cost of some broken segment nesting.

### v8.4.0 (2021-09-28)

* **Deprecation Warning**: Cross Application Tracing (CAT) has been deprecated and will be removed in a future major release. For applications that explicitly disable Distributed Tracing (DT) to leverage CAT, we recommend migrating to DT to avoid loss of cross-service visibility.
* Disables CAT by default. You must explicitly enable CAT along with turning off DT.
* Adds a deprecation warning when CAT is enabled and active (DT disabled).

* Adds a deprecation warning when CAT is enabled and active (DT disabled).
* Fixed issue with `clearTimeout` that could result in dropping parent segments or spans.

This bug resulted in some MongoDB calls being dropped from Transaction Traces and Distributed Traces (spans): https://github.com/newrelic/node-newrelic/issues/922.

* Removed warnings from agent tests for `no-var` eslint rule.

* Added support for Cassandra driver v4.0.0 and above.

* Fixed issue where DT headers would not be processed by `transaction-shim.handleCATHeaders()` when CAT was explicitly disabled. This primarily impacts `amqplib` instrumentation.

* Transitioned aws-lambda.test.js to use Tap over Mocha.

* Removed warnings from agent for `no-var` eslint rule.

* Refactored `transaction-shim`, `http` and `http-outbound` to use centralized CAT methods in `util/cat`

* Replaced http-outbound test call to use example.com to avoid unpredictable connection resets.

* Migrated sql query parser tests to tap

This bug resulted in some MongoDB calls being dropped from Transaction Traces and Distributed Traces (spans): https://github.com/newrelic/node-newrelic/issues/922.
* Removed warnings from agent tests for `no-var` eslint rule.
* Added support for Cassandra driver v4.0.0 and above.
* Fixed issue where DT headers would not be processed by `transaction-shim.handleCATHeaders()` when CAT was explicitly disabled. This primarily impacts `amqplib` instrumentation.
* Transitioned aws-lambda.test.js to use Tap over Mocha.
* Removed warnings from agent for `no-var` eslint rule.
* Refactored `transaction-shim`, `http` and `http-outbound` to use centralized CAT methods in `util/cat`
* Replaced http-outbound test call to use example.com to avoid unpredictable connection resets.
* Migrated sql query parser tests to tap
* Added more API usage examples.

* Added a README to the `examples/` folder discussing how to use the examples.

* Fixed `message-shim` test assertion to avoid flakiness based on precision differences(ms vs ns)

* Applied new lint rules barring the use of `var` and preferring the use of `const` wherever possible.

* Added a README to the `examples/` folder discussing how to use the examples.
* Fixed `message-shim` test assertion to avoid flakiness based on precision differences(ms vs ns)
* Applied new lint rules barring the use of `var` and preferring the use of `const` wherever possible.
### v8.3.0 (2021-09-09)

* Enabled Distributed Tracing (DT) by default.
Expand Down
2 changes: 1 addition & 1 deletion package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "newrelic",
"version": "8.4.0",
"version": "8.5.0",
"author": "New Relic Node.js agent team <[email protected]>",
"license": "Apache-2.0",
"contributors": [
Expand Down