• /
  • EnglishEspañol日本語한국어Português
  • Log inStart now

Node.js agent release notesRSS

July 30, 2014
Node.js agent v1.9.1

Important

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

  • Added a check for invalid characters in the app_name setting.

    The agent will now emit a warning and disable itself if any application name is invalid. Allowed characters are alphanumerics and certain punctuation characters ({}.?!')

  • Router queue time now properly handles floating point values.

  • Fixed a bug where a socket connection could throw a synchronous error and cause the application to crash.

July 24, 2014
Node.js agent v1.9.0

Important

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

  • We now support Cassandra via the node-cassandra-cql driver.

    New database instrumentation means that we can present you with the timing data for how long those queries take. Thanks to Aaron Silvas from GoDaddy for the initial implementation of the Cassandra instrumentation.

  • Router queue time now supports t=<number> in the X-REQUEST-START and X-QUEUE-START headers.

July 18, 2014
Node.js agent v1.8.1

Important

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

  • Agent now tracks metrics for router queue time. In addition to X-REQUEST-START, the agent now supports X-QUEUE-START header times. This metric will show up as "Request Queueing" in the Overview tab.

July 11, 2014
Node.js agent v1.8.0

Important

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

  • General release of proxy support for the agent to connect to New Relic.
    • HTTP/HTTPS support from the newrelic module to the proxy
    • HTTP/HTTPS support from the newrelic module to New Relic.
    • Basic proxy authentication.
    • Allow custom certificates during TLS negotiation.
    • For more information, read our docs here
  • Fix for enabling High-security mode via an environment variable
  • Optimization to allow early garbage collection of TLS slab buffers.

July 2, 2014
Node.js agent v1.7.5

Important

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

June 26, 2014
Node.js agent v1.7.4

Important

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

  • The agent now reports the value of the NODE_ENV environment variable to New Relic.

    This will show up in your Settings -> Environment tab in APM. The data is being collected for debugging and to aid support.

June 20, 2014
Node.js agent v1.7.3

Important

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

  • Support for instrumenting a standalone express 4 router. See issue 154.
  • Set the default log level to info.

June 13, 2014
Node.js agent v1.7.2

Important

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

  • Captured parameters for express, restify, and hapi have been normalized.

    When capture_params is enabled the agent will collect route and query parameters. Previously express and restify only captured route params, and hapi only captured query params. This normalizes the behavior across the frameworks.

  • Fixed an issue with restify instrumentation that caused the agent to always collect route parameters.

    Users of restify who want to continue capturing route (and now query) parameters are advised to enable capture_params.

  • Fixed an issue where circular configs caused the agent to crash.

June 5, 2014
Node.js agent v1.7.1

Important

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

  • Fixed an issue where collected errors did not include captured and custom parameters.
  • Added the environment variable NEW_RELIC_HIGH_SECURITY. This correlates to the high_security setting in your newrelic.js for High-security mode.

May 29, 2014
Node.js agent v1.7.0

Important

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

  • Client side setting of high_security is now supported.

    High-security mode is a feature to prevent any sensitive data from being sent to New Relic. The local setting for the agent must match the server setting in the New Relic APM UI. If there is a mismatch, the agent will log a message and act as if it is disabled. A link to the docs for High-security mode can be found here

    Attributes of high-security mode (when enabled):

    • requires ssl
    • does not allow capturing of parameters,
    • does not allow custom parameters

    The default setting for High-security mode is ‘false’.

    Note: If you currently have high-security mode enabled within the New Relic APM UI, you have to add high_security: true to your local newrelic.js.

  • Fixed a bug in our instrumentation of restify, where if you were using the restify client with express as a web server, req.query would be overridden.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.