[{"agent":"streaming_for_mobile","date":"2026-09-03","downloadLink":null,"version":"4.4.0","features":["Added support for Swift Package Manager.","Added a new AWS MediaTailor server-side ad-insertion (SSAI) tracker for AVPlayer (iOS 12+ and tvOS 12+), offering feature parity with `NRIMATracker`"],"bugs":[{"ios-publish":"Modified retry logic to survive partial pipeline failures."}],"security":[],"supportedOperatingSystems":null,"description":"New features Added support for Swift Package Manager. NRMediaTailorTracker: Added a new AWS MediaTailor server-side ad-insertion (SSAI) tracker for AVPlayer (iOS 12+ and tvOS 12+), offering feature parity with NRIMATracker. Bug Fixes ios-publish: Modified retry logic to survive partial pipeline failures.","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-26-09-03","category":"iOS","eolDate":"2027-09-03"},{"agent":"streaming_for_mobile","date":"2026-08-04","downloadLink":null,"version":"4.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Published to CocoaPods NewRelicVideoAgent 4.3.0 NRAVPlayerTracker 4.3.0 NRIMATracker 4.3.0 New features Added JP region support. (2acc442) Added new QOE attributes. (7b06033) Bug fixes Fixed ad-break time inflating totalPauseTime. (7c41112) Corrected rendition KPIs across views in multi-video sessions. (bd7d6c9) Fixed multiple device UUIDs per viewId. (790c7e6)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-26-08-04","category":"iOS","eolDate":"2027-08-04"},{"agent":"streaming_for_mobile","date":"2026-06-05","downloadLink":null,"version":"4.1.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Published to CocoaPods NewRelicVideoAgent 4.1.4 NRAVPlayerTracker 4.1.4 NRIMATracker 4.1.4 Bug fixes Exposed sendSeekStart/sendSeekEnd on NRVAVideo; auto-detected seek in AVPlayerTracker (34493b4) Fixed NRTrackerPair leaking NSNull sentinel to callers (82ef94f) Implemented partial container sanitization, nil guard, and dead code removal (6aac79f) Read totalPreRollAdTime from CONTENT_START attributes (d565378) Sanitized attribute values at setAttribute storage boundary (7d07298)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-26-06-05","category":"iOS","eolDate":"2027-06-05"},{"agent":"streaming_for_mobile","date":"2026-05-21","downloadLink":null,"version":"4.1.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Published to CocoaPods NewRelicVideoAgent 4.1.3 NRAVPlayerTracker 4.1.3 NRIMATracker 4.1.3","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-26-05-21","category":"iOS","eolDate":"2027-05-21"},{"agent":"streaming_for_mobile","date":"2026-05-20","downloadLink":null,"version":"4.1.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Published to CocoaPods NewRelicVideoAgent 4.1.2 NRAVPlayerTracker 4.1.2 NRIMATracker 4.1.2","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-26-05-20","category":"iOS","eolDate":"2027-05-20"},{"agent":"streaming_for_mobile","date":"2026-04-22","downloadLink":null,"version":"4.1.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Published to CocoaPods NewRelicVideoAgent 4.1.1 NRAVPlayerTracker 4.1.1 NRIMATracker 4.1.1 Bug fixes Add obfuscation rules support (2734ca7) New bitrate metrics added (61cc6d1)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-26-04-22","category":"iOS","eolDate":"2027-04-22"},{"agent":"streaming_for_mobile","date":"2026-03-31","downloadLink":null,"version":"4.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Published to CocoaPods NewRelicVideoAgent 4.1.0 NRAVPlayerTracker 4.1.0 NRIMATracker 4.1.0 New features Added QoE aggregation system and fixed critical timing/playtime bugs (aa761f8) Bug fixes Improved error handling and retry logic in CocoaPods publish workflow (00e4e46)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-26-03-31","category":"iOS","eolDate":"2027-03-31"},{"agent":"streaming_for_mobile","date":"2026-02-17","downloadLink":null,"version":"4.0.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Published to CocoaPods NewRelicVideoAgent 4.0.5 NRAVPlayerTracker 4.0.5 NRIMATracker 4.0.5 Changes Drop bitrate attributes before start event (ad4f9ba) IMA tracker null ad attributes in AD_HEARTBEAT and bitrate unit mismatch (e51b109)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-26-02-17","category":"iOS","eolDate":"2027-02-17"},{"agent":"streaming_for_mobile","date":"2026-02-02","downloadLink":null,"version":"4.0.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Published to CocoaPods: NewRelicVideoAgent 4.0.4 NRAVPlayerTracker 4.0.4 NRIMATracker 4.0.4 What's changed Bug fixes Staging token issue (04956d5)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-26-02-02","category":"iOS","eolDate":"2027-02-02"},{"agent":"streaming_for_mobile","date":"2026-01-20","downloadLink":null,"version":"4.0.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Whats changed iOS fix contentBitrate to report actual video quality in #169 chore(release): 4.0.3 by @github-actions[bot] in #175","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-26-01-20","category":"iOS","eolDate":"2027-01-20"},{"agent":"streaming_for_mobile","date":"2026-01-12","downloadLink":null,"version":"4.0.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Corrected Log attribute spelling (0b90490)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-26-01-12","category":"iOS","eolDate":"2027-01-12"},{"agent":"streaming_for_mobile","date":"2025-11-25","downloadLink":null,"version":"4.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changes Fixed concurrent access crash in NRTimeSinceTable Fixed inaccurate totalPlayTime","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-25-11-25","category":"iOS","eolDate":"2026-11-25"},{"agent":"streaming_for_mobile","date":"2025-10-13","downloadLink":null,"version":"4.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Major features Standalone agent with advanced harvest logic Introduced standalone initialization with advanced harvest logic for improved event processing Added multi-task harvest scheduler for efficient data collection and transmission Implemented priority-based event buffering system New optimized HTTP client with enhanced networking capabilities Enhanced event management New crash-safe event buffer with persistent storage Integrated dead letter handler for failed event recovery Priority event buffer for critical events Default size estimator for optimized memory usage Swift support Updated iOS agent with Swift code support Added Swift example implementation (PiPExampleSwift) Improved Swift interoperability Architecture changes Pod restructuring Breaking Change : Renamed NewRelicVideoCore to NewRelicVideoAgent Updated pod specifications and dependencies Streamlined component factory pattern New core components NRVAVideo - Main video agent interface NRVAVideoConfiguration - Centralized configuration management NRVATokenManager - Enhanced authentication handling NRVAHarvestManager - Centralized harvest orchestration NRVAVideoLifecycleObserver - Video lifecycle management NRVADeviceInformation - Device information collection NRVAErrorExceptionHandler - Centralized error handling Storage & persistence New offline storage capabilities with crash recovery Crash-safe harvest factory for reliable data persistence Integrated dead letter handling for failed events Breaking changes Pod name change : NewRelicVideoCore has been renamed to NewRelicVideoAgent Update your podfile: pod NewRelicVideoAgent Initialization changes : New standalone initialization pattern with configuration objects API changes : Some internal APIs have been refactored for the standalone architecture","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-25-10-13","category":"iOS","eolDate":"2026-10-13"},{"agent":"streaming_for_mobile","date":"2025-04-23","downloadLink":null,"version":"3.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Minor changes The errorName attribute has been renamed to errorMessage.","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-25-04-23","category":"iOS","eolDate":"2026-04-23"},{"agent":"streaming_for_mobile","date":"2025-03-03","downloadLink":null,"version":"3.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features and enhancements New Event Types Introduced VideoAction : This event type represents standard actions related to video playback and interaction. VideoErrorAction : This event type captures errors that occur during video playback, providing detailed insight for troubleshooting. VideoAdAction : Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting. VideoCustomAction : A flexible event type for custom actions and interactions within video applications. Deprecations MobileVideo The MobileVideo event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity. New attributes introduced We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types\nPlease refer to the data model documentation  for more details.\nEvent Types\n• VideoAction: Events triggered by general video interactions, such as starting, pausing, or seeking.\n• VideoAdAction: Events related to ad playback, such as starting, completing, or skipping an ad.\n• VideoErrorAction: Events triggered by errors encountered during video or ad playback.\n• VideoCustomAction: Custom events defined to capture specific actions or interactions beyond default event types. Impact and actions required Transition from MobileVideo : Users currently tracking MobileVideo events should adapt their implementations to utilise the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions. Update Implementations : Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking. Testing & Validation : We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission. Additional information For more details on implementing these changes, refer to the updated documentation and integration guides available here . Should you have any questions or require further assistance, please reach out to our support team.","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-ios-agent-25-03-03","category":"iOS","eolDate":"2026-03-03"},{"agent":"streaming_for_mobile","date":"2026-09-17","downloadLink":null,"version":"5.0.0","features":["THEOplayer integration - add NRTHEOPlayerTracker module and sample app support"],"bugs":["Add error handler","Add Read Me file","Add Rendition shift","Add unit test","Added test cases","**ci:** remove --no-ci from semantic-release to fix major version detection","**ci:** remove --no-ci from semantic-release to fix major version detection","Error code to null","Fix CI failure","Fix CI failure","Fix CI failure","Release tracker issue","Remove config driven code","Remove default code reference","Remove unused code","Remove unused code","Rephrased the statement","Resize the video","Review comments","Review comments","Sample app","Test cases","**theo:** restart session on seek-back after video end","timeSince-session-boundary","Update comment","Update ReadMe file","Update the video url","Updated error handler","Updated error handler part","Updated with config driven"],"security":[],"supportedOperatingSystems":null,"description":"Features THEOplayer integration - add NRTHEOPlayerTracker module and sample app support Bug fixes Add error handler Add Read Me file Add Rendition shift Add unit test Added test cases ci:  remove --no-ci from semantic-release to fix major version detection ci:  remove --no-ci from semantic-release to fix major version detection Error code to null Fix CI failure Fix CI failure Fix CI failure Release tracker issue Remove config driven code Remove default code reference Remove unused code Remove unused code Rephrased the statement Resize the video Review comments Review comments Sample app Test cases theo:  restart session on seek-back after video end timeSince-session-boundary Update comment Update ReadMe file Update the video url Updated error handler Updated error handler part Updated with config driven","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-26-09-17","category":"Android","eolDate":"2027-09-17"},{"agent":"streaming_for_mobile","date":"2026-08-31","downloadLink":null,"version":"4.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Features sample-app:  show a LIVE badge instead of a countdown for live streams sample-app:  support direct manifest URL playback and mock-server testing Bug Fixes exoplayer:  report contentIsLive and omit contentDuration for live streams mediatailor:  append newly-reported ads when a tracking-built avail grows (fd2b5fd ), closes #2  #3 mediatailor:  centralise trailing-segment sessionId extraction mediatailor:  classify how the tracking endpoint was resolved mediatailor:  correct DASH cue offset and give HLS breaks a stable id mediatailor:  derive tracking URL from implicit-session DASH playlist path mediatailor:  derive tracking URL from implicit-session HLS playlist path mediatailor:  describe pending implicit-session tracking URL as deferral mediatailor:  emit AD_ERROR when tracking fetch fails silently mediatailor:  expose creativeId-first primary key for per-ad metrics mediatailor:  harden schedule merge against zombie breaks and pod drift mediatailor:  keep manifest pod boundaries when tracking ad count disagrees mediatailor:  let EXT-X-DATERANGE override an earlier trackingUrl guess mediatailor:  make playhead poll interval configurable at construction mediatailor:  match growing-avail ads by start time when adId is absent mediatailor:  match manifest breaks by id, gate MISSING_AVAIL_START once mediatailor:  paginate NextToken within one poll instead of across polls mediatailor:  parse tracking-event beacons with ad-start-relative timing mediatailor:  pod endTimeMs must not exceed its enclosing break mediatailor:  prune viewed avails from the live schedule mediatailor:  read HLS tracking URL from EXT-X-DATERANGE when advertised mediatailor:  rename segmentPrefix to canonical adSegmentPrefix mediatailor:  require unanimous representation agreement for DASH ad periods mediatailor:  revert tracking requests from POST back to GET mediatailor:  round-trip NextToken across tracking polls mediatailor:  stabilise avail identity across live window rotations mediatailor:  surface avails missing startTimeInSeconds as an error mediatailor:  surface pods appended after the playhead left their window mediatailor:  treat empty avails as no-fill instead of firing AD_START","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-26-08-31","category":"Android","eolDate":"2027-08-31"},{"agent":"streaming_for_mobile","date":"2026-08-04","downloadLink":null,"version":"4.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added JP region support. (e97c6ca) Bug fixes Aligned totalPauseTime with the iOS clock model and stopped emitting totalTimeSwitchedDown. (924c7b9) Classified startup and playback errors by content-started state, for iOS parity. (a6b3288) Corrected CONTENT_DROPPED_FRAMES event fields and fixed the underlying ANR root cause. (a5afc73) Deduplicated consecutive identical download-rate samples. (e9b6d1f) Emitted a fresh totalPlaytime value in QOE_AGGREGATE. (af065d6) Excluded only ad time from startupTime, for iOS parity. (9321ac8) Recorded the final QoE event into the crash-safe buffer at CONTENT_END. (e1d3ae1) Removed an unused classpath. (f729768) Removed an unused dependency. (0bdd95b) Removed an unused plugin. (fa11838) Replaced the global harvestCycleNumber gate with a per-tracker gate. (9e19faf) Updated a variable name. (72de035) Updated the allowlist for QOE_AGGREGATE context attributes, for iOS parity. (dd1d3ef) Updated the bitrate timer to use the isPlaying transition. (011ade3)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-26-08-04","category":"Android","eolDate":"2027-08-04"},{"agent":"streaming_for_mobile","date":"2026-07-13","downloadLink":null,"version":"4.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"4.3.1  (2026-07-13) Bug Fixes Fixed an issue where CSAI preroll operations inadvertently dropped CONTENT_START events. (948f229 )","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-26-07-14","category":"Android","eolDate":"2027-07-13"},{"agent":"streaming_for_mobile","date":"2026-05-21","downloadLink":null,"version":"4.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added the AWS MediaTailor server-side ad insertion (SSAI) tracker for DASH and HLS streams. (caf8f7c) Bug fixes Removed trust-all SSL bypass in MediaTailor sample (92ad555)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-26-05-21","category":"Android","eolDate":"2027-05-21"},{"agent":"streaming_for_mobile","date":"2026-04-22","downloadLink":null,"version":"4.1.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added obfuscation rules (f756c78) Added qoeHarvestCycle (aa4940c)  (0218d31) Added timeSinceRequested, timeSinceStarted to QoE event payload (1f627cf) Added QoeProvider (ed48dee) Update Changed QoE architecture (7913826) Updated bitrate name (928d3af) Updated function name (42a842e) Updated name to contentSegmentDownloadBitrate and contentNetworkDownloadBitrate (e1a3dc9) Updated calculation of startup time and average bitrate (371da00) Updated harvestCycle to AtomicInteger (0d550d2) Updated condition for sending QoE events (f307de9) Bug fixes Added fallback for ad bitrate (3077faa) Added final QoE event at content end (f151a21) Implemented thread-safe QoE generation and real-time totalPlaytime calculation (e53e6f7) Implemented thread-safe QoE generation using attribute caching (43d21cd) Implemented thread-safe QoE with real-time metrics and immediate final QoE (a506f66)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-26-04-22","category":"Android","eolDate":"2027-04-22"},{"agent":"streaming_for_mobile","date":"2026-03-31","downloadLink":null,"version":"4.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added beta release workflow for JitPack from the stable-beta branch (6317416)  (94475c6) Updated beta release workflow (aa77e9e)  (131dd23) Update Added bitrate (7bb2d07) Renamed QoE playback failure attributes to error (825779c) Used getActualBitrate function (ba7b922) Bug fixes Fixed regional collector URLs (ac2811b) Fixed staging credentials (7187413) Reverted use of getOrDefault (5cb62a6) Triggered HEARTBEAT at elapsed time 0 (fb40db3)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-26-03-31","category":"Android","eolDate":"2027-03-31"},{"agent":"streaming_for_mobile","date":"2026-02-10","downloadLink":null,"version":"4.0.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Regional collector URLs, drop bitrate attributes before start, HEARTBEAT  timing, and build fixes (e717dda)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-26-02-10","category":"Android","eolDate":"2027-02-10"},{"agent":"streaming_for_mobile","date":"2026-01-20","downloadLink":null,"version":"4.0.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Replace bitrate calculation to use video quality instead of download speed (b676954) Update media3 from 1.1.0 to 1.2.0 for Android 14 compatibility (320d92b)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-26-01-20","category":"Android","eolDate":"2027-01-20"},{"agent":"streaming_for_mobile","date":"2025-12-18","downloadLink":null,"version":"4.0.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Build issues codeql (#70)  (32f4438) updated sample app's custom attribute (9054208)","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-25-12-18","category":"Android","eolDate":"2026-12-18"},{"agent":"streaming_for_mobile","date":"2025-11-28","downloadLink":null,"version":"4.0.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Update Fixed CONTENT_DROPPED_FRAMES event volume issue It does not include any code changes, It fixes the version inconsistency","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-25-11-28","category":"Android","eolDate":"2026-11-28"},{"agent":"streaming_for_mobile","date":"2025-11-27","downloadLink":null,"version":"4.0.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Update Fixed CONTENT_DROPPED_FRAMES event volume issue","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-25-11-27","category":"Android","eolDate":"2026-11-27"},{"agent":"streaming_for_mobile","date":"2025-09-15","downloadLink":null,"version":"4.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Update Enriched custom event with attributes like content *, view *, timeSince *","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-25-09-15","category":"Android","eolDate":"2026-09-15"},{"agent":"streaming_for_mobile","date":"2025-08-01","downloadLink":null,"version":"4.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Update Introduced Android Video Agent with Self-Harvesting Capabilities","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-25-08-01","category":"Android","eolDate":"2026-08-01"},{"agent":"streaming_for_mobile","date":"2025-07-09","downloadLink":null,"version":"3.0.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Update Improved calculation logic for contentBitrate Bug fixes Fixed the totalPlayTime attribute","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-25-07-09","category":"Android","eolDate":"2026-07-09"},{"agent":"streaming_for_mobile","date":"2025-05-02","downloadLink":null,"version":"3.0.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Added ErrorCode and ErrorName as new attributes","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-25-05-02","category":"Android","eolDate":"2026-05-02"},{"agent":"streaming_for_mobile","date":"2025-03-06","downloadLink":null,"version":"3.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Added method to set, userId for ads","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-25-03-05","category":"Android","eolDate":"2026-03-06"},{"agent":"streaming_for_mobile","date":"2025-03-06","downloadLink":null,"version":"3.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features and enhancements New Event Types Introduced VideoAction : This event type represents standard actions related to video playback and interaction. VideoErrorAction : This event type captures errors that occur during video playback, providing detailed insight for troubleshooting. VideoAdAction : Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting. VideoCustomAction : A flexible event type for custom actions and interactions within video applications. Deprecations MobileVideo The MobileVideo event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity. New attributes introduced We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types, Please refer to the data model documentation  for more details. Impact and actions required Transition from PageAction : Users currently tracking PageAction events should adapt their implementations to utilize the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions. Update Implementations : Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking. Testing & Validation : We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission. Additional information For more details on implementing these changes, refer to the updated documentation and integration guides available here . Should you have any questions or require further assistance, please reach out to our support team.","slug":"docs/release-notes/streaming-mobile-release-notes/streaming-android-agent-25-03-04","category":"Android","eolDate":"2026-03-06"},{"agent":"streaming_for_browser","date":"2026-08-11","downloadLink":null,"version":"4.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added optional automatic rendition/quality-level change tracking: integrates with the videojs-contrib-quality-levels plugin (when present) to report quality transitions along with the previous and new bitrates, with a graceful fallback when the plugin isn't loaded.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-videojs-26-08-11","category":"Video JS","eolDate":"2027-08-11"},{"agent":"streaming_for_browser","date":"2026-06-19","downloadLink":null,"version":"4.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Highlights Explicit opt-in for AWS MediaTailor , with full support for custom CDN domains . New config.ad.type API to choose between CSAI  and SSAI  (DAI, MT) ad tracking — no more URL-based guessing for SSAI. End-to-end logging through nrvideo.Log, with active detection mode logged at startup. Features MediaTailor custom CDN support Replaced URL-based auto-detection with explicit opt-in. Enabled the tracker via mediatailor: true (or mediatailor: { trackingUrl, adSegmentPrefix }), supporting both default AWS hostnames and custom CDN domains. Added MT_DEFAULT_AD_SEGMENT_PATH (/tm/) constant for AWS-recommended CDN ad-segment path; ad segments rewritten to a custom CDN domain under /tm/ are detected automatically. Updated isMediaTailorSegment() to check the default AWS segments hostname, the /tm/ path, and an optional customer-supplied adSegmentPrefix. Threaded adSegmentPrefix through HLS (VHS) and DASH manifest parsing. Added explicit session initialization via mediatailor: { trackingUrl } for POST /v1/session/ flows. Ad tracking configuration Introduced config.ad.type to control ad tracker selection. Exposed AD_TRACKING constant with CSAI  (flat value covering IMA / Brightcove IMA / Freewheel / generic) and SSAI  sub-types (DAI, MT). Required an explicit sub-type for SSAI — each platform needs its own SDK and cannot be auto-detected. Mapped SSAI.MT to imply mediatailor: true. Added a fallback to CSAI auto-detection with a warning when config.ad.type is unset (backward compatible for v4.1.2 users). Co-located segmentPrefix and trackingUrl under config.ad. Added DaiAdsTracker to static exports. Logging improvements Exposed VideojsTracker.Log as a static so UMD callers can set log level. Added logging of the active ad segment detection mode at tracker startup. Added logging of the matched ad segment detection path on the first ad break (once per session). Added logging of which CSAI framework was auto-detected (BrightcoveIma / IMA / Freewheel / generic). Replaced console.log/warn/error with nrvideo.Log across MediaTailor files. Bug fixes Fixed buffer end handling in tracker. Fixed register-plugin.js silently dropping the options object and not forwarding it to the TrackerJS constructor. Documentation Updated the README and SSAI docs for custom CDN support, clarified when trackingUrl and adSegmentPrefix overrides are needed, and cleaned up sessionId references. Corrected adSegmentPrefix references to config.ad.segmentPrefix in the SSAI troubleshooting docs. Upgrade from 4.1.x No breaking changes for CSAI users.  If config.ad.type is unset, the tracker still auto-detects CSAI frameworks (with a one-time warning). MediaTailor users must opt in explicitly.  Replace any URL-pattern reliance with one of: mediatailor: true (default AWS hostnames + /tm/ path) mediatailor: { trackingUrl, adSegmentPrefix } (custom CDN / explicit session init) config.ad.type: AD_TRACKING.SSAI.MT If you previously passed adSegmentPrefix at the top level, move it to config.ad.segmentPrefix.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-videojs-26-06-19","category":"Video JS","eolDate":"2027-06-19"},{"agent":"streaming_for_browser","date":"2026-05-13","downloadLink":null,"version":"4.1.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Highlights Added MediaTailor SSAI tracker initialization on loadstart after source load detection. Added DAI stream manager support through the stream-manager event. Improved bitrate reporting with: Playback bitrate (AVERAGE-BANDWIDTH/BANDWIDTH) Manifest max bitrate Segment download bitrate Network throughput bitrate Improvements Refined ad and content event handling to avoid duplicate or incorrect content events while ads are active for following events: Pause/Resume Seek Start/End Buffer Start Improved end-of-content handling for ad-enabled playback paths during IMA and Freewheel scenarios. Added safer fallback logic for tech wrappers (Hls.js, Shaka, contrib-hls) when bitrate data is unavailable in VHS. Technical notes Tracker metadata and playback context methods remain aligned with Video.js/Brightcove integrations: Retrieves the title, ID, and duration from mediainfo when available. Retrieves source and rendition data from the active tech component when available. Updated the Listener registration and unregistration to include ad and stream manager lifecycle events.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-videojs-26-05-13","category":"Video JS","eolDate":"2027-05-13"},{"agent":"streaming_for_browser","date":"2025-11-21","downloadLink":null,"version":"4.0.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Removed github token (f5f9ade)","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-videojs-25-11-21","category":"Video JS","eolDate":"2026-11-21"},{"agent":"streaming_for_browser","date":"2025-10-21","downloadLink":null,"version":"4.0.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Content Bitrate detection enhancement We've significantly improved the getBitrate() method with comprehensive Video.js technology support: Key improvements VHS (Video HTTP Streaming) API support : Added native support for HLS and DASH content bitrate detection Enhanced bandwidth calculation : Implemented audio + video bitrate combination for accurate total bandwidth reporting Extended tech support : Added fallback support for popular streaming libraries: Shaka Player HLS.js DASH.js Improved reliability : Enhanced bitrate detection accuracy across different streaming technologies Dynamic bitrate updates : Fixed issue where bitrate values remained static throughout video playback","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-videojs-25-10-21","category":"Video JS","eolDate":"2026-10-21"},{"agent":"streaming_for_browser","date":"2025-09-26","downloadLink":null,"version":"4.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Ad Bitrate for CSAI and DAI Added methods to calculate Google IMA Ad bitrate for CSAI and DAI","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-videojs-25-09-26","category":"Video JS","eolDate":"2026-09-26"},{"agent":"streaming_for_browser","date":"2025-09-02","downloadLink":null,"version":"4.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Feature Standalone agent Decoupled from Browser agent : The video agent now operates independently with its own harvesting logic. This separation reduces overhead and ensures that video data is collected and sent to New Relic without being tied to the browser agent's data collection schedule.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-videojs-25-09-02","category":"Video JS","eolDate":"2026-09-02"},{"agent":"streaming_for_browser","date":"2025-06-09","downloadLink":null,"version":"3.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Enhancements Publishing to npm : The package can now be published to npm, making it easily accessible. Build Distribution formats : Added cjs, esm, and umd builds to the dist folder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-videojs-25-06-09","category":"Video JS","eolDate":"2026-06-09"},{"agent":"streaming_for_browser","date":"2025-04-27","downloadLink":null,"version":"3.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Key changes Error reporting update : The errorName attribute, previously used for identifying error description, has been deprecated. The errorMessage attribute is now the standard for conveying detailed error descriptions. Please update any monitoring or logging systems that rely on error information to utilize the errorMessage attribute going forward. Upgrade notes Users who rely on the errorName attribute for error analysis should plan to migrate to the errorMessage attribute to ensure continued functionality and access to detailed error information.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-videojs-25-04-27","category":"Video JS","eolDate":"2026-04-27"},{"agent":"streaming_for_browser","date":"2025-04-15","downloadLink":null,"version":"3.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features & enhancements New event types introduced VideoAction : This event type represents standard actions related to video playback and interaction. VideoErrorAction : This event type captures errors that occur during video playback, providing detailed insight for troubleshooting. VideoAdAction : Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting. VideoCustomAction : A flexible event type for custom actions and interactions within video applications. Deprecations PageAction The PageAction event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity. New attributes introduced We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types, refer to the data model documentation  for more details. Impact & actions required Transition from PageAction : Users currently tracking PageAction events should adapt their implementations to utilize the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions. Update implementations : Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking. Testing & validation : We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission. Additional information For more details on implementing these changes, refer to the updated documentation and integration guides available here . Should you have any questions or require further assistance, please reach out to our support team.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-videojs-25-03-05","category":"Video JS","eolDate":"2026-04-15"},{"agent":"streaming_for_browser","date":"2026-08-06","downloadLink":null,"version":"5.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Updated the bundled @newrelic/video-core dependency to v5.0.1, adding Japan(JP) region collector support for Vega/Fire TV tracking.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-shaka-26-08-11","category":"Shaka","eolDate":"2027-08-06"},{"agent":"streaming_for_browser","date":"2026-03-09","downloadLink":null,"version":"4.0.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"This release introduces three new bitrate metrics for granular playback observability, QoE (Quality of Experience) support, and Shaka Player 5.x compatibility while maintaining backward compatibility with Shaka 4.x. New bitrate metrics Three new attributes are now available to provide deeper insight into streaming performance: Attribute Source Description contentManifestBitrate stats.streamBandwidth Total variant bitrate (video + audio) as declared in the manifest (Indicated Bitrate). contentMeasuredBitrate stats.estimatedBandwidth Estimated network bandwidth measured by Shaka's ABR algorithm (Observed Bitrate). contentDownloadBitrate (bytesDownloaded × 8) / playTime Effective download throughput across all downloaded media. Additionally, contentBitrate uses track.videoBandwidth (video-only bitrate) to differentiate it from other metrics that report combined video and audio bandwidth. Quality of Experience (QoE) support QoE aggregate events are now supported via video-core. Enable them by setting qoeAggregate: true in the config: The following KPIs are tracked automatically: KPI Description startupTime Time from content request to content start (ms). peakBitrate Maximum contentBitrate observed during playback. averageBitrate Weighted average bitrate across the session. hadStartupFailure true if a content error occurred before content started. hadPlaybackFailure true if a content error occurred during playback. totalRebufferingTime Total time spent rebuffering (ms). rebufferingRatio Rebuffering time as a percentage of total playtime. totalPlaytime Total content playtime (ms). numberOfErrors Total number of errors during the session. Shaka Player 5.x compatibility The tracker is now compatible with both Shaka Player 4.x and 5.x: getPlayerVersion() resolves version across both major versions. onError() handles both Shaka player errors (e.detail) and HTML video element errors (e.target.error). Sample files updated for Shaka 5.x (removed deprecated shaka.polyfill.installAll(), updated player instantiation). Upgrade guide Run the following following to update: To enable QoE, add qoeAggregate: true to your config options as shown above. Dependencies Requires @newrelic/video-core v4.1.1 or later for QoE support.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-shaka-26-03-09","category":"Shaka","eolDate":"2027-03-09"},{"agent":"streaming_for_browser","date":"2026-02-18","downloadLink":null,"version":"4.0.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed contentBitrate to accurately report stream bitrate Issue:  The contentBitrate attribute used estimatedBandwidth (the network capacity estimate) as its primary source, which didn't accurately represent the actual bitrate of the playing video stream. Solution:  Updated the bitrate calculation to prioritize streamBandwidth from Shaka Player statistics, which provides the actual content bitrate of the current video variant as defined in the manifest. Impact:  The contentBitrate attribute correctly reports the bitrate (in bits per second) of playing video stream rather than the estimated network bandwidth. This provides more accurate telemetry data for video quality monitoring and analytics. Technical details Changed the priority order in getContentBitratePlayback() method Uses the stats.streamBandwidth as the primary source for content bitrate Updated the DATAMODEL.md documentation to reflect the accurate definition","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-shaka-26-02-18","category":"Shaka","eolDate":"2027-02-18"},{"agent":"streaming_for_browser","date":"2025-11-17","downloadLink":null,"version":"4.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Enhancements Improved error logging Improved error logging by mapping Shaka errors to the following attributes: errorCode, errorPlatformCode, errorMessage, errorStackTrace, errorSeverity. This enhancement ensures cleaner, more structured error data in New Relic by extracting only the essential error attributes from Shaka Player errors, removing unwanted properties like the data array. Updates Fixed CONTENT_ERROR Event Attached the error EventListener to the player instead of its tag, following Shaka's specifications, to fix the CONTENT_ERROR event.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-shaka-25-11-17","category":"Shaka","eolDate":"2026-11-17"},{"agent":"streaming_for_browser","date":"2025-09-02","downloadLink":null,"version":"4.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Feature Standalone Agent Decoupled from Browser agent : The video agent now operates independently with its own harvesting logic. This separation reduces overhead and ensures that video data is collected and sent to New Relic without being tied to the browser agent's data collection schedule.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-shaka-25-09-02","category":"Shaka","eolDate":"2026-09-02"},{"agent":"streaming_for_browser","date":"2025-06-09","downloadLink":null,"version":"3.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Enhancements Publishing to npm : The package can now be published to npm, making it easily accessible. Build Distribution formats : Added cjs, esm, and umd builds to the dist folder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-shaka-25-06-09","category":"Shaka","eolDate":"2026-06-09"},{"agent":"streaming_for_browser","date":"2025-04-27","downloadLink":null,"version":"3.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"This release of the New Relic Shaka Tracker includes a change to error reporting. Key changes Error reporting update : The errorName attribute, previously used for identifying error description, has been deprecated. The errorMessage attribute is now the standard for conveying detailed error descriptions. Please update any monitoring or logging systems that rely on error information to utilize the errorMessage attribute going forward. Upgrade notes Users who rely on the errorName attribute for error analysis should plan to migrate to the errorMessage attribute to ensure continued functionality and access to detailed error information.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-shaka-25-04-27","category":"Shaka","eolDate":"2026-04-27"},{"agent":"streaming_for_browser","date":"2025-02-23","downloadLink":null,"version":"3.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features & enhancements New event types introduced VideoAction : This event type represents standard actions related to video playback and interaction. VideoErrorAction : This event type captures errors that occur during video playback, providing detailed insight for troubleshooting. VideoAdAction : Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting. VideoCustomAction : A flexible event type for custom actions and interactions within video applications. Deprecations PageAction The PageAction event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity. New attributes introduced We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types, refer to the data model documentation  for more details. Impact & actions required Transition from PageAction : Users currently tracking PageAction events should adapt their implementations to utilize the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions. Update Implementations : Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking. Testing & Validation : We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission. Additional information For more details on implementing these changes, refer to the updated documentation and integration guides available here . Should you have any questions or require further assistance, please reach out to our support team.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-shaka-25-02-23","category":"Shaka","eolDate":"2026-02-23"},{"agent":"streaming_for_browser","date":"2026-08-06","downloadLink":null,"version":"5.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Updated the bundled @newrelic/video-core dependency to v5.0.1, adding Japan (JP) region collector support for Vega/Fire TV tracking.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-html5-26-08-11","category":"HTML5","eolDate":"2027-08-06"},{"agent":"streaming_for_browser","date":"2026-07-29","downloadLink":null,"version":"5.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"What's changed feat: Add Vega Video Monitoring support by @rajeevkumar-nr in https://github.com/newrelic/video-html5-js/pull/58 Release/06 jul2026 by @rajeevkumar-nr in https://github.com/newrelic/video-html5-js/pull/59 feat: Update html5 tracker version by @rajeevkumar-nr in https://github.com/newrelic/video-html5-js/pull/61 Full Changelog : https://github.com/newrelic/video-html5-js/compare/v4.1.2...v5.0.0","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-html5-26-07-31","category":"HTML5","eolDate":"2027-07-29"},{"agent":"streaming_for_browser","date":"2026-06-29","downloadLink":null,"version":"4.1.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"What's changed chore: release updated by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/39 Fix/workflow by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/40 chore: add smart release detection and improve workflow triggers by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/41 fix: buffer end fix by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/44 Release/25 may2026 by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/45 chore: add release notes docs PR workflow by @ametku in https://github.com/newrelic/video-html5-js/pull/46 chore: release workflow updated by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/49 fix: address docs reviewer comments on release notes PR format by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/52 chore: trigger release-notes-docs-pr after release creation by @ametku in https://github.com/newrelic/video-html5-js/pull/56 chore(release): v4.1.2 by @github-actions[bot] in https://github.com/newrelic/video-html5-js/pull/50 New Contributors @github-actions[bot] made their first contribution in https://github.com/newrelic/video-html5-js/pull/50 Full Changelog : https://github.com/newrelic/video-html5-js/compare/v4.1.1...v4.1.2","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-html5-26-07-28","category":"HTML5","eolDate":"2027-06-29"},{"agent":"streaming_for_browser","date":"2026-04-17","downloadLink":null,"version":"4.1.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"What's changed Documentation README Overhaul:  Restructured and expanded README with comprehensive installation guides, usage examples, best practices, configuration options, API reference, and support channels. Improvements Attributes Validation:  Updated validation logic for custom attributes to enforce correctness at the tracker level. Custom Attributes Limit:  Added an enforced limit on the number of custom attributes that can be sent per event, preventing unexpected payload sizes. Installation Full changelog","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-html5-26-07-02","category":"HTML5","eolDate":"2027-04-17"},{"agent":"streaming_for_browser","date":"2025-10-05","downloadLink":null,"version":"4.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Feature Added IMA Ad tracking capability Improved Ad tracking capability for the agent with IMA ad tracking.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-html5-25-10-05","category":"HTML5","eolDate":"2026-10-05"},{"agent":"streaming_for_browser","date":"2025-09-02","downloadLink":null,"version":"4.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Feature Standalone agent Decoupled from Browser agent : The video agent now operates independently with its own harvesting logic. This separation reduces overhead and ensures that video data is collected and sent to New Relic without being tied to the browser agent's data collection schedule.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-html5-25-09-02","category":"HTML5","eolDate":"2026-09-02"},{"agent":"streaming_for_browser","date":"2025-06-09","downloadLink":null,"version":"3.1.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Enhancements Publishing to npm : The package can now be published to npm, making it easily accessible. Build Distribution formats : Added cjs, esm, and umd builds to the dist folder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-html5-25-06-09","category":"HTML5","eolDate":"2026-06-09"},{"agent":"streaming_for_browser","date":"2025-04-15","downloadLink":null,"version":"3.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features & enhancements New event types introduced VideoAction : This event type represents standard actions related to video playback and interaction. VideoErrorAction : This event type captures errors that occur during video playback, providing detailed insight for troubleshooting. VideoAdAction : Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting. VideoCustomAction : A flexible event type for custom actions and interactions within video applications. Deprecations PageAction The PageAction event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity. New attributes introduced We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types, refer to the data model documentation  for more details. Impact & actions required Transition from PageAction : Users currently tracking PageAction events should adapt their implementations to utilize the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions. Update implementations : Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking. Testing & validation : We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission. Additional information For more details on implementing these changes, refer to the updated documentation and integration guides available here . Should you have any questions or require further assistance, please reach out to our support team.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-html5-25-04-15","category":"HTML5","eolDate":"2026-04-15"},{"agent":"streaming_for_browser","date":"2026-08-06","downloadLink":null,"version":"5.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Updated the bundled @newrelic/video-core dependency to v5.0.1, adding Japan(JP) region collector support for Vega/Fire TV tracking.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-dashjs-26-08-11","category":"Dash JS","eolDate":"2027-08-06"},{"agent":"streaming_for_browser","date":"2026-02-18","downloadLink":null,"version":"4.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"What's new This release introduces three new bitrate metrics providing comprehensive quality analysis for MPEG-DASH streaming, along with important improvements to existing bitrate calculations and dash.js v4/v5 compatibility. New features New bitrate metrics contentManifestBitrate: Maximum combined (video + audio) bitrate from the MPD manifest. Represents the highest possible stream variant available. contentMeasuredBitrate: Network estimated by the player's Adaptive BitRate (ABR) algorithm, based on measured download throughput. Use this metric to analyze ABR decision-making. contentDownloadBitrate: Effective download throughput calculated from video segment request data (bytesDownloaded × 8 / downloadTime). This Provides real-time network performance monitoring. Changes Updated bitrate calculations contentBitrate: Returns the video-only  bitrate from the active track and excludes audio. Previous versions included combined bitrate. contentRenditionBitrate: Returns the combined video and audio bandwidth  of the active rendition to provide a complete quality picture. Compatibility improvements getDashBitrate(): Fixed v4 compatibility issue. Version check now occurs before calling v5-only APIs, preventing errors on dash.js v4.x installations. getManifestBitrate(): Introduced a smart version detection that uses getRepresentationsByType() on dash.js v5+ and falls back to getBitrateInfoListFor() on v4.x. Bug fixes Removed duplicate getPlayhead() method definition Removed console.log statement from getTrack() error handler Bitrate metrics overview Attribute Type Description contentBitrate Video-only Bitrate of the currently active video track contentRenditionBitrate Combined Video + audio bandwidth of active rendition contentManifestBitrate Maximum Highest quality variant from MPD manifest contentMeasuredBitrate Estimated ABR algorithm bandwidth estimate contentDownloadBitrate Real-time Effective download throughput","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-dashjs-26-03-16","category":"Dash JS","eolDate":"2027-02-18"},{"agent":"streaming_for_browser","date":"2026-02-18","downloadLink":null,"version":"4.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Improved contentBitrate calculation Issue : The contentBitrate attribute reported the target bitrate from the manifest instead of the actual measured throughput during playback. Fix : Updated the bitrate calculation method to use getAverageThroughput() from dash.js. This captures the measured average throughput, providing a more accurate, real-time representation of the content consumption rate during playback. Implementation details Primary logic : Uses player.getAverageThroughput('video') to retrieve measured throughput Fallback logic : Uses manifest bitrate if throughput measurement is unavailable Improves accuracy of video quality monitoring and analytics Impact : More accurate bitrate reporting in New Relic video monitoring Better visibility into actual network conditions and video quality Improved debugging capabilities for playback issues","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-dashjs-26-02-18","category":"Dash JS","eolDate":"2027-02-18"},{"agent":"streaming_for_browser","date":"2025-09-02","downloadLink":null,"version":"4.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Feature Standalone agent Decoupled from Browser agent : The video agent now operates independently with its own harvesting logic . This separation reduces overhead and ensures that video data is collected and sent to New Relic without being tied to the browser agent's data collection schedule.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-dashjs-25-09-02","category":"Dash JS","eolDate":"2026-09-02"},{"agent":"streaming_for_browser","date":"2025-06-09","downloadLink":null,"version":"3.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Enhancements Publishing to npm: The package can now be published to npm, making it easily accessible. Build Distribution formats : Added cjs, esm, and umd builds to the dist folder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-dashjs-25-06-09","category":"Dash JS","eolDate":"2026-06-09"},{"agent":"streaming_for_browser","date":"2025-04-22","downloadLink":null,"version":"3.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"This release of the New Relic Dash.js tracker includes important compatibility updates and a change to error reporting. Key changes Dash.js player compatibility : This version has been tested and confirmed to be fully compatible with the latest release of the Dash.js Player, ensuring seamless integration and accurate tracking. Error reporting update : The errorName attribute, previously used for identifying error description, has been deprecated. The errorMessage attribute is now the standard for conveying detailed error descriptions. Please update any monitoring or logging systems that rely on error information to utilize the errorMessage attribute going forward. Upgrade notes Users who rely on the errorName attribute for error analysis should plan to migrate to the errorMessage attribute to ensure continued functionality and access to detailed error information.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-dashjs-25-04-22","category":"Dash JS","eolDate":"2026-04-22"},{"agent":"streaming_for_browser","date":"2025-03-05","downloadLink":null,"version":"3.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features & enhancements New event types introduced VideoAction: This event type represents standard actions related to video playback and interaction. VideoErrorAction: This event type captures errors that occur during video playback, providing detailed insight for troubleshooting. VideoAdAction: Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting. VideoCustomAction: A flexible event type for custom actions and interactions within video applications. Deprecations PageAction The PageAction event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity. New attributes introduced We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types, refer to the data model documentation  for more details. Impact & actions required Transition from PageAction : Users currently tracking PageAction events should adapt their implementations to utilize the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions. Update implementations : Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking. Testing & validation : We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission. Additional information For more details on implementing these changes, refer to the updated documentation and integration guides available here . Should you have any questions or require further assistance, please reach out to our support team.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-dashjs-25-03-05","category":"Dash JS","eolDate":"2026-03-05"},{"agent":"streaming_for_browser","date":"2025-09-02","downloadLink":null,"version":"4.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Feature Standalone agent Decoupled from Browser Agent : The video agent now operates independently with its own harvesting logic. This separation reduces overhead and ensures that video data is collected and sent to New Relic without being tied to the browser agent's data collection schedule.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-bitmovin-25-09-02","category":"Bitmovin","eolDate":"2026-09-02"},{"agent":"streaming_for_browser","date":"2025-06-09","downloadLink":null,"version":"3.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Enhancements Publishing to npm : The package can now be published to npm, making it easily accessible. Build Distribution formats : Added cjs, esm, and umd builds to the dist folder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-bitmovin-25-06-09","category":"Bitmovin","eolDate":"2026-06-09"},{"agent":"streaming_for_browser","date":"2025-04-27","downloadLink":null,"version":"3.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"This minor release of the New Relic Bitmovin Tracker includes important change to error reporting. Key changes Error reporting update : The errorName attribute, previously used for identifying error description, has been deprecated. The errorMessage attribute is now the standard for conveying detailed error descriptions. Please update any monitoring or logging systems that rely on error information to utilize the errorMessage attribute going forward. Upgrade notes Users who rely on the errorName attribute for error analysis should plan to migrate to the errorMessage attribute to ensure continued functionality and access to detailed error information.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-bitmovin-25-04-27","category":"Bitmovin","eolDate":"2026-04-27"},{"agent":"streaming_for_browser","date":"2025-03-05","downloadLink":null,"version":"3.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features & enhancements New event types introduced VideoAction: This event type represents standard actions related to video playback and interaction. VideoErrorAction: This event type captures errors that occur during video playback, providing detailed insight for troubleshooting. VideoAdAction: Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting. VideoCustomAction: A flexible event type for custom actions and interactions within video applications. Deprecations PageAction The PageAction event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity. New attributes introduced We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types, refer to the data model documentation  for more details. Impact & actions required Transition from PageAction : Users currently tracking PageAction events should adapt their implementations to utilize the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions. Update implementations : Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking. Testing & validation : We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission. Additional information For more details on implementing these changes, refer to the updated documentation and integration guides available here . Should you have any questions or require further assistance, please reach out to our support team.","slug":"docs/release-notes/streaming-browser-release-notes/streaming-browser-agent-bitmovin-25-02-23","category":"Bitmovin","eolDate":"2026-03-05"},{"agent":"pipeline_control_gateway","date":"2026-07-28","downloadLink":null,"version":"2.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features and improvements Upgraded the embedded OpenTelemetry Collector from v0.139.0 to v0.156.0, incorporating the latest upstream components and resolving several CVEs flagged by vulnerability scanning. Migrated the gateway runtime to a hardened distroless/Alpine base image, with Docker base images now pinned by digest for reproducible, tamper-resistant builds. Upgraded to Go 1.25 and refreshed the golang.org/x/crypto dependency. Updated metering to retain the first data point in each series. Fixes Added nil-safety checks to prevent potential panics. Prevented an unintended overwrite of the trace_id string value. Security updates The gateway container now runs as a non-root user (UID 65532) by default, reducing its privilege footprint. The gateway now listens on the unprivileged port 8080 instead of 80. The Kubernetes Service, ingress, and Gloo upstream definitions are all updated to match. If you reference the gateway service port directly, update it to 8080. The gateway now masks sensitive values, such as license keys and API keys, in the logs it emits. The gateway now fails fast when the license key is missing or invalid. Applied additional security hardening and dependency fixes.","slug":"docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-26-07-28","eolDate":"2027-07-28"},{"agent":"pipeline_control_gateway","date":"2026-05-29","downloadLink":null,"version":"2.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Configuration-only mode (without Flux) You can now install and operate Pipeline Control gateway without requiring Flux controllers in your cluster. In this mode, New Relic continues to manage your pipeline configuration (sampling, filtering, transforms) automatically through the UI, while you manage gateway infrastructure (scaling, versions) manually via Helm. This reduces the permissions footprint from cluster-admin to namespace-scoped ConfigMap access only, making it suitable for security-restricted and compliance-driven environments. A built-in config-watcher sidecar automatically detects configuration changes pushed from the UI and restarts gateway pods — no external operators (such as Stakater Reloader) required. For installation instructions, refer to Install gateway without Flux . DaemonSet deployment mode Added support for deploying the gateway as a Kubernetes DaemonSet (one pod per node) instead of a Deployment with HPA. This is useful for environments that require node-level telemetry processing or consistent per-node resource allocation. Enable DaemonSet mode by setting daemonset.enabled: true in your Helm values. The DaemonSet mode also supports the config-watcher sidecar and customConfigMap for configuration-only installations. DaemonSet and Deployment modes are mutually exclusive — the chart uses conditional guards to ensure only one mode is active at a time.","slug":"docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-26-05-29","eolDate":"2027-05-29"},{"agent":"pipeline_control_gateway","date":"2026-05-13","downloadLink":null,"version":"2.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Multi-fleet support You can now create and manage multiple gateway fleets within a single organization. This allows separate business units or environments (for example, prod vs. staging) to maintain independent sampling, filtering, and transformation rules. Easily navigate between different configurations using the new fleet selector dropdown in the Pipeline Control UI. Updated YAML schema Migrated to a streamlined configuration that removes signal-specific nesting (for example, logs:, spans:) in favor of a direct rules array, making configurations flatter and easier to read. For filter processors, the new schema supports an explicit context field. This enables more precise targeting of data sub-types, such as metric datapoints  and span events . Improved deployment UX The new deployment page now automatically fills in default values for the deployment name and description, significantly reducing the manual steps required to ship changes. Added a side-by-side configuration diff preview for transform processors. This allows you to compare your new YAML logic against the current version before finalizing a deployment.","slug":"docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-26-05-13","eolDate":"2027-05-13"},{"agent":"pipeline_control_gateway","date":"2026-02-13","downloadLink":null,"version":"2.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Pipeline Control gateway release notes - v2.0.1 Bug fixes Fix for EU environment Resolved an issue affecting Pipeline Control Gateway deployment and operation in EU environments. This fix ensures proper connectivity and data routing for EU-based instances.","slug":"docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-26-02-13","eolDate":"2027-02-13"},{"agent":"pipeline_control_gateway","date":"2026-02-12","downloadLink":null,"version":"2.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"This release has issues with EU environment deployment and operation. Please use version 2.0.1. Pipeline Control gateway release notes - v2.0.0 Updated to OpenTelemetry Collector v0.139.0 This release is based on OpenTelemetry Collector v0.139.0, bringing the latest stability improvements and features from the upstream project. This upgrade enables new data processing capabilities not available in previous gateway versions. New processor capabilities Added three new processors that give you control over your telemetry data before it leaves your infrastructure: Sampling processor : Reduce data volume with probabilistic and conditional sampling rules Filter processor : Drop entire records or specific attributes based on OTTL boolean conditions Transform processor : Add, modify, or delete attributes using OpenTelemetry Transformation Language (OTTL) These processors can be chained together to create sophisticated data processing pipelines for metrics, events, logs, and traces. Enhanced configuration options Redesigned UI : New form-based interface for creating and managing processor rules without writing YAML Enhanced YAML configuration : Support for OTTL-based processor configuration Improved documentation structure Comprehensive guides for each processor type with OTTL examples and use cases Clear distinction between gateway rules (in your infrastructure) and cloud rules (in New Relic's infrastructure) Expanded troubleshooting resources for gateway installation, health monitoring, and data flow issues Reorganized information architecture for easier navigation","slug":"docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-26-02-12","eolDate":"2027-02-12"},{"agent":"pipeline_control_gateway","date":"2025-09-01","downloadLink":null,"version":"1.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Pipeline Control Gateway Release Notes - v1.2.0 Upgrade OpenTelemetry Collector From 0.109.0 to 0.131.0 We have upgraded the internal OpenTelemetry Collector from version 0.109.0 to 0.131.0. This significant update includes numerous key improvements and bug fixes, providing a more robust and stable platform.\nFor a complete list of changes, please refer to the OpenTelemetry Collector release notes .","slug":"docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-09-01","eolDate":"2026-09-01"},{"agent":"pipeline_control_gateway","date":"2025-08-05","downloadLink":null,"version":"1.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Pipeline Control Gateway Release Notes - v1.1.0 Support for SQL trace and transaction trace data Implemented a new functionality to selectively drop data and attributes from SqlTrace and TransactionTrace events using drop rules. Security updates Addressed vulnerabilities in the golang.org/x/net package, including a cross-site scripting issue and an HTTP Proxy bypass related to IPv6 Zone IDs. Upgraded to Go 1.24 and the following dependencies are updated to enhance security and incorporate recent fixes: golang.org/x/net to v0.38.0 golang.org/x/sys to v0.31.0 golang.org/x/text to v0.23.0 Support for new functions Added support for several new functions in NRQL drop rule queries. You can now use the following functions: aparse() floor() getField() hourOf() numeric() round() string() substring() weekdayOf() mod() dimensions()","slug":"docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-08-05","eolDate":"2026-08-05"},{"agent":"pipeline_control_gateway","date":"2025-04-02","downloadLink":null,"version":"1.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Support for Pipeline Control gateway 1.0.0 New Relic Pipeline Control is the data management component of New Relic Control that helps filter and discard low-value data prior to ingestion into the New Relic Platform. It consists of an agent called the Pipeline Control gateway that's deployed in your environment. You can create NRQL-based rules to discard unwanted data before it exits your environment. To know more about Pipeline Control gateway, refer to the Pipeline Control documentation .","slug":"docs/release-notes/pipeline-control-gateway-release-notes/pipeline-control-gateway-25-04-02","eolDate":"2026-04-02"},{"agent":"nrdot","date":"2026-09-15","downloadLink":"https://github.com/newrelic/nrdot-collector-releases/releases/tag/2.5.0","version":"2.5.0","features":["Host use case verified to work with `nrdot-collector:2.5.0`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Features Host use case verified to work with nrdot-collector:2.5.0","slug":"docs/release-notes/nrdot-release-notes/nrdot-host-2-5-0","category":"Host Monitoring","eolDate":"2027-09-15"},{"agent":"nrdot","date":"2026-09-09","downloadLink":"https://github.com/newrelic/nrdot-collector-releases/releases/tag/2.4.3","version":"2.4.3","features":["Host use case verified to work with `nrdot-collector:2.4.3`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Features Host use case verified to work with nrdot-collector:2.4.3","slug":"docs/release-notes/nrdot-release-notes/nrdot-host-2-4-3","category":"Host Monitoring","eolDate":"2027-09-09"},{"agent":"nrdot","date":"2026-09-02","downloadLink":"https://github.com/newrelic/nrdot-collector-releases/releases/tag/2.4.2","version":"2.4.2","features":["Host use case verified to work with `nrdot-collector:2.4.2`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Features Host use case verified to work with nrdot-collector:2.4.2","slug":"docs/release-notes/nrdot-release-notes/nrdot-host-2-4-2","category":"Host Monitoring","eolDate":"2027-09-02"},{"agent":"nrdot","date":"2026-09-01","downloadLink":"https://github.com/newrelic/nrdot-collector-releases/releases/tag/2.4.1","version":"2.4.1","features":["Host use case verified to work with `nrdot-collector:2.4.1`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Features Host use case verified to work with nrdot-collector:2.4.1","slug":"docs/release-notes/nrdot-release-notes/nrdot-host-2-4-1","category":"Host Monitoring","eolDate":"2027-09-01"},{"agent":"nrdot","date":"2026-08-05","downloadLink":"https://github.com/newrelic/nrdot-collector-releases/releases/tag/2.0.0","version":"2.0.0","features":["Host use case verified to work with `nrdot-collector:2.0.0`"],"bugs":["Renamed configuration nodes `cumulativetodelta` to `cumulative_to_delta` following the component rename in `v0.157.0`","Disabled `system.cpu.logical.count` in host config","Removed `system.cpu.utilization` mean aggregation rule from host config"],"security":[],"supportedOperatingSystems":null,"description":"Features Host use case verified to work with nrdot-collector:2.0.0 Bug fixes Renamed configuration nodes cumulativetodelta to cumulative_to_delta following the component rename in v0.157.0The original name cumulativetodelta remains available as a deprecated alias. Disabled system.cpu.logical.count in host configThe v0.157.0 update to receiver/host_metrics enabled this metric by default. This change restores the previous behavior. Removed system.cpu.utilization mean aggregation rule from host configThe v0.157.0 update to receiver/host_metrics changed its default behavior to aggregate system.cpu.utilization by mean, rendering the removed rule redundant.","slug":"docs/release-notes/nrdot-release-notes/nrdot-host-2-0-0","category":"Host Monitoring","eolDate":"2027-08-05"},{"agent":"nrdot","date":"2026-07-17","downloadLink":"https://github.com/newrelic/nrdot-collector-releases/releases/tag/1.21.0","version":"1.21.0","features":["Host use case verified to work with `nrdot-collector:1.21.0`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Features Host use case verified to work with nrdot-collector:1.21.0","slug":"docs/release-notes/nrdot-release-notes/nrdot-host-1-21-0","category":"Host Monitoring","eolDate":"2027-07-17"},{"agent":"nrdot","date":"2026-07-15","downloadLink":"https://github.com/newrelic/nrdot-collector-releases/releases/tag/1.20.0","version":"1.20.0","features":["Host use case verified to work with `nrdot-collector:1.20.0`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Features Host use case: Verified compatibility with nrdot-collector:1.20.0","slug":"docs/release-notes/nrdot-release-notes/nrdot-host-1-20-0","category":"Host Monitoring","eolDate":"2027-07-15"},{"agent":"nrdot","date":"2026-07-06","downloadLink":"https://github.com/newrelic/nrdot-collector-releases/releases/tag/1.19.0","version":"1.19.0","features":["Host use case verified to work with `nrdot-collector:1.19.0`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Features Host use case verified to work with nrdot-collector:1.19.0","slug":"docs/release-notes/nrdot-release-notes/nrdot-host-1-19-0","category":"Host Monitoring","eolDate":"2027-07-06"},{"agent":"nrdot","date":"2026-06-15","downloadLink":"https://github.com/newrelic/nrdot-collector-releases/releases/tag/1.17.0","version":"1.17.0","features":["Host use case verified to work with `nrdot-collector:1.17.0`","Replaced `hostmetrics` with `host_metrics`, `resourcedetection` with `resource_detection` and `metricstransform` with `metrics_transform` due to deprecations."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Features Validates that the host use case works correctly with nrdot-collector:1.17.0. Replaced hostmetrics with host_metrics, resourcedetection with resource_detection, and metricstransform with metrics_transform due to deprecations.\nThe hostmetricsreceiver, resourcedetectionprocessor, and metricstransformprocessor changed their metadata.yaml :: type identifiers to use snake_case, which changed how they are referenced in the configuration.","slug":"docs/release-notes/nrdot-release-notes/nrdot-host-1-17-0","category":"Host Monitoring","eolDate":"2027-06-15"},{"agent":"nrdot","date":"2026-05-14","downloadLink":"https://github.com/newrelic/nrdot-collector-releases/releases/tag/1.15.1","version":"1.15.1","features":["Host use case verified to work with `nrdot-collector:1.15.1`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Features Host use case verified to work with nrdot-collector:1.15.1","slug":"docs/release-notes/nrdot-release-notes/nrdot-host-1-15-1","category":"Host Monitoring","eolDate":"2027-05-14"},{"agent":"nrdot","date":"2026-05-05","downloadLink":"https://github.com/newrelic/nrdot-collector-releases/releases/tag/1.14.0","version":"1.14.0","features":["Host use case verified to work with `nrdot-collector:1.14.0`","Replaced `filelog` with `file_log` in config due to deprecation."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Features Host use case verified to work with nrdot-collector:1.14.0 Replaced filelog with file_log in config due to deprecation.The filelogreceiver has changed its metadata.yaml::type from filelog to file_log which defines how it gets referenced in the config.","slug":"docs/release-notes/nrdot-release-notes/nrdot-host-1-14-0","category":"Host Monitoring","eolDate":"2027-05-05"},{"agent":"nrdot","date":"2026-04-30","downloadLink":"https://github.com/newrelic/nrdot-collector-releases/releases/tag/1.12.0","version":"1.12.0","features":["Host use case verified to work with `nrdot-collector:1.12.0`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog First dedicated release notes for the 'Host Monitoring'  use case which are scoped to relevant changes in the configuration or nrdot-collector. The nrdot-collector  will continue to bundle the config necessary to power this use case. However, with nrdot-collector supporting more and more use cases, we want to provide additional release notes that are more easily conusamble for someone using NRDOT for a specific purpose like Host Monitoring. Features Host use case verified to work with nrdot-collector:1.12.0","slug":"docs/release-notes/nrdot-release-notes/nrdot-host-1-12-0","category":"Host Monitoring","eolDate":"2027-04-30"},{"agent":"nrdot","date":"2026-09-15","downloadLink":null,"version":"2.5.0","features":["Bump otel component versions from v0.158.0 to v0.160.0","Bump `nrmysqlreceiver`, `nroracledbreceiver`, `nrpostgresqlreceiver` and `nrsqlserverreceiver` to v0.160.0"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features Bump otel component versions from v0.158.0 to v0.160.0 (#670) Bump nrmysqlreceiver, nroracledbreceiver, nrpostgresqlreceiver and nrsqlserverreceiver to v0.160.0 (#670) For the list of changes to these components, refer to their changelog .","slug":"docs/release-notes/nrdot-release-notes/nrdot-2-5-0","category":"Collector","eolDate":"2027-09-15"},{"agent":"nrdot","date":"2026-09-09","downloadLink":null,"version":"2.4.3","features":[],"bugs":["Fixed CVE-2026-84445"],"security":[],"supportedOperatingSystems":null,"description":"Changelog Bug fixes CVE-2026-84445 (#668)","slug":"docs/release-notes/nrdot-release-notes/nrdot-2-4-3","category":"Collector","eolDate":"2027-09-09"},{"agent":"nrdot","date":"2026-09-02","downloadLink":null,"version":"2.4.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changelog Bug Fixes CVE-2026-84304 (#665)","slug":"docs/release-notes/nrdot-release-notes/nrdot-2-4-2","category":"Collector","eolDate":"2027-09-02"},{"agent":"nrdot","date":"2026-09-01","downloadLink":null,"version":"2.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changelog Bug Fixes CVE-2026-56854 (#663)","slug":"docs/release-notes/nrdot-release-notes/nrdot-2-4-1","category":"Collector","eolDate":"2027-09-01"},{"agent":"nrdot","date":"2026-08-25","downloadLink":null,"version":"2.4.0","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features Bump nrmysqlreceiver, nroracledbreceiver, nrpostgresqlreceiver and nrsqlserverreceiver to v0.158.3 (#658) For the list of changes to these components, refer to their changelog .","slug":"docs/release-notes/nrdot-release-notes/nrdot-2-4-0","category":"Collector","eolDate":"2027-08-25"},{"agent":"nrdot","date":"2026-08-21","downloadLink":null,"version":"2.3.0","features":["Added nrpostgresqlreceiver, nrmysqlreceiver, and sqlqueryreceiver to nrdot-collector"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features Add nrpostgresqlreceiver, nrmysqlreceiver, and sqlqueryreceiver to nrdot-collector. (#655)","slug":"docs/release-notes/nrdot-release-notes/nrdot-2-3-0","category":"Collector","eolDate":"2027-08-21"},{"agent":"nrdot","date":"2026-08-19","downloadLink":null,"version":"2.2.0","features":["Added nrpostgresqlreceiver and nrmysqlreceiver to nrdot-collector-experimental"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features Added nrpostgresqlreceiver and nrmysqlreceiver to nrdot-collector-experimental. (#652)","slug":"docs/release-notes/nrdot-release-notes/nrdot-2-2-0","category":"Collector","eolDate":"2027-08-19"},{"agent":"nrdot","date":"2026-08-19","downloadLink":null,"version":"2.1.0","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features Bump otel component versions from v0.157.0 to v0.158.0 (#650) Bump nroracledbreceiver and nrsqlserverreceiver to v0.158.1 (#650) For the list of changes to these components, refer to their changelog .","slug":"docs/release-notes/nrdot-release-notes/nrdot-2-1-0","category":"Collector","eolDate":"2027-08-19"},{"agent":"nrdot","date":"2026-08-04","downloadLink":null,"version":"2.0.0","features":["Added sqlqueryreceiver to nrdot-collector-experimental"],"bugs":["**Breaking:** Removed receiver/jmxreceiver from nrdot-collector and nrdot-collector-experimental following its upstream removal","Renamed configuration node cumulativetodelta to cumulative_to_delta (deprecated alias still available)","Disabled system.cpu.logical.count in host config to restore previous behavior","Removed the redundant system.cpu.utilization mean aggregation rule from host config"],"security":["Fixed CVE-2026-56852"],"supportedOperatingSystems":null,"description":"Changelog We’re issuing a breaking release to mark the removal of jmxreceiver from the component manifests of both nrdot-collector and nrdot-collector-experimental following its removal from opentelemetry-collector-contrib in 0.157.0 (see issue 45740  for reference). The component was exclusively used by the Kafka Monitoring  use case which has been adapted to no longer rely on this receiver. If you deploy nrdot-collector with a custom configuration using jmxreceiver, please migrate following the guidance of the deprecation notice of the receiver . Features Bumped otel component versions from v0.156.0 to v0.157.0 (#643) Bumped nroracledbreceiver and nrsqlserverreceiver to v0.157.2 (#643) For the list of changes to these components, refer to their changelog . Added the sqlqueryreceiver to the nrdot-collector-experimental distribution. (#632) Bug fixes Removed receiver/jmxreceiver from nrdot-collector and nrdot-collector-experimental. (#635) This component was removed upstream in v0.157.0 following its deprecation in v0.145.0. Renamed configuration nodes cumulativetodelta to cumulative_to_delta following the component rename in v0.157.0. (#644) The original name cumulativetodelta remains available as a deprecated alias. Disabled system.cpu.logical.count in host config. (#647) The v0.157.0 update to receiver/host_metrics enabled this metric by default. This change restores the previous behavior. Removed system.cpu.utilization mean aggregation rule from host config. (#646) The v0.157.0 update to receiver/host_metrics changed its default behavior to aggregate system.cpu.utilization by mean, rendering the removed rule redundant. CVE-2026-56852 (#634)","slug":"docs/release-notes/nrdot-release-notes/nrdot-2-0-0","category":"Collector","eolDate":"2027-08-04"},{"agent":"nrdot","date":"2026-02-04","downloadLink":null,"version":"1.9.0","features":["Added OHI components to core, enabling the OHI use case at alpha stability"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features feat: add ohi components to core (#475) enabling OHI use case with stability alpha Docs docs: add security best practices (#483) docs: clarify fips still in preview (#481) docs: document core stability by use case (#469)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-9-0","category":"Collector","eolDate":"2027-02-04"},{"agent":"nrdot","date":"2025-12-19","downloadLink":null,"version":"1.8.0","features":[],"bugs":[],"security":["Forced expr-lang/expr:1.17.7 to fix CVE-2025-68156"],"supportedOperatingSystems":null,"description":"Changelog Features feat: Bump otel component versions from v0.141.0 to v0.142.0 (#464) Bug Fixes fix: force expr-lang/expr:1.17.7 to fix CVE-2025-68156 (#468)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-8-0","category":"Collector","eolDate":"2026-12-19"},{"agent":"nrdot","date":"2025-12-15","downloadLink":null,"version":"1.7.0","features":["Published the nrdot-collector-experimental distribution","Added OHI components to nrdot-collector-experimental"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog This version marks the first publication of the distribution nrdot-collector-experimental which is intended to act as a staging area for components / features for nrdot-collector. The distribution is and will never be considered stable. Features feat: add ohi components to nrdot-collector-experimental (#461)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-7-0","category":"Collector","eolDate":"2026-12-15"},{"agent":"nrdot","date":"2025-12-12","downloadLink":null,"version":"1.6.0","features":[],"bugs":["Addressed transformprocessor config deprecation from 0.119.0"],"security":["Bumped to golang 1.24.11 to fix CVE-2025-61729"],"supportedOperatingSystems":null,"description":"Changelog Features feat(internal-o11y): disable internal traces by default in example config (#422) feat: Bump otel component versions from v0.135.0 to v0.141.0 (#440) Bug Fixes fix(CVE-2025-61729): bump to golang 1.24.11 (#454) (#456) fix: address transformprocessor config deprecation of 0.119.0 (#421) Docs docs: add fips readme (#407)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-6-0","category":"Collector","eolDate":"2026-12-12"},{"agent":"nrdot","date":"2025-09-25","downloadLink":null,"version":"1.5.0","features":["Added metricsgenerationprocessor to nrdot-collector-k8s"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features feat: add metricsgenerationprocessor to nrdot-collector-k8s (#386)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-5-0","category":"Collector","eolDate":"2026-09-25"},{"agent":"nrdot","date":"2025-09-18","downloadLink":null,"version":"1.4.0","features":["Added spanprocessor to nrdot-collector","Enabled host.name detection for EC2"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features feat: Add spanprocessor to nrdot-collector (#371) feat: Bump otel component versions from v0.131.0 to v0.132.0 (#368) feat: Add newrelic.service.type to internal telemetry config (#380) feat: Enable host.name detection for ec2 (#382)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-4-0","category":"Collector","eolDate":"2026-09-18"},{"agent":"nrdot","date":"2025-08-13","downloadLink":null,"version":"1.3.0","features":["Introduced the nrdot-collector distribution (alpha)"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog This release introduces the nrdot-collector  distribution.  This distro is currently in alpha but will eventually serve as a replacement for the nrdort-collector-host distribution.  Future distributions will use nrdot-collector as a base manifest and expand on it as needed. Features feat: Bump otel component versions from v0.128.0 to v0.131.0 (#357) feat: Introducting nrdot core distribution (#359)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-3-0","category":"Collector","eolDate":"2026-08-13"},{"agent":"nrdot","date":"2026-07-23","downloadLink":null,"version":"1.21.1","features":[],"bugs":[],"security":["Fixed GHSA-hrxh-6v49-42gf"],"supportedOperatingSystems":null,"description":"Changelog Bug Fixes fix: GHSA-hrxh-6v49-42gf (#625)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-21-1","category":"Collector","eolDate":"2027-07-23"},{"agent":"nrdot","date":"2026-07-17","downloadLink":null,"version":"1.21.0","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features feat: Bump otel component versions from v0.154.0 to v0.156.0 (#620) feat: Bump nroracledbreceiver and nrsqlserverreceiver to v0.156.1 (#620)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-21-0","category":"Collector","eolDate":"2027-07-17"},{"agent":"nrdot","date":"2026-07-14","downloadLink":null,"version":"1.20.0","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features Updated the nroracledbreceiver and nrsqlserverreceiver to v0.154.6. Docs docs: Updated the Microsoft SQL Server link.","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-20-0","category":"Collector","eolDate":"2027-07-14"},{"agent":"nrdot","date":"2025-06-26","downloadLink":null,"version":"1.2.0","features":["nrdot-collector-k8s distribution reaches public stability"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog This release marks the nrdot-collector-k8s  distribution reaching Stability: public. Please refer to its README  for further details. Features feat: bump OTEL beta core to v0.128.0 (#321)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-2-0","category":"Collector","eolDate":"2026-06-26"},{"agent":"nrdot","date":"2026-06-29","downloadLink":null,"version":"1.19.0","features":["Added nroracledbreceiver, nrsqlserverreceiver, secretsmanagerprovider, and aesprovider components to nrdot-collector for DB monitoring"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features feat(db-monitoring): added new components (nroracledbreceiver, nrsqlserverreceiver, secretsmanagerprovider, aesprovider) to nrdot-collector (#612)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-19-0","category":"Collector","eolDate":"2027-06-29"},{"agent":"nrdot","date":"2026-06-22","downloadLink":null,"version":"1.18.0","features":["Added forked DB components (nroracledbreceiver, nrsqlserverreceiver) and providers (secretsmanagerprovider, aesprovider) for the DB use case","Added OHI components (awsecscontainermetricsreceiver, haproxyreceiver, kafkareceiver, redisreceiver) to nrdot-collector"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features Added forked db components (nroracledbreceiver, nrsqlserverreceiver) and additional providers (secretsmanagerprovider, aesprovider) for db use case (#606) Added OHI components (awsecscontainermetricsreceiver, haproxyreceiver, kafkareceiver, redisreceiver) to nrdot-collector (#609)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-18-0","category":"Collector","eolDate":"2027-06-22"},{"agent":"nrdot","date":"2026-06-15","downloadLink":null,"version":"1.17.0","features":["Added additional OHI components"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features Added additional OHI components (#599) Bump OTel component versions from v0.150.0 to v0.154.0 (#601) Host config nodes renamed due to upstream changes: hostmetrics to host_metrics resourcedetection to resource_detection metricstransform to metrics_transform","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-17-0","category":"Collector","eolDate":"2027-06-15"},{"agent":"nrdot","date":"2026-06-09","downloadLink":null,"version":"1.16.0","features":["Published an MSI installer for the nrdot-collector distribution"],"bugs":[],"security":["Built artifacts with golang 1.26.4 to fix CVE-2026-42504"],"supportedOperatingSystems":null,"description":"Changelog This release marks the initial publication of the msi installer for the nrdot-collector distribution. For additional information, please refer to the general distribution README . Features feat: publish msi and update readme (#588) Bug Fixes Using golang 1.26.4 to build artifacts fixes CVE-2026-42504","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-16-0","category":"Collector","eolDate":"2027-06-09"},{"agent":"nrdot","date":"2026-05-11","downloadLink":null,"version":"1.15.1","features":[],"bugs":[],"security":["Fixed CVE-2026-42151 and CVE-2026-42154"],"supportedOperatingSystems":null,"description":"Changelog Bug Fixes fix: CVE-2026-42151 and CVE-2026-42154 (#578)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-15-1","category":"Collector","eolDate":"2027-05-11"},{"agent":"nrdot","date":"2026-05-05","downloadLink":null,"version":"1.15.0","features":["Added k8sobjectsreceiver as an experimental feature"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features Added k8sobjectsreceiver as a experimental feature. (#573)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-15-0","category":"Collector","eolDate":"2027-05-05"},{"agent":"nrdot","date":"2026-04-29","downloadLink":null,"version":"1.14.0","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features feat: update components to 0.150.0 #567 filelogreceiver: configuration node renamed from filelog to file_log due to upstream change #46750","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-14-0","category":"Collector","eolDate":"2027-04-29"},{"agent":"nrdot","date":"2026-04-23","downloadLink":null,"version":"1.13.0","features":["Added StateDirectory for ATP storage in systemd service"],"bugs":[],"security":["Fixed CVE-2026-39883"],"supportedOperatingSystems":null,"description":"Changelog This release marks the removal of the nrdot-collector-k8s and nrdot-collector-host distribution. The last published version of those distros is 1.12.0. Please migrate to using nrdot-collector instead which is a superset in terms of functionality and acts as a drop-in replacement with the two removed distros being implemented as use cases . Features feat: add StateDirectory for ATP storage in systemd service (#545) Bug Fixes fix: CVE-2026-39883 (#560) Docs docs: update FIPS documentation (#565)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-13-0","category":"Collector","eolDate":"2027-04-23"},{"agent":"nrdot","date":"2026-04-01","downloadLink":null,"version":"1.12.0","features":["Added spanmetricsconnector to experimental"],"bugs":[],"security":["Added grpc v1.79.2 replace to fix CVE-2026-33186","Rotated public GPG signing key","Suppressed CVE-2026-34040 in Trivy scan"],"supportedOperatingSystems":null,"description":"Changelog Features feat: Bump OTEL beta core to v0.148.0 (#548) feat: add spanmetricsconnector to experimental (#531) Bug Fixes fix: add grpc v1.79.2 replace to fix CVE-2026-33186 (#551) fix: rotate public GPG signing key (#552) fix: suppress CVE-2026-34040 in trivy scan (#554)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-12-0","category":"Collector","eolDate":"2027-04-01"},{"agent":"nrdot","date":"2026-03-10","downloadLink":null,"version":"1.11.1","features":[],"bugs":[],"security":["Refreshed GPG public key and fixed CVE-2026-24051"],"supportedOperatingSystems":null,"description":"Changelog Bug Fixes fix: refresh GPG public key and fix CVE-2026-24051","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-11-1","category":"Collector","eolDate":"2027-03-10"},{"agent":"nrdot","date":"2026-02-11","downloadLink":null,"version":"1.11.0","features":["Added adaptivetelemetryprocessor (ATP) to core"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features feat: add adaptivetelemetryprocessor to core (#500)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-11-0","category":"Collector","eolDate":"2027-02-11"},{"agent":"nrdot","date":"2026-02-10","downloadLink":null,"version":"1.10.0","features":["Added adaptivetelemetryprocessor (ATP) to experimental"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features feat: add adaptivetelemetryprocessor (ATP) to experimental (#494)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-10-0","category":"Collector","eolDate":"2027-02-10"},{"agent":"nrdot","date":"2025-05-06","downloadLink":null,"version":"1.1.0","features":["Added routing connector to host and k8s distro","Added memory_limiter to all host pipelines"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features feat: Add routing connector to host and k8s distro (#305) feat: Updating otel components to 0.125.0 (#303) feat: add memory_limiter to all host pipelines (#301) feat: sync config with nr-k8s-otel-collector 0.8.10 (#300)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-1-0","category":"Collector","eolDate":"2026-05-06"},{"agent":"nrdot","date":"2025-04-03","downloadLink":null,"version":"1.0.3","features":[],"bugs":[],"security":["Bumped upstream components to 0.123.0, including a fix for CVE-2025-30204"],"supportedOperatingSystems":null,"description":"Changelog Features feat: bumping upstream components to 0.123.0, includes fix to CVE-2025-30204 (#294) Docs docs: add missing documentation (#292)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-0-3","category":"Collector","eolDate":"2026-04-03"},{"agent":"nrdot","date":"2025-03-20","downloadLink":null,"version":"1.0.2","features":[],"bugs":[],"security":["Forced expr-lang 1.17.0 to fix CVE-2025-29786"],"supportedOperatingSystems":null,"description":"Changelog Features feat: update otel components to 0.122.1 and enables enableCPUUsageMetrics gate in k8s distro (#283) Bug Fixes fix: force expr-lang 1.17.0 to fix CVE-2025-29786 (#284) Docs docs: add governance section (#277)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-0-2","category":"Collector","eolDate":"2026-03-20"},{"agent":"nrdot","date":"2025-03-18","downloadLink":null,"version":"1.0.1","features":[],"bugs":["Added missing default configs to archive artifacts (.tar.gz, .zip)"],"security":[],"supportedOperatingSystems":null,"description":"Changelog Features feat: remove debugexporter from default host config (#271) Bug Fixes fix: add missing default configs to archive artifacts (.tar.gz, .zip) (#274) Docs docs: add installation docs (#275) docs: add troubleshooting guide (#272)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-0-1","category":"Collector","eolDate":"2026-03-18"},{"agent":"nrdot","date":"2025-03-05","downloadLink":null,"version":"1.0.0","features":["nrdot-collector-k8s distribution reaches general availability"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Release Summary We're releasing version  to represent the  distribution now being generally available.  It should be noted that the  distribution is still in preview and should be used with caution for the time being. Changelog Features feat: Update otel components to 0.121.0 (#265) feat: syncing latest version of the k8s helm configs (#269) Docs docs: flagging k8s distro as preview (#268)","slug":"docs/release-notes/nrdot-release-notes/nrdot-1-0-0","category":"Collector","eolDate":"2026-03-05"},{"agent":"nrdot","date":"2024-10-25","downloadLink":null,"version":"0.8.5","features":[],"bugs":[],"security":["Forced docker@27.3.1 to fix CVE-2024-41110"],"supportedOperatingSystems":null,"description":"Changes For a detailed description of changes, see full release notes Fixes force docker@27.3.1 to fix CVE-2024-41110","slug":"docs/release-notes/nrdot-release-notes/nrdot-0-8-5","category":"Collector","eolDate":"2025-10-25"},{"agent":"fluentbit","date":"2026-06-30","downloadLink":null,"version":"5.0.8","features":[],"bugs":[],"security":null,"supportedOperatingSystems":[{"osName":"debian","osVersions":[{"versionName":"bullseye","architectures":["amd64","arm64"]},{"versionName":"bookworm","architectures":["amd64","arm64"]}]},{"osName":"centos","osVersions":[{"versionName":"7","architectures":["x86_64","aarch64"]},{"versionName":"8","architectures":["x86_64","aarch64"]},{"versionName":"9","architectures":["x86_64","aarch64"]}]},{"osName":"rockylinux","osVersions":[{"versionName":"10","architectures":["x86_64","aarch64"]}]},{"osName":"amazonlinux","osVersions":[{"versionName":"2","architectures":["x86_64","aarch64"]},{"versionName":"2023","architectures":["x86_64","aarch64"]}]},{"osName":"ubuntu","osVersions":[{"versionName":"jammy","architectures":["amd64","arm64"]},{"versionName":"noble","architectures":["amd64","arm64"]}]},{"osName":"sles","osVersions":[{"versionName":"15.3","architectures":["x86_64"]},{"versionName":"15.4","architectures":["x86_64"]},{"versionName":"15.5","architectures":["x86_64"]},{"versionName":"15.6","architectures":["x86_64"]},{"versionName":"15.7","architectures":["x86_64"]}]},{"osName":"windows-server","osVersions":[{"versionName":"2019","architectures":["win64","win32"]},{"versionName":"2022","architectures":["win64","win32"]}]}],"description":"Support for Fluent Bit 5.0.8 Users will now receive Fluent Bit version 5.0.8. For more details, refer to the Fluent Bit announcements . This release includes New Relic Fluent Bit Output Plugin 3.7.0 . Added New Relic Fluent Bit Output Plugin 3.7.0 integration Changed The Go version is upgraded to 1.26.4 for CVE fixes The Infrastructure agent recommends Fluent Bit 5.0.8 packages (Linux) and 5.0.7 (Windows) Fluent Bit Output Plugin Docker image  uses Fluent Bit 5.0.8 with output plugin 3.7.0 New Relic Logging Helm chart  installs the new plugin image Windows Docker image uses Fluent Bit 5.0.7 (5.0.8 Windows image not yet available upstream) Notes To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed .","slug":"docs/release-notes/fluentbit-release-notes/fluentbit-26-06-30","eolDate":"2027-06-30"},{"agent":"fluentbit","date":"2026-06-09","downloadLink":null,"version":"5.0.6","features":[],"bugs":[],"security":null,"supportedOperatingSystems":[{"osName":"debian","osVersions":[{"versionName":"bullseye","architectures":["amd64","arm64"]},{"versionName":"bookworm","architectures":["amd64","arm64"]}]},{"osName":"centos","osVersions":[{"versionName":"7","architectures":["x86_64","aarch64"]},{"versionName":"8","architectures":["x86_64","aarch64"]},{"versionName":"9","architectures":["x86_64","aarch64"]}]},{"osName":"rockylinux","osVersions":[{"versionName":"10","architectures":["x86_64","aarch64"]}]},{"osName":"amazonlinux","osVersions":[{"versionName":"2","architectures":["x86_64","aarch64"]},{"versionName":"2023","architectures":["x86_64","aarch64"]}]},{"osName":"ubuntu","osVersions":[{"versionName":"jammy","architectures":["amd64","arm64"]},{"versionName":"noble","architectures":["amd64","arm64"]},{"versionName":"resolute","architectures":["amd64","arm64"]}]},{"osName":"sles","osVersions":[{"versionName":"15.3","architectures":["x86_64"]},{"versionName":"15.4","architectures":["x86_64"]},{"versionName":"15.5","architectures":["x86_64"]},{"versionName":"15.6","architectures":["x86_64"]},{"versionName":"15.7","architectures":["x86_64"]}]},{"osName":"windows-server","osVersions":[{"versionName":"2019","architectures":["win64","win32"]},{"versionName":"2022","architectures":["win64","win32"]}]}],"description":"Support for Fluent Bit 5.0.6 Users will now receive Fluent Bit version 5.0.6. For more details, refer to the Fluent Bit announcements . This release includes New Relic Fluent Bit Output Plugin 3.6.0 . Added Support for Ubuntu 26.04 (Resolute) New Relic Fluent Bit Output Plugin 3.6.0 integration Changed The Infrastructure agent recommends Fluent Bit 5.0.6 packages Fluent Bit Output Plugin Docker image  uses Fluent Bit 5.0.6 with output plugin 3.6.0 New Relic Logging Helm chart  installs the new plugin image aws-for-fluent-bit base image (Firelens) updated from 3.2.5 to 3.4.0 (bundles Fluent Bit 5.0.5; will move to 5.0.6 when AWS publishes a matching tag) Notes To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed .","slug":"docs/release-notes/fluentbit-release-notes/fluentbit-26-06-09","eolDate":"2027-06-09"},{"agent":"fluentbit","date":"2026-02-17","downloadLink":null,"version":"4.2.2","features":[],"bugs":[],"security":null,"supportedOperatingSystems":[{"osName":"debian","osVersions":[{"versionName":"bullseye","architectures":["amd64","arm64"]},{"versionName":"bookworm","architectures":["amd64","arm64"]}]},{"osName":"centos","osVersions":[{"versionName":"7","architectures":["x86_64","aarch64"]},{"versionName":"8","architectures":["x86_64","aarch64"]},{"versionName":"9","architectures":["x86_64","aarch64"]}]},{"osName":"rockylinux","osVersions":[{"versionName":"10","architectures":["x86_64","aarch64"]}]},{"osName":"amazonlinux","osVersions":[{"versionName":"2","architectures":["x86_64","aarch64"]},{"versionName":"2023","architectures":["x86_64","aarch64"]}]},{"osName":"ubuntu","osVersions":[{"versionName":"jammy","architectures":["amd64","arm64"]},{"versionName":"noble","architectures":["amd64","arm64"]}]},{"osName":"sles","osVersions":[{"versionName":"15.3","architectures":["x86_64"]},{"versionName":"15.4","architectures":["x86_64"]},{"versionName":"15.5","architectures":["x86_64"]},{"versionName":"15.6","architectures":["x86_64"]},{"versionName":"15.7","architectures":["x86_64"]}]},{"osName":"windows-server","osVersions":[{"versionName":"2019","architectures":["win64","win32"]},{"versionName":"2022","architectures":["win64","win32"]}]}],"description":"Support for Fluent Bit 4.2.2 Users will now receive Fluent Bit version 4.2.2. For more details, refer to the Fluent Bit announcements . This release includes New Relic Fluent Bit Output Plugin 3.4.0  with critical security updates and enhanced platform compatibility. Added Support for SLES 15.6 and 15.7 New Relic Fluent Bit Output Plugin 3.4.0 integration Changed The Infrastructure agent recommends Fluent Bit 4.2.2 packages Fluent Bit Output Plugin Docker image  uses Fluent Bit 4.2.2 with output plugin 3.4.0 New Relic Logging Helm chart  installs the new plugin image (newrelic-logging chart version 1.35.0) aws-for-fluent-bit base image updated from 3.1.0 to 3.2.1 Fixed GLIBC compatibility issues on RHEL8 and Amazon Linux 2 using Zig cross-compilation targeting GLIBC 2.17 Notes To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed .","slug":"docs/release-notes/fluentbit-release-notes/fluentbit-26-02-17","eolDate":"2027-02-17"},{"agent":"fluentbit","date":"2025-12-09","downloadLink":null,"version":"4.2.0","features":[],"bugs":[],"security":null,"supportedOperatingSystems":[{"osName":"debian","osVersions":[{"versionName":"bullseye","architectures":["amd64","arm64"]},{"versionName":"bookworm","architectures":["amd64","arm64"]}]},{"osName":"centos","osVersions":[{"versionName":"7","architectures":["x86_64","aarch64"]},{"versionName":"8","architectures":["x86_64","aarch64"]},{"versionName":"9","architectures":["x86_64","aarch64"]}]},{"osName":"amazonlinux","osVersions":[{"versionName":"2","architectures":["x86_64","aarch64"]},{"versionName":"2023","architectures":["x86_64","aarch64"]}]},{"osName":"ubuntu","osVersions":[{"versionName":"jammy","architectures":["amd64","arm64"]},{"versionName":"noble","architectures":["amd64","arm64"]}]},{"osName":"sles","osVersions":[{"versionName":"15.3","architectures":["x86_64"]},{"versionName":"15.5","architectures":["x86_64"]}]},{"osName":"windows-server","osVersions":[{"versionName":"2019","architectures":["win64","win32"]},{"versionName":"2022","architectures":["win64","win32"]}]}],"description":"Support for Fluent Bit 4.2.0 Users will now receive Fluent Bit version 4.2.0. For more details, refer https://fluentbit.io/announcements/. Changed Infrastructure agent recommends Fluent Bit 4.2.0 packages. Fluent Bit Output Plugin Docker image  uses Fluent Bit 4.2.0 except for Windows-Server-2019. New Relic Logging Helm chart  installs the new plugin image (newrelic-logging chart version 1.33.0) Notes To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed .","slug":"docs/release-notes/fluentbit-release-notes/fluentbit-25-12-09","eolDate":"2026-12-09"},{"agent":"fluentbit","date":"2025-05-12","downloadLink":null,"version":"3.2.10","features":[],"bugs":["filter_modifier: fixed log event memory leak","core_processor: fixed log decoding errors from missing flags","core_record_accessor: fixed log access on record parsing failures","out_http: corrected status handling for compressed logs"],"security":null,"supportedOperatingSystems":[{"osName":"debian","osVersions":[{"versionName":"buster","architectures":["amd64","arm64"]},{"versionName":"bullseye","architectures":["amd64","arm64"]},{"versionName":"bookworm","architectures":["amd64","arm64"]}]},{"osName":"centos","osVersions":[{"versionName":"7","architectures":["x86_64","aarch64"]},{"versionName":"8","architectures":["x86_64","aarch64"]},{"versionName":"9","architectures":["x86_64","aarch64"]}]},{"osName":"amazonlinux","osVersions":[{"versionName":"2","architectures":["x86_64","aarch64"]},{"versionName":"2023","architectures":["x86_64","aarch64"]}]},{"osName":"ubuntu","osVersions":[{"versionName":"bionic","architectures":["amd64","arm64"]},{"versionName":"focal","architectures":["amd64","arm64"]},{"versionName":"jammy","architectures":["amd64","arm64"]},{"versionName":"noble","architectures":["amd64","arm64"]}]},{"osName":"sles","osVersions":[{"versionName":"12.5","architectures":["x86_64"]},{"versionName":"15.3","architectures":["x86_64"]},{"versionName":"15.4","architectures":["x86_64"]},{"versionName":"15.5","architectures":["x86_64"]}]},{"osName":"windows-server","osVersions":[{"versionName":"2019","architectures":["win64","win32"]},{"versionName":"2022","architectures":["win64","win32"]}]}],"description":"Support for Fluent Bit 3.2.10 Users will now receive Fluent Bit version 3.2.10. For more details, refer https://fluentbit.io/announcements/. Changed Infrastructure agent recommends Fluent Bit 3.2.10 packages. Fluent Bit Output Plugin Docker image  uses Fluent Bit 3.2.10. New Relic Logging Helm chart  installs the new plugin image (newrelic-logging chart version 1.27.0) Notes To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed .","slug":"docs/release-notes/fluentbit-release-notes/fluentbit-25-05-12","eolDate":"2026-05-12"},{"agent":"fluentbit","date":"2025-02-27","downloadLink":null,"version":"3.2.7","features":[],"bugs":["new management signal to overcome a deadlock","input_chunk: log plugin alias instead of plugin name if exists"],"security":["OpenTelemetry input: CVE-2024-50609","Prometheus Remote Write input: CVE-2024-50608"],"supportedOperatingSystems":[{"osName":"debian","osVersions":[{"versionName":"buster","architectures":["amd64","arm64"]},{"versionName":"bullseye","architectures":["amd64","arm64"]}]},{"osName":"centos","osVersions":[{"versionName":"7","architectures":["x86_64","aarch64"]},{"versionName":"8","architectures":["x86_64","aarch64"]}]},{"osName":"amazonlinux","osVersions":[{"versionName":"2","architectures":["x86_64","aarch64"]},{"versionName":"2023","architectures":["x86_64","aarch64"]}]}],"description":"Support for Fluent Bit 3.2.7 Users will now receive Fluent Bit version 3.2.7, which includes fixes for known vulnerabilities. For more details, refer https://fluentbit.io/announcements/. Security Previous versions of Fluent Bit in the 3.1 and 3.2  series are affected by two security vulnerabilities if customers use the OpenTelemetry input plugin  or Prometheus Remote Write input . The identified vulnerabilities are: CVE-2024-50608 , CVE-2024-50609 . By default, New Relic does not include these plugins in our distribution of the Fluent Bit packages in any of the instrumentation packages we provide. However, in order to support customers using these plugins and mitigate any potential impact, we recommend customers to upgrade to the latest available versions of these packages: Hosts: Windows: Infrastructure Agent upgraded to v1.62.0 or later Linux: Infrastructure Agent upgraded to v1.62.0 or later Kubernetes: newrelic-logging upgraded to v1.26.1 nri-bundle upgraded to v5.0.115 Fluent Bit: New Relic Fluent Bit Output Docker Image upgraded to v2.3.0 Notes To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed .","slug":"docs/release-notes/fluentbit-release-notes/fluentbit-25-02-27","eolDate":"2026-02-27"},{"agent":"fluentbit","date":"2025-02-20","downloadLink":null,"version":"3.2.2","features":[],"bugs":["http_common: added missing initializers","http_client: assorted HTTP/2 related fixes","http_client: potential memory corruption fixes"],"security":null,"supportedOperatingSystems":null,"description":"Support for Fluent Bit 3.2.2 Users will now receive Fluent Bit version 3.2.2, which includes fixes for known vulnerabilities. For more details, refer https://fluentbit.io/announcements/. Changed Infrastructure agent recommends Fluent Bit 3.2.2 packages. Fluent Bit Output Plugin Docker image  uses Fluent Bit 3.2.2. New Relic Logging Helm chart  installs the new plugin image (newrelic-logging chart version 1.25.1) Notes To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed .","slug":"docs/release-notes/fluentbit-release-notes/fluentbit-25-02-20","eolDate":"2026-02-20"},{"agent":"fluentbit","date":"2024-10-31","downloadLink":null,"version":"3.1.9","features":["Multiline reset fixes high CPU","improved error messaging","ctraces upgraded","Multiline filter enhancement"],"bugs":["YAML memory fixes","prevent crash during reload"],"security":null,"supportedOperatingSystems":null,"description":"Support for Fluent Bit 3.1.9 Users will now receive Fluent Bit version 3.1.9, which includes fixes for known vulnerabilities. For more details, refer  https://fluentbit.io/announcements/. Changed Infrastructure agent recommends Fluent Bit 3.1.9 packages. Fluent Bit Output Plugin Docker image  uses Fluent Bit 3.1.9. New Relic Logging Helm chart  installs the new plugin image (newrelic-logging chart version 1.24.0). Notes To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed .","slug":"docs/release-notes/fluentbit-release-notes/fluentbit-24-10-31","eolDate":"2025-10-31"},{"agent":"fluentbit","date":"2024-08-31","downloadLink":null,"version":"3.1.2","features":["file_cache_advise (default: on) to reduce file cache usage","plugin pause/resume mechanism"],"bugs":["Centos 7 package fix","prevent crash during reload"],"security":null,"supportedOperatingSystems":null,"description":"Support for Fluent Bit 3.1.2 Users will now receive Fluent Bit version 3.1.2, which includes fixes for known vulnerabilities. For more details, refer https://fluentbit.io/announcements/. Changed Infrastructure agent recommends Fluent Bit 3.1.2 packages. Fluent Bit Output Plugin Docker image  uses Fluent Bit 3.1.2. New Relic Logging Helm chart  installs the new plugin image. Notes To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed .","slug":"docs/release-notes/fluentbit-release-notes/fluentbit-24-08-31","eolDate":"2025-08-31"},{"agent":"aws_lambda_log_forwarder","date":"2025-07-25","downloadLink":null,"version":"1.1.1","features":["Update go version to 1.24.4"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Enhanced AWS Lambda log processing with request ID injection New Relic enhances the security of its Lambda functions by updating the underlying Go runtime to version 1.24.4, which includes the latest security patches. Changed Go version upgrade:  New Relic has enhanced its security posture by upgrading the Go version in its systems to 1.24.4. Notes To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed .","slug":"docs/release-notes/aws-lambda-log-forwarder-release-notes/lambda-25-07-25","eolDate":"2026-07-25"},{"agent":"aws_lambda_log_forwarder","date":"2025-01-21","downloadLink":null,"version":"1.1.0","features":["Consistent Request ID annotation for all AWS Lambda log messages, improving traceability and observability."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Enhanced AWS Lambda Log Processing with Request ID Injection New Relic enhances log processing for AWS Lambda functions by ensuring that request IDs are consistently added to logs lacking default runtime annotations. This improves traceability and observability across Lambda invocations. Changed Consistent Request ID Annotation:  Logs from AWS Lambda functions now have request IDs added to every message using the UUID found in the first and last log entries. This ensures comprehensive traceability and completeness in log data, enabling more effective monitoring and debugging. Notes To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed .","slug":"docs/release-notes/aws-lambda-log-forwarder-release-notes/lambda-25-01-21","eolDate":"2026-01-21"},{"agent":"aws_lambda_log_forwarder","date":"2024-12-06","downloadLink":null,"version":"1.0.0","features":["Accelerated AWS services logs onboarding with one-step observability.","Simplified logs and metrics onboarding using a CloudFormation template.","Ability to set up log forwarding from multiple sinks (CloudWatch or S3) in a single workflow.","Support for configuring triggers for up to 40 S3 buckets and log groups at once.","Organize your logs more effectively by adding attributes, making it easier to search, filter, analyze, and parse your data."],"bugs":[],"security":["New Relic's API keys can be securely stored in AWS Secrets Management for enhanced security."],"supportedOperatingSystems":null,"description":"Accelerated AWS logs forwarding with New Relic's One-Step Observability New Relic's one-step observability now includes accelerated AWS services logs onboarding. This enhanced AWS integration offers experienced and new New Relic users a seamless and flexible experience for onboarding logs and metrics within minutes—all in a streamlined workflow. Changed Simplified logs onboarding with cloudFormation template:  Effortless set up experience for both logs and metrics using ready-made templates that simplify the deployment of AWS resources. Enhanced operational Efficiency:  In a single onboarding workflow users can set up log forwarding from many sinks (CloudWatch or S3), using Lambda-based integration, and setting up triggers for up to 40 S3 buckets and log groups, all in one go. Advanced Security:   New Relic's API keys can securely stored in AWS Secrets Management, for enhances security posture. Notes To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed .","slug":"docs/release-notes/aws-lambda-log-forwarder-release-notes/lambda-24-12-06","eolDate":"2025-12-06"},{"agent":"aws_firehose_log_forwarder","date":"2024-12-06","downloadLink":null,"version":"1.0.0","features":["Accelerated AWS logs forwarding with New Relic's One-Step Observability","Simplified logs onboarding with CloudFormation template for both logs and metrics","Enhanced operational efficiency with a single onboarding workflow for AWS CloudWatch log forwarding via Amazon Data Firehose","Organize your logs more effectively by adding attributes, making it easier to search, filter, analyze, and parse your data."],"bugs":[],"security":["New Relic's API keys can be securely stored in AWS Secrets Management for enhanced security."],"supportedOperatingSystems":null,"description":"Accelerated AWS logs forwarding with New Relic's One-Step Observability New Relic's one-step observability now includes accelerated AWS services logs onboarding. This enhanced AWS integration offers experienced and new New Relic users a seamless and flexible experience for onboarding logs and metrics within minutes—all in a streamlined workflow. Changed Simplified logs onboarding with cloudFormation template:  Effortless set up experience for both logs and metrics using ready-made templates that simplify the deployment of AWS resources. Enhanced operational Efficiency:  In a single onboarding workflow users can set up log forwarding from AWS CloudWatch , using the Amazon Data Firehose integration. Advanced Security:   New Relic's API keys can securely stored in AWS Secrets Management, for enhances security posture. Notes To stay up to date with the most recent fixes and enhancements, subscribe to our Logs RSS feed .","slug":"docs/release-notes/aws-firehose-log-forwarder-release-notes/firehose-24-12-06","eolDate":"2025-12-06"},{"agent":"agent_control","date":"2026-07-06","downloadLink":null,"version":"1.18.0","features":["Adds exponential backoff + jitter retries to OCI artifact fetches via a new `BackoffPolicy` (configurable under `self_update.download_retry`), replacing the old `with_retries(usize, Duration)` API.","add post-download script support for OCI packages.","Hardens service restart policies on Linux and Windows (systemd rate limiting: 5 restarts max in 60s) to prevent crash-looping from saturating CPU.","Added support for remote agent type definition retrieval from OCI registries.","Agent type definitions now tolerate unknown fields for forward compatibility.","On-host agents: now it is possible to avoid specifying a health check in the agent type definition, in which case the agent health will be not reported.","On-host agents: removed command-based version checking. Agent version is now determined from OCI package metadata, eliminating the need for `deployment.version` configuration in agent type definitions.","Replace filesystem in on-host agent-type definitions with an explicit, recursive, tagged-kind tree: every entry declares `kind: file | dir | dir_content_from_map`, and `dir` entries nest via `entries:`.","On-host filesystem entries now accept a `persistent` flag (default `false`): ephemeral entries are deleted on sub-agent stop, persistent entries survive until the agent is removed from the fleet. Reconciliation across writes is driven by a `.ac-managed-paths.json` manifest (reserved filename — agent types must not declare it) so paths Agent Control no longer owns are deleted while sub-agent-created files are preserved.","Include new 'shared-filesystem-dir` variable for Agent Types.","Extend internal `fs` crate with a copy operation.","Removed the filesystem manifest-based prune mechanism; Agent Control no longer deletes previously-declared paths that a config later drops. Agent-managed files are reclaimed only when the agent is removed from the fleet."],"bugs":["On-host self-update: an empty `version: \"\"` pushed from Fleet Control now behaves the same as an absent `version` field (no-op, no update attempted). Previously it silently triggered a pull of the `:latest` OCI tag."],"security":null,"supportedOperatingSystems":null,"description":"Features Added exponential backoff and jitter retries to OCI artifact fetches using a new BackoffPolicy (configured under self_update.download_retry), replacing the previous with_retries(usize, Duration) API. Added post-download script support for OCI packages. Hardened service restart policies on Linux and Windows platforms (implementing systemd rate limiting: maximum of 5 restarts within 60 seconds) to prevent crash-looping from saturating CPU capacity. Added support for retrieving remote agent type definitions directly from OCI registries. Configured agent type definitions to tolerate unknown fields to ensure forward compatibility. Added support for creating on-host agents without defining a health check, which disables health reporting for that agent. Streamlined version tracking for on-host agents by deriving versions directly from OCI package metadata. This eliminates command-based version checking and removes the need for the deployment.version configuration in agent type definitions. Replaced the filesystem configuration in on-host agent type definitions with an explicit, recursive, tagged-kind tree structure where every entry declares kind: file | dir | dir_content_from_map and dir entries nest using entries:. Introduced a persistent flag (default value is set to false) for on-host filesystem entries; ephemeral entries are deleted when a sub-agent stops, while persistent entries remain until the agent is removed from the fleet.Reconciliation across writes is driven by a .ac-managed-paths.json manifest (reserved filename — agent types must not declare it) so paths Agent Control no longer owns are deleted while sub-agent-created files are preserved. Introduced the shared-filesystem-dir variable for agent type configurations. Extended the internal fs crate to support file copy operations. Removed the filesystem manifest-based prune mechanism; Agent Control no longer deletes previously-declared paths dropped by subsequent configurations; agent-managed files are now reclaimed only when the agent is removed from the fleet. Fixes Fixed an on-host self-update issue where pushing an empty version: \"\" string from Fleet Control incorrectly triggered an image pull of the :latest OCI tag. It now correctly treats an empty string as a no-op (), matching the behavior of an absent version field. For a detailed description of changes, see the release notes .","slug":"docs/release-notes/agent-control-release-notes/agent-control-2026-07-06","eolDate":"2027-07-06"},{"agent":"ios","date":"2022-10-20","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.4.0.zip","version":"7.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Swift symbol upload script. Cold and Hot App Launch Time Metrics are now reported automatically. Note: Warm and prewarmed times are not reported. Fix a bug where install metrics were not sent in all cases. Other notes Deprecation notice: This version introduces a new Swift symbol upload script. See installation instructions for details on how to update to the new script. In a future version of the iOS agent the Python based symbol upload scripts will be removed. This artifact was built using Xcode 13.4.1 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher and Swift Package Manager. For Mac Catalyst, the zip file installation may integrate more easily than using CocoaPods. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. The iOS and tvOS agents were deprecated with the release of version 7.2.1 of the XCFramework  agent. As of this release, the oldest supported version is 7.0.0 of the XCFramework","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-740","eolDate":"2023-10-20"},{"agent":"ios","date":"2022-08-24","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.3.8.zip","version":"7.3.8","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Automatic dSYM file upload script updated to use Python 3. Fix for custom event memory leak. Other notes This artifact was built using Xcode 13.4.1 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher and Swift Package Manager. For Mac Catalyst, the zip file installation may integrate more easily than using CocoaPods. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. The iOS and tvOS agents were deprecated with the release of version 7.2.1 of the XCFramework  agent. As of this release, the oldest supported version is 7.0.0 of the XCFramework","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-738","eolDate":"2023-08-24"},{"agent":"ios","date":"2022-07-13","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.3.7.zip","version":"7.3.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Updates to support Hybrid Frameworks Fix for custom event memory leak Fix for custom traces when disabling default traces Other notes This artifact was built using Xcode 13.3 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher and Swift Package Manager For Mac Catalyst, the zip file installation may integrate more easily than using CocoaPods. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. The iOS and tvOS agents were deprecated with the release of version 7.2.1 of the XCFramework  agent. As of this release, the oldest supported version is 7.0.0 of the XCFramework","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-737","eolDate":"2024-07-13"},{"agent":"ios","date":"2022-06-01","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.3.6.zip","version":"7.3.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Bug fixes for stability More accurate bytes received calculation for HTTP transactions Updates to support Hybrid Frameworks Other notes This artifact was built using Xcode 13.3 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher and Swift Package Manager For Mac Catalyst, the zip file installation may integrate more easily than using CocoaPods. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. The iOS and tvOS agents were deprecated with the release of version 7.2.1 of the XCFramework  agent. As of this release, the oldest supported version is 7.0.0 of the XCFramework","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-736","eolDate":"2024-06-01"},{"agent":"ios","date":"2022-04-22","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.3.5.zip","version":"7.3.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Support for Xcode 13 Fixed an issue with distributed tracing headers not being added Other notes This artifact was built using Xcode 13.3 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher and Swift Package Manager For Mac Catalyst, the zip file installation may integrate more easily than using CocoaPods. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. The iOS and tvOS agents were deprecated with the release of version 7.2.1 of the XCFramework  agent. As of this release, the oldest supported version is 7.0.0 of the XCFramework","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-735","eolDate":"2024-04-22"},{"agent":"ios","date":"2021-11-18","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.3.4.zip","version":"7.3.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Added New Relic dSYMs for deeper crash reporting symbolication on iOS and tvOS. Fixed reachabilty crash. Other notes This artifact was built using Xcode 12.3 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher. For Mac Catalyst, the zip file installation may integrate more easily than using CocoaPods. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. The iOS and tvOS agents were deprecated with the release of version 7.2.0 of the XCFramework  agent. As of this release, the oldest supported version is 7.2.1 of the XCFramework","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-734","eolDate":"2023-11-18"},{"agent":"ios","date":"2021-08-23","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.3.3.zip","version":"7.3.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Improved crash reporting symbolication for all iOS and tvOS architectures. Updated post-build step script for uploading dSYM files. Other notes This artifact was built using Xcode 12.3 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher. For Mac Catalyst, the zip file installation may integrate more easily than using CocoaPods. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. The iOS and tvOS agents were deprecated with the release of version 7.2.0 of the XCFramework  agent. As of this release, the oldest supported version is 7.2.0 of the XCFramework","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-733","eolDate":"2023-08-23"},{"agent":"ios","date":"2021-06-17","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.3.2.zip","version":"7.3.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Updated framework anatomy for Mac Catalyst. Crash reporting symbolication bug fixes. URLSession error handling improvements. Other notes This artifact was built using Xcode 12.3 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher. For Mac Catalyst, the zip file installation may integrate more easily than using CocoaPods. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. The iOS and tvOS agents were deprecated with the release of version 7.1.0 of the XCFramework  agent. As of this release, the oldest supported version is 7.1.0 of the XCFramework","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-732","eolDate":"2023-06-17"},{"agent":"ios","date":"2021-04-30","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.3.1.zip","version":"7.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Support for Xcode running Catalyst and tvOS Simulator on Apple silicon Macs. Other notes This artifact was built using Xcode 12.3 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher. For Mac Catalyst, the zip file installation may integrate more easily than using Cocoapods. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. The iOS and tvOS agents were deprecated with the release of version 7.0.0 of the XCFramework  agent. As of this release, the oldest supported version is 7.0.0 of the XCFramework","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-731","eolDate":"2023-04-30"},{"agent":"ios","date":"2021-03-31","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.3.0.zip","version":"7.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Adds Distributed Tracing support The agent will now add Distributed Tracing headers to instrumented network requests. This feature is enabled by default, but can be disabled through the DistributedTracing feature flag. Refer to How New Relic distributed tracing works  for more information on Distributed Tracing in mobile apps. Fixed in this release Support for Xcode running on Apple Silicon Macs. Other Notes This artifact was built using Xcode 12.3 with a minimum deployment target of iOS version 9.0 Support Statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. The iOS and tvOS agents were deprecated with the release of version 7.0.0 of the XCFramework  agent. As of this release, the oldest supported version is 6.5.0 for the iOS  and tvOS  agents.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-730","eolDate":"2023-03-31"},{"agent":"ios","date":"2020-12-17","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.2.1.zip","version":"7.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Resolve tvOS thinning issues when publishing to Apple. Other Notes This artifact was built using Xcode 12.0.1 with a minimum deployment target of iOS version 9.0 Support Statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. The iOS and tvOS agents were deprecated with the release of version 7.0.0 of the XCFramework  agent. As of this release, the oldest supported version is 6.5.0 for the iOS  and tvOS  agents.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-721","eolDate":"2022-12-17"},{"agent":"ios","date":"2020-11-19","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.2.0.zip","version":"7.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements The dSYM upload scripts and dependencies have been updated. Other Notes This artifact was built using Xcode 12.0.1 with a minimum deployment target of iOS version 9.0 Support Statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. The iOS and tvOS agents were deprecated with the release of version 7.0.0 of the XCFramework  agent. As of this release, the oldest supported version is 6.5.0 for the iOS  and tvOS  agents.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-720","eolDate":"2022-11-19"},{"agent":"ios","date":"2020-10-15","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.1.0.zip","version":"7.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improved attribute validation The agent will no longer reject events containing invalid attributes. Attributes that fail basic event validation are pruned from the map of provided event attributes. We've also corrected an event creation error where attribute maps containing null keys would result in events with a subset of passed attributes. This applies to recordCustomEvent:withAttributes: and recordBreadcrumb:withAttributes:. Other Notes This artifact was built using Xcode 12.0.1 with a minimum deployment target of iOS version 9.0","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-710","eolDate":"2022-10-15"},{"agent":"ios","date":"2020-09-09","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.0.0.zip","version":"7.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The New Relic XCFramework Agent is the updated distribution method for the iOS & tvOS agent. Starting with the 7.0.0 release, all future updates will be deployed via the XCFramework agent. The XCFramework agent will be distributed via the NewRelicAgent cocoapods, as well as via download. New features A single artifact support iOS, tvOS, and Catalyst  apps. Dynamic Library  support. This will greatly improve support for shared frameworks instrumentation. Notes To import this artifact you'll have to use #import <NewRelic/NewRelic.h> instead of the previous#<NewRelicAgent/NewRelic.h>.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/xcframework-agent-700","eolDate":"2023-09-09"},{"agent":"ios","date":"2020-09-11","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.0.0.zip","version":"7.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The New Relic tvOS agent is now deprecated. Please refer to the New Relic XCFramework Agent  for tvOS support.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-700","eolDate":"2023-09-11"},{"agent":"ios","date":"2019-10-25","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.9.0.zip","version":"6.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Improved possible race-condition with accessing currentSessionId. Note: This release was built with Xcode11 and may be incompatible with earlier versions of Xcode.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-690","eolDate":"2022-10-25"},{"agent":"ios","date":"2019-09-13","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.8.0.zip","version":"6.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed incorrect time units recorded for response time of network errors. It was reporting as milliseconds, and it was corrected to seconds.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-680","eolDate":"2022-09-13"},{"agent":"ios","date":"2019-06-07","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.7.0.zip","version":"6.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements The NewRelic NSURLSessionTaskDelegate object now provides an isKindOfClass: method that presents as the wrapped class. This improves compatibility with other frameworks. Fixes Fixes potential crash if _dyld_register_func_for_add_image callback is executed in an unexpected way.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-670","eolDate":"2022-06-07"},{"agent":"ios","date":"2019-03-14","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.6.0.zip","version":"6.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Bumped session attribute limit to 128 from 64. Fixes +recordCustomEvent:withName:attributes: no longer requires a dictionary to capture name. Values in attributes dictionaries passed to recordEvent APIs will no longer be cast to int or float values, which degraded large data types.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-660","eolDate":"2022-03-14"},{"agent":"ios","date":"2019-02-05","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.5.0.zip","version":"6.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Improved dSYM upload script.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-650","eolDate":"2022-02-05"},{"agent":"ios","date":"2018-10-30","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.4.1.zip","version":"6.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Corrects bug in dSYM upload script introduced by Xcode10's new build system.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-641","eolDate":"2021-10-30"},{"agent":"ios","date":"2018-10-09","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.4.0.zip","version":"6.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes +setMaxEventBufferTime and +setMaxEventPoolSize now persist between background/foreground dSYM upload script has been improved. It is now better at finding and uploading dSYMs. Note: This agent was built with Xcode10. It may be necessary to use Xcode10 for compatibility.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-640","eolDate":"2021-10-09"},{"agent":"ios","date":"2018-09-12","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.3.2.zip","version":"6.3.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed race condition in handled exceptions component, which had the potential of crashing on background inside std::recursive_mutex::lock()","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-632","eolDate":"2021-09-12"},{"agent":"ios","date":"2018-06-14","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.3.1.zip","version":"6.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Replaced missing llvm bitcode in framework.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-631","eolDate":"2021-06-14"},{"agent":"ios","date":"2018-06-01","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.3.0.zip","version":"6.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Agent can now handle region specific application tokens. Fixes Fixed inconsistency in deviceManufacturer session attribute; it will always be set as \"Apple, Inc\". memUsageMb session attribute will now be stored as a numeric value rather than a string value. Fixed race-condition in gesture instrumentation that could cause a crash on app background. RequestUrl and RequestPath attributes on MobileRequest and MobileRequestError events will consistently be not URL-encoded. Crash reports will now be uploaded immediately after processing on subsequent launch. Fixed potential race-condition in +[NewRelic stopCurrentInteraction:(NSString*)activityIdentifier]; that could result in dead-lock. Bugs Missing llvm bitcode (fixed in 6.3.1)","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-630","eolDate":"2021-06-01"},{"agent":"ios","date":"2018-03-01","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.2.0.zip","version":"6.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Improved performance of symbol map upload script. Improved performance of recordHandledException API. Removed deprecated APIs. Fixes Prevents possible corrupted event data. Event/Attribute APIs now accept NSNumbers containing BOOL values +[NewRelic setApplicationVersion:] and +[NewRelic setApplicationBuild:] will now throw an exception if called after the agent is started.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-620","eolDate":"2021-03-01"},{"agent":"ios","date":"2020-08-25","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.14.0.zip","version":"6.14.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added API to allow the agent data upload hosts to be set during agent start-up. ( +(void) startWithApplicationToken:andCollectorAddress:andCrashCollectorAddress: )","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-6140","eolDate":"2023-08-25"},{"agent":"ios","date":"2020-07-21","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.13.0.zip","version":"6.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Removed deprecated use of NSURLConnection methods Improved ptr auth stripping in arm64e crashes.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-6130","eolDate":"2023-07-21"},{"agent":"ios","date":"2020-07-13","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.12.0.zip","version":"6.12.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed build warnings related to the tvOS agent.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-6120","eolDate":"2023-07-13"},{"agent":"ios","date":"2020-04-20","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.11.0.zip","version":"6.11.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes +[NewRelic recordHandledException:(NSException*)] will no longer accept exceptions that were not thrown.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-6110","eolDate":"2023-04-20"},{"agent":"ios","date":"2019-11-20","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.10.0.zip","version":"6.10.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes dSYM upload script can handle paths with spaces in them.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-6100","eolDate":"2022-11-20"},{"agent":"ios","date":"2017-12-14","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.1.0.zip","version":"6.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release MobileRequestError events now contain the response body returned in the network request response, if one exists. Response bodies will only be reported if the http response body capture feature flag  is enabled. HttpResponseBodyCapture is enabled by default. Response body data will be limited to the first 4096 bytes (the Insights attribute limit). MobileRequestError events now also contain any cross-application tracing (CAT) data returned in the response headers. See Introduction to cross-application traces  for more information. Fixed in this release Fixed a memory leak in NRMAReachability.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-610","eolDate":"2020-12-14"},{"agent":"ios","date":"2017-11-08","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_6.0.0.zip","version":"6.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Major release This agent release was built with Xcode 9, breaking backwards compatibility with older versions of Xcode. Improvements Swift error support. This release adds a new API in the NewRelic object +recordError:(NSError*)error withAttributes:(NSDictionary*)attributes;. This allows Swift errors to be recorded as MobileHandledException events and to be viewable in the Handled Exception Mobile UI page. MobileRequest events are on by default. MobileRequest events will now be transmitted by default. They can be turned off by calling [NewRelic disableFeatures:NRFeatureFlag_NetworkRequestEvents] before [NewRelic startWithApplicationToken:...]. Improved post build script. Symbol files will now be processed at build time and uploaded to New Relic using the postbuild.sh, rather than uploading the entire dSYM at build time. This will reduce network overhead as well as improve the time it takes for crashes to symbolicate. Fixes Fixed low frequency crash in NRMAHarvestableMetric.m:45. Resolved memory leaks.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-600","eolDate":"2020-11-08"},{"agent":"ios","date":"2016-09-22","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_5.8.2.zip","version":"5.8.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added support for control characters in Insights data. Control characters will now be displayed by their common escaped character representation. For example: an 'end-of-text' control character will be displayed as '^C'. Fixes Removed instrumentation of ASI networking framework. This prevents collisions with Apple's private API scans, which produces a false positive when scanning our instrumentation of this library. We recommend anyone still using ASI for networking to use our custom network instrumentation  tools going forward.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-582-0","eolDate":"2019-09-22"},{"agent":"ios","date":"2016-09-02","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_5.8.0.zip","version":"5.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added support for control characters in insights data. Control characters will now be displayed by their common escaped character representation. e.g.: an 'end-of-text' control character will be displayed a '^C'.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-580","eolDate":"2019-09-02"},{"agent":"ios","date":"2016-08-02","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_5.7.1.zip","version":"5.7.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes The dSYM upload script can now handle targets with spaces in the name.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-571","eolDate":"2019-08-02"},{"agent":"ios","date":"2016-07-29","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_5.7.0.zip","version":"5.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Embedded framework support in crash reporting: If your application is built with an embedded framework, the agent will now automatically upload all dSYMs associated with your app and utilize them in symbolication of crash reporting. Fixes Corrected some instances where networking errors were being recorded as HTTP errors.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-570","eolDate":"2019-07-29"},{"agent":"ios","date":"2016-06-17","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.6.0.zip","version":"5.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This is the initial release of the New Relic Agent for tvOS! The tvOS agent allows you to monitor and manage the performance of your tvOS applications by providing end-to-end details, errors, and throughput from every angle in real time. Provides access to New Relic Crash Reporting to track and diagnose crashes in your tvOS apps. Includes APIs for custom instrumentation to gain deeper insights into specific areas of your app. Get more details in the New Relic for tvOS documentation","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-560","eolDate":"2019-06-17"},{"agent":"ios","date":"2017-10-17","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_5.15.0.zip","version":"5.15.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Handled Exceptions in Objective-C The tvOS agent now exposes an API on the NewRelic object: Passing a caught exception to this API will record details as a MobileHandledException event and record the thread details of the exception. This information will be available in the new UI for handled exceptions. A new feature flag is available, NRFeatureFlag_HandledExceptionEvents. This toggles the generation of MobileHandledExceptions events and auxiliary data. It is enabled by default Fixes Fixed memory leak introduced by NSURLSession instrumentation.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-5150","eolDate":"2020-10-17"},{"agent":"ios","date":"2017-07-11","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_5.14.1.zip","version":"5.14.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Removed URL parameters from MobileRequestError and MobileRequest events. The concern being there may be confidential information contained in these parameters.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-5141-0","eolDate":"2020-07-11"},{"agent":"ios","date":"2017-06-20","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_5.14.0.zip","version":"5.14.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Now reports network request events to Insights! This feature must be enabled when starting the agent using [NewRelic enableFeatures:NRFeatureFlag_NetworkRequestEvents]. When enabled all network calls will be tracked, in addition to network errors. These new events will be available under the MobileNetworkRequest eventType.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-5140","eolDate":"2020-06-20"},{"agent":"ios","date":"2017-05-11","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_5.13.0.zip","version":"5.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Features Added a new MobileBeadcrumb  event type that allows you to annotate the execution of your app, to help troubleshoot crashes and provide greater detail in Insights. Use this new event type using the conveneince method +recordBreadcrumb:withAttributes: Added an additional +recordCustomEvent:name:withAttributes  method that takes the event name as an optional parameter. This avoids the need to add a name attribute in the passed attribute set.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-5130","eolDate":"2020-05-11"},{"agent":"ios","date":"2017-03-10","downloadLink":"https://download.newrelic.com/tvos_agent/NewRelic_tvOS_Agent_5.12.1.zip","version":"5.12.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Adds new API +[NewRelic recordCustomEvent:(NSString*)eventType withAttributes:(NSDictionary*)attributes] This method replaces +[NewRelic recordEvent:(NSString*)name withAttributes:(NSDictionary*)attributes] which is now deprecated, with the intention of removal in the future. The new API creates a new event with an event type specified by the eventType parameter, whereas the deprecated method create a event with the Mobile event type and an attribute with the name 'name' and the value of the name parameter. This change satisfies customer requests for: Improved Insights query performance Defining custom event types Finding custom event in Insights more easily Flexibility to define data retention per custom event type Adds helper method +setUserId: to NewRelic.h which sets a session attribute, userId, with the passed value. This method is effectively the same as [NewRelic setAttribute:@\"userId\" value:<username>]; This release adds a new Insights event type: MobileRequestError. This new event tracks networking and http errors during the app's lifecycle, adding the ability to slice and dice network error data! More details can be found at Mobile Request Error Events . This agent now applies the lastInteraction attribute to all events, not just crash events. The applications build value is now added as a default session attribute: appBuild.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/tvos-agent-5121","eolDate":"2020-03-10"},{"agent":"ios","date":"2025-02-19","downloadLink":"https://itunes.apple.com/us/app/new-relic/id594038638?mt=8","version":"6.9.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Feature changes Removed Teams support","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/new-relic-ios-6091","eolDate":"2026-02-19"},{"agent":"ios","date":"2026-09-08","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.7.7.zip","version":"7.7.7","features":["Updated the XCFramework build configuration"],"bugs":["Resolved a crash ('SIGSEGV' within 'objc_msgSend') occurring during harvest configuration reads.","Resolved an issue where all activity traces were dropped for a session when the '/connect' response omitted the 'at_capture' attribute.","Corrected the 'platform' value reported with React Native errors to report as 'ReactNative'.","Fixed the 'agentVersion' field in the JavaScript error payload to accurately report the iOS agent version","Updated custom attribute validation"],"security":[],"supportedOperatingSystems":null,"description":"New feature Updated the XCFramework build configuration to target a minimum deployment version of iOS 15.0 and tvOS 15.0, aligning with documented minimum platform requirements. Bug fixes Resolved a crash (SIGSEGV within objc_msgSend) occurring during harvest configuration reads. Eight object properties on NRMAHarvesterConfiguration declared as assign retained dangling pointers after autorelease pool drainage from the /connect response or NSUserDefaults dictionary. Resolved an issue where all activity traces were dropped for a session when the /connect response omitted the at_capture attribute. Corrected the platform value reported with React Native errors to report as ReactNative. Fixed the agentVersion field in the JavaScript error payload to accurately report the iOS agent version rather than the host platform version. Updated custom attribute validation: Passing an NSArray or NSDictionary object as an event attribute now logs an explicit error identifying the unsupported type, replacing the generic \"value must be an NSString, NSNumber, or BOOL\" warning message.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-777","eolDate":"2027-09-08"},{"agent":"ios","date":"2026-08-13","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.7.6.zip","version":"7.7.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed session replay events sorting ahead of Meta/FullSnapshot. fixed potential missing data by rewriting NRMAExceptionMetaDataStore. Fixed RN sourcemap upload script. Fixed a potential session restart issue in checkAndHandleSessionTimeout.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-776","eolDate":"2027-08-13"},{"agent":"ios","date":"2026-08-07","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.7.5.zip","version":"7.7.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed a bug where calling setUserId with nil always started a new session. Prevented old session replay frames from uploading with a new session. Changed reachability to update a callback on change instead of calling it every time. Fixed hex invalidate crash. Fixed setUserId vendorId crash. Fixed atomicity across NRMA Trace collections. Fixed setUserId to stay synchronous. Fixed a crash by changing session replay from a Timer to a DispatchSourceTimer. Fixed a CoreData NRMAMethodProfiler crash. Fixed a crash by having sessionAttributeJSONString take a snapshot of dicts. Fixed MSR text by clamping the SwiftUI text width-compensation offset to its content. Fixed a JSErrorController memory leak. Fixed MSR text by referring to the precise numeric font weight instead of the binary bold trait. Updated the dSYM upload tools to add the appVersion param to dsym-upload-tools run-symbol-tool. Fixed the missing SwiftUI modals in MSR.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-775","eolDate":"2027-08-07"},{"agent":"ios","date":"2026-07-09","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.7.4.zip","version":"7.7.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Simulator devices now report as simulator-(deviceType). Fixed in this release Removed the KMP detection that was causing instability in 7.7.3. Fixed a crash that could occur when recording async web requests. Fixed a crash caused by a harvest config race condition.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-774","eolDate":"2027-07-09"},{"agent":"ios","date":"2026-07-02","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.7.3.zip","version":"7.7.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Offline storage functionality for Mobile Session Replay. Fixed in this release Replaced timestamp-seeded LCG in IGuidGenerator with arc4random_buf. Added EU region detection to RN Sourcemap upload. Blocked recursion for MAUI style default interaction swizzle. Renamed appVersionId to appVersion in RN source map upload. Fixed infinite loop in EventDeserializer that froze the agent on launch. Changed default session replay masking mode to not allow unmasking using programmatic APIs and fixed UIKit override APIs. Fixed crash that could occur in NRMAWKWebViewNavigationDelegate webViewWebContentProcessDidTerminate. Ensured session replay data uploads on next launch if it failed to upload when the app closed. Discarded permanently-rejected (400/403) crash reports. Added TTL eviction for offline storage (#786). Fixed NRMAHarvestController initialize crash (#793).","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-773","eolDate":"2027-07-02"},{"agent":"ios","date":"2026-05-26","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.7.2.zip","version":"7.7.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release fix: NR-563752 fix for hasReplay getting added to errorMode before fullMode (#728 ) — @mbruin-NR fix: Adds UIColor safety to MSR to resolve reported crash. (#737 ) — @cdillard-NewRelic fix: Added a fix for crash in NRMAHarvester transitionToConnected:] (NRMAHarvester transitionToConnected:] (NRMAHarvester.mm:549) (#742 ) — @cdillard-NewRelic fix: NR-567271 crash fix hex library (#743 ) — @cdillard-NewRelic NR-566589 Persist session attributes on each stored error.  (#736 ) — @mbruin-NR fix: NR-568021 - fix crash in NRMAMethodProfiler.m (#744 ) — @cdillard-NewRelic fix: Fixed crash that could occur in HexStore.cxx when sending lots of HeX (#745 ) — @cdillard-NewRelic NR-567933 - fix RBMovedDisplayListContents (#747 ) — @cdillard-NewRelic","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-772","eolDate":"2027-05-26"},{"agent":"ios","date":"2026-04-22","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.7.1.zip","version":"7.7.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Mobile Session Replay Enhancements. Fix lifetime/threading race in NRMAHarvestController.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-771","eolDate":"2027-04-22"},{"agent":"ios","date":"2026-03-25","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.7.0.zip","version":"7.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Session Replay Blocked Views:  Added new blocked views functionality. For UIKit use \"nr-block\" accessibility id, new UIView blockView, or in SwiftUI NRConditionalMaskView with blockView=true to block regions from capture during session replay. Fixed in this release Fixed an overheating issue caused by excessive logging in rare cases. Resolved a bug in NewRelic.setMaxOfflineStorageSize. During harvest handle status code 0. Resolved issues in getAndClearFrames and flattenTree.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-770","eolDate":"2027-03-25"},{"agent":"ios","date":"2026-03-06","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.6.3.zip","version":"7.6.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Bug fixes and performance enhancements.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-763","eolDate":"2027-03-06"},{"agent":"ios","date":"2026-02-18","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.6.2.zip","version":"7.6.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Restored iOS 15 support. Session Replay Enhancements - we have added fixes for SwiftUI colors that should improve replay fidelity Session Replay Stability - we have fixed a number of issues that could occur. We have fixed an issue that could occur on older iOS devices.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-762","eolDate":"2027-02-18"},{"agent":"ios","date":"2026-01-22","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.6.1.zip","version":"7.6.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Important This release bumps the required iOS version of the New Relic iOS agent to iOS 16. iOS 15 support will come back in a future version. New in this release Updated the public preview of mobile Session Replay to include sampling for errored sessions and fixed issues related to Session Replay. Fixed in this release Fixed an issue that prevented distributed tracing from functioning in certain edge cases. Added stability fixes for identified issues.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-761","eolDate":"2027-01-22"},{"agent":"ios","date":"2025-11-03","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.6.0.zip","version":"7.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Important This release bumps the required iOS version of the New Relic iOS agent to iOS 16. New in this release Includes Public Preview of Mobile Session Replay. Fixed in this release Fixed issue with handled exceptions that could occur when logging. Fixed incorrect parameter naming warning.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-760","eolDate":"2026-11-03"},{"agent":"ios","date":"2025-08-18","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.5.9.zip","version":"7.5.9","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Agent is built using Xcode 16.4. Fixed an issue that could cause distributed tracing to not have all required account information at start of a session. Fixed an issue that could cause a crash on agent start.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-759","eolDate":"2026-08-18"},{"agent":"ios","date":"2025-07-30","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.5.8.zip","version":"7.5.8","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Starting from iOS SDK version 7.5.4, a change has been implemented that causes previously suppressed Handled Exception events to be reported. Please update to New Relic iOS agent 7.5.9. We've identified a bug in iOS SDK version 7.5.8 that could cause incorrect data upload, and a fix is included in the New Relic iOS agent 7.5.9 release. Please update to New Relic iOS agent 7.5.9. We've identified a bug in iOS SDK version 7.5.7 that could cause a crash on agent launch, and a fix is included in the New Relic iOS agent 7.5.9 release. Fixed in this release Agent is built using Xcode 16.4. Fixed an issue that could cause distributed tracing to not have all required account information at start of a session. Fixed an issue that could cause a crash on agent start.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-758","eolDate":"2026-07-30"},{"agent":"ios","date":"2025-07-28","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.5.7.zip","version":"7.5.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Starting from iOS SDK version 7.5.4, a change has been implemented that causes previously suppressed Handled Exception events to be reported. Please update to New Relic iOS agent 7.5.8. We've identified a bug in iOS SDK version 7.5.7 that could cause a crash on agent launch, and a fix is included in the New Relic iOS agent 7.5.8 release. Fixed in this release Agent is built using Xcode 16.4. Fixed an issue that could cause distributed tracing to not have all required account information at start of a session.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-757","eolDate":"2026-07-28"},{"agent":"ios","date":"2025-06-05","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.5.6.zip","version":"7.5.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Starting from iOS SDK version 7.5.4, a change has been implemented that causes previously suppressed Handled Exception events to be reported. Fixed in this release Agent is built using Xcode 16.3. This should correct any errors related to Code Coverage when using the New Relic iOS agent with Xcode 16.3. Fixed in an issue that could cause distributed tracing account to be set incorrectly. Fixed an issue that could cause the agent to crash when setting session attributes.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-756","eolDate":"2026-06-05"},{"agent":"ios","date":"2025-04-22","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.5.5.zip","version":"7.5.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Starting from iOS SDK version 7.5.4, a change has been implemented that causes previously suppressed Handled Exception events to be reported. Fixed in this release Addressed customer-reported crashes and bugs. Fixed a SPM version warning. Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.6.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-755","eolDate":"2026-04-22"},{"agent":"ios","date":"2025-03-06","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.5.4.zip","version":"7.5.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Starting from iOS SDK version 7.5.4, a change has been implemented that causes previously suppressed Handled Exception events to be reported. Fixed in this release Fixed crash that could occur when recording handled exceptions. Fixed various crashes that could occur when using the New Relic iOS agent. The New Relic iOS agent now includes Session Attributes in Mobile Logs. Fixed an issue that could occur when sending multiple handled exceptions to New Relic. The New Relic iOS agent will now will prevent data loss when sending multiple handled exceptions. Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.6.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-754","eolDate":"2026-03-06"},{"agent":"ios","date":"2024-12-04","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.5.3.zip","version":"7.5.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release The tracked headers set in addHTTPHeaderTrackingFor  are now correctly added to network request events manually captured using noticeNetworkRequestForURL . Fixed a bug in the new event system that prevented adding an attribute with a key that contain a reserved key string as a prefix. Made changes to address the NRMA__deallocInteractionHistoryList crash reported by users. Other notes The iOS agent now supports automatic log collection for remote logging. This feature is limited to NSLog(),  Swift print(), and other print-family functions. To enable it, use the NRFeatureFlag_AutoCollectLogs feature flag. For more information on how to enable and configure remote logging, visit our documentation . Changed the agent to agent to consistently send the sampled flag as '01' (true) in the W3C Traceparent header to maintain trace continuity with OpenTelemetry agents, which expect '00' (false) for dropped spans and '01' (true) for sampled spans. Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.6.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-753","eolDate":"2025-12-04"},{"agent":"ios","date":"2024-09-23","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.5.2.zip","version":"7.5.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed an issue that could cause app hangs. Fixed an issue that caused events created in applicationDidFinishLaunchingWithOptions to not be reported. Fixed a crash that could occur when using the NRFeatureFlag_NewEventSystem and forming the attribute json in a harvest. Fixed a crash that could occur from a NRMAPayload object while using the NRFeatureFlag_NewEventSystem. Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.6.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-752","eolDate":"2025-09-23"},{"agent":"ios","date":"2025-10-07","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.5.11.zip","version":"7.5.11","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed performance issues that could occur when using Interaction Tracing. Fixed a log related to Distributed Tracing that could be incorrectly shown.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-7511","eolDate":"2026-10-07"},{"agent":"ios","date":"2025-09-15","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.5.10.zip","version":"7.5.10","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed a crash that could occur on agent start.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-7510","eolDate":"2026-09-15"},{"agent":"ios","date":"2024-08-21","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.5.1.zip","version":"7.5.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Added watchOS as a compatible environment for the iOS agent. Fixed to work with SPM and Cocoapods. For more information on using the agent in a watchOS project visit our documentation. Starting the New Relic agent to your watchOS project Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.6.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-751","eolDate":"2025-08-21"},{"agent":"ios","date":"2024-06-28","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.5.0.zip","version":"7.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Additional fixes for an issue that could cause CryptoKit or NSCoding warnings in some environments. Fixed a bug when using setUserId that could cause some events to not align with the correct userId during a session. Fixed a bug when using NRFeatureFlag_BackgroundReporting that caused some events created in the background to not get reported. New Relic iOS agent now supports remote logging. Enable this feature within your mobile entity applications setting page to turn on logging for the agent. For more information on how to enable and configure remote logging visit our documentation. Fixed a bug that caused crash reports to be uploaded without session attributes when NRFeatureFlag_HandledExceptionEvents is disabled. Other notes Added watchOS as a compatible environment for the iOS agent. For more information on using the agent in a watchOS project visit our documentation. Starting the New Relic agent to your watchOS project Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.6.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-750","eolDate":"2025-06-28"},{"agent":"ios","date":"2024-02-28","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.4.9.zip","version":"7.4.9","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed events maximum buffer size not maintaining after backgrounding. Fixed issue when /connect has a missing harvest configuration. Other notes Added the ability to store harvests that previously would be lost if the application doesn't have internet connection. These harvest are then sent after an internet connection is established and the next harvest successfully uploads. Use the + (void) setMaxOfflineStorageSize:(unsigned int)megaBytes; API to set the maximum amount of data that can be stored locally. More info The feature flag NRFeatureFlag_OfflineStorage was added to disable the above mentioned offline storage. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. The iOS and tvOS agents were deprecated with the release of version 7.2.1 of the XCFramework  agent. As of this release, the oldest supported version is 7.0.0 of the XCFramework .","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-749","eolDate":"2025-02-28"},{"agent":"ios","date":"2023-12-11","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.4.8.zip","version":"7.4.8","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release [#fixed] Fixes async requests so they appear in distributed tracing. Adds NRFeatureFlag_NewEventSystem feature flag. Enable this flag to use our new, more stable, event system for iOS agent: Adds configurable request header instrumentation to network events: The agent will now produce network event attributes for select header values if it detects headers on the request. The header names to instrument pass into the agent when started. For more information, see Adding Tracked Headers  in the Mobile Monitoring documentation. Adds GraphQL attributes to network events: If the agent detects request headers from Apollo GraphQL servers, it will add additional attributes to the network request event. For more information, see Adding Tracked Headers  in the Mobile Monitoring documentation. Other notes With the 7.4.6 release, the XCFramework no longer includes the dsym-upload-tools. You can find the dsym-upload-tools in the dsym-upload-tools folder of the https://github.com/newrelic/newrelic-ios-agent-spm Swift Package Manager repository. Please copy the dsym-upload-tools directory into your application source code directory by copying the XCFramework into your project or using Cocoapods if you're integrating the New Relic iOS Agent. Use the run script below in your Xcode build phases to perform symbol upload steps during app builds in Xcode. We recommend using the swift package manager for your installation method. Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.2.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-748","eolDate":"2024-12-11"},{"agent":"ios","date":"2023-10-02","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.4.7.zip","version":"7.4.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed required privacy manifest for iOS 17. Other notes With the 7.4.6 release the dsym-upload-tools are no longer included inside the XCFramework. The dsym-upload-tools are available in the dsym-upload-tools folder of the https://github.com/newrelic/newrelic-ios-agent-spm Swift Package Manager repository. Please copy this dsym-upload-tools directory to your applications source code directory if you are integrating the New Relic iOS Agent by copying XCFramework into project or using cocoapods. Please use the run script below in your Xcode build phases to perform symbol upload steps during app builds in Xcode. Instrumentation of async await url sessions that was added in 7.4.1 has been moved behind a feature flag in 7.4.6. To use that feature, include the NRFeatureFlag_SwiftAsyncURLSessionSupport flag in the enableFeatures function. In  version 7.4.6 of the iOS agent, the Python-based symbol upload scripts were removed. Update to the Swift based script. This artifact was built using Xcode 14.3 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher and Swift Package Manager. The agent should be used with the latest Xcode version (Xcode 14.3 at the time of release). Swift Package Manager is the preferred installation method. Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.2.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-747","eolDate":"2024-10-02"},{"agent":"ios","date":"2023-07-24","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.4.6.zip","version":"7.4.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed framework signing to be compatible with Xcode 15. Fixed compatibility with RxWebKit. Other notes With this release the dsym-upload-tools are no longer included inside the XCFramework. The dsym-upload-tools are available in the dsym-upload-tools folder of the https://github.com/newrelic/newrelic-ios-agent-spm Swift Package Manager repository. Please copy this dsym-upload-tools directory to your applications source code directory if you are integrating the New Relic iOS Agent by copying XCFramework into project or using cocoapods. Please use the run script below in your Xcode build phases to perform symbol upload steps during app builds in Xcode. Instrumentation of async await url sessions that was added in v7.4.1 has been moved behind a feature flag. To use that feature, include the NRFeatureFlag_SwiftAsyncURLSessionSupport flag in the enableFeatures function. In  version 7.4.6 of the iOS agent, the Python-based symbol upload scripts were removed. Update to the Swift based script. This artifact was built using Xcode 14.3 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher and Swift Package Manager. The agent should be used with the latest Xcode version (Xcode 14.3 at the time of release). Swift Package Manager is the preferred installation method. Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.2.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-746","eolDate":"2024-07-24"},{"agent":"ios","date":"2023-05-31","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.4.5.zip","version":"7.4.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Added a feature flag for FedRAMP support. Fixed an issue with tvOS not reporting carrier type as wifi. Fixed an issue where the iOS agent prevented webView:decidePolicyForNavigationAction:decisionHandler: from getting called. Fixed a bug that stopped http error data from getting uploaded. Other notes Instrumentation of async await url sessions that was added in v7.4.1 has been moved behind a feature flag. To use that feature include the NRFeatureFlag_SwiftAsyncURLSessionSupport flag in the enableFeatures function. Deprecation notice: The 7.4.0 version introduced a new Swift symbol upload script. See installation instructions  for details on how to update to the new script. In a future version of the iOS agent, the Python-based symbol upload scripts will be removed. This artifact was built using Xcode 14.2 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher and Swift Package Manager. The agent should be used with the latest Xcode version (Xcode 14.2 at the time of release). For Mac Catalyst, the zip file installation may integrate more easily than using CocoaPods. Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.2.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-745","eolDate":"2024-05-31"},{"agent":"ios","date":"2023-04-17","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.4.4.zip","version":"7.4.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed an issue with the agent that could cause a crash when releasing the Payload object. Fixed an issue with the agent that could cause crashes during web view instrumentation. Other notes Apple no longer supports bitcode-based submissions to the App Store. The New Relic iOS agent should not be used with bitcode-based apps. The included dSYM upload script will not work with bitcode-based apps. Deprecation notice: The 7.4.0 version introduced a new Swift symbol upload script. See installation instructions  for details on how to update to the new script. In a future version of the iOS agent, the Python-based symbol upload scripts will be removed. This artifact was built using Xcode 14.2 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher and Swift Package Manager. The agent should be used with the latest Xcode version (Xcode 14.2 at the time of release). For Mac Catalyst, the zip file installation may integrate more easily than using CocoaPods. Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.1.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-744","eolDate":"2024-04-17"},{"agent":"ios","date":"2023-03-01","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.4.3.zip","version":"7.4.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed an issue with the agent that could cause API MISUSE to log to the console. Other notes Apple no longer supports bitcode-based submissions to the App Store. The New Relic iOS agent should not be used with bitcode-based apps. The included dSYM upload script will not work with bitcode-based apps. Deprecation notice: The 7.4.0 version introduced a new Swift symbol upload script. See installation instructions  for details on how to update to the new script. In a future version of the iOS agent, the Python-based symbol upload scripts will be removed. This artifact was built using Xcode 14.2 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher and Swift Package Manager. The agent should be used with the latest Xcode version (Xcode 14.2 at the time of release). For Mac Catalyst, the zip file installation may integrate more easily than using CocoaPods. Support statement As of this release, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version is 7.3.0 of the XCFramework .","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-743","eolDate":"2024-03-01"},{"agent":"ios","date":"2023-02-23","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.4.2.zip","version":"7.4.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed an issue with the agent that could cause Apple App Store rejection. Other notes Apple no longer supports bitcode-based submissions to the App Store. The New Relic iOS agent should not be used with bitcode-based apps. The included dSYM upload script will not work with bitcode-based apps. Deprecation notice: The 7.4.0 version introduced a new Swift symbol upload script. See installation instructions  for details on how to update to the new script. In a future version of the iOS agent, the Python-based symbol upload scripts will be removed. This artifact was built using Xcode 14.2 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher and Swift Package Manager. The agent should be used with the latest Xcode version (Xcode 14.2 at the time of release). For Mac Catalyst, the zip file installation may integrate more easily than using CocoaPods. Support statement As of this release, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version is 7.3.0 of the XCFramework .","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-742","eolDate":"2024-02-23"},{"agent":"ios","date":"2024-05-29","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.4.12.zip","version":"7.4.12","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed an issue that could cause the distributed tracing header to be missing on some requests. Fixed issues that could cause CryptoKit or NSCoding warnings in some environments. A feature flag has been added to enable background reporting. Background reporting is disabled by default. Enable the NRFeatureFlag_BackgroundReporting feature flag to turn on background reporting. Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.6.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-7412","eolDate":"2025-05-29"},{"agent":"ios","date":"2024-04-30","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.4.11.zip","version":"7.4.11","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed an issue with the NewEventSystem flag that could cause crash data to upload incorrectly. Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.6.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-7411","eolDate":"2025-04-30"},{"agent":"ios","date":"2024-03-19","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.4.10.zip","version":"7.4.10","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed a bug that caused some distributed tracing headers not being attached to network events. Fixed the offline attribute not being added in the old event system. Fixed an unrecognized selector crash in the react native agent for iOS 13 & 14 devices. Other notes The NRFeatureFlag_OfflineStorage feature flag will now be disabled by default. For more information on configuring the offline storage feature. More info Support statement As of iOS agent version 7.4.1, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version of the XCFramework  is 7.3.2.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-7410","eolDate":"2025-03-19"},{"agent":"ios","date":"2023-02-22","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.4.1.zip","version":"7.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Added Network Monitoring support for async URLSession functions. Fixed an issue that would cause conflicts with other iOS network monitoring tools such as FlipperKit. Fixed an issue where install metrics were not sent with initial metric payload. Fixed an issue that caused irrelevant logs to be printed to the console. Fixed an issue that could cause crashes when monitoring network failures. Other notes Apple no longer supports bitcode-based submissions to the App Store. The New Relic iOS agent should not be used with bitcode-based apps. The included dSYM upload script will not work with bitcode-based apps. Deprecation notice: The 7.4.0 version introduced a new Swift symbol upload script. See installation instructions  for details on how to update to the new script. In a future version of the iOS agent, the Python-based symbol upload scripts will be removed. This artifact was built using Xcode 14.2 with a minimum deployment target of iOS version 9.0. Compatible with CocoaPods 1.10 or higher and Swift Package Manager. The agent should be used with the latest Xcode version (Xcode 14.2 at the time of release). For Mac Catalyst, the zip file installation may integrate more easily than using CocoaPods. Support statement As of this release, the iOS agent will consolidate previously separate XCFramework and tvOS agents into a singular iOS agent. As of this release, the oldest supported version is 7.3.0 of the XCFramework .","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-741","eolDate":"2024-02-22"},{"agent":"ios","date":"2020-09-11","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_XCFramework_Agent_7.0.0.zip","version":"7.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The New Relic iOS agent is now deprecated. Please refer to the New Relic XCFramework Agent  for iOS support.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-700","eolDate":"2023-09-11"},{"agent":"ios","date":"2019-10-24","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.9.0.zip","version":"6.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Adds support for crash reports from A12 devices. Fixes Improved possible race-condition with accessing currentSessionId. Note: This release was built with Xcode11 and may be incompatible with earlier versions of Xcode.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-690","eolDate":"2022-10-24"},{"agent":"ios","date":"2019-09-13","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.8.0.zip","version":"6.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Removed support and instrumentation for deprecated UIWebView. Fixes Fixed memory leak in WKWebView instrumentation. Fixed incorrect time units recorded for response time of network errors. It was reporting as milliseconds, and it was corrected to seconds.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-680","eolDate":"2022-09-13"},{"agent":"ios","date":"2019-06-07","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.7.0.zip","version":"6.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements The NewRelic NSURLSessionTaskDelegate object now provides an isKindOfClass: method that presents as the wrapped class. This improves compatibility with other frameworks. Fixes Fixes potential crash if _dyld_register_func_for_add_image callback is executed in an unexpected way.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-670","eolDate":"2022-06-07"},{"agent":"ios","date":"2019-03-14","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.6.0.zip","version":"6.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Bumped session attribute limit to 128 from 64. Fixes +recordCustomEvent:withName:attributes: no longer requires a dictionary to capture name. Values in attributes dictionaries passed to recordEvent APIs will no longer be cast to int or float values, which degraded large data types.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-660","eolDate":"2022-03-14"},{"agent":"ios","date":"2019-02-05","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.5.0.zip","version":"6.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Improved dSYM upload script.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-650","eolDate":"2022-02-05"},{"agent":"ios","date":"2018-10-30","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.4.1.zip","version":"6.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Corrects bug in dSYM upload script introduced by Xcode10's new build system.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-641","eolDate":"2021-10-30"},{"agent":"ios","date":"2018-10-09","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.4.0.zip","version":"6.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes +setMaxEventBufferTime and +setMaxEventPoolSize now persist between background/foreground dSYM upload script has been improved. It is now better at finding and uploading dSYMs. Improvements Reduced agent size by removing old architectures. Note: with the removal of i386 the agent will no longer build with iPhone4S simulators (however, it will still run on iPhone4S devices.) Note: This agent was built with Xcode10. It may be necessary to use Xcode10 for compatibility.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-640","eolDate":"2021-10-09"},{"agent":"ios","date":"2018-09-12","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.3.2.zip","version":"6.3.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed race condition in handled exceptions component, which had the potential of crashing on background inside std::recursive_mutex::lock()","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-632","eolDate":"2021-09-12"},{"agent":"ios","date":"2018-06-01","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.3.0.zip","version":"6.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Agent can now handle region specific application tokens. Moved New Relic specific files out of users' \"Documents\" directory. Fixes Fixed inconsistency in deviceManufacturer session attribute; it will always be set as \"Apple, Inc\". memUsageMb session attribute will now be stored as a numeric value rather than a string value. Fixed race-condition in gesture instrumentation that could cause a crash on app background. RequestUrl and RequestPath attributes on MobileRequest and MobileRequestError events will consistently be not URL-encoded. Crash reports will now be uploaded immediately after processing on subsequent launch. Fixed potential race-condition in +[NewRelic stopCurrentInteraction:(NSString*)activityIdentifier]; that could result in dead-lock.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-630","eolDate":"2021-06-01"},{"agent":"ios","date":"2018-03-06","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.2.0.zip","version":"6.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Improved performance of symbol map upload script. Improved performance of recordHandledException API. Removed deprecated APIs. Fixes Prevents possible corrupted event data. Event/Attribute APIs now accept NSNumbers containing BOOL values +[NewRelic setApplicationVersion:] and +[NewRelic setApplicationBuild:] will now throw an exception if called after the agent is started.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-620-0","eolDate":"2021-03-06"},{"agent":"ios","date":"2020-08-25","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.14.0.zip","version":"6.14.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added API to allow the agent data upload hosts to be set during agent start-up. ( +(void) startWithApplicationToken:andCollectorAddress:andCrashCollectorAddress: )","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-6140","eolDate":"2023-08-25"},{"agent":"ios","date":"2020-07-21","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.13.0.zip","version":"6.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Removed deprecated use of NSURLConnection methods Improved ptr auth stripping in arm64e crashes.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-6130","eolDate":"2023-07-21"},{"agent":"ios","date":"2020-04-20","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.11.0.zip","version":"6.11.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes The New Relic WKWebView navigation delegate wrapper will respond as the wrapped delegate when isKindOfClass: is called. +[NewRelic recordHandledException:(NSException*)] will no longer accept exceptions that were not thrown.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-6110","eolDate":"2023-04-20"},{"agent":"ios","date":"2018-02-09","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.1.1.zip","version":"6.1.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed an agent hang when relaunching an app after a crash. In some cases, the agent would appear to deadlock in the agent's startWithApplicationToken:appToken method after relaunching, which has been addressed.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-611","eolDate":"2021-02-09"},{"agent":"ios","date":"2019-11-20","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.10.0.zip","version":"6.10.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Now packaged with arm64e architectures. dSYM upload script can handle paths with spaces in them.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-6100","eolDate":"2022-11-20"},{"agent":"ios","date":"2017-12-14","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.1.0.zip","version":"6.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release MobileRequestError events now contain the response body returned in the network request response, if one exists. Response bodies will only be reported if the http response body header capture feature flag  is enabled. HttpResponseBodyCapture is enabled by default. Response body data will be limited to the first 4096 bytes (the Insights attribute limit). MobileRequestError events now also contain any cross-application tracing (CAT) data returned in the response headers. See Introduction to cross-application traces  for more information. Fixed in this release Fixed a memory leak in NRMAReachability.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-610","eolDate":"2020-12-14"},{"agent":"ios","date":"2017-11-08","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_6.0.0.zip","version":"6.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Major release This agent release was built with Xcode 9, breaking backwards compatibility with older versions of Xcode. Improvements Swift error support. This release adds a new API in the NewRelic object +recordError:(NSError*)error withAttributes:(NSDictionary*)attributes;. This allows Swift errors to be recorded as MobileHandledException events and to be viewable in the Handled Exception Mobile UI page. MobileRequest events are on by default. MobileRequest events will now be transmitted by default. They can be turned off by calling [NewRelic disableFeatures:NRFeatureFlag_NetworkRequestEvents] before [NewRelic startWithApplicationToken:...]. Improved post build script. Symbol files will now be processed at build time and uploaded to New Relic using the postbuild.sh, rather than uploading the entire dSYM at build time. This will reduce network overhead as well as improve the time it takes for crashes to symbolicate. Fixes Fixed low frequency crash in NRMAHarvestableMetric.m:45. Resolved memory leaks.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-600","eolDate":"2020-11-08"},{"agent":"ios","date":"2017-01-10","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.9.0.zip","version":"5.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Adds helper method +setUserId: to NewRelic.h which sets a session attribute, userId, with the passed value. This method is effectively the same as [NewRelic setAttribute:@\"userId\" value:<username>];","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-590","eolDate":"2020-01-10"},{"agent":"ios","date":"2016-09-27","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.8.3.zip","version":"5.8.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Corrected crashing issue the affected some ARMv7s device. Improvements This version of the iOS agent is built with Xcode 8, and Xcode 8 is required to build with this agent. If earlier versions of Xcode are required use iOS Agent 5.8.1.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-583","eolDate":"2019-09-27"},{"agent":"ios","date":"2016-09-22","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.8.2.zip","version":"5.8.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added support for control characters in Insights data. Control characters will now be displayed by their common escaped character representation. For example: an 'end-of-text' control character will be displayed as '^C'. Fixes Removed instrumentation of ASI networking framework. This prevents collisions with Apple's private API scans, which produces a false positive when scanning our instrumentation of this library. We recommend anyone still using ASI for networking to use our custom network instrumentation  tools going forward.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-582","eolDate":"2019-09-22"},{"agent":"ios","date":"2016-09-09","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.8.1.zip","version":"5.8.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Information This release is a \"roll-forward\" of release 5.7.1. Agent release 5.8.0 was discovered to have compatibility issues with a small set of devices and has been removed.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-581","eolDate":"2019-09-09"},{"agent":"ios","date":"2016-09-02","downloadLink":null,"version":"5.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added support for control characters in insights data. Control characters will now be displayed by their common escaped character representation. e.g.: an 'end-of-text' control character will be displayed a '^C'. This release was removed as compatibility issues were discovered. See iOS agent release v5.8.1  notes for more details.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-580","eolDate":"2019-09-02"},{"agent":"ios","date":"2016-08-02","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.7.1.zip","version":"5.7.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes The dSYM upload script can now handle targets with spaces in the name.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-571","eolDate":"2019-08-02"},{"agent":"ios","date":"2016-07-29","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.7.0.zip","version":"5.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Embedded framework support in crash reporting: If your application is built with an embedded framework, the agent will now automatically upload all dSYMs associated with your app and utilize them in symbolication of crash reporting. Fixes UIWebView instrumentation improvements: Network requests coming out of UIWebViews will no longer get double recorded. Corrected some instances where networking errors were being recorded as HTTP errors.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-570","eolDate":"2019-07-29"},{"agent":"ios","date":"2016-06-16","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.6.0.zip","version":"5.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements tvOS is now supported! The New Relic agent will now build and run on your tvOS apps with the same great features as the iOS agent! For more information, learn how to install and configure the iOS agent for tvOS apps . Fixes Fixed crash caused by a notification that could occur if the app is shutting down when it attempts to access deallocated objects.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-560","eolDate":"2019-06-16"},{"agent":"ios","date":"2016-05-23","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.5.2.zip","version":"5.5.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Crash Report Upload Retry Limiting Crash report upload retries will now be limited. This is to prevent crashes from being queued eternally. Platform Tracking A new API, +setPlatform:, was added to NewRelic.h. This will allow bold users to set which platform their app is built with (for example, Unity, Xamarin, React, etc.). This will allow for additional features in the future. Fixes Insights API Improvements +recordEvent:withAttributes: and +setAttribute:withValue: will no longer block the calling thread.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-552","eolDate":"2019-05-23"},{"agent":"ios","date":"2016-05-06","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.5.1.zip","version":"5.5.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Information This release is a \"roll-forward\" of release 5.4.1. Agent release 5.5.0 was discovered to have compatibility issues with armv7 architecture devices.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-551","eolDate":"2019-05-06"},{"agent":"ios","date":"2016-05-03","downloadLink":null,"version":"5.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Crash Report Upload Retry Limiting Crash report upload retries will now be limited. This is to prevent crashes from being queued eternally. Platform Tracking A new API, +setPlatform:, was added to NewRelic.h. This will allow bold users to set which platform their app is built with (for example, Unity, Xamarin, React, etc.). This will allow for additional features in the future. Fixes Insights API Improvements +recordEvent:withAttributes: and +setAttribute:withValue: will no longer block the calling thread. This release is no longer available due to compatibility issues. See iOS agent release v5.5.1 notes  for more details.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-550","eolDate":"2019-05-03"},{"agent":"ios","date":"2016-03-18","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.4.1.zip","version":"5.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Corrects possible crash on launch if key data file is corrupted.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-541","eolDate":"2019-03-18"},{"agent":"ios","date":"2016-03-04","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.4.0.zip","version":"5.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added new feature flag, NRFeatureFlag_DefaultInteraction, which allows default interactions to be disabled. Disabling this feature flag will allow the agent to only capture custom interactions. Fixes Corrected warnings inadvertently caused by new Xcode build setting, CLANG_ENABLE_MODULES = YES.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-540","eolDate":"2019-03-04"},{"agent":"ios","date":"2016-01-26","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.3.6.zip","version":"5.3.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Improved the dSYM archive uploader so it will now dispatch asynchronously to the build, and will retry the upload up to 3 times. Custom metrics will now accept spaces in the name. Improved Cocoapods support. The NewRelicAgent podspec no longer includes version strings in framework paths. This eases pod management and reduces diff clutter when dealing with version control software. Fixes Corrected a bug in crash reporting where certain internal symbols were globally visible when the -ObjC linker flag is present. Corrected a bug in crash reporting where Cortex-A9 chips were reported as ARM-Unknown in crash reports. Validating the length of activities, only allowing those with a start time within the current session.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-536","eolDate":"2019-01-26"},{"agent":"ios","date":"2016-01-07","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.3.5.zip","version":"5.3.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements This release changes the way Monthly Active Unique devices (MAUs) are identified. The iOS agent now uses the iOS provided identifierForVendor  from Apple to count unique devices.  Fixes Improved internal management of application termination, reducing occurrences of a specific agent crash. The agent will no longer harvest in the background if the app is executing background activities.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-535","eolDate":"2019-01-07"},{"agent":"ios","date":"2015-11-19","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.3.4.zip","version":"5.3.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added new Insights attributes tracking new app installs and upgrades, for the upcoming Mobile Version Trends Report. Fixes Fixed missing Cross Application Trace  header in HTTP Error data. This will result in more detailed data in HTTP Errors dashboards. Off-loaded interaction event generation from main thread to background thread. This caused UI sluggishness under extreme circumstances","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-534","eolDate":"2018-11-19"},{"agent":"ios","date":"2015-09-01","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.2.2.zip","version":"5.2.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes The iOS SDK now accepts control characters (such as \\t, \\r, \\n, etc.) while sending custom attributes and events for New Relic Insights. Fixes a problem while sending quote characters in custom attribute or event data. Addresses a crash that could occur in the iOS CoreTelephony library when the agent gathers the carrier name. Mitigates a rare scenario that could result in the agent harvest process occurring twice when the app was sent to the background. Notes This is the last iOS agent release to support building with Xcode 6 or earlier. This is the last iOS agent release to support iOS 5.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-522","eolDate":"2018-09-01"},{"agent":"ios","date":"2017-10-17","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.15.0.zip","version":"5.15.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Handled Exceptions  in Objective-C The iOS agent now exposes an API on the NewRelic object: Passing a caught exception to this API will record details as a MobileHandledException event and record the thread details of the exception. This information will be available in the new UI for handled exceptions. A new feature flag is available, NRFeatureFlag_HandledExceptionEvents. This toggles the generation of MobileHandledExceptions events and auxiliary data. It is enabled by default Fixes Fixed memory leak introduced by NSURLSession instrumentation.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-5150","eolDate":"2020-10-17"},{"agent":"ios","date":"2017-08-01","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.14.2.zip","version":"5.14.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes crash in WKWebView instrumentation caused by a nil WKNavigation object being passed to the web view delegate methods.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-5142","eolDate":"2020-08-01"},{"agent":"ios","date":"2017-07-11","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.14.1.zip","version":"5.14.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Removed URL parameters from MobileRequest and MobileRequestError events. The concern being there may be confidential information contained in these parameters.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-5141","eolDate":"2020-07-11"},{"agent":"ios","date":"2017-06-20","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.14.0.zip","version":"5.14.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Now reports network request events to Insights! This feature must be enabled when starting the agent using [NewRelic enableFeatures:NRFeatureFlag_NetworkRequestEvents]. When enabled all network calls will be tracked, in addition to network errors. These new events will be available under the MobileNetworkRequest eventType. Examples of how to query these new events is available in our documentation: Mobile request query examples (MobileRequest) .","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-5140","eolDate":"2020-06-20"},{"agent":"ios","date":"2017-05-11","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.13.0.zip","version":"5.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Features Added a new MobileBreadcrumb custom event type that allows you to annotate the execution of your app, to help troubleshoot crashes and provide greater detail in Insights. Record this new event type with the method +recordBreadcrumb:withAttributes:. Added an additional +recordCustomEvent:name:withAttributes method that takes the event name as an optional parameter. This avoids the need to add a name attribute in the passed attribute set.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-5130","eolDate":"2020-05-11"},{"agent":"ios","date":"2017-04-20","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.12.3.zip","version":"5.12.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed rare app launch crash caused by collision of JSON serialization & New Relic's method instrumentation. Added better messaging for custom eventType validation errors. Improved crash report data quality.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-5123","eolDate":"2020-04-20"},{"agent":"ios","date":"2017-03-29","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.12.2.zip","version":"5.12.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes The New Relic post-build script will now capture and upload dSYM files created in subfolders of the build folder.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-5122","eolDate":"2020-03-29"},{"agent":"ios","date":"2017-03-09","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.12.0.zip","version":"5.12.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Adds new API +[NewRelic recordCustomEvent:(NSString*)eventType withAttributes:(NSDictionary*)attributes] This method replaces +[NewRelic recordEvent:(NSString*)name withAttributes:(NSDictionary*)attributes] which is now deprecated, with the intention of removal in the future. The new API creates a new event with an event type specified by the eventType parameter, whereas the deprecated method create a event with the Mobile event type and an attribute with the name 'name' and the value of the name parameter. This change satisfies customer requests for: Improved Insights query performance Defining custom event types Finding custom event in Insights more easily Flexibility to define data retention per custom event type","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-5120","eolDate":"2020-03-09"},{"agent":"ios","date":"2017-02-27","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.11.0.zip","version":"5.11.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements This release adds a new Insights event type: MobileRequestError. This new event tracks networking and http errors during the app's lifecycle, adding the ability to slice and dice network error data! More details can be found at Mobile Request Error Events . This agent now applies the lastInteraction attribute to all events, not just crash events. The applications build value is now added as a default session attribute: appBuild.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-5110","eolDate":"2020-02-27"},{"agent":"ios","date":"2017-02-07","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.10.1.zip","version":"5.10.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Corrects WKWebView instrumentation bug that results in the NavigationDelegate method, webView:didCommitNavigation: being called instead of webView:didStartProvisionalNavigation:. This would result in a crash if the former is implemented in the delegate, but the latter is not.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-5101","eolDate":"2020-02-07"},{"agent":"ios","date":"2017-01-23","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.10.0.zip","version":"5.10.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Adds limited network monitoring for WKWebView. Due to constraints within the WKWebView API data sent and received counts are not available.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-5100","eolDate":"2020-01-23"},{"agent":"ios","date":"2013-03-29","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_1.309.zip","version":"1.309","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Improvements Improved verbose logging Fixes Fixes a circular strong reference memory leak of NSURLRequest Ensures connection:didSendBodyData:totalBytesWritten:totalBytesExpectedToWrite: is dispatched to the correct thread","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-agent-1309","eolDate":"2016-03-29"},{"agent":"ios","date":"2015-10-29","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.3.2.zip","version":"5.3.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes This release fixed incorrect data validation for some custom Insights events. The event attribute value validation was too strict, causing it to sometimes incorrectly reject valid input.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-532","eolDate":"2018-10-29"},{"agent":"ios","date":"2015-10-13","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.3.1.zip","version":"5.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Adds IPv6 support to the iOS agent. At WWDC this year, Apple announced they will be requiring IPv6 compatibility for all submitted apps at some point in the future. Fixes Fixes a crash that can occur when the app is backgrounded and the OS forcibly destructs the app while the agent was still active. This caused critical agent code to be unexpectedly destructed while data was still being processed.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-531","eolDate":"2018-10-13"},{"agent":"ios","date":"2015-09-17","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.3.0.zip","version":"5.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements This release adds support for building apps with Xcode 7. Xcode 6 and earlier are no longer supported. If you require Xcode 6, use version 5.2.2  or earlier of the iOS agent. This release also adds Bitcode support, used in apps with Bitcode enabled (Bitcode is enabled by default in Xcode 7). Notes As of this release, the New Relic iOS agent no longer supports iOS 5. The minimum required version is now iOS 6.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-530","eolDate":"2018-09-17"},{"agent":"ios","date":"2015-08-17","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.2.1.zip","version":"5.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Prevents the execution of certain NSNotification observers during key background operations. This will mitigate a crash that could occur during that time frame within the associated observers.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-521","eolDate":"2018-08-17"},{"agent":"ios","date":"2015-07-30","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.2.0.zip","version":"5.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements The SDK now tracks the number and duration of network requests per interaction, which will be used in upcoming features. A session duration is now recorded for sessions that crash. Mobile crash events in Insights will have a session duration. Fixes Fixes a bug where certain HTTP request measurements were duplicated in interaction trace details. Improves the accuracy of recording measurements in the SDK.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-520","eolDate":"2018-07-30"},{"agent":"ios","date":"2015-06-30","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.1.2.zip","version":"5.1.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Improves overall agent performance. Fixes race condition that prevents session start metrics from being logged on app launch. Fixes crash in -setNRSessionAttribute:value: that can occasionally occur on app background or foreground.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-512","eolDate":"2018-06-30"},{"agent":"ios","date":"2015-06-03","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.1.0.zip","version":"5.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements The iOS SDK will now collect an app build identifier when an app crashes, which will be displayed in parentheses beside the version number in the Crash Details page in RPM. This value defaults to the string CFBundleVersion that is specified in Xcode build settings. If CFBundleVersion is not specified the build identifier will not be displayed. A new API method +setApplicationBuild:(NSString*)buildNumber was added to allow specifying a custom app build identifier, overriding the default value pulled from CFBundleVersion.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-510","eolDate":"2018-06-03"},{"agent":"ios","date":"2015-05-15","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.0.3.zip","version":"5.0.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Corrects an issue with default recorded attributes, ensuring osVersion and carrier attributes are sent properly. Prevents out-of-session network requests from being included in activity traces","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-503","eolDate":"2018-05-15"},{"agent":"ios","date":"2015-05-11","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.0.2.zip","version":"5.0.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes a crash in the agent that could occur when using the simulator for iOS 7.1 during testing. Resolves a rare crash scenario that may have occurred when the app was sent to the background.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-502","eolDate":"2018-05-11"},{"agent":"ios","date":"2015-05-01","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.0.1.zip","version":"5.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Corrects an issue where Session events may not have been sent to New Relic Insights.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-501","eolDate":"2018-05-01"},{"agent":"ios","date":"2015-05-01","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_5.0.0.zip","version":"5.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Insights for Mobile This release introduces Insights for New Relic Mobile.  The iOS SDK now automatically records Session, Interaction, and Crash events in New Relic Insights. After upgrading to this release, you will be able to build queries and dashboards in Insights with the new Mobile event type. All events include attributes reflecting session and unique install identifiers, device, OS, geography, duration and other data. See the Insights documentation  for a description of Mobile attributes and Insights usage details. Custom events In addition to the standard events available in Insights, you can now record custom events. Custom events have a name and set of key:value attributes, perfect for capturing usage, monetization, and custom performance data. Custom events are also available in Insights. See the Mobile Custom Event documentation  for details. Custom attributes In addition to event-specific attributes, this release provides support for install-scoped attributes. An attribute recorded in the app will be attached to every Session, Interaction, Crash, and Custom event reported from that instance of the app. Custom attributes are perfect for tracking durable information like account id, campaign origin, subscription level, etc. See the Mobile Custom Attribute documentation  for details.  The iOS API documentation  includes details on sending custom events and attributes to Insights.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-500","eolDate":"2018-05-01"},{"agent":"ios","date":"2014-10-08","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_4.83.zip","version":"4.83.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Improvements Crash reporting This release introduces crash reporting for mobile apps . Crash reporting supports capture and reporting of unhandled Objective-C runtime exceptions as well as native crashes like segfaults and bus errors. Crashes include Interaction trails:  a history of automatically instrumented actions that occurred during the app session leading up to the crashing event. No breadcrumbs needed. The SDK includes a [NewRelic crashNow] method to trigger a test crash quickly and easily. When an app is built for release, the debugging symbols are sent to New Relic (via a dSYM file) to automatically provide human-readable crash reports in the UI. Swift app compatibility This release can be safely included in Swift applications. While we do not yet support instrumentation of Swift code, the New Relic SDK is now capable of instrumenting the Objective-C code included in your Swift app. More configuration options An expanded runtime configuration API now supports disabling of crash reporting and interaction tracing, as well as enabling experimental Swift instrumentation  for dynamically invoked methods.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-483","eolDate":"2017-10-08"},{"agent":"ios","date":"2015-04-23","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_4.186.1.zip","version":"4.186.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Addresses a compatibility issue that could result in a crash when using Swift 1.2 and Xcode 6.3","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-41861","eolDate":"2018-04-23"},{"agent":"ios","date":"2015-01-29","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_4.186.zip","version":"4.186","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Addresses a potential crash in a rare case when attempting to capture data from a metadata file that is empty. Corrects an issue with custom interaction names that may not have been displayed properly. Fixes an issue where duplicate data may have been recorded from from NSURLSession.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-4186","eolDate":"2018-01-29"},{"agent":"ios","date":"2015-01-26","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_4.174.zip","version":"4.174","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Fixes a potential crash in UIImage constructor instrumentation.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-4174","eolDate":"2018-01-26"},{"agent":"ios","date":"2015-01-08","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_4.155.zip","version":"4.155","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Corrects a potential crash when an instrumented init method releases the self pointer or sets the self pointer to nil before invoking a superclass method.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-4155","eolDate":"2018-01-08"},{"agent":"ios","date":"2014-12-18","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_4.152.zip","version":"4.152","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Improvements Improved network instrumentation performance resulting from a change in the way we detect the network connection type, which also prevents the potential for a deadlock under high concurrency. The agent will raise an exception with detailed information in the event it detects a fatal conflict where another library interferes with our code instrumentation. Fixes Resolves an issue with ASI instrumentation that could cause a crash when receiving certain network level errors. Resolves a deadlock scenario that could occur during certain high-load circumstances.  Fixes an issue where heavy network load could potentially cause the OS Reachability functionality to hang, forcing the OS to terminate the app on launch.  NewRelic.h was updated to correct syntax issues causing compiler warnings.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-4152-0","eolDate":"2017-12-18"},{"agent":"ios","date":"2014-11-21","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_4.139.zip","version":"4.139","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Improvements Improved logging to identify when crash reporting is disabled during debugging. You can now disable the capture of the HTTP response body for requests by calling the disableFeature method and passing the flag NRMAFeatureFlag_httpResponseCapture. Added support for the armv7s architecture as it is not available in Xcode 6. The SDK was updated to accept the HTTP method in the signature of the [NewRelic noticeNetworkRequestForURL] and [NewRelic noticeNetworkFailureForURL] methods allowing more detailed information to be collected. The version of the New Relic iOS agent was added to the comments in NewRelic.h  for convenience. Fixes Corrected a potentially crashing situation when calling [NewRelic noticeNetworkRequestForURL]. Updated SDK to include iOS agent symbols in crash reports that may include New Relic code. Removed potential deadlock on main thread for reachability requests by moving reachability flags off the main thread. Resolves a crashing issue with Swift related to cases where class_getSuperClass() was called with the root Swift class.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-4139","eolDate":"2017-11-21"},{"agent":"ios","date":"2014-09-12","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.412.zip","version":"3.412","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Fixed minor memory leak caused by network instrumentation. Fixed a bug where network data was missing from interaction traces.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3412","eolDate":"2017-09-12"},{"agent":"ios","date":"2014-09-03","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.406.zip","version":"3.406","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Corrected edge case that caused network requests to fail in a 400 error. Corrected issue causing New Relic Cross Application Tracing to fail.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3406-0","eolDate":"2017-09-03"},{"agent":"ios","date":"2014-08-27","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.398.zip","version":"3.398","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Stability improvements: Certain application design patterns could trigger a concurrency problem in the New Relic SDK that caused app instability. This version properly handles those edge cases.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3398","eolDate":"2017-08-27"},{"agent":"ios","date":"2014-08-19","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.396.zip","version":"3.396","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Stability improvements: Certain application design patterns could trigger a concurrency problem in the New Relic SDK that caused app instability. This version properly handles those edge cases. A memory leak in NRMATraceMachine has been removed.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3396","eolDate":"2017-08-19"},{"agent":"ios","date":"2014-08-05","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.380.zip","version":"3.380","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Resolved issue that corrupted New Relic interaction trace data, and resulted in a \"ThreadLocalTrace is not parentTrace\" log message.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3380","eolDate":"2017-08-05"},{"agent":"ios","date":"2014-07-24","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.378.zip","version":"3.378","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Improvements Fixed build errors in NewRelicFeatureFlags.h that occurred if NewRelic.h was imported before foundation.h in the prefix.pch file. Interaction traces period is more discrete. An interaction will only record traces until a new interaction is started, rather than combining the data into one interaction. The method +[NRTaskQueue dequeue] will no longer fire on the UI thread. Interaction traces now have more easily identifiable names. Instead of “ViewController#Method” they will now be named “Display ViewController”. The healthy interaction timer will no longer fire repeatedly over very short intervals. The agent will no longer crash if the instrumented method:; [NSURLConnection sendAsynchronousRequest:queue:completionHandler:] is passed a nil completionHandler. Fixes Default interaction traces can now be renamed by adding @protocol NewRelicCustomInteractionInterface( (defined in NewRelic.h) to the traced view controller. Added new method for starting a custom interaction trace +startInteractionWithName: (defined in NewRelic.h) Deprecated the following methods in NewRelic.h : +startInterationFromMethodName:object:, +startInterationFromMethodName:object:customizedName, and +startInterationFromMethodName:object:cancelRunningTrace:. Use +startInteractionWithName: instead. Added method +stopCurrentInteraction: to NewRelic.h. Allows user to stop a custom interaction trace manually.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3378","eolDate":"2017-07-24"},{"agent":"ios","date":"2014-06-16","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.343.zip","version":"3.343","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Fixed [AFURLSessionManager disposition]: unrecognized selector crash. Crashes in NRURLProtocol client call backs should no longer occur. Fixed C++ compilation error caused by the New Relic Agent feature flags. Improvements Added new flag for NRFeatureFlags: NRFeatureFlag_ExperimentalNetworkingInstrumentation. This forces all network traffic to run through the NRURLProtocol, normally only traffic on UIWebViews are routed through the NRURLProtocol. It is not recommended to enable this flag.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3343","eolDate":"2017-06-16"},{"agent":"ios","date":"2014-05-16","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.324.zip","version":"3.324","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Fixed crash: BAD_ACCESS in +[NRThreadLocalStore currentThreadDictionary] Resolves a warning from Veracode SAST about an unchecked return from a malloc call","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3324","eolDate":"2017-05-16"},{"agent":"ios","date":"2014-05-05","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.311.zip","version":"3.311","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Improvements NSURLSession Instrumentation Beta The iOS agent now instruments NSURLSessions. Specifically, network requests created with NSURLSessionDataTask and NSURLSessionUploadTask. Network requests made using these objects will appear in the Mobile UI under the Network tab along with previously instrumented network requests. This feature is disabled by default. It can be enabled via the new configuration flags. Configuration Flags Allow users to enable/disable New Relic features. This feature specifically added for Beta NSURLSession support, which is, by default, disabled. Fixes Agent will no longer produces garbled server response bodies under Network > Errors > Error Traces. Agent will no longer display the error message \"threadLocalTrace is not parentTrace\" when it isn't actually an error. Agent will no longer trim the last traced method of an activity trace.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3311","eolDate":"2017-05-05"},{"agent":"ios","date":"2014-03-26","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.289.zip","version":"3.289","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Fixes a sporadic crash triggered by xpc_mach_port activity in the application after a call to read thread CPU usage fails. Also appears as a crash triggered by the SCReachability system API. Fixes an issue where certain class inheritance hierarchies may cause a grandparent class's implementation of an instrumented method to be invoked multiple times. Fixes a crash related to enabling both Verbose mode and File Output mode in the New Relic SDK.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3289","eolDate":"2017-03-26"},{"agent":"ios","date":"2014-03-11","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.257.zip","version":"3.257","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Interaction traces will properly terminate on app closing. This avoids certain edge cases where the interaction will resume on app launch and create an Interaction that spans the length of time the app was backgrounded.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3257","eolDate":"2017-03-11"},{"agent":"ios","date":"2014-03-07","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.256.zip","version":"3.256","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Improvements Created a workaround for no-network-activity bug that occurs when New Relic and Crittercism are installed simultaneously. Fixes Fixed memory leak in NRTraceMachine","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3256","eolDate":"2017-03-07"},{"agent":"ios","date":"2014-02-26","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.252.zip","version":"3.252","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release is a recommended upgrade for all iOS SDK users. Improvements Agent stability & self-management. Critical sections of the agent have been isolated to prevent agent-related errors from destabilizing the host application, and certain classes of errors will be automatically reported to New Relic without the need for customer-initiated communication. Performance tuning. Overhead for on-device code tracing has been reduced by over 50% in some cases. The agent will consume less CPU time on the mobile device, resulting in improved application responsiveness and lower battery drain. Improved data accuracy. Under certain conditions it was possible for the SDK to record total time for method invocations but not record the associated exclusive time. This improvement will result in more accurate breakdown charts and tables, and improve the collection of certain interaction traces. Fixes This release resolves multiple stability issues in the SDK. We recommend this release for any customers who have encountered application crashes with previous SDK versions.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3252","eolDate":"2017-02-26"},{"agent":"ios","date":"2014-01-31","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.196.zip","version":"3.196","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Resolves NRURLProtocol crashes for non-webView network requests. Large file uploads should no longer timeout after the default timeout period while there is network activity.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3196","eolDate":"2017-01-31"},{"agent":"ios","date":"2014-01-21","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.184.zip","version":"3.184","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Improvements ARM64 support - you can now compile New Relic in your native 64-bit applications. Improved sub-millisecond timing resolution on method tracing. Blame breakdowns and interaction traces will now have improved \"total time\" and \"total exclusive time\" measurements. Fixes Resolves a crashing timing-related issue in method tracing. Relevant exceptions include note of \"object cannot be nil\" or \"setObject:forKey:\" with a nil value. Resolves several stability and accuracy issues in the NRTimer class.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3184","eolDate":"2017-01-21"},{"agent":"ios","date":"2014-01-08","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.174.zip","version":"3.174","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Improvements Supports C++ linkage. For projects using C++, the New Relic library now properly marks our exported symbols as requiring C linkage. Fixes Corrects an issue where data might cease reporting to New Relic after app has been running for 60 seconds. Fixes an issue that could cause incorrectly sized UIImages or repeating icons.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3174","eolDate":"2017-01-08"},{"agent":"ios","date":"2013-12-16","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.154.zip","version":"3.154","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Improvements Added explanation to missing CFBundleVersion/CFBundleShortVersion String exception Fixes -setThreadLocalTrace: crash fixed UIImage -imageFromData: crash fixed other various bug fixes","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3154","eolDate":"2016-12-16"},{"agent":"ios","date":"2013-12-02","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_3.130.zip","version":"3.130","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Features End to end instrumentation for your mobile applications. Automatic instrumentation of important system objects and methods. Customizability to allow for instrumentation of your most important objects and methods.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-3130","eolDate":"2016-12-02"},{"agent":"ios","date":"2013-11-22","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_1.396.zip","version":"1.396","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Fixes occasional crashes in NRURLProtocol.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-1396","eolDate":"2016-11-22"},{"agent":"ios","date":"2013-09-17","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_1.376.zip","version":"1.376","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Bug fix release Removes an Apple app store submission false-positive warning about accessing private APIs Fixes an occasional block retain-related crash when handling UIWebView-initiated network requests on iOS 6","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-1376","eolDate":"2016-09-17"},{"agent":"ios","date":"2013-06-28","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_1.354.zip","version":"1.354","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release fixes several customer-reported performance problems when using New Relic for iOS prevents agent from adding duplicate X-NewRelic-ID headers to outgoing requests prevents agent from interfering with HTTP cacheing fixes potential crash if available heap space is exhausted","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-1354","eolDate":"2016-06-28"},{"agent":"ios","date":"2013-05-31","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_1.342.zip","version":"1.342","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Stability Release This release addresses a potential floating point exception in NRStatsEngine triggered by a race condition. ASIHttpRequest Improvement This release adds mobile-server correlation of HTTP requests when using the ASIHttpRequest library. Previously these requests would not be linked to the corresponding transaction in the application server view.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-1342","eolDate":"2016-05-31"},{"agent":"ios","date":"2013-04-22","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_1.328.zip","version":"1.328","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixes Improve performance of certain concurrent networking operations in iOS 6 Correct errors effecting certain uses of UIWebView AJAX activity Remove dependency on NSJSONSerialization when app is run on iOS 4 Prevent situation where some HTTP redirects were not reported to application","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-1328","eolDate":"2016-04-22"},{"agent":"ios","date":"2013-03-13","downloadLink":"https://download.newrelic.com/ios_agent/NewRelic_iOS_Agent_1.300.zip","version":"1.300","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Happy Pi Day! Welcome to New Relic for Mobile Apps, we're glad to have you aboard.","slug":"docs/release-notes/mobile-release-notes/ios-release-notes/ios-1300","eolDate":"2016-03-13"},{"agent":"android","date":"2014-10-22","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_4.95.0.zip","version":"4.95.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Corrects an issue where the agent may crash under certain concurrent access of instrumented InputStream implementations. Corrects an issue where a thread pool was not properly getting destroyed upon application background-to-foreground transitions.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/clone-android-4950","eolDate":"2017-10-22"},{"agent":"android","date":"2026-06-17","downloadLink":null,"version":"1.1.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fix Fix an issue to prevent ANRMonitor from blocking the main thread on its own lock Fix a crash that is happening in android ndk agent v1.1.4 Support statement The Android NDK agent version 1.1.5 and above requires Android agent 7.7.6 and higher. The Android NDK agent version 1.1.1 and above requires Android agent 7.5.1 and higher. The Android NDK agent version 1.1.0 and above requires Android agent 7.5.0 and higher. The Android NDK agent version 1.0.3 and above requires Android agent 6.11.0 and higher. Versions 1.0.0 - 1.0.2 are compatible with Android agent 6.10.0 and lower. We recommend you to upgrade the agent regularly, at least every 3 months.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-115","eolDate":"2027-06-17"},{"agent":"android","date":"2026-06-03","downloadLink":null,"version":"1.1.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Important notice This release is invalid and should not be used. Support statement The Android NDK agent version 1.1.1 and above requires Android agent 7.5.1 and higher. The Android NDK agent version 1.1.0 and above requires Android agent 7.5.0 and higher. The Android NDK agent version 1.0.3 and above requires Android agent 6.11.0 and higher. Versions 1.0.0 - 1.0.2 are compatible with Android agent 6.10.0 and lower. We recommend you to upgrade the agent regularly, at least every 3 months.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-114","eolDate":"2027-06-03"},{"agent":"android","date":"2025-07-10","downloadLink":null,"version":"1.1.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fix Added support for 16KB page size Support statement The Android NDK agent version 1.1.1 and above requires Android agent 7.5.1 and higher. The Android NDK agent version 1.1.0 and above requires Android agent 7.5.0 and higher. The Android NDK agent version 1.0.3 and above requires Android agent 6.11.0 and higher. Versions 1.0.0 - 1.0.2 are compatible with Android agent 6.10.0 and lower. We recommend you to upgrade the agent regularly, at least every 3 months.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-113","eolDate":"2026-07-10"},{"agent":"android","date":"2024-08-21","downloadLink":null,"version":"1.1.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"This release is invalid and should not be used. Support statement The Android NDK agent version 1.1.1 and above requires Android agent 7.5.1 and higher.\nThe Android NDK agent version 1.1.0 and above requires Android agent 7.5.0 and higher.\nThe Android NDK agent version 1.0.3 and above requires Android agent 6.11.0 and higher.\nVersions 1.0.0 - 1.0.2 are compatible with Android agent 6.10.0 and lower. We recommend you to upgrade the agent regularly, at least every 3 months.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-112","eolDate":"2025-08-21"},{"agent":"android","date":"2024-07-25","downloadLink":null,"version":"1.1.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fix Tighten implementation logic to better handle potential memory leakage, and add more logging for debugging visibilities. Support statement The Android NDK agent version 1.1.0 and above requires Android agent 7.5.0 and higher.\nThe Android NDK agent version 1.0.3 and above requires Android agent 6.11.0 and higher.\nVersions 1.0.0 - 1.0.2 are compatible with Android agent 6.10.0 and lower. We recommend you to upgrade the agent regularly, at least every 3 months.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-111","eolDate":"2025-07-25"},{"agent":"android","date":"2024-06-27","downloadLink":null,"version":"1.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Reduce the overall size of the agent. Extend AgentNDK.Builder.withANRMonitor(boolean) to disable native ANR detection as well. Support statement The Android NDK agent version 1.1.0 and above requires Android agent 7.5.0 and higher.\nThe Android NDK agent version 1.0.3 and above requires Android agent 6.11.0 and higher.\nVersions 1.0.0 - 1.0.2 are compatible with Android agent 6.10.0 and lower. We recommend you to upgrade the agent regularly, at least every 3 months.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-110","eolDate":"2025-06-27"},{"agent":"android","date":"2023-10-19","downloadLink":null,"version":"1.0.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed Fixed a memory leak when ANRMonitor is enabled. Support statement The Android NDK agent version 1.0.3 and above requires Android agent 6.11.0 and higher. Versions 1.0.0 - 1.0.2 are compatible with Android agent 6.10.0 and lower. We recommend you to upgrade the agent regularly, at least every 3 months.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-104","eolDate":"2024-10-19"},{"agent":"android","date":"2023-07-19","downloadLink":null,"version":"1.0.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed Fixed java.lang.NoSuchMethodError when using the NDK agent and Android agent version 6.11.0 and higher. Support statement The Android NDK agent version 1.0.3 requires Android agent 6.11.0 and higher. Versions 1.0.0 - 1.0.2 are compatible with Android agent 6.10.0 and lower. We recommend you to upgrade the agent regularly, at least every 3 months.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-103","eolDate":"2024-07-19"},{"agent":"android","date":"2023-05-04","downloadLink":null,"version":"1.0.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed Updated Kotlin library to a version that addressed a vulnerability. Support statement We recommend you to upgrade the agent regularly, at least every 3 months.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-102","eolDate":"2024-05-04"},{"agent":"android","date":"2023-04-10","downloadLink":null,"version":"1.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed Addressed a memory leak resulting from ANR detection Support statement We recommend you to upgrade the agent regularly, at least every 3 months.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-ndk-101","eolDate":"2024-04-10"},{"agent":"android","date":"2026-08-24","downloadLink":null,"version":"7.8.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed correct regional/default source map API host for React Native Source Map Upload Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-782","eolDate":"2027-08-24"},{"agent":"android","date":"2026-08-18","downloadLink":null,"version":"7.8.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed the endpoint URL for uploading React Native source map. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-781","eolDate":"2027-08-18"},{"agent":"android","date":"2026-08-05","downloadLink":null,"version":"7.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features and improvements Added offline storage for Session Replay: replay payloads that can't be sent immediately — due to no network connection, app force-close, process exit, or a low-memory kill — are now persisted\nto disk and delivered on the next successful harvest, instead of being lost. Added underlying support for hybrid error reporting from React Native apps, to be enabled alongside an upcoming React Native agent release. Unhandled JavaScript errors will be captured as agent\nevents, correlated with Session Replay and tagged with the app version for accurate symbolication. Added underlying support for automatic upload of React Native JavaScript source maps during the Gradle build, to be enabled alongside an upcoming React Native agent release. Added per-build-target ProGuard/DexGuard mapping file upload, so apps with multiple DexGuard packaging targets get correctly matched crash deobfuscation for each target. Added a session-scoped attribute store so Application Exit Info (AEI) events carry the session attributes of the session that actually crashed, rather than the session created after relaunch. Event persistence is now enabled by default, so buffered events and analytics data survive app termination and are recovered on the next launch. Added support for Android Gradle Plugin (AGP) 9.x, raising the supported ceiling to 9.3.0. Bug fixes Fixed cold start timing to measure time to initial display (TTID) from launch to the first rendered frame, instead of from Activity resume. Fixed a crash-recovery issue where a stale backup file could prevent the crash store from recovering after a previous crash. Fixed handled exceptions to be persisted off the calling thread, preventing potential slowdowns when the exception store is written to. Fixed Gradle build-cache invalidation caused by embedding per-build build ID and metrics values directly in compiled source — these are now generated as Android resources instead, reducing unnecessary recompiles and rebuild time, with the resources protected from being stripped when shrinkResources is enabled. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-780","eolDate":"2027-08-05"},{"agent":"android","date":"2026-07-01","downloadLink":null,"version":"7.7.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed a performance issue where Session Replay image compression ran on the main thread. It now runs asynchronously, reducing overhead during capture. Addressed rendering accuracy issues in Session Replay by emitting incremental view additions in their natural view order. Fixed an issue where stale offline payloads could be sent by enforcing a time-to-live (TTL) that discards data queued too long. Resolved an issue where session attributes could be lost during the shutdown harvest. Fixed an issue where buffered events were dropped during app shutdown, ensuring they are now sent in the final harvest to prevent data loss. Fixed a timing issue during device rotation where session continuity could be lost during the transition. Made HTTP header handling thread-safe, resolving errors that could occur under concurrent access. Fixed an issue where app start-up metrics could be miscalculated when a start-up timestamp was not set. Resolved an issue where the agent attempts to report crashes without an active network connection, causing unnecessary errors on offline devices. Fixed a native (NDK) crash that could occur during shutdown due to an ABI mismatch in stop(). Fixed ProGuard map upload for builds that produce a DexGuard APK directly. Improved Gradle configuration-cache compatibility during map upload. Relocated the bundled commons-io dependency in the Gradle plugin to prevent conflicts with host applications. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-777","eolDate":"2027-07-01"},{"agent":"android","date":"2026-06-03","downloadLink":null,"version":"7.7.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fix a crash in newrelicTransformClasses with a java.lang.IllegalAccessError after upgrading to AGP 9.1.0 Fix a NullPointerException thrown from session replay textview section Fix an issue with onTrimMemory() call in hybrid application Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-776","eolDate":"2027-06-03"},{"agent":"android","date":"2026-05-21","downloadLink":null,"version":"7.7.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fix an issue when initializing userId on first launch Fix an issue in mobile session replay to capture z-index for React Native views Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-775","eolDate":"2027-05-21"},{"agent":"android","date":"2026-05-07","downloadLink":null,"version":"7.7.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed an OutOfMemory issue caused by payload data accumulating in SharedPreferences. Cached payloads are now persisted to disk and capped to prevent unbounded growth on devices with poor connectivity. Resolved an ANR caused by repeated Binder IPC calls to ConnectivityManager on every reachability check. Network state is now tracked asynchronously via a registered network callback. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-774","eolDate":"2027-05-07"},{"agent":"android","date":"2026-04-27","downloadLink":null,"version":"7.7.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Announcements Session Replay for Android has moved from preview to general availability. Gain full visibility into your users' mobile experience with faithful visual reproductions of their sessions. Learn more about\nSession Replay. New features Added the ability to programmatically block specific views from being captured during Session Replay, giving fine-grained control over what is recorded beyond the default masking rules. The agent now automatically creates a new session after 4 hours of continuous use, improving long-running session tracking. Log forwarding now coordinates its sampling decisions with Session Replay, ensuring logs are captured for sessions that are being replayed. Bug fixes Resolved an issue where the agent attempted to forward logs without an active network connection, causing unnecessary errors on offline devices. Fixed a RuntimeException that could occur when reading or closing streams from HttpsURLConnection. Addressed a null pointer exception that could occur during session handling. Fixed a timing issue where session rotation could occur before the harvest cycle completed, potentially causing data loss during the transition. Resolved an issue where the session ID could be null during session rotation, causing data to be attributed incorrectly. Addressed several rendering accuracy issues in Session Replay captures. Fixed an issue where local masking configuration was not correctly applied to text elements during Session Replay capture. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-773","eolDate":"2027-04-27"},{"agent":"android","date":"2026-04-23","downloadLink":null,"version":"7.7.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A bug in this release causes all Session Replay text to appear masked as asterisks, regardless of the masking settings configured in the New Relic dashboard. Upgrade to v7.7.3 to resolve this issue. Announcements Session Replay for Android has moved from preview to general availability. Gain full visibility into your users' mobile experience with faithful visual reproductions of their sessions. Learn more about\nSession Replay. New features Added the ability to programmatically block specific views from being captured during Session Replay, giving fine-grained control over what is recorded beyond the default masking rules. The agent now automatically creates a new session after 4 hours of continuous use, improving long-running session tracking. Log forwarding now coordinates its sampling decisions with Session Replay, ensuring logs are captured for sessions that are being replayed. Bug fixes Resolved an issue where the agent attempted to forward logs without an active network connection, causing unnecessary errors on offline devices. Fixed a RuntimeException that could occur when reading or closing streams from HttpsURLConnection. Addressed a null pointer exception that could occur during session handling. Fixed a timing issue where session rotation could occur before the harvest cycle completed, potentially causing data loss during the transition. Resolved an issue where the session ID could be null during session rotation, causing data to be attributed incorrectly. Addressed several rendering accuracy issues in Session Replay captures. Fixed an issue where local masking configuration was not correctly applied to text elements during Session Replay capture. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-772","eolDate":"2027-04-23"},{"agent":"android","date":"2026-03-17","downloadLink":null,"version":"7.7.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Use SecureRandom() for generating unique identifies Fix potential ANR on the main thread when using heavy load sampling Add exception handling for lower SDK version Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-771","eolDate":"2027-03-17"},{"agent":"android","date":"2026-02-13","downloadLink":null,"version":"7.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Add support for AGP 9 Add error sampling for mobile session replay Add pauseReplay and recordReplay APIs Fixes Multiple mobile session replay fixes for better performance Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-770","eolDate":"2027-02-13"},{"agent":"android","date":"2025-09-15","downloadLink":null,"version":"7.6.9","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes Resolved a memory leak issue where trace listeners were not being removed properly after the app switched between foreground and background multiple times. Fixed the issue with thread synchronization that occasionally resulted in data not being reported to New Relic. Addressed issues related to log reporting during ANRs to improve stability and performance. Corrected duplicate class issues related to the Curtains Library to ensure compatibility and prevent conflicts. Resolved a null pointer exception issue in the setUserId method to enhance robustness. Fixed issues with the Retrofit Interceptor where URLs were not reported correctly if the request failed due to network errors on the device. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-769","eolDate":"2026-09-15"},{"agent":"android","date":"2025-07-29","downloadLink":null,"version":"7.6.8","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes Fixed an issue where stack traces for Unity errors were not displayed correctly. Fixed an issue that prevented summary metrics from being recorded when the app returned to the foreground after its initial launch. Fixed an issue where invalid JSON in log entries could cause errors. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-768","eolDate":"2026-07-29"},{"agent":"android","date":"2025-06-18","downloadLink":null,"version":"7.6.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes Improved performance to resolve ANRs when reporting logs Fixed an issue to continue reporting logs upon termination of the application Resolved an issue with application state monitoring and data transmission Improved few violations when turning on strictmode Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-767","eolDate":"2026-06-18"},{"agent":"android","date":"2025-04-14","downloadLink":null,"version":"7.6.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes Addressed an issue with custom interaction conflicts with default interaction Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-766","eolDate":"2026-04-14"},{"agent":"android","date":"2025-03-26","downloadLink":null,"version":"7.6.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes Addressed a problem where the agent failed to parse double values with non-zero digits after the decimal point. Corrected an issue where the agent recorded app launch metrics as astronomical values. Fixed build issues related to newer versions of Dexguard. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-765","eolDate":"2026-03-26"},{"agent":"android","date":"2025-02-21","downloadLink":null,"version":"7.6.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Upgrade agent to support AGP 8.8 Added processId as a session attribute for application exit info to ensure better troubleshooting ability Bug Fixes Resolved an issue that logs are not sent after first app launch Resolved the issue where HttpHeaders were not being tracked when added through an interceptor. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-764","eolDate":"2026-02-21"},{"agent":"android","date":"2025-01-24","downloadLink":null,"version":"7.6.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Introduced build-time feature flag for LogInstrumentation. Enhanced logging by including Session Attributes as Log Attributes. Bug Fixes Resolved missed session events in the background reporting feature. Fixed memory leak related to mobile handled exceptions during network unavailability. Corrected application crash scenario during agent shutdown. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-763","eolDate":"2026-01-24"},{"agent":"android","date":"2024-12-06","downloadLink":null,"version":"7.6.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Implemented OpenTelemetry (Otel) Distributed Tracing. Added support for Gzip compression for log data ingestion. Included Application Not Responding (ANR) thread data in the reporting process. Fixed issues Fixed an issue with log instrumentation that caused build failures. Fixed an issue where throwable errors generated repetitive entries in Logcat. Fixed a crash caused by calling removeAttributes before starting an agent. Fixed user-reported issues with log functionality. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-762","eolDate":"2025-12-06"},{"agent":"android","date":"2026-01-20","downloadLink":null,"version":"7.6.15","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Changed the default interval for sending event data from 10 minutes to 1 minute. Fixed an issue where mapping files aren't sent in DexGuard 9 with different flavor configurations. Fixed multiple crashes related to mobile session replay. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-7615","eolDate":"2027-01-20"},{"agent":"android","date":"2025-12-04","downloadLink":null,"version":"7.6.14","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fix an issue that artifacts are missing for monoEnabled build Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-7614","eolDate":"2026-12-04"},{"agent":"android","date":"2025-11-14","downloadLink":null,"version":"7.6.13","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fix ANR cased by setUserId Fix ANR caused by blocking SecureRandom initialization during agent configuration Improve content length detection and limit reponsebody capture in okhttp3 Fix few bugs in webview instrumentation Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-7613","eolDate":"2026-11-14"},{"agent":"android","date":"2025-11-04","downloadLink":null,"version":"7.6.12","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Added session replay functionality for Jetpack Compose. Official session replay public preview version. Fixes Fixed multiple session replay bugs. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-7612","eolDate":"2026-11-04"},{"agent":"android","date":"2025-10-30","downloadLink":null,"version":"7.6.11","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed a NullPointerException issue in memory sampling process. Added safe casting during the initialization of app launch times to prevent ClassCastException compatibility in Microsoft Intune MAM SDK. Improved okhttp callback protection to prevent agent crashes from user code exceptions. Fixed duplicated crashes from native crash reports. Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-7611","eolDate":"2026-10-30"},{"agent":"android","date":"2025-10-10","downloadLink":null,"version":"7.6.10","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Added Gradle 9 Support Support statement We recommend updating the agent at least every three months. Find specific policies and dates for Android agent support in the Mobile Monitoring Agents EOL Policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-7610","eolDate":"2026-10-10"},{"agent":"android","date":"2024-10-17","downloadLink":null,"version":"7.6.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Adds support for the Android Gradle Plugin 8.7. Fixed issues Resolved an issue where ProGuard/DexGuard mapping files weren't being properly uploaded to New Relic, improving crash reporting accuracy. Fixed a crash that occurred when Kotlin mutable maps were passed to breadcrumbs and custom events. Corrected behavior where default interactions were being recorded even when the feature flag was disabled. Support statement We recommend updating the agent at least every 3 months. The specific policies and dates for Android agent support of the can be found in the Mobile monitoring agents EOL policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-761","eolDate":"2025-10-17"},{"agent":"android","date":"2024-09-10","downloadLink":null,"version":"7.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Upgrade JDK support to JAVA22. Upgrade AGP support to 8.6. Add feature flag for event persistence. You can read our docs  to learn how to enable this feature]. Fixed issues Fixed a corner case to prevent a mismatch between appbuildid and appversion. Fixed issue where crashes aren't ingested due to empty stacktraceElements. Fixed a NullValuePointer exception when a shutdown is called. Fixed a parameter mismatch in the gradle plugin which caused confusion in the logs. Support statement We recommend updating the agent at least every 3 months. The specific policies and dates for Android agent support of the can be found in the Mobile monitoring agents EOL policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-760","eolDate":"2025-09-10"},{"agent":"android","date":"2024-08-01","downloadLink":null,"version":"7.5.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fix Tighten the logic around metric clearance to prevent dropping metrics when harvest is unsuccessful Add sessionId attribute as part of the log reporting Support statement We recommend updating the agent at least every 3 months. The specific policies and dates for Android agent support of the can be found in the Mobile monitoring agents EOL policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-751","eolDate":"2025-08-01"},{"agent":"android","date":"2024-06-28","downloadLink":null,"version":"7.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Add mobile log reporting feature. You can read our docs to learn more and how to enable this feature . Support statement We recommend updating the agent at least every 3 months. The specific policies and dates for Android agent support of the can be found in the Mobile monitoring agents EOL policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-750","eolDate":"2025-06-28"},{"agent":"android","date":"2024-06-24","downloadLink":null,"version":"7.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Add ApplicationExitInfo as part of data reporting, and the feature is enabled by default. To disable go to your mobile applications entity application settings page. Support statement We recommend updating the agent at least every 3 months. The specific policies and dates for Android agent support of the can be found in the Mobile monitoring agents EOL policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-741","eolDate":"2025-06-24"},{"agent":"android","date":"2024-06-20","downloadLink":null,"version":"7.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Add ApplicationExitInfo as part of data reporting. Add the ability to report data while an application goes into a background state. You can read our docs to learn how to enable this feature . Includes code for upcoming log forwarding feature. See your Account Team for information about early adoption. Fix Enhance setUserId() function to add the ability to update userID attribute multiple times in a short period without losing the history of different end users. You can read our docs to learn about this fix . Enhance the accuracy of device time calculation when it is changed by the mobile network. Resolve an ANR issue when the application reports events. Resolve an issue when exceptionMessage of a MobileHandledException doesn't display in query results. Support statement We recommend updating the agent at least every 3 months. The specific policies and dates for Android agent support of the can be found in the Mobile monitoring agents EOL policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-740","eolDate":"2025-06-20"},{"agent":"android","date":"2024-04-25","downloadLink":null,"version":"7.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fix Resolve a SHA-signed error during build time by disabling JAR signing verification. Resolve reported ANRs during event persistance serialization. Enhance symbol upload process to improve request error rate and support a pending new upload endpoint. Support statement We recommend you to upgrade the agent at least every 3 months. The specific policies and dates for Android agent support of the can be found in the Mobile monitoring agents EOL policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-731","eolDate":"2025-04-25"},{"agent":"android","date":"2024-03-04","downloadLink":null,"version":"7.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Added the ability to persist events when application is force killed. Added the ability to store harvest data that previously would be lost if the application doesn't have internet connection. These harvest are then sent after an internet connection is established and the next harvest successfully uploads. This feature is disabled by default, see more details here  to enable it. Added setMaxOfflineStorageSize  API to set the maximum amount of data that can be stored locally. Added support for Unreal platform. Added support for Android dynamic features. Fix Fixed an issue that target activity is not captured when calculating app launch time from the start to a target activity rather than the default main activity. Support statement We recommend you to upgrade the agent at least every 3 months. The specific policies and dates for Android agent support of the can be found in the Mobile monitoring agents EOL policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-730","eolDate":"2025-03-04"},{"agent":"android","date":"2024-02-05","downloadLink":null,"version":"7.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fix Upgrade the support version of AGP to 8.4 Support statement We recommend you to upgrade the agent at least every 3 months. The specific policies and dates for Android agent support of the can be found in the Mobile monitoring agents EOL policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-721","eolDate":"2025-02-05"},{"agent":"android","date":"2023-11-15","downloadLink":null,"version":"7.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Adds configurable request header instrumentation to network events The agent will now produce network event attributes for select header values if the headers are detected on the request. The header names to instrument are passed into the agent when started. For more information, see Adding Tracked Headers  in the Mobile Monitoring documentation. Adds GraphQL attributes to network events If the agent detects request headers from Apollo GraphQL servers, it will add additional attributes to the network request event. For more information, see Adding Tracked Headers  in the Mobile Monitoring documentation. Exclude instrumentation by package name The agent plugin can now be configured to exclude classes from a specific package space during instrumentation. These classes will be unmodified. This feature can be useful when encountering sensitive or problematic class data. For more information, see Configure the New Relic Gradle plugin . Fixed Exclude signed jars from instrumentation Support statement We recommend you to upgrade the agent at least every 3 months. The specific policies and dates for Android agent support of the can be found in the Mobile monitoring agents EOL policy .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-720","eolDate":"2024-11-15"},{"agent":"android","date":"2023-09-25","downloadLink":null,"version":"7.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Adds support for DexGuard 9+ with Gradle 8/AGP 8 Adds unity support with custom exceptions Adds map parameters for both custom and auto HTTP instrumentation to ensure data accuracy Decouple map tagging with uploads in plugin to improve the build pipeline by making the tagged map a cachable build artifact Fixed Fix NoClassDefFoundError when using agent v7.0.0 due to uninstrumented signed libraries Fix an issue that excludeVariantInstrumention is not accepting camel case variant names Support statement We recommend you to upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is 6.3.0 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-710","eolDate":"2024-09-25"},{"agent":"android","date":"2023-07-10","downloadLink":null,"version":"7.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Welcome to the New Relic Android agent version 7.0. This major release breaks compatibility with versions of Gradle 6.x Android Gradle Plugin (AGP) 4.x Android agent 7.x is increasing the minimum Gradle version to 7.2. Customers will be required to upgrade to Android Gradle Plugin (AGP) 7.0.0 and higher. New Adds support for Gradle 8.0 and higher Adds support for the Android Gradle Plugin 8.0 and higher Adds support for Gradle configuration caching Adds support for JDK 17 when used with Gradle 8 Support statement We recommend you to upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is 6.1.0 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-700","eolDate":"2024-07-10"},{"agent":"android","date":"2023-01-11","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.9.2.zip","version":"6.9.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed Fixed an issue of missing element in harvest payload, which has caused data loss during ingest in version 6.9.1 Tightened metric data validations to prevent data loss during ingest Fixed a bug that allowed direct access to the agent plugin extension's configuration from Kotlin that could result in a failure to tag and upload obfuscation maps. Support statement We recommend you to upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is 6.0.0 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-692","eolDate":"2024-01-11"},{"agent":"android","date":"2022-12-06","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.9.1.zip","version":"6.9.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed Fixed a distributed tracing issue for httpURLConnection in Cordova/Ionic apps. Support statement We recommend you to upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is 5.28.1 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-691","eolDate":"2023-12-06"},{"agent":"android","date":"2022-09-26","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.9.0.zip","version":"6.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Add support for reporting app launch time, including cold time and hot time. Cold start time refers to an app’s starting from scratch. This means that the app’s process has not been created by the system until then. Hot start time refers to when your app’s process is already running in the background. Fixed in this release Fixed an instrumentation race condition when build is run with multiple Gradle workers (--max-workers > 2) Fixed a crash when trying to report exceptions with missing stacktraces through supportability metrics. Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.27.0 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-690","eolDate":"2023-09-26"},{"agent":"android","date":"2022-07-27","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.8.0.zip","version":"6.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Add support for handling JavaScript errors from React Native apps Add a new session attribute RootedDevice when native reporting is enabled to signify whether the hosting device is rooted Fixed in this release Fixed an issue to address the format of distributed tracing header Fixed an issue in plugin to address a corner-case exception thrown during map processing Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.26.0 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-680","eolDate":"2024-07-27"},{"agent":"android","date":"2022-07-06","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.7.0.zip","version":"6.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Add support for native crash reporting  in legacy agent crash reporting. Add distributed tracing context support to New Relic SDK Fixed in this release Fixed issue that kept the app's supportability metrics from being reported to New Relic Updated the agent to address Gradle deprecation warnings Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.26.0 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-670","eolDate":"2024-07-06"},{"agent":"android","date":"2022-06-02","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.6.0.zip","version":"6.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Add support for DexGuard 9 End of life for supporting android SDK 21 (Android 5) to 23 (Android 6) Fixed in this release Fix a bug to capture response body using noticeHttpTransaction method Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.26.0 . Please note, support for Android SDK 21-23 has been removed in this release.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-660","eolDate":"2024-06-02"},{"agent":"android","date":"2022-03-09","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.5.0.zip","version":"6.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Add support for passing Throwable types to NewRelic.recordHandledException() Fixed in this release Resolved a sampler thread leak that occurred in long-lived apps. Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.24.0 . Please note, support for Android SDK 21-23 will be removed in a future release.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-650","eolDate":"2024-03-09"},{"agent":"android","date":"2022-01-25","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.4.1.zip","version":"6.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Resolved an error when transforming some libraries during build time.\nDetailed message: [ClassTransformer] transformArchive: java.util.zip.ZipException: duplicate entry: META-INF/MANIFEST.MF Resolved a 'java.lang.NoClassDefFoundError' crash during runtime. Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.24.0 . Please note, support for Android SDK 21-23 will be removed in a future release.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-641","eolDate":"2024-01-25"},{"agent":"android","date":"2022-01-12","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.4.0.zip","version":"6.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Resolved D8/R8 warning messages: Expected stack map table for method with non-linear control flow. Fixed crash caused by NoSuchMethodError that occurred on Android 5 and 6. Reverted the fix for missing Retrofit2/OkHttp3 bytesReceived and error response body results to prevent memory leaking. Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.24.0 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-640","eolDate":"2024-01-12"},{"agent":"android","date":"2021-10-18","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.3.1.zip","version":"6.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Deprecated SDK location support, and removed geolocation listener from agent. Fixed in this release Resolved missing Retrofit2/OkHttp3 'bytesReceived' and error response body results Fixed single/orphan Distributed Tracing spans resulting from malformed trace parent HTTP header Resolved missing OkHttp3 response bodies that made the agent incompatible with Mapquest Resolved Gradle 7 execution optimization warnings due to the agent plugin's failure to declare an explicit or implicit dependency. Removed erroneous Kotlin UnknownTaskException log warning Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.23.0 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-631","eolDate":"2023-10-18"},{"agent":"android","date":"2021-10-08","downloadLink":null,"version":"6.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"This release is invalid and should not be used. Please use Android agent version 6.3.1 . Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.23.0 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-630","eolDate":"2023-10-08"},{"agent":"android","date":"2021-08-24","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.2.1.zip","version":"6.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Update ASM API level for all classes to fix a build error indicating: java.lang.UnsupportedOperationException: This feature requires ASM7 when running on JDK 11 and Gradle 7+ Emit log messages to warning while processing some unsupported classes due to an incompatibility with our bytecode injection library, further investigation needed Add exception handling to address NoSuchMethodError runtime crash on certain Android devices Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.23.0 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-621","eolDate":"2023-08-24"},{"agent":"android","date":"2021-08-01","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.2.0.zip","version":"6.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Add suppport for Android Gradle plugin (AGP) version 7.0 Update instrumentation support level to JDK 11 Fixed in this release Replace Map.putIfAsent() method reference that caused runtime crashes when using compileSDK < 24 Remove any remaining location listener when app goes to background Fix OkHttp interceptor failure when updating the URL of Retrofit POST requests Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.23.0 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-620","eolDate":"2023-08-01"},{"agent":"android","date":"2023-05-16","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.11.1.zip","version":"6.11.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed Fix an issue where the app crashes when it goes to background after agent shutdown Support statement We recommend you to upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is 6.1.0 . Please note, the Android agent will be increasing the minimum Gradle versions in agent release 6.12.0. Customers will be required to upgrade to Android Gradle Plugin 7.0 or higher.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-6111","eolDate":"2024-05-16"},{"agent":"android","date":"2023-05-10","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.11.0.zip","version":"6.11.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Add FedRAMP support Fixed Fix an issue of NR_BUILD_ID not appending with default release variant Tighten the exception handling of TraceMachine to prevent NullPointerException Support statement We recommend you to upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is 6.1.0 . Please note, the Android agent will be increasing the minimum Gradle versions in agent release 6.12.0. Customers will be required to upgrade to Android Gradle Plugin 7.2 or higher.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-6110","eolDate":"2024-05-10"},{"agent":"android","date":"2023-03-09","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.10.0.zip","version":"6.10.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Add a new feature to provide the ability to disable agent at runtime Fixed Fix an issue of failing to report network failure Tighten the exception handling of HarvestTimer.tickNow() to prevent NullPointerException Support statement We recommend you to upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is 6.0.0 . Please note, the Android agent will be increasing the minimum Gradle versions in agent release 6.12.0. Customers will be required to upgrade to Android Gradle Plugin 7.2 or higher.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-6100","eolDate":"2024-03-09"},{"agent":"android","date":"2021-06-29","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.1.0.zip","version":"6.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"We have noticed that this version has issues running on devices with API levels below 24. This will be fixed in the upcoming release. In the meantime we suggest you revert to version 6.0.0 (or upgrade compileSDK to 24). New in this release In consideration of customers still dependent on Android 5.0, we've reverted the minimum supported SDK level (minSdkVersion) from 24 to 21. Fixed in this release Agent version 6.0.0 introduced changes to the way the agent processes crashes at runtime. Deferred crash reporting  is now the default crash reporting behavior, in which case crash reports are recorded when they occur, but not uploaded until the next application launch. This agent release: fixes a race condition with deferred crash reporting that resulted in dropped crashes. corrects the inadvertently deprectated NewRelic.withCrashReportingEnabled(boolean) API method. Resolve D8 crash caused by incomplete instrumentation of AsyncTask implementations. Correct misleading logging messages generated when Http/HttpsUrlConnections are are instrumented for Distributed Tracing. Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.23.0 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-610","eolDate":"2023-06-29"},{"agent":"android","date":"2021-03-17","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_6.0.0.zip","version":"6.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Welcome to the New Relic Android agent version 6.0. This major release breaks compatibility with older 2.x and early 3.x versions of the Android Gradle Plugin (AGP). New in this release Adds Distributed Tracing support The agent will now add Distributed Tracing headers to instrumented network requests. This feature is enabled by default, but can be disabled through the DistributedTracing feature flag. Refer to How New Relic distributed tracing works  for more information on Distributed Tracing in mobile apps. Exclude variants from instrumentation Variant builds can now be selectively excluded from instrumentation during builds.\nBuild types or product flavors are excluded through the New Relic Gradle plugin extension : Updated requirements The minimum supported SDK level (minSdkVersion) is now 24 (Android 7.0)\nThe minimum supported Android Gradle plugin version is now 3.4 using Gradle 5.1.1 or higher. Fixed in this release Bluetooth and ethernet connections are now correctly identified. Fix build crash involving manifestPlaceholder replacement when used with AGP 4.1. Remove unused compile dependency on the support-v4 Android support library . Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.22.1 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-600","eolDate":"2023-03-17"},{"agent":"android","date":"2016-12-06","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.9.0.zip","version":"5.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New In This Release Starting with this version of the SDK, you can set a custom user identifier value that can be used to associate user sessions with analytics events and attributes. Check out the NewRelic.setUserId  method for more information.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-590","eolDate":"2019-12-06"},{"agent":"android","date":"2016-10-18","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.8.4.zip","version":"5.8.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed content length tracking and reporting failure for Retrofit ResponseBody contents.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-584-0","eolDate":"2019-10-18"},{"agent":"android","date":"2016-10-03","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.8.3.zip","version":"5.8.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Update for OkHttp3 instrumentation This release updates OkHttp3 instrumentation. OkHttp3 instrumentation is the automatic instrumentation for apps using the OkHttp version 3 HTTP client library for synchronous and asynchronous network requests. OkUrlFactory is also now supported when used with OkHttp3 client. Fixes Fixed the class cast exception crash when using OkHttp3 web sockets.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-583","eolDate":"2019-10-03"},{"agent":"android","date":"2016-09-29","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.8.2.zip","version":"5.8.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Addressed a potential crash that could occur when using OkHttp3 with both interceptors and caching.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-581","eolDate":"2019-09-29"},{"agent":"android","date":"2016-09-26","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.8.0.zip","version":"5.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Add support for OkHttp3 instrumentation This release adds automatic instrumentation for apps using the OkHttp version 3 HTTP client library for synchronous and asynchronous network requests. OkUrlFactory is also now supported when used with OkHttp3 client. Fixes Improved interaction reporting The app's main activity, not Android SDK subclasses, is now reported as the default interaction. Fixed NPE when reading from instrumented InputStream instances. Fixed unhandled MeasurementException crash in when renaming interactions. Added session attributes missing from crash reports.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-580","eolDate":"2019-09-26"},{"agent":"android","date":"2016-09-02","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.7.1.zip","version":"5.7.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed a hang due to a sampling race condition that occurred when an app's crash was uploaded to New Relic.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-571","eolDate":"2019-09-02"},{"agent":"android","date":"2016-08-04","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.7.0.zip","version":"5.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release We are pleased to announce support for Dexguard. Full build time compatibility with Dexguard version 7.2.04 or higher Full instrumentation support De-obfuscated crash report stack traces Fixes The New Relic Gradle plugin depends on the Android application or library plugin having been installed first. The New Relic plugin now throws a Gradle runtime exception, which includes instructions on how to fix the problem, if it is applied before Android. Interaction trace completion was blocked on the sampling tasks running during the interaction. Any running sample tasks are stopped immediately when the interaction trace completes. Changes The Android agent now requires  Proguard version 5.0 or higher for Proguard support","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-570","eolDate":"2019-08-04"},{"agent":"android","date":"2016-05-31","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.6.1.zip","version":"5.6.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes crashes when initializing JsonObject instances with null values. The class constructor now throws a JSONException if the passed JSON string argument is null. Fixes crashes that resulted from attempting to determine the root cause of an unhandled exception. Fixes very rare crashes when OkHttp2 returns a null Response object following a network request.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-561","eolDate":"2019-05-31"},{"agent":"android","date":"2016-05-04","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.6.0.zip","version":"5.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Improved OkHttp2 error reporting A set of OkHttp2 request exceptions, previously listed as Unknown  errors, have been adapted to reportable error types. Reduce upload attempts for cached crash reports Crash reports that are collected, but cannot be immediately uploaded, are saved locally. Saved crashes are uploaded to the crash collectors as part of agent initialization, and if the upload was successful, the local copy is removed. Otherwise, the upload is tried again the next time the app is launched, and this would go on until the upload was successful. To limit accumulation, and reduce old or duplicated crash reports, the agent now limits retries to three attempts. Fixes Fixes crash when initializing JsonArray instances with null values. Throws JSONException if the passed JSON string argument is null. Fixes certain crashes resulting from NoClassDefFoundError exceptions thrown by multi-dexed apps compiled for Dalvik on platforms prior to Lollipop (Android 5.0, API level 21).","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-560","eolDate":"2019-05-04"},{"agent":"android","date":"2016-03-08","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.5.0.zip","version":"5.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements This release adds a new feature flag, DefaultInteractions , that controls whether automatically instrumented (default) interactions are collected by the agent. With auto-instrumented interactions disabled, only custom interactions (interactions created through the public New Relic agent API) will be recorded. This flag is enabled  by default, and is disabled by calling NewRelic.disableFeature(FeatureFlag.DefaultInteractions); Fixes Fixes a problem reading a response body in asynchronous network requests via OkHttp, which was introduced by version 5.4.1.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-550","eolDate":"2019-03-08"},{"agent":"android","date":"2016-02-10","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.4.1.zip","version":"5.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Prevent duplication of the New Relic HTTP header used for cross application tracing ('X-NewRelic-Id') if the request is replayed through OkHttp The agent will now send the HTTP header 'X-NewRelic-Id' (used for cross application tracing) using exactly that casing (it was previously lowercased) Failed OkHttp requests will now correctly report the full error response body Changes This release will be the last to support the New Relic Eclipse plugin for Eclipse IDE's. Eclipse users are encouraged to use the Eclipse Gradle plugin  or migrate to Android Studio . Eclipse users may continue to use this (5.4.1) or any previous agent release.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-541","eolDate":"2019-02-10"},{"agent":"android","date":"2016-01-07","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.4.0.zip","version":"5.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Interaction tracing can now be globally disabled with the new API method , NewRelic.withInteractionTracing(boolean). This method should be called prior to starting the agent, but it can be changed any time thereafter. Interaction tracing will be disabled after the agent has started; interactions for any activity or methods executed prior to starting the agent may still appear in the Interactions page. Fixes A bug introduced in the previous release that resulted in missing analytics data in crash reports has been fixed. The session ID is now correctly updated when the app returns to foreground. Unique session counts were not affected. Additional safeguards were added to prevent agent from starting or harvesting when app is in the background.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-540","eolDate":"2019-01-07"},{"agent":"android","date":"2015-11-24","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.3.3.zip","version":"5.3.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements This release adds two new Insights attributes for the upcoming Mobile Version Trends Report: install, and upgradeFrom. This allows tracking when a session includes a new install or a new upgrade. The install attribute records true if the app was a new installation. The upgradeFrom attribute tracks the last version of the application when an upgrade is detected. Fixes Patched a GSON vulnerability that could result in null pointer exception in Json serialization during harvest.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-533","eolDate":"2018-11-24"},{"agent":"android","date":"2015-10-29","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.3.2.zip","version":"5.3.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Android Gradle plugin 1.4 compatibility (1.4.0-beta6) Google is working to improve the build system within Android Developer Toolkit (ADT) and as of version 1.4.0-beta2 a change was made that breaks compatibility with the New Relic Android agent. This update provides compatibility with the new beta and previous versions of the Android Gradle plugin. Fixes With Strict Mode enabled in Android Studio, there may have been a resource leak detected with the Android agent installed. This has been corrected for Strict Mode compatibility and to prevent potential resource leaks. An edge case scenario was detected where an app left open past the scheduled timeout value would continue sending data on the standard harvest cycle rather than the timeout value. This was corrected to ensure the timeout count is reset and respected. A small number of network error types in the Android agent were found to be reporting invalid codes that resulted in missing exceptions on the Errors page for the app. This behavior was corrected and each type of exception is now properly displayed in the Errors screen. In version 1.3 of the Gradle plugin, Google made a change that requires the mapping.txt file to be in a specific format when creating multi-dexed apps. This release accounts for that and ensures building with the Android agent is supports multi-dex.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-532","eolDate":"2018-10-29"},{"agent":"android","date":"2015-10-12","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.3.1.zip","version":"5.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Retrofit compatibility - this release of the Android SDK adds support for the current beta version of the Retrofit library (2.0.0-beta2) and addresses a crash that may have occurred previously when making an HTTP request with this beta version.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-531","eolDate":"2018-10-12"},{"agent":"android","date":"2015-09-03","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.3.0.zip","version":"5.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements This release adds a new API method withApplicationBuild(String build) which replaces the now deprecated method, withBuildIdentifier(String build). The functionality remains the same, allowing the application build to be set rather than relying on the versionCode. See Android API documentation  for details. Log messages from the Android SDK have been updated to reflect updated New Relic support team contact information. Fixes This release improves UI performance when an app has crashed and that crash is being sent to New Relic. The logic for sampling memory and CPU resources during an interaction trace was improved to limit the use of system resources. A crash was addressed in a rare instance when the Apache BasicHttpRequest library was used for networking purposes.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-530","eolDate":"2018-09-03"},{"agent":"android","date":"2020-12-15","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.28.1.zip","version":"5.28.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Crash reports uploads are sent immediately for wired connections (i.e., AndroidTV). Previously, crashes were deferred until the first harvest of the next app launch. Android Gradle Plugin Support This will be the last version of the Android agent to support versions 2.+ of the Android Gradle Plugin. Support statement: New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.21.3 .","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5281","eolDate":"2022-12-15"},{"agent":"android","date":"2020-10-15","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.27.1.zip","version":"5.28.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Improved attribute validation The agent will no longer reject events containing invalid attributes. Attributes that fail basic event validation are pruned from the map of provided event attributes. We've also corrected an event creation error where attribute maps containing null keys would result in events with a subset of passed attributes. This applies to attributes passed torecordCustomEvent(), recordEvent() and recordBreadCrumb() API methods. Map uploads are now compressed by default To disable compressed uploads, add the following to the newrelic.properties: Fixed in this release Fixes the java.lang.LinkageError runtime crash when instrumenting OkHttp 4.9 Fixed IllegalArgumentException thrown during builds when the agent inspects classes compiled with JDK 9 and higher. Classes compiled with JDK 9 through JDK 11 are now inspected for instrumentation","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5280","eolDate":"2022-10-15"},{"agent":"android","date":"2020-09-10","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.27.1.zip","version":"5.27.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed MissingPropertyException thrown by newRelicInstrumentTask when building with Android Gradle Plugin 2.x","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5271","eolDate":"2023-09-10"},{"agent":"android","date":"2020-09-03","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.27.0.zip","version":"5.27.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Enhanced the New Relic Gradle plugin's build-time reporting of ProGuard/DexGuard maps Maps will only be reported during select variant builds (i.e., Release) Build variants are assigned unique build IDs Maps can be compressed prior to upload Please refer to Android agent crash reporting  for more detail regarding these features. These features are configurable through the New Relic Gradle Plugin extension  and existing newrelic.properties. Fixed in this release Fixed build errors that occur when older (pre-3.0) versions of the Android Gradle Plugin is used Fixed 'IllegalStateException' crash that resulted when header queries were made to failed HttpsUrlConnection requests","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5270","eolDate":"2023-09-03"},{"agent":"android","date":"2020-07-13","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.26.0.zip","version":"5.26.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Updated for Android Gradle Plugin 4.0 See the Android compatibility matrix here Fixed in this release Missing O/S versions for Android 9 and above are now reported as undefined O/S major  versions that were reported as empty string are no longer recorded if the agent is unable to determine a value OkHttp2 and OkHttp3 requests are now reporting bytesSent in HttpRequests, when available Interaction counts reported as zero are now recorded with the correct value","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5260-0","eolDate":"2023-07-13"},{"agent":"android","date":"2020-05-18","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.25.2.zip","version":"5.25.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed additional incompatibilities with DexGuard and AGP 3.6 Fixed automatic map uploads for some variants types, broken in the previous hotfix (our apologies)","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5252","eolDate":"2023-05-18"},{"agent":"android","date":"2020-05-06","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.25.1.zip","version":"5.25.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed detection of DexGuard-generated mapping.txt files (\"mappingFile is null \") Update OkHttp request transaction state when interceptors are used Improved visibility into obfuscation map uploads. Users can invoke the Gradle task newRelicMapUpload{Variant}  (newRelicDexguardMapUpload{Variant}  for DexGuard) to resend tagged obfuscation maps. {Variant}  is dependent on configuration. Toned-down plugin debugging messages inadvertently emitted as errors","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5251","eolDate":"2023-05-06"},{"agent":"android","date":"2020-04-06","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.25.0.zip","version":"5.25.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Adds support for Android Gradle Plugin (AGP) version 3.6. AGP 3.6 requires version 5.25.0 of the New Relic agent. Previous agent versions are not supported with 3.6. Apache HttpClient instrumentation is deprecated Fixed in this release Fix unhandled exception when closing a Cronet HttpUrlConnection on error conditions Fixed OkHttp2/Retrofit crash when reading error response bodies Better content length/bytes received reporting for OkHttp2 and OkHttp3 Known issues The New Relic agent may not correctly detect the 'mapping.txt' file using Dexguard and AGP 3.6. We are looking into the issue.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5250","eolDate":"2023-04-06"},{"agent":"android","date":"2020-02-18","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.24.3.zip","version":"5.24.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release The agent now uploads mapping.txt  files to New Relic when bundle  tasks are used with Dexguard.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5243","eolDate":"2023-02-18"},{"agent":"android","date":"2019-12-03","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.24.2.zip","version":"5.24.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed a harvest error that occurred when the sum of all activity traces exceeded the default limit (64k characters), and filtering removed all traces. Fixed a set of DEX failures that emerged when JSONObject(String) and JSONArray(String) invocations were instrumented. Unfortunately, the time spent in instance construction can no longer be reported as a result of the change.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5242","eolDate":"2022-12-03"},{"agent":"android","date":"2019-10-28","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.24.1.zip","version":"5.24.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Clear up duplicate reporting of device data Address a build failure when instrumenting apps using Gson 2.8.6 Exclude additional 3rd party packages from instrumentation (to address a D8 crash)","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5241","eolDate":"2022-10-28"},{"agent":"android","date":"2019-09-24","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.24.0.zip","version":"5.24.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Updated instrumentation to include Fragment and Activity classes derived from androidx support packages. Updated 3rd party licenses information. Fixed in this release Fixed crash that occurred when the agent tried to instrument Kotlin module_info.class files. Updated JSON instrumentation to address crash that could occur when using R8 tools.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5240","eolDate":"2022-09-24"},{"agent":"android","date":"2019-05-06","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.23.0.zip","version":"5.23.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Refactored New Relic Agent plugin to conform to Gradle 5 Fixed in this release Fixed build crash that occurred during debug logging when using Dexguard versions 8.2 - 8.4 Eliminated erroneous exception logging for CountingInputStream implementations Clarified documentation of analytic enablement  options (FeatureFlag.AnalyticsEvents and NewRelic.withAnalyticsEvents)","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5230","eolDate":"2022-05-06"},{"agent":"android","date":"2019-03-08","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.22.1.zip","version":"5.22.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixes an issue that caused lock contention on the main thread when an Activity or Fragment started during harvest.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5221","eolDate":"2022-03-08"},{"agent":"android","date":"2019-02-04","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.22.0.zip","version":"5.22.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Updated instrumentation support for OkHttp to version 3.12.0 Minimum supported versions are now OkHttp 3.5.0, and OkIO 1.11.0 Dependency JARs using signature validation  are detected during instrumentation. The agent cannot instrument JARs that use signature validation  when signed. JARs whose manifest contains SHA1-Digest or SHA-256-Digest manifest attributes will not be modified Increase the number of available user attributes from 64 to 128 Fixed in this release Fixes null pointer exception during map upload when the generated map file is empty, such as when Proguard is enabled, but obfuscation is disabled using the -dontobfuscate  Proguard configuration setting.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5220","eolDate":"2022-02-04"},{"agent":"android","date":"2019-01-03","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.21.3.zip","version":"5.21.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixes build failure when Kotlin extensions are used Eliminates a race condition that could result in ANR in apps that make many concurrent network requests","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5213","eolDate":"2022-01-03"},{"agent":"android","date":"2018-12-03","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.21.2.zip","version":"5.21.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Corrects a condition where a Gradle task would block when uploading Proguard/Dexguard map files","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5212","eolDate":"2021-12-03"},{"agent":"android","date":"2018-11-26","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.21.1.zip","version":"5.21.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Corrects a problem detecting R8-generated map files Removes unnecessary Proguard map file processing task","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5211","eolDate":"2021-11-26"},{"agent":"android","date":"2018-11-05","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.21.0.zip","version":"5.21.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Add support for the upcoming Android D8/R8 toolset Discontinue the New Relic Maven plugin Disable CPU sampling for apps running on Android 8 and higher Fixed in this release Correct the mismatched build ID shared between the stamped and uploaded Proguard/Dexguard map file and submitted crashes Fix an issue that caused a Facebook login API failure Update agent plugin to address Gradle 5 warnings Notes Dexguard users must upgrade to version 8.2.22 to be compatible with this release.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5210","eolDate":"2021-11-05"},{"agent":"android","date":"2015-08-05","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.2.1.zip","version":"5.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes a crash that occurred when attempting to cast the result of OkHttpFactory.open() to a javax.net.ssl.HttpsURLConnection, resulting in a java.lang.ClassCastException Resolves a crashing java.lang.NullPointerException when the app is brought from background to foreground in a specific scenario","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-521","eolDate":"2018-08-05"},{"agent":"android","date":"2018-10-15","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.20.0.zip","version":"5.20.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Support for the Maven plugin is now deprecated, and will be removed in version 5.21.0. The minimum supported SDK level (minSdkVersion) is now 14 (Android 4.0) Fixed in this release Removed dependency on legacy Android Apache library, which resulted in NoClassDefFoundError exceptions when targeting Android SDK 28. Removed cast exception with OkHTTP2 CacheResponseBody when using Retrofit 1.9.0 with OkHttp 2.7.5 . Corrected mismatched UUID added to Proguard/Dexguard mapping file (the map UUID didn't match the UUID of reported crashes). Restored missing Dexguard lambda instrumentation. Corrected representation of LONG numeric attributes to prevent loss of precision (agent could not record precise timestamp attributes). Crashes that occur prior to successfully connecting to collector will be queued until a valid connection data token is received. Restored agent shutdown and final harvest when foreground services present.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5200-0","eolDate":"2021-10-15"},{"agent":"android","date":"2015-07-29","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.2.0.zip","version":"5.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements The SDK now tracks the number and duration of network requests per interaction, which will be used in upcoming features. Deprecates the NewRelic.shutdown() method, which will be removed from the API in a future release. Fixes Resolves a potential UI performance issue when experiencing low/no network connectivity. Addresses a crashing java.lang.RuntimeException thrown while determining the root cause of an app crash. Fixes a potential crash during trace collection resulting from a java.lang.ClassCastException.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-520","eolDate":"2018-07-29"},{"agent":"android","date":"2018-09-10","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.19.1.zip","version":"5.19.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes NoClassDefFoundError crash due to missing Apache classes for apps targeting Android 9 (SDK versions P  or 28 ). This release is only needed by apps that target SDK 28 or higher.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5191-0","eolDate":"2021-09-10"},{"agent":"android","date":"2018-06-08","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.19.0.zip","version":"5.19.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements The agent will now recognize region-specific application tokens.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5190","eolDate":"2021-06-08"},{"agent":"android","date":"2018-04-03","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.18.1.zip","version":"5.18.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed problem reading from the error stream of instrumented Http/HttpsUrlConnection requests. Fixed problems uploading Proguard/Dexguard mapping.txt files. Eliminated a delay in shutting down the app when reporting a crash.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5181","eolDate":"2021-04-03"},{"agent":"android","date":"2018-03-07","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.18.0.zip","version":"5.18.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Addressed potential ANR at launch when an app has the Firebase performance monitoring SDK also running.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5180","eolDate":"2021-03-07"},{"agent":"android","date":"2018-02-14","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.17.2.zip","version":"5.17.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed instrumentation failures introduced in the 5.17.0 release. Corrected a hang during instant app shutdown that could occur during a crash.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5172","eolDate":"2021-02-14"},{"agent":"android","date":"2018-02-08","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.17.0.zip","version":"5.17.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fixed trace instrumentation crash introduced in 5.17.0 release.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5171","eolDate":"2021-02-08"},{"agent":"android","date":"2018-02-07","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.17.0.zip","version":"5.17.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Added instrumentation support for Android Instant Apps \nThe agent now detects and instruments all feature modules for an instant app. Because instant apps are typically side-loaded, users must add NewRelic.start() calls to each entry point activity in the module. We've also created a document to help integrate the agent into your Instant App. See Install the New Relic plugin for Android Instant Apps  for more information. Fixed in this release Correctly restore any pre-existing unhandled exception handler when the agent shuts downs. Maintain the state of existing unhandled exception handlers when the agent returns to foreground. Fixed instrumentation of abstract classes derived from Android SDK classes. Fixed instrumentation failure when using certain Java 8 features, such as lambdas. Updated instrumentation support for Dexguard 8 on Android Studio 3.0. Enforce @SkipTrace with Android SDK-derived classes. Previously, onCreate() and onCreateView() could not be skipped from Activity, Fragment and other SDK classes.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5170","eolDate":"2021-02-07"},{"agent":"android","date":"2017-12-14","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.16.0.zip","version":"5.16.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release MobileRequestError events now contain the response body returned in the network request response, if one exists. Response bodies will only be reported if the withHttpResponseBodyCaptureEnabled feature flag  is enabled. HttpResponseBodyCapture is enabled by default. Response body data will be limited to the first 4096 bytes (the Insights attribute limit). A content type attribute will also be added to the event if a \"content_type\" header is found in the response. MobileRequestError events now also contain any cross-application tracing (CAT) data returned in the response headers. See Introduction to cross-application traces  for more information. Fixed in this release Stream file handle usage during class instrumentation has been tightened up to prevent potential resource leaks. Proguard map detection of release variants when using AndroidStudio 3 has been restored. Add content type parameter missing from HTTP error traces when instrumenting OkHttp2, OkHttp3 and Retrofit requests.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5160","eolDate":"2020-12-14"},{"agent":"android","date":"2017-11-08","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.15.2.zip","version":"5.15.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release The NetworkRequests feature flag  is now enabled by default. The feature can still be disabled (and re-enabled) at any time if the additional MobileRequest events  are not needed. Added a feature flag for MobileHandledException events (FeatureFlag.HandledExceptions). Handled exception reporting is enabled by default; use this flag to globally disable the feature. Fixed in this release Crash reports are again uploaded immediately, rather than during the next scheduled harvest. Correctly detects Proguard/Dexguard-enabled apps, and uploads their mapping.txt files to the symbol upload collector. Restored missing instrumentation of Square Retrofit2 classes. Added missing response codes from HttpURLConnection POST requests. The MobileRequest event byteSent attribute has been renamed to bytesSent. Any Insights queries using byteSent must be updated to maintain accuracy.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5152","eolDate":"2020-11-08"},{"agent":"android","date":"2017-10-18","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.15.1.zip","version":"5.15.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release The agent has added API methods to report handled exception events to Insights! Details and examples of how to use the new APIs can be found in the Android SDK API document recordHandledException . We've also updated the document that describes how to query handled exception events from Insights: Insights query examples for New Relic Mobile  provides useful queries for examining handled exception event data. Apps that use Proguard or Dexguard may have to make adjustments to their Proguard configuration to preserve all exception information. Please review Configure ProGuard or DexGuard for Android Apps  for more details. Added support for automatic instrumentation when using Android Gradle plugin version 3 (used by Android Studio 3). Fixed in this release HttpURLConnection requests now return the correct status codes in MobileRequest events Report carrier type  as 'Unknown' if a valid carrier type can not be determined Restore instrumentation of Android support classes (missing since version 5.13.0)","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5151","eolDate":"2020-10-18"},{"agent":"android","date":"2017-10-02","downloadLink":null,"version":"5.15.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"This release has been removed due to deployment issues with Jcenter. Please use release version 5.15.1 instead. ### New in this release The agent has added API methods to report handled exception events to Insights! Details and examples of how to use the new APIs can be found in the Android SDK API document recordHandledException . We've also updated the document that describes how to query handled exception events from Insights: Insights query examples for New Relic Mobile  provides useful queries for examining handled exception event data. Apps that use Proguard or Dexguard may have to make adjustments to their Proguard configuration to preserve all exception information. Please review Configure ProGuard or DexGuard for Android Apps  for more details. Added support for automatic instrumentation when using Android Gradle plugin version 3 (used by Android Studio 3). ### Fixed in this release HttpURLConnection requests now return the correct status codes in MobileRequest events Report carrier type  as 'Unknown' if a valid carrier type can not be determined Restore instrumentation of Android support classes (missing since version 5.13.0)","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5150","eolDate":"2020-10-02"},{"agent":"android","date":"2017-06-14","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.14.0.zip","version":"5.14.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release The agent now reports network request events to Insights! This feature must be enabled when starting the agent using the NetworkRequests  FeatureFlag. When enabled all network calls will be tracked, in addition to network errors. We've also added a new document that describes how to query network events from Insights. Mobile Request Query Examples  provides useful queries for examining network request event data. Fixed in this release Ensure there is no shared activity history state between launched sessions.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5140","eolDate":"2020-06-14"},{"agent":"android","date":"2017-05-10","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.13.0.zip","version":"5.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Added a new MobileBreadcrumb  event type that allows you to annotate the execution of your app, to help troubleshoot crashes and provide greater detail in Insights. See the recordBreadcrumb()  API docs for more information. Added an additional recordCustomEvent  method that takes the event name as an optional parameter. This avoids the need to add a name attribute in the passed attribute set. See the recordCustomEvent()  API docs for more information.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5130","eolDate":"2020-05-10"},{"agent":"android","date":"2017-04-21","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.12.3.zip","version":"5.12.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Validate custom event type names with the same rules as the backend service, reporting invalid event types to the user immediately. Previous agent versions would allow custom event type names that would be rejected by Insights during ingest. The name may be comprised of alphanumeric, space, ., : or _ characters.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5123","eolDate":"2020-04-21"},{"agent":"android","date":"2017-03-29","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.12.2.zip","version":"5.12.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fix instrumentation failure when using Dexguard, Retrolambda and build product flavors.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5122","eolDate":"2020-03-29"},{"agent":"android","date":"2017-03-23","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.12.1.zip","version":"5.12.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed in this release Fix a null pointer exception crash that occurred during completion of activity traces. Optimize updates to the analytics attribute store. OkHttp3 responses are no longer pre-buffered. Streamed responses without a content length header will report -1 for content length.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5121","eolDate":"2020-03-23"},{"agent":"android","date":"2017-03-08","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.12.0.zip","version":"5.12.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Updates to recording custom events With this agent release, Mobile custom events are now recorded as their own event type in New Relic Insights. Until this release, custom events for New Relic Mobile were bundled under the \"Mobile\" event type (category='Custom'). This release includes a new method to be used for adding custom events: recordCustomEvent . The previously used method for this, recordEvent , is now deprecated. This update is to satisfy customer requests for: Improved Insights query performance Defining your own custom event names Finding custom events in Insights more easily Flexibility to define data retention per custom event type (1 day default; more with Insights Pro) For this and the next several releases, we will continue to support the previous method for custom events (recordEvent) to avoid impact on your queries and existing dashboards. Fixed in this release Ignore BaseFragmentActivityGingerbread base class when auto-instrumenting activities.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5120","eolDate":"2020-03-08"},{"agent":"android","date":"2015-06-19","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.1.2.zip","version":"5.1.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Resolves an issue where the connection type used by the app may have been incorrectly reported.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-512","eolDate":"2018-06-19"},{"agent":"android","date":"2017-02-28","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.11.0.zip","version":"5.11.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Adds recording of network request error events The agent now generates MobileRequestError  events describing failures in network requests. This new event tracks networking and HTTP errors, and includes attributes for common request properties. More details can be found at Mobile Request Error Events . Adds additional session attributes lastInteraction  allows you to see in Insights, what the most common exit screen was for customers across all sessions or a filtered selection of sessions. appBuild  allow developers to view the adoption of a new build, particularly if rolled out under an existing app version number. Originally, this was only available on crash events. architecture  and runTime  allow you to see the hardware type and Java runtime version the of the device on which the app is running. Both values are taken form the device's system properties, and are useful for debugging device-specific issues. Fixed in this release Fix the minimum utilization  instrumentation filter Slow interaction trace capture relied on an incorrectly interpreted minimum utilization value. In some cases you may see more slow interaction traces than previous agent versions. Please reach out to support if you are not seeing slow interaction traces. Fix crash when using OkHttp 3.2.0 web sockets Although the Android agent does not officially  support OkHttp versions prior to 3.4, this fix avoids crashes that may occur when including 3rd-party libraries that may depend on those versions of OkHttp. Warn when agent and class rewriter versions do not match Instead of halting a build of the application, the agent will warn of this benign scenario. Agent JAR version mismatch sometimes occurs when upgrading to a new agent version. Fix ConcurrentModificationException crash This change addresses a rarely seen crash that occurs during agent start-up. Move remaining sampler shutdown to background thread This change addresses a lag seen during interaction trace completion.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5110","eolDate":"2020-02-28"},{"agent":"android","date":"2015-06-05","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.1.1.zip","version":"5.1.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Resolves a compatibility issue that may occur when running apps on Android M preview.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-511","eolDate":"2018-06-05"},{"agent":"android","date":"2017-01-12","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.10.0.zip","version":"5.10.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New in this release Fixed instrumentation failures that occurred when building apps that used both Dexguard and the Android Retrolambda plugin. Updated agent logging to remove noise and conform to Gradle logging conventions.Adding --info or --debug to the Gradle build will result in more detailed logging messages. Replaced Gradle agent plugin POM file missing from Jfrog Bintray artifact repository. Agent and agent plugin are now built using JDK 1.8.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-5100","eolDate":"2020-01-12"},{"agent":"android","date":"2015-06-03","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.1.0.zip","version":"5.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements The Android SDK will now collect an app build identifier when an app crashes, which will be displayed in parentheses beside the version number in the Crash Details page in RPM. This value defaults to the string versionCode that is specified in the app's AndroidManifest.xml. If versionCode is not specified the build identifier not be displayed. A new API method withBuildIdentifier(String) was added to allow specifying a custom app build identifier, overriding the default value pulled from versionCode.  Updates to unique ID management to improve accuracy of unique device counts.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-510","eolDate":"2018-06-03"},{"agent":"android","date":"2015-05-19","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.0.3.zip","version":"5.0.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes a crash resulting from empty body responses when using version 1.9 of the Retrofit library. Corrects an internal issue with reserved attribute names. 'interactionDuration' is now a reserved attribute name.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-503","eolDate":"2018-05-19"},{"agent":"android","date":"2015-05-01","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.0.1.zip","version":"5.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Corrects an issue where the timeSinceLoad attribute  may not have been sent for Insights Events.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-501","eolDate":"2018-05-01"},{"agent":"android","date":"2015-05-01","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_5.0.0.zip","version":"5.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Insights for Mobile This release introduces Insights for New Relic Mobile. The Android SDK now automatically records Session, Interaction, and Crash events in New Relic Insights. After upgrading to this release, you will be able to build queries and dashboards in Insights with the new Mobile event type. All events include attributes reflecting session and unique install identifiers, device, OS, geography, duration and other data. See the Insights documentation  for a description of Mobile attributes and Insights usage details. Custom events In addition to the standard events available in Insights, you can now record custom events. Custom events have a name and set of key:value attributes, perfect for capturing usage, monetization, and custom performance data. Custom events are also available in Insights. See the Mobile Custom Event documentation  for details. Custom attributes In addition to event-specific attributes, this release provides support for install-scoped attributes. An attribute recorded in the app will be attached to every Session, Interaction, Crash, and Custom event reported from that instance of the app. Custom attributes are perfect for tracking durable information like account id, campaign origin, subscription level, etc. See the Mobile Custom Attribute documentation  for details. The Android API documentation  includes details on sending custom events and attributes to Insights.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-500","eolDate":"2018-05-01"},{"agent":"android","date":"2014-10-29","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_4.98.0.zip","version":"4.98.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Resolves a crash in InputStream instrumentation when chunked transfer encoding is used. Custom interaction names, when specified, are now used in Crash interaction history trails.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-4980","eolDate":"2017-10-29"},{"agent":"android","date":"2014-10-08","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_4.87.0.zip","version":"4.87.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Crash Reporting This release introduces crash reporting for mobile apps. Crash reporting supports capture and reporting of unhandled Java runtime exceptions. Crashes include interaction trails: a history of automatically instrumented actions that occurred during the app session leading up to the crashing event. No breadcrumbs needed. The SDK includes a NewRelic.crashNow() method to trigger a test crash quickly and easily. You can also disable crash reporting via the runtime API. When building an app with Proguard enabled, the Proguard mapping file is sent to New Relic to automatically provide human readable crash reports in the UI. Session improvements The SDK now more consistently records MobileSession events in Insights when users use various app switchers on Android 4.x. Fixes Improve reported traffic accuracy Corrects an issue where the SDK could continue to report an app as active when it had entered the background. This fix will reduce the traffic reported for an app to more accurately reflect actual usage. Improve thread naming accuracy Corrects an issue where the SDK reported some metrics with an incorrect display name. This fix will more accurately reflect thread breakdown data in interactions.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-4870","eolDate":"2017-10-08"},{"agent":"android","date":"2015-04-08","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_4.273.4.zip","version":"4.273.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Addresses an issue that could cause a null pointer exception when an empty response body was received using older versions of the Retrofit library Corrects a potential ConcurrentModificationException during instrumentation when a large number of HTTP requests was made","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-42734","eolDate":"2018-04-08"},{"agent":"android","date":"2015-03-04","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_4.265.0.zip","version":"4.265.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements This release adds instrumentation for versions 2.1+ of Square's OkHttp library. 1.x versions continue to be supported. This release also adds support for the Retrofit (1.8+) and Picasso (2.4+) libraries from Square. Notes With this release, the Android SDK will require a minimum version of Android 2.3. Apps requiring Android 2.2 can still use the legacy version of the New Relic Mobile Android SDK, 4.244.0 (instructions here ). The legacy version will only receive critical updates if necessary. Please note that versions 2.x of the OkHttp library require Android 2.3+ and Java 7. (see https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-200 )","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-42650-0","eolDate":"2018-03-04"},{"agent":"android","date":"2015-02-19","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_4.244.0.zip","version":"4.244.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements A custom application version can now be set using the new method NewRelic.withApplicationVersion(String appVersion) Added the method NewRelic.recordMetric(String name, String category) to allow recording a custom metric with just a name and category, the value defaulted to 1.  Notes This release supports Android 2.2+. Future releases will require 2.3+.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-42440","eolDate":"2018-02-19"},{"agent":"android","date":"2015-02-05","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_4.190.0.zip","version":"4.190.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Improved instrumentation of the OkHttp library v1.6 to include support for OkURLFactory Notes This will be the last release of the Android SDK to support Android 2.2. Future versions will require 2.3+.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-41900","eolDate":"2018-02-05"},{"agent":"android","date":"2015-01-08","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_4.178.0.zip","version":"4.178.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Addresses an issue that may have caused an upgraded application to continue reporting the older version of the application to New Relic. Corrects a potential RuntimeException when the HEAD method was used in an HTTP request. Resolves an IllegalArgumentException that could have occurred in the edge case where the start or end time of an HTTP transaction was invalid.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-41780","eolDate":"2018-01-08"},{"agent":"android","date":"2014-11-21","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_4.120.0.zip","version":"4.120.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements You can now disable the capture of the HTTP response body for requests by calling NewRelic.disableFeature(FeatureFlag.HttpResponseBodyCapture). You can now disable crash reporting by calling NewRelic.disableFeature(FeatureFlag.CrashReporting). The SDK was updated to accept the HTTP method in NewRelic.noticeHttpTransaction() and NewRelic.noticeNetworkFailure() allowing more detailed information to be collected. Fixes Resolves an issue related to recording a URL that could have potentially resulted in a Null Pointer Exception.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-41200","eolDate":"2017-11-21"},{"agent":"android","date":"2014-08-22","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_3.429.0.zip","version":"3.429.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements New Gradle Plugin We've rewritten the New Relic Gradle plugin from the ground up to impose a smaller footprint on your build and improve compatibility with the new Gradle Daemon.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-34290","eolDate":"2017-08-22"},{"agent":"android","date":"2014-07-24","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_3.419.0.zip","version":"3.419.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Naming changes to Interaction Traces We've changed the naming scheme for Interaction Traces to be more clear. Instead of \"ActivityClass#onCreate\", you'll see \"Display ActivityClass\". If you want to change the name of a running Interaction, just call setInteractionName(). New API methods for starting and stopping Interaction Traces We've added two new methods to the NewRelic class API to give you greater control over starting and stopping Interaction Traces. The startInteraction() method now just takes a string, no context needed. Use endInteraction() to stop a running interaction. New @SkipTrace annotation to exclude methods from default instrumentation While automatic instrumentation is one of the more convenient features of the agent, there are a few cases where it can get in the way. Should you encounter one of these cases, simply add this annotation to the method in question, and the agent will skip it during compile time instrumentation.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-34190","eolDate":"2017-07-24"},{"agent":"android","date":"2014-06-12","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_3.407.0.zip","version":"3.407.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Improvements API methods now check for bad values and throw IllegalArgumentException Previously, our API methods would silently discard bad data without recording errors or metrics. We've changed this behavior to be more informative by throwing an exception when bad arguments are passed. Fixes Android Gradle plugin 0.10 compatibility Version 0.10.0 of the plugin introduced a subtle change that caused errors during build time that would produce ClassCastException errors at runtime. We’ve fixed this issue and verified we're also compatible with 0.11. Improved thread safety in the API Some API methods exhibited race conditions under heavy utilization. These race conditions are now solved. Summary metrics occasionally exhibited bad values You may have noticed strange numbers in your application overview chart. We've isolated the cause of these numbers and fixed the underlying issue in the agent.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-34070","eolDate":"2017-06-12"},{"agent":"android","date":"2014-05-15","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_3.378.0.zip","version":"3.378.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements CPU vitals in Interaction traces. We've added CPU vitals in interaction traces. You'll now be able to see your application's usage of the device's CPU(s) as a percentage of the total CPU time. Fixes Restore compatibility for building with Java 7u55 and support Java 8. Java 7u55 introduced a slight change that broke our build process. We've corrected this issue and added support for Java 8. Applications without version numbers crashed the agent. Strangely, it's possible to build an Android application without a version number defined in the manifest. We now detect this case and shut down the agent cleanly with an error message indicating we require a version number. Encode custom Http(s) error response bodies. Http(s) error response bodies are normally encoded to ease escaping. However, errors reported via the API were not encoded. We've fixed this so all errors should appear properly in the UI.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-33780","eolDate":"2017-05-15"},{"agent":"android","date":"2014-04-07","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_3.361.0.zip","version":"3.361.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Better auto-naming support for Fragments. Previously, separating fragments from the calling Activity required renaming the running interaction. Now, Fragments have first class treatment and will show up alongside Activities. OkHttp instrumentation. If you're using Square’s OkHttp library, you'll now see your HTTP transactions automatically appear on RPM. There’s no longer any need to use the agent API to track these transactions. Fixes Clear all metric caches after a failed harvest cycle. In rare cases where the agent is unable to connect to New Relic's servers, some metric caches persisted and caused unusually large metric numbers. Now, all these caches are cleared at the end of the cycle to prevent compounding aggregation. Improved inflight interaction naming. There are some cases in which renaming a running interaction did not fully rename the metric scope. This fix ensures all aspects of the interaction bear the new name. Fixed an issue in Proguard bytecode handling. While compiling Android apps with Proguard's optimizations turned on is discouraged, the agent does its best to support such optimizations. However, we mishandled one such case and have fixed it in this release.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-33610","eolDate":"2017-04-07"},{"agent":"android","date":"2014-03-11","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_3.330.0.zip","version":"3.330.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Ensure interactions complete when an app leaves the foreground. Previously, it was possible for an interaction to persist across application foreground/background lifecycles if a trace segment was still in flight. This resulted in interaction traces extending past the default 60-second limit. Now, interactions are stopped when the app leaves the foreground regardless of segment states. Machine metrics continue generation upon app restore. Machine metrics now continue to generate after an app has been in the background and enters the foreground. Previously, they were only generated from launch until the app entered the background. Improve BitmapFactory instrumentation scoping. BitmapFactory’s static method instrumentation is now scoped to more tightly to its package and class to prevent instrumentation of similar but unrelated method signatures. Added more instrumentation to summary metrics. Now all instrumented methods are included in summarized category metrics including those only present in background threads. Added missing methods to HttpsUrlConnection instrumentation. Several missing proxy methods have been added to our HttpsUrlConnection shim. This restores the ability to override default HTTPS behavior.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-33300","eolDate":"2017-03-11"},{"agent":"android","date":"2014-02-26","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_3.308.0.zip","version":"3.308.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements New API methods for adding cross application tracing headers to noticeHttpTransaction(). In case the New Relic agent doesn't support the HTTP API you're using, you can manually submit a transaction via the noticeHttpTransaction() method. With this release, this method now allows you to set the NR cross application tracing header for tracking purposes. Fixes Fixed a rare build crash where newly constructed objects go unused and are later optimized down by ProGuard.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-33080","eolDate":"2017-02-26"},{"agent":"android","date":"2014-01-16","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_3.264.0.zip","version":"3.264.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements New API method for configuring logging verbosity. You can now choose how verbose the agent will be at boot by chaining withLogLevel() before your NewRelic start() call. The default level is INFO. New API method for renaming inflight interactions. Call NewRelic.setInteractionName() at the beginning of your onCreate() method to set a custom name for your interaction. This usually defaults to the name of the Activity subclass. Method tracing optimizations. We’ve carefully reviewed the code involved in tracing instrumented methods and reduced its CPU and memory overhead substantially.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-32640","eolDate":"2017-01-16"},{"agent":"android","date":"2013-12-17","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_3.239.0.zip","version":"3.239.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Call checkcast before invoking NR instrumentation. This fixes an issue where the Dalvik VM refuses to load a class with our instrumentation in cases where the inbound object is not the expected type as determined by static code analysis. Don't attempt to instrument constructors in subclasses of classes we normally instrument. While we support instrumenting constructors by replacing the call to , we don't support doing this in subclasses. For now, we ignore these cases but may return to adding inline instrumentation to constructors in the future. Java 7u60 (pre-release) refactored the class in which we were storing our invocation dispatcher. We've future proofed the agent by storing the dispatcher in another core class.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-32390","eolDate":"2016-12-17"},{"agent":"android","date":"2013-12-01","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_3.214.0.zip","version":"3.214.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements End to end instrumentation for your mobile applications. Automatic instrumentation of important system objects and methods. Customizability to allow for instrumentation of your most important objects and methods.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-32140","eolDate":"2016-12-01"},{"agent":"android","date":"2013-11-21","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_2.444.0.zip","version":"2.444.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed rare bug in Eclipse where all projects are built with New Relic regardless of agent jar presence.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-24440","eolDate":"2016-11-21"},{"agent":"android","date":"2013-09-25","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_2.433.0.zip","version":"2.433.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added support for ProGuard with Ant builds. Clarified naming of unknown carriers on Android","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-24330","eolDate":"2016-09-25"},{"agent":"android","date":"2013-09-11","downloadLink":"https://download.newrelic.com/android_agent/ant/newrelic-android-2.426.1.zip","version":"2.426.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added support for ProGuard with Ant builds. *Note: Version 2.426.0 of the Android agent already works with ProGuard and other build systems (Gradle, Maven, and Eclipse).","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-24261","eolDate":"2016-09-11"},{"agent":"android","date":"2013-06-27","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_2.426.0.zip","version":"2.426.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements The agent now detects if the app was instrumented properly and displays an error message if otherwise. The Eclipse plugin now refreshes your project after installing/updating New Relic. Improved post installation messaging in Eclipse. Fixes Fixes an issue in Eclipse on Windows where Eclipse is installed in a location with a space in the path. Repackaged the agent with JarJar to prevent class space collisions. Fixes an issue where a re-used HttpRequest object would have multiple X-NewRelic-ID headers added.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-24260","eolDate":"2016-06-27"},{"agent":"android","date":"2013-06-07","downloadLink":null,"version":"2.397.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Gradle and Android Studio support Now you can add New Relic to your Gradle builds Android Studio support via Gradle/Maven","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-23970","eolDate":"2016-06-07"},{"agent":"android","date":"2013-05-31","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_2.365.zip","version":"2.365","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Install Process Eclipse plugin support Maven Sonatype repository Simplified Ant installation Eclipse Install via Eclipse plugin or Eclipse Marketplace Debug in Eclipse with New Relic Maven Reference New Relic in pom.xml Updated Agent API Control when New Relic starts Be sure to read our upgrade notes","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-2365","eolDate":"2016-05-31"},{"agent":"android","date":"2013-05-08","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_1.363.zip","version":"1.363","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic for Android is now compatible with Android 2.2 (API Level 8) Fixes a scenario where the New Relic SDK could cause Android apps to crash when running on Android 2.2 Fully supports network activity instrumentation and reporting on Android 2.2","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-1363","eolDate":"2016-05-08"},{"agent":"android","date":"2013-03-29","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_1.347.zip","version":"1.347","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Improved setup and configuration support, especially on Windows Fixes Fixes an issue where HttpURLConnection responses could raise an unhandled exception Fixes an issue where reported response time is much shorter than actual response time under certain conditions Fixes an issue where certain HTTP requests could raise an unhandled exception","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-1347","eolDate":"2016-03-29"},{"agent":"android","date":"2013-03-13","downloadLink":"https://download.newrelic.com/android_agent/ant/NewRelic_Android_Agent_1.338.zip","version":"1.338","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Happy Pi Day! Welcome to New Relic for Mobile Apps, we're glad to have you aboard.","slug":"docs/release-notes/mobile-release-notes/android-release-notes/android-1338","eolDate":"2016-03-13"},{"agent":"browser","date":"2016-11-03","downloadLink":null,"version":"998","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The Browser Agent, sometimes called the JS Agent, has multiple variants: Lite, Pro, Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent. New features Added the setCurrentRouteName API method [relevant only for Pro+SPA] : The agent now has an API method to set the current route name for the page. This api can be used to set the previousRouteName and targetRouteName for BrowserInteraction events. For details on how and why to use this API, see our Browser SPA API Docs Improvements Disabled insecure communication with New Relic : Previously the agent would send RUM data to the router without TLS if the request was initiated from an insecure page. Now the Browser Agent will always use TLS connection when transmitting data. Browser Agent no longer mutates the attributes object passed to the addPageAction API : Previously the agent would mutate the attributes object passed to add page actions by adding the default and page attributes onto this object. Bug fixes Fixed a compatibility issue with zone.js : Previously when the Browser Agent and zone.js were both included on a page, additional event handlers would be triggered twice. For example, when event handlers were added as properties, such as onreadystatechange, these handlers would be triggered twice in some browsers. This issue has now been resolved. Fixed a bug with cross-frame callbacks : Previously, when adding event handlers for events in iframes, the agent would attempt to wrap the provided callbacks. When the wrapping logic called the callback belonging to another frame, a permissions exception would be thrown. The agent will now only wrap callbacks created in the same frame. Fixed a memory leak when the Browser agent fails to load correctly How to upgrade To upgrade your agent to the latest version, see Upgrade Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v998","eolDate":"2019-11-03"},{"agent":"browser","date":"2016-08-24","downloadLink":null,"version":"974","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The Browser Agent, sometimes called the JS Agent, has multiple variants: Lite, Pro, Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent. New features Added newrelic.setErrorHandler API to allow for selective ignoring of known errors [Pro, Pro+SPA] : This API takes a single error handler function, which will be called for each error the agent captures. If the handler returns true, the error will NOT be recorded by New Relic, otherwise it will be processed normally. For details on how to use this API, see our Browser API Docs . How to upgrade To upgrade your agent to the latest version, see Upgrade Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v974","eolDate":"2019-08-24"},{"agent":"browser","date":"2016-08-17","downloadLink":null,"version":"971","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The Browser Agent, sometimes called the JS Agent, has multiple variants: Lite, Pro, Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent. New features Add support for keyboard change events [Pro+SPA]:  Keyboard events will now automatically trigger a Browser Interaction timing. Browser Timing Events now have Traced Callback Duration [Pro+SPA] : In order to match the attributes on other New Relic Browser related events, the Browser Timing events now include callback durations by default. Improvements Change harvest to not use sendBeacon : We now use the sendBeacon native API only for page unload. The agent will now attempt to use an XHR when available and save sendBeacon for unload events, in order to reduce the data transferred using the sendBeacon API. How to upgrade To upgrade your agent to the latest version, see Upgrade Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v971","eolDate":"2019-08-17"},{"agent":"browser","date":"2023-03-09","downloadLink":null,"version":"1227","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Add INP and long tasks reporting The interaction-to-next-paint metric is now calculated and reported at the end of user sessions, via the Google CWV  library. In addition, long continuously executed and blocking scripts detected by the PerformanceLongTaskTiming API are also forwarded to New Relic. This latter functionality is off by default, until a curated UI experience is created to utilize this data. Bug Fixes Revert unwrapping of globals on agent abort Partial revert of graceful handling change made in v1225 that unwrapped modified global APIs and handlers, which caused integration issues with other wrapping libraries and code. Add resiliency around SPA interaction saving Added resiliency code around SPA interaction node save functionality to ensure a cancelled interaction node without a parent further up the interaction tree does not cause an exception to be raised from the agent. Internal Add internal metrics to evaluate feasibility page resource harvests Internal metrics were added to track the feasibility and impact of collecting page resource information using the PerformanceObserver resource timings, such as scripts, images, network calls, and more. Collect supportability metrics at the end of page life Collate all of the internal statistic metrics calls, which, as of today, are sent at page start and periodically into one call made when the end user is leaving the page.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1227","eolDate":"2024-03-09"},{"agent":"browser","date":"2023-02-23","downloadLink":null,"version":"1226","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Enable back/forward cache Updating the agent default configuration to enable the back/forward cache feature previously released in version 1222 by default. Bug Fixes Revert xhr deny list timeslice metrics Customers were losing visibility into all calls on the page when denying timeslice metrics based on the deny list. This change reverts to the behavior seen in all previous versions of the browser agent. Handle unhandledPromiseRejections more gracefully The agent will attempt to handle niche objects throw from unhandledPromiseRejection events more gracefully. These cases could include objects with frozen or static properties, or custom extensions of the Error class without a set method in place. Disable metrics for missing entitlement Fixing issue where metrics harvesting was not being halted when the agent RUM call indicated the account did not have entitlement to the jserrors endpoint. Before this change, customers missing this entitlement would see network calls to the New Relic jserrors endpoint result in 403 or 409 errors.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1226","eolDate":"2024-02-23"},{"agent":"browser","date":"2023-02-10","downloadLink":null,"version":"1225","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Gracefully abort agent if not fully instantiated When importing of agent code fails, as when content gets blocked, the agent will clean up memory, the global scope, and any wrapped or modified APIs as much as feasible. Bug Fixes Resolve Google indexing of agent relative paths In previous versions, the agent script included relative paths to its lazy-loaded chunks, which Googlebot picked up and attempted to index as pages. This change removes those relatives paths from the loader and centralizes our lazy chunk loading of agent features. Refactor wrapping of Promise object The agent's wrapping of the Promise object has been refactored to address conflicts with third party libraries and to add newer methods available on the native object. The new wrapping implementation is more conventional and less error-prone. Fix uncaught promise error introduced in v1223 In some cases of failure to import agent script chunk \"629\", an error was thrown rather than caught and logged as a warning. The uncaught promise error responsible for this unintended behavior has been fixed.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1225","eolDate":"2024-02-10"},{"agent":"browser","date":"2023-02-08","downloadLink":null,"version":"1224","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Support SPA, XHR, and session trace features on Chrome for iOS Previously, the agent didn't collect SPA browser interactions, XHR events, or session trace data in Chrome for iOS, which uses the webkit engine with modifications. The agent now collects the same data in Chrome for iOS as in other supported browsers. Expose build version to newrelic global The build version is exposed to the newrelic global object. You can access it with newrelic.intializedAgents[<agentID>].runtime.version. Internal Add automation for documentation site updates on new releases A new release of the browser agent will automatically raise a PR to the documentation site with the relevant changelog items. Bug Fixes Fix multiple custom interaction end times Fixed an issue where multiple custom interactions harvested at the same time would result in only one interaction being persisted in New Relic. Prevent AJAX time slice metrics based on deny list Prevent time slice metric collection for AJAX calls when such a call matches an entry in the AJAX deny list. Bind navigator scope to sendBeacon Some browser versions will throw errors if sendBeacon doesn't have the navigator scope bound to it. A fail-safe action of binding the navigator scope to sendBeacon was added to try to support those browsers. Preserve unhandledPromiseRejection reasons as human-readable strings in error payloads The agent will attempt to preserve unhandledPromiseRejection reasons as human-readable messages on the Error payload that gets harvested. The previous strategy didn't always work, because Promise.reject can pass any value, not just strings. Fix missing interactions for dynamic routes in Next/React Fixed an issue where when using the SPA loader with Next/React, route changes that lazy loaded components wouldn't be captured. While the issue specifically called out Next/React, this should apply to Nuxt/Vue and Angular. Fix interactions missing API calls in Angular Fixed an issue where when using the SPA loader with Angular, route changes that contained API calls, via Angular resolver, wouldn't capture the xhr/fetch on the interaction. This works with eager and lazy routes in an Angular SPA.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1224","eolDate":"2024-02-08"},{"agent":"browser","date":"2023-01-27","downloadLink":null,"version":"1223","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Refactor loader architecture for improved developer experience This architectural release simplifies file structure and refactors the way features are composed, in preparation for future developer experience improvements. These changes are not anticipated to have impact on agent behavior or functionality.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1223","eolDate":"2024-01-27"},{"agent":"browser","date":"2023-01-18","downloadLink":null,"version":"1222","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features EXPERIMENTAL - Unblock instrumented pages from the back/forward cache (w/ feature flag) An instrumented page's back-forward cache eligibility was hampered by the agent's unload listener, which will be removed  when a feature flag is on. With the allow_bfcache enabled in the init config, the agent's definition of (the end of) an user's session is more refined, and it will no longer be blocking the browser from utilizing its respective b/f cache. Internal Reduce size of builds for modern browser targets The agent is now compatible with only modern web syntax (ES6+) ; this reduces loader size for these browsers by 20% or more . We target and test support for just the last ten versions of Chrome, Edge, Safari, and Firefox -- see browser agent EOL policy  for more details. Bug Fixes Prevent feature from collecting and harvesting future data if account entitlements are invalid The agent will now attempt to shut down an initialized feature if account entitlements are invalid. Accounts that lack entitlements to use certain endpoints will see many 403 errors in the console without this behavior. This behavior requires the Page View Event feature to be enabled. Do not collect XHR events for data URLs AJAX events for data URLs have not historically been collected due to errors in the agent when handling URLs without hostnames. Going forward, XHR calls to data URLs will not cause agent errors and will continue to be excluded from collection. Fix nrWrapper exclusion in error stack traces Restoring previous functionality whereby the nrWrapper agent method should be excluded from JavaScript error stack traces. Fix errors with global self redefinition Fixing an issue where external code redefining the self global variable causes the agent async loading to fail and the agent to crash. Fix check for sessionStorage object Ensure the agent does not crash when sessionStorage is not available or when the quota has been exceeded or set to 0.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1222","eolDate":"2024-01-18"},{"agent":"browser","date":"2022-12-15","downloadLink":null,"version":"1221","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Add infrastructure to run on web workers The agent's infrastructure will now allow for the agent to be built to run on web workers for future projects. Bug Fixes Expose webpack library as output type \"self\" vs. \"umd\" To address \"mismatched anonymous define\" errors thrown by RequireJS, the agent's webpack library output will no longer include UMD checks for CommonJS and AMD module environments, and will instead be exposed globally via self. Fix custom attribute handling in cases where the info block is loaded after initialization Fixed an issue where custom attributes could be cleared and reset if the info block was included on the page below the loader script. Our guidance still remains that all configurations should be included on the page above the loader code , however this is an attempt to do no harm when feasible for backwards compatibility. Update JS error bucketing algorithm The agent will now take into account the error object type, message, and original stack trace when deciding on whether multiple JS errors should be bucketed together. Fix initial page load interaction reporting with Nuxt Fixed an issue where when using the SPA loader with Nuxt, the initial page load interaction was never being completed. This resulted in events like errors being retained in memory and never harvested because they were tied to an incomplete interaction. Fix error with jsPDF library and SPA agent Fixed an issue with the jsPDF library where it was not correctly detecting browser native support for Promises due to our wrapper. This resulted in an exception and jsPDF not generating the PDF. This issue is not present with the pro or lite agent. Note : This issue does not affect the pro or lite agent. This change allows the jsPDF library to function correctly when the SPA agent is used. However, it does cause an internal error within the agent to be generated. This error does not break the agent, jsPDF, or other functionality. The issue is planned to be addressed in a future update.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1221","eolDate":"2023-12-15"},{"agent":"browser","date":"2022-10-07","downloadLink":null,"version":"1220","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"This release is in public preview. We're slowly rolling out these features to different browser agents based on the browser's instrumentation method. Here's the release timeline: Internal NR Platform release date: 10/07/2022 Production APM-injected release date: 10/7/2022 Production Standalone release date: Estimated around 12/13/2022 New Features Capture unhandled Promise rejections The Agent now observes and captures unhandled Promise rejections as JavaScript Error objects. Removed 3rd Party Cookies The browser agent no longer uses 3rd party cookies to maintain and track session information. 1st party implementation using window.sessionStorage is now used, which is automatically cleared when a page session ends. This is still managed using the privacy settings form in your browser application settings. LCP is no longer reported on initially-hidden pages LCP metrics are no longer reported on pages whose state is hidden at load time, such as tabs refreshing in the background of a focused tab. Async Module Loading Individual features of the browser agent can now be dynamically loaded, enabled, or disabled at runtime. Removal of script tag injection The agent no longer inserts other features into the page via a script tag insertion. It now uses network requests to instantiate other code modules. Updated test process In an effort to better support the majority of our traffic, the test suite required to merge PRs has been updated to run against the latest 10 major versions of Chrome, Firefox, Edge, Android, and the latest 5 major versions of Safari and iOS. As part of this process, outdated code and polyfill libraries aimed at supporting deprecated browsers are no longer included in production builds by default. Bug Fixes Fixed issue with BrowserInteraction nodes generating circular references BrowserInteractions no longer generate circular trees when they are self referential. Remove non-ASCII characters from builds Certain dependencies were appending non-ASCII characters to build files. These characters were affecting older Python agent implementations downstream that worked to parse and encode the agent snippet. The build files are now checked and cleaned of non-ASCII characters before shipping.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1220","eolDate":"2023-10-07"},{"agent":"browser","date":"2022-04-20","downloadLink":null,"version":"1216","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Internal NR Platform release date: 04/19/2022 Production APM-injected release date: 04/20/2022 Production Standalone release date: 04/27/2022 New Features Introduced obfuscation mechanism to payloads Added internal mechanism for applying regex and replacement rules to all strings in payloads to obfuscate before sending to ingest. Automatically obfuscate file:// protocol A change has been implemented in our handling of applications hosted locally on a file:// protocol. For security reasons, we can not send payloads that contain file information, so our previous implementation revolved around completely shutting the agent down when file:// protocols were detected. This change automatically obfuscates all file:// paths from our payloads before sending to ingest. Bug Fixes Fixed issue with trace ID random hex character length The final character in trace ID hex generation was returning as undefined, which translated to always be 0 (undefined & 15 === 0).  This change fixes this final character and ensures it is valid.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1216","eolDate":"2024-04-20"},{"agent":"browser","date":"2022-01-25","downloadLink":null,"version":"1215","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Internal NR Platform release date: 01/24/2021 Production APM-injected release date: TBD Production Standalone release date: TBD Collect supportability metrics for frontend frameworks Added frontend framework detection metrics to help guide future priorities for browser agent features. The following frontend frameworks will now be detected and analyzed: React Angular AngularJS Backbone Ember Vue Meteor Zepto Jquery","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1215","eolDate":"2024-01-25"},{"agent":"browser","date":"2022-01-06","downloadLink":null,"version":"1214","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added NetworkInformation attributes to LCP & FI The Largest Contentful Paint (largestContentfulPaint) and First Interaction (firstInteraction) PageViewTiming events will now include attributes from the NetworkInformation API  (on compatible browsers) observed on the page.  This includes network type  (networkType), round trip time  (rtt) and downlink  (downlink). Added element identification attributes to LargestContentfulPaint LargestContentfulPaint PageViewTiming events will now include the elementTagName attribute which represents the triggering element's tag name . If the triggering element is an image, the event will also include the elementUrl representing the image URL  if present. Included page view timing data in session trace payload If observed, the agent will now include PageViewTiming events in the session trace waterfall payload. These events will be available in an upcoming update to the session traces UI. Added session trace IDs to harvests If a session trace is active on a page, a session trace ID associated with that trace will now be appended to all subsequent events generated on the page for the linking of session-related datasets downstream. This ID will be appended to any payload that sent after a session trace has been started. PageView events are generated before session traces begin and will not contain this ID and in most cases Initial Page Load BrowserInteraction events complete before a session trace begins and are not guaranteed to contain this ID. Bug fixes Exclude Data URL requests from Ajax events and metrics Previously, XMLHttpRequest and Fetch calls made with Data URLs  could prevent the agent from harvesting data.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1214","eolDate":"2024-01-06"},{"agent":"browser","date":"2021-11-08","downloadLink":null,"version":"1212","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Updated LCP tracking Largest Contentful Paint will now stop being tracked when page visibility changes to hidden. This aligns with the web-vitals  library. Added passive flag to addEventListener calls Using the addEventEventListener without the passive flag for the touchstart event is flagged in Lighthouse. The passive flag is now applied to all addEventListener calls in the agent. Update to Cumulative Layout Shift calculation The CLS calculation has been updated to use session windows in order to align with Google Chrome tooling (Lighthouse, PageSpeed Insights, CrUX). For more information, see the official blog post on web.dev . Bug Fixes Fixed issue with Array.isArray() call Array.isArray() call is not supported on old browsers and can cause a runtime error. This call has been replaced with an alternative that works on older browsers. Fixed issue with null function argument in the addEventListener API When a null value was passed in to the addEventListener API, the agent would report an internal error. This edge case is now being handled. Fixed issue with Ajax deny list There was an edge case where certain ajax calls could have been excluded when they should not have been. This is now handled correctly. Miscellaneous Added support for collecting internal/supportability metrics The agent can now send metrics that capture information about how the agent itself is working internally. Added agent supportability metrics for tracking API usage Added agent supportability metrics for tracking excluded Ajax events","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1212","eolDate":"2023-11-08"},{"agent":"browser","date":"2021-10-06","downloadLink":null,"version":"1211","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements AjaxRequest events for all XHR/fetch requests Previously, XHR/fetch requests were captured as AjaxRequest events only when they were part of a route change. With this change, all requests will be captured as events. This feature can be further configured by specifying which requests should not be collected. Span events are for all XHR/fetch requests Previously, Span events were generated only for XHR/fetch requests that were part of a route change. With this change, all requests will be captured as Spans. Update to Cumulative Layout Shift calculation The CLS calculation has been updated to use session windows in order to align with Google Chrome tooling (Lighthouse, PageSpeed Insights, CrUX). For more information, see the official blog post on web.dev . Bug Fixes Prevent duplicate session trace nodes The agent no longer calls the clearResourceTimings API, which had the potential to affect other scripts from accessing all resources. Instead, it now uses the PerformanceObserver API to collect information about resources.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1211","eolDate":"2023-10-06"},{"agent":"browser","date":"2021-06-30","downloadLink":null,"version":"1210","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements PageHide PageViewTiming events are now accounted for during page unload events PageHide PageViewTiming events are used to query CLS values. In cases where the page was never hidden, inconsistencies would arise because the PageViewTiming event with that type would not be collected.  Now when pageUnload fires, if a pageHide PageViewTiming has not already been set, it will set it to the time of unload. Perfect Cumulative Layout Scores (CLS) are now recorded as 0 Perfect CLS scores were being ignored, because a score was only recorded when content shifted.  This change reports perfect scores as 0, fixing inconsistent CLS queries. Record fetch calls as metrics Fetch calls are currently only recorded as AjaxRequest events with SPA browser interactions. This change records fetch calls as AJAX metrics, which will make them visible in the AJAX UI charts.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1210","eolDate":"2023-06-30"},{"agent":"browser","date":"2021-05-26","downloadLink":null,"version":"1209","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Doubled the limit of PageAction events per harvest Up to 120 PageAction events can be harvested every 30 seconds. Removed call to /ping endpoint Removed a legacy behavior used to ensure network connection was kept alive in IE 7/8/9. Bug Fixes Prevent duplicate session trace nodes The final Session Trace node in a harvest, captured using the Resource Timing API, is no longer duplicated in the subsequent harvest. This issue lead to 1 duplicate node in a Session Trace, every 10 seconds, over the duration of the trace. Memory overhead when agent script Fixed a memory leak in the agent when the network request to load the second part of the agent is blocked. Update to file protocol restriction Fixed an error thrown in the console when the agent is loaded using the file:// protocol caused by features in the agent trying to run when others had been aborted. setTimeouts without callback functions Fixed an issue where route change Browser Interactions would wait forever if a setTimeout was called without a callback function (passing code in as a string in the first argument ) as the first argument. Cypress.io Fixed a conflict between the Browser agent and the Cypress.io test framework when instrumenting XMLHttpRequest.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1209","eolDate":"2023-05-26"},{"agent":"browser","date":"2021-03-11","downloadLink":null,"version":"1208","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Retry harvest network requests The agent retries harvest XHR requests when it receives 408, 429, 500 or 503 response codes. Additionally, includes a security update to address NR21-01 . File protocol disallowed The agent will not report any data when it is on a page opened from a local file.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1208","eolDate":"2023-03-11"},{"agent":"browser","date":"2021-02-01","downloadLink":null,"version":"1198","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Updated mechanism for collecting data The agent now sends JS errors and AJAX metrics data as body of a standard XHR request. This makes it possible to send more data than the maximum allowed length of URL query string.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1198","eolDate":"2023-02-01"},{"agent":"browser","date":"2021-01-11","downloadLink":null,"version":"1194","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Optimized instrumentation of promises The promise instrumentation has been updated to reduce performance overhead on web sites that use large number of promises. Issue Resolutions Fixed issue with SPA overhead In a rare case where large number of callbacks are executed at the end of an interaction, the agent could cause a significant overhead. This has been fixed in this version of the agent. Fixed issue with Fetch instrumentation Updated fetch instrumentation to account for cases when the function argument is a URL object.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1194","eolDate":"2023-01-11"},{"agent":"browser","date":"2020-09-30","downloadLink":null,"version":"1184","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added support for custom attributes on PageViewTiming events Custom attributes created using the setCustomAttribute API method  will now be included in all PageViewTiming events . Issue Resolutions [SPA- BrowserInteractions] Fixed an issue resulting from too many fetch requests Resolved a bug throwing a null reference error during browser interactions where more than 128 fetch requests were recorded and distributed tracing was enabled. [PageViewTiming] Fixed an edge-case issue with the paint timing instrumentation In cases when nothing was painted to screen before the load event, the agent would throw an error. We have added a guard for this scenario. [PageViewTiming] Fixed issue with Largest Contentful Paint recording The browser agent stops recording largest contentful paint after 60 seconds on a page. We fixed an issue where recording continued beyond that threshold. How to upgrade your agent For instructions for upgrading your agent, please view our docs .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1184","eolDate":"2023-09-30"},{"agent":"browser","date":"2020-08-18","downloadLink":null,"version":"1177","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features We are excited to announce the release of Cumulative Layout Shift , the third and final metric in Google's Core Web Vitals . This metric is an important, user-centric metric for measuring visual stability because it helps quantify how often users experience unexpected layout shifts—a low CLS helps ensure that the page is delightful. The current set for 2020 Core Web Vitals focuses on three aspects of the user experience—loading, interactivity, and visual stability—and includes the following metrics (and their respective thresholds): Largest Contentful Paint (LCP): measures loading performance. To provide a good user experience, LCP should occur within 2.5 seconds of when the page first starts loading. First Input Delay (FID): measures interactivity. To provide a good user experience, pages should have a FID of less than 100 milliseconds. Cumulative Layout Shift (CLS): measures visual stability. To provide a good user experience, pages should maintain a CLS of less than 0.1. For each of the above metrics, to ensure you're hitting the recommended target for most of your users, a good threshold to measure is the 75th percentile of page loads, segmented across mobile and desktop devices. To learn more about the research and methodology behind these recommendations, see: Defining the Core Web Vitals metrics thresholds . Tools that assess Core Web Vitals compliance should consider a page passing if it meets the recommended targets at the 75th percentile for all of the above three metrics. How does the Browser Agent report this data? The agent now collects CLS (Cumulative Layout Shift) values as attributes on PageViewTiming events. CLS measures how much layout of the page shifts and is represented as a score. All types of PageViewTiming events (except FP and FCP) include this attribute, showing the score up until the point the timing measurement was taken. You can now track your CLS score throughout the page loading cycle to better understand and focus your optimization work on the moment in time where you are experiencing the worst scores. We have also added two new events to the PageViewTiming event, pageHide and windowLoad to complete the full page load journey. These timings are useful with its CLS (Cumulative Layout Shift) attribute to paint the picture of a user's journey through the load experience. The pageHide  event represents the first time that the page was hidden (e.g. by switching browser tab). Note that we only collect the first pageHide events at this point. The windowLoad  event is fired when the whole page has loaded, including all dependent resources such as stylesheets and images. For more information, please visit our docs on the PageViewTiming event . Issue Fixes [PageViewTiming event] Fixed unrealistic high values for FI & FID Older browsers report Event.timeStamp as an epoch time instead of value relative to the page navigation start. The agent took this into account for FI (First Interaction) timing values but not for FID (First Input Delay). With this fix, there should no longer be unrealistic outlier values for FID. How to upgrade your agent For instructions for upgrading your agent, please view our docs .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1177","eolDate":"2023-08-18"},{"agent":"browser","date":"2020-07-29","downloadLink":null,"version":"1173","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Browser in distributed tracing  now supports W3C trace context headers. W3C Trace Context  is a standard that makes distributed tracing easier to implement, more reliable, and ultimately more valuable for developers working with modern, highly distributed applications. The standard greatly simplifies use cases where developers instrument services using tools from different distributed tracing solutions. Now all tracers and agents that conform to the W3C Trace Context standard can participate in a trace. Trace data can be propagated from the root service all the way to the terminal service. Once Distributed Tracing is turned on in your Browser Application Settings page, the trace context headers will be added by default, along with the newrelic proprietary header, for same origin AJAX requests. If your system is fully configured to send w3c trace context throughout all services, you can choose to disable the newrelic header from the Application setting tab. For cross origin AJAX requests already configured to accept the newrelic header, you can now select the option to send the W3C trace context headers. When selected, all origins defined must be configured to accept the traceparent and tracestate headers. For information on configuring CORS headers , please see our docs page for an example. As with the same origin requests, if you system is fully configured for W3C trace context headers, you can choose to disable the newrelic header. For more information, please see our New Relic Support for W3C Trace Context  blog post. The following New Relic agents now support W3C: Browser Pro+SPA agent 1173 and higher Java 5.1.0 and higher Python 5.5 and higher Go 3.1.0 and higher Node.js 6.4 and higher Ruby 6.9.0 and higher PHP 9.8 and higher .NET 8.27 and higher","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1173","eolDate":"2023-07-29"},{"agent":"browser","date":"2020-05-22","downloadLink":null,"version":"1169","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Privacy: Added the ability for admin users to toggle cookie collection On/Off via Browser Application Settings UI The agent now accepts new configuration privacy.cookies_enabled. When it is set to false (OFF), the agent doesn't write any third party cookies (JSESSIONID  & NREUM ) and it also notifies the intake server to not return a third party cookie. By default, all current and newly created applications will have this value set to true (ON), so there will be no change in the data currently being collected by the agent. Admin users must toggle the setting to OFF and redeploy the agent in order to see this change take effect. Once cookie collection is set to false, users should no longer see session information captured with their event data. If a session was already in progress, that data will continue to be collected until that session expires. New sessions should report a null value. Please note that auto-injected apps will receive this update before the UI option is available. See release dates below. To learn more about how New Relic Browser uses cookies, see our documentation . For more information on security considerations, specifically around cookies, visit our Security for Browser documentation . Release Dates Auto-injected apps - May 28, 2020 Copy/paste apps - June 1, 2020 Corresponding UI changes - June 1, 2020 Issues Resolved Fixed issue with document XHR requests In some cases, the agent was causing a DOMException error when getting the size of XHR responses for requests with document response type.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1169","eolDate":"2023-05-22"},{"agent":"browser","date":"2020-02-07","downloadLink":null,"version":"1167","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Issue Resolution Resolved a bug that caused a script error when the windowUnload event fired. This issue affected only Internet Explorer prior to version 9.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1167","eolDate":"2023-02-07"},{"agent":"browser","date":"2020-02-05","downloadLink":null,"version":"1163","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features With this release of the New Relic Browser agent, we now support new metrics, largestContentfulPaint and windowUnload, in our PageViewTiming event. With the release of Chrome 77, Google now reports a metric called largest contentful paint . This metric, LCP for short, reports the render time of the largest content element visible in the viewport, along with the element size and element Id values. This new metric comes after extensive research by Google . They found that the more accurate way to measure when the main content of a page is loaded is to look at when the largest element was rendered. Largest Contentful Paint is replacing First Meaningful Paint (which is now a deprecated metric) in Google Lighthouse as well. Additionally, LCP is considered the \"field\" equivalent to the Speed Index \"lab\" metric. Largest Contentful Paint is updated over time, but captured and reported when one of these three criteria is met: A user interacts with the page, thus potentially changing the content in the viewport The user closes the page (the window unload event fires) If no other other interaction happens, and we have received a LCP value, we will report that value after 1 minute has passed If we have not received a value, and no interaction has occurred after a minute, we will simply wait until we have received any value for LCP. This would only occur for very high values (> 1minute) of LCP. In addition to this metric, we added the windowUnload  event to PageViewTiming, so you can see when your users are most commonly closing their sessions. This metric is supported by all browsers on both desktop and mobile devices. For more information about these new metrics, supporting attributes and browser compatibility, visit our PageViewTiming documentation. Issue Fixes Fix to resolve repeated InvalidStateError errors associated with IE11 and some Edge versions. How to upgrade To upgrade your agent to the latest version, see Upgrade the Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1163","eolDate":"2023-02-05"},{"agent":"browser","date":"2019-12-19","downloadLink":null,"version":"1158","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This agent release includes functionality to support the addition of cross-origin resource sharing (CORS) for Browser's distributed tracing feature. This agent will be rolled out prior to the feature availability in the UI. Please note that the Browser-distributed-tracing feature is only supported with our Browser Pro + SPA agent. Full feature availability delivered on Jan. 2, 2019. Agent release schedule Browser distributed tracing CORS support APM auto-injected agents: 12/19/2019 Copy/Paste agent: 12/30/2019 Distributed tracing for cross-origin AJAX calls The agent can now add the newrelic distributed tracing header to outgoing cross-origin AJAX calls. The origins that the agent should add headers to must be defined in the distributed_tracing.allowed_origins configuration section. Users can now enable CORS from the Browser 'Application settings' page. For complete feature documentation, visit the Enable cross-origin resource sharing (CORS)  section of our Browser data in distributed tracing  documentation.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1158","eolDate":"2022-12-19"},{"agent":"browser","date":"2019-11-08","downloadLink":null,"version":"1153","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Support for End User Originated Spans in Distributed Tracing New Relic now supports end-to-end distributed tracing with this release. For our Browser & APM Pro customers, you can now enable the Browser spans for any app that uses our Browser Pro + SPA agent.This MVP includes support for same-origin AJAX requests that originate during a BrowserInteraction event. This AJAX request will be listed as the root entry span for a trace. Learn More For more details about APM & Browser agent version requirements and enablement, see our Browser Data in Distributed Tracing Page . Please note that not all APM agents are supported at this time. For more details about all supported Span attributes, visit our Event Data Dictionary Known Issues Enabling Browser in Distributed Tracing for use with current versions of these language agents, Java, PHP, and C, will result in disconnected traces (single span traces for all Browser requests) and potentially the loss of APM transaction traces and spans. Please see the APM compatibility requirements  for supported versions and estimated release dates. New PageViewTiming Event to capture User Centric Perceived Performance metrics in real time With this release, we are tying together the visual and responsiveness performance for our customer's site. With every page view, the agent is now capturing the time of the first interaction along with FID (First Input Delay). The existing paint timing metrics (First Paint and First Contentful Paint) are now collected even when they occur after the load event. All of these new metrics are captured on the new PageViewTiming events, available in Insights. This new event type is available for all agents, but requires a Browser Pro subscription . Visit our New Relic Event Data Dictionary for a list of attributes and more details about the PageViewTiming event . First Interaction First Interaction timing captures the moment in time that a user first engages with a site. Within this timing, we also capture the type of interaction (click, key, mousedown, etc). This timing represents the first step in calculating the First Input Delay, which is the time from First Interaction to the moment that the site responds (is interactive). First Input Delay FID is a metric that tracks the delay between the time a user can attempt to interact with a part of the site (for example, when they click a link, tap on a button, or use a custom, JavaScript-powered control), and the time that the interface is able to respond to that interaction. We have all experienced situations where a webpage has visibly loaded, but when we try to click around on buttons or any JavaScript-powered interactive elements, nothing responds. This delay is what the FID metric tracks. The FID metric  is in some ways an intersection of the First Contentful Paint and Time to Interactive metrics. It lies in the middle of those two points, measuring the time between the FCP (and therefore when a first input can be made) and when the browser’s main thread is able to respond to any interactions. One major point of FID that differentiates it from Time to Interactive is that it requires  a user to interact! TTI can be calculated without user input, so it is somewhat less powerful in the sense that it isn't providing any new information about my user's active experience or frustration, we can only assume that slow = bad. Why only consider the first input Learn more For more information and query examples, see our PageViewTiming event documentation . For more information about the Paint Timing browser compatibility, see the Browser compatibility and requirements documentation . For more information about User-Centric Perceived Performance metrics, visit the Google Developers Web Fundamentals Guides on Performance . For more information about the difference between FID and TTI, see When Users Click: Tracking First Input Delay Improvements Browser interactions now wait on external scripts to finish loading : Browser interactions measure the time of all Javascript code that runs as a result of an interaction. The agent now includes the time it takes to load and execute external scripts. This is useful, for example, when the code started by an interaction must be loaded first (lazy loading). How to upgrade To upgrade your agent to the latest version, see Upgrade the Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1153","eolDate":"2022-11-08"},{"agent":"browser","date":"2019-07-16","downloadLink":null,"version":"1130","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features First Paint and First Contentful Paint values are now being collected:  For browsers that support the Paint Timing API , these two values are now collected and made available as attributes on the PageView and BrowserInteraction (initial load) events. Definitions for each attribute in BrowserInteractions and PageViews are available in the New Relic event data dictionary . For more information about the Paint Timing browser compatibility, see the Browser compatibility and requirements documentation . For more information about User-Centric Perceived Performance metrics, visit the Google Developers Web Fundamentals Guides on Performance . Read more on our New Relic blog . Improvements Updated instrumentation of the History API:  The history API methods are now instrumented on the History object constructor. This is to ensure that our instrumentation does not override other libraries that wrap these methods. Updated instrumentation of DOM API methods:  The DOM API methods used for JSONP instrumentation are now instrumented on the Node object prototype (as opposed to HTMLElement lower in the prototype chain). This is to ensure that our instrumentation does not override other libraries that wrap these methods. How to upgrade To upgrade your agent to the latest version, see Upgrade the Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1130","eolDate":"2022-07-16"},{"agent":"browser","date":"2019-04-19","downloadLink":null,"version":"1123","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed issue with capturing AJAX status code in Angular apps:  Angular calls abort() on the XHR object after it successfully finishes. This was seen by our instrumentation as a call that did not finish, and as a result status code was set to 0 and reported as a network error. This fix addresses this use case by capturing status code before the call is aborted.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1123","eolDate":"2022-04-19"},{"agent":"browser","date":"2019-01-04","downloadLink":null,"version":"1118","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Custom attributes are now added to JavascriptError events:  Custom attributes collected with the setCustomAttribute()  and interaction.setAttribute()  API methods are now added to JavascriptError events. Updated the noticeError() API:  The noticeError() API method now accepts a second argument for custom attributes. For more details and examples, see the noticeError() documentation . Improvements Updated the timing of when page URL is collected:  The URL collected by the agent and used for page view names is now collected after the load event to account for redirects. Currently, we are using the referrer header value from the initial agent call for transaction naming and for URL attributes on Insights events. The agent also sends the URL value as a part of its payload to get around HTTP header stripping. This update brings this value on a par with the HTTP header by capturing it at the time the agent call is made. How to upgrade To upgrade your agent to the latest version, see Upgrade the Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1118","eolDate":"2022-01-04"},{"agent":"browser","date":"2018-10-04","downloadLink":null,"version":"1099","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The Browser agent, sometimes called the JavaScript agent, has multiple variants: Lite, Pro, and Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent. New features Action Text:  The agent now captures the text of the HTML element that was clicked when a browser interaction started. This value is stored as an attribute called actionText on the BrowserInteraction events. There is also a new API actionText , which can be used to manually set the action text value. Bug fixes The agent now uses a fallback method for collecting data when sendBeacon fails:  Browsers can return false from sendBeacon call when it cannot be completed. The agent now detects it and falls back to a different method to ensure data is captured. Fixed calculating stackHash value in Safari 10 and 11:  The stackHash value was not being properly calculated for global errors in Safari 10 and 11, causing incorrect grouping of errors across all browsers. Fixed issue with calling fetch without any arguments:  On certain versions of the Safari browser, calling fetch without any arguments is permitted. Other browsers, in contrast, do not allow this and throw an error. This also prevented the agent from working properly. Removed response size calculation for streaming fetch calls:  Previously, the agent cloned the response of a fetch call and read the response body in order to capture its size. In certain versions of the Safari browser this caused other clone calls to fail. As a result, the agent now only uses the content-length header, when available, to capture response size. How to upgrade To upgrade your agent to the latest version, see Upgrade the Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1099","eolDate":"2021-10-04"},{"agent":"browser","date":"2017-12-04","downloadLink":null,"version":"1071","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The Browser agent, sometimes called the JavaScript agent, has multiple variants: Lite, Pro, and Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent. New features Link JS Errors to Browser Interactions (relevant only for PRO+SPA):  When a JS error occurs inside a browser interaction event, the error will now be associated with the interaction via Insights attributes. BrowserInteraction, AjaxRequest, and BrowserTiming events will now have the following attributes: browserInteractionId, eventId, and parentEventId. Bug fixes JSONP Tracking Breaks in some versions of Safari (relevant only for PRO+SPA):  Previously, the agent would cause Safari browsers to lock up when JSONP requests returned large data. The agent no longer calculates JSONP response size. How to upgrade To upgrade your agent to the latest version, see Upgrade the Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1071","eolDate":"2020-12-04"},{"agent":"browser","date":"2017-10-02","downloadLink":null,"version":"1059","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This Browser agent version has been temporarily removed; the most up-to-date version is currently agent version 1044 . The Browser agent, sometimes called the JavaScript agent, has multiple variants: Lite, Pro, and Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent. New features Added JSONP support (relevant only for PRO+SPA):  Browser Interactions that include JSONP requests are now correctly tracked. Previously, browser interactions that included JSONP were ended early and not included in the Breakdowns tab. Bug fixes Fixed a compatibility issue with zone.js:  When New Relic and Zone.js v0.8.13 were used together, the context (this) was not being set correctly in some of the addEventListener calls used by clients. Correctly send data when methods aren't wrappable:  When XHR was not wrappable, the agent did not send data to the collector via XHR in some edge cases. We are now correctly sending the data if XHR exists on the page, even if it's not wrappable. How to upgrade To upgrade your agent to the latest version, see Upgrade the Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1059","eolDate":"2020-10-02"},{"agent":"browser","date":"2017-07-17","downloadLink":null,"version":"1044","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The Browser Agent, sometimes called the JS agent, has multiple variants: Lite, Pro, and Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent. Bug fixes Improved Agent Performance:  Improvements to how the agent verifies interactions are complete by setting and clearing multiple timers. Previously, the agent would make many unnecessary calls to clearTimeout, and will now only clear timers when appropriate. Protect against custom events:  Improvements to how the agent determines the event origin for Session Traces. In some libraries that use custom event wrappers, when the agent calls target on an event it can throw an exception. The agent now catches these types of exceptions when building Session Traces. How to upgrade To upgrade your agent to the latest version, see Upgrade the Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1044","eolDate":"2020-07-17"},{"agent":"browser","date":"2017-06-22","downloadLink":null,"version":"1039","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The Browser Agent, sometimes called the JS agent, has multiple variants: Lite, Pro, and Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent. Bug fixes Do not instrument SPA without a wrappable XHR:  In browsers that don't orchestrate the wrapping of XHR, the SPA agent does not collect event data, only metric timeslice data . The agent will still report SPA for browsers that support XHR wrapping. Mobile Safari and a few other browsers didn’t support wrapping the XMLHttpRequest, so they would not produce event data for instrumenting Single Page Apps. They still collect other types of metrics. Support setTimeout with a string duration:  When you call setTimeout with a string as the duration, browsers will cast this as a number, but the agent did not handle this correctly. We are now handling this case correctly. Work around mutation observer memory leak in IE 11:  We have discovered that MutationObserver in IE causes a memory leak, so the agent now will prefer setImmediate for IE, and use a resolved promise to schedule the wrapping in Edge (and other browsers that support promises). Handle short recursive timers:  Some libraries recursively set timers that left our interactions open. The agent now handles this by reducing the max time it will allow to be included in the interaction. How to upgrade To upgrade your agent to the latest version, see Upgrade the Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1039","eolDate":"2020-06-22"},{"agent":"browser","date":"2017-03-20","downloadLink":null,"version":"1026","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The Browser Agent, sometimes called the JS Agent, has multiple variants: Lite, Pro, Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent. Improvements Adjusted PageAction limits:  Previously, we limited PageAction events to 120 per page load and only 20 events per harvest cycle, resulting in dropped data if a user sent more than 20 pageAction events in a single burst. Increasing the harvest time to 30 seconds also increases the event buffer, allowing users to send up to 60 events per harvest. Improved time measurement:  Previously, the agent used the system clock to calculate timing, and since the system clock may shift over the lifecycle of a page, the agent could occasionally report inaccurate or unexpectedly negative values. Going forward, the agent will use perfomance.now(), which is a monotonically increasing clock that starts from navigationStart. This change will result in more accurate timing for modern browsers. Bug fixes Preserve event listeners:  Previously, if the agent doesn't load correctly it affected the functionality of add- and removeEventListener. These will now function the same whether the agent loads or not. How to upgrade To upgrade your agent to the latest version, see Upgrade Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1026","eolDate":"2020-03-20"},{"agent":"browser","date":"2017-01-19","downloadLink":null,"version":"1016","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The Browser Agent, sometimes called the JS Agent, has multiple variants: Lite, Pro, Pro+SPA. Unless noted otherwise, all features/improvements/bug fixes are available in all variants of the agent. New features Release ID API:  A new API allows you to uniquely identify your current JavaScript version, enabling a richer error feature with source maps identification. Stay tuned for more information and documentation! Improvements Passive Scroll Event Listeners:  Previously, the wrapped scroll event listener did not take advantage of an available performance optimization: the passive annotation. By including this annotation, our wrapped scroll listener will allow a non-blocking, smooth scrolling action. Bug fixes XHR With Credentials:  Previously, when the agent would send data using an XHR, it would feature-check the withCredentials property and set it to true if it was available. However, older versions of IE do not allow modification of the withCredentials property on unsent XHRs. The agent now wraps the property assignment in a try/catch block to prevent errors. How to upgrade To upgrade your agent to the latest version, see Upgrade Browser agent .","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1016","eolDate":"2020-01-19"},{"agent":"browser","date":"2026-09-11","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.322.0","features":["Include observer API for SPV events","MFE Manifest","Add registration validation warnings"],"bugs":["Upgrade web-vitals from 4.2.4 to 6.2.1 to plug a listener leak"],"security":[],"supportedOperatingSystems":null,"description":"v1.322.0 Features Include observer API for SPV events Use the ReportingObserver API to catch securitypolicyviolation events that occurred prior to the agent loader execution. In practice, this mainly affects chromium browsers, as existing configs and bugs affect Firefox and Safari collection. MFE Manifest Adds an optional manifest to the register() API so a Micro Frontend can declare its own known assets (scripts, stylesheets, images, fonts), letting the agent accurately attribute errors, logs, AJAX calls, WebSockets, and resource-timing events to it — even for assets loaded by a script other than the one that called register(). An opt-in timingMethod also lets a manifest widen MicroFrontEndTiming fetch/execution windows across its declared assets. Add registration validation warnings Emits local debugging warnings if obvious issues are detected from supplied targets to the register API. Bug fixes Upgrade web-vitals from 4.2.4 to 6.2.1 to plug a listener leak Upgraded the bundled web-vitals library from 4.2.4 to 6.2.1, fixing an unbounded document visibilitychange listener leak: web-vitals 4.x registers a permanent listener on every INP report cycle, so long-lived pages accumulate hundreds of listeners. Also absorbed the v5/v6 attribution API changes the agent is exposed to (the LCPAttribution.element → target rename and newly-optional INP/CLS attribution fields) with no change to the attribute names the agent emits. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. The following features are currently in limited preview and will not receive standard support: Micro frontend (MFE) monitoring  via the register() API BrowserPerformance \"resource\"  type events New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.322.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 142-152, Edge 141-151, Safari 18-27, and Firefox 144-154. For mobile devices, v1.322.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.322.0","eolDate":"2027-09-11"},{"agent":"browser","date":"2026-08-31","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.321.0","features":["MicroFrontEndTiming attributes changes","Add instrumentation to track races between tabs","improve v2 target standardization","Introduce v2 PageView & decouple connect service call"],"bugs":["Ensure Session Replay's custom masker applies to non-inputs"],"security":[],"supportedOperatingSystems":null,"description":"v1.321.0 Features MicroFrontEndTiming attributes changes MicroFrontEndTiming event attribute changes Additions: registerUrl : The URL at the time the MFE was registered deregisterUrl : The URL at the time the MFE was deregistered or the page unloaded vitals.fcp.value : The value of the first contentful paint detected tied to the MFE DOM tree vitals.lcp.value : The value of the largest contentful paint detected tied to the MFE DOM tree vitals.cls.value : The value of the cumulative layout shift detected tied to the MFE DOM tree vitals.inp.value : The value of the interaction to next paint detected tied to the MFE DOM tree Removals: pageUrl currentUrl Add instrumentation to track races between tabs Adds a supportability metric to track a race condition that occurs when another page runs at the same time with an updated session state. improve v2 target standardization Improves agent internals to provide an explicit reference for container agent targets while processing v2 MFE pathway data, rather than relying on side-effect driven undefined target assumptions. Introduce v2 PageView & decouple connect service call The old RUM request responsible for both retrieving app configurations and PageView generation is now split (temporarily under a feature flag). This makes the agent more resilient on problematic connect cycles or unsuccessful config retrieval, and the PageView event would no longer be the dependency blocking other events from harvesting. Bug fixes Ensure Session Replay's custom masker applies to non-inputs Fixed an issue where the custom masker function was not applying to certain element types. The custom masker is applied to elements that are decorated with one of nr-umask CSS class or data-nr-unmask data attribute, allowing a node that would otherwise be masked to be overridden and its text contents exposed. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.321.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 141-151, Edge 141-151, Safari 18-27, and Firefox 143-153. For mobile devices, v1.321.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.321.0","eolDate":"2027-08-31"},{"agent":"browser","date":"2026-08-12","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.320.1","features":[],"bugs":["Avoid obfuscating keys and reserved system vals","Apply hard cap to MFE FCP"],"security":[],"supportedOperatingSystems":null,"description":"v1.320.1 Bug fixes Avoid obfuscating keys and reserved system vals Preserves all keys as well as reserved system values for AjaxRequest and Page View Timing events. Apply hard cap to MFE FCP Fixes an issue where MFE vitals could occasionally report out of bounds FCP/LCP values (e.g. after a browser tab freeze or suspend) instead of being dropped like other stale data. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.320.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 140-150, Edge 140-150, Safari 18-27, and Firefox 142-152. For mobile devices, v1.320.1 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.320.1","eolDate":"2027-08-12"},{"agent":"browser","date":"2026-08-07","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.320.0","features":["Improve ability to apply reasonable caps to MFE vitals","MFE iframe support - Beta Access"],"bugs":["Deduplicate auto-instrumented MFE events"],"security":[],"supportedOperatingSystems":null,"description":"v1.320.0 Features Improve ability to apply reasonable caps to MFE vitals Fixed a bug in the Register API's micro-frontend (MFE) vitals tracking where a script's timing correlation could be reused after it went stale, causing First Contentful Paint (and other vitals) to be misreported as up to several seconds slower than they actually were for MFEs that remount without their underlying script reloading (e.g. in single-page applications). MFE iframe support - Beta Access Adds an interface for capturing MFE data encapsulated in an iFrame.  This is experimental, is subject to change or total removal and should not be used in a production environment until GA status has been reached Bug fixes Deduplicate auto-instrumented MFE events Fixes duplicate reporting of auto-instrumented events (AJAX requests, JS errors, console logs, WebSocket activity etc.) when a micro-frontend is registered with the register() API multiple times. Previously, a single auto-instrumented event originating from a repeatedly-registered MFE script would be reported once per registration — Auto-detected events are now collapsed to a single report per real occurrence when they resolve to the same underlying script and the same registered MFE id. Explicit API-driven calls (.addPageAction(), .log(), .noticeError(), etc.) and MicroFrontEndTiming events remain per-registration, as intended, and distinct MFEs that happen to share a script (e.g. two different MFEs registered from the same inline <script> block) continue to be reported independently. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.320.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 140-150, Edge 140-150, Safari 18-27, and Firefox 142-152. For mobile devices, v1.320.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.320.0","eolDate":"2027-08-07"},{"agent":"browser","date":"2026-07-28","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.319.0","features":["MFE vitals improvements","Automatically Detect MFE Web Sockets","Do not obfuscate attribute keys"],"bugs":["Avoid capturing agent AJAX payloads","Keep Ajax payload out of unrelated events"],"security":[],"supportedOperatingSystems":null,"description":"v1.319.0 Features MFE vitals improvements Implement quality of life improvements on the collection of MFE vital timings. If no FCP value is observed within 10 seconds, shut down observers for memory saving and outlier control. Decorate observed DOM trees with the MFE instance ID to facilitate debugging and prevent double-instrumentation of the same DOM tree from multiple instances pointed at the same MFE target. Automatically Detect MFE Web Sockets Add support for automatic Micro Frontend (MFE) attribution of WebSocket events. Previously, WebSocket events were only ever  automatically  captured globally by the container browser application. With this change, the agent cross-compares the call stack signature of the WebSocket method to the call stack signature of the MFE module that registered with the register API.  If the file that is responsible for registering with the browser agent is found in the call stack signature of the WebSocket method being triggered, that event will be attributed to the MFE instead of the container. Do not obfuscate attribute keys Do not obfuscate attribute keys in our addCustomAttributes method for the BEL serializer. This change affects attributes in AjaxRequest, PageViewTiming, and BrowserInteraction (soft nav only) events. Bug fixes Avoid capturing agent AJAX payloads Prevent the AJAX capture_payloads feature from capturing the agent's own telemetry requests (harvests to NR beacon endpoints). Keep Ajax payload out of unrelated events Drops captured AJAX request + payload info from unrelated events (AJAX timeslice metrics, session trace) via a shared params object. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.319.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 139-149, Edge 139-149, Safari 18-27, and Firefox 142-152. For mobile devices, v1.319.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.319.0","eolDate":"2027-07-28"},{"agent":"browser","date":"2026-07-08","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.318.0","features":["Add websocket init config","MFE core web-vitals detection","Improve agent startup"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.318.0 Features Add websocket init config Adds web_sockets block to NREUM init configuration. Setting web_sockets.enabled to true turns on the web sockets feature. The web sockets feature is disabled by default. MFE core web-vitals detection Add internal detection methods for FCP, INP, CLS, and LCP when spawned by a MFE Improve agent startup Provide better support for scenarios where agent startup can be interrupted before RUM call completes successfully and feature session modes are saved into local storage (where applicable). Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.318.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 139-149, Edge 139-149, Safari 18-26, and Firefox 141-151. For mobile devices, v1.318.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.318.0","eolDate":"2027-07-08"},{"agent":"browser","date":"2026-06-18","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.317.0","features":["Detect and report AJAX payloads","Enhance obfuscation to support event filter"],"bugs":["Calculate browser_stack_hash from truncated stack trace","Get responseBodySize from body if content-length is missing","Patch handling of inlining images for Session Replay"],"security":[],"supportedOperatingSystems":null,"description":"v1.317.0 Features Detect and report AJAX payloads Introduces support of AJAX payload capture for XMLHttpRequest and Fetch API calls. When enabled, the browser agent will captures request/response bodies, headers, and query parameters, with automatic detection and parsing of GraphQL operations. Payload capture is configurable to monitor all requests or only failures, with built-in size limits (4KB per attribute) and obfuscation support for sensitive data protection. New AjaxRequest Attributes Payload Capture  - The Browser Agent can now capture and report request and response payloads for AJAX calls, providing deeper insights into network activity and API interactions. Configuration: \r\nEnable payload capture using the ajax.capture_payloads configuration option: 'all' - Capture payloads for all AJAX requests 'failures' - Capture only failed requests (HTTP errors, network errors, or GraphQL errors) none - Disable payload capture (default) New Attributes on AjaxRequest Events: \r\nWhen AJAX payloads are captured, new attributes are automatically included on AjaxRequest events: requestQuery - URL query parameters requestHeaders, responseHeaders - HTTP headers requestBody, responseBody - Request and response payloads (text-based formats only: JSON, XML, GraphQL, plain text) GraphQL Detection: \r\nWhen GraphQL errors are detected, a new additional attribute is automatically included on AjaxRequest events: operationHasErrors - Indicates if the operation returned errors All captured data is automatically truncated to 4KB per attribute and supports obfuscation patterns for sensitive information. Enhance obfuscation to support event filter Obfuscation behavior can now be configured to apply only to a subset of event types, using the eventFilter property, which supports an array of event type strings per obfuscation rule.  When supplied, the obfuscation rule will only be applied when the event type matches one of the items in the eventFilter array. For backwards compatibility, not supplying an eventFilter property on configuration rules will apply the rule to all data. Bug fixes Calculate browser_stack_hash from truncated stack trace Calculate the browser stack hash off of the truncated stack trace instead of the non-truncated stack trace. Before this change, first-occurrence harvests of JSE events can have a different browser stack hash from future harvests of the same stack trace if it was truncated. This will improve error grouping of JavaScriptError events. Get responseBodySize from body if content-length is missing Addresses an issue where AjaxRequest events inaccurately reported a responseSize of 0 or undefined due to a lack of fallback mechanisms and overly restrictive falsy checks. Introduced a fallback mechanism that calculates response sizes from captured payloads for Fetch and XHR requests when the content-length header is missing. Patch handling of inlining images for Session Replay Fixes an issue where Session Replay may leave an image broken in the live DOM.  In this version, the underlying rrweb version will avoid manipulating the live image on the DOM. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.317.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 139-149, Edge 139-149, Safari 18-26, and Firefox 141-151. For mobile devices, v1.317.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.317.0","eolDate":"2027-06-18"},{"agent":"browser","date":"2026-06-01","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.316.0","features":["Use app-namespaced keys for session"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.316.0 Features Use app-namespaced keys for session The browser agent now namespaces the session info to per browser app, using the combination of licenseKey and applicationID provided at startup. This means different apps sharing the same origin and browser localStorage will no longer share the same session, which was an accepted but not ideal collision, causing feature modes to bleed from one over to another for the duration of a session previously. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.316.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.316.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.316.0","eolDate":"2027-06-01"},{"agent":"browser","date":"2026-05-26","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.315.0","features":["Enhance SPA API to support targetPageLoad option"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.315.0 Features Enhance SPA API to support targetPageLoad option Allow the SPA API to target and work on the initialPageLoad type BrowserInteraction event. A new option is added to .interaction that now binds the returned handle to the initial page load interaction at any point in time. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.315.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.315.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.315.0","eolDate":"2027-05-26"},{"agent":"browser","date":"2026-05-04","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.314.0","features":["Add ajaxRequest.id attribute","Improve PageViewTiming load timing capture","Adjust timestamps for clock skew due to machine sleep","Automatically Detect MFE User Actions","Allow Session Replay to retry payloads"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.314.0 Features Add ajaxRequest.id attribute Adds a unique identifier to all AjaxRequest events to facilitate direct queries and drilling-down into data in NR1 UIs. Improve PageViewTiming load timing capture The load timing is now more reliably captured for pages, inheriting the idea from web-vital's onTTFB. Before, it occasionally missed loadEventEnd from nav entry from a browser race condition, particularly for larger/longer-loaded pages, which caused load to be 0. Adjust timestamps for clock skew due to machine sleep Certain linux and apple hardware can freeze the performance API clocks when entering deep sleep, which can cause inaccurate timestamps on New Relic events upon awakening. This introduces a new change which attempts to correct clock skew caused by frozen machines. Automatically Detect MFE User Actions Add support for automatic Micro Frontend (MFE) attribution of UserAction events via a data-nr-mfe-id data attribute. Previously, UserAction events were only ever captured globally by the container browser application. With this change, the agent now performs a parental chain lookup for elements associated with the action, identified by the data-nr-mfe-id attribute. To associate UserAction events with a registered MFE, add a data-nr-mfe-id at the root DOM node controlled by your MFE package that matches the ID supplied to the register API. Allow Session Replay to retry payloads Payloads failed with retryable codes will be re-harvested by the agent. Further session replay data will not be collected until the harvest retries successfully. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.314.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.314.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.314.0","eolDate":"2027-05-04"},{"agent":"browser","date":"2026-04-21","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.313.1","features":[],"bugs":["Fix method names for MFE methods"],"security":[],"supportedOperatingSystems":null,"description":"v1.313.1 Bug fixes Fix method names for MFE methods Fixes MFE method names which could be minified and unable to be internally tracked for improvements. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.313.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.313.1 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.313.1","eolDate":"2027-04-21"},{"agent":"browser","date":"2026-04-14","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.313.0","features":["Automatically Detect MFE Errors","remove \"withCredentials\"","Improve MicroFrontEndTiming heuristics","Report CSP violations as new events","Apply legal and compliance requirements to register API"],"bugs":["Bad `trace.lastTimestamp` in Safari + back nav edge case"],"security":[],"supportedOperatingSystems":null,"description":"v1.313.0 Features Automatically Detect MFE Errors Add support for automatic Micro Frontend (MFE) attribution of JavaScriptError events. Previously, JavaScriptError events were only ever captured globally by the container browser application. With this change, the agent cross-compares the stack trace of the thrown Error instance to the call stack signature of the MFE module that registered with the register API.  If the file that is responsible for registering with the browser agent is found in the stack trace of the thrown Error instance, that event will be attributed to the MFE instead of the container. remove \"withCredentials\" Remove all usage of withCredentials or credentials: 'include' from agent harvests, as cookies have not been used in the agent since before v1220 . Improve MicroFrontEndTiming heuristics Improve the ability to detect script execution times for MFE, leading to more accurate timeToLoad metrics. Report CSP violations as new events Content Security Policy (CSP) violations bubbled up are now captured and reported as a new SecurityPolicyViolation event type to Page Insight consumer. They become query-able through NRQL. Apply legal and compliance requirements to register API Ensure the register API complies to company requirements before exposing for limited preview. Bug fixes Bad trace.lastTimestamp in Safari + back nav edge case Fixes a race condition where Safari browser's back navigation (BFCache) could cause absolute timestamps to be recorded at the start of the session trace feature, resulting in an abnormal trace.lastTimestamp value and a mix of relative and absolute timestamps in a single payload. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.313.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.313.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.313.0","eolDate":"2027-04-14"},{"agent":"browser","date":"2026-04-02","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.312.1","features":[],"bugs":[".at causes issues in older browsers"],"security":[],"supportedOperatingSystems":null,"description":"v1.312.1 Bug fixes .at causes issues in older browsers .at() is not being properly transpiled and causing initialization issues, switched to indexing. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.312.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.312.1 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.312.1","eolDate":"2027-04-02"},{"agent":"browser","date":"2026-03-30","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.312.0","features":["Automatically Detect MFE Logs","Automatically Detect MFE AJAX"],"bugs":["Session replays not working for Angular app running on Safari","Revert circular replacer"],"security":[],"supportedOperatingSystems":null,"description":"v1.312.0 Features Automatically Detect MFE Logs Add support for automatic Micro Frontend (MFE) attribution of Log events. Previously, Log events were only ever  automatically  captured globally by the container browser application. With this change, the agent cross-compares the call stack signature of the given log method (such as console.log, console.info, etc.) to the call stack signature of the MFE module that registered with the register API.  If the file that is responsible for registering with the browser agent is found in the call stack signature of the log method being triggered, that event will be attributed to the MFE instead of the container. Automatically Detect MFE AJAX Add support for automatic Micro Frontend (MFE) attribution of AjaxRequest events. Previously, AjaxRequest events were only ever captured globally by the container browser application. With this change, the agent cross-compares the call stack signature of the AJAX call to the call stack signature of the MFE module that registered with the register API.  If the file that is responsible for registering with the browser agent is found in the call stack signature of the AJAX request being triggered, that event will be attributed to the MFE instead of the container. Bug fixes Session replays not working for Angular app running on Safari Fixes an issue where session replays would fail to capture any recordings beyond an initial snapshot for Angular apps running on Safari. Revert circular replacer The circular replacer method applied to JSON.stringify operations was seen to cause lag in niche cases with deeply complex and nested objects emitted in quick succession such as in scroll event handlers.  This method was revert back to a faster simpler operation to decrease performance bottlenecks. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.312.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.312.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.312.0","eolDate":"2027-03-30"},{"agent":"browser","date":"2026-03-20","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.311.0","features":["agentIdentifier removal","Attribute original page URL to all PageViewTiming nodes","improve MFE timing logic"],"bugs":["Enforce string IDs for new MFE registrations","Circular replacer removed reused objects from harvests","Update RegExp to prevent un-minimized webpack build issue"],"security":[],"supportedOperatingSystems":null,"description":"v1.311.0 Features agentIdentifier removal Removed scoped references by agent identifier to simplify the agent architecture. All references are now stored directly within the agent reference, eliminating the need to blend agent references with scoped objects via lookup keys. Attribute original page URL to all PageViewTiming nodes Expanded pageUrl attribution to all timings, building on previous work for LCP. PageViewTiming events now report the original hard navigation URL for all node types, ensuring data consistency for SPA even if the URL changes before harvest. improve MFE timing logic Enhanced the agent's ability to identify the correct MFE script calling the register API. This improvement results in more accurate timing information for MFE environments. Bug fixes Enforce string IDs for new MFE registrations Resolved an issue where non-string IDs caused errors during MFE entity synthesis. The agent now enforces string-based IDs and issues a warning if a different data type is provided. Circular replacer removed reused objects from harvests Fixed an issue where the internal stringify method removed shared pointers across harvest payloads, which occasionally caused missing params attributes on error harvests. Update RegExp to prevent un-minimized webpack build issue Replaced the $ character with its hexadecimal equivalent in regular expressions. This prevents Webpack from incorrectly replacing the character during the build process, which previously caused agent failures in unminimized builds. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.311.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 134-144, Edge 134-144, Safari 18-26, and Firefox 137-147. For mobile devices, v1.311.0 was built and tested for Android OS 16 and iOS Safari 18-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.311.0","eolDate":"2027-03-20"},{"agent":"browser","date":"2026-02-19","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.310.1","features":[],"bugs":["Enhance LCP entry with fallback attribution values"],"security":[],"supportedOperatingSystems":null,"description":"v1.310.1 Bug fixes Enhance LCP entry with fallback attribution values In cases wherein LCP is reported with no attribution entry from web-vitals, the agent will now pass on other default provided attributes such as timeToFirstByte instead of ignoring them. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.310.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 134-144, Edge 134-144, Safari 18-26, and Firefox 137-147. For mobile devices, v1.310.1 was built and tested for Android OS 16 and iOS Safari 18-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.310.1","eolDate":"2027-02-19"},{"agent":"browser","date":"2026-02-17","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.310.0","features":["better MFE timing handling","Removing old SPA feature & related wrappings entirely","Capture MFE timings as MicroFrontEndTiming Events"],"bugs":["Update measure API types"],"security":[],"supportedOperatingSystems":null,"description":"v1.310.0 Features better MFE timing handling Improve the detection of script assets reported by the browser which power the MicroFrontEndTiming event's timeToFetch and timeToBeRequested attributes. This change also includes new assetUrl and assetType attributes to better illustrate the assets used to populate the timing data. Removing old SPA feature & related wrappings entirely This concludes the complete removal of the old SPA feature that is replaced by Soft Navigations feature. Since agent version 1.307.0, the default \"SPA\" was already switched over, so no breaking changes from this version are expected. Capture MFE timings as MicroFrontEndTiming Events Captures the lifecycle timings of registered entities in preparation for future micro front end product Bug fixes Update measure API types Corrects an issue where the typings associated with the measure API did not accept PerformanceMark as a valid input for start or end values. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.310.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 134-144, Edge 134-144, Safari 17-26, and Firefox 137-147. For mobile devices, v1.310.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.310.0","eolDate":"2027-02-17"},{"agent":"browser","date":"2026-02-03","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.309.0","features":["Warn when more than one agent is running","Improve MFE tag setting","Add WebDriver detection attribute to PageView & PageViewTiming"],"bugs":["Micro agent duplicate handlers","allow child registrations from blocked parents"],"security":[],"supportedOperatingSystems":null,"description":"v1.309.0 Features Warn when more than one agent is running Added a console warning when more than one Browser agent is running on the page. Improve MFE tag setting Enforce tags to be set for micro frontends by supplying an object of key-value pairs to the tags argument of the register(...) API.  This allows for tags to be specified with an explicit value instead of only supporting boolean tags. Add WebDriver detection attribute to PageView & PageViewTiming PageView, PageViewTiming and initialPageLoad-category BrowserInteraction events will now report a webdriverDetected property corresponding to the navigator.webdriver set by the browser. Bug fixes Micro agent duplicate handlers Fixes when micro agents are created in a staggered fashion, handlers for each agent is multiplied by the number of agents that follow.  For example if there were two agents, the handlers for the first agent was registered twice.  This had the effect of duplicating events + contents of harvest payloads. allow child registrations from blocked parents Allow blocked parent entities to still instantiate a child MFE when registering Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.309.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 136-146. For mobile devices, v1.309.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.309.0","eolDate":"2027-02-03"},{"agent":"browser","date":"2026-01-08","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.308.0","features":["add support for mfe tags with the register API","add child.id attribute to facilitate MFE cross-linking","Add \"deregister\" API","add parent.type attribute to facilitate relationship synthesis","Add default close reason"],"bugs":["enforce non-null values on the numeric fields","Clean WebSocket URLs"],"security":[],"supportedOperatingSystems":null,"description":"v1.308.0 Features add support for mfe tags with the register API Adds support for adding entity tags through the usage of the register API add child.id attribute to facilitate MFE cross-linking Adds a child.id attribute to duplicated data to facilitate future cross-linking in the UI Add \"deregister\" API Adds support for deregistering a registered entity, for use with the upcoming Micro Front End support initiative. add parent.type attribute to facilitate relationship synthesis Adds the required parent.type attribute for future relationship synthesis during MFE ingest. Add default close reason Add a default close reason of unknown to WebSocket events whose close reason could not be determined. Bug fixes enforce non-null values on the numeric fields Ensure that numeric fields are always reported on WebSocket events by defaulting to 0 instead of undefined Clean WebSocket URLs Remove hash fragments and query params from URLs reported on WebSocket events Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.308.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 136-146. For mobile devices, v1.308.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.308.0","eolDate":"2027-01-08"},{"agent":"browser","date":"2026-01-06","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.307.0","features":["Make soft navigations feature the default SPA","Add resetSession option to setUserId() API","Ajax deny list wildcard support"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.307.0 Features Make soft navigations feature the default SPA Soft navigations feature is now the enforced running feature for SPA. The older and deprecated SPA feature cannot be selected or used as of this update. Add resetSession option to setUserId() API Introduces option to reset the browser agent session when updating a userid via the setUserId() API. Ajax deny list wildcard support Adds wildcard character support, with the * character, to the AJAX deny list feature which allows to substitute one or more characters in your deny list filters. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.307.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 136-146. For mobile devices, v1.307.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.307.0","eolDate":"2027-01-06"},{"agent":"browser","date":"2025-12-16","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.306.0","features":["Control log API through separate RUM flag","Ensure responseStart is valid before relying on onTTFB"],"bugs":["Remove linebreak syntax from webpack output"],"security":[],"supportedOperatingSystems":null,"description":"v1.306.0 Features Control log API through separate RUM flag Logs captured by the newrelic.log method will now be configurable through settings and controlled separately from wrapped logs. This allows one to be disabled without affecting the other, as in the case that only newrelic.log is desired and not auto instrumented console. Ensure responseStart is valid before relying on onTTFB Adds an extra validation step to ensure that responseStart of the nav timing entry is valid before relying on onTTFB to return valid data.  The web-vitals library depends on that value to operate correctly, and without a valid TTFB response, the agent will not send the RUM call.  This change ensures that fallback measures are taken when responseStart is invalid, to ensure a RUM call is sent more reliably, which helps compatibility with unsupported frameworks such as ElectronJS. Bug fixes Remove linebreak syntax from webpack output Removes the newline character in webpack output to avoid issues with copy-pasting our script as a string inside code. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.306.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 135-145. For mobile devices, v1.306.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.306.0","eolDate":"2026-12-16"},{"agent":"browser","date":"2025-12-10","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.305.0","features":["Improve agent compatibility with ChatGPT connector apps","Enable user frustrations for Pro/SPA agents"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.305.0 Features Improve agent compatibility with ChatGPT connector apps Small tweaks were made to the agent to allow for better compatibility with the unique iframe constraints of ChatGPT connector applications. Enable user frustrations for Pro/SPA agents Officially releases dead click and error click detections for interactive elements to Pro and SPA agents. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.305.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 132-142, Edge 132-142, Safari 17-26, and Firefox 135-145. For mobile devices, v1.305.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.305.0","eolDate":"2026-12-10"},{"agent":"browser","date":"2025-12-03","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.304.0","features":["Warn message on session reset","Reduce Session Replay snapshot sizes"],"bugs":["Observe document.body after document is interactive"],"security":[],"supportedOperatingSystems":null,"description":"v1.304.0 Features Warn message on session reset Adds a warning code when an agent session reset happens so that we have better debugging on browser transition behavior. Reduce Session Replay snapshot sizes Use slimDOMOption = 'all' by default to reduce session replay snapshot payload sizes. Bug fixes Observe document.body after document is interactive Addresses the scenario where MutationObserver.observe() was issued before document.body is available, causing Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'. error. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.304.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 132-142, Edge 132-142, Safari 17-26, and Firefox 134-144. For mobile devices, v1.304.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.304.0","eolDate":"2026-12-03"},{"agent":"browser","date":"2025-11-13","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.303.0","features":["Allow consent API to be invoked without localStorage access","Allow nested registrations","Additional validation to prepare agent for MFE registrations","Add measure support to register API","Add useConsentModel functionality","Retry initial connect call","Add custom event support to register API","SMs for browser connect response"],"bugs":["Obfuscate custom attributes for logs added after PVE","memoize promise context propagation to avoid safari hangs"],"security":[],"supportedOperatingSystems":null,"description":"v1.303.0 Features Allow consent API to be invoked without localStorage access Allows the consent API to function without requiring localStorage access, by keeping common state in the agent that controls harvests.  Applications must invoke the API on every hard page load when localStorage access is blocked. Allow nested registrations To facilitate inherent parent-child relationships with the planned register API, allow registered entities to expose their own .register() API for children of that entity to register with.  Entities who register with the container agent will be related to the container.  Entities that register under another registered entity will be related to both the container as well as the parent entity. Additional validation to prepare agent for MFE registrations Adding validation rules in the agent to prevent bad values for MFE target id and name in support of MFE/v2 registrations. Add measure support to register API Adds support for the measure API in the register response object. This is in support of the future micro front end offering planned. Add useConsentModel functionality Adds use_consent_mode init property and functionality. Adds the consent() API call. The consent model, if enabled, disallows agent harvesting unless consent is given through the consent() API call. Retry initial connect call To help prevent data loss, the agent will now retry the original \"RUM\" call an extra time for retryable status codes. Add custom event support to register API Adds methods for capturing custom events to the register API, to be used later when MFE support is established. SMs for browser connect response Adds supportability metrics for failed responses on initializing the page_view_event aggregate. Bug fixes Obfuscate custom attributes for logs added after PVE Extends obfuscation to cover custom attributes on logging events added after the initial RUM/PageViewEvent harvest. memoize promise context propagation to avoid safari hangs Memoizes promise context propagation to prevent potential browser hangs in Safari by avoiding repeated context operations. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.303.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 131-141, Edge 131-141, Safari 17-26, and Firefox 134-144. For mobile devices, v1.303.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.303.0","eolDate":"2026-11-13"},{"agent":"browser","date":"2025-10-24","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.302.0","features":["Prepare agent to utilize v2 harvests for MFE registrations"],"bugs":["User frustrations logic should be gated","Improve accuracy in standalone AjaxRequest event start times"],"security":[],"supportedOperatingSystems":null,"description":"v1.302.0 Features Prepare agent to utilize v2 harvests for MFE registrations Update the agent to handle harvests for registered targets to use the newly defined v2 endpoint schemas. This will act as the mechanism to handle client-side entity and relationship synthesis as well as ingest MFE specific data. This will be supported for Log, PageAction and JavaScriptError events, but is currently gated behind internal feature flags until a public preview is announced. Bug fixes User frustrations logic should be gated Move user frustrations logic to browser scope only with FF gate in Generic Events instrumentation.  This should avoid running extraneous wrapping logic and events related to user frustrations. Improve accuracy in standalone AjaxRequest event start times Adjusts a problem in the agent where start times of certain standalone AjaxRequest event payloads were reported relative to the page origin instead of relative to the first event in the payload, causing discrepancies when visualizing in NR1. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.302.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 131-141, Edge 131-141, Safari 17-26, and Firefox 134-144. For mobile devices, v1.302.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.302.0","eolDate":"2026-10-24"},{"agent":"browser","date":"2025-10-21","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.301.0","features":["Switch to using NR fork of rrweb"],"bugs":["Preserve agent attributes for log payloads"],"security":[],"supportedOperatingSystems":null,"description":"v1.301.0 Features Switch to using NR fork of rrweb Browser agent will now switch to using New Relic's forked version of rrweb for Session Replay instead of the original repository. This will allow browser team to custom tailor hotfixes for issues. Bug fixes Preserve agent attributes for log payloads Adjust browser log payloads, such that agent-reserved attributes will take precedence over user-provided values if they happen to share the same name. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.301.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 131-141, Edge 131-141, Safari 17-26, and Firefox 133-143. For mobile devices, v1.301.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.301.0","eolDate":"2026-10-21"},{"agent":"browser","date":"2025-10-14","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.300.0","features":["Remove usage of the marks and measures feature flag","Reduce hasReplay attribute false positive rate"],"bugs":["Update typings for interaction API to reflect waitForEnd","Address issues with dynamic require and Rollup.js"],"security":[],"supportedOperatingSystems":null,"description":"v1.300.0 Features Remove usage of the marks and measures feature flag No longer gates the agent by an internal feature flag.  Measures will be enabled for all users by default unless turned off through the application settings. Reduce hasReplay attribute false positive rate Only set \"hasReplay\" attribute once a successful session replay harvest has been observed to help reduce false positives. Bug fixes Update typings for interaction API to reflect waitForEnd Fixes an issue where the typing file defining the .interaction API was not decorated correctly to account for the optional waitForEnd argument as documented . Address issues with dynamic require and Rollup.js Fixes an issue that led Rollup.js to spawn the error Error: Could not dynamically require ... when building pages that included the MicroAgent loader. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.300.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 131-141, Edge 131-141, Safari 17-26, and Firefox 133-143. For mobile devices, v1.300.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.300.0","eolDate":"2026-10-14"},{"agent":"browser","date":"2025-10-07","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.299.0","features":["Add Flutter supportability metric","Add user frustration signals to UserAction","Evaluate the accuracy of cross-feature attribution"],"bugs":["Fix recordReplay API inconsistencies"],"security":[],"supportedOperatingSystems":null,"description":"v1.299.0 Features Add Flutter supportability metric Introduces a supportability metric to track browser agent usage in Flutter web applications. Add user frustration signals to UserAction Provide better insight into potential user frustrations for specific user actions via dead click and error click detections. Evaluate the accuracy of cross-feature attribution To support internal improvement benchmarks, add supportability metrics that evaluate the accuracy of attributes that indicate the state of a separate event, such as hasReplay or hasTrace. Bug fixes Fix recordReplay API inconsistencies Fixes an issue where a late-called recordReplay API call would not successfully harvest data. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.299.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 130-140, Edge 130-140, Safari 17-19, and Firefox 132-142. For mobile devices, v1.299.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.299.0","eolDate":"2026-10-07"},{"agent":"browser","date":"2025-09-19","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.298.0","features":["Factor long tasks into soft nav base interaction span"],"bugs":["Force LCP to report the original page URL"],"security":[],"supportedOperatingSystems":null,"description":"v1.298.0 Features Factor long tasks into soft nav base interaction span BrowserInteraction under soft navigation (\"SPA 2.0\") will extend in duration beyond DOM modification time until the point wherein no long tasks have been observed for 5 seconds. JavascriptError and AjaxRequest are not yet associated with such interaction during this extended period beyond the end of the original heuristic. Bug fixes Force LCP to report the original page URL Allow LCP to report its pageUrl distinctly from the harvest URL.  An issue was observed where soft navigations occurring before the LCP harvest would report the current page URL instead of the original page URL tied to LCP.  This change allows LCP harvest nodes to report the original URL, regardless of the current page URL.  The change should apply both to the pageUrl and targetGroupedUrl attributes. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.298.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 130-140, Edge 130-140, Safari 17-19, and Firefox 132-142. For mobile devices, v1.298.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.298.0","eolDate":"2026-09-19"},{"agent":"browser","date":"2025-09-17","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.297.1","features":[],"bugs":["Prevent double import of Session Replay aggregate class"],"security":[],"supportedOperatingSystems":null,"description":"v1.297.1 Bug fixes Prevent double import of Session Replay aggregate class Fixes an issue that was found where the Session Replay aggregate class could be double imported when using the newrelic.recordReplay API method while preloading was enabled. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.297.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 130-140, Edge 130-140, Safari 17-19, and Firefox 132-142. For mobile devices, v1.297.1 was built and tested for Android OS 16 and iOS Safari 17-18.5.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.1","eolDate":"2026-09-17"},{"agent":"browser","date":"2025-09-10","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.297.0","features":["Prevent early harvests when in retry period","remove newrelic meta attribute"],"bugs":["Fix exceptions for null bodies arising from empty harvests"],"security":[],"supportedOperatingSystems":null,"description":"v1.297.0 Features Prevent early harvests when in retry period Prevent the agent from harvesting early when being rate limited.  If the ingest service returns a 429, the agent will replace its data and try the harvest again later.  While that is happening, it will no longer be able to harvest early as new data comes in, until it successfully harvests. remove newrelic meta attribute Remove the reporting of the __newrelic meta attribute from outgoing replay payloads.  This is being conducted as a measure to help save billable bytes for customers and reduce cost of use for Session Replay functionalities. Bug fixes Fix exceptions for null bodies arising from empty harvests A change has been made to enforce that all cleaned payloads ensure a valid output. Before, an empty string passing through the body cleaning process could throw an error as the mechanism would return the body as null.  Now empty strings will pass through untouched, allowing further processing to apply successfully. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.297.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 129-139, Edge 129-139, Safari 17-19, and Firefox 131-141. For mobile devices, v1.297.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.297.0","eolDate":"2026-09-10"},{"agent":"browser","date":"2025-08-19","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.296.0","features":["Harvest traces early"],"bugs":["Remove event buffer inspection event"],"security":[],"supportedOperatingSystems":null,"description":"v1.296.0 Features Harvest traces early Update agent to handle session traces the same way other features handle data as of 1.294.0 , by allowing harvests at 16kb of size. Bug fixes Remove event buffer inspection event Removes the event buffer inspection event to avoid a memory leak on using console.log with the newrelic window event listener. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.296.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 129-139, Edge 129-139, Safari 17-19, and Firefox 131-141. For mobile devices, v1.296.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.296.0","eolDate":"2026-08-19"},{"agent":"browser","date":"2025-08-04","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.295.0","features":["Add error cause detection"],"bugs":["Add monkey-patching warnings","Calculate first and last timestamps from raw data"],"security":[],"supportedOperatingSystems":null,"description":"v1.295.0 Features Add error cause detection Detect and report the cause attribute on captured JavaScriptError events.  If the cause is an instance of an Error, the stack trace will be captured, otherwise the stringified contents of the cause will be reported. This will be queryable in JavaScriptError events under the attribute cause. Bug fixes Add monkey-patching warnings Added detection and warnings for when expected globals have been monkey-patched before the agent has been executed on the page.  This can cause unexpected behaviors and the intent is to inform customers of this behavior. Calculate first and last timestamps from raw data Ensure the agent manually calculates the first and last timestamps of a SessionReplay payload before harvesting to help improve consistency on the UI replayer. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.295.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 128-138, Edge 128-138, Safari 17-19, and Firefox 130-140. For mobile devices, v1.295.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.295.0","eolDate":"2026-08-04"},{"agent":"browser","date":"2025-07-23","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.294.0","features":["Harvest early"],"bugs":["report empty previousUrl as undefined"],"security":[],"supportedOperatingSystems":null,"description":"v1.294.0 Features Harvest early The agent will now be able to trigger early harvests if certain criteria is met.  This will help ensure that more payloads are kept and memory leaks are prevented. The agent will initiate an early harvest when a feature buffer size reaches 16KB, otherwise it will continue to harvest every 30 seconds as before. This new behavior will apply to the following events: AjaxRequest BrowserInteraction BrowserPerformance Custom Events Log PageAction PageViewTiming SessionReplay UserAction A separate effort will be conducted to enable early harvesting for timeslice metrics, javascript errors and session traces which use other mechanisms for storage in the agent. Bug fixes report empty previousUrl as undefined The previousUrl attribute on BrowserInteraction events was reported as an empty string is cases where document.referrer is empty.  This caused URL grouping to apply grouping on an empty string, leading to meaningless groups being appended to previousUrl.  previousUrl is now reported as undefined to allow URL grouping to skip empty URLs. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.294.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 128-138, Edge 128-138, Safari 17-19, and Firefox 130-140. For mobile devices, v1.294.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.294.0","eolDate":"2026-07-23"},{"agent":"browser","date":"2025-07-01","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.293.0","features":["Add \"long tasks\" internal message","Emit SM on rum response invalid timestamps"],"bugs":["Address issue keeping distributed traces from being disabled"],"security":[],"supportedOperatingSystems":null,"description":"v1.293.0 Features Add \"long tasks\" internal message Add an internal message indicating if a wrapped function qualifies as a \"long task\".  This is to be used later in agent features to enhance future behaviors. Emit SM on rum response invalid timestamps Emit a supportability metric on receiving an invalid timestamp in the rum call response. Bug fixes Address issue keeping distributed traces from being disabled Addressed a bug where the agent was able to capture distributed traces, even when distributed_tracing: false was supplied in the configuration. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.293.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 128-138, Edge 127-137, Safari 17-19, and Firefox 129-139. For mobile devices, v1.293.0 was built and tested for Android OS 16 and iOS Safari 17-26.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.293.0","eolDate":"2026-07-01"},{"agent":"browser","date":"2025-06-26","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.292.1","features":[],"bugs":["fix custom attribute race condition precedence"],"security":[],"supportedOperatingSystems":null,"description":"v1.292.1 Bug fixes fix custom attribute race condition precedence Addressed a race condition that occurred between the local storage module reading and writing custom attributes locally and the API updating custom attributes in page memory. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.292.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 127-137, Edge 127-137, Safari 17-18, and Firefox 129-139. For mobile devices, v1.292.1 was built and tested for Android OS 16 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.1","eolDate":"2026-06-26"},{"agent":"browser","date":"2025-06-16","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.292.0","features":["Update BrowserInteraction previousUrl definition","Add more inspection events"],"bugs":["Fix .finished API timeSinceLoad value"],"security":[],"supportedOperatingSystems":null,"description":"v1.292.0 Features Update BrowserInteraction and previousUrl definition Update BrowserInteractions to use document.referrer for previousUrl values on initialPageLoad interactions instead of mirroring previousUrl and targetUrl. This enables better functionality for user journeys and provides more insight on page linkages. Add more inspection events Adds new inspection events to the agent. These events include the drain event, window lifecycle events such as navigate, load, DOMContentLoaded, and the session event which emits on changes to the agent's session state. Bug fixes Fix finished API timeSinceLoad value Fixes an issue where the finished api was creating a timeSinceLoad value for PageAction data as the unix timestamp instead of a relative time value in seconds from the page origin. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.292.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 127-137, Edge 127-137, Safari 17-18, and Firefox 128-138. For mobile devices, v1.292.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.292.0","eolDate":"2026-06-16"},{"agent":"browser","date":"2025-06-06","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.291.1","features":[],"bugs":["Prevent ST from holding onto Event refs in memory when aborted","Clean BrowserPerformance entryName for resources","Add safeguards for addToTrace"],"security":[],"supportedOperatingSystems":null,"description":"v1.291.1 Bug fixes Prevent ST from holding onto Event refs in memory when aborted Releases the Event entries the agent hold onto in Trace after it has aborted. This addresses a known case of memory leak caused by continuing to add those references to a Set that is never cleared. Clean BrowserPerformance entryName for resources The entryName attribute of resource type BrowserPerformance events will now have a cleaner URL, removing the hash fragment from reported URLs. Add safeguards for addToTrace Events created with addToTrace API, which have an invalid UNIX timestamp, emit a warning and return without creating the event. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.291.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 126-136, Edge 126-136, Safari 17-18, and Firefox 128-138. For mobile devices, v1.291.1 was built and tested for Android OS 16 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.291.1","eolDate":"2026-06-06"},{"agent":"browser","date":"2025-05-30","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.291.0","features":["Create the measure API"],"bugs":["Fix race between end of session and features aborting","Harvest first session trace payload immediately"],"security":[],"supportedOperatingSystems":null,"description":"v1.291.0 Features Create the measure API Adds the measure API to the newrelic global object. This API allows generating new BrowserPerformance data even if auto-detection of marks and measures is not enabled. Bug fixes Fix race between end of session and features aborting Fix an issue where features would race with the session manager when a session ends. This required a check for session timings to match a given session and could create a state where a new session created from a pre-existing session would trigger a partial replay or no replay, and prevent the agent from sending trace data with a given replay. Harvest first session trace payload immediately For better consistency, implemented old behavior where the first ST payload is harvested immediately when the page loads.  This helps ensure cases where replays are harvested but traces are not happen less frequently. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.291.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 126-136, Edge 126-136, Safari 17-17, and Firefox 128-138. For mobile devices, v1.291.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.291.0","eolDate":"2026-05-30"},{"agent":"browser","date":"2025-05-21","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.290.1","features":[],"bugs":["Silence setting getter only harvestCount message"],"security":[],"supportedOperatingSystems":null,"description":"v1.290.1 Bug fixes Silence setting getter only harvestCount message The warning that results from the agent attempting to overwrite the runtime harvestCount will be correctly silenced. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.290.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 126-136, Edge 126-136, Safari 17-17, and Firefox 128-138. For mobile devices, v1.290.1 was built and tested for Android OS 16 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.290.1","eolDate":"2026-05-21"},{"agent":"browser","date":"2025-05-02","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.290.0","features":["bundler tools exports","Set UserAction currentUrl before aggregation end","Improve lazy-loading optimization","API Code Splitting"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.290.0 Features Bundler tools exports An optional Webpack splitChunks cacheGroup matcher is now available for users who build the agent via NPM. This matcher enables de-duplication and merging of the agent's lazy-loaded JavaScript into a single chunk. This single chunk loads post-page render, consistent with the behavior of our pre-built agent for APM and copy/paste implementations. Set UserAction currentUrl before aggregation end Set currentUrl on the first event of a user action instead of at the end of aggregation. Improve lazy-loading optimization Optimize our pattern to ensure that code-bundlers such as webpack can more effectively tree-shake the output to only include the relevant files needed to run the agent.  This specifically helps reduce the bundle size, reduce the amount of lazy files generated, and streamlines \"custom\" agent builds used with NPM. API Code Splitting Split the API method definitions per feature instead of a single file shared across all loader types.  This allows each loader to only instantiate the necessary APIs for the features included, and reduce overall bundle size for the \"Lite\" build as well as custom-built agents with NPM.  A shell will still exist for non-initialized APIs to prevent errors from throwing on APIs used without the needed features. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.290.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 125-135, Edge 125-135, Safari 17-17, and Firefox 127-137. For mobile devices, v1.290.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.290.0","eolDate":"2026-05-02"},{"agent":"browser","date":"2025-04-24","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.289.0","features":["Remove agent config cache and getters/setters"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.289.0 Features Remove agent config cache and getters/setters Removes agent internal configuration utility functions. No impact to agent functionality is expected. Build size have been reduced by this coding style change. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.289.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 125-135, Edge 125-135, Safari 17-17, and Firefox 127-137. For mobile devices, v1.289.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.289.0","eolDate":"2026-04-24"},{"agent":"browser","date":"2025-04-18","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.288.1","features":[],"bugs":["Ensure event buffer always exists","Call handle directly for submitting SM"],"security":[],"supportedOperatingSystems":null,"description":"v1.288.1 Bug fixes Ensure event buffer always exists Ensure event buffers always exist to prevent race conditions between agent life-cycles and data storage. Call handle directly for submitting SM This fixes a bad reference to a parent function that is not accessible. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.288.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 125-135, Edge 125-135, Safari 17-17, and Firefox 127-137. For mobile devices, v1.288.1 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.288.1","eolDate":"2026-04-18"},{"agent":"browser","date":"2025-04-16","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.288.0","features":["Prevent storing session data past session expiry","Introduce isFirstOfSession attribute on InitialPageLoad events"],"bugs":["Reset `notified` when replay stops recording","Solve race condition in logging abort"],"security":[],"supportedOperatingSystems":null,"description":"v1.288.0 Features Prevent storing session data past session expiry There may be edge cases where some Session Replay/Session Trace data could be stored even though the agent session has expired.  Add instrumentation to detect such occurrences and skip storing these events for the time being. Introduce isFirstOfSession attribute on InitialPageLoad events To help support User Journeys, the isFirstOfSession custom attribute will be added to BrowserInteraction events of initial page load kind if the page is the first of a new session. Bug fixes Reset notified when replay stops recording Resolves an issue where JavaScriptError events would be missing the hasReplay attribute after session recording is resumed (for example, from user clicking on another tab/tab going idle and then coming back to it). Solve race condition in logging abort If the logging feature aborted before the agent had set up the event buffer, it could throw errors.  This was addressed by checking for the presence of the event buffer before running methods against it. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.288.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 124-134, Edge 124-134, Safari 17-17, and Firefox 126-136. For mobile devices, v1.288.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.288.0","eolDate":"2026-04-16"},{"agent":"browser","date":"2025-04-10","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.287.0","features":["Change architecture to help enable future Micro Front End support"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.287.0 Features Change architecture to help enable future Micro Front End support Update the browser agent to support the future product decisions necessary to support micro front end architecture patterns from a single agent instance.  This includes the addition of experimental APIs, intended to be used internally only to help support product development until future general availability (GA) is reached. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.287.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 124-134, Edge 124-134, Safari 17-17, and Firefox 126-136. For mobile devices, v1.287.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.287.0","eolDate":"2026-04-10"},{"agent":"browser","date":"2025-04-01","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.286.0","features":["Erase .api property on agent instance","Reduce noise from `mousemove` events","Handle duplicate agent APIs"],"bugs":["Patch `newrelic` event detail","Get string className for SVG elements"],"security":[],"supportedOperatingSystems":null,"description":"v1.286.0 Features Erase .api property on agent instance The .api property of full and micro agents have been removed. The browser API methods are instead moved to the agent instance itself for ease of targeted access. This includes a minor fix of runtime loaderType for agents that are re-configured after load. Reduce noise from mousemove events There may be an edge case where a site performance can be impacted if the browser agent picked up mousemove events via addEventListener. Handle duplicate agent APIs Top-level interaction api calls are only responded to by the first exposed non-micro agent. This was changed to prevent issues for customers that run multiple agents together. The top-level interaction api should only be used to communicate with the main agent on the webpage. API calls on micro agents must instead be directly called on the respective micro agents. Bug fixes Patch newrelic event detail There is an edge case where if there is a listener on the newrelic event (as described in the install docs ) and any API call is invoked inside this listener, it will trigger an infinite loop. Get string className for SVG elements Change the nearestClass field for SVG elements to be a meaningful string name. The className of such elements is of type SVGAnimatedString and previously resulted in an empty object string. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.286.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 124-134, Edge 124-134, Safari 17-17, and Firefox 126-136. For mobile devices, v1.286.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.286.0","eolDate":"2026-04-01"},{"agent":"browser","date":"2025-03-18","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.285.0","features":["Decorate harvest requests with ht (hasTrace) param","Inspection events"],"bugs":["Session Replay text masking for whitespace","Logging mode on session update"],"security":[],"supportedOperatingSystems":null,"description":"v1.285.0 Features Decorate harvest requests with ht (hasTrace) param Decorate with ht (hasTrace) query param for all harvest requests except for blobs and logs endpoints.  This helps support searching for browser data with associated tracing data. Inspection events Adds inspection events that detail when various agent-related events occur. These events can be listened to on the event listener 'newrelic' string type. Events include agent initialization, agent fully loaded, event buffered, event harvested, and api calls. Bug fixes Session Replay text masking for whitespace There is an edge case where whitespace was being masked, which interferes with the layout/styling in session replays. Logging mode on session update Fixes a typo in the session update handler for logging feature. The loggingMode which controls feature output will be correctly set after its session mode value is updated from another tab or window. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.285.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 124-134, Edge 124-134, Safari 17-17, and Firefox 126-136. For mobile devices, v1.285.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.285.0","eolDate":"2026-03-18"},{"agent":"browser","date":"2025-03-11","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.284.1","features":[],"bugs":["Obtain FirstInteraction directly from performance API","Console error on some cross-origin requests without NR CAT header"],"security":[],"supportedOperatingSystems":null,"description":"v1.284.1 Bug fixes Obtain FirstInteraction directly from performance API To alleviate the potential performance impact of creating new performance observers to support legacy FirstInteraction timings, a change has been made to query the performance API directly for the presence of first-input data without the use of an observer at logical checkpoints. Console error on some cross-origin requests without NR CAT header XHR headers will be checked for the deprecated New Relic CAT header before calling getResponseHeader, which throws a console error if it does not exist for cross-origin requests. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.284.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.284.1 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.284.1","eolDate":"2026-03-11"},{"agent":"browser","date":"2025-03-04","downloadLink":"https://www.npmjs.com/package/@newrelic/browser-agent","version":"1.284.0","features":["Remove FID, replace first interaction detection with INP"],"bugs":["Deduplicate Prefixes on Unhandled Promise Rejection Messages","Upgrade rrweb to 18","bump web-vitals from 4.2.3 to 4.2.4","Guard against non-CSSStyleSheet when fixing sheets for replay"],"security":[],"supportedOperatingSystems":null,"description":"v1.284.0 Features Remove FID, replace first interaction detection with INP First Input Delay (FID) has been deprecated and replaced by Interaction To Next Paint (INP). PageViewTiming events for first interactions are preserved by detecting the first INP event and will no longer output value for the firstInputDelay attribute. For more info on PageViewTiming, see https://docs.newrelic.com/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/. For more info on INP and the FID deprecation, see https://web.dev/articles/inp. Bug fixes Deduplicate Prefixes on Unhandled Promise Rejection Messages Remove an issue that caused Unhandled Promise Rejection: prefixes on casted error messages to be duplicated if already supplied on rejection reason messages. Upgrade rrweb to 18 Upgrade RRWeb dependency to version 18 to improve session replay performance. bump web-vitals from 4.2.3 to 4.2.4 Bumps web-vitals  from 4.2.3 to 4.2.4 to fix memory leak in registering new event listeners on every keydown and click (#554 ) Guard against non-CSSStyleSheet when fixing sheets for replay Nullish values in the global styleSheets API can break implementations with the weakMap object tracking their status, throwing an error similar to TypeError: Invalid value used in weak set at WeakSet.add....  This fix checks that the value is acceptable before adding. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.284.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.284.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.284.0","eolDate":"2026-03-04"},{"agent":"browser","date":"2025-02-21","downloadLink":null,"version":"1.283.2","features":[],"bugs":["Add logging analytic metrics and fix browser performance metrics"],"security":[],"supportedOperatingSystems":null,"description":"v1.283.2 Bug fixes Add logging analytic metrics and fix browser performance metrics Fix logging analytics metrics and centralize the metrics reporter for easier use Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.283.2 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.283.2 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.283.2","eolDate":"2026-02-21"},{"agent":"browser","date":"2025-02-19","downloadLink":null,"version":"1.283.1","features":[],"bugs":["Removing websocket wrapping & SM"],"security":[],"supportedOperatingSystems":null,"description":"v1.283.1 Bug fixes Removing websocket wrapping & SM Removing websocket wrapping and metrics. WS instrumentation may be re-implemented behind a feature flag at a later time. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.283.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.283.1 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.283.1","eolDate":"2026-02-19"},{"agent":"browser","date":"2025-02-18","downloadLink":null,"version":"1.283.0","features":["Add global custom attributes to log data","Add auto-logging feature"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.283.0 Features Add global custom attributes to log data Add custom attributes set by the setCustomAttributes method in Browser Agent API to logging data. These attributes are in the common.attributes section of the outgoing payload. Local custom attributes set by the log and wrapLogger APIs take precedence in the backend over the global custom attributes set by the setCustomAttributes API. Add auto-logging feature Introduces automatic observation of browser console methods to capture logging statements from the browser console across a given session automatically. On/off, logging level, and sampling are controllable via the application settings section of your browser entities. Check the getting started guide for more info. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.283.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.283.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.283.0","eolDate":"2026-02-18"},{"agent":"browser","date":"2025-02-13","downloadLink":null,"version":"1.282.0","features":["Re-implement wrap-websocket into agent"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.282.0 Features Re-implement wrap-websocket into agent Re-implement wrap-websocket code using ES6 extends syntax into the agent. This will allow supportability metrics to be reportable from websocket API usage. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.282.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 122-132, Edge 122-132, Safari 17-17, and Firefox 124-134. For mobile devices, v1.282.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.282.0","eolDate":"2026-02-13"},{"agent":"browser","date":"2025-02-04","downloadLink":null,"version":"1.281.0","features":["Capture Nearest UserAction Fields"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.281.0 Features Capture Nearest UserAction Fields The UserAction feature has been extended to capture \"nearest\" field values when the UserAction target does not include the desired fields. To facilitate this, a configuration was added allowing the user to control what fields are collected, specified as init.user_actions.elementAttributes: [].  When empty, no extra fields will be collected.  When supplied, the target will be checked for each property. This configuration defaults to ['id', 'className', 'tagName', 'type'], which matches the fields captured before this change. For each elementAttribute defined, if the property is not found, the agent will search up the parent tree of the target element, until the property is found.  If found up the parent tree, a property called \"nearest\" + fieldName will be added to the event. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.281.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 122-132, Edge 122-132, Safari 17-17, and Firefox 124-134. For mobile devices, v1.281.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.281.0","eolDate":"2026-02-04"},{"agent":"browser","date":"2025-01-31","downloadLink":null,"version":"1.280.0","features":["Remove agentIdentifier argument from agent constructors"],"bugs":["Roll back to previous FirstInteraction implementation"],"security":[],"supportedOperatingSystems":null,"description":"v1.280.0 Features Remove agentIdentifier argument from agent constructors Removes the agentIdentifier argument from the Agent and MicroAgent class constructors. The agentIdentifier should always be a random hex string to guarantee uniqueness across agent instances. Bug fixes Roll back to previous FirstInteraction implementation Setting agent back to previous FirstInteraction implementation after some reports of slow downs around the performance observer on the first input of a page. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.280.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 122-132, Edge 122-132, Safari 17-17, and Firefox 124-134. For mobile devices, v1.280.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.280.0","eolDate":"2026-01-31"},{"agent":"browser","date":"2025-01-28","downloadLink":null,"version":"1.279.1","features":[],"bugs":["CLS timing node not being reported post new Harvester"],"security":[],"supportedOperatingSystems":null,"description":"v1.279.1 Bug fixes CLS timing node not being reported post new Harvester Reintroduce the cumulativeLayoutShift timing of PageViewTiming events into EoL harvests. After v1.278.0, this timing stopped being sent when the user leaves the page, resulting in a drop in CLS counts. The node contains attributes that aid in identifying the cause of bad scores. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.279.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 122-132, Edge 122-132, Safari 17-17, and Firefox 124-134. For mobile devices, v1.279.1 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.279.1","eolDate":"2026-01-28"},{"agent":"browser","date":"2025-01-24","downloadLink":null,"version":"1.279.0","features":["Remove FID","Debounce window user actions","Capture details in marks and measures","Add HTTP codes for harvest retry attempts"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.279.0 Features Remove FID First Input Delay (FID) has been deprecated and replaced by Interaction To Next Paint (INP).   PageViewTiming events for first interactions are preserved by detecting the first first-input event  and will no longer output value for the firstInputDelay and loadState attributes.  For more info on PageViewTiming, see https://docs.newrelic.com/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/.  For more info on INP and the FID deprecation, see https://web.dev/articles/inp. Debounce window user actions Debounce focus and blur events on the window for 500ms to prevent duplicate events from being harvested. All major browsers have their own quirky behaviors that generate duplicate blur and focus events under some conditions. This change ensures that only 1 blur or focus event can be captured every 500ms to reduce noise. Capture details in marks and measures The detail property of PerformanceMark and PerformanceMeasure events will now be captured in New Relic BrowserPerformance under the entryDetail attribute.  If detail is an object, it and any nested objects within it will be flatten into string path keys prefixed with entryDetail. See the PR  for elucidation. Add HTTP codes for harvest retry attempts Agent will begin to retry harvests to the endpoints that failed for the following additional status codes: 502, 504, and 512-530. This is suggested by New Relic ingest teams as a possibility to recapture lost data in these marginal cases. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.279.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.279.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.279.0","eolDate":"2026-01-24"},{"agent":"browser","date":"2025-01-14","downloadLink":null,"version":"1.278.3","features":[],"bugs":["Change obfuscator to read dynamically from configuration"],"security":[],"supportedOperatingSystems":null,"description":"v1.278.3 Bug fixes Change obfuscator to read dynamically from configuration Fix an issue where obfuscation rules are not honored if added after the agent has initialized.  Some user cases require obfuscation rules to be dynamically added, this change will allow that behavior -- as long as the obfuscation rules are added to newrelic.initializedAgents[index].init.obfuscate Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.278.3 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.278.3 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.278.3","eolDate":"2026-01-14"},{"agent":"browser","date":"2025-01-09","downloadLink":null,"version":"1.278.2","features":[],"bugs":["Allow the page view feature to have access to an event buffer"],"security":[],"supportedOperatingSystems":null,"description":"v1.278.2 Bug fixes Allow the page view feature to have access to an event buffer Fix an issue where if the page unloaded before the page view feature could \"block\" itself from future harvests, an undefined error could be thrown when the harvester tries to access each feature's event buffer. The page view feature now has access to the event buffer, to prevent that undefined check.  The event buffer will remain empty, since the page view feature does not carry state. This change rectifies an issue observed in 1.278.1. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.278.2 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.278.2 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.278.2","eolDate":"2026-01-09"},{"agent":"browser","date":"2025-01-08","downloadLink":null,"version":"1.278.1","features":[],"bugs":["Make Metrics harvest only on EoL for new Harvester"],"security":[],"supportedOperatingSystems":null,"description":"v1.278.1 Bug fixes Make Metrics harvest only on EoL for new Harvester Prevent Metrics feature from harvesting on interval after changes in v1.278.0. This reverts its behavior back to sending only final harvests. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.278.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.278.1 was built and tested for Android OS 15 and iOS Safari 17-18.1.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.278.1","eolDate":"2026-01-08"},{"agent":"browser","date":"2025-01-07","downloadLink":null,"version":"1.278.0","features":["Centralized harvesting"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.278.0 Features Centralized harvesting Introduces a singleton harvester tasked with sending feature payloads rather than each feature utilizing their own scheduler. This reduces runtime space usage and the number of timers which proportionally scales as the number of features increases. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.278.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.278.0 was built and tested for Android OS 15 and iOS Safari 17-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.278.0","eolDate":"2026-01-07"},{"agent":"browser","date":"2024-12-18","downloadLink":null,"version":"1.277.0","features":["Add custom events API"],"bugs":["Soft navigation bug fixes and new soft navigation tests"],"security":[],"supportedOperatingSystems":null,"description":"v1.277.0 Features Add custom events API Add a new API - recordCustomEvent(eventType, attributes). This allows any custom-defined eventType to be stored in NRDB. Check the API documentation  for more information. Bug fixes Soft navigation bug fixes and new soft navigation tests Fixes several issues tied to the soft navigations feature.  Calling newrelic.interaction() prior to a page load now creates a separate \"api\" trigger node. Multiple interactions managed simultaneously now have correct timings. Fixes a bug in soft navigation, where API-triggered interactions fail to close under default heuristic (URL + DOM change), because the mutation observer is not started. Finally, 'popstate' events are now valid interaction triggers for soft navigations. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.277.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.277.0 was built and tested for Android OS 15 and iOS Safari 17-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.277.0","eolDate":"2025-12-18"},{"agent":"browser","date":"2024-12-16","downloadLink":null,"version":"1.276.0","features":["allow feature flags to control experimental features","Capture Page Resource Assets"],"bugs":["Ignore reserved attribute names on UserActions tied to the window","Fix syntax error in fallback when tracking xhr readyState"],"security":[],"supportedOperatingSystems":null,"description":"v1.276.0 Features Allow feature flags to control experimental features Use internal feature flags to control experimental features, reducing your effort and supporting APM-injected installations. Capture Page Resource Assets Add detection for page resource assets that captures data as a BrowserPerformance event. This feature is being shipped in an experimental state and is off by default. To opt in to using this feature, it can be turned on by setting the config value init.performance.resources.enabled = true in Copy/Paste or NPM installations. Bug fixes Ignore reserved attribute names on UserActions tied to the window Force the agent to not capture target-level attributes for window-level UserActions. You can set window-level variables that mimic HTML element attributes like type or tagName. This change prevents the potential capture of those attributes as part of blur or focus user actions tied to the window. Fix syntax error in fallback when tracking xhr readyState Fixed the syntax error that would cause xhr readystate fallback checks to always capture. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.276.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 121-131, Edge 121-131, Safari 17-17, and Firefox 122-132. For mobile devices, v1.276.0 was built and tested for Android OS 15 and iOS Safari 17-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.276.0","eolDate":"2025-12-16"},{"agent":"browser","date":"2024-12-03","downloadLink":null,"version":"1.275.0","features":["Allow logs api wrapper to update custom attributes","Enable the browser agent to run in extension background contexts"],"bugs":["Harvest generic events when max size is reached"],"security":[],"supportedOperatingSystems":null,"description":"v1.275.0 Features Allow logs API wrapper to update custom attributes This supports the rollout of the auto-logging feature without disrupting customers that may currently be using wrapLogger to wrap the console object. Enable the browser agent to run in extension background contexts Use fetch to send harvest payloads when XMLHttpRequest is unavailable, such as in browser extension contexts. Bug fixes Harvest generic events when max size is reached To avoid behavior that could lead to more network requests than necessary, generic events will now harvest early when the max payload size is reached. This represents an increase from 64Kb to 1Mb. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.275.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 122-132. For mobile devices, v1.275.0 was built and tested for Android OS 15 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.275.0","eolDate":"2025-12-03"},{"agent":"browser","date":"2024-11-19","downloadLink":null,"version":"1.274.0","features":["Upgrade SessionReplay libraries to latest version"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.274.0 Features Upgrade SessionReplay libraries to latest version Upgrade underlying session replay libraries to latest version which addresses some known bugs. This change also removes the error swallower inside the session replay module and instead handles all session replay errors at the window level to allow for external libraries to observe known errors to induce fallback behaviors, such as those implemented in CSS-as-JS libraries. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.274.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 122-132. For mobile devices, v1.274.0 was built and tested for Android OS 15 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.274.0","eolDate":"2025-11-19"},{"agent":"browser","date":"2024-11-18","downloadLink":null,"version":"1.273.1","features":[],"bugs":["Multiple MicroAgent undefined session and limit available API"],"security":[],"supportedOperatingSystems":null,"description":"v1.273.1 Bug fixes Multiple MicroAgent undefined session and limit available API MicroAgent class now only shows the relevant API for use with NPM. The set is limited to methods that relate to features available with the MicroAgent. An issue with missing session when multiple MicroAgents are initialized is also fixed. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.273.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 122-132. For mobile devices, v1.273.1 was built and tested for Android OS 15 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.273.1","eolDate":"2025-11-18"},{"agent":"browser","date":"2024-11-11","downloadLink":null,"version":"1.273.0","features":["Refactor feature storages","Remove wrap-events usage from soft nav"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.273.0 Features Refactor feature storages This change rewrites the way every feature stores its respective data to optimize runtime overhead, improve agent internals efficiency, and standardize the way storages are referenced and called. Remove wrap-events usage from soft nav Remove wrap-events module from usage for soft navigation feature. This is part of an effort to cleanup code in the agent. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.273.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 122-132. For mobile devices, v1.273.0 was built and tested for Android OS 15 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.273.0","eolDate":"2025-11-11"},{"agent":"browser","date":"2024-11-07","downloadLink":null,"version":"1.272.0","features":["Marks and measures"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.272.0 Features Marks and measures Add detection for marks and measures which captures data as a BrowserPerformance event.  This feature is being shipped in an experimental state and is off by default. To opt in to using this feature, it can be turned on by setting the config value init.performance.capture_marks = true or init.performance.capture_measures = true in Copy/Paste or NPM installations. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.272.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 122-132. For mobile devices, v1.272.0 was built and tested for Android OS 15 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.272.0","eolDate":"2025-11-07"},{"agent":"browser","date":"2024-11-01","downloadLink":null,"version":"1.271.0","features":["Ignore unhandled promise rejections that lack a valid reason"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.271.0 Features Ignore unhandled promise rejections that lack a valid reason The agent will not report unhandled promise rejections that lack a reason property as they cannot generate sufficient stack trace or messaging information for debugging. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.271.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 121-131. For mobile devices, v1.271.0 was built and tested for Android OS 15 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.271.0","eolDate":"2025-11-01"},{"agent":"browser","date":"2024-10-31","downloadLink":null,"version":"1.270.3","features":[],"bugs":["Ensure all lazy loaded modules issue warning instead of errors"],"security":[],"supportedOperatingSystems":null,"description":"v1.270.3 Bug fixes Ensure all lazy loaded modules issue warning instead of errors Lazy loaded modules that are blocked from loading by third-party tools (such as ad blocking mechanisms) will issue a warning to console instead of throwing an error. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.270.3 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 120-130, Edge 120-130, Safari 16-17, and Firefox 121-131. For mobile devices, v1.270.3 was built and tested for Android OS 15 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.270.3","eolDate":"2025-10-31"},{"agent":"browser","date":"2024-10-28","downloadLink":null,"version":"1.270.2","features":[],"bugs":["Correct naming for logging pageUrl attribute"],"security":[],"supportedOperatingSystems":null,"description":"v1.270.2 Bug fixes Correct naming for logging pageUrl attribute Corrects naming for the Logging pageUrl attribute by using the original url of the page instead of the url of when the event happens. Removes origin attribute from the runtime model object. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.270.2 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 119-129, Edge 119-129, Safari 16-17, and Firefox 121-131. For mobile devices, v1.270.2 was built and tested for Android OS 15 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.270.2","eolDate":"2025-10-28"},{"agent":"browser","date":"2024-10-23","downloadLink":null,"version":"1.270.1","features":[],"bugs":["Remove undefined agentRuntime in Session Trace"],"security":[],"supportedOperatingSystems":null,"description":"v1.270.1 Bug fixes Remove undefined agentRuntime in Session Trace Remove an outdated reference to agentRuntime variable in the Trace feature released in 1.270.0. It caused undefined errors in sub-cases wherein max harvest nodes were reached. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.270.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 119-129, Edge 119-129, Safari 16-17, and Firefox 121-131. For mobile devices, v1.270.1 was built and tested for Android OS 15 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.270.1","eolDate":"2025-10-23"},{"agent":"browser","date":"2024-10-22","downloadLink":null,"version":"1.270.0","features":["Remove supportsSendBeacon runtime property","Add Firefox to LCP test matcher","Remove 'pageHide' from page end-of-lifecycle listener","Move deregisterDrain method to feature-base","Relocate aggregator from loader and improve agent internals"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.270.0 Features Remove supportsSendBeacon runtime property Removes the supportsSendBeacon runtime property from our agent code. We no longer officially support browsers that cannot use the sendBeacon method, so there's no point in checking for it. Add Firefox to LCP test matcher Add Firefox versions 122 and above to LCP test matcher since versions 122 and above now support collection of LCP web vital timings. Remove 'pageHide' from page end-of-lifecycle listener Remove pageHide from page end-of-lifecycle listener since browser agent support for Safari 14.4 is deprecated Move deregisterDrain method to feature-base Moves the deregisterDrain method in order to standardize the implementation pattern to match the drain method. Relocate aggregator from loader and improve agent internals Styling and architectural changes that will reduce agent loader size by moving the Aggregator module to async chunk and removing the need for some configuration getters in the features. No behavioral change or significant performance impact from the agent is expected. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.270.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 119-129, Edge 119-129, Safari 16-17, and Firefox 121-131. For mobile devices, v1.270.0 was built and tested for Android OS 15 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.270.0","eolDate":"2025-10-22"},{"agent":"browser","date":"2024-10-16","downloadLink":null,"version":"1.269.0","features":["Include logging feature in micro agent loader","Add instrumentation metadata to logging"],"bugs":["Only ever allow session traces to capture page load timings once","Handle Session Replay Security Policy Errors"],"security":[],"supportedOperatingSystems":null,"description":"v1.269.0 Features Include logging feature in micro agent loader Allow the MicroAgent loader on NPM to utilize the logging APIs to manually capture log data. Add instrumentation metadata to logging Add instrumentation attribution to logging payloads to fortify categorization and billing calculations in New Relic platforms. These attributes are dropped during processing and before storing the data and as such don't affect customer billing rates. Bug fixes Only ever allow session traces to capture page load timings once An edge case issue was resolved where session traces could include duplicate copies of the page load timings obtained from the browser timing APIs. Handle Session Replay Security Policy Errors Handle Security Policy Errors encountered by session replay when browser APIs have been natively disabled. This was also observed to happen in Chromium browsers that completely disabled cookie storage. Supportability metrics about agent internal errors are now captured as a biproduct of this work to help facilitate future improvements. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.269.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 118-128, Edge 119-129, Safari 16-17, and Firefox 119-129. For mobile devices, v1.269.0 was built and tested for Android OS 15 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.269.0","eolDate":"2025-10-16"},{"agent":"browser","date":"2024-10-08","downloadLink":null,"version":"1.268.0","features":["Aggregate UserActions","Add UserAction to GenericEvents"],"bugs":["Always return a string for custom stringify method","Force generic events feature to clear buffer when unloading"],"security":[],"supportedOperatingSystems":null,"description":"v1.268.0 Features Aggregate UserActions Utilize sequential aggregation techniques when observing UserAction data to reduce ingest cost for customers. Add UserAction to GenericEvents Select user interactive events will be captured in this release. This is an extension of the GenericEvents feature meant to drive UI experience. Bug fixes Always return a string for custom stringify method An internal mechanism used to convert JS values to string was returning undefined for certain values, which may lead to errors for downstream callers when they are expecting a string. This is part 2 of a patch to ensure a string is returned. Force generic events feature to clear buffer when unloading Fixed an issue where the generic events buffer was not clearing when unloading. This affected a small portion of experiences where the agent was \"unloading\" due to the page losing focus, but not actually closing.  Subsequent harvests when the page was re-focused would have the potential for duplicated data. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.268.0 of the browser agent was built for and tested against these browsers and version ranges: Chrome 118-128, Edge 117-127, Safari 16-17, and Firefox 119-129. For mobile devices, v1.268.0 was built and tested for Android OS 14 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.268.0","eolDate":"2025-10-08"},{"agent":"browser","date":"2024-09-23","downloadLink":null,"version":"1.267.0","features":["Upgrade to web-vitals v4","Improve notifications of stylesheet status for session replay","Add soft navigations to Browser-Agent loader","Update TimeKeeper Source of Truth"],"bugs":["Improve reliability of customMasker","Stringify now returns an empty string if failed to transform"],"security":[],"supportedOperatingSystems":null,"description":"v1.267.0 Features Upgrade to web-vitals v4 Upgrade to web-vitals v4.  For more info, please see https://github.com/GoogleChrome/web-vitals/blob/main/docs/upgrading-to-v4.md. Improve notifications of stylesheet status for session replay The agent reports internal metadata about the status of stylesheets on the page when collecting session replay information. This process was spotty and the logic has been improved to make the metadata more consistent.  The ability to turn off \"inlining\" the stylesheets has been removed, as that behavior is required for the UI to re-render the replay. Add soft navigations to Browser-Agent loader Add the Soft Navigations limited preview feature to the default Browser Agent loader accessible via NPM. Update TimeKeeper Source of Truth Update the Agent's TimeKeeper to evaluate a timestamp provided directly by the consumer instead of a generic Date header, which should provide more control stability and granularity to the time synchronization processes. Bug fixes Improve reliability of customMasker The customMasker method of the Session Replay feature has been fixed to be more reliable with DOM elements that do not fit web-standards, as to not throw errors when processing.  Initial Replay harvests will now be gated until a valid snapshot is taken. Stringify now returns an empty string if failed to transform An internal mechanism used to convert objects to strings would return undefined if an exception was thrown during the process. This could lead downstream users of that method to throw errors if they expected the output to be a string. The utility method now always returns a string. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.267.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 118-128, Edge 117-127, Safari 16-17, and Firefox 119-129. For mobile devices, v1.267.0 was built and tested for Android OS 14 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.267.0","eolDate":"2025-09-23"},{"agent":"browser","date":"2024-09-16","downloadLink":null,"version":"1.266.0","features":["Removing long task"],"bugs":["Remove nullish coalescing inside getter"],"security":[],"supportedOperatingSystems":null,"description":"v1.266.0 Features Removing long task Previously, an agent configuration turned on reporting of long tasks that took over 50ms. This functionality is being shelved effective this agent version. The configuration will no longer do anything. Bug fixes Remove nullish coalescing inside getter Removed a nullish coalescing assignment in a class getter -- which even though is claimed to be supported -- behaved badly in old versions of webkit browsers like Safari 15, some versions of Mobile Safari, and old chromium iOS browsers that use webkit. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.266.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 118-128, Edge 117-127, Safari 16-17, and Firefox 119-129. For mobile devices, v1.266.0 was built and tested for Android OS 14 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.266.0","eolDate":"2025-09-16"},{"agent":"browser","date":"2024-09-06","downloadLink":null,"version":"1.265.1","features":[],"bugs":["Disable websocket wrapping"],"security":[],"supportedOperatingSystems":null,"description":"v1.265.1 Bug fixes Disable websocket wrapping Fix websocket problems and breakage in application using other third party libraries dealing with sockets by removing the wrapping introduced in version 1.265.0. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.265.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 117-127, Edge 117-127, Safari 16-17, and Firefox 118-128. For mobile devices, v1.265.1 was built and tested for Android OS 14 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.265.1","eolDate":"2025-09-06"},{"agent":"browser","date":"2024-08-30","downloadLink":null,"version":"1.265.0","features":["Standardize Feature Buffering Behavior","Add WebSocket wrapper and supportability metrics","Configure Session Replay to wait for DOMContentLoaded","removing internal barrel exports","add payload size evaluation to generic events feature"],"bugs":["fix duplicative log payloads on unload","Ensure drain target is a valid event emitter before subscribing","relative timestamps in session trace","Updated Logging API function"],"security":["apply obfuscation rules to session trace"],"supportedOperatingSystems":null,"description":"v1.265.0 Features Standardized feature buffering behavior We've established one pattern for holding data before harvests and for retry logic that can be shared by the all of the features. This reduces bespoke logic per feature and establishes a pattern for use with future architecture changes. Add WebSocket wrapper and supportability metrics We added a wrapper to detect usage of WebSockets. This is intended to help evaluate viability of the agent tracking WebSocket data and its overall mechanism usage patterns. Configure session replay to wait for DOMContentLoaded We decreased the time spent waiting by triggering the session replay mutation observer wrapping on the DOMContentLoaded event instead of the previously used window load event. This ensures wrapping is completed before the load chain. Removed internal barrel exports We reduced the loader bundle size by reworking the internal source code imports and exports. Added payload size evaluation to generic events feature We've changed data harvesting, where now harvesting occurs early when the payload reaches 64kb and and will harvests from sending if it exceeds the 1MB ingest limit. Bug fixes Fix duplicative log payloads on unload Ensure agent clears buffer on page navigation unload harvests to prevent duplicative payloads from being sent. Ensure drain target is a valid event emitter before subscribing Ensure that the drain target is a valid event emitter to ensure that the .on method exists and will not throw errors. Telative timestamps in session trace In rare cases where PerformanceNavigationTiming API is undefined, session trace timing nodes would be reported using epoch timestamp values instead of relative timestamp values. This would result in a broken session trace experience in New Relic. If the PerformanceNavigationTiming API is unavailable, the epoch timestamps will now be converted to relative timestamps accounting for user clock difference with New Relic servers. Updated logging API function Fix an issue where the logging API method would always result in an uninitialized agent warning and would not capture the log. Security fixes Apply obfuscation rules to session trace A bug was introduced in version 1.259.0 where session trace data was not being processed through configured obfuscation rules. This fix ensures session trace data is properly obfuscated. Potential areas where un-obfuscated data could be added to the session trace: When calling newrelic.addToTrace, the name of the trace event is a string provided by the customer. When capturing session trace nodes for ajax requests, the node will contain the current page URL excluding query parameters and hash fragments. When capturing resources being loaded on the page (javascript and css files), the session trace node will contain the URL of the resource excluding query parameters and hash fragments. When a user clicks a link on the page containing an href that includes a hash fragment and does not result in a hard page load, the href value of the link will be captured in a session trace node. When the browser agent captures an error on the page, the message of the error is included in a session trace node. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.265.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 117-127, Edge 116-126, Safari 16-17, and Firefox 118-128. For mobile devices, v1.265.0 was built and tested for Android OS 14 and iOS Safari 16-18.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.265.0","eolDate":"2025-08-30"},{"agent":"browser","date":"2024-08-06","downloadLink":null,"version":"1.264.0","features":["Create generic events feature with 1,000 event limit","Report Page Actions with Generic Events Feature"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.264.0 Features Create generic events feature with 1,000 event limit Create a feature that will normalize, aggregate and harvest all generic events. Report Page Actions with Generic Events Feature Report all customer PageAction data utilizing the new Generic Events feature. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.264.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 116-126, Edge 116-126, Safari 16-17, and Firefox 117-127. For mobile devices, v1.264.0 was built and tested for Android OS 9-14 and iOS Safari 16-17.5.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.264.0","eolDate":"2025-08-06"},{"agent":"browser","date":"2024-07-25","downloadLink":null,"version":"1.263.0","features":["Optimize bundle size with warning codes","Shut down agent if improperly configured"],"bugs":["Prevent agent using invalid date header"],"security":[],"supportedOperatingSystems":null,"description":"v1.263.0 Features Optimize bundle size with warning codes Decrease bundle size by converting static strings to warning codes with an accompanying link to a web resource. Shut down agent if improperly configured Shut down initialization of the agent if improperly configured. Agents must be provided a valid licenseKey and applicationID at runtime. Bug Fixes Prevent agent using invalid date header Shut down the agent when unable to read a correctly formatted date header for the page view event harvest. This prevents harvesting data with wildly inaccurate timestamps. This should only happen with third-party or non-agent code has tampered with the ajax response headers. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.263.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 116-126, Edge 116-126, Safari 16-17, and Firefox 117-127. For mobile devices, v1.263.0 was built and tested for Android OS 9-14 and iOS Safari 16-17.5.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.263.0","eolDate":"2025-07-25"},{"agent":"browser","date":"2024-07-09","downloadLink":null,"version":"1.262.0","features":["logging bundle optimization"],"bugs":["Release backlog memory when features are blocked by RUM","address call to stopTimer on undefined scheduler","safeguard api calls"],"security":[],"supportedOperatingSystems":null,"description":"v1.262.0 Features logging bundle optimization Improve the bundle size of the logging feature by moving non-critical pieces to the aggregation portion of the agent code. Bug fixes Release backlog memory when features are blocked by RUM Plug a memory leak in Session Trace and other features. When entitlement or enable flag from RUM request returns a 0 for a feature, the agent will now release the reference to the events buffer under that feature so it can be garbage collected. address call to stopTimer on undefined scheduler Fixed an issue where session trace stopping on one tab while the same site was opening in another tab could result in the second tab throwing an exception when attempting to call stopTimer() on an undefined harvest scheduler. safeguard api calls Adding a safeguard to prevent an exception from being thrown when browser agent APIs are called before the agent is fully initialized. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.262.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 116-126, Edge 116-126, Safari 16-17, and Firefox 117-127. For mobile devices, v1.262.0 was built and tested for Android OS 9-14 and iOS Safari 16-17.5.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.262.0","eolDate":"2025-07-09"},{"agent":"browser","date":"2024-07-01","downloadLink":null,"version":"1.261.2","features":[],"bugs":["recordReplay will restart replays on same session page loads"],"security":[],"supportedOperatingSystems":null,"description":"v1.261.2 Bug fixes recordReplay will restart replays on same session page loads Patch a case of recordReplay not restarting session replay. Customers can now programatically continue the session replay after a hard page navigation. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.261.2 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 116-126, Edge 116-126, Safari 16-17, and Firefox 117-127. For mobile devices, v1.261.2 was built and tested for Android OS 9-14 and iOS Safari 16-17.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.261.2","eolDate":"2025-07-01"},{"agent":"browser","date":"2024-06-26","downloadLink":null,"version":"1.261.1","features":[],"bugs":["Unhandled promise rejection for session import"],"security":[],"supportedOperatingSystems":null,"description":"v1.261.1 Bug fixes Unhandled promise rejection for session import Fixing an issue where an unhandled promise rejection could be thrown from the agent when using the npm package if the session manager async chunk get blocked or fails to setup a session. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.261.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-125, Edge 116-126, Safari 16-17, and Firefox 116-126. For mobile devices, v1.261.1 was built and tested for Android OS 9-14 and iOS Safari 16-17.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.261.1","eolDate":"2025-06-26"},{"agent":"browser","date":"2024-06-25","downloadLink":null,"version":"1.261.0","features":["Pass logging API args as object for better extensibility","Logging feature harvesting and optimizations","Create logging feature","Add Logging Configurations","Add wrapLogger API method for wrapping 3rd party loggers","Add Logging API entry points and central handler"],"bugs":["Reading finish of null in SPA","dedup pre-load ajax requests","Prevent session reset triggers from harvesting session trace data"],"security":[],"supportedOperatingSystems":null,"description":"v1.261.0 Features Pass logging API args as object for better extensibility Pass logging API arguments an object to allow for better extensibility later without requiring so many arguments for options. Logging feature harvesting and optimizations Allow the new logging feature to process and send harvests while optimizing log capture mechanisms Create logging feature Add basis of logging feature for handling and buffering observed log data Add Logging Configurations Add default configuration settings to be used for upcoming logging feature Add wrapLogger API method for wrapping 3rd party loggers Observe existing logging functions and report through event emitter for later processing when capturing log events. Add Logging API entry points and central handler Add Logging API interface and central handling mechanism as customer interface for capturing logging data Bug fixes Reading finish of null in SPA Patch cases wherein SPA .end() can throw exception on a finished or full interaction. .end still force finishes an interaction. dedup pre-load ajax requests Fixing an issue where ajax requests made prior to the page load event would be reported as part of the SPA data and as standard ajax events. Prevent session reset triggers from harvesting session trace data Prevent Session Traces from \"final\" harvesting if the session identifiers change during a page life-cycle, such as when a session becomes stale and resets. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.261.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-125, Edge 116-126, Safari 16-17, and Firefox 116-126. For mobile devices, v1.261.0 was built and tested for Android OS 9-14 and iOS Safari 16-17.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.261.0","eolDate":"2025-06-25"},{"agent":"browser","date":"2024-05-16","downloadLink":null,"version":"1.260.1","features":[],"bugs":["Undefined stns in blob Trace"],"security":[],"supportedOperatingSystems":null,"description":"v1.260.1 Bug fixes Undefined stns in blob Trace Fix an instance of undefined error in Session Trace feature introduced in v1.259.0. Harvest will now no longer be attempted if there are no trace nodes to send. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.260.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-124, Edge 115-123, Safari 16-17, and Firefox 116-125. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-124 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.260.1","eolDate":"2025-05-16"},{"agent":"browser","date":"2024-05-13","downloadLink":null,"version":"1.260.0","features":["Improve time stamping of page view events"],"bugs":["Adjust session entity to not race between tabs","Add internal error handler to session replay recorder"],"security":[],"supportedOperatingSystems":null,"description":"v1.260.0 Features Improve time stamping of page view events Improved the time stamping of page view events for subsequent page loads when sessions are enabled. Subsequent page loads will use the calculated New Relic server time to make the timestamp more accurate. Bug fixes Adjust session entity to not race between tabs Allow individual tabs loading simultaneously to calculate New Relic server time. Add internal error handler to session replay recorder Fixed a bug where internal errors caused by the internal session replay recording library from being reported as customer errors. They now report as internal errors. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.260.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-124, Edge 115-123, Safari 16-17, and Firefox 116-125. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-124 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.260.0","eolDate":"2025-05-13"},{"agent":"browser","date":"2024-05-08","downloadLink":null,"version":"1.259.0","features":["Migrate Session Traces to Use Blob Consumer with Feature Flags"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.259.0 Features Migrate Session Traces to Use Blob Consumer with Feature Flags Create migration path for Session Traces to use the Blob Consumer, which aligns Session Traces and Session Replays and allows for better ingest scaling. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.259.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-124, Edge 115-123, Safari 16-17, and Firefox 116-125. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-124 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.259.0","eolDate":"2025-05-08"},{"agent":"browser","date":"2024-05-07","downloadLink":null,"version":"1.258.2","features":[],"bugs":["Prevent noticeError() API from running if not given an argument"],"security":[],"supportedOperatingSystems":null,"description":"v1.258.2 Bug fixes Prevent noticeError() API from running if not given an argument Short circuit the execution of the noticeError API if an argument is not supplied Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.258.2 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-124, Edge 115-123, Safari 16-17, and Firefox 116-125. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-124 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.258.2","eolDate":"2025-05-07"},{"agent":"browser","date":"2024-05-07","downloadLink":null,"version":"1.258.1","features":[],"bugs":["Improve Error Casting","Run inside cross-origin iframes for firefox/safari","Exclude data url requests as captured AJAX events","Session trace nodes de-duplication","Remove API start()'s features param"],"security":[],"supportedOperatingSystems":null,"description":"v1.258.1 Bug fixes Improve Error Casting Improve detection of line and column to allow errors that throw without a stack -- such as some chrome errors -- to still get basic error location information Run inside cross-origin iframes for firefox/safari Resolve a bug that prevented the agent from running in cross-origin iFrames for Firefox and Safari due to how the browsers implement context security. Exclude data url requests as captured AJAX events Do not report XMLHttpRequest or fetch calls made for data urls. The event and metric created for data urls are sparse and unhelpful, so they are no longer being captured or sent. Session trace nodes de-duplication Remove duplicated error and event nodes in traces. Each error noticed by the JS errors feature will now only be 1 node instead of 3. Each occurrence of any event fired on for a DOM node or XMLHttpRequest object is pared down to 1 instead of being directly proportional to the number of subscribed listeners. Remove API start()'s features param The start() method in agent API no longer accepts an argument. It will forcibly start all features that were marked autoStart: false in the configuration that has not yet started when it is called. If page_view_event had this property set to false, the agent will not send anything until start is called. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.258.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-124, Edge 115-123, Safari 16-17, and Firefox 116-125. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-124 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.258.1","eolDate":"2025-05-07"},{"agent":"browser","date":"2024-04-29","downloadLink":null,"version":"1.258.0","features":["Restructure AJAX Aggregate","Maintain calculated NR server time for session","Add harvestId to Session Replay payloads","JSErrors timestamped per harvest"],"bugs":["Clean up xhrWrappable","Prevent null CLS"],"security":[],"supportedOperatingSystems":null,"description":"v1.258.0 Features Restructure AJAX Aggregate Re-organization of the Ajax feature as part of agent maintenance. This has no expected impact on its functionality. Maintain calculated NR server time for session This update changes the agent to store the New Relic server time calculated when session tracking is enabled. This will prevent the agent from re-calculating server time on subsequent page loads, ensuring the timeline view of events in New Relic is more accurate. Add harvestId to Session Replay payloads Adds a unique harvest ID to Session Replay payloads to support better indexing and querying on the platform. JSErrors timestamped per harvest JSErrors that happen multiple times throughout a page's life will now receive a timestamp unique to the agent harvest cycle instead of consistently reporting the timestamp of the first occurrence of that error. Bug fixes Clean up xhrWrappable Remove xhrWrappable which is an old variable checking for addEventListener on XHR. It is expected to have no compatibility impact on modern standard frameworks or browsers. Prevent null CLS Add a check to prevent null and undefined web-vitals values from being reported. Support statement New Relic recommends upgrading the agent regularly to ensure you get the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.258.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 115-123, Edge 114-123, Safari 16-17, and Firefox 116-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.258.0","eolDate":"2025-04-29"},{"agent":"browser","date":"2024-04-18","downloadLink":null,"version":"1.257.0","features":["Session Replay preload optimizations","Decorate errors with hasReplay individually"],"bugs":["Session replay preload without autoStart","JSEerrors harvest hasReplay decoration","Agent class type declarations","Soft navigations memory leak on harvest"],"security":[],"supportedOperatingSystems":null,"description":"v1.257.0 Features Session Replay preload optimizations Optimize early load error detection to mitigate certain race conditions when transitioning from error mode to full mode. Decorate errors with hasReplay individually Change the error aggregation method to consider errors with a hasReplay flag separately to ensure timestamps are always correct. Decorate each aggregation set with hasReplay directly instead of a request-level query param Bug fixes Session replay preload without autoStart In scenarios where SessionReplay was configured to not auto start and the user already has a replay recording from a previous page or after a page reload, calls to the start('session_replay') API made too soon after agent initialization would be ignored. JSEerrors harvest hasReplay decoration In scenarios where the SessionReplay feature was preloaded but a recording was never started, errors happening on the page would be improperly decorated with the hasReplay flag. Agent class type declarations Fixing incorrect type declarations for the constructor parameters of the Agent class. Soft navigations memory leak on harvest Address a couple scenarios of memory being not released by the soft navigation harvest cycle. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.257.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 114-123, Edge 114-123, Safari 16-17, and Firefox 115-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.257.0","eolDate":"2025-04-18"},{"agent":"browser","date":"2024-04-15","downloadLink":null,"version":"1.256.1","features":[],"bugs":["Revert \"Generate PTID in Agent\""],"security":[],"supportedOperatingSystems":null,"description":"v1.256.1 Bug fixes Revert \"Generate PTID in Agent\" Revert a change causing Trace to begin harvest even when the rum flag given is 0. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.256.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 114-123, Edge 114-123, Safari 16-17, and Firefox 115-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.256.1","eolDate":"2025-04-15"},{"agent":"browser","date":"2024-04-11","downloadLink":null,"version":"1.256.0","features":["Generate PTID in Agent","Allow unmasking elements with nr-unmask selectors","Adjust Session Replay Error Tracking"],"bugs":["stabilize timestamp corrections","Resume Page Focus Now Checks Session State"],"security":[],"supportedOperatingSystems":null,"description":"v1.256.0 Features Generate PTID in Agent Generate PTID in agent instead of in RUM response.  This allows PageView events to be decorated with a page trace ID. Allow unmasking elements with nr-unmask selectors Add custom masking mechanism to allow unmasking elements with nr-unmask class selectors and data-nr-unmask data attribute selectors Adjust Session Replay Error Tracking Adjust when errors are decorated with session replay identifiers to more closely match actual recording data Bug fixes stabilize timestamp corrections Ensure Session Replay timestamps are only ever adjusted once and fix correction factor to alleviate timeOrigin inconsistencies Resume Page Focus Now Checks Session State Check session state when resuming focus to an actively instrumented page.  This ensures that stale sessions are caught before invoking other feature-level methods. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.256.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 114-123, Edge 114-123, Safari 16-17, and Firefox 115-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.256.0","eolDate":"2025-04-11"},{"agent":"browser","date":"2024-04-04","downloadLink":null,"version":"1.255.0","features":["Adjust SR Timestamps to NR Server Time","Send CLS as timing node additionally","Update agent to use new relic server time","Switch web vitals library to attribution build"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.255.0 Features Adjust session replay timestamps to New Relic server time Adjust all timestamps sent as session replay event nodes to represent New Relic server time for accuracy in querying against adjacent but separate events in the timeline such as errors, page views, and interactions. Send CLS as timing node additionally cumulativeLayoutShift can now be queried for (with that as its timingName) as its own PageViewTiming event in New Relic. The additional attribution are a part of these events, and the values are more reflective of true end-session CLS scores. Update agent to use new relic server time Update the agent to use New Relic server time as the timestamp for harvested page action and error data. Switch web vitals library to attribution build Report extra attributes for each vital using web vital library's attribution build. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.255.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 113-123, Edge 113-122, Safari 16-17, and Firefox 114-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.255.0","eolDate":"2025-04-04"},{"agent":"browser","date":"2024-03-26","downloadLink":null,"version":"1.254.1","features":[],"bugs":["Server Timing - Remove reliance on performance API"],"security":[],"supportedOperatingSystems":null,"description":"v1.254.1 Bug fixes Server Timing - Remove reliance on performance API Removing reliance on the browser resources API for the calculation of New Relic server time. On site with many resource requests, there was a small chance that the RUM network call would be flushed from the resources API cache before we could capture it and calculate server time. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.254.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 113-123, Edge 113-122, Safari 16-17, and Firefox 114-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.254.1","eolDate":"2025-03-26"},{"agent":"browser","date":"2024-03-25","downloadLink":null,"version":"1.254.0","features":["Standardize all feature behavior to wait for RUM response","maintain a harvestCount for use later with harvestId","Add rum-response metadata handler","Calculate New Relic time in the agent"],"bugs":["Remove webpack imports in npm package"],"security":[],"supportedOperatingSystems":null,"description":"v1.254.0 Features Standardize all feature behavior to wait for RUM response Force features to wait for entitlement checks from the rum call before processing buffered data. maintain a harvestCount for use later with harvestId Add a counter which increments after every harvest. This will be used in a future effort to curate a unique harvest ID for API paging purposes. Add rum-response metadata handler The initial connect call can now supply browser app metadata. This adds a handler to store and use that metadata for future harvests. Calculate New Relic time in the agent Migrating the process of time-stamping harvested data to the agent. The agent uses the date and time reported by the ingest pipeline during the RUM call as well as browser network and timing stats to derive a server time offset that can be applied to harvested data as event occur. This improves the ability to visualize the harvested data on a timeline within the New Relic UI. Bug fixes Remove webpack imports in npm package Transitioning certain module imports so that the default import is for the npm version of the module instead of the cdn or webpack version. This should completely eliminate all references to webpack globals when using the npm package. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.254.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 113-122, Edge 113-122, Safari 16-17, and Firefox 114-122. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-122 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.254.0","eolDate":"2025-03-25"},{"agent":"browser","date":"2024-03-13","downloadLink":null,"version":"1.253.0","features":["Soft Navigations trial","Apply deny list to ajax metrics","Preload the Session Replay recorder when properly configured","Isolate observation context per agent"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.253.0 Features Soft Navigations trial Introducing a lighter and simplified version of the existing spa feature that tracks soft navigations. This new feature still sends BrowserInteraction events, but the duration and finishing of those interactions have been redefined. As a replacement, it ought to reduce complexity and integration issues around the existing spa and exhibit better and faster performance. Apply deny list to ajax metrics The ajax deny list has historically only applied to the collection of ajax events and not ajax metrics. With this feature, the deny list will also be applied to the collection and reporting of ajax timeslice metric data. If an ajax request matches an entry in the deny list, both events and metrics will be blocked from being collected in the agent. This feature will be behind a feature flag to assess impact before final complete rollout. Thanks to community member @Wrhector  for contributing this feature. Preload the session replay recorder when properly configured Load the session replay recorder module before the page load when configured to do so.  This will increase visibility for recordable data for customers who have opted in to the behavior. Isolate observation context per agent Initial implementation of an isolated observation context per agent running on the same page. This reduces the modification of instances of globals like events and instead each agent will track its own observation context internally. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.253.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 113-122, Edge 113-122, Safari 16-17, and Firefox 114-122. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-122 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.253.0","eolDate":"2025-03-13"},{"agent":"browser","date":"2024-02-29","downloadLink":null,"version":"1.252.1","features":[],"bugs":["Fix webpack imports in npm package","Page load after session timeouts don't start new session"],"security":[],"supportedOperatingSystems":null,"description":"v1.252.1 Bug fixes Fix webpack imports in npm package Fixing some import overrides in our NPM package build to prevent imports existing that include code reliant on webpack globals. This will resolve the error Uncaught ReferenceError: __webpack_require__ is not defined when using the NPM package in a project that does not use webpack. Page load after session timeouts don't start new session When a session expires or becomes inactive while the user does not have the page open and they re-open the page, that is now treated as a new session. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.252.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 112-121, Edge 112-121, Safari 16-17, and Firefox 113-122. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-121 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.252.1","eolDate":"2025-02-28"},{"agent":"browser","date":"2024-02-12","downloadLink":null,"version":"1.252.0","features":["add types mappings for esm distribution","Report config changes away from default state for UX improvement","Create more granular metrics about stylesheet fix success","align browser reported uncaught syntax errors","Capture Internal Metrics for Session Replay Configurations"],"bugs":["Add safe logic to snapshots","Fix adblock memory leak"],"security":[],"supportedOperatingSystems":null,"description":"v1.252.0 Features Add types mappings for esm distribution Adding typescript types mappings for the ESM distribution in the npm package. Report config changes away from default state for UX improvement Detect if the default config values have been altered at runtime.  This is useful to evaluate what the reasonable defaults are across a customer base over time to provide a better UX. Create more granular metrics about stylesheet fix success Utilize a finer granularity when collecting success metrics on local stylesheet fixes for Session Replay compatibility. Align browser reported uncaught syntax errors Aligning the data reported for uncaught syntax errors across modern browsers. Chrome specifically fails to include the file name and line number in instances of SyntaxError. This could also cause issue in the New Relic error inbox where Chrome syntax errors were not being properly grouped. Capture Internal Metrics for Session Replay Configurations Capture supportability metrics sounding Session Replay configuration usage to improve user experiences around configuration of the agent's Session Replay feature. Bug fixes Add safe logic to snapshots Safe-guarded a race condition where an asynchronous call to fix a stylesheet could trigger the agent to try to force a snapshot after it has already stopped recording due to a visibility change. Fix adblock memory leak Fixed memory leaks caused by request resolve failure (e.G. due to adblocker). Thanks to community member @Joe-Degler   for contributing this fix. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.252.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 112-121, Edge 112-120, Safari 16-17, and Firefox 113-121. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-121 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.252.0","eolDate":"2025-02-12"},{"agent":"browser","date":"2024-01-29","downloadLink":null,"version":"1.251.1","features":[],"bugs":["Pass unload options to simultaneous harvests in session replay","Fix deferred Session Replay payloads"],"security":[],"supportedOperatingSystems":null,"description":"v1.251.1 Bug fixes Pass unload options to simultaneous harvests in session replay Pass unload options to simultaneous harvests in session replay  to allow all calls to utilize sendBeacon when unloading. Fix deferred session replay payloads Force agent to send preloaded session replay payloads if present at load time. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.251.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 111-120, Edge 111-120, Safari 16-17, and Firefox 112-121. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-120 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.251.1","eolDate":"2025-01-29"},{"agent":"browser","date":"2024-01-24","downloadLink":null,"version":"1.251.0","features":["Session Replay - Detect Non-Inlined Stylesheets"],"bugs":["Bubble Up API Methods to Top-Level Instance For NPM","Add fallback for currentBufferTarget"],"security":[],"supportedOperatingSystems":null,"description":"v1.251.0 Features Session Replay - Detect Non-Inlined Stylesheets Add check for invalid stylesheet inlining and asynchronously fetch the stylesheet contents for future payloads. Bug fixes Bubble Up API Methods to Top-Level Instance For NPM Fix an issue where the NPM wrapping of the agent would not bubble the APIs up to the top-level of the instance, causing invalid warnings to log. Add fallback for currentBufferTarget Add a fallback to the currentBufferTarget for cases where the preload buffer has been cleared Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.251.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 111-120, Edge 111-119, Safari 16-17, and Firefox 112-120. For mobile devices, v1.251.0 was built and tested for Android Chrome 100-120 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.251.0","eolDate":"2025-01-24"},{"agent":"browser","date":"2024-01-09","downloadLink":null,"version":"1.250.0","features":["Add a flag to note that a payload occurred during a replay","Session Replay Dynamic Loading"],"bugs":["TraceId generation regression (non-random trace ids)"],"security":[],"supportedOperatingSystems":null,"description":"v1.250.0 Features Add a flag to note that a payload occurred during a replay Added a flag to mark harvests as having occurred during an active session replay. This will aid cross-feature querying in NR1. Session Replay Dynamic Loading Allow Session Replay modules to load earlier in the page lifecycle if a replay is ongoing Bug fixes TraceId generation regression (non-random trace ids) Fixes a regression which caused all trace ids generated to end in a 0. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.250.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 111-119, Edge 111-118, Safari 16-17, and Firefox 111-119. For mobile devices, v1.250.0 was built and tested for Android Chrome 100-119 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.250.0","eolDate":"2025-01-09"},{"agent":"browser","date":"2023-12-14","downloadLink":null,"version":"1.249.0","features":["Allow empty string for Session Replay masking value"],"bugs":["loader missing sub-resource integrity hashes","Fix API Warning Messages","traceids not random when using `webcrypto`"],"security":[],"supportedOperatingSystems":null,"description":"v1.249.0 Features Allow empty string for session replay masking value Allow empty strings to be provided for session replay masking values, which helps the UI/API provide sane fallbacks for never-set values. Bug fixes loader missing sub-resource integrity hashes Sub-resource integrity hashes were not being properly generated and included in the loader for async chunks related to session replay. This would cause a warning to appear in the browser console, but would not block those chunks from loading. This would have only affected customers taking part in the session replay limited preview. Fix API warning messages Fix warning messages given by API calls made before the agent has initialized. Traceids not random when using webcrypto Fix non-random hexadecimal generation when using the webcrypto api, which in turn creates non-random traceIds, that always end in 00. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. We no longer support older releases when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases roll out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.249.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 110-119, Edge 110-118, Safari 15-16, and Firefox 110-119. For mobile devices, v1.249.0 was built and tested for Android Chrome 100-119 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.249.0","eolDate":"2024-12-14"},{"agent":"browser","date":"2023-11-16","downloadLink":null,"version":"1.248.0","features":["Report enduser.id with Session Replay"],"bugs":["Fix issue with errors forcefully triggering session traces"],"security":[],"supportedOperatingSystems":null,"description":"v1.248.0 Features Report enduser.id with Session Replay Report enduser.id if set with Session Replay data to improve faceting the Session Replay UX Bug fixes Fix issue with errors forcefully triggering session traces Fixing an issue where an uncaught error or calls to the noticeError API would force session trace to begin collecting and harvesting data, even though session trace and session replay were disabled via the RUM response. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.248.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 110-119, Edge 110-118, Safari 15-16, and Firefox 110-119. For mobile devices, v1.248.0 was built and tested for Android Chrome 100-119 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.248.0","eolDate":"2024-11-16"},{"agent":"browser","date":"2023-11-14","downloadLink":null,"version":"1.247.0","features":["Session Replay API","Add relative timestamps to Session Replay payloads","Expose library versions used to capture session replay data","Add basic support for deferring the browser agent loader script","Enable SRI and nonce attributes for async chunks","Add session durationMs to Session Replay payloads"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.247.0 Features Session Replay API Add two new APIs for controlling session replay behaviors: newrelic.recordReplay() newrelic.pauseReplay() Add relative timestamps to Session Replay payloads Add relative timestamps to Session Replay payloads to allow for server-side clock skew adjustments and improve the API pagination experience. Expose library versions used to capture session replay data Expose library versions used to capture session replay data, which helps sync visualizations in the UI Replayer components across version migrations. Add basic support for deferring the browser agent loader script Add basic support for deferring the browser agent loader script, including exposing a DOM-level event for external use to indicate the agent is successfully running. Enable SRI and nonce attributes for async chunks Additional JavaScript resources loaded by the agent will now include a SHA512 integrity hash and will respect the presence of a nonce token on scripts loaded on the page. This gets the agent closer to being able to run within an environment with a more secure content security policy. Add session durationMs to Session Replay payloads Add current session's running duration to all outgoing session replay payloads for use with ingest estimations Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.247.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 109-119, Edge 109-118, Safari 15-16, and Firefox 109-119. For mobile devices, v1.247.0 was built and tested for Android Chrome 100-119 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.247.0","eolDate":"2024-11-14"},{"agent":"browser","date":"2023-10-31","downloadLink":null,"version":"1.246.1","features":[],"bugs":["Fix missing type declarations"],"security":[],"supportedOperatingSystems":null,"description":"v1.246.1 Bug fixes Fix missing type declarations Fixing missing type declarations in the feature utilities that show up when skibLibCheck is not enabled in the tsconfig. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.246.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 109-118, Edge 109-117, Safari 15-16, and Firefox 109-118. For mobile devices, v1.246.1 was built and tested for Android Chrome 100-118 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.246.1","eolDate":"2024-10-31"},{"agent":"browser","date":"2023-10-23","downloadLink":null,"version":"1.246.0","features":["Replace url parsing with URL class","Add network info to all page view timing events"],"bugs":["Add feature flag support for Browser Interactions","Add first harvest of session flags to RUM and Trace"],"security":[],"supportedOperatingSystems":null,"description":"v1.246.0 Features Replace url parsing with URL class Replacing internal url parsing logic with the browser built-in URL class. Add network info to all page view timing events Add client network information to all PageViewTiming events in New Relic. The attributes currently only exist on LCP and FI event types and will now be reported with all others such as load and pagehide events. Bug fixes Add feature flag support for Browser Interactions Implementing a feature flag that will disable the fix 315 . That fix was specifically around Angular, React, and Vue applications with routes containing network calls resulting in browser interactions missing those ajax calls. This feature flag should not be enabled unless specifically instructed to do so by support. Add first harvest of session flags to RUM and Trace Mark the first RUM call and Session Trace harvest of any given session so that it becomes queryable in New Relic. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.246.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 109-118, Edge 109-117, Safari 15-16, and Firefox 109-118. For mobile devices, v1.246.0 was built and tested for Android Chrome 100-118 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.246.0","eolDate":"2024-10-23"},{"agent":"browser","date":"2023-10-18","downloadLink":null,"version":"1.245.0","features":["Allow boolean values in setCustomAttribute","Detect GraphQL operation names and types in AJAX calls","Removing worker build"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.245.0 Features Allow boolean values in setCustomAttribute Allow boolean values to be supplied to newrelic.setCustomAttribute() API calls. Detect GraphQL operation names and types in AJAX calls Detect GraphQL operation names and types in AJAX calls and decorate AJAX events with that information. Removing worker build Removing the worker build from the agent. The worker build was a never released custom build of the agent that could be imported into web and service workers. The agent will continue to support running in those contexts but customers will need to use the NPM package to create their own customized agent for those contexts. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.245.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 108-117, Edge 108-116, Safari 15-16, and Firefox 109-118. For mobile devices, v1.245.0 was built and tested for Android Chrome 100-117 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.245.0","eolDate":"2024-10-18"},{"agent":"browser","date":"2023-10-10","downloadLink":null,"version":"1.244.0","features":["Bump rrweb to 2.0.0.11 and make constant dynamic at build time","Add Session Replay configurations to collect inline assets","Ensure 15 second minimum error buffer when possible"],"bugs":["Fix invalid timestamps","Isolate browser interaction node"],"security":[],"supportedOperatingSystems":null,"description":"v1.244.0 Features Bump rrweb to 2.0.0.11 and make constant dynamic at build time Bump rrweb dependency version to 2.0.0.11 and include in Session Replay payload metadata dynamically Add Session Replay configurations to collect inline assets Add Session Replay configurations to collect inline images, stylesheets, and fonts for private applications. Ensure 15 second minimum error buffer when possible Add a two-step sliding window to ensure 15-30 second buffer time for applicable error replays Bug fixes Fix invalid timestamps Ensure that Session Replay node injection does not cause desynchronized timestamps for blob payloads Isolate browser interaction node Improving context isolation for events the SPA feature tracks to allow for multiple agent bundles to live on the same page. This is only intended for internal New Relic usage at this time and should not affect customers. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.244.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 108-117, Edge 108-116, Safari 15-16, and Firefox 108-117. For mobile devices, v1.244.0 was built and tested for Android Chrome 100-117 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.244.0","eolDate":"2024-10-10"},{"agent":"browser","date":"2023-10-04","downloadLink":null,"version":"1.243.1","features":[],"bugs":["Improve Session Replay abort metric reliability"],"security":[],"supportedOperatingSystems":null,"description":"v1.243.1 Bug fixes Improve Session Replay abort metric reliability Pass Session Replay abort metrics through the event emitter buffer to guarantee that early lifecycle failures are captured by the Metrics feature for prioritizing future improvements. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.243.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 108-117, Edge 108-116, Safari 15-16, and Firefox 108-117. For mobile devices, v1.243.1 was built and tested for Android Chrome 100-117 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.243.1","eolDate":"2024-10-04"},{"agent":"browser","date":"2023-10-04","downloadLink":null,"version":"1.243.0","features":["Do not report ajax nodes in session traces if in deny list","Remove deprecated API inlineHit"],"bugs":["Re-update assets proxy to accept host URL strings","Adjust Session Replay meta and timestamps","Tap session entity into storage api for changes across tabs","Set Session Replay first chunk flags more reliably"],"security":[],"supportedOperatingSystems":null,"description":"v1.243.0 Features Do not report ajax nodes in session traces if in deny list Prevent ajax nodes derived from calls found in the ajax deny list from populating Session Trace payloads Remove deprecated API inlineHit Removing the browser agent API inlineHit. This API was deprecated in 2014 and is no longer supported or used by newer versions of the browser agent. Bug fixes Re-update assets proxy to accept host URL strings Previously, the agent expected the protocol (for example, https://) to be included in the configuration input. However, we have since decided to allow the protocol to be excluded, as the proxy beacon field only accepts a host string. Adjust Session Replay meta and timestamps Ensure that payloads can not ends with a meta node or start with a snapshot node for consistency in UI render queries. Tap session entity into storage API for changes across tabs Tap session entity into storage event listener for stateful changes across tabs. Set Session Replay first chunk flags more reliably Add logic to set firstChunk flag and replay mode on new replays more reliably. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.243.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 108-117, Edge 108-116, Safari 15-16, and Firefox 108-117. For mobile devices, v1.243.0 was built and tested for Android Chrome 100-117 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.243.0","eolDate":"2024-10-04"},{"agent":"browser","date":"2023-09-25","downloadLink":null,"version":"1.242.0","features":["Add messaging about Session Replay abort behavior","Applying new cache headers to assets"],"bugs":["Drain event emitter even when feature fails to initialize","Validation of SR configurations"],"security":[],"supportedOperatingSystems":null,"description":"v1.242.0 Features Add messaging about Session Replay abort behavior Add messaging to signal why a replay aborted, which could happen for a number of reasons. Applying new cache headers to assets Released browser agent assets will now be delivered with a 1 year cache header. This will allow user's browsers to cache the async chunks the agent loads for much longer and eliminate performance recommendations found in synthetic performance tools like Lighthouse. This will be applied retroactively to all released versions of the agent. Bug Fixes Drain event emitter even when feature fails to initialize A failure to import and initialize a feature could block the agent from draining data out of the event emitter, which prevents the agent from making any successful calls.  This fix allows the event emitter to drain even when an individual feature fails to initialize. Validation of SR configurations Update the block selector, mask selector, and mask input setters to handle empty strings. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.242.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 108-117, Edge 108-116, Safari 15-16, and Firefox 108-117. For mobile devices, v1.242.0 was built and tested for Android Chrome 100-117 and iOS Safari 15.5-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.242.0","eolDate":"2024-09-25"},{"agent":"browser","date":"2023-09-18","downloadLink":null,"version":"1.241.0","features":["Add SR entrypoint to NPM ahead of LP","Removing hash from chunk asset name"],"bugs":["Final harvest does not happen when initial RUM call fails"],"security":[],"supportedOperatingSystems":null,"description":"v1.241.0 Features Add SR entrypoint to NPM ahead of LP Add SR instrumentation entrypoint to NPM ahead of the upcoming Limited Preview window Removing hash from chunk asset name Removing the hash from the chunk asset file name. This will allow internal and external automation to predict the file name of each asset chunk as long as the loader type and version number is known. Bug Fixes Final harvest does not happen when initial RUM call fails Fixes the final harvest behavior in cases when the RUM request fails. The initial request is meant to act as a gateway for the agent to start reporting data, and its failure should result in the agent not sending anything. As of previous version, the metrics and page view timing features do not follow this rule, and that has been corrected. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.241.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 107-116, Edge 107-115, Safari 15-16, and Firefox 108-116. For mobile devices, v1.241.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.241.0","eolDate":"2024-09-18"},{"agent":"browser","date":"2023-09-12","downloadLink":null,"version":"1.240.0","features":["Origin of agent webpack chunks now changeable","Add session trace metadata params","Add SR to pro and spa builds (only runs for LP customers)","Centralize web vitals timings"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.240.0 Features Origin of agent webpack chunks now changeable Allow the agent to operate through a proxy. The agent needs to be able to fetch its source code and send analytics to a different domain, and this solves the former. NPM is not affected. Add session trace metadata params Add first timestamp and node count information to session trace payloads for optimization in UI experiences. Add SR to pro and spa builds (only runs for LP customers) Add the SR feature to Pro and Pro+Spa builds of the agent. The session replay library shipping with this version of the browser agent is in limited preview  and is not turned on by default. To use the feature, users will need to be part of the limited preview customer group and configure their browser application settings in the UI. Centralize web vitals timings Centralize web vitals timings to be accessible from any part of the agent. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.240.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 107-116, Edge 107-115, Safari 15-16, and Firefox 108-116. For mobile devices, v1.240.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.240.0","eolDate":"2024-09-12"},{"agent":"browser","date":"2023-09-01","downloadLink":null,"version":"1.239.1","features":["Add best effort to detect Ajax events before instantiation","Add mode to enable agent to not harvest until user consent","Remove allow_bfcache flag","Remove old supportability metrics"],"bugs":["Fix issue with leaking event listeners","Issues with types resolution","Fix internal release process"],"security":[],"supportedOperatingSystems":null,"description":"v1.239.1 Features Add best effort to detect Ajax events before instantiation Add a \"best effort\" at detecting ajax events that may have happened on the page before the agent was instantiated by utilizing the ResourceTiming browser API. Add mode to enable agent to not harvest until user consent Add ability for customers to wait to start harvesting. This behavior will utilize a configuration setting in tandem with an API call to trigger features to begin harvesting. Remove allow_bfcache flag Removes unused code which still relied on the window unload event. Going forward, the only method the agent will use to monitor potential end of page session will be visibility change in accordance with modern web practice. Remove old supportability metrics Removing supportability metrics that are no longer needed including polyfill detection, bfcache usage, body and query bytes sent count, and custom attributes size. Bug Fixes Fix issue with leaking event listeners Fixing an issue where session timeout would result in rewrapping global event handlers. For instances where the site would be open for long periods of time, such as kiosks, this would eventually result in a degradation in event handler performance. Issues with types resolution Fixing issues with typescript throwing errors when trying to resolve the typings for individual features with \"moduleResolution\": \"node\" set in the tsconfig.json. \"moduleResolution\": \"nodenext\" and \"moduleResolution\": \"node16\" will enable typescript use of the exports field of our package.json but could also break other libraries and forces developers to change all local imports to include file extensions. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.239.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 107-116, Edge 107-115, Safari 15-16, and Firefox 108-116. For mobile devices, v1.238.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.239.1","eolDate":"2024-09-01"},{"agent":"browser","date":"2023-08-16","downloadLink":null,"version":"1.238.0","features":["Reducing the agent chunk count","Add API: setApplicationVersion"],"bugs":["Capture potential missing tail data for session trace","Fix distributed tracing handling of empty string fetch parameter","Typo in type declarations"],"security":[],"supportedOperatingSystems":null,"description":"v1.238.0 Features Reducing the agent chunk count Reducing the number JavaScript files the agent loads asynchronously down to a single file. This means customer's users will now only need to load one additional JavaScript file for the New Relic Browser Agent to operate. This additional JavaScript file will continue to only be loaded upon the document \"load\" event. This change not only reduces the number of additional requests the agent must make but also reduces the amount of code that must be loaded by eliminating duplication. Add API: setApplicationVersion Add api method to top-level interface to allow the setting of application version across all outgoing payloads Bug Fixes Capture potential missing tail data for session trace Send buffered session trace data in certain cases when it's being discarded at the tail end of a captured session. Fix distributed tracing handling of empty string fetch parameter Fixing an issue with distributed tracing that would result in an exception within the agent when fetch is called with an empty string as the first parameter. Typo in type declarations Fixing typos made in the browser and micro agent API declarations. This includes adding internal test cases for those types to ensure this issue does not happen again. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.238.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 106-114, Edge 106-113, Safari 15-16, and Firefox 107-113. For mobile devices, v1.238.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.238.0","eolDate":"2024-08-16"},{"agent":"browser","date":"2023-08-02","downloadLink":null,"version":"1.237.1","features":[],"bugs":["SPA feature respects ajax deny_list for fetch","prevent dollar symbol only variable names","Undefined deny list ignores block internal","Fix serialization issue with array data"],"security":[],"supportedOperatingSystems":null,"description":"v1.237.1 Bug Fixes SPA feature respects ajax deny_list for fetch The SPA feature will now properly respect the Ajax deny list and block internal settings for fetch calls. In prior versions, the SPA feature only consulted the Ajax deny list for XMLHttpRequest calls. prevent dollar symbol only variable names Prevent the build process of the agent from creating minified variable names that only contain the dollar symbol. If such a variable is immediately followed by an ampersand, as could be the case in a minified logic block, it could be picked up by string replacement logic applied to outgoing HTML within their server. Undefined deny list ignores block internal In cases where the customer's configuration does not include the init.ajax.deny_list property, the agent would not properly account for the init.ajax.block_internal setting and would not block Ajax events for internal agent network calls. Fix serialization issue with array data Update the harvester to account for array payloads, which in niche cases could convert array payloads to indexed objects. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. Browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.237.1 of the browser agent was built for and tested against these browsers and version ranges: Chrome 106-114 Edge 106-113 Safari 15-16 Firefox 106-113. For mobile devices, v1.237.1 was built and tested for Android Chrome 100 and iOS Safari 15.2-16.2.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.237.1","eolDate":"2024-08-02"},{"agent":"browser","date":"2023-07-28","downloadLink":null,"version":"1.237.0","features":["Stop reporting ajax events going to same beacon","Add warning for large payloads","reduce jserrors wrapping and remove onerror use"],"bugs":["Remove fetch keep-alive unhandled rejection","prevent invalid error stack traces","Defining agent api methods for ts types","Fix potential property of undefined errors"],"security":[],"supportedOperatingSystems":null,"description":"v1.237.0 Features Stop reporting ajax events going to same beacon Network requests made to the same hostname as the agent's reporting beacon endpoint are no longer captured, by default. As an example, outgoing XHRs to the bam.nr-data.net URL where analytic data is typically sent would not reflectively record itself. Add warning for large payloads Add warning for large payloads, which is typically caused by excessive custom attribute sizes. reduce jserrors wrapping and remove onerror use Replaces the use of the onerror global function with addEventListener to capture errors that go unhandled by customer code. This does not change how unhandled promise rejects are captured. Additional wrappings for events, timers, and animation fames have been removed in favor of capturing unhandled errors using a global event listener. Bug Fixes Remove fetch keep-alive unhandled rejection Eliminate an unhandled promise rejection error caused by fetch failure in agent EoL logic. prevent invalid error stack traces Removing the instantiation of the Error class in the jserrors feature for instances where a non-Error value is thrown from customer's code. In such cases, an Error instance would be created and the stack trace would point back to the agent code as the source. This causes confusion since it makes it seem like the agent code is throwing the error when that is not the case. Instead, the internal UncaughtError class will be used and no stack trace will exist. Defining agent api methods for ts types Updating the type interface of the Agent and MicroAgent classes to properly expose the agent API methods in the generated typescript types. Fix potential property of undefined errors Patch a couple of areas that can yield reading property of undefined or null errors in the RUM call and jsonp wrapper. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.237.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 106-114, Edge 105-113, Safari 15-16, and Firefox 106-113. For mobile devices, v1.237.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-15.5.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.237.0","eolDate":"2024-07-28"},{"agent":"browser","date":"2023-06-27","downloadLink":null,"version":"1.236.0","features":["Expose MicroLoader in the npm package","Remove img, jsonp, and xhrGet methods"],"bugs":["Handle chunk load promise error introduced in 1.235.0","Fix illegal invocation error on final harvest"],"security":[],"supportedOperatingSystems":null,"description":"v1.236.0 Features Expose MicroLoader in the npm package The npm package now exposes an entry-point called MicroLoader, which may be used to instantiate multiple agents on one page. This loader type, which is smaller than the Lite loader, captures a distinct PageView event per instance but does not auto-instrument the page. Instead, manual API calls may be used to capture JavaScriptError and PageAction events via the noticeError and addPageAction methods. Remove img, jsonp, and xhrGet methods Unused agent network methods have been removed. All data transmitted by the agent will now default to using XMLHttpRequest POST calls except for data transmitted during a visibility change or page unload. Visibility changes and page unloads will use sendBeacon with a fallback to fetch with keepalive. For browsers that do not support sendBeacon, the final data transmission will use XMLHttpRequest POST. Bug Fixes Handle chunk load promise error introduced in 1.235.0 Starting in 1.235.0, loading the agent in browsers with strict privacy settings resulted in an uncaught error in a promise. This error has been handled, and chunk load failures again result only in a warning. Fix illegal invocation error on final harvest An issue from 1.234.0 has been addressed in which an illegal invocation error could occur during a final harvest as a result of calling addPageAction and passing window.location as an argument before a navigation. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.236.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 105-114, Edge 105-113, Safari 15-16, and Firefox 105-113. For mobile devices, v1.236.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-15.5.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.236.0","eolDate":"2024-06-27"},{"agent":"browser","date":"2023-06-20","downloadLink":null,"version":"1.235.0","features":["Add error mode to session trace","Minor feature class changes to support testing new features","Decorate error objects to facilitate future UI experiences","Use new shared session for Session Trace feature","Remove unused data from session trace requests"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.235.0 Features Add error mode to session trace Session-enabled traces now have an \"error mode\" capability in which the feature lies dormant until an exception is thrown. Upon the error, the past 30 seconds of data is retained and sent, and the feature becomes fully activated again. Minor feature class changes to support testing new features Feature class internals and testing architecture have been augmented to support testing new experimental features in progress. Decorate error objects to facilitate future UI experiences Error payloads will now be decorated with a real timestamp and feature flags to facilitate error usages in future NR1 UI experiences. Use new shared session for Session Trace feature Session Trace becomes more aligned with the new interpretation of a user's session defined as part of the upcoming and experimental Session Replay feature. When the session tracking setting is enabled, the Session Trace feature will now use stored session info to make capturing decisions. Remove unused data from session trace requests Data defined by APM agents and the customer will no longer be included in session trace requests since the data is not consumed downstream and can result in 414 errors in cases where the custom data would cause the URL to exceed the maximum length of 8,192 bytes. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.235.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 105-114, Edge 105-113, Safari 15-16, and Firefox 104-113. For mobile devices, v1.235.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-15.5.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.235.0","eolDate":"2024-06-20"},{"agent":"browser","date":"2023-06-02","downloadLink":null,"version":"1.234.0","features":["Migrate RUM network call from GET to POST"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.234.0 Features Migrate RUM network call from GET to POST When making its initial network call (the RUM call), the agent will now use the POST method instead of the GET method and will not depend on JSON-P to trigger follow-on events. This change facilitates setting custom attributes in the request body, reducing the likelihood of long GET URLs. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.234.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 104-114, Edge 104-113, Safari 15-16, and Firefox 104-113. For mobile devices, v1.234.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-15.5.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.234.0","eolDate":"2024-06-02"},{"agent":"browser","date":"2023-05-31","downloadLink":null,"version":"1.233.1","features":[],"bugs":["Address bug affecting XHR harvest re-schedule"],"security":[],"supportedOperatingSystems":null,"description":"v1.233.1 Bug Fixes Address bug affecting XHR harvest re-schedule A early return condition in the harvest rescheduling logic in version 1.233.0 was preventing Ajax event harvest from being rescheduled in cases where no data had accumulated. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.233.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 104-113, Edge 104-113, Safari 15-16, and Firefox 104-113. For mobile devices, v1.233.1 was built and tested for Android Chrome 100 and iOS Safari 15.2-15.5.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.233.1","eolDate":"2024-05-31"},{"agent":"browser","date":"2023-05-26","downloadLink":null,"version":"1.233.0","features":["Capture metrics for usage of MooTools and certain polyfills","Update agent internals in early preparation for new features"],"bugs":["Address \"configurable\" warnings arising from user-agent module","Refactor usage of Array.from to address MooTools conflict","Ensure runtime is preserved for late-configuration cases"],"security":[],"supportedOperatingSystems":null,"description":"v1.233.0 Features Capture metrics for usage of MooTools and certain polyfills New supportability metrics have been added to capture MooTools library usage and presence of customer-defined polyfills for certain native JavaScript features, such as function binding and ES6 Array prototype methods. Update agent internals in early preparation for new features The agent code base now contains the non-functional foundations of session replay mechanics. Note that this code is dormant and disabled. It will not download or execute until the session replay feature and its downstream dependencies are in a finished state. Bug Fixes Address \"configurable\" warnings arising from user-agent module The unused userAgent property and corresponding module have been removed from the runtime object due to \"configurable\" warnings being thrown in cases attempting to overwrite the runtime configuration. Refactor usage of Array.from to address MooTools conflict To work around a conflict with some versions of the MooTools library that mutate the native Array.from method, the agent will now use alternative methods. Ensure runtime is preserved for late-configuration cases Fix an issue where the internal runtime state of the agent was not preserved when the agent configurations were supplied after the loader had finished initializing, which caused the session to be cleared. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , v1.233.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 104-113, Edge 104-113, Safari 15-16, and Firefox 104-113. For mobile devices, v1.233.0 was built and tested for Android Chrome 100 and iOS Safari 15.2-15.5.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.233.0","eolDate":"2024-05-26"},{"agent":"browser","date":"2023-05-17","downloadLink":null,"version":"1.232.1","features":[],"bugs":["Add X-NewRelic-ID header only if defined","Identify inline stack trace URLs more precisely"],"security":[],"supportedOperatingSystems":null,"description":"v1.232.1 Bug Fixes Add X-NewRelic-ID header only if defined The agent will now set the X-NewRelic-ID header on XHR requests only when a truthy xpid value is explicitly set in the loader configuration. Previously the header was added even if undefined. Identify inline stack trace URLs more precisely URLs in JavaScriptError stack traces were sometimes misidentified as inline scripts when they shared a partial URL with the page on which the agent was loaded. The agent will now identify same-page scripts more precisely. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , version v1.232.1 of the browser agent was built for and tested against these browsers and version ranges: Chrome 104-113, Edge 104-113, Safari 15-16, Firefox 104-113. For mobile devices, v1.232.1 was built and tested for Android Chrome 100 and iOS Safari 15-15.5.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.232.1","eolDate":"2024-05-17"},{"agent":"browser","date":"2023-05-08","downloadLink":null,"version":"1.232.0","features":["Minor changes to SMs","Add query parameter supportability metrics","Allow custom error grouping","Add new stateful Session Manager"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v1.232.0 Features Minor changes to SMs Add internal metrics to track the duration of the average session, to improve estimation for future efforts. Add query parameter supportability metrics Adding supportability metrics to capture legacy network method usage, query parameter size statistics, and custom data size statistics. Allow custom error grouping The setErrorHandler method now supports applying custom fingerprints to exceptions. Events with the same fingerprint appear grouped together in the New Relic One errors inbox. Add new stateful Session Manager The agent will now manage the end-user session lifecycle statefully, across page views and tab changes. Support statement: We recommend you to upgrade the agent regularly so you get the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , version v1.232.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 104-113, Edge 104-112, Safari 15-16, Firefox 103-112; and for mobile devices, Android Chrome 100 and iOS Safari 15-15.5.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.232.0","eolDate":"2024-05-08"},{"agent":"browser","date":"2023-04-28","downloadLink":null,"version":"1.231.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v1.231.0 Omit CLS scores before web-vitals report them Initial snapshots of CLS reported as 0s attached to timing metrics will be omitted, so as to \"de-noise\" the aggregate CLS dataset. This also temporarily addresses an edge case of long loading pages potentially sending a \"final\" CLS value of 0, inaccurately. The case of a final 0 CLS when a user only navigates away from the page has also been fixed. Fix accepted argument type for all and race methods of Promise The wrapped Promise's static all and race methods now work with iterators per native implementation, rather than only arrays. Upgrade Navigation Timing API in PageView (RUM) call The performance entry data sent for PageView now uses the Navigation Timing Level 2 API over the deprecated Level 1 API. Fix typo in top-level API causing exception An an uncaught reference exception was occurring on pages with more than one initialized agent due to a typo in the name of a variable (returnsVals). Add null entry checks to certain web-vitals handlers For LCP and FID, we will exclude the performance entry info when there are no entries given by web-vitals. This had thrown exceptions. Remove previously added console logging measurements This reverses performance impacts and exceptions introduced in the prior release by serializing console API arguments. Rectify version reported by NPM agent implementations Agents installed via the NPM method will report the correct semantic version in data harvests. Fix exception when importing NPM package source code An error was occurring related to a missing environment variable when importing from the NPM package source directly (versus via the CJS/ESM packages). Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information. Consistent with our browser support policy , version v1.231.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 103-112, Edge 103-112, Safari 15-16, Firefox 103-112; and for mobile devices, Android Chrome 100 and iOS Safari 15-15.5.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.231.0","eolDate":"2024-04-28"},{"agent":"browser","date":"2023-04-10","downloadLink":null,"version":"1.230.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v1.230.0 Add persistence for custom attributes Custom attributes may now optionally be persisted between page loads via session storage. The API method setCustomAttribute now takes a third parameter, which defaults to false. When true, this boolean indicates that the provided custom attribute should be persisted in session storage and restored on subsequent page loads. Session storage is subject to the same-origin policy  of the browser. Add setUserId API A new setUserId API method is now available. It defines a custom attribute containing a specified user ID, to be included in all payloads. The setUserId API is an extension of the setCustomAttribute API and automatically persists between page loads. Fix npm package browser targets The previous npm package release included code that was not compatible with browsers in our supported browser list . The package exports will now default to code that matches our browser support list. The package will also include the source code for power users that would like more control over how the agent is built. Fix npm package exports Some dangling, unused, and non-existent imports and exports were causing issues with consuming the NPM package in some projects. These have been removed. Fix npm package import for typescript projects Fixed an issue where typescript projects attempting to import the browser agent library would not get proper auto-complete in the import statement and would receive module declaration errors. The browser agent will not use tsc to generate type definitions from the JavaScript code at build time. The package.json has been updated with appropriate type export declarations. Add error catch around sendBeacon Added error catch logic around the sendBeacon usage. In the event sendBeacon throws an error during the final harvest, the final harvest will attempt to fall back to the image data submission method. Remove array reduce polyfill Removed the array reduce polyfill in favor of the native browser array reduce method. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.230.0","eolDate":"2024-04-10"},{"agent":"browser","date":"2023-03-31","downloadLink":null,"version":"1.229.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v1.229.0 Use semantic versioning scheme The agent will now utilize semantic versioning for subsequent releases. The previous version (1228) will carry forward into 1.229.0, and so on. Use web-vitals library for internal timing calculations In an effort to align and standardize the timings the agent collects, the agent now uses the Google CWV  library to track page timings such as CLS, LCP, FCP, TTFB and more. See Core Web Vitals documentation  for more information. Ship the Browser Agent repository to NPM The Browser Agent repository will now be available as a pre-release NPM package. See @newrelic/browser-agent  for more information. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life . Release dates are reflective of the original publish date of the agent version. New Browser Agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard  for more information.","slug":"docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1.229.0","eolDate":"2024-03-31"},{"agent":"prometheus","date":"2024-12-12","downloadLink":null,"version":"1.18.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-prometheus-agent-1.15.5 nri-bundle-5.0.105","slug":"docs/release-notes/infrastructure-release-notes/prometheus-agent-release-notes/prometheus-agent-1-18-5","eolDate":"2025-12-12"},{"agent":"infrastructure","date":"2018-06-18","downloadLink":null,"version":"1.0.934","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the Windows agent has been released, fixing a security issue that allowed non-privileged users with access to the system to inject configuration arguments to the agent external plugins. Please see New Relic Security Bulletin NR18-10  for more details.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-windows-agent-10934","eolDate":"2021-06-18"},{"agent":"infrastructure","date":"2020-02-10","downloadLink":null,"version":"1.9.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Bug fixes Updated bundled nri-docker integration version to v1.1.1 . This version fixes missing Docker container metrics improving Linux cgroup path detection. This issue happened when cgroup was not mounted in the standard path /sys/fs/cgroup. Now it can discover different cgroup paths. Still cgroup PIDs (process and thread count) is not available on Kernel versions lower than 4.3 see support . Therefore column threadCount won't be available for these systems. For instance Amazon-Linux v1 runs on kernel 4.13. Fixed permissions to /tmp/nri-integrations directory while updating the agent from root mode to privileged or unprivileged mode . This changes the owner of the /tmp/nri-integrations folder, which is used by some integrations and the Infrastructure integrations SDK  to cache data. Fixed issue when running in Kubernetes where an integration configuration change provided by ConfigMap wouldn't be picked up by the agent, breaking the hot config reload feature for integrations.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-197","eolDate":"2023-02-10"},{"agent":"infrastructure","date":"2020-01-29","downloadLink":null,"version":"1.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Added IPv6 support during hostname resolution via DNS. In verbose mode, more detailed logging during hostname resolution. Bug fixes Fixed a bug from the new integrations' engine added in the version 1.8.0 , which caused any JSON line larger than 64 KB to be ignored. This does not affect to the integrations that are configured with the format prior to 1.8.0, which is still supported. Fixed ${config.path} replacement  in new integrations' configuration file. When an integration configuration contained a config or config_file_template section and the ${config.path} variable was used in an environment variable or command-line argument, the correct path was set only during the first execution, remaining the same for the rest of executions, even if the path changes. Fixed Linux packaging metadata. Updated the Vendor field from \"<jenkins@401c99d99b5f>\" to \"New Relic, Inc.\", fixing the problem that some customers where having on SLES v11.2 Suse, or higher, due to the \"repository vendor stickiness\", which protects apps from accidentally replacing stable versions of installed packages with experimental versions from a different repository when updating. Added extra metadata fields: License, Maintainer, URL, Description, Distribution and Summary","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-190","eolDate":"2023-01-29"},{"agent":"infrastructure","date":"2019-12-17","downloadLink":null,"version":"1.8.8","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Added \"Smart Verbose\" mode. Once enabled most recent debug messages will be shown whenever an error is logged. The maximum number of cached entries are configured through the \"smart_verbose_mode_entry_limit\" attribute (defaults to 1000). To enable \"Smart Verbose\" mode, set the verbose config value to 2. Auto-discovery enhancements: (will update this soon)","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-188","eolDate":"2022-12-17"},{"agent":"infrastructure","date":"2019-12-12","downloadLink":null,"version":"1.8.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Implemented disconnect call when the agent detects that the host is shutting down.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-184","eolDate":"2022-12-12"},{"agent":"infrastructure","date":"2020-01-15","downloadLink":null,"version":"1.8.32","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Now the Infrastructure agent, when running on Linux, can collect Docker container metrics  like CPU, memory, I/O and network. This feature is enabled by default for all supported Linux OSs . Please, ensure the host meets the requirements . The new integration config files  now support the when section. It allows you to control the execution of an integration if a given file exists. Here's an example: The agent will execute ssh-integration only if the /var/run/sshd.pid file exists. Bug fixes Agent service wasn't stopping / restarting properly on upstart-based Linux distributions. In Integration config files: Dollar symbols were unintentionally being expanded into environment variables. Before, pa$$word would have been expanded to pa${}${}word; this behavior has been corrected. Improved NFS  support. Read and write bytes per second were not being correctly set to 0, resulting JSON marshalling errors.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1832","eolDate":"2023-01-15"},{"agent":"infrastructure","date":"2020-01-02","downloadLink":null,"version":"1.8.23","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Inventory body reporting the agent entity ID. Bug fixes Supporting Overlay File Systems in the storage samples. Before agent 1.8.23, a device mapped from multiple overlay folders might not be reported as the parent partition but as any folder mounting it. Now the agent reports the parent mount folder. Removed confusing warning log message from the integrations' engine ignoring legacy configuration files.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1823","eolDate":"2023-01-02"},{"agent":"infrastructure","date":"2019-12-05","downloadLink":null,"version":"1.8.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Fixed command channel URL for EU Preventing certain combinations of new integrations configuration (introduced in 1.8.0) crashing the agent","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-182","eolDate":"2022-12-05"},{"agent":"infrastructure","date":"2019-12-30","downloadLink":null,"version":"1.8.19","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Removed recurring warning message flooding the logs which was introduced in release v.1.8.4","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1819","eolDate":"2022-12-30"},{"agent":"infrastructure","date":"2019-12-19","downloadLink":null,"version":"1.8.14","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Added \"Host Not Reporting\" alert condition support, in order to avoid getting alerted on expected cluster downscaling. Further details: https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/i...","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1814","eolDate":"2022-12-19"},{"agent":"infrastructure","date":"2026-09-03","downloadLink":null,"version":"1.80.3","features":[],"bugs":["Allowed mount path validation during safe directory checks"],"security":["updated google.golang.org/grpc from 1.82.1 to 1.83.1  to fixes CVE-2026-84304"],"supportedOperatingSystems":null,"description":"Notes 🛡️ Security updates Updated google.golang.org/grpc to 1.83.1 to resolve security vulnerability CVE-2026-84304 in #2328 🐞 Bug fixes Allowed mount path validation during safe directory checks #2325 Support statement: A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Infrastructure agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1803","eolDate":"2027-09-03"},{"agent":"infrastructure","date":"2026-09-01","downloadLink":null,"version":"1.80.2","features":[],"bugs":[],"security":["bump `flex` version to v1.18.12 fixing [CVE-2026-56854](https://github.com/advisories/GHSA-gjhq-gjfw-99mq)"],"supportedOperatingSystems":null,"description":"Notes 🛡️ Security notices Updated flex to version v1.18.12 to resolve security vulnerability CVE-2026-56854  in #2323 Support statement: A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Infrastructure agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1802","eolDate":"2027-09-01"},{"agent":"infrastructure","date":"2026-08-31","downloadLink":null,"version":"1.80.1","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes 🛡️ Security notices Bumped http://golang.org/x/crypto to v0.55.0 fix security CVE-2026-56854  in #2321 🐞 Bug fixes Extended the WMI fallback to retrieve Queue Length in #2312 Retry Start-Service on SCM races and validate license key before starting in #2307 Support statement: A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Infrastructure agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1801","eolDate":"2027-08-31"},{"agent":"infrastructure","date":"2026-08-24","downloadLink":null,"version":"1.80.0","features":["Added Azure Key Vault as another databind secret source"],"bugs":[],"security":["Fixed a local privilege escalation vulnerability caused by predictable Fluent Bit config directory reuse"],"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.65.3 . Changed Added Azure Key Vault as another databind secret source. #2304 Fixed a local privilege escalation vulnerability caused by predictable Fluent Bit config directory reuse. #2306 Bumped Go to 1.26.6 to fix multiple Go stdlib CVEs. #2308 Updated embedded OHI versions (nri-docker, nri-flex, nri-winservices, nri-prometheus) to fix CVEs. #2316","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1800","eolDate":"2027-08-24"},{"agent":"infrastructure","date":"2019-12-03","downloadLink":null,"version":"1.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features New integrations engine , which coexists with the previous engine for backwards-compatibility and smoother transition. Featuring: Simpler setup of integrations, with fewer files and fewer mandatory properties. In some cases, you only have to set the integration name to enable it. Flexible configuration of integrations via command-line arguments, environment variables, or external files. Ability to group different integrations in the same configuration file. Hot reload of integrations, so you can add a new integration or change its configuration without needing to restart the Infrastructure agent. Timeouts when an integration does not respond before a user-specified time. The integration process is killed and restarted. This can also be disabled. Smooth migration from the old integrations engine. Please read the documentation about Infrastructure integration configuration file specifications for agent v1.8.0 or higher  for a complete description of how to start using the new integrations engine, as well as a detailed description and examples of the new configuration options.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-180","eolDate":"2022-12-03"},{"agent":"infrastructure","date":"2026-08-10","downloadLink":null,"version":"1.79.0","features":["Added support for ignoring default integration locations via disable_plugin_default_dir_scan","Made environment variables used by Agent Control public","Added OCI tag support to match AWS tags (Phase 1 + Phase 2)","Enabled NRIA_DISABLE_PLUGIN_DEFAULT_DIR_SCAN by default for Agent-Control-managed agents","Removed nri-flex from agent-control artifacts"],"bugs":["Restored missing job permissions for release and canary workflows"],"security":["Fixed a remote code execution vulnerability caused by path traversal","Added explicit permissions to GitHub Actions workflows to reduce token scope","Bumped google.golang.org/grpc from 1.79.3 to 1.82.1","Bumped embedded OHI versions (nri-docker, nri-flex) to fix known CVEs","bump vulnerable dependencies flagged by Trivy scan"],"supportedOperatingSystems":null,"description":"Notes 🛡️ Security notices Fixed a remote code execution vulnerability caused by path traversal in #2292 Added explicit permissions to GitHub Actions workflows to reduce token scope in #2232 Bumped google.golang.org/grpc from 1.79.3 to 1.82.1 in go.mod in #2296 Bumped embedded OHI versions (nri-docker, nri-flex) to fix known CVEs in #2302 bump vulnerable dependencies flagged by Trivy scan in #2301 🚀 Enhancements Added support for ignoring default integration locations via disable_plugin_default_dir_scan in #2290 Made environment variables used by Agent Control public in #2293 Added OCI tag support to match AWS tags (Phase 1 + Phase 2) in #2295 Enabled NRIA_DISABLE_PLUGIN_DEFAULT_DIR_SCAN by default for Agent-Control-managed agents in #2300 Removed nri-flex from agent-control artifacts in #2291 🐞 Bug fixes Restored missing job permissions for release and canary workflows in #2303 Support statement: A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Infrastructure agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1790","eolDate":"2027-08-10"},{"agent":"infrastructure","date":"2026-07-15","downloadLink":null,"version":"1.78.1","features":[],"bugs":[],"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.65.3 . Changed Updated the embedded newrelic-fluent-bit-output plugin to v3.7.0 (Windows) to resolve security vulnerabilities CVE-2026-39820, CVE-2026-42499, CVE-2026-33814, CVE-2026-42501, CVE-2026-33811, and CVE-2026-42504. #2283 Added unit tests for the custom health check port. #2286","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1781","eolDate":"2027-07-15"},{"agent":"infrastructure","date":"2026-07-13","downloadLink":null,"version":"1.78.0","features":[],"bugs":["fix panic due to double close","fix bind local server to only localhost by default"],"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.65.3 . Changed Fixed a panic condition caused by a double close operation. 2270 Fixed the local server binding behavior to default strictly to localhost. 2271 Dependency updates: Updated newrelic/nri-flex to v1.18.8. #2278 Updated newrelic/nri-winservices to v1.5.3. #2279 Updated newrelic/nri-prometheus to v2.29.4. #2276 Updated newrelic/nri-docker to v2.8.1. #2277 Updated the core agent dependency to v1.26.5. #2275 Updated newrelic-fluent-bit-output to v3.7.0 (Linux) to resolve security vulnerabilities CVE-2026-39820, CVE-2026-42499, CVE-2026-33814, CVE-2026-42501, CVE-2026-33811, and CVE-2026-42504. #2280","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1780","eolDate":"2027-07-13"},{"agent":"infrastructure","date":"2026-06-30","downloadLink":null,"version":"1.77.1","features":[],"bugs":[],"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.65.1 . Changed updated golang.org/x/net v0.55.0 in #2265 updated alpine docker tag to v3.24 in #2263 updated containerd version to v1.7.33 in #2269","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1771","eolDate":"2027-06-30"},{"agent":"infrastructure","date":"2026-06-22","downloadLink":null,"version":"1.77.0","features":["Added support for ubuntu 26 Resolute Raccoon"],"bugs":[],"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.65.1 . Changed Updated dependency newrelic/nri-prometheus to v2.29.3 in #2264 Added support for Ubuntu 26.04 LTS (Resolute Raccoon) in #2224 Updated the newrelic/nri-flex dependency to v1.18.6 in #2266","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1770","eolDate":"2027-06-22"},{"agent":"infrastructure","date":"2026-06-11","downloadLink":null,"version":"1.76.2","features":["Added configurable log endpoint"],"bugs":[],"security":["Bumped Go version from 1.26.3 to 1.26.4 to address CVE-2026-42504, CVE-2026-27145 and CVE-2026-42507","Bumped net module - golang.org/x/net - Go Packages  to v0.54.0","Bumped newrelic fluent bit output version to 3.6.0 and fluent-bit to 5.0.6","Bumped nri-docker to v2.7.3, nri-flex to v1.18.5, nri-winservices to v1.5.2, nri-prometheus to v2.29.2 to address CVE-2026-42504, CVE-2026-27145 and CVE-2026-42507"],"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.65.0 . Changed Updated Go version from 1.26.3 to 1.26.4 in#2259 Updated net module - golang.org/x/net - Go Packages to v0.54.0 in #2257 Updated New Relic Fluent Bit output version to 3.6.0 and Fluent Bit to 5.0.6 in #2258 Added configurable log endpoint in #2255 Updated integration versions in #2261","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1762","eolDate":"2027-06-11"},{"agent":"infrastructure","date":"2026-06-01","downloadLink":null,"version":"1.76.1","features":[],"bugs":["Fixed an issue where set-service-account failed for local users"],"security":["Bumped containerd to version 1.7.32 to address CVE-2026-46680","Bumped nri-flex to version 1.18.4 to address CVE-2026-45570"],"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1 . What's Changed Bugs Fixed an issue where set-service-account failed for local users in #2247 . Security Bumped containerd to version 1.7.32 to address the CVE-2026-46680 vulnerability in #2250 . Bumped nri-flex to version 1.18.4 to address the CVE-2026-45570 vulnerability in #2252 . Full Changelog : https://github.com/newrelic/infrastructure-agent/compare/1.76.0...1.76.1","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1761","eolDate":"2027-06-01"},{"agent":"infrastructure","date":"2026-05-25","downloadLink":null,"version":"1.76.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1 . Changed feat: support Unicode.Encoding option for tail input plugin for fluent-bit in #2231 Full Changelog : 1.75.0...1.76.0","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1760","eolDate":"2027-05-25"},{"agent":"infrastructure","date":"2019-11-25","downloadLink":null,"version":"1.7.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Fixed issue that caused long running integrations to continue running after the agent was stopped.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-176","eolDate":"2022-11-25"},{"agent":"infrastructure","date":"2026-05-19","downloadLink":null,"version":"1.75.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1 . Added Add OCI IMDS v2 endpoint support (Note: no fall-back from v2 to v1) in #2238 Changed chore(deps): update dependency newrelic/nri-docker to v2.7.2 in #2229 chore(deps): update dependency newrelic/nri-winservices to v1.5.1 in #2241 chore(deps): update dependency newrelic/nri-prometheus to v2.29.1 in #2240 chore(deps): update dependency newrelic/nri-flex to v1.18.3 in #2239 chore: bump Go version to 1.26.3 in #2243","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1750","eolDate":"2027-05-19"},{"agent":"infrastructure","date":"2019-11-21","downloadLink":null,"version":"1.7.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Added new config options: file_devices_ignored, allowed_list_process_sample","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-175","eolDate":"2022-11-21"},{"agent":"infrastructure","date":"2026-05-11","downloadLink":null,"version":"1.74.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.64.0 . Changed Updated dependency newrelic/nri-flex to v1.18.2 to address CVE-2026-29181  #2235","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1744","eolDate":"2027-05-11"},{"agent":"infrastructure","date":"2026-05-07","downloadLink":null,"version":"1.74.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.64.0 . Bug fixes Security Fix (Windows): Resolved an unquoted search path vulnerability (BinaryPathName) that could trigger EDR warnings or block installation. Recommended for all Windows users on versions 1.73.x or 1.74.x. #2230","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1743","eolDate":"2027-05-07"},{"agent":"infrastructure","date":"2026-05-04","downloadLink":null,"version":"1.74.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.64.0 . Changed Updated New Relic Fluent Bit output to version 3.5.1. #2226 Updated nri-flex to v1.18.1. #2228","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1742","eolDate":"2027-05-04"},{"agent":"infrastructure","date":"2026-04-22","downloadLink":null,"version":"1.74.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.63.0 . Changed update go version to v1.25.9 in #2223 update dependency newrelic/nri-winservices to v1.5.0 in #2223 update dependency newrelic/nri-prometheus to v2.29.0 in #2223 update dependency newrelic/nri-flex to v1.18.0 in #2223 update dependency newrelic/nri-docker to v2.7.0 in #2223","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1741","eolDate":"2027-04-22"},{"agent":"infrastructure","date":"2026-04-14","downloadLink":null,"version":"1.73.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.64.0 . Changed Updated dependency nri-docker to 2.6.10, dependency nri-flex to v1.17.7 and dependency docker to v29 in #2220 Built Docker images for infrastructure-agent for Windows in #2202 Updated Windows image release workflow in #2213 Security Addresses CVE-2026-34040","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1731","eolDate":"2027-04-14"},{"agent":"infrastructure","date":"2026-03-31","downloadLink":null,"version":"1.73.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.63.0 . Added feat:NewRelic Infrastructure Agent Least Privileged Service Account Support on Windows (#2152 ) This release introduces comprehensive support for running the Infrastructure agent under least-privileged service accounts on Windows: Upgrade preserves service account: On upgrade, the installer now detects and preserves the existing service logon account (for example, a custom domain or gMSA account) instead of resetting it to LocalSystem. Permissions on the app data directory are automatically re-granted to the preserved account. Fresh install uses LocalSystem by default: New installations continue to register the service under LocalSystem. Use set-service-account.ps1 (new companion script) post-install to switch to a least privileged account. Supports local accounts, standard domain accounts and Group Managed Service Accounts (gMSA). Also supports the credentials stored in Windows Credential Manager. Rollback safety: A marker file is written before service creation so the MSI rollback action only removes services created by the current run — it won't delete a pre-existing service during a failed upgrade. Debug logging: Installation now writes a timestamped debug log (newrelic_installer_debug.log) making troubleshooting easier. Impact: No breaking changes for existing installations using the default SYSTEM account. The new parameters are fully optional. Changed Updated nri-winservices to v1.4.6 in #2207 Updated nri-prometheus to v2.28.0 in #220","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1730","eolDate":"2027-03-31"},{"agent":"infrastructure","date":"2026-03-24","downloadLink":null,"version":"1.72.9","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.63.0 . Security Updated google.golang.org/grpc to v1.79.3 to address CVE-2026-33186 . Updated Go to v1.25.8 to address CVE-2026-25679  and CVE-2026-27142 .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1729","eolDate":"2027-03-24"},{"agent":"infrastructure","date":"2026-03-12","downloadLink":null,"version":"1.72.8","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.63.0 . Security Address CVE-2026-22184","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1728","eolDate":"2027-03-12"},{"agent":"infrastructure","date":"2026-03-05","downloadLink":null,"version":"1.72.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.63.0 . Changed Updated dependency newrelic/nri-winservices to 1.4.4 in #2196 Removed all the EOL OS support in #2176 Updated dependency newrelic/nri-flex to 1.17.5 in #2197","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1727","eolDate":"2027-03-05"},{"agent":"infrastructure","date":"2026-02-26","downloadLink":null,"version":"1.72.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1 . Changed Update fluent-bit version to 4.2.2 for Windows in #2192","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1726","eolDate":"2027-02-26"},{"agent":"infrastructure","date":"2026-02-13","downloadLink":null,"version":"1.72.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1 . Changed Updated the Fluent Bit plugin to version 3.4.0 for RHEL 8.4","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1724","eolDate":"2027-02-13"},{"agent":"infrastructure","date":"2026-02-11","downloadLink":null,"version":"1.72.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1 . Changed Updated the Go version to 1.25.7 Security Addresses vulnerabilities","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1723","eolDate":"2027-02-11"},{"agent":"infrastructure","date":"2026-02-05","downloadLink":null,"version":"1.72.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1 . Changed Updated dependency newrelic/nri-prometheus to v2.27.6 in #2177 Updated dependency newrelic/nri-flex to v1.17.3 in #2180 Updated dependency newrelic/nri-winservices to v1.4.2 in #2181 Updated dependency newrelic/nri-docker to v2.6.7 in #2182 Updated the go version to 1.25.6 in #2183 Security Addressed High Vulnerabilities CVE-2025-61726 and CVE-2025-61728","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1722","eolDate":"2027-02-05"},{"agent":"infrastructure","date":"2026-01-29","downloadLink":null,"version":"1.72.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1 . Added Added logging_http_client_timeout configuration option to control HTTP client timeout (in seconds) for the New Relic fluent-bit output plugin in #2167 Added upload schema for RHEL10 in #2171 Changed Make win_network_interface_v2 flag true by default in #2173 Updated min version for pkg-tests in #2172 Security Addressed Critical Vulnerability - CVE-2025-15467 and High Vulnerability - CVE-2025-69419","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1721","eolDate":"2027-01-29"},{"agent":"infrastructure","date":"2026-01-27","downloadLink":null,"version":"1.72.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1 . Added Added support for RHEL10 in #2169 Changed Updated newrelic_plugin_version in #2170","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1720","eolDate":"2027-01-27"},{"agent":"infrastructure","date":"2026-01-07","downloadLink":null,"version":"1.71.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1 . Fixed Fixed transmitBytesPerSecond showing zero during high traffic on Windows (NR-502872) in #2166 To enable this fix, you must set the win_network_interface_v2  configuration option to true. This option uses 64-bit counters instead of 32-bit counters for network metrics on Windows.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1714","eolDate":"2027-01-07"},{"agent":"infrastructure","date":"2025-12-11","downloadLink":null,"version":"1.71.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.1 . Changed Updated alpine docker tag to v3.23 in #2158 Updated go version to 1.25.5 in #2161","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1713","eolDate":"2026-12-11"},{"agent":"infrastructure","date":"2025-12-08","downloadLink":null,"version":"1.71.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Security A new version of the Fluent Bit version has been released with a fix for CVE-2025-12972 ,  CVE-2025-12970 ,CVE-2025-12978 ,CVE-2025-12977 ,CVE-2025-12969  . Fluent Bit versions earlier than v4.0.13 series are affected by security vulnerabilities. The specific plugins and their associated vulnerabilities are following: Forward input plugin (in_forward) - Affected by CVE-2025-12969 Docker input plugin (in_docker) - Affected by CVE-2025-12970 File output plugin (out_file) - Affected by CVE-2025-12972 HTTP, Splunk, and Elasticsearch input plugins (in_http, in_splunk, in_elasticsearch) - Affected by CVE-2025-12978 & CVE-2025-12977 Notes: There is no secure FluentBit upstream package available for Ubuntu 16, 18, and 20. If you are running on any of these distributions, make sure you remove the affected input plugins to protect from vulnerabilities. We are working to provide secure packages for SLES 12.5 and 15.4 as soon as possible. Until we roll out the safe packages for these distributions, we recommend removing the affected plugins to protect from vulnerabilities. We are working to provide a secure package for Debian 10 as soon as possible. Until we roll out a safe package for this distribution, we recommend removing the affected plugins to protect from vulnerabilities. Changed Removed 32-bit Windows builds in #2144 Updated Fluent Bit version on Windows in #2156 Updated dependency versions in #2159 Fixed an issue where CPU performance counters didn't work on non-English systems in #2154","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1712","eolDate":"2026-12-08"},{"agent":"infrastructure","date":"2025-11-18","downloadLink":null,"version":"1.71.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Changed update dependency newrelic/nri-docker to v2.6.3 in #2142 update dependency newrelic/nri-flex to v1.17.1 in #2147 upgrade go version to 1.25.4 in #2149 update dependency newrelic/nri-prometheus to v2.27.3 in #2150","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1711","eolDate":"2026-11-18"},{"agent":"infrastructure","date":"2025-10-27","downloadLink":null,"version":"1.71.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Changed Add support for Suse 15.7 #2139 Add support for debian 13 (Trixie) #2140 Updated dependency newrelic/nri-winservices to v1.4.0 #2143 updated dependency newrelic/nri-prometheus to v2.27.2 #2130","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1710","eolDate":"2026-10-27"},{"agent":"infrastructure","date":"2019-11-13","downloadLink":null,"version":"1.7.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Log warning when OHI amount of entity attributes exceeds 240. Removed warning message when system can't find upstart integration.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-171","eolDate":"2022-11-13"},{"agent":"infrastructure","date":"2025-10-21","downloadLink":null,"version":"1.70.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.58.0 . Changed feat(oci): add Oracle Cloud-specific tags to hosts running on OCI in https://github.com/newrelic/infrastructure-agent/pull/2121 Starting with version 1.70.0, the New Relic Infrastructure agent now automatically collects metadata for VMs running in Oracle Cloud Infrastructure (OCI). The agent collects the following details: displayName host.id oci.availabilityDomain oci.region oci.compartmentId oci.shape oci.imageId You can use this metadata as tags for entity search or as attributes in NRQL queries. The host.id attribute is also used by the New Relic Cloud Integration for OCI to attach cloud metadata to the correct host entity. This feature is enabled by default to ensure consistency with existing metadata on other cloud providers. If you need to disable this feature, you can use the configuration settings disable_cloud_metadata  or disable_cloud_instance_id . Background :\nFor many years already, New Relic Infrastructure Agents installed on a VM running in AWS, Azure or GCP had the equivalent metadata detail collection, and this behavior is enabled by default. For consistency across different clouds, the OCI feature is using the same configuration items and the same default behavior.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1700","eolDate":"2026-10-21"},{"agent":"infrastructure","date":"2019-11-04","downloadLink":null,"version":"1.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Improved host shutdown detection in Windows and Linux (systemd only). This will add a new inventory source called agent/shutdown_status with the value Running or Shutdown and a corresponding event in events In Windows, the Agent will create a NamedPipe to communicate between the service process and the agent process. The NamedPipe is only writable for admin users Removed some warning when running the agent Fixed issue where enabling \"Verbose Logs\" was not working in some cases","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-170","eolDate":"2022-11-04"},{"agent":"infrastructure","date":"2019-11-13","downloadLink":null,"version":"1.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Host shutdown detection in Windows and Linux (systemd only). As part of a feature to reduce Host Not Reporting alerts, the Agent will (try to) detect if a Host is being shutdown. There will be a new Inventory entry, agent/shutdown_status, with a value of either Running or Shutdown that will later be used by Alerts to decide if a HNR alert should be triggered or not. Verbose logging enablement from newrelic-infra-ctl for Windows. Improved agent identification","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-170-0","eolDate":"2022-11-13"},{"agent":"infrastructure","date":"2025-10-01","downloadLink":null,"version":"1.69.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Changed Upgrade aws-sdk from V1 to V2 #2129 Upgrade docker api lib from v26 to v28 #2131 fix: Handle NRIA_LOG_FORMAT by using default NRIA_LOG_LEVEL #2133 Update flex, docker versions #2137 feat: Windows CPU fix for instance with multiple CPU groups (more than 64 cores) #2101","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1690","eolDate":"2026-10-01"},{"agent":"infrastructure","date":"2025-09-01","downloadLink":null,"version":"1.67.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Changed Chore: upgraded embedded integration versions in #2126","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1673","eolDate":"2026-09-01"},{"agent":"infrastructure","date":"2025-08-08","downloadLink":null,"version":"1.66.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Changed Revert \"feat: support AWS EFS mounts in storage samples\" in #2108","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1661","eolDate":"2026-08-08"},{"agent":"infrastructure","date":"2025-08-04","downloadLink":null,"version":"1.65.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Known issues : this release has a known issue with diskUsedPercent calculation because of StorageSample containing NFSv4 mount data on Linux hosts having NFSv4 mounts. Please consider one of these alternatives: Use any version higher than 1.65.5 Use any version lower than 1.65.5 A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Changed feat: support AWS EFS mounts in storage samples in #2069 chore(deps): bump golang.org/x/oauth2 from 0.20.0 to 0.27.0 in #2093 chore(deps): update nri-prometheus version to v2.27.0 in #2094","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1655","eolDate":"2026-08-04"},{"agent":"infrastructure","date":"2025-07-16","downloadLink":null,"version":"1.65.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Changed chore(deps): update dependency newrelic/nri-prometheus to v2.26.2 in #2087 chore(deps): bump github.com/containerd/containerd from 1.7.13 to 1.7.27 in #2088 chore(deps): update go dependency version to 1.23.11 in #2090","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1654","eolDate":"2026-07-16"},{"agent":"infrastructure","date":"2025-07-14","downloadLink":null,"version":"1.65.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Changed fix: Windows process handle in #2080 chore(deps): bump nri-docker to v2.5.1, nri-prometheus to v2.26.1 in #2081","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1653","eolDate":"2026-07-14"},{"agent":"infrastructure","date":"2025-06-26","downloadLink":null,"version":"1.65.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Known issues : this release has a known issue with memory (process handle) leak on Windows. Please consider one of these alternatives: Use version 1.65.3 or higher Use any version lower than 1.64.0 A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Changed chore(deps): update dependency newrelic/nri-flex to v1.16.6 in #2075","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1651","eolDate":"2026-06-26"},{"agent":"infrastructure","date":"2025-06-20","downloadLink":null,"version":"1.65.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Known issues : this release has a known issue with memory (process handle) leak on Windows. Please consider one of these alternatives: Use version 1.65.3 or higher Use any version lower than 1.64.0 A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Changed Chore: Updated dependency newrelic/nri-winservices to v1.2.0 in #2070 Chore: Updated alpine docker tag to v3.22 in #2067","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1650","eolDate":"2026-06-20"},{"agent":"infrastructure","date":"2025-05-22","downloadLink":null,"version":"1.64.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Known issues : this release has a known issue with memory (process handle) leak on Windows. Please consider one of these alternatives: Use version 1.65.3 or higher Use any version lower than 1.64.0 A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Changed Fix: Fixed hash character escaping in nri-flex YAML config parsing #2028 Fix: Removed trailing slash in mandatory prefix when path is empty #2037 Bumped fluent bit version to 3.2.10 #2045 Chore(deps): Updated dependency newrelic/nri-docker to v2.5.0 #2027 Chore(deps): Updated dependency newrelic/nri-prometheus to v2.25.0 #2016 Bumped dependency versions #2046 Chore: Upgraded go version to 1.23.8 #2059 Chore: Updated log level in #2053","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1640","eolDate":"2026-05-22"},{"agent":"infrastructure","date":"2025-04-02","downloadLink":null,"version":"1.63.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Changed chore(deps): update dependency newrelic/nri-flex to v1.16.5 #2025","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1631","eolDate":"2026-04-02"},{"agent":"infrastructure","date":"2025-03-27","downloadLink":null,"version":"1.63.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Added Add a feature flag to clean inventory cache on start in #2026","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1630","eolDate":"2026-03-27"},{"agent":"infrastructure","date":"2025-02-27","downloadLink":null,"version":"1.62.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.50.0 . Security A new version of the Fluent Bit version has been released with a fix for CVE-2024-50608 ,  CVE-2024-50609 . Previous versions of Fluent Bit in the 3.1 and 3.2  series are affected by two security vulnerabilities if customers use the OpenTelemetry input plugin  or Prometheus Remote Write input . Windows Infrastructure Agent:  upgraded to v1.62.0 Linux Infrastructure Agent: upgraded the Infrastructure agent to v1.62.0 or later, AND update Fluent Bit to v3.2.7 or later By default, New Relic does not include these plugins in our distribution of the Fluent Bit packages in any of the instrumentation packages we provide. However, in order to support customers using these plugins and mitigate any potential impact, we recommend customers to upgrade their Fluent Bit versions embedded in the Infrastructure agent log forwarder solution to version 3.2.7. Changed Improve logs when truncating event #2004 Bump New Relic APM Agent to v3.36.0 #2009 Move container errors to info #2010 Added Enable configuration of APM agent via environment variables #1947 Fixed Fix publishing of docker images #2005","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1620","eolDate":"2026-02-27"},{"agent":"infrastructure","date":"2025-01-21","downloadLink":null,"version":"1.60.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.49.0 . Added Updated workflow actions to prevent errors and warnings in execution in #1990 . Added a FIPS constraint to Ansible packaging cleanup process in #1997 . Resolved issues with unprivileged installation for FIPS in #1998 . Added a suffix for publishing FIPS Docker images in #2002 . Updated the nri-winservices to the latest version in #1999 .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1601","eolDate":"2026-01-21"},{"agent":"infrastructure","date":"2025-01-20","downloadLink":null,"version":"1.60.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.49.0 . Added Add labels from nri-winservices config  as tags on UI in #1989 . FIPS compatible packages for Linux.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1600","eolDate":"2026-01-20"},{"agent":"infrastructure","date":"2019-11-04","downloadLink":null,"version":"1.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Containers' discovery allows you executing your integrations within a set of containers that are dynamically discovered at runtime. It also allows dynamically configuring your integrations to match the container's data (labels, ports, IPs...). Currently, Docker and Fargate containers are supported. For more information, please check the container auto-discovery documentation . Secret variables binding allows you passing secrets (users, passwords...) to your integrations without having to write them as plain text in your configuration files. Currently, Vault and Amazon KMS are supported. For more information, please check the secrets management documentation .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-160","eolDate":"2022-11-04"},{"agent":"infrastructure","date":"2025-01-13","downloadLink":null,"version":"1.59.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent is now available. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.49.0 . Changed Bump nri-flex last version #1985","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1592","eolDate":"2026-01-13"},{"agent":"infrastructure","date":"2025-01-08","downloadLink":null,"version":"1.59.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent is now available. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.48.3 . Changed Bump golang.org/x/net to latest version in #1971 chore(deps): update dependency newrelic/nri-flex to v1.16.3 in #1972 chore(deps): update dependency newrelic/nri-prometheus to v2.23.0 in #1974 chore(deps): update dependency newrelic/nri-docker to v2.2.0 in #1973","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1591","eolDate":"2026-01-08"},{"agent":"infrastructure","date":"2024-12-19","downloadLink":null,"version":"1.59.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent is now available. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.48.1 . Changed Update newrelic-infra-template.yml.example in #1956 Adding fips compliant agents to prerelease on demand in #1942 Bump nri-docker, nri-flex and nri-prometheus to last versions in #1968","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1590","eolDate":"2025-12-19"},{"agent":"infrastructure","date":"2024-12-16","downloadLink":null,"version":"1.58.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent is now available. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.48.1 . Changed chore(deps): update alpine docker tag to v3.21 in #1958","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1581","eolDate":"2025-12-16"},{"agent":"infrastructure","date":"2024-11-13","downloadLink":null,"version":"1.58.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent is now available. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.48.1 . Changed chore(deps): Upgrade fluent bit version to 3.1.9  https://github.com/newrelic/infrastructure-agent/pull/1946 chore(deps): update dependency newrelic/nri-prometheus to v2.21.6  https://github.com/newrelic/infrastructure-agent/pull/1928 chore(deps): update dependency newrelic/nri-docker to v2.1.0  https://github.com/newrelic/infrastructure-agent/pull/1933 chore: add log for size of compressed data in request in https://github.com/newrelic/infrastructure-agent/pull/1936 Fixed fix: exclude_matching_metrics is excluding non-ProcessSamples  https://github.com/newrelic/infrastructure-agent/pull/1943 fix: use custom dialer when testing connectivity with httpTracer in https://github.com/newrelic/infrastructure-agent/pull/1934 fix: Make TTL not mandatory in secret management command https://github.com/newrelic/infrastructure-agent/pull/1939 fix: Newer versions of semodule tool don't display the SELinux modules version https://github.com/newrelic/infrastructure-agent/pull/1940","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1580","eolDate":"2025-11-13"},{"agent":"infrastructure","date":"2019-10-30","downloadLink":null,"version":"1.5.75","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Bug fixes Fixed graceful stop that was previously behaving non-optimally under system load circumstances: Introduced within the new newrelic-infra-service binary at v1.5.59. This affected cpu_profile option, restored now.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1575","eolDate":"2022-10-30"},{"agent":"infrastructure","date":"2024-09-25","downloadLink":null,"version":"1.57.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.47.1 . Fixed Process metrics are being sent even if enable_process_metrics is undefined or defined as false  #1927","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1572","eolDate":"2025-09-25"},{"agent":"infrastructure","date":"2024-09-12","downloadLink":null,"version":"1.57.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Defective release : this release has a known issue where process metrics might be reported even if enable_process_metrics is undefined or set to false in agent settings. Please consider one of these alternatives: Use any version lower than 1.57.0 Upgrade to 1.57.2 or later. Use metrics_process_sample_rate: -1 to completely disable process monitoring. We've released a new version of the agent. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly, every 3 months at a minimum. As of this release, the oldest supported version is Infrastructure agent 1.47.0 . Changed ci: support SLES 15.6 #1916 chore: bump Go to version to use latest 1.22 #1922 chore(deps): update dependency newrelic/nri-flex to v1.15.2 #1923 chore(deps): update dependency newrelic/nri-prometheus to v2.21.5 #1925 chore(deps): update dependency newrelic/nri-docker to v2.0.9 #1924 chore(deps): update dependency newrelic/nri-winservices to v1.0.3 #1926","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1571","eolDate":"2025-09-12"},{"agent":"infrastructure","date":"2024-09-02","downloadLink":null,"version":"1.57.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Defective release : this release has a known issue where process metrics might be reported even if enable_process_metrics is undefined or set to false in agent settings. Please consider one of these alternatives: Use any version lower than 1.57.0 Upgrade to 1.57.2 or later. Use metrics_process_sample_rate: -1 to completely disable process monitoring. We've released a new version of the agent. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly, every 3 months at a minimum. As of this release, the oldest supported version is Infrastructure agent 1.47.0 . Changed New local health status (/v1/status/health) checks for valid credentials to connect to NR backend #1908 Ability to define exclusion lists for process monitoring using the exclude_matching_metrics setting  #1914","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1570","eolDate":"2025-09-02"},{"agent":"infrastructure","date":"2019-10-22","downloadLink":null,"version":"1.5.66","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Bug fixes Reverted previous changes of version 1.5.62 because there are some edge cases not handled properly. We'll bring back the feature as soon as possible.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1566","eolDate":"2022-10-22"},{"agent":"infrastructure","date":"2024-08-19","downloadLink":null,"version":"1.56.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"We've released a new version of the agent. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly, every 3 months at a minimum. As of this release, the oldest supported version is Infrastructure agent 1.46.0 . Changed Update dependency newrelic/nri-docker to v2.0.7 #1912","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1561","eolDate":"2025-08-19"},{"agent":"infrastructure","date":"2024-08-13","downloadLink":null,"version":"1.56.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"We've released a new version of the agent. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly, every 3 months at a minimum. As of this release, the oldest supported version is Infrastructure agent 1.46.0 . Added Add support to Fluent Bit 3 on Windows #1909","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1560","eolDate":"2025-08-13"},{"agent":"infrastructure","date":"2019-10-17","downloadLink":null,"version":"1.5.59","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Changed Agent service binary is now newrelic-infra-service instead of newrelic-infra. Later is now a child process spawned by the prior. See further details . Added Command channel. Enables NR platform to trigger commands to agents via command-api HTTPS endpoint . See further details . Added log entry for when initializing docker client fails: unable to initialize docker client. Bug fixes Disabled keep-alive on cloud metadata requests to avoid leaking open connections.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1559","eolDate":"2022-10-17"},{"agent":"infrastructure","date":"2024-08-05","downloadLink":null,"version":"1.55.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"We've released a new version of the agent. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly, every 3 months at a minimum. As of this release, the oldest supported version is Infrastructure agent 1.46.0 . Changed chore: Bump docker dependency from v24.0.9 to v26.1.5 #1901 chore(deps): Update the dependency newrelic/nri-flex to v1.15.1 #1900 chore(deps): Update the dependency newrelic/nri-docker to v2.0.6#1902 chore: Bump nri-winservices to v1.0.2 #1903","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1552","eolDate":"2025-08-05"},{"agent":"infrastructure","date":"2019-10-07","downloadLink":null,"version":"1.5.51","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Changed Linux Better error handling for NFS support. HostInfo plugin to provide uptime for older distros. Bug fixes The agent will reuse network connections again. Since v1.3.18, the agent created a new connection on each metrics post. Not reusing the connections may lead metrics to be accumulated and submitted with long delays in systems where the connection establishment is slow.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1551","eolDate":"2022-10-07"},{"agent":"infrastructure","date":"2024-07-23","downloadLink":null,"version":"1.55.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.45.0 . Changed Avoid wrong delta calculation for integrations (temporary config name calculated with content's md5) #1894","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1551-0","eolDate":"2025-07-23"},{"agent":"infrastructure","date":"2024-07-16","downloadLink":null,"version":"1.55.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.43.2 . Added Config option to disable container decoration in ProcessSample  #1888 Changed Update dependency newrelic/nri-docker to v2.0.4  #1891 Update dependency newrelic/nri-prometheus to v2.21.4 #1879","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1550","eolDate":"2025-07-16"},{"agent":"infrastructure","date":"2019-09-23","downloadLink":null,"version":"1.5.45","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added Linux: Added additional checks to confirm the user ID to determine whether the agent is running as a root user. Changed Using a new endpoint for Agent identity retrieval to mitigate the hostname flipping issue. This change was introduced for the Windows Agent 1.5.37, and now is also active for the Linux Agent.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1545","eolDate":"2022-09-23"},{"agent":"infrastructure","date":"2019-09-19","downloadLink":null,"version":"1.5.40","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added Added new NFSSample (event type is NFSSample) for gathering NFS client metrics. This is configurable by the following config option: metrics_nfs_sample_rate (default: 20) detailed_nfs (default: false)","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1540","eolDate":"2022-09-19"},{"agent":"infrastructure","date":"2019-09-05","downloadLink":null,"version":"1.5.37","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Changed Add extra information on verbose logs. On each metrics post, an incremental counter and the timestamps of the submitted metrics are logged. Windows specific Using a new endpoint for Agent identity retrieval to mitigate the hostname flipping issue.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1537","eolDate":"2022-09-05"},{"agent":"infrastructure","date":"2019-08-26","downloadLink":null,"version":"1.5.31","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Changed Improve trial management mechanism in Agent Add support for including extra attributes in the Events; before, events only supported a summary and category field, now extra attributes can be defined.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1531","eolDate":"2022-08-26"},{"agent":"infrastructure","date":"2024-06-19","downloadLink":null,"version":"1.53.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent .\nNew Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is infrastructure agent 1.43.0 . Changed [#changed] Update dependency newrelic/nri-flex to v1.14.0 #1863 Update dependency newrelic/nri-prometheus to v2.21.2 #1864 Update dependency newrelic/nri-docker to v2.0.3 #1869 Update alpine docker tag to v3.20 #1870 Update dependency newrelic/nri-flex to v1.15.0 #1885 Add new integrations_only agent mode #1875 Add new multiline parser config param to logging config #1881","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1530","eolDate":"2025-06-19"},{"agent":"infrastructure","date":"2019-08-20","downloadLink":null,"version":"1.5.29","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Changed Optimized Storage Sampler CPU consumption (noticeable in agents managing > 100 mounted devices). Windows specific All executables are now signed. Added versioning info to newrelic-infra-ctl.exe. These changes should avoid Defender to flag the package as threat.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1529","eolDate":"2022-08-20"},{"agent":"infrastructure","date":"2019-08-13","downloadLink":null,"version":"1.5.26","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Windows only Previous agent version 1.5.0 got flagged by Windows Defender. We found it was a false positive. This version proved to pass Defender test, but could still get flagged by Defender on some systems. Improved StorageSample metrics performance. Please refer to the New Relic event data dictionary  for a detailed description of them.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1526","eolDate":"2022-08-13"},{"agent":"infrastructure","date":"2024-05-21","downloadLink":null,"version":"1.52.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.42.0 . Changed Add support for ubuntu 24.04 854 Logs are not supported yet for this ubuntu version Bump nri-flex to v1.13.0 (https://github.com/newrelic/infrastructure-agent/pull/1860 )","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1523","eolDate":"2025-05-21"},{"agent":"infrastructure","date":"2024-06-08","downloadLink":null,"version":"1.52.3 (Fluent Bit 3.0.4)","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the Fluent Bit package has been released with a fix for CVE-2024-4323 . Follow the recommended procedures to update the Infrastructure agent : Windows Infrastructure agent On Windows, the embedded version of Fluent Bit within the Windows Infrastructure Agent has been determined to not be impacted by CVE-2024-4323. Linux Infrastructure agent Upgrade the Infrastructure agent to version 1.52.3 or later, AND update Fluent Bit to version 3.0.4 or later Changed Update Fluent Bit to version 3.0.4 as a fix for CVE-2024-4323 , which impacted certain prior Fluent Bit versions contained in the Infra-agent log forwarder solution. Bump nri-flex to v1.13.0 (https://github.com/newrelic/infrastructure-agent/pull/1860)","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1523-fb-304","eolDate":"2025-06-08"},{"agent":"infrastructure","date":"2024-05-13","downloadLink":null,"version":"1.52.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.41.0 . Changed Support Cyberark on Windows  #1853 Update dependency newrelic/nri-docker to v2.0.2 #1846 Update dependency newrelic/nri-prometheus to v2.21.1  #1848 Update Gopsutil to 3.24.4 #1849 Update nri-flex to 1.12.0 #1855","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1522","eolDate":"2025-05-13"},{"agent":"infrastructure","date":"2024-05-06","downloadLink":null,"version":"1.52.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.40.0 . Changed Add host.id to System Sample in #1840 General dependency upgrades and improvements","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1521","eolDate":"2025-05-06"},{"agent":"infrastructure","date":"2024-04-02","downloadLink":null,"version":"1.52.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.39.2 . Changed Added logging config: Wrapped Record attribute key and value in double quotes in #1827 Added logging config: Add log warning msg when logging too many files in #1823 Enabled FluentBit installation for arm64 AmazonLinux 2023 in #1824 Added new attribute host.id in connect metadata in #1838 Updated dependency newrelic/nri-flex to v1.11.0 in #1839","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1520","eolDate":"2025-04-02"},{"agent":"infrastructure","date":"2024-03-25","downloadLink":null,"version":"1.51.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.39.1 . Changed Update dependency newrelic/nri-prometheus to v2.21.0  #1820 . Update dependency newrelic/nri-docker to v2 #1828 . Fixed Create log files with reduced permissions #1825 .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1510","eolDate":"2025-03-25"},{"agent":"infrastructure","date":"2019-08-12","downloadLink":null,"version":"1.5.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Changed Improved StorageSample metrics performance. Please refer to the New Relic event data dictionary  for a detailed description of them. Windows only IMPORTANT: This version was deleted from the Windows repository to avoid causing issues on the platform. Improved hostname flipping issue mitigation using a new endpoint for agent identity retrieval. Cases where a host flipping its hostname (because DNS lookup is not available or any other reasons) caused host entity identification to change (and some alerts to fail) should be mitigated, but some cases could still persist.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-151","eolDate":"2022-08-12"},{"agent":"infrastructure","date":"2024-02-26","downloadLink":null,"version":"1.50.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.38.0 . Changed Add sdk temp_dir environment variable propagation #1808 Exclude integration error logs by default  #1816 chore(deps): update dependency newrelic/nri-docker to v1.10.0  #1817 chore(deps): update dependency newrelic/nri-flex to v1.10.0  #1818","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1500","eolDate":"2025-02-26"},{"agent":"infrastructure","date":"2019-08-05","downloadLink":null,"version":"1.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added New StorageSample metrics. Please refer to the New Relic event data dictionary  for a detailed description of them. Linux-only storage metrics: inodesFree, inodesUsed, inodesTotal and inodesUsedPercent. Windows-only storage metrics: avgQueueLen, avgReadQueueLen, avgWriteQueueLen and currentQueueLen. Security notes Windows package gets flagged by Windows-Defender on some machines. Use newer versions instead.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-150","eolDate":"2022-08-05"},{"agent":"infrastructure","date":"2024-02-20","downloadLink":null,"version":"1.49.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.37.2 . Changed Log Container initialization errors #1810","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1491","eolDate":"2025-02-20"},{"agent":"infrastructure","date":"2024-02-12","downloadLink":null,"version":"1.49.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.37.1 . Added Enable fluent-bit package for SUSE 15.5 [https://github.com/newrelic/infrastructure-agent/pull/1795] Configurable integrations temporal directory [https://github.com/newrelic/infrastructure-agent/pull/1793] Configurable agent temporal directory [https://github.com/newrelic/infrastructure-agent/pull/1798] Add parser for integration SDK errors [https://github.com/newrelic/infrastructure-agent/pull/1800] Changed Bump containerd dependency [https://github.com/newrelic/infrastructure-agent/pull/1802] Update dependency newrelic/nri-docker to v1.9.8 [https://github.com/newrelic/infrastructure-agent/pull/1805]","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1490","eolDate":"2025-02-12"},{"agent":"infrastructure","date":"2019-07-18","downloadLink":null,"version":"1.4.9","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added Optional JSON log format (doc coming soon). Changed Startup info and errors are now logged into the log file since the beginning. Log messages prior to configuration being fully loaded. Improved error catching and logging on fatal failures. Improved log messages. Most of the messages are now static, not inlined with context values, so messages are more easily filterable/greppable, and context fields are provided attached. Example old message: Example new message:","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-149","eolDate":"2022-07-18"},{"agent":"infrastructure","date":"2024-02-07","downloadLink":null,"version":"1.48.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.37.1 . Changed Update dependency newrelic/nri-docker to v1.9.5 #1782 Update dependency newrelic/nri-prometheus to v2.20.1 #1784 Update dependency newrelic/nri-flex to v1.9.4 #1788 Bump Go dependencies #1786","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1485","eolDate":"2025-02-07"},{"agent":"infrastructure","date":"2024-01-15","downloadLink":null,"version":"1.48.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent .\nWe recommend you upgrade the agent regularly and at a minimum every 3 months. As\nof this release, the oldest supported version is infrastructure agent\n1.36.1 . Changed Added the sendMetrics parameter to the NewRelic output plugin in the FB conf file #1759 Fixed HTTP Tracer error control #1757 Adjust Dimensional Metrics max size #1764 Obfuscate wrong license key #1767","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1483","eolDate":"2025-01-15"},{"agent":"infrastructure","date":"2023-11-09","downloadLink":null,"version":"1.48.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent .\nWe recommend you upgrade the agent regularly and at a minimum every 3 months. As\nof this release, the oldest supported version is infrastructure agent\n1.33.2 . Changed Update dependency newrelic/nri-docker to v1.8.27 #1752 Update dependency newrelic/nri-flex to v1.9.2 #1752 Update dependency newrelic/nri-prometheus to v2.19.0 #1752","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1481","eolDate":"2024-11-09"},{"agent":"infrastructure","date":"2023-10-25","downloadLink":null,"version":"1.48.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent .\nWe recommend you upgrade the agent regularly and at a minimum every 3 months. As\nof this release, the oldest supported version is infrastructure agent\n1.33.0 . Changed Update dependency newrelic/nri-docker to v1.8.24 #1740 Remove internal Prometheus metrics endpoint #1745 Move embedded binaries to /opt in Linux systems #1742 Fixed Default NTP queries timeout #1744","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1480","eolDate":"2024-10-25"},{"agent":"infrastructure","date":"2023-09-29","downloadLink":null,"version":"1.47.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is infrastructure agent 1.30.0 . Changed Updated dependency newrelic/nri-prometheus to v2.18.7 in #1738 Updated dependency newrelic/nri-docker to v1.8.20 #1737 Updated Go to v1.20.8 #1739","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1472","eolDate":"2024-09-29"},{"agent":"infrastructure","date":"2023-09-18","downloadLink":null,"version":"1.47.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent .\nWe recommend you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is infrastructure agent 1.29.0 . Added Add cmdline process darwin (NR-155368) in #1731","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1471","eolDate":"2024-09-18"},{"agent":"infrastructure","date":"2023-08-29","downloadLink":null,"version":"1.47.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent .\nWe recommend you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is infrastructure agent 1.28.4 . Added Packages for Debian 12 #1724 Container decoration with Docker and Containerd dual sockets #1725 Changed Bump newrelic/nri-docker dependency to v1.8.16 #1727","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1470","eolDate":"2024-08-29"},{"agent":"infrastructure","date":"2023-08-24","downloadLink":null,"version":"1.46.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend that you update the agent regularly and at a minimum every three months. As of this release, the oldest supported version is infrastructure agent 1.28.3 . Added Packages for SUSE 15.5 #1717 Changed Bump newrelic/nri-docker dependency to v1.8.14 #1718 Bump newrelic/nri-flex dependency to v1.9.1  #1719","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1460","eolDate":"2024-08-24"},{"agent":"infrastructure","date":"2023-07-24","downloadLink":null,"version":"1.45.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend that you update the agent regularly and at a minimum every three months. As of this release, the oldest supported version is infrastructure agent 1.28.0 . Changed Bump newrelic/nri-docker dependency to v1.8.10  #1698 Bump Go to v1.20 #1690 Update NTP interval check on error #1699 Fixed Infra Agent executable privileges being reset #1693 Handle error when no task is found #1697","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1450","eolDate":"2024-07-24"},{"agent":"infrastructure","date":"2019-07-15","downloadLink":null,"version":"1.4.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Changed Allow enabling http-server (required for Statsd integration) to work in forwarder mode.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-145","eolDate":"2022-07-15"},{"agent":"infrastructure","date":"2023-07-18","downloadLink":null,"version":"1.44.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend that you update the agent regularly and at a minimum every three months. As of this release, the oldest supported version is infrastructure agent 1.27.5 . Added Use rpmv3 signature mode for sles12.x packages #1691 Changed Disable CGO for amd64 #1689 Bump dependency newrelic/nri-prometheus to v2.18.5 #1696 Bump dependency newrelic/nri-docker to v1.8.9 #1695 Fixed Fallback to td-agent-bit when fluent-bit not present #1694","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1440","eolDate":"2024-07-18"},{"agent":"infrastructure","date":"2023-07-11","downloadLink":null,"version":"1.43.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . New Relic recommends that you upgrade the agent regularly and at a minimum every three months. As of this release, the oldest supported version is Infrastructure agent 1.27.4 . Changed Validate NTP responses #1684 Bump Go patch version to v1.19.10 #1683 Bump newrelic/nri-docker to v1.8.7 #1685 Bump newrelic/nri-flex to v1.8.6 #1686","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1432","eolDate":"2024-07-11"},{"agent":"infrastructure","date":"2023-06-23","downloadLink":null,"version":"1.43.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . New Relic recommends that you upgrade the agent regularly and at a minimum every three months. As of this release, the oldest supported version is Infrastructure agent 1.27.3 . Changed Update nri-prometheus to v2.18.4 #1681","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1431","eolDate":"2024-06-23"},{"agent":"infrastructure","date":"2023-06-16","downloadLink":null,"version":"1.43.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . New Relic recommends that you upgrade the agent regularly and at a minimum every three months. As of this release, the oldest supported version is Infrastructure agent 1.27.2 . Changed Log negative CPU percent as a warning #1676 Bump fluent-bit-plugin version to 1.17.1  #1677","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1430","eolDate":"2024-06-16"},{"agent":"infrastructure","date":"2023-06-09","downloadLink":null,"version":"1.42.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . New Relic recommends that you upgrade the agent regularly and at a minimum every three months. As of this release, the oldest supported version is Infrastructure agent 1.27.1 . Changed Bump github.com/containerd/containerd from v1.5.10 to v1.5.18 #1674","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1425","eolDate":"2024-06-09"},{"agent":"infrastructure","date":"2023-06-01","downloadLink":null,"version":"1.42.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . New Relic recommends that you upgrade the agent regularly and at a minimum every three months. As of this release, the oldest supported version is Infrastructure agent 1.27.0 . Changed Bump newrelic/nri-docker to v1.8.6 #1673","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1424","eolDate":"2024-06-01"},{"agent":"infrastructure","date":"2023-06-01","downloadLink":null,"version":"1.42.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend that you update the agent regularly and at a minimum every three months. As of this release, the oldest supported version is infrastructure agent 1.27.0 . Fixed Ensure containerDecorator is not nil in containerd environments","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1423","eolDate":"2024-06-01"},{"agent":"infrastructure","date":"2023-06-01","downloadLink":null,"version":"1.42.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.27.0 . Added Support Fluent Bit Use_ANSI flag in #1661 . Changed Bump nri-flex version to 1.8.5 in #1668 . Bump nri-prometheus version to 2.18.1 in #1665 . Bump nri-docker version to 1.8.4 in #1660 . Fixed msi checks performed before creating agent data directory in #1635 .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1422","eolDate":"2024-06-01"},{"agent":"infrastructure","date":"2023-05-24","downloadLink":null,"version":"1.42.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the infrastructure agent is available. Update the Infrastructure agent  regularly, at least every three months. As of this release, the oldest supported version is Infrastructure agent 1.26.0 . Changed Bumped nri-docker version to v1.8.2 in #1663 . Bumped Go version to 1.19.9 and docker dependencies in #1664 . Fixed Don't use ipv6-prefixed localhost hostnames as a fully qualified domain name. Fixed in #1662 .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1421","eolDate":"2024-05-24"},{"agent":"infrastructure","date":"2023-05-18","downloadLink":null,"version":"1.42.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.25.0 . Added Support for containerd as container runtime in process monitoring Use enable_wmi_proc_data to enable process monitoring via WMI on Windows (when agent is run as non-admin or any restricted environment) Using fluent-bit instead of td-agent package for log forwarding Changed Update dependency newrelic/nri-flex to v1.8.3 Update alpine docker tag to v3.18","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1420","eolDate":"2024-05-18"},{"agent":"infrastructure","date":"2019-08-01","downloadLink":null,"version":"1.4.14","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Bugfixes Fixed crash behaviour while stopping the agent under certain circumstances. Ie, containerised agent service stop could trigger a crash dumping a trace. Crash on stop should not be harmful for the agent itself or remaining data, but a non zero exit code and/or crash backtrace output might affect 3rd parties.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1414","eolDate":"2022-08-01"},{"agent":"infrastructure","date":"2019-07-29","downloadLink":null,"version":"1.4.11","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Bugfixes Fix log obfuscation feature applying to integration received arguments. Bug was introduced on agent v1.4.0 affecting some OHIs arguments. Symptom was: OHI receives obfuscated PASSWORD env vars with value HIDDEN.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1411","eolDate":"2022-07-29"},{"agent":"infrastructure","date":"2023-05-10","downloadLink":null,"version":"1.41.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. See how to update the Infrastructure agent . We recommend you to upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.24.2 . Added Allow custom HTTP headers  for all requests #1640 Ability to load agent and integration configurations from custom commands #1640 . Refer to secrets documentation  to learn more. Changed Bump newrelic/nri-docker to v1.8.1 #1629 Bump newrelic/nri-flex to v1.8.2 #1631 Fixed Set default timeout for cloud metadata requests to 2s #1627 Split dimensional metrics request in batches when bigger than the limit (1mb) (fixes nri-ibmmq) #1634","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1410","eolDate":"2024-05-10"},{"agent":"infrastructure","date":"2023-04-18","downloadLink":null,"version":"1.40.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the infrastructure agent regularly, at least every three months. As of this release, the oldest supported version is agent version 1.23.3 . Added New configuration option 'cloud_provider'  that allows to explicitly set the Cloud Provider instead of using the automatic detection. Cloud Provider is required in order to collect host metadata. https://github.com/newrelic/infrastructure-agent/pull/1614","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1401","eolDate":"2024-04-18"},{"agent":"infrastructure","date":"2023-04-06","downloadLink":null,"version":"1.40.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the infrastructure agent regularly, at least every three months. As of this release, the oldest supported version is agent version 1.23.3 . Changed Bump nri-winservices to v1.0.1 #1619 Bump Go version to 1.19.8 #1622","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1400","eolDate":"2024-04-06"},{"agent":"infrastructure","date":"2019-07-11","downloadLink":null,"version":"1.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added Improved logging and troubleshooting features: Logging agent config options at startup (with obfuscation of sensitive data). Logging all the config options of the loaded integrations at startup (with obfuscation of sensitive data). Improve log messages related to integrations. Integrations health checks New binary called newrelic-infra-ctl for sending notifications to the agent for: Enabling verbose logs for 5 minutes Integrations health check Agent daemon notification For notifying the agent to perform actions, the newrelic-infra-ctl command was created. It has the sole responsibility of sending a notification to the agent process that's running inside the host. In Linux this communication happens via POSIX signals. newrelic-infra-ctl first tries to find if there is an agent process running. If it finds it, it checks if the process is running inside a Docker container. This is because signals to Docker containers are sent with the docker kill command. Once it knows the pid and the signaling method to use, it sends a SIGUSR1 signal to the agent. The agent just has to set a signal handler for when it receives a SIGUSR1. In Windows, things are a little different. The only signals that we could send to the process were exit signals. In Windows processes communicate by sending messages to their respective windows, but you might be wondering (as I was), the agent is a daemon process so it doesn't have a window. The solution, easy, a hidden window. On startup the agent creates a hidden window, and sets a handler that listens for messages that arrive in that window. newrelic-infra-ctl finds that windows and sends messages to it. Changed Decorate samples with reportingAgent attribute and replace loopback address if found in reportingEndpoint and reportingEntityKey samples attributes. Do not log config.pid_file property in the Windows agent.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-140","eolDate":"2022-07-11"},{"agent":"infrastructure","date":"2023-04-05","downloadLink":null,"version":"1.39.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the infrastructure agent regularly, at least every three months. As of this release, the oldest supported version is agent version 1.23.3 . Changed Set permissions to binary in PRIVILEGED mode #1592 Added MemBufferLimit parameter to limit the amount of memory used by td-agent-bit process #1576 Log original event length instead of the limit value #1606 Upgrade Go SDK to 1.19 #1613 Bump nri-flex version to v1.8.0 #1610 Fixed Issue with msi installer on Windows 2012 #1609","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1392","eolDate":"2024-04-05"},{"agent":"infrastructure","date":"2023-03-17","downloadLink":null,"version":"1.39.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the infrastructure agent regularly, at least every three months. As of this release, the oldest supported version is agent version 1.23.3 . Changed Bump nri-winservice to v1.0.0 #1598 Fixed Use agent tmp folder only in Windows #1600","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1391","eolDate":"2024-03-17"},{"agent":"infrastructure","date":"2023-03-16","downloadLink":null,"version":"1.39.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the infrastructure agent regularly, at least every three months. As of this release, the oldest supported version is agent version 1.23.3 . Added Use custom tmp folder #1579 Amazon Linux 2023  #1589 Do not let Infra Agent's Fluent Bit config files fill the disk #1580 Changed nri-docker to v1.8.0 #1582 nri-prometheus to v2.18.0 #1585 nri-flex to v1.7.2 #1586","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1390","eolDate":"2024-03-16"},{"agent":"infrastructure","date":"2023-03-07","downloadLink":null,"version":"1.38.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the infrastructure agent regularly, at least every three months. As of this release, the oldest supported version is agent version 1.23.3 . Added Add EntityKey into /v1/status/entity output #1564 Changed protocol_v4_enabled Feature Flag enabled by default #1568","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1380","eolDate":"2024-03-07"},{"agent":"infrastructure","date":"2023-02-16","downloadLink":null,"version":"1.37.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. See how to update the infrastructure agent . We recommend you to upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is infrastructure agent 1.23.0 . Changed Bump nri-docker to v1.7.6 #1552 (Windows) Create data directory during infrastructure agent msi installation #1550","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1372","eolDate":"2024-02-16"},{"agent":"infrastructure","date":"2023-02-01","downloadLink":null,"version":"1.37.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. See how to update the Infrastructure agent . We recommend you to upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.23.0 . Changed Remove transformation from v3 integrations configuration to v4","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1371","eolDate":"2024-02-01"},{"agent":"infrastructure","date":"2023-01-30","downloadLink":null,"version":"1.37.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the infrastructure agent regularly, at least every three months. As of this release, the oldest supported version is agent version 1.23.0 . Changed Upgrade go version to 1.19 #1524 Bump nri-flex to v1.7.0 #1539 Bump x/net package #1537 Fixed aarch64 checksums schema paths for arm64 #1535","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1370","eolDate":"2024-01-30"},{"agent":"infrastructure","date":"2023-01-12","downloadLink":null,"version":"1.36.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.21.0 . Changed chore(deps): update dependency newrelic/nri-flex to v1.6.1 chore(deps): bump Alpine container base image to 3.17.1","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1361","eolDate":"2024-01-12"},{"agent":"infrastructure","date":"2022-12-15","downloadLink":null,"version":"1.36.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.20.7 . Added Set log rotation by default for Windows #1499 Add build date to binary metadata #1521 Changed Update dependency newrelic/nri-prometheus to v2.17.0 #1527","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1360","eolDate":"2023-12-15"},{"agent":"infrastructure","date":"2022-12-05","downloadLink":null,"version":"1.35.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.20.7 . Added Log rotate zip compression for windows #1514 Changed Bump dependency newrelic/nri-docker to v1.7.5  #1520 Bump dependency newrelic/nri-flex to v1.6.0 #1523 Bump Go version to 1.18.8 by #1525","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1350","eolDate":"2023-12-05"},{"agent":"infrastructure","date":"2019-04-01","downloadLink":null,"version":"1.3.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Bug fixes Fix post installation script for upstart.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-135","eolDate":"2022-04-01"},{"agent":"infrastructure","date":"2022-12-01","downloadLink":null,"version":"1.34.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend you to upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.20.7 . New Additional Azure metadata (subscriptionID and availabilityZone) SLES 15.4 packages Support for urls in discovery Log TLS version in trace mode Fixed Stop the service to allow upgrade with tarball installation Parse hash character in key/value yaml Fix deadlock in heartbeat package Changed Obfuscate logs of config protocol chore(deps): update alpine docker tag to v3.17 in chore(deps): update dependency newrelic/nri-flex to v1.5.4","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1340","eolDate":"2023-12-01"},{"agent":"infrastructure","date":"2019-07-01","downloadLink":null,"version":"1.3.33","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Changes Minor internal architectural improvements. No impact expected.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1333","eolDate":"2022-07-01"},{"agent":"infrastructure","date":"2022-11-03","downloadLink":null,"version":"1.33.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the infrastructure agent regularly, at least every three months. As of this release, the oldest supported version is agent version 1.20.7 . Fixed Cache NTP value for the specified interval #1488 NTP timeout in seconds #1488","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1332","eolDate":"2023-11-03"},{"agent":"infrastructure","date":"2022-10-31","downloadLink":null,"version":"1.33.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend you to upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.20.5 . Fixed CVE-2022-32149  in docker image","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1331","eolDate":"2023-10-31"},{"agent":"infrastructure","date":"2022-10-24","downloadLink":null,"version":"1.33.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend you to upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.20.5 . New Add support for reizerFS Extend memory metrics (MemoryKernelFree, MemoryBuffers) Changed Rename NTP config option Bump newrelic/nri-flex to v1.5.3 Bump newrelic/nri-prometheus to v2.16.7 Fixed Fix CVE-2022-32149 Added support for super block metadata rw/ro","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1330","eolDate":"2023-10-24"},{"agent":"infrastructure","date":"2019-03-27","downloadLink":null,"version":"1.3.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Changes Removed libcap dependency since it's only used for privileged mode. Bug fixes Lower log level for Selinux errors.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-133","eolDate":"2022-03-27"},{"agent":"infrastructure","date":"2019-05-27","downloadLink":null,"version":"1.3.27","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Add support for Red Hat Enterprise Linux 8 and CentOS 8 Improvements Improve log messages related to startup permissions errors.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1327","eolDate":"2022-05-27"},{"agent":"infrastructure","date":"2022-10-13","downloadLink":null,"version":"1.32.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is infrastructure agent 1.12.5 . New Added logs_queue_size configuration option for integrations config files. This will allow specifying how many log lines will be reported for each integration if collection fails #1439 Added swap metrics #1437 Add network profiler to help troubleshooting network issues. To enable it add log include filter component HttpTracer #1433 Added host NTP offset as an attribute to SystemSample to detect real collection time of the samples #1432 Changed Bump newrelic/nri-prometheus to v2.16.6 #1436 Fixed Issue when checks were still performed even if the status server failed to initialize #1438 Hide license key when logging FB config file #1442 Full changelog : https://github.com/newrelic/infrastructure-agent/compare/1.31.0...1.32.0","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1320","eolDate":"2023-10-13"},{"agent":"infrastructure","date":"2019-04-11","downloadLink":null,"version":"1.3.18","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Bug fixes When the configuration variable startup_connection_retries is set to -1, the Agent will keep checking forever the connectivity at startup to avoid CrashLoopBackOff states in K8S in case of failures. 'startup_connection_retry_time' has been removed and now the Agent uses an exponential backoff algorithm. Improve the exponential backoff algorithm the Agent uses when posting metrics fails due to a non 2xx request response. Filter duplicated device entries in the StorageSample.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1318","eolDate":"2022-04-11"},{"agent":"infrastructure","date":"2022-09-29","downloadLink":null,"version":"1.31.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend you upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.12.5 . New Added uptime to SystemSample by #1412 Changed Bump newrelic/nri-prometheus to v2.16.5 #1422 Bump newrelic/nri-docker to v1.7.4  #1421 Bump nri-flex to v1.5.2 #1427 Full Changelog : https://github.com/newrelic/infrastructure-agent/compare/1.30.0...1.31.0","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1310","eolDate":"2023-09-29"},{"agent":"infrastructure","date":"2019-03-25","downloadLink":null,"version":"1.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Improvements Added HTTPS proxy certificate verification. You can enable it with the proxy_validate_certificates: true configuration option. When this option is set to true and you setup an HTTPS proxy with self-signed certificates, you may need to specify the certificates location with the ca_bundle_fileor ca_bundle_dir configuration options. Added a Proxy Configuration Plugin that submits non-sensitive proxy configuration information as inventory. To disable it, set the proxy_config_plugin: false configuration option. Warn on RPM plugin package parsing error. Changes Increased the intervals of some samplers Increased ProcessSample default interval from 10 to 20 Increased StorageSample default interval from 5 to 20 Increased NetworkSample default interval from 5 to 10 When the configuration option startup_connection_retries is set to -1, the Agent, at startup, will keep checking forever the connectivity. The configuration option startup_connection_retry_time has been removed and now the Agent uses an exponential backoff algorithm. The Windows Agent does not ignore A: and B: drives anymore, as they may be mapped to actual Hard Disks. If those drives are reported because they map into a removable drive and you don't want the agent to report them, you can set the win_removable_drives: false configuration option. Bug fixes Fixed a bug that may cause some configuration options to be ignored when settting via environment variables (e.g. NRIA_IGNORE_RECLAIMABLE or NRIA_PROXY_VALIDATE_CERTIFICATES) Fixed a bug in the Linux agent that prevented the agent from loading the system root certificates when the ca_bundle_dir or ca_bundle_file options were specified. This bug can't be fixed in the Windows Agent so the user will need to place in the ca_bundle_dir a copy of the New Relic certificate.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-131","eolDate":"2022-03-25"},{"agent":"infrastructure","date":"2022-09-27","downloadLink":null,"version":"1.30.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend you upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.12.5 . New Support for Apple Silicon based Macos #1416 Fixed Check all APT distributions packages before cleaning CDN cache #1411 Fix CVE-2022-27664 in golang.org/x/net #1415 Full Changelog : https://github.com/newrelic/infrastructure-agent/compare/1.29.1...1.30.0","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1300","eolDate":"2023-09-27"},{"agent":"infrastructure","date":"2022-09-13","downloadLink":null,"version":"1.29.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend you upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.12.4 . Changed Add config parameter for output retry_limit  #1392 Bump publish action to v1.2.6 #1400 Fixed Avoid warnings when Discovery template replacements are not found #1398 Full Changelog : https://github.com/newrelic/infrastructure-agent/compare/1.29.0...1.29.1","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1291","eolDate":"2023-09-13"},{"agent":"infrastructure","date":"2022-09-06","downloadLink":null,"version":"1.29.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend you upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.12.4 . Changed Bump nri-winservices to v0.6.0-beta #1391 Allow Tags for DM Integrations in #1360 Full Changelog : https://github.com/newrelic/infrastructure-agent/compare/1.28.4...1.29.0","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1290","eolDate":"2023-09-06"},{"agent":"infrastructure","date":"2022-08-29","downloadLink":null,"version":"1.28.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend you upgrade the agent regularly, at least every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.12.3 . Fixed Heartbeat context cancelation https://github.com/newrelic/infrastructure-agent/pull/1388 Full Changelog : https://github.com/newrelic/infrastructure-agent/compare/1.28.3...1.28.4","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1284","eolDate":"2023-08-29"},{"agent":"infrastructure","date":"2022-08-23","downloadLink":null,"version":"1.28.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.12.2 . Changed Bump go version to 1.18.5 in https://github.com/newrelic/infrastructure-agent/pull/1383 Full Changelog : https://github.com/newrelic/infrastructure-agent/compare/1.28.2...1.28.3","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1283","eolDate":"2023-08-23"},{"agent":"infrastructure","date":"2022-08-18","downloadLink":null,"version":"1.28.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.12.2 . nri-flex to v1.5.1 #1367 nri-prometheus to v2.16.4 #1358 nri-docker to v1.7.3 #1374 Full Changelog : https://github.com/newrelic/infrastructure-agent/compare/1.28.1...1.28.2","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1282","eolDate":"2023-08-18"},{"agent":"infrastructure","date":"2022-08-17","downloadLink":null,"version":"1.28.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.12.2 . Fixed Fargate struct exit code #1336 Fix security issues #1343 , #1364 Chore Improvements in the LogConfig #1292 Full Changelog : https://github.com/newrelic/infrastructure-agent/compare/1.28.0...1.28.1","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1281","eolDate":"2023-08-17"},{"agent":"infrastructure","date":"2022-07-20","downloadLink":null,"version":"1.28.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . We recommend you to upgrade the agent at least, every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.12.0 . Added Built-in log rotation #1281 . For more information, see log rotate configuration option . Full changelog Find the full changelog for this version in GitHub .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1280","eolDate":"2024-07-20"},{"agent":"infrastructure","date":"2022-07-13","downloadLink":null,"version":"1.27.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Changed bump nri-docker to v1.7.2 (#1284) bump nri-prometheus to v2.16.2 (#1300) Full changelog 1.27.4...1.27.5","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1275","eolDate":"2024-07-13"},{"agent":"infrastructure","date":"2022-06-30","downloadLink":null,"version":"1.27.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Added Checksums and signatures for tar.gz & zip #1257 Fixed False heartbeat timeout warning #1240 Change log level for Unable to retrieve NFS stats. back to debug if there is no NFS #1270","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1274","eolDate":"2024-06-30"},{"agent":"infrastructure","date":"2022-06-20","downloadLink":null,"version":"1.27.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. See these instructions on how to update the Infrastructure agent . We recommend you to upgrade the agent regularly, at least, every 3 months. Changed Bump nri-flex to v1.5.0 #1227","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1273","eolDate":"2024-06-20"},{"agent":"infrastructure","date":"2022-06-15","downloadLink":null,"version":"1.27.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. See these instructions on how to update the Infrastructure agent . We recommend you to upgrade the agent regularly, at least, every 3 months. Changed Bump nri-docker to v1.7.1 #1212 Fixed Return first valid ipv4/port in Docker discovery #1201","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1272","eolDate":"2024-06-15"},{"agent":"infrastructure","date":"2022-06-08","downloadLink":null,"version":"1.27.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. See these instructions on how to update the Infrastructure agent . We recommend you to upgrade the agent regularly, at least, every 3 months. Added Troubleshooting: log http requests traces #1191 documentation for Dry Run mode #1203","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1271","eolDate":"2024-06-08"},{"agent":"infrastructure","date":"2022-05-31","downloadLink":null,"version":"1.27.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. See these instructions on how to update the Infrastructure agent . We recommend you to upgrade the agent regularly, at least, every 3 months. Added FluentBit as weak dependency in SLES 15.1, 15.2, 15.3 #1180 Changed New Logging configuration structure and options   #1186 Update base Alpine image => 3.16 #1179 Fixed Integrations with template replacements are not processed issue 32  #1175","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1270","eolDate":"2024-05-31"},{"agent":"infrastructure","date":"2022-05-26","downloadLink":null,"version":"1.26.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. See these instructions on how to update the infrastructure agent . We recommend you upgrade the agent regularly, at least once every 3 months. Added basic disk metrics for ZFS (#1139) #1139 Changed bump nri-docker to v1.7.0 (#1170) #1170 bump nri-flex to v1.4.5 (#1166) #1166 Fixed logging options from config (#1175) #1175","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1260","eolDate":"2024-05-26"},{"agent":"infrastructure","date":"2019-02-04","downloadLink":null,"version":"1.2.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Added the dns_hostname_resolution configuration option (default: true). If set to false, the agent won't use DNS-based hostname resolution and will ask directly to the operating system. Added ignore_reclaimable configuration option (Linux only), which considers reclaimable memory as part of the free memory (and not part of the used memory). Free memory will be is calculated as: total - free - buffers - cached - sreclaimable, independently of the MemAvailable report from the kernel. Improvements In cloud environments, the instance ID retrieval process is more solid during the agent startup. It also allows the agent to be spawned from VM snapshots. Changes Removed total_cores host metric. Bug fixes Fixed a bug that caused the DiskMonitor samples to show devices in the deny list (from the file_devices_ignored configuration option). Fixed Storage Sampler in 32-bit Windows agent. Reduced the incidence of hostname flipping in DNS-based hostname resolution. Fixed a bug that, in the Linux agent, removed the last character of the command line of some process samples. (Linux only) Fixed the used memory values in the System Samples, which in agent 1.2.1 were slightly different from the actual value. Fixed a problem that, when an environment configuration option had a wrong format, caused the rest of the environment variables to not be parsed.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-126","eolDate":"2022-02-04"},{"agent":"infrastructure","date":"2022-05-19","downloadLink":null,"version":"1.25.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. See these instructions on how to update the Infrastructure agent . We recommend you to upgrade the agent regularly, at least, every 3 months. Changed Update Go version to 1.18 #1084 Fixed Avoid deprecated sysctl retrans_time for any device #1164","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1250","eolDate":"2024-05-19"},{"agent":"infrastructure","date":"2022-05-17","downloadLink":null,"version":"1.24.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. See these instructions on how to update the Infrastructure agent . We recommend you to upgrade the agent regularly, at least, every 3 months. Added Add common Windows environment variables to integrations executions #112 Support Winevtlog logging plugin #1125 Changed Update Fluentbit Windows package version to 1.9.3 #115 Fixed Update Containerd to fix CVE-2022-23648  #114","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1243","eolDate":"2024-05-17"},{"agent":"infrastructure","date":"2022-04-21","downloadLink":null,"version":"1.24.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. See these instructions on how to update the Infrastructure agent . We recommend you to upgrade the agent regularly, at least, every 3 months. Added AWS additional cloud metadata reported by default: awsAccountId, awsAvailabilityZone, ec2AmiId (#1054). Extended EC2 metadata, including custom tags, can be ingested using New Relic AWS Cloud Integrations . Changed Update fluentbit windows package version to 1.9.1 (#1096)","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1242","eolDate":"2024-04-21"},{"agent":"infrastructure","date":"2022-04-06","downloadLink":null,"version":"1.24.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you to upgrade the agent every 3 months. Added Regex support in passthrough_environment setting #1060 Additional instrumentation in integration payloads #1027 Changed bump nri-prometheus 2.8.0 -> 2.14.0 #1059","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1241","eolDate":"2024-04-06"},{"agent":"infrastructure","date":"2022-03-23","downloadLink":null,"version":"1.24.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the infrastructure agent . We recommend you to upgrade the agent every 3 months. Added https and mTLS support added to the infra-agent HTTP ingest endpoint #913 . Self-instrumentation of the agent via the Go APM agent (disabled by default) #981 . Passing the NRI_HOST_ID environment variable to v4 integrations #1021 . Changed Deprecated the register_enabled feature flag, and added a new sdk parameter to prevent entity registration #1015 .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1240","eolDate":"2024-03-23"},{"agent":"infrastructure","date":"2022-02-28","downloadLink":null,"version":"1.23.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Fixed Several CVEs for expat in the docker image: CVE-2022-25235 CVE-2022-25236 CVE-2022-25315 CVE-2022-25314","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1233","eolDate":"2024-02-28"},{"agent":"infrastructure","date":"2022-02-14","downloadLink":null,"version":"1.23.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Changed bump flex to v1.4.4 #976 Fixed decorate events with custom_attributes #939","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1232","eolDate":"2024-02-14"},{"agent":"infrastructure","date":"2022-02-08","downloadLink":null,"version":"1.23.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Added v3 integration config to v4 migration tool and warning notification when v3 configs are detected (#795 ) Example of v3tov4 notification time=\"2022-02-01T14:31:56Z\" level=warning msg=\"Integration v3 config detected. Recommended to migrate this config to v4 format. Command to migrate 'newrelic-infra -v3tov4=/etc/newrelic-infra/integrations.d/redis-config.yml:/var/db/newrelic-infra/newrelic-integrations/redis-definition.yml:/etc/newrelic-infra/integrations.d/com.newrelic.redis-v4.yml:false'\" component=PluginRegistry configFile=/etc/newrelic-infra/integrations.d/redis-config.yml integration=com.newrelic.redis Fixed fix CVE-2019-11254, GHSA-77vh-xpmg-72qh, GHSA-c72p-9xmj-rx3w (#907 )","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1231","eolDate":"2024-02-08"},{"agent":"infrastructure","date":"2022-01-25","downloadLink":null,"version":"1.23.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Changed Upgrade Gopsutil to v3 (#886 ) Fixed RPM plugin watcher for version 4.16 and higher (#901 )","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1230","eolDate":"2024-01-25"},{"agent":"infrastructure","date":"2019-03-14","downloadLink":null,"version":"1.2.25","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Improvements Added replacement of on-host integration's remote entity-names; when a loopback address is found, it will be replaced with agent entity-name. This change will be applied in the entity key and the hostname metric field (if present), when the data comes from an integration using protocol V3. See protocol V3 documentation  for further details. Bug fixes Fixed unreported processes issue caused by the inability to parse a different format of /proc//stat. Fixed a problem that caused the Windows agent to submit os:\"unknown\". Security updates Fixed a low security issue that caused the Windows agent to periodically access C:\\etc folder.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1225","eolDate":"2022-03-14"},{"agent":"infrastructure","date":"2022-01-17","downloadLink":null,"version":"1.22.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Added Adding custom attributes as extraLabels for OHIs while in forwarding mode #825 Partition file scanning #868 Changed Update base Alpine image => 3.15 #847  #852 Go 1.16.12 #888 Fixed Undetected changes on rpm packages inventory #848 Do not read sysctl deprecated item #855 Read the last line if no newline #862","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1220","eolDate":"2024-01-17"},{"agent":"infrastructure","date":"2019-02-27","downloadLink":null,"version":"1.2.15","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Changes Added support for defining integration arguments as environment variables in the configuration file. When defining the value of an argument in the integration configuration file with something that starts with $ (for example hostname: $HOSTNAME) the agent will try to expand the environment variable. Added internal configuration options for use in Kubernetes.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1215","eolDate":"2022-02-27"},{"agent":"infrastructure","date":"2019-02-25","downloadLink":null,"version":"1.2.13","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Changes Creation of nri-agent only when environment variable NRIA_MODE is set to PRIVILEGED or UNPRIVILEGED. Log when docker_api_version is not supported. Bug fixes Agent: Fix system sampler disk metrics problem when the same device is mounted multiple times causing increased values.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1213","eolDate":"2022-02-25"},{"agent":"infrastructure","date":"2022-01-10","downloadLink":null,"version":"1.21.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Fixed Corrects name in on-host integration reporting for integration protocol v3 payloads (integrationName in event samples). #823 Fixes issue when inventory was not correctly reset when changing entityID, as host was not visible in the UI after changing the reporting license_key for an active agent. #811 Added Logging of full path when loading config files. #820","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1210","eolDate":"2024-01-10"},{"agent":"infrastructure","date":"2019-01-17","downloadLink":null,"version":"1.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Features Added disable_all_plugins config option that disables all the inventory plugins which don't have their own frequency option specified. Check out the documentation . Added cpu_profile config option for creating pprof cpu profiles. Improvements Reduced CPU consumption by 80% on average. Changes Decreased sysctl sampling frequency. Bug fixes Fixed an issue that avoids the agent being installed in old Ubuntu versions.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-121","eolDate":"2022-01-17"},{"agent":"infrastructure","date":"2021-11-02","downloadLink":null,"version":"1.20.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Fixed Make the td-agent-bit dependency required for SLES 12.5 #786 Send inventory on secure forwarder mode #796","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1207","eolDate":"2023-11-02"},{"agent":"infrastructure","date":"2021-10-26","downloadLink":null,"version":"1.20.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Added Propagate agent process priority class to integrations in windows #772 Add log forwarder support for arm64: Amazon Linux 2, CentOS 7 & 8, Ubuntu 16.04, 18.04 & 20.04, Debian 8, 9 & 10 #778","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1206","eolDate":"2023-10-26"},{"agent":"infrastructure","date":"2021-10-18","downloadLink":null,"version":"1.20.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Changed Update nri-winservices to v0.5.0-beta #755 Fixed Windows issue detecting host shutdown which caused false HNR alerts #745 Improved performance on process sampler in macOS #760","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1205","eolDate":"2023-10-18"},{"agent":"infrastructure","date":"2021-09-30","downloadLink":null,"version":"1.20.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Added Added process sampler for macos #740 Changed Update nri-winservices to v0.4.0-beta #753 Fixed Only pass environment variables present in NRIA_PASSTHROUGH_ENVIRONMENT to v4 integrations #751","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1204","eolDate":"2023-09-30"},{"agent":"infrastructure","date":"2021-09-22","downloadLink":null,"version":"1.20.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Added Expanding infrastructure agent support for new OS versions: Ubuntu: 20.10 (groovy), 21.04 (Hirsute Hippo) Suse / SLES: 12.5, 15.1, 15.2, 15.3 Oracle Linux: 7, 8 Debian: 11(bullseye) Changed Update docker alpine curl dependency #737 Bump docker image to alpine@3.14  and curl and ntpsec to latest #744 Update log forwarder output plugin to v1.9.2 and fluent-bit v1.8.6 #742 Fixed Don't panic when process command line is not found in Windows #710 Log forwarder support for sles12.5 with fluent bit v1.8.6 #742","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1203","eolDate":"2023-09-22"},{"agent":"infrastructure","date":"2021-08-30","downloadLink":null,"version":"1.20.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Changed Bumped nri-winservices to v0.3.0-beta  #706","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1202","eolDate":"2023-08-30"},{"agent":"infrastructure","date":"2021-08-30","downloadLink":null,"version":"1.20.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Fixed Restart loop when trying to stop the Windows service #703 Enabled CGO for amd64. Fixes the issue username not found for processes when collecting process metrics #679","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1201","eolDate":"2023-08-30"},{"agent":"infrastructure","date":"2021-08-17","downloadLink":null,"version":"1.20.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Changed All environment variables defined in integration config files treated as uppercase. Also, the variables printed in payload output log. #676 . Added Brew formula file to publish the initial Beta of the infrastructure agent on Homebrew for macOS. See the homebrew-core PR status  and our public documentation  to learn more about requirements and limitations for macOS support. Fixed Certain configuration settings printed as memory addresses instead of values. For example, enable_process_metrics #647 .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1200","eolDate":"2023-08-17"},{"agent":"infrastructure","date":"2021-07-29","downloadLink":null,"version":"1.19.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Fixed Don't send inventory if forward only mode is enabled #659 Avoid executor possible goroutine leaks #658","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1194","eolDate":"2023-07-29"},{"agent":"infrastructure","date":"2021-07-26","downloadLink":null,"version":"1.19.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Changed Bump nri-prometheus #651 Bump nri-flex #653 Bump fluent-bit #632 Added MacOS instrumentation beta. Docs not published yet . Log truncated or dropped events #634 . Entity status API  #635 Fixed Lazy loaded dimensional metrics harvester, to avoid memory consumption when no dimensional metrics are sent. #648","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1193","eolDate":"2023-07-26"},{"agent":"infrastructure","date":"2021-07-08","downloadLink":null,"version":"1.19.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Changed 599  Add memory profile interval. 605  Bump nri-flex. 600  Upgrade fluent-bit version to 1.7.9.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1192","eolDate":"2023-07-08"},{"agent":"infrastructure","date":"2021-06-30","downloadLink":null,"version":"1.19.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Fixed 597  HTTP APIs regression introduced at v1.19.0 where status_server_enabled acted as http_server_enabled and viceversa.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1191","eolDate":"2023-06-30"},{"agent":"infrastructure","date":"2021-06-29","downloadLink":null,"version":"1.19.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nWe recommend you to upgrade the agent every 3 months. Added #589  Detailed log to help troubleshoot payloads sent to New Relic platform when pushing event samples (non dimensional metrics). This example  shows how to enable trace-level logging.\n#212  A temporal hostType value for boxes running in the cloud is defined  until cloud identifier gets resolved. Changed #562  Log forwarder as \"recommended\" package dependency in linux systems. Supported distributions have enabled \"recommends\" declared dependencies out of the box. Unless this is disabled, installation should be transparent. In case your distribution has disabled \"recommends\" dependencies you'll need to explicitly enable it via apt-get -o APT::Install-Suggests=\"true\" install newrelic-infra. #552  Goreleaser updated to version 0.169.0","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1190","eolDate":"2023-06-29"},{"agent":"infrastructure","date":"2018-12-14","downloadLink":null,"version":"1.1.9","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changes In the Linux agent, fixed a problem with the /var/run/newrelic-infra folder that could prevent the agent to correctly start under some circumstances.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-119","eolDate":"2021-12-14"},{"agent":"infrastructure","date":"2021-06-21","downloadLink":null,"version":"1.18.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Added Windows service recovery settings (documentation ). Changed Added identity, command channel, logging, and trace FedRamp endpoints . Curl version pump for container image. Fixed #221  - Issue that prevented the Windows service to exit when unexpected failures occured on the child process.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1182","eolDate":"2023-06-21"},{"agent":"infrastructure","date":"2021-06-11","downloadLink":null,"version":"1.18.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Added Added the following new host memory metrics (see documentation ): memoryCachedBytes memorySharedBytes memorySlabBytes Agent self instrumentation #477 This is a base implementation of a prometheus endpoint to gather some metrics about agent runtime and a few product metrics. In order to work, agent opens a port with prom data and starts nri-prometheus integration to scrap prom endpoint and send data to the backend. Status API #475 . See docs Changed Upgraded nri-prometheus to v2.7.0 #517 Updates Winlog.yml sample #336","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1181","eolDate":"2023-06-11"},{"agent":"infrastructure","date":"2021-05-31","downloadLink":null,"version":"1.18.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Added newrelic-infrastrucutre agent now supported on ARM architecture for linux. Fixed CVE-2020-14040  Updated golang.org/x/text/encoding/unicode dependency to avoid infinite loop #438 . Changed Upgraded FB win version up to v1.7.3 Upgraded nri-prometheus to v2.6.0 . Upgraded nri-flex to v1.4.1 . Upgraded curl in agent docker image to version 7.77.0-r0","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1180","eolDate":"2023-05-31"},{"agent":"infrastructure","date":"2021-05-04","downloadLink":null,"version":"1.17.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Fixed Log forwarder (FluentBit) missing libssl library. Error logged: Log forwarder was downgraded to previous agent release versions:","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1171","eolDate":"2023-05-04"},{"agent":"infrastructure","date":"2021-05-03","downloadLink":null,"version":"1.17.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Changed nri-docker to v1.6.0 . New memory and storage metrics added. memoryUsageBytes and memoryUsageLimitPercent calculation has changed. Please refer to this product update post  and nri-docker release notes  for more information. nri-winservices to v0.2.0-beta .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1170","eolDate":"2023-05-03"},{"agent":"infrastructure","date":"2018-12-11","downloadLink":null,"version":"1.1.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Changes Limited the inventory source field to 100 characters. This would only affect custom integrations with atypically long source names. Improvements For users with Facter  enabled, we provide the facter_home_dir configuration option that allows setting the HOME environment variable for Facter. If unset, it defaults to the current user's home directory. Bug fixes Fix a bug introduced in version 1.1.4 that prevented the agent running after a system restart.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-117","eolDate":"2021-12-11"},{"agent":"infrastructure","date":"2021-04-21","downloadLink":null,"version":"1.16.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Fixed The Log forwarder (FluentBit) stopped working on some Linux distribution versions (Ubuntu16, RHEL7, AmazonLinux2). See a sample error log: The Log forwarder has been downgraded to the previous agent release versions: Linux: output plugin to 1.1.0, FluentBit to 1.3.0 Windows: output plugin to 1.4.6, FluentBit to 1.4.1","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1165","eolDate":"2023-04-21"},{"agent":"infrastructure","date":"2021-04-20","downloadLink":null,"version":"1.16.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Changed Upgraded log-forwarder (FluentBit ) to v1.7.3 . Fixed Issue that caused package conflict errors during the installation process of the Linux infrastructure-agent.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1164","eolDate":"2023-04-20"},{"agent":"infrastructure","date":"2021-04-09","downloadLink":null,"version":"1.16.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Fixes Linux specific : Fixed issue when log-forwarder (Fluent Bit ) was not able to process systemd  logs. Due to a transition from building the Infra Agent in our previous internal pipeline to the publicly available GitHub actions, we applied the following changes: Included Fluent Bit 1.6.3, built by our previous internal pipeline, from (here)[https://github.com/newrelic/fluent-bit-package/releases/tag/1.3.0]. Included Fluent Bit Output Plugin for New Relic v1.4.3 from (here)[https://github.com/newrelic/newrelic-fluent-bit-output/releases/tag/v1.1.0].","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1163","eolDate":"2023-04-09"},{"agent":"infrastructure","date":"2021-04-06","downloadLink":null,"version":"1.16.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. We're releasing this version in a granular way. This means that we will release different asset types on different days (RPM, DEB, MSI, zip, targz, Docker).\nThis is required as we are releasing via our new open source build pipeline for the first time. Following releases will be done as usual, all assets at once. Changed newrelic-fluent-bit-output to v1.4.1 . Log forwarder feature comes with Fluent Bit version v1.6.3 , now obtained from (here)[https://github.com/newrelic/fluent-bit-package/releases/tag/1.4.1]. For more information about Logging feature, see our docs .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1162","eolDate":"2023-04-06"},{"agent":"infrastructure","date":"2021-03-25","downloadLink":null,"version":"1.16.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Fix #357  An issue with the agent update that disabled newrelic-infra-service and remain the agent stopped. Changed Downgrade newrelic-fluent-bit-output to v1.4.0 . Log forwarder feature has downgraded Fluent Bit to version v1.6.3  and downgraded Fluent Bit Output Plugin for New Relic to v1.4.3 . For more information about Logging feature, see our docs . newrelic/infrastructure agent docker image  only for amd64.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1161","eolDate":"2023-03-25"},{"agent":"infrastructure","date":"2021-03-24","downloadLink":null,"version":"1.16.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Updating RPM packages to this version will disable newrelic-infra-service. More details in #357 Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Added newrelic/infrastructure agent docker image  is now published as multi-arch (amd64 and arm64). Changed nri-docker built-in integration updated to v1.4.3 Log forwarder feature has updated Fluent Bit to version v1.7.2  available here  and Fluent Bit Output Plugin for New Relic to v1.4.6 . For more information about Logging feature, see our docs . nri-flex built-in integration updated to v1.4.0 . Deprecated CentOS 5 & RHEL 5 newrelic-infra packages are no longer published due to manufacturer end of life. Please check the system requirements documentation  for an updated list of supported OS and platforms.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1160","eolDate":"2023-03-24"},{"agent":"infrastructure","date":"2021-02-17","downloadLink":null,"version":"1.15.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly, at least every 3 months. Added Changed #307  Docker image update: alpine 3.13, ca-certificates 20191127-r5, ntpsec 1.2.0-r0, curl 7.74.0-r0 Fixed #302  Fixes an issue where literals within configuration files containing \"#\" (like password fields) caused an \"invalid configuration file\" error. This bug was introduced at v1.14.2 .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1152","eolDate":"2023-02-17"},{"agent":"infrastructure","date":"2021-01-29","downloadLink":null,"version":"1.15.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Added #288  Add tracing capabilities (enabled via trace: [\"proc\"]) to enable logging process IO counters as they are fetched from the OS. Changed #301  nri-flex updated to v1.3.10 . Fixed #299  Command API wrong allowed integration name and condition.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1151","eolDate":"2023-01-29"},{"agent":"infrastructure","date":"2021-01-25","downloadLink":null,"version":"1.15.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Fixed #275  SLES-11 service management clean stops/starts. #249  Agent configuration plugin serialises only fields defined as public (struct annotation). Changed #285  nri-flex updated to v1.3.9 . Added #286  Fedramp configuration flag  (fedramp: true) & remove gov license prefix. #287  Command channel run/stop_integration allow list.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1150","eolDate":"2023-01-25"},{"agent":"infrastructure","date":"2020-12-18","downloadLink":null,"version":"1.14.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Changed #274  nri-flex updated to v1.3.8 . #272  Drop comments from config files. Env-vars expansion won't take place when those are commented out.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1142","eolDate":"2022-12-18"},{"agent":"infrastructure","date":"2020-12-17","downloadLink":null,"version":"1.14.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Changed #271  More verbose connectivity error messages. #270  Increase obfuscated provider test coverage. Minor improvements for command-channel: #259  Event submission on command-api run_integration exit including exit-code. #261  Command channel metadata.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1141","eolDate":"2022-12-17"},{"agent":"infrastructure","date":"2020-12-15","downloadLink":null,"version":"1.14.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. Changed Integration protocol v4: Log entity registration errors / warning only when debug is enabled. Fix logic that checks max entity batch in bytes. #224  Allow list of infrastructure event fields restructured as deny list so that additional fields can be included. #235  Updated HTTP API to support all kind of integration payload versions, added support for exposing integrations API via raw TCP socket. #268  Update curl version  to fix CVEs Bundled integrations: Flex integration has been updated to version 1.3.7. For more information, see the nri-flex changelog . Docker integration has been updated to version 1.4.1. For more information, see the nri-docker changelog . Log forwarder: #255  Parser renamed to filter. #255  Removed deprecated folder parameter. Added Secrets management & environment variables support: #251  Agent configuration now supports secrets  to manage sensitive settings (databind variables block). See Secrets Management documentation #260  #263  #266  Added environment-variables replacement  support for agent & integration configuration files. Replacement of env-vars for agent config file using double curly braces {{ ENV_VAR }}. Env-vars replacement happens before YAML is parsed or databind  (secrets/variables engine) runs. #258  Added New Relic CLI  obfuscated support for secrets. See obfuscated provider  in Secrets management documentation.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1140","eolDate":"2022-12-15"},{"agent":"infrastructure","date":"2018-12-10","downloadLink":null,"version":"1.1.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Improvements Windows Docker  support for Windows Server 2016 hosts. Only Windows server native containers are supported. Bug fixes Fix a bug that prevented protected processes from being recorded by the agent in Windows.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-114","eolDate":"2021-12-10"},{"agent":"infrastructure","date":"2020-11-19","downloadLink":null,"version":"1.13.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . Added #126  The embedded telemetry API, responsible for sending dimensional metrics, now limits the amount of queued entities. This feature tends to avoid memory consumption when metrics can not be submitted. Agent and on-host integrations are now supported on Ubuntu 20.04 LTS (focal). Changed #222  The built-in Docker integration has been updated to version 1.3.3. For more information, see the nri-docker changelog . Log forwarder feature has updated Fluent Bit to version v1.6.3  and Fluent Bit Output Plugin for New Relic to v1.4.3 . For more information about Logging feature, see our docs .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1132","eolDate":"2022-11-19"},{"agent":"infrastructure","date":"2020-11-09","downloadLink":null,"version":"1.13.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . Added #155  The Infrastructure agent now handles entities' registration errors the following way (Infrastructure SDK v4 protocol): For request errors: Connectivity failure or limit exceeded (429 or 503 status codes) will trigger a retry with an exponential backoff with a maximum backoff of 1 minute. Other types of errors (including bad payload format) will be logged, and data will be discarded. For successful requests (200 status code) containing: Errors: The agent will discard related data. Warnings will be logged. #156  The Infrastructure agent entity registration now batches requests with a maximum of 1000 entities and payloads of 1Mb per call. #123  The embedded telemetry API now splits DM submission by number of entities following requested driven contract limitations. For more informations on the limits, see our docs Changed #206  The built-in Prometheus integration has been updated to version [2.3.0] (https://github.com/newrelic/nri-prometheus/releases/tag/v2.3.0 ). For more information about the Prometheus integration, see our documentation . Fixed #203  NFS invalid stats fix. #188  Prometheus summary type calculated as delta value to properly allow average calculation in NRQL. #167  Container processes now correctly filtered as host processes when Process Monitoring is enabled and \"include_matching_metrics\" rules are defined. For more information about enabling process monitoring  and filtering processes , see our documentation .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1131","eolDate":"2022-11-09"},{"agent":"infrastructure","date":"2020-10-29","downloadLink":null,"version":"1.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent . Added #172  The Infrastructure agent now includes the nri-prometheus v2.2.1  integration embedded with Linux packages and Docker image. For more information about the Prometheus integration, see our docs #152  Integrations with protocol v4 are now being registered and stored in memory by their unique entity name. #125  Improvements in protocol v4 dimensional metric submission. #174  Optional list of CLI arguments when configuration name is used instead of exec. Fixed #177  The Infrastructure agent now properly handles nested inventory items.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1130","eolDate":"2022-10-29"},{"agent":"infrastructure","date":"2020-10-16","downloadLink":null,"version":"1.12.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added #141  Support for prometheus summary and histogram metric types in the infrastructure SDK protocol v4. #145  Integrations based on SDK protocol V4 now submit events with the registered entity ID. #146  Log improvement to increase visibility when troubleshooting service failures. #164  Log forwarder feature supports verbose mode of Fluent Bit when running the agent in verbose mode. This will greatly help when troubleshooting Log Forwarder issues. For more information about Logging feature, see our docs Fixed #149  Host might start reporting as different entity when running on the cloud and the cloud API couldn't be reached or returned an error.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1127","eolDate":"2022-10-16"},{"agent":"infrastructure","date":"2020-10-06","downloadLink":null,"version":"1.12.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your infrastructure agent . Added #131  Dimensional metrics will be sent using collector_url configuration for fedRAMP compliance. Fixed #137  A bug in how collector_url is calculated to be FedRAMP compliance. For more information FedRAMP compliance, see our docs .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1126","eolDate":"2022-10-06"},{"agent":"infrastructure","date":"2020-09-21","downloadLink":null,"version":"1.12.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your infrastructure agent . Added #53  Dimensional metrics are now processed by the agent, registering entities for them. This feature is disabled under a feature-flag. #90  The log forwarder now captures the name of the file being tailed as Path_Key. #96  The agent now supports accessing secrets from CyberArk either using an HTTP endpoint or the CLI tool. For more information on secrets management using CyberArk, see our docs . Fixed #101  Fixed issue where the agent would panic when trying to compact inventory data. Changed #109  The built-in Flex integration  has been updated to version 1.3.5. For more information, see the Flex changelog . #108  curl has been updated to 7.69.1-r1 in the base image.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1125","eolDate":"2023-09-21"},{"agent":"infrastructure","date":"2020-09-03","downloadLink":null,"version":"1.12.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your infrastructure agent . Added #77 , #84  The Log Forwarder now supports Winlog events and allows EventID filtering For more information on the Log Forwarder, see Forward your logs using New Relic Infrastructure (Winlog) . Fixed #75  Fixed a bug that produced this error message can't save submission time when incorrectly trying to save submission time for the host entity that was not required. Changed #82  The built-in Flex integration  has been updated to version 1.3.4. For more information, see the Flex changelog . #78  Upgraded fsnotify to v1.4.9 to improve the detection of file system changes.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1124","eolDate":"2023-09-03"},{"agent":"infrastructure","date":"2020-08-24","downloadLink":null,"version":"1.12.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added a7b17c6  Inventory data collection could now work in a non-blocking manner: We now allocate a configurable inventory queue in the same fashion as metrics/events. This feature is disabled under a feature-flag . Fixed 71cc96b  Fixed issue in the storage sampler where we reported only one mount point for each device. Changed 14bcf94  The built-in Docker integration has been updated to version 1.3.2. For more information, see the nri-docker changelog","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1123","eolDate":"2023-08-24"},{"agent":"infrastructure","date":"2020-08-12","downloadLink":null,"version":"1.12.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Fixed PR-50  Fixed inventory deltas submission for remote (non host) entities. This fixes inventory errors showing up on the log for DEBUG level with message error field deltas not in expected order: have delta ID XXX, want YYY. Context Inventory deltas are JSON diffs and they need to be applied in order aiming to provide a consistent state. Both the infrastructure agent and the New Relic database stored their latest delta ID  received/submitted. This delta ID is incremented in each plugin entity inventory submission to New Relic. When these IDs go out of sync between agent and platform, the latter provides its latest known ID  for the given inventory plugin and entity. Then a reconciliation process is run by the agent for that plugin so that the next ID  will match the one expected by New Relic. Root cause For remote, non-host entities the agent side didn't store delta IDs on a per-entity basis as the New Relic database did. This means that for a given inventory plugin or integration providing more than 1 entity there'd be delta ID order  issues, which were only seen on agent's DEBUG level (verbose mode > 0). At some point all data would usually be submitted as reconciliation process attempts to fix this. But for high load integrations producing multiple remote entities this reconciliation process would be triggered every time an entity needs to be submitted as for each of them platform keeps a record, while the agent recorded ID on a per-plugin basis. Therefore, for high-load integrations, the agent reconciliation process might enter in race-condition loop when trying to fix the delta IDs. Fix This release fixes this behaviour by keeping track of delta IDs in the same way as the New Relic database does (or a per-plugin, per-entity basis). As state might be stored on disk for inventory deltas, if any integration had it persisted before the fix it'll take a reconciliation run per entity to fix agent's locally stored IDs. In this case you might still see some log entries, but they'll be gone during their first submissions.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1122","eolDate":"2023-08-12"},{"agent":"infrastructure","date":"2020-07-27","downloadLink":null,"version":"1.12.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added Beta version (v0.1.0-beta) of nri-winservices  is now packaged with the agent. For more information, see the Windows services integration documentation . Fixed d35cbe7  Fixed the sending of heartbeat samples to New Relic. 6503df0  Inventory is now fully re-sent if the host has been offline for 24 hours or if the agent ID changes. 4ccd9ff  Fixed issue where running Docker auto discovery was leaking file descriptors.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1121","eolDate":"2023-07-27"},{"agent":"infrastructure","date":"2020-07-20","downloadLink":null,"version":"1.12.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Processes metrics can be enabled for new accounts By default, the Infrastructure agent doesn't send data about the operating system's processes . The agent still collects such data, unless metrics_process_sample_rate  is set to -1. The sending of processes data to New Relic can be manually enabled by setting enable_process_metrics  to true. To fine-tune which processes you want to monitor, configure include_matching_metrics  or exclude_matching_metrics . Accounts and subaccounts created before July 20, 2020  have enable_process_metrics set to true by default; this can be overridden by setting a different value in the config file. Added f670501  Added ReadWriteBytesPerSecond to storage sampler. Fixed 1c06e93  Improved the handling of child process on Windows. 3394abd  Fixed a bug where Logs in Context  wouldn't map to an application when using the Infrastructure forwarder Updated KMS Secrets management to work correctly with credential_file and config_file. Removed some potential race conditions in the agent which should improve the stability of the agent. Fixed issue where storage sample would sometimes not report storage devices correctly. Changed 04335dd  Updated base Docker image for newrelic/infrastructure  (used by newrelic/infrastructure-k8s ) to Alpine 3.12 and also updated the packages to latest versions in the container. The built-in Flex integration  has been updated to version 1.3.2. For more information, see the Flex changelog . The built-in Docker integration has been updated to version 1.3.1. For more information, see the nri-docker changelog","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1120","eolDate":"2023-07-20"},{"agent":"infrastructure","date":"2019-01-14","downloadLink":null,"version":"1.1.19","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . New Features Adds support for running integrations as different users by setting the integration_user attribute in the instances section of the config file. Stops setting the NRIA_CACHE_PATH variable for integrations. This variable was used by pre-V3 SDK integrations for storing cache data. Without it the integrations will default to a /tmp directory like SDK V3 integrations. Attaches integration_user attribute to the integration samples. Adds new user/group nri-agent to be used in different user modes.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1119","eolDate":"2022-01-14"},{"agent":"infrastructure","date":"2020-06-02","downloadLink":null,"version":"1.11.45","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added SystemSample  has two new attributes,MemoryUsedPercent  and MemoryFreePercent . The log forwarder now supports the pattern parameter  for tcp and syslog For more information on the log forwarder feature, see Forward your logs using New Relic Infrastructure . Changed The built-in Flex integration  has been updated to version 1.3.1. For more information, see the Flex changelog . Fluent Bit Output plugin for New Relic has been upgraded to v1.3.0. For more information, see the changelog .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11145","eolDate":"2023-06-02"},{"agent":"infrastructure","date":"2020-05-25","downloadLink":null,"version":"1.11.42","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added The agent now adds Alibaba Cloud metadata, when available, to all data collected. When the agent runs in verbose mode, all integrations that support it now also run in verbose mode. When querying EC2 Instance Metadata Service  the agent now uses Instance Metadata Service v2 (IMDSv2) for all requests. For more information on why you should use IMDSv2, see this AWS blog post  .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11142","eolDate":"2023-05-25"},{"agent":"infrastructure","date":"2020-05-21","downloadLink":null,"version":"1.11.40","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added The agent now logs error and fatal messages from integrations even when not running in verbose mode. This feature is only available to integrations configured using the V4 configuration format found in versions 1.8.0  or higher of the agent. Fixed Fixed an issue where spaces in integration commands would sometimes get split incorrectly, causing the commands to fail. Changed The built-in Flex integration has been updated to version 1.3.0 For more information, see the Flex changelog The built-in Docker integration has been updated to version 1.3.0. For more information, see the nri-docker changelog","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11140","eolDate":"2023-05-21"},{"agent":"infrastructure","date":"2018-12-20","downloadLink":null,"version":"1.1.14","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Bug fixes Fixed wrong values in containerImageName for processes running inside a Docker container.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1114","eolDate":"2021-12-20"},{"agent":"infrastructure","date":"2020-03-23","downloadLink":null,"version":"1.11.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added Beta: Log forwarding allows you to forward logs to New Relic using the infrastructure agent. For more information, see Forward your logs using the New Relic infrastructure agent .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1114-0","eolDate":"2023-03-23"},{"agent":"infrastructure","date":"2020-05-08","downloadLink":null,"version":"1.11.37","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Security fixes In Linux, at startup, the agent ensures it has ownership of the integrations temporary data folder, /tmp/nr-integrations/ . This ensures only the agent/integrations can write into it negating potential abuse that could result in Denial/Degradation of Service.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11137-0","eolDate":"2023-05-08"},{"agent":"infrastructure","date":"2020-05-07","downloadLink":null,"version":"1.11.35","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added The Log Forwarder now adds additional validation and information logging when parsing the logging configuration files. Example configuration for the Log Forwarder has been added to the logging.d directory in the Infrastructure agent. When the Log Forwarder is started it will now only read YAML configuration files (*.yml and *.yaml). For more information on the Log Forwarder, see Forward your logs using New Relic Infrastructure . Fixed The Log Forwarder can now be started even if the hostname cannot be resolved. Changed The built-in Flex integration has been updated to version 1.2.2. For more information, see the Flex changelog . Fluent Bit Output for New Relic has been increased to 1.2.1, see the changelog","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11135","eolDate":"2023-05-07"},{"agent":"infrastructure","date":"2020-04-29","downloadLink":null,"version":"1.11.26","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added HTTP proxy support for the log forwarder. Log records are automatically sent through the same proxy used by the agent to send metrics. [BETA] HTTPS proxy support for the log forwarder.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11126","eolDate":"2023-04-29"},{"agent":"infrastructure","date":"2020-04-20","downloadLink":null,"version":"1.11.24","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added Agent version is now logged in non-verbose mode, too. Fixed A missing parsers configuration file for the log forwarder has been restored to the Windows installer. The mountInfo / diskstats mapping for fetching LVM volumes' I/O stats has been fixed; it can still fail for older systems that lack a mountInfo file and use custom names for their LVM volumes. A bug in the log forwarder that prevented some tcp and syslog URIs to be parsed correctly has been fixed. Changed The built-in Flex integration has been updated to version 1.1.2. For more information, see the Flex changelog . The built-in Docker integration has been updated to version 1.2.1. For more information, see the Docker integration changelog .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11124","eolDate":"2023-04-20"},{"agent":"infrastructure","date":"2020-04-14","downloadLink":null,"version":"1.11.22","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added Integrations can now be enabled or disabled via environment variables. This feature is only valid from version 1.8.0 , since it requires the V4 configuration format. Example: Changed Improvements in the agent internals to better support ECS environments.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11122","eolDate":"2023-04-14"},{"agent":"infrastructure","date":"2020-04-08","downloadLink":null,"version":"1.11.21","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added [Beta] Log forwarding can now collect Syslog logs. [Beta] Log forwarding can now collect logs over plain TCP socket connections. [Beta] Log forwarding can now be configured via user-provided Fluent-Bit configuration files. [Beta] Log forwarding is now able to include custom attributes for each log record as key-value pairs. For more information, see Forward your logs using New Relic Infrastructure .","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11121","eolDate":"2023-04-08"},{"agent":"infrastructure","date":"2020-04-01","downloadLink":null,"version":"1.11.20","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added The agent can now retrieve secrets from Vault  when running KV Secrets Engine - Version 1 . Log forwarder  entries now include hostname as an attribute. Changed Update nri-docker to v1.2.0  (beta Fargate) Security fixes Fixed an issue that could cause secrets to leak into log warning messages when using secrets management . Bug fixes Fixed a log forwarder error that occurred when enabling eventlog sources. Fixed an issue that could cause the storage sampler to not return all mount points for a device. Avoid spamming the log when agent can't get a process path. This happened mostly when dealing with Windows system-level processes.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11120","eolDate":"2023-04-01"},{"agent":"infrastructure","date":"2020-02-18","downloadLink":null,"version":"1.10.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added All the distributions of the Agent (packages, containers...) are shipped with nri-flex and nri-docker integrations, so you don't need to install them anymore. Agent Linux package  and containerized agent  both now include nri-docker . Before, only the package did. Agent Linux package  and containerized agent  both now include nri-flex . Before, none did. New containerized agent \"bundle\" was created from https://github.com/newrelic/infrastructure-bundle  , and published at (DockerHub)[https://github.com/newrelic/infrastructure-bundle] . \"Bundle\" container can now be released and included agent and integration versions could be tracked from the GH repository tags  and versions file. Bug fixes Auto-discovery annotations  no longer override integration metrics . For example: it avoids Kubernetes auto-discovery  overriding the cluster_name attributes if it's already set in the integration configuration. Removed a memory leak that caused a slow but constant increase in memory and CPU consumption (up to 1%cpu & 5MB per week).","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1107","eolDate":"2023-02-18"},{"agent":"infrastructure","date":"2020-03-20","downloadLink":null,"version":"1.10.41","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added The agent now includes the AWS region in the inventory  data under metadata/system when running in an AWS VM. Bug fixes Fixed bug on Debian 7 and Centos 5 where the agent would leave child processes running after receiving a service management stop instruction.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11041","eolDate":"2023-03-20"},{"agent":"infrastructure","date":"2020-03-17","downloadLink":null,"version":"1.10.35","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added Samplers  that are disabled are no longer pre-warmed avoiding errors messages in the log. Bug fixes Fixed an issue with the containerized agent where the agent would crash when the container is stopped Fixed an issue in Linux where in some situations the process display name would be empty Fixed an issue where in certain situations the unavailability of cpu metrics would lead to a crash","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11035","eolDate":"2023-03-17"},{"agent":"infrastructure","date":"2020-03-10","downloadLink":null,"version":"1.10.30","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added Improved auto discovery  of ports: If a container exposes ports 80 and 443, then ${discovery.port} or ${discovery.ports.0} would equal to port 80 and ${discovery.ports.1} to 443. As ports are are sorted in ascending order, port 8080 would have been assigned to number three and so on. Ports are also tagged by port type (usually TCP): ${discovery.ports.tcp} and ${discovery.ports.tcp.0} would equal to 80 and ${discovery.ports.tcp.1} to 443. Bug fixes On Windows, the agent can now report processes even when their command line cannot be gathered. The commandLine  attribute will be empty in those cases.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11030","eolDate":"2023-03-10"},{"agent":"infrastructure","date":"2020-02-27","downloadLink":null,"version":"1.10.26","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Added The agent now sends the integration name (integrationName) and version (integrationVersion) when any events are generated. For example, when using the Redis monitoring integration  integrationName will be set to com.newrelic.redis and integrationVersion to 1.4.0 nri-flex has been upgraded to version v1.0.0 . RPM packages generated now include the distribution name in the filename. For example: The RHEL8 package newrelic-infra-<version>-1.x86_64.rpm will now become newrelic-infra-<version>-1.el8.x86_64.rpm when published. Bug fixes The agent no longer panics on startup when reading corrupt caches files. When using new configuration format  the agent would create inventory as integration/<binary name> rather than integration/<integration name> breaking some charts. For better backwards compatibility the agent will now create inventory using the integration's name. For example, when using the Redis monitoring integration  before it would create inventory under integration/nri-redis but with the new update it will create it under inventory/com.newrelic.redis Sample text fields are now truncated to 4095 characters. Before these fields would be rejected and so would never appear in New Relic. Now the fields will appear but will be truncated.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-11026","eolDate":"2023-02-27"},{"agent":"infrastructure","date":"2018-09-17","downloadLink":null,"version":"1.0.989","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released, including some improvements and bug fixes. Follow standard procedures to update your Infrastructure agent . Improvements We now officially support SLES  12 Improved inventory submission reliability Bug fixes Fixed windows agent storage sample when a specific volume does not have permissions Fixed wrong storage metrics for containerized agent","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10989","eolDate":"2021-09-17"},{"agent":"infrastructure","date":"2018-07-31","downloadLink":null,"version":"1.0.976","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released, including some improvements and bug fixes. Follow standard procedures to update your Infrastructure agent . New features Add Support to Windows ReFS (Resilient FileSystem). Improvements Windows: optimized collection of processes and services data. Bug fixes Fixed a bug that caused the agent to switch between full and short reported hostname in some configurations. Windows: Fixed a bug that caused custom integrations being executed twice.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10976","eolDate":"2021-07-31"},{"agent":"infrastructure","date":"2018-06-27","downloadLink":null,"version":"1.0.944","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released, including some internal improvements and bug fixes. Follow standard procedures to update your Infrastructure agent . Improvements Slightly restructured the inventory cache to optimize its behavior when the agent identifier changes. Bug fixes Windows: Fixed a bug that avoids the submission of some metrics when the user changes the default namespace for Windows management instrumentation. Fixed an error that happens during the configuration parse of some Docker containers.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10944","eolDate":"2021-06-27"},{"agent":"infrastructure","date":"2018-05-24","downloadLink":null,"version":"1.0.912","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the Infrastructure agent has been released. Bug fixes Fixed disk usage above 100% in Windows. Fixed previous version bug causing zero values for CPU and IO in the process samples.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10912","eolDate":"2021-05-24"},{"agent":"infrastructure","date":"2018-05-23","downloadLink":null,"version":"1.0.909","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the Infrastructure agent has been released. Improvements Unix processes are now sampled in a non-blocking manner. Bug fixes In Linux, solved a bug that prevented the agent submitting the metrics from all the storage devices when reading the data from a single device failed. Fixed negative CPU steal in some old versions of Linux paravirtualized kernels.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10909","eolDate":"2021-05-23"},{"agent":"infrastructure","date":"2018-04-19","downloadLink":null,"version":"1.0.989","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent that fixes some bugs has been released. Bug fixes Fixed a bug that caused the agent to crash in some systems. Fixed an error message that displays after running new on-host integrations for the first time.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10898","eolDate":"2021-04-19"},{"agent":"infrastructure","date":"2018-04-09","downloadLink":null,"version":"1.0.888","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released, which includes a security fix. Improvements Disabled warning messages when caching new plugins info. The warning messages might have given the impression that there was an error or malfunction where the caching mechanism was working as intended. Bug fixes Security Bulletin NR18-05 : Fixed a security issue in which, under some premises, the process sampler may not strip correctly the command-line information and submit some sensitive data to the Process View. Fixed a problem where if the agent was disconnected for >24 hours and then would reconnect, it would not resend this data to New Relic. Fixed storage metrics calculations on Windows hosts. Fixed inventory of installed programs on Windows hosts, which were not correctly reported since v1.0.859.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10888","eolDate":"2021-04-09"},{"agent":"infrastructure","date":"2018-03-14","downloadLink":null,"version":"1.0.872","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Linux and Windows release. Improvements Allow disabling inventory of SELinux modules in hosts where the associated command consumes too much CPU. Set selinux_enable_semodule configuration option to false to disable it while keeping the rest of SELinux plugin features. Bug fixes Fixed a bug that avoided updating the information of a Linux process when its command name changes at runtime, or when a new process starts with a PID that already existed for a previous process.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10872","eolDate":"2021-03-14"},{"agent":"infrastructure","date":"2018-02-20","downloadLink":null,"version":"1.0.859","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Linux and Windows release. Improvements Implement Remote Entity for Inventories. Removed Cassandra and Crontab bundled plugin. Updated URLs for region-aware licenses. Bug fixes Fixed a deadlock that happened during Read/Write of large plugin outputs.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10859","eolDate":"2021-02-20"},{"agent":"infrastructure","date":"2018-02-08","downloadLink":null,"version":"1.0.848","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Linux and Windows release. Improvements Prevent multiple instances of an integration from running at the same time. Bug fixes Fixes issues with possibly corrupt JSON stored in the delta cache due to agent shutting down uncleanly. Security Bulletin NR18-05 : Fixes issue introduced in version 1.0.822 where command lines that included arguments that themselves had paths in them would trip up the parser and not properly strip out the command.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10848","eolDate":"2021-02-08"},{"agent":"infrastructure","date":"2018-01-31","downloadLink":null,"version":"1.0.840","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Linux and Windows release. Improvements Optimized inventory data gathering performance for sysctls. Updated YAML parsing to be more reliable. Can use dots in the names in inventory prefixes in integrations. Bug fixes Fixes a potential panic when trying to read network information.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10840","eolDate":"2021-01-31"},{"agent":"infrastructure","date":"2018-01-22","downloadLink":null,"version":"1.0.834","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Linux and Windows release. Improvements Factor built-in integration filters noisy puppet_agent_pid change events. Enhanced information available when running in verbose logging mode to help find StorageSample issues with unsupported file systems. StorageSamples are now collected for vxfs filesystem on Linux. Windows: svchost.exe processes will show more context info in their process names (akin to TaskMgr.exe behavior). Windows: Initial support for optional enabled_elevated_process_priv (set to true to use) which captures more process information if the account being used to run the agent has the SeDebugPrivilege right in its local policy. Bug fixes StorageSample I/O calculations that show percentage should now display a ceiling of 100%. Agent will better detect when a PID is reused on Linux and Windows, and refresh any cached information about that process. Windows: built-in integration lp.exe (List Packages), has been re-written to use the latest On Host Integration SDK and protocol. The original integration was not working reliably and could litter logs with warnings.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10834","eolDate":"2021-01-22"},{"agent":"infrastructure","date":"2017-12-20","downloadLink":null,"version":"1.0.822","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows release. Bug fixes If you are using the strip_command_line option in its default (true) setting, the command line value will properly handle paths with white space embedded in them. A memory leak found on Windows 10 and Windows Servers 2016 has been fixed.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10822","eolDate":"2020-12-20"},{"agent":"infrastructure","date":"2017-11-20","downloadLink":null,"version":"1.0.818","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. New features Adds support for latest versions of the Infrastructure Integration SDK. Adds support for identifying the Google Cloud Platform instance ID (NOTE: all the existent GCP nodes will be renamed as now we're adding the gcp prefix in the id. This may trigger false-positive host not reporting alerts) Bug fixes Fixes bug where absolute values specified in custom integration command lines would not be recognized. Fixes possible race condition when trying to collect storage metrics that could lead to a panic error and crash the agent. Fixes problem on Windows where agent would try to read the deprecated user_data folder and cause an error.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10818","eolDate":"2020-11-20"},{"agent":"infrastructure","date":"2017-11-14","downloadLink":null,"version":"1.0.808","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Bug fixes Deprecated Sysctl message will no longer appear in the logs. Containerized agents will now restart without an error.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10808","eolDate":"2020-11-14"},{"agent":"infrastructure","date":"2017-11-06","downloadLink":null,"version":"1.0.804","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Bugs Disk free/used percent now matches output from df -h on Linux. Docker container metadata now updates on a one-minute schedule. This will capture container changes such as restarts or container name changes. Payload compression for outgoing data will be turned on for all agents. To turn off compression, set the config setting payload_compression_level to 0.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10804","eolDate":"2020-11-06"},{"agent":"infrastructure","date":"2017-11-02","downloadLink":null,"version":"1.0.799","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Limit the scope of the agent's search for pidfiles in /var/run to a max depth of 3 Bugs Fixed bug causing sysctl inventory to always be blank When the same device is mounted to multiple paths, the device's IO metrics will be attached to each path's StorageSample event rather than just one of them When running in AWS, the Linux distribution string reported as \"linuxDistribution\" will no longer include the AMI ID Restored the output of external plugins in verbose logs Fixed inconsistency in processDisplayName values Removed \"Empty line handling plugin output\" message from verbose logs when the plugin was handled correctly","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10799","eolDate":"2020-11-02"},{"agent":"infrastructure","date":"2017-10-17","downloadLink":null,"version":"1.0.790","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Implemented Windows Disk Utilization metrics. Those can now be seen on the Storage and Compute pages. Bugs Fixed issue where hosts unable to retrieve Azure metadata did not show up in the UI","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10790","eolDate":"2020-10-17"},{"agent":"infrastructure","date":"2017-09-25","downloadLink":null,"version":"1.0.785","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Address the bug where custom attributes set in the agent were not being shown in the UI","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10785","eolDate":"2020-09-25"},{"agent":"infrastructure","date":"2017-09-19","downloadLink":null,"version":"1.0.783","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Container names will now be sent up as a part of the process sample","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10783","eolDate":"2020-09-19"},{"agent":"infrastructure","date":"2017-08-25","downloadLink":null,"version":"1.0.775","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Support for Windows AppData for all data cache, user_data, and integration related temp files. The log file is also written to %AppData%/New Relic/newrelic-infra/...instead of the Program Files location. Integrations can now invoke executables from the system path without using an absolute path to them, and the value of $PATH is passed through to integration executables For agents deployed inside containers, the Linux distribution and version will now reflect the parent host rather than the OS within the container itself","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10775","eolDate":"2020-08-25"},{"agent":"infrastructure","date":"2017-08-01","downloadLink":null,"version":"1.0.752","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Updated service code to make starting the New Relic Infrastructure Agent as a service faster","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10752","eolDate":"2020-08-01"},{"agent":"infrastructure","date":"2017-07-24","downloadLink":null,"version":"1.0.726","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Updates for On Host Integrations Fixes issues with Containerized Agent not displaying identifying information in UI","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10726","eolDate":"2020-07-24"},{"agent":"infrastructure","date":"2017-07-17","downloadLink":null,"version":"1.0.724","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Agent proxy config no longer appears in the inventory UI. This is to prevent information leaks","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10724","eolDate":"2020-07-17"},{"agent":"infrastructure","date":"2017-07-05","downloadLink":null,"version":"1.0.719","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Support for product_uuid and boot_id inventory  in the hostinfo (metadata/system) plugin. This is non-variance inducing inventory. Bug fixes No longer using dmidecode to gather hardware information. Please refer to docs  for more details Various other bug fixes","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10719","eolDate":"2020-07-05"},{"agent":"infrastructure","date":"2017-06-12","downloadLink":null,"version":"1.0.703","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Reduce log noise for short lived processes and built-in modules that are not active on the current platform. Agent can be run with empty config files or no config file at all (when using environment variables for necessary configuration options like your license key). Adds configuration option log_to_stdout (default is true). Set this option to false to restrict log output to a file only when log_file is configured. Bug fixes Fix so no extra command line elements are added when creating an On-Host Integration with no parameters using Python.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10703","eolDate":"2020-06-12"},{"agent":"infrastructure","date":"2017-05-17","downloadLink":null,"version":"1.0.690","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Better on-host integrations SDK support including pre-creating some require directories, skipping ill-configured integrations, and fixes around how the command for an integration definition is parsed. Bug fixes Optimization fixes for the amount of time needed to check whether on a cloud instance. Should try once and timeout quickly. Optional disable_cloud_metadata can be used if you need to force turn off collection of cloud-specific metadata.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10690","eolDate":"2020-05-17"},{"agent":"infrastructure","date":"2017-04-21","downloadLink":null,"version":"1.0.682","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Updates internal process for starting up and reading configuration files. Better handling of some configuration file formatting variants. Bug fixes Fixes an issue where Windows Storage metrics could fail when encountering removable drives.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10682","eolDate":"2020-04-21"},{"agent":"infrastructure","date":"2017-04-06","downloadLink":null,"version":"1.0.677","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Bug fixes Fixes agent crash if default Windows System Drive was other than C: Fixes bug where RPM packages were not starting after upgrades","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10677","eolDate":"2020-04-06"},{"agent":"infrastructure","date":"2017-03-22","downloadLink":null,"version":"1.0.673","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure  agent for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Also note that the build number was \"fast forwarded\" to fix a version related bug. Bug fixes High cross platform I/O rate change numbers now reporting correct storage, network, and processes. Improved diagnostics when calculating CPU usage in certain scenarios where it would appear unusually large. Fixes handling of Inventory naming prefix.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10673","eolDate":"2020-03-22"},{"agent":"infrastructure","date":"2017-03-16","downloadLink":null,"version":"1.0.341","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure  agent for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows only release. Bug fixes High Windows I/O read/write operations numbers now reporting correct network information.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10341","eolDate":"2020-03-16"},{"agent":"infrastructure","date":"2017-03-09","downloadLink":null,"version":"1.0.338","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure  agent for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Improved handling for configuration files syntax. Agent can recover more gracefully when inventory information is ill formed. lp.exe plugin (Windows Programs Inventory) significantly more performant. Entities (hosts) are less likely to get combined unexpectedly when starting Agent from AMIs or other images. Warns if you try to use \"localhost\" as the hostname. Network interface information captured as inventory.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10338","eolDate":"2020-03-09"},{"agent":"infrastructure","date":"2017-03-07","downloadLink":null,"version":"1.0.336","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Agent build 1.0.336 was superseded by 1.0.338. They contain the same improvements, but 1.0.338 includes a Windows release and fixes a dormant issue introduced in 1.0.336.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10336","eolDate":"2020-03-07"},{"agent":"infrastructure","date":"2017-02-09","downloadLink":null,"version":"1.0.323","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. Improvements Test if the configured license is obviously not correct. Check network availability at startup to ascertain agent can communicate with New Relic. Additional verbose logging for debugging network data. Added an event_queue_depth config option (default 1000) to support hosts with high numbers of processes (100s or more). Adjust this number in increments of 1000 if you see \"Queue full\" messages in the logs. Will require a restart of the agent to take effect.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10323","eolDate":"2020-02-09"},{"agent":"infrastructure","date":"2017-02-02","downloadLink":null,"version":"1.0.316","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See the Update the Infrastructure agent  for how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows and Linux release. New features Added an agent_config plugin that reports the agent's config file as inventory. Improvements Added more diagnostic logging when using verbose mode. Added configs to adjust the frequency of certain inventory plugins. Here we show the name of the config, the default sampling period in seconds, and the fastest the plugin will sample (its \"floor\". You should only change these values if advised by New Relic Support. sysctl_interval_sec, default: 10, floor: 10 daemontools_interval_sec, default: 15, floor: 10 supervisor_interval_sec, default: 15, floor: 10 systemd_interval_sec, default: 30, floor: 10 sysvinit_interval_sec, default: 30, floor: 10 upstart_interval_sec, default: 30, floor: 10 rpm_interval_sec, default: 30, floor: 30 dpkg_interval_sec, default: 30, floor: 30 facter_interval_sec, default: 30, floor: 30 selinux_interval_sec, default: 30, floor: 30","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10316","eolDate":"2020-02-02"},{"agent":"infrastructure","date":"2017-01-11","downloadLink":null,"version":"1.0.311","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See the document \"Update the Infrastructure agent\"  for instructions detailing how to download and update the appropriate version of the agent for your platform. Note also that this is a Windows only release. Improvements Added new fields ram, total_ram, cpu_name, cpu_num, total_cpu, and total_cores to metadata/system/system for Windows.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10311","eolDate":"2020-01-11"},{"agent":"infrastructure","date":"2017-01-11","downloadLink":null,"version":"1.0.308","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See the document \"Update the Infrastructure agent\"  for instructions detailing how to download and update the appropriate version of the agent for your platform. Note this is a Linux only release. Improvements Added new field total_ram to metadata/system/system for Linux that reports the amount of ram installed on the machine. Added new fields total_cpu and total_cores to metadata/system/system inventory for Linux that reports the total number of processors on the machine and the total number of cores (number of cores x number of processors). Added CPU steal field cpuStealPercent to SystemSample.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10308","eolDate":"2020-01-11"},{"agent":"infrastructure","date":"2016-12-28","downloadLink":null,"version":"1.0.301","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See the document \"Update the Infrastructure agent\"  for instructions detailing how to download and update the appropriate version of the agent for your platform. Bug fixes Fixes a regression where sestatus would be called even if SELinux features were inactive. Log file set in config will no longer be overwritten during agent restart","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10301","eolDate":"2019-12-28"},{"agent":"infrastructure","date":"2016-12-14","downloadLink":null,"version":"1.0.296","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic Infrastructure Agent builds are available for multiple platforms. See the document \"Update the Infrastructure agent\"  for instructions detailing how to download and update the appropriate version of the agent for your platform. Improvements Added config setting (ca_bundle_file and ca_bundle_dir) to enable users to specify a file location for a x509 certificate in .pem format to permit TLS communication with custom certificate authorities.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-10296","eolDate":"2019-12-14"},{"agent":"infrastructure","date":"2018-11-15","downloadLink":null,"version":"1.0.1051","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Improvements Add new improved Windows Storage Sampler based on PDH instead of WMI. This new sampler is faster and more reliable; it is activated by default, to revert to the old one you can set the legacy_storage_sampler option to true. Bug fixes Fix a bug where some inventory items could disappear. Fix bug with strip_command_line=true that could cause some processes to be discarded in the samples. Fix bug that prevented some inventory items from updating their state when asked for a full reset.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-101051","eolDate":"2021-11-15"},{"agent":"infrastructure","date":"2018-10-29","downloadLink":null,"version":"1.0.1033","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Bug fixes Fixed wrong log message: agent has been offline for 24h0m0s min. Recreating delta store triggered when there hasn't been any deltas to post for more than 24h. Fixed parsing error of who command output when using different locale values.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-101033","eolDate":"2021-10-29"},{"agent":"infrastructure","date":"2018-10-10","downloadLink":null,"version":"1.0.1019","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Bug fixes Fixed wrong log message introduced in version 1.0.1017: msg=\"error flushing inventory to cache\" error=<nil>.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-101019","eolDate":"2021-10-10"},{"agent":"infrastructure","date":"2018-10-09","downloadLink":null,"version":"1.0.1017","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Improvements Internal instrumentation for tracing custom-attributes","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-101017","eolDate":"2021-10-09"},{"agent":"infrastructure","date":"2018-10-08","downloadLink":null,"version":"1.0.1015","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released, including some improvements and bug fixes. Follow standard procedures to update your Infrastructure agent . Security Update A security update for the Windows Infrastructure agent corrects an issue where the agent may execute privileged binaries in the system path. Security bulletin NR18-11 . Improvements Add override_hostname and override_hostname_short configuration options, to disable hostname resolution and setting directly these values. Documentation available here . Bug fixes Fix errors with https values on the proxy configuration option. More information can be found in the troubleshooting guide . Fix 'error resolving entity identity' errors in log. Fix some hosts reporting localhost as full hostname. Fix some 0-value samples not being reported, and appeared as \"No value\" in the UI.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-101015","eolDate":"2021-10-08"},{"agent":"infrastructure","date":"2018-10-01","downloadLink":null,"version":"1.0.1002","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released, including some improvements and bug fixes. Follow standard procedures to update your Infrastructure agent . Improvements Added max_procs configuration option to specify the number of logical processors available to the agent. Increasing this value can help to distribute the load between different cores. Default value is 1. If value is set to -1 then it will try to read the environment variable GOMAXPROCS. If that variable is not set then the default value will be the total number of cores available in the host. Added ignore_system_proxy configuration option to make the Agent ignore the environment variables HTTP_PROXY and HTTPS_PROXY Bug fixes Fixed errors with https values on the proxy configuration option","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-101002","eolDate":"2021-10-01"},{"agent":"infrastructure","date":"2019-10-21","downloadLink":null,"version":"1.5.62","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Bug fixes When a wrong agent id was set up prior to have a cloud-id, agent was not able to migrate to a new more stable id once it got cloud-id. Now agent id is updated and new data is therefor attached to this more stable cloud-id.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/clone-new-relic-infrastructure-agent-1559","eolDate":"2022-10-21"},{"agent":"infrastructure","date":"2018-11-28","downloadLink":null,"version":"1.0.1052","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A new version of the agent has been released. Follow standard procedures to update your Infrastructure agent . Improvements Adds new functionality that will allow sample decoration from integrations that have add_hostname bool flag. Security Update A security update for the Windows agent corrects an issue where the agent may follow unprivileged hard links or junction folders. Security bulletin NR18-12 . Bug fixes Fix a bug with docker in AWS instances that caused the agent not to report Docker metrics. Fix a bug that was making the agent to log \"Plugin not registered\" during agent startup.","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/clone-new-relic-infrastructure-agent-101052","eolDate":"2021-11-28"},{"agent":"infrastructure","date":"2025-09-17","downloadLink":null,"version":"1.68.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"A new version of the agent has been released. Follow standard procedures to update the Infrastructure agent .\nNew Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is Infrastructure agent 1.51.0 . Changed Upgraded go version to 1.25.0 in #2125 Updated dependency newrelic/nri-winservices to v1.3.0 in #2128","slug":"docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/1680","eolDate":"2026-09-17"},{"agent":"kubernetes","date":"2026-09-15","downloadLink":null,"version":"4.7.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.6.3 nri-bundle-8.0.26","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-7-3","eolDate":"2027-09-15"},{"agent":"kubernetes","date":"2026-09-08","downloadLink":null,"version":"4.7.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.6.2 nri-bundle-8.0.24","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-7-2","eolDate":"2027-09-08"},{"agent":"kubernetes","date":"2026-08-31","downloadLink":null,"version":"4.7.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.6.1 nri-bundle-8.0.22","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-7-1","eolDate":"2027-08-31"},{"agent":"kubernetes","date":"2026-08-25","downloadLink":null,"version":"4.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.6.0 nri-bundle-8.0.20","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-7-0","eolDate":"2027-08-25"},{"agent":"kubernetes","date":"2026-08-05","downloadLink":null,"version":"4.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.5.0 nri-bundle-8.0.12","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-5-0","eolDate":"2027-08-05"},{"agent":"kubernetes","date":"2026-07-21","downloadLink":null,"version":"4.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.4.1 nri-bundle-8.0.8","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-4-1","eolDate":"2027-07-21"},{"agent":"kubernetes","date":"2026-07-14","downloadLink":null,"version":"4.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.4.0 nri-bundle-8.0.4","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-4-0","eolDate":"2027-07-14"},{"agent":"kubernetes","date":"2026-07-09","downloadLink":null,"version":"4.3.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.3.7 nri-bundle-8.0.2","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-3-7","eolDate":"2027-07-09"},{"agent":"kubernetes","date":"2026-07-02","downloadLink":null,"version":"4.3.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.3.6 nri-bundle-8.0.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-3-6","eolDate":"2027-07-02"},{"agent":"kubernetes","date":"2026-06-16","downloadLink":null,"version":"4.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.3.1 nri-bundle-7.0.21","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-3-1","eolDate":"2027-06-16"},{"agent":"kubernetes","date":"2026-06-09","downloadLink":null,"version":"4.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.3.0 nri-bundle-7.0.16","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-3-0","eolDate":"2027-06-09"},{"agent":"kubernetes","date":"2026-06-02","downloadLink":null,"version":"4.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.2.0 nri-bundle-7.0.14","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-2-0","eolDate":"2027-06-02"},{"agent":"kubernetes","date":"2026-05-19","downloadLink":null,"version":"4.1.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.1.1 nri-bundle-7.0.12","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-1-1","eolDate":"2027-05-19"},{"agent":"kubernetes","date":"2026-05-12","downloadLink":null,"version":"4.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.1.0 nri-bundle-7.0.10","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-1-0","eolDate":"2027-05-12"},{"agent":"kubernetes","date":"2026-04-21","downloadLink":null,"version":"4.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.0.1 nri-bundle-7.0.4","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-0-1","eolDate":"2027-04-21"},{"agent":"kubernetes","date":"2026-04-09","downloadLink":null,"version":"4.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-4.0.0 nri-bundle-7.0.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-4-0-0","eolDate":"2027-04-09"},{"agent":"kubernetes","date":"2023-03-21","downloadLink":null,"version":"3.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Updated dependencies Updated Kubernetes image registry Fix an issue where the agent fails when the kubelet is unavailable Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.7.0...v3.9.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-9-0","eolDate":"2024-03-21"},{"agent":"kubernetes","date":"2022-11-30","downloadLink":null,"version":"3.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Added Added support for KSM v2. You can check all the changes that come with the new KSM versions in the official documentation . Added support for k8s 1.25 from nri-bundle v5.0.0 . Changed Improved running e2e locally docs Updated testing certificates Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.5.0...v3.6.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-6-0","eolDate":"2023-11-30"},{"agent":"kubernetes","date":"2026-03-17","downloadLink":null,"version":"3.57.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.62.0 nri-bundle-6.0.42","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-57-0","eolDate":"2027-03-17"},{"agent":"kubernetes","date":"2026-03-10","downloadLink":null,"version":"3.56.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.61.0 nri-bundle-6.0.40","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-56-0","eolDate":"2027-03-10"},{"agent":"kubernetes","date":"2026-03-03","downloadLink":null,"version":"3.55.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.60.0 nri-bundle-6.0.39","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-55-0","eolDate":"2027-03-03"},{"agent":"kubernetes","date":"2026-02-17","downloadLink":null,"version":"3.54.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.59.0 nri-bundle-6.0.38","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-54-0","eolDate":"2027-02-17"},{"agent":"kubernetes","date":"2026-02-10","downloadLink":null,"version":"3.53.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.58.2 nri-bundle-6.0.37","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-53-2","eolDate":"2027-02-10"},{"agent":"kubernetes","date":"2026-02-03","downloadLink":null,"version":"3.53.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.58.1 nri-bundle-6.0.36","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-53-1","eolDate":"2027-02-03"},{"agent":"kubernetes","date":"2026-01-20","downloadLink":null,"version":"3.53.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.58.0 nri-bundle-6.0.35","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-53-0","eolDate":"2027-01-20"},{"agent":"kubernetes","date":"2025-12-30","downloadLink":null,"version":"3.52.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.57.0 nri-bundle-6.0.32","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-52-0","eolDate":"2026-12-30"},{"agent":"kubernetes","date":"2025-12-23","downloadLink":null,"version":"3.51.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.56.2 nri-bundle-6.0.31","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-51-2","eolDate":"2026-12-23"},{"agent":"kubernetes","date":"2025-12-16","downloadLink":null,"version":"3.51.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.56.1 nri-bundle-6.0.30","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-51-1","eolDate":"2026-12-16"},{"agent":"kubernetes","date":"2025-12-09","downloadLink":null,"version":"3.51.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.56.0 nri-bundle-6.0.27","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-51-0","eolDate":"2026-12-09"},{"agent":"kubernetes","date":"2025-11-25","downloadLink":null,"version":"3.50.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.55.2 nri-bundle-6.0.26","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-2","eolDate":"2026-11-25"},{"agent":"kubernetes","date":"2025-11-19","downloadLink":null,"version":"3.50.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.55.1 nri-bundle-6.0.25","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-1","eolDate":"2026-11-19"},{"agent":"kubernetes","date":"2025-11-10","downloadLink":null,"version":"3.50.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.55.0 nri-bundle-6.0.22","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-50-0","eolDate":"2026-11-10"},{"agent":"kubernetes","date":"2022-11-02","downloadLink":null,"version":"3.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Updated several dependencies Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.4.2...v3.5.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-5-0","eolDate":"2023-11-02"},{"agent":"kubernetes","date":"2025-11-04","downloadLink":null,"version":"3.49.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.54.0 nri-bundle-6.0.20","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-49-0","eolDate":"2026-11-04"},{"agent":"kubernetes","date":"2025-10-28","downloadLink":null,"version":"3.48.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.53.0 nri-bundle-6.0.19","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-48-0","eolDate":"2026-10-28"},{"agent":"kubernetes","date":"2025-10-21","downloadLink":null,"version":"3.47.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.52.0 nri-bundle-6.0.18","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-47-0","eolDate":"2026-10-21"},{"agent":"kubernetes","date":"2025-10-14","downloadLink":null,"version":"3.46.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.51.0 nri-bundle-6.0.17","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-46-0","eolDate":"2026-10-14"},{"agent":"kubernetes","date":"2025-10-06","downloadLink":null,"version":"3.45.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.50.4 nri-bundle-6.0.16","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-4","eolDate":"2026-10-06"},{"agent":"kubernetes","date":"2025-09-30","downloadLink":null,"version":"3.45.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.50.3 nri-bundle-6.0.15","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-3","eolDate":"2026-09-30"},{"agent":"kubernetes","date":"2025-09-16","downloadLink":null,"version":"3.45.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.50.2 nri-bundle-6.0.13","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-2","eolDate":"2026-09-16"},{"agent":"kubernetes","date":"2025-09-09","downloadLink":null,"version":"3.45.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.50.1 nri-bundle-6.0.12","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-1","eolDate":"2026-09-09"},{"agent":"kubernetes","date":"2025-08-26","downloadLink":null,"version":"3.45.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.50.0 nri-bundle-6.0.11","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-45-0","eolDate":"2026-08-26"},{"agent":"kubernetes","date":"2025-08-19","downloadLink":null,"version":"3.44.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.49.1 nri-bundle-6.0.10","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-44-1","eolDate":"2026-08-19"},{"agent":"kubernetes","date":"2025-08-12","downloadLink":null,"version":"3.44.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.49.0 nri-bundle-6.0.9","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-44-0","eolDate":"2026-08-12"},{"agent":"kubernetes","date":"2025-08-05","downloadLink":null,"version":"3.43.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.48.3 nri-bundle-6.0.8","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-3","eolDate":"2026-08-05"},{"agent":"kubernetes","date":"2025-07-22","downloadLink":null,"version":"3.43.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.48.2 nri-bundle-6.0.6","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-2","eolDate":"2026-07-22"},{"agent":"kubernetes","date":"2025-07-15","downloadLink":null,"version":"3.43.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.48.1 nri-bundle-6.0.5","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-1","eolDate":"2026-07-15"},{"agent":"kubernetes","date":"2025-07-01","downloadLink":null,"version":"3.43.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.48.0 nri-bundle-6.0.4","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-43-0","eolDate":"2026-07-01"},{"agent":"kubernetes","date":"2025-06-24","downloadLink":null,"version":"3.42.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.47.2 nri-bundle-6.0.3","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-2","eolDate":"2026-06-24"},{"agent":"kubernetes","date":"2025-06-17","downloadLink":null,"version":"3.42.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.47.1 nri-bundle-6.0.2","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-1","eolDate":"2026-06-17"},{"agent":"kubernetes","date":"2025-06-10","downloadLink":null,"version":"3.42.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.47.0 nri-bundle-6.0.1","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-42-0","eolDate":"2026-06-10"},{"agent":"kubernetes","date":"2025-06-05","downloadLink":null,"version":"3.41.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.46.0 nri-bundle-6.0.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-41-0","eolDate":"2026-06-05"},{"agent":"kubernetes","date":"2025-05-21","downloadLink":null,"version":"3.40.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.45.0 nri-bundle-5.0.124","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-40-0","eolDate":"2026-05-21"},{"agent":"kubernetes","date":"2022-09-13","downloadLink":null,"version":"3.4.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Updated several dependencies Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.4.1...v3.4.2","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-4-2","eolDate":"2023-09-13"},{"agent":"kubernetes","date":"2022-07-18","downloadLink":null,"version":"3.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed For Kubernetes versions higher than 1.21: having the apiServer flag service-account-extend-token-expiration set to false was causing the kubelet scraper pod to be restarted each time the token expired (each hour). In EKS due to its implementation a pod restart was caused each 90 days. Changed Updated several dependencies Full changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.4.0...v3.4.1","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-4-1","eolDate":"2024-07-18"},{"agent":"kubernetes","date":"2022-07-05","downloadLink":null,"version":"3.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Added Support for new k8s versions 1.23 & 1.24 Add k8s v1.23 & v1.24 new metrics: apiserverCurrentInflightRequestsMutating apiserverCurrentInflightRequestsReadOnly containerOOMEventsDelta nodeCollectorEvictionsDelta schedulerPendingPodsActive schedulerPendingPodsBackoff schedulerPendingPodsUnschedulable Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.3.1...v3.4.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-4-0","eolDate":"2024-07-05"},{"agent":"kubernetes","date":"2025-05-14","downloadLink":null,"version":"3.39.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.44.1 nri-bundle-5.0.123","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-39-1","eolDate":"2026-05-14"},{"agent":"kubernetes","date":"2025-04-29","downloadLink":null,"version":"3.39.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.44.0 nri-bundle-5.0.122","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-39-0","eolDate":"2026-04-29"},{"agent":"kubernetes","date":"2025-04-15","downloadLink":null,"version":"3.38.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.43.0 nri-bundle-5.0.120","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-38-0","eolDate":"2026-04-15"},{"agent":"kubernetes","date":"2025-04-08","downloadLink":null,"version":"3.37.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.42.0 nri-bundle-5.0.119","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-37-0","eolDate":"2026-04-08"},{"agent":"kubernetes","date":"2025-03-31","downloadLink":null,"version":"3.36.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.41.0 nri-bundle-5.0.118","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-36-0","eolDate":"2026-03-31"},{"agent":"kubernetes","date":"2025-03-25","downloadLink":null,"version":"3.35.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.40.1 nri-bundle-5.0.117","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-35-1","eolDate":"2026-03-25"},{"agent":"kubernetes","date":"2025-03-20","downloadLink":null,"version":"3.35.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.40.0 nri-bundle-5.0.116","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-35-0","eolDate":"2026-03-20"},{"agent":"kubernetes","date":"2025-02-19","downloadLink":null,"version":"3.33.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.38.3 nri-bundle-5.0.113","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-33-3","eolDate":"2026-02-19"},{"agent":"kubernetes","date":"2025-02-13","downloadLink":null,"version":"3.33.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.38.2 nri-bundle-5.0.112","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-33-2","eolDate":"2026-02-13"},{"agent":"kubernetes","date":"2025-01-28","downloadLink":null,"version":"3.33.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.38.1 nri-bundle-5.0.108","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-33-1","eolDate":"2026-01-28"},{"agent":"kubernetes","date":"2025-01-21","downloadLink":null,"version":"3.33.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.38.0 nri-bundle-5.0.107","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-33-0","eolDate":"2026-01-21"},{"agent":"kubernetes","date":"2025-01-15","downloadLink":null,"version":"3.32.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.37.4 nri-bundle-5.0.106","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-32-4","eolDate":"2026-01-15"},{"agent":"kubernetes","date":"2024-12-31","downloadLink":null,"version":"3.32.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.37.3 nri-bundle-5.0.105","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-32-3","eolDate":"2025-12-31"},{"agent":"kubernetes","date":"2024-12-10","downloadLink":null,"version":"3.32.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.37.1 nri-bundle-5.0.104","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-32-1","eolDate":"2025-12-10"},{"agent":"kubernetes","date":"2024-11-19","downloadLink":null,"version":"3.32.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.37.0 nri-bundle-5.0.102","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-32-0","eolDate":"2025-11-19"},{"agent":"kubernetes","date":"2024-11-12","downloadLink":null,"version":"3.31.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.36.0 nri-bundle-5.0.101","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-31-0","eolDate":"2025-11-12"},{"agent":"kubernetes","date":"2024-11-06","downloadLink":null,"version":"3.30.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.35.1 nri-bundle-5.0.100","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-30-1","eolDate":"2025-11-06"},{"agent":"kubernetes","date":"2024-10-29","downloadLink":null,"version":"3.30.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.35.0 nri-bundle-5.0.98","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-30-0","eolDate":"2025-10-29"},{"agent":"kubernetes","date":"2022-06-20","downloadLink":null,"version":"3.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Added nrFiltered attribute has been added to K8sNamespaceSamples when using namespace filtering Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.3.0...v3.3.1","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-3-1","eolDate":"2024-06-20"},{"agent":"kubernetes","date":"2022-06-13","downloadLink":null,"version":"3.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Added Now it is possible to scrape data only from selected namespaces. For further information refer to filtering namespaces Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.2.1...v3.3.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-3-0","eolDate":"2024-06-13"},{"agent":"kubernetes","date":"2024-10-08","downloadLink":null,"version":"3.29.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.34.6 nri-bundle-5.0.94","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-6","eolDate":"2025-10-08"},{"agent":"kubernetes","date":"2024-10-02","downloadLink":null,"version":"3.29.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.34.5 nri-bundle-5.0.93","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-5","eolDate":"2025-10-02"},{"agent":"kubernetes","date":"2024-08-13","downloadLink":null,"version":"3.29.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.34.4 nri-bundle-5.0.89","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-4","eolDate":"2025-08-13"},{"agent":"kubernetes","date":"2024-07-30","downloadLink":null,"version":"3.29.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.34.3 nri-bundle-5.0.88","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-3","eolDate":"2025-07-30"},{"agent":"kubernetes","date":"2024-07-16","downloadLink":null,"version":"3.29.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.34.2 nri-bundle-5.0.86","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-2","eolDate":"2025-07-16"},{"agent":"kubernetes","date":"2024-07-09","downloadLink":null,"version":"3.29.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.34.1 nri-bundle-5.0.85","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-1","eolDate":"2025-07-09"},{"agent":"kubernetes","date":"2024-06-25","downloadLink":null,"version":"3.29.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.34.0 nri-bundle-5.0.83","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-29-0","eolDate":"2025-06-25"},{"agent":"kubernetes","date":"2024-06-18","downloadLink":null,"version":"3.28.9","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.33.9 nri-bundle-5.0.82","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-9","eolDate":"2025-06-18"},{"agent":"kubernetes","date":"2024-05-28","downloadLink":null,"version":"3.28.8","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.33.8 nri-bundle-5.0.79","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-8","eolDate":"2025-05-28"},{"agent":"kubernetes","date":"2024-05-21","downloadLink":null,"version":"3.28.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.33.7 nri-bundle-5.0.78","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-7","eolDate":"2025-05-21"},{"agent":"kubernetes","date":"2024-05-15","downloadLink":null,"version":"3.28.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.33.6 nri-bundle-5.0.77","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-6","eolDate":"2025-05-15"},{"agent":"kubernetes","date":"2024-05-07","downloadLink":null,"version":"3.28.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.33.5 nri-bundle-5.0.76","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-5","eolDate":"2025-05-07"},{"agent":"kubernetes","date":"2024-04-30","downloadLink":null,"version":"3.28.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.33.4 nri-bundle-5.0.75","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-4","eolDate":"2025-04-30"},{"agent":"kubernetes","date":"2024-04-24","downloadLink":null,"version":"3.28.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.33.3 nri-bundle-5.0.74","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-3","eolDate":"2025-04-24"},{"agent":"kubernetes","date":"2024-04-16","downloadLink":null,"version":"3.28.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.33.2 nri-bundle-5.0.73","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-2","eolDate":"2025-04-16"},{"agent":"kubernetes","date":"2024-04-02","downloadLink":null,"version":"3.28.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.33.1 nri-bundle-5.0.72","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-1","eolDate":"2025-04-02"},{"agent":"kubernetes","date":"2024-03-26","downloadLink":null,"version":"3.28.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.33.0 nri-bundle-5.0.71","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-28-0","eolDate":"2025-03-26"},{"agent":"kubernetes","date":"2024-03-19","downloadLink":null,"version":"3.27.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.32.1 nri-bundle-5.0.70","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-27-1","eolDate":"2025-03-19"},{"agent":"kubernetes","date":"2024-03-12","downloadLink":null,"version":"3.27.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.32.0 nri-bundle-5.0.69","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-27-0","eolDate":"2025-03-12"},{"agent":"kubernetes","date":"2024-03-05","downloadLink":null,"version":"3.26.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.31.1 nri-bundle-5.0.68","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-26-1","eolDate":"2025-03-05"},{"agent":"kubernetes","date":"2024-02-27","downloadLink":null,"version":"3.26.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.31.0 nri-bundle-5.0.67","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-26-0","eolDate":"2025-02-27"},{"agent":"kubernetes","date":"2024-02-21","downloadLink":null,"version":"3.25.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.30.2 nri-bundle-5.0.66","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-25-2","eolDate":"2025-02-21"},{"agent":"kubernetes","date":"2024-02-13","downloadLink":null,"version":"3.25.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.30.1 nri-bundle-5.0.65","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-25-1","eolDate":"2025-02-13"},{"agent":"kubernetes","date":"2024-02-06","downloadLink":null,"version":"3.25.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.30.0 nri-bundle-5.0.62","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-25-0","eolDate":"2025-02-06"},{"agent":"kubernetes","date":"2024-01-30","downloadLink":null,"version":"3.24.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.29.2 nri-bundle-5.0.61","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-24-2","eolDate":"2025-01-30"},{"agent":"kubernetes","date":"2024-01-23","downloadLink":null,"version":"3.24.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.29.1 nri-bundle-5.0.60","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-24-1","eolDate":"2025-01-23"},{"agent":"kubernetes","date":"2024-01-09","downloadLink":null,"version":"3.24.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.29.0 nri-bundle-5.0.58","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-24-0","eolDate":"2025-01-09"},{"agent":"kubernetes","date":"2023-12-12","downloadLink":null,"version":"3.23.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.28.0 nri-bundle-5.0.55","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-23-0","eolDate":"2024-12-12"},{"agent":"kubernetes","date":"2023-12-08","downloadLink":null,"version":"3.22.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.27.0 nri-bundle-5.0.54","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-22-0","eolDate":"2024-12-08"},{"agent":"kubernetes","date":"2023-11-21","downloadLink":null,"version":"3.21.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.26.0 nri-bundle-5.0.46","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-21-0","eolDate":"2024-11-21"},{"agent":"kubernetes","date":"2023-11-14","downloadLink":null,"version":"3.20.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, check out the release notes in the nri-kubernetes repo . This integration is included in the following chart versions: newrelic-infrastructure-3.25.0 nri-bundle-5.0.45","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-20-0","eolDate":"2024-11-14"},{"agent":"kubernetes","date":"2022-05-31","downloadLink":null,"version":"3.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed Fixed rounding issue for allocatable cores https://github.com/newrelic/nri-kubernetes/issues/75 Changed Updated base alpine image from 3.15.4 to 3.16.0 Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.2.0...v3.2.1","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-2-1","eolDate":"2024-05-31"},{"agent":"kubernetes","date":"2022-05-02","downloadLink":null,"version":"3.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Added RestartCount metric for pods is now also available as restartCountDelta Fixed isReady metric is now correctly reported as false (rather than NULL) for pending pods Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.1.0...v3.1.1","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-2-0","eolDate":"2024-05-02"},{"agent":"kubernetes","date":"2023-11-07","downloadLink":null,"version":"3.19.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.24.0 nri-bundle-5.0.44","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-19-0","eolDate":"2024-11-07"},{"agent":"kubernetes","date":"2023-10-31","downloadLink":null,"version":"3.18.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.23.4 nri-bundle-5.0.43","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-18-4","eolDate":"2024-10-31"},{"agent":"kubernetes","date":"2023-10-25","downloadLink":null,"version":"3.18.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.23.3 nri-bundle-5.0.42","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-18-3","eolDate":"2024-10-25"},{"agent":"kubernetes","date":"2023-10-17","downloadLink":null,"version":"3.18.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.23.2 nri-bundle-5.0.41","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-18-2","eolDate":"2024-10-17"},{"agent":"kubernetes","date":"2023-10-15","downloadLink":null,"version":"3.18.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"For a detailed description of changes, see the release notes . This integration is included in the following chart versions: newrelic-infrastructure-3.23.1 nri-bundle-5.0.40","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-18-1","eolDate":"2024-10-15"},{"agent":"kubernetes","date":"2023-09-15","downloadLink":null,"version":"3.17.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Updated KSM version to v2.10.0 Updated dependencies Fixed bugs Full changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.16.0...v3.17.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-17-0","eolDate":"2024-09-15"},{"agent":"kubernetes","date":"2023-08-21","downloadLink":null,"version":"3.16.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Added full support for Kubernetes version 1.27 Updated dependencies Fixed bugs Full changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.15.3...v3.16.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-16-0","eolDate":"2024-08-21"},{"agent":"kubernetes","date":"2023-08-02","downloadLink":null,"version":"3.15.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Updated dependencies Fixed bugs Full changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.15.2...v3.15.3","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-15-3","eolDate":"2024-08-02"},{"agent":"kubernetes","date":"2023-07-31","downloadLink":null,"version":"3.15.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Updated dependencies Patched vulnerabilities Fixed bugs Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.15.1...v3.15.2","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-15-2","eolDate":"2024-07-31"},{"agent":"kubernetes","date":"2023-06-23","downloadLink":null,"version":"3.15.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Updated dependencies Patched vulnerabilities Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.15.0...v3.15.1","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-15-1","eolDate":"2024-06-23"},{"agent":"kubernetes","date":"2023-06-21","downloadLink":null,"version":"3.15.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Updated dependencies Improve testing Patched vulnerabilities Find the full changelog in GitHub .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-15-0","eolDate":"2024-06-21"},{"agent":"kubernetes","date":"2023-06-07","downloadLink":null,"version":"3.14.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Performance improvements Updated dependencies Improve testing Fix bug leading to kubelet scraper crash-looping in infrastructure-bundle Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.13.0...v3.14.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-14-0","eolDate":"2024-06-07"},{"agent":"kubernetes","date":"2023-05-30","downloadLink":null,"version":"3.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Performance improvements Updated dependencies Beta support for Kubernetes 1.27 (for testing and evaluation purposes only) Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.12.0...v3.13.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-13-0","eolDate":"2024-05-30"},{"agent":"kubernetes","date":"2023-05-15","downloadLink":null,"version":"3.12.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Added support for scraping metrics for Cronjobs, Jobs, PersistentVolumes and PersistentVolumeClaims Added KSM metrics recently promoted to stable category Added more workload name fields to K8sContainerSample, K8sPodSample Performance improvements Updated dependencies Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.9.0...v3.12.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-12-0","eolDate":"2024-05-15"},{"agent":"kubernetes","date":"2022-02-22","downloadLink":null,"version":"3.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Now kubernetes.io/tls secrets are supported when configuring mTLS authentication for controlplane Full Changelog: https://github.com/newrelic/nri-kubernetes/compare/v3.0.0...v3.1.0","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-1-0","eolDate":"2024-02-22"},{"agent":"kubernetes","date":"2022-02-03","downloadLink":null,"version":"3.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"This new version makes significant changes to the number of components that are deployed to the cluster, and introduces many new configuration options to tune the behavior to your environment. We encourage you to take a look at what's changed in full detail here . Breaking changes The number and format of the metrics reported by version 3 of the integration have not changed with respect to earlier versions. The format of the values.yml file has changed to accommodate the newly added configuration options. Please take a look at our migration guide  to see how to change your configuration. Changed Our solution is now deployed in three components: A DaemonSet to monitor the Kubelet, deployed in all nodes of the cluster. A second DaemonSet to monitor the control plane, deployed in master nodes only. A Deployment to collect metrics from kube-state-metrics, deployed in the same node as the latter. We now offer better control for CPU and memory limits and requests, which can be now configured for the three components individually. Impact of discovery and collection operations on the API server has been greatly reduced, thanks to the use of kubernetes informers . Logs messages have been greatly revamped to surface problems more clearly. Added Comprehensive configuration options have been added to provide fine-grain control to how the integration discovers and connects to metric providers. Remarkably: Discovery options for control plane components have been improved. You can check the details on how discovery is configured here . It is now possible to collect metrics from control plane components running outside of the cluster. Discovery options for KSM and the kubelet have also been added. The interval at which metrics are collected is now configurable .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-3-0-0","eolDate":"2024-02-03"},{"agent":"kubernetes","date":"2022-01-19","downloadLink":null,"version":"2.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Moved default config.sample to V4 , added a dependency for infra-agent version 1.20.0 Please notice that old V3  configuration format is deprecated, but still supported.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-9-0","eolDate":"2024-01-19"},{"agent":"kubernetes","date":"2021-11-22","downloadLink":null,"version":"2.8.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Updated agent and integrations to their latest version","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-8-3","eolDate":"2023-11-22"},{"agent":"kubernetes","date":"2021-11-08","downloadLink":null,"version":"2.8.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Updated agent and integrations to their latest versions","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-8-2","eolDate":"2023-11-08"},{"agent":"kubernetes","date":"2021-09-28","downloadLink":null,"version":"2.8.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Breaking changes With the addition of Kubernetes 1.22.x support, we are phasing out of the support bracket Kubernetes versions 1.15.x and below. This means the supported versions bracket for this version and the rest of the nri-kubernetes 2.8.x branch is from Kubernetes v1.16.x to v1.22.x. Users may still use previous versions of the integration and their Helm charts to instrument their clusters, and limited support will be offered for them. Development for said older versions is considered stopped and New Relic does not guarantee feature parity or bugfixes (security or otherwise) for those older versions. Changed Node status and conditions are now fetched from the API Server rather than KSM, which fixes some inconsistencies in the samples. This does not change which data is reported, and should be an invisible change. (#194). Add a series of parameters which allow to configure a jitter to be applied to API Server response caching, which might help to spread the load on large clusters. (#185).","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-8-1","eolDate":"2023-09-28"},{"agent":"kubernetes","date":"2021-09-20","downloadLink":null,"version":"2.7.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed Node status and conditions are now fetched from the Kubernetes API rather than KSM, which makes the query experience more consistent. Infrastructure agent and integrations have been updated to the latest versions.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-7-1","eolDate":"2023-09-20"},{"agent":"kubernetes","date":"2021-08-03","downloadLink":null,"version":"2.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Added Integration now reports node status and conditions as condition.{Name} (for example condition.Ready, condition.PIDPressure). Added the new KubeStateMetricsNamespace parameter to restrict discovery of KSM pod to a particular namespace. This should help reduce load in the control plane for clusters with many pods and/or nodes. Added the unschedulable metric to K8sNodeSamples. Added the podIP metric to K8sPodSample.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-7-0","eolDate":"2023-08-03"},{"agent":"kubernetes","date":"2021-06-07","downloadLink":null,"version":"2.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changed Upgrade infrastructure-bundle to 2.6.0 #123 See https://github.com/newrelic/infrastructure-bundle/releases/tag/2.6.0  for more details about the upgraded integrations in this release of the infrastructure-bundle","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-6-0","eolDate":"2023-06-07"},{"agent":"kubernetes","date":"2021-05-28","downloadLink":null,"version":"2.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changelog Changed Bumped all dependencies and moved to v2 in go.mod #111 Improved e2e tests with more coverage and support for Helm3 and Kubernetes 1.20-1.21 #110  #108 Improved KSM discovery logic #104","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-5-0","eolDate":"2023-05-28"},{"agent":"kubernetes","date":"2021-04-16","downloadLink":null,"version":"2.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changelog Added Added support for ARM and ARM64 nodes, and published a multiarch docker image.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-4-0","eolDate":"2023-04-16"},{"agent":"kubernetes","date":"2021-03-31","downloadLink":null,"version":"2.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changelog Fixed Correctly identifing the Kubernetes server version with characters (#81).","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-3-1","eolDate":"2023-03-31"},{"agent":"kubernetes","date":"2021-02-24","downloadLink":null,"version":"2.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changelog Changed The base image of newrelic/infrastructure-k8s has been updated to 2.2.3.\nMore info regarding all the upgraded integrations can be found in the release notes of the base image . Added Added metrics belonging to Horizontal Pod Autoscaler. More information about the collected metrics can be found in the official documentation . Fixed LoadBalancerIP was not being collected properly. It's now fetched from KSM metric kube_service_status_load_balancer_ingress.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-3-0","eolDate":"2023-02-24"},{"agent":"kubernetes","date":"2021-01-27","downloadLink":null,"version":"2.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changelog The base image of newrelic/infrastructure-k8s has been updated to 2.2.1. This base image has fixed an issue where nrjmx was not properly running due to the bundled java version. More info regarding all the upgraded integrations can be found in the release notes of the base image .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-2-0","eolDate":"2023-01-27"},{"agent":"kubernetes","date":"2021-01-04","downloadLink":null,"version":"2.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changelog Added aggregate CPU and memory request metrics for nodes.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-1-0","eolDate":"2023-01-04"},{"agent":"kubernetes","date":"2020-12-23","downloadLink":null,"version":"2.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changelog The base image of newrelic/infrastructure-k8s has been updated to 2.0.1.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-0-1","eolDate":"2022-12-23"},{"agent":"kubernetes","date":"2020-12-02","downloadLink":null,"version":"2.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Changelog Improve end-to-end testing and move it to GitHub Actions. Release Docker images and artifacts using GitHub Actions.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-2-0-0","eolDate":"2022-12-02"},{"agent":"kubernetes","date":"2019-08-28","downloadLink":null,"version":"1.9.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed:  The integration now uses the Infrastructure Agent v1.5.31. The biggest changes were major improvements to logging and to the StorageSampler. For more information, please refer to the infrastructure agent release notes  between versions v1.3.18 and v1.5.31.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-195","eolDate":"2022-08-28"},{"agent":"kubernetes","date":"2019-08-21","downloadLink":null,"version":"1.9.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Fixed:  The Docker image has been rebuilt to fix a regression related to the issue: moby/moby#35443 .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-194","eolDate":"2022-08-21"},{"agent":"kubernetes","date":"2019-08-01","downloadLink":null,"version":"1.9.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added:  Support for discovering KSMs when running with the label app.kubernetes.io/name. This should fix problems discovering KSM when deploying recent versions of their Helm chart.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-193","eolDate":"2022-08-01"},{"agent":"kubernetes","date":"2019-06-13","downloadLink":null,"version":"1.9.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Fixed:  The Docker image has been rebuilt to fix this issue: moby/moby#35443 .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-192","eolDate":"2022-06-13"},{"agent":"kubernetes","date":"2019-06-05","downloadLink":null,"version":"1.9.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Fixed:  The unprivileged version of Kubernetes integration was running as root after a restart of the container due to kubernetes/kubernetes#78308 . Fixed:  Autodiscovery cache directory permissions got changed from 644 to 744 in order to let the nri-agent user write inside. This change was necessary to release an unprivileged version of the Kubernetes integration.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-191","eolDate":"2022-06-05"},{"agent":"kubernetes","date":"2019-05-15","downloadLink":null,"version":"1.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed:  The integration now uses the Infrastructure agent v1.3.18 instead of 1.1.14. For more information about all changes in this update, see the Infrastructure agent release notes .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-190","eolDate":"2022-05-15"},{"agent":"kubernetes","date":"2019-04-15","downloadLink":null,"version":"1.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added:  The integration reports the name of the cluster as Infrastructure inventory. Added:  The integration reports a new event type K8sClusterSample. At this moment, these events contain only the cluster name as an attribute.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-180","eolDate":"2022-04-15"},{"agent":"kubernetes","date":"2019-03-26","downloadLink":null,"version":"1.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added : Support for kube-state-metrics (KSM) 1.5. Added : The reason and message attributes are added to K8sPodSample. This will provide visibility into why a pod status is Failed. For example, a pod that failed due to memory pressure on the node will report the following attributes: Status: Failed Reason: Evicted Message: Pod The node was low on resource: [MemoryPressure] It is possible to create an alert for any of these attributes. Added : The memoryWorkingSetBytes attribute is added to K8sContainerSample. This metric is used by the OOMkiller to decide when a container is using too much memory compared to its limit and should therefore be killed. It will enable more precise monitoring of the memory usage for containers. Changed : Always request metrics from kube-state-metrics in text format. In KSM's v1.5 this is the default regardless of the format requested.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-170","eolDate":"2022-03-26"},{"agent":"kubernetes","date":"2019-02-12","downloadLink":null,"version":"1.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added : namespaceName attribute was added to all the samples where the namespace attribute is present. This is to align with standard naming for attributes. Other examples: clusterName, podName, etc. Deprecated : namespace attribute is deprecated. We recommend using namespaceName instead.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-160","eolDate":"2022-02-12"},{"agent":"kubernetes","date":"2019-01-22","downloadLink":null,"version":"1.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed : Starting in version 1.5.0, the Kubernetes integration is not reporting the status of static pods anymore to avoid report an incorrect status. The following Github Issue tracks the progress of the bugfix in Kubernetes source code: https://github.com/kubernetes/kubernetes/issues/61717 .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-150","eolDate":"2022-01-22"},{"agent":"kubernetes","date":"2019-01-22","downloadLink":null,"version":"1.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed : Starting in version 1.5.0, the Kubernetes integration is not reporting the status of static pods anymore to avoid report an incorrect status. The following Github Issue tracks the progress of the bugfix in Kubernetes source code: https://github.com/kubernetes/kubernetes/issues/61717 .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-150-0","eolDate":"2022-01-22"},{"agent":"kubernetes","date":"2019-01-07","downloadLink":null,"version":"1.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed : Starting in version 1.4.0, the Kubernetes integration is using Alpine Linux as the base image. With Alpine the new image is smaller (16 MB instead of the previous 85 MB) and more secure. Alpine reduces the number of packages and libraries to the bare minimum, thus reducing the attack surface.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-140","eolDate":"2022-01-07"},{"agent":"kubernetes","date":"2018-11-07","downloadLink":null,"version":"1.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added : Pod Volume metrics. Monitor disk volume space and inodes for Volumes  and Persistent Volumes  associated with pods. See the detailed list of attributes in the documentation . Added : Cluster name is now added to agent data as the clusterName attribute so that you can easily correlate Kubernetes integration data with agent data. Fixed : In version 1.3.0, the volume bytes and inodes usage percentage calculation were incorrect.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-131","eolDate":"2021-11-07"},{"agent":"kubernetes","date":"2020-11-26","downloadLink":null,"version":"1.26.8","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Fixed:  upgraded Docker base image newrelic/infrastructure-bundle to v1.6.0. For more information on the release please see the New Relic Infrastructure bundle release notes .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1268","eolDate":"2022-11-26"},{"agent":"kubernetes","date":"2020-11-13","downloadLink":null,"version":"1.26.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Fixed: When configuring API_SERVER_ENDPOINT_URL with https endpoint, the api-server component will use that that instead of the default. More info at issue #41","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1267","eolDate":"2022-11-13"},{"agent":"kubernetes","date":"2020-11-12","downloadLink":null,"version":"1.26.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Fixed: When discovering kube-state-metrics behind a headless service, the DNS discovery will now return an error. Previously it was considered successful, and returned \"None\" as endpoint.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1266","eolDate":"2022-11-12"},{"agent":"kubernetes","date":"2020-10-22","downloadLink":null,"version":"1.26.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed:  Container identifiers are properly parsed when systemD driver is being used Container identifiers are no longer prefixed with crio  and suffixed with .scope","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1265","eolDate":"2022-10-22"},{"agent":"kubernetes","date":"2020-09-23","downloadLink":null,"version":"1.26.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Addded:  Add restartCount  metric to containers in the waiting  and terminated  states For containers that enter a crash loop, this value was not being reported in the Kubernetes Explorer","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1264","eolDate":"2023-09-23"},{"agent":"kubernetes","date":"2020-09-23","downloadLink":null,"version":"1.26.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Addded:  Add restartCount  metric to containers in the waiting  and terminated  states For containers that enter a crash loop, this value was not being reported in the Kubernetes Explorer","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1264-0","eolDate":"2023-09-23"},{"agent":"kubernetes","date":"2020-09-07","downloadLink":null,"version":"1.26.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog **Changed:**Upgrade Docker image to use Tini entrypoint solving: Reaps orphaned zombie process attached to PID 1 Correctly forwards signals to CMD processRead for more details: https://blog.phusion.nl/2015/01/20/docker-and-the-pid-1-zombie-reaping-problem/ Changed:  Upgraded Docker base image newrelic/infrastructure-bundle to v1.5.1.For more information on the release please see the New Relic Infrastructure Bundle release notes .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1262","eolDate":"2023-09-07"},{"agent":"kubernetes","date":"2020-08-26","downloadLink":null,"version":"1.26.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed:  Upgraded Docker base image newrelic/infrastructure-bundle to v1.5.0.For more information on the release please see the New Relic Infrastructure Bundle release notes .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1261","eolDate":"2023-08-26"},{"agent":"kubernetes","date":"2020-08-13","downloadLink":null,"version":"1.26.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added:  Support for OpenShift 4.5 and Kubernetes versions 1.18.X Changed:  Upgraded Docker base image newrelic/infrastructure-bundle to v1.4.2.For more information on the release please see the New Relic Infrastructure Bundle release notes . Changed:  When querying the summary endpoint from Kubelet to get the Node or Pod network metrics, if the default network interface is not eth0 then summary endpoint for Kubelet doesn't return the metrics as we expect them. We rely on them being a direct member of the \"network\" object. See rxBytes, txBytes and rxErrors in the following example metrics: This scenario only happens when the default interface is eth0. Kubernetessource code has it hardcoded that eth0 is the default. In the followingexample you can see that we only have network metrics inside the interfaceslist, in this case there is no eth0 on the and the default interface is ens5: In cases like this, the integration will look for the default interfaceinside the interfaces list and use those values. The default interface nameis retrieved from the network route file (default /proc/net/route). When running the unprivileged version of the integration we don't have accessto the route file, the integration won't be able to get the default interfacename and won't send network metrics for the unless there's a networkinterface called eth0. For Pods, this issue is mainly present when using hostNetwok since theyshared the same network interfaces with the Node.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1260","eolDate":"2023-08-13"},{"agent":"kubernetes","date":"2020-07-30","downloadLink":null,"version":"1.25.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added:  Support for OpenShift 4.4 and Kubernetes versions 1.17.X Changed:  Upgraded Docker base image newrelic/infrastructure-bundle to v1.4.1.For more information on the release please see the New Relic Infrastructure Bundle release notes . Changed:  When retrieving control plane metrics from the API server to generate the K8sApiServerSample, the integration now uses by default the secure port localhost:443 with the service account's bearer authentication. If the query on the secure port fails, it will fallback automatically to the non-secure one localhost:8080, this should preserve the same behavior as previous versions. If your cluster uses a different secure port to expose its metrics you can use the configuration option API_SERVER_ENDPOINT_URL  to specify it.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1250","eolDate":"2023-07-30"},{"agent":"kubernetes","date":"2020-07-20","downloadLink":null,"version":"1.24.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed:  Upgraded Docker base image newrelic/infrastructure-bundle to v1.4.0.For more information on the release please see the New Relic Infrastructure Bundle release notes .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1240","eolDate":"2023-07-20"},{"agent":"kubernetes","date":"2020-07-10","downloadLink":null,"version":"1.23.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Fixes a bug that was swapping the values for Node Allocatable Resources with the Node Capacity Resources in the K8sNodeSample.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1231","eolDate":"2023-07-10"},{"agent":"kubernetes","date":"2020-06-12","downloadLink":null,"version":"1.23.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Kubernetes 1.16  is now officially supported! The minimum supported version of kube-state-metrics for this release is 1.9.5, according to the KSM compatibility matrix . Added container throttling metrics to the K8sContainerSample: containerCpuCfsPeriodsDelta: Delta change of elapsed enforcement period intervals. containerCpuCfsThrottledPeriodsDelta: Delta change of throttled period intervals. containerCpuCfsThrottledSecondsDelta: Delta change of duration the container has been throttled. containerCpuCfsPeriodsTotal: Number of elapsed enforcement period intervals. containerCpuCfsThrottledPeriodsTotal: Number of throttled period intervals. containerCpuCfsThrottledSecondsTotal: Total time duration the container has been throttled. Added container mmap byte usage metrics to the K8sContainerSample: containerMemoryMappedFileBytes: Size of memory mapped files in bytes.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1230","eolDate":"2023-06-12"},{"agent":"kubernetes","date":"2020-06-04","downloadLink":null,"version":"1.22.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed:  Upgraded the base image newrelic/infrastructure-bundle  to v1.3.9. For more information on the release please see the New Relic Infrastructure Bundle release notes .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1220","eolDate":"2023-06-04"},{"agent":"kubernetes","date":"2020-05-22","downloadLink":null,"version":"1.21.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"The Kubernetes integration v1.21.0 brings several changes related to node allocatable resources . Cluster explorer Cluster dashboard Kubernetes metrics Changes to the cluster explorer We added support for allocatable resources to the Kubernetes cluster explorer : The cluster explorer entity list now calculates CPU usage by summing the allocatableCpuCores from the K8sNodeSample instead of using processorCount from SystemSample. Similarly, memory usage is now calculated by summing allocatableMemoryBytes instead of memoryTotalBytes. Pods' columns now refer to running pods vs. allocatable pods. In addition to resource consumption, the node's tooltip in the cluster explorer now shows the amount of allocatable pods used by the node. The node card, which appears when clicking a node in cluster explorer, now shows resource consumption (CPU, memory, and storage) against the allocatable resources. CPU usage aggregates cpuUsedCores, cpuRequestedCores, and cpuLimitCores from K8sContainerSample, and allocatableCpuCores from the K8sNodeSample. Memory usage aggregates memoryWorkingSetBytes, memoryRequestedBytes, and memoryLimitBytes from K8sContainerSample, and allocatableMemoryBytes from K8sNodeSample. Storage usage relies on fsUsedBytes and fsCapacityBytes fromK8sNodeSample. A new pods widget has been added to the node card that shows the amount of pods used against the total allocatable pods of the node. If you run the unprivileged version of the Kubernetes integration , you can now see the node metrics. Previously, this was only possible with the privileged version. Changes to the cluster dashboard [#clusterdashboard] The cluster explorer dashboard, which appears when clicking Kubernetes dashboard , has been updated to account for resource consumption against allocatable resources. CPU widgets displays cpuUsedCores and allocatableCpuCores from K8sNodeSample. As for Memory usage, it now shows memoryWorkingSetBytes and allocatableMemoryBytes. Disk widgets use fsUsedBytes and fsCapacityBytes from K8sNodeSample. A new pods widget has been added that shows the amount of pods used against the total allocatable pods of the cluster. Changes to Kubernetes metrics  [#k8smetrics] Node allocatable resources  and capacity are retrieved from the API server and added to the K8sNodeSample as capacity<ResourceName> and allocatable<ResourceName>. The Kubernetes server version is now retrieved from the API server and cached with the APIServerCacheK8SVersionTTL config option. The version is added to K8sClusterSample as clusterK8sVersion, and to the inventory. Add support for static pods status for Kubernetes server versions 1.15 or newer. In older versions of Kubernetes, the kubeletes wouldn’t sync  the status of the static pods with the API server and would always return a Pending status. This behavior was fixed in v1.15 of Kubernetes. Our integration now detects what version of Kubernetes the cluster is running and, if it’s 1.15 or newer, it adds the status of the static pods in K8sPodSample. Other changes We have upgraded the newrelic/infrastructure-bundle  base image to v1.3.8. For more information, see the New Relic Infrastructure Bundle release notes .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1210","eolDate":"2023-05-22"},{"agent":"kubernetes","date":"2020-04-24","downloadLink":null,"version":"1.20.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed:  Upgraded the base image newrelic/infrastructure-bundle  to v1.3.5. For more information on the release please see the New Relic Infrastructure Bundle release notes .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1200","eolDate":"2023-04-24"},{"agent":"kubernetes","date":"2018-08-21","downloadLink":null,"version":"1.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added: Add 'reason' metric for containers in the 'Terminated' status. In the previous versions, the 'reason' was already captured for the 'Waiting' status.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-120","eolDate":"2021-08-21"},{"agent":"kubernetes","date":"2020-04-21","downloadLink":null,"version":"1.19.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added:  new label combination to discover the Kubernetes controller manager: app=controller-manager controller-manager=true Changed:  Upgraded the base image newrelic/infrastructure-bundle  to v1.3.4. For more information on the release please see the New Relic Infrastructure Bundle release notes .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1190","eolDate":"2023-04-21"},{"agent":"kubernetes","date":"2020-04-07","downloadLink":null,"version":"1.18.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed:  Upgraded the base image newrelic/infrastructure-bundle  to v1.3.2. For more information on the release please see the New Relic Infrastructure Bundle release notes .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1180","eolDate":"2023-04-07"},{"agent":"kubernetes","date":"2020-03-26","downloadLink":null,"version":"1.17.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed:  Upgraded the base image newrelic/infrastructure-bundle  to v1.3.0. For more information on the release please see the New Relic Infrastructure Bundle release notes .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1170","eolDate":"2023-03-26"},{"agent":"kubernetes","date":"2020-03-12","downloadLink":null,"version":"1.16.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added:  Support for completely avoid querying Kube State Metrics. It's behind the DISABLE_KUBE_STATE_METRICS environment variable and its default value is false. Note that disabling this will imply missing metrics that are collected from KSM and possibly missing features in the Kubernetes cluster explorer. Please, refer to our official documentation on this configuration option  for more information.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1160","eolDate":"2023-03-12"},{"agent":"kubernetes","date":"2020-02-27","downloadLink":null,"version":"1.15.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added:  support for querying Kube State Metrics (KSM) instances behind kube-rbac-proxy . This feature only works when paired with the label-based KSM discovery (see release notes of version 1.11.0  for more information). This adds two new environment variables that allow deeper configuration of the feature: KUBE_STATE_METRICS_SCHEME: Whether the query should use the http or https protocols. Defaults to http and doesn't introduce a breaking change in behavior. KUBE_STATE_METRICS_PORT: The port in which the kube-rbac-proxy instance is listening on. You can confirm this by describing your KSM pod. Defaults to 8080 and doesn't introduce a breaking change in behavior. Added:  Added 4 new environment variables to explicitly set the control plane component base URLs. These variables can be used for Kubernetes configurations, such as OpenShift , that are different than the defaults defined in the section Discovery of master nodes and control plane components . See the section OpenShift 4.x Configuration  for more information. SCHEDULER_ENDPOINT_URL: The base URL of the scheduler pod metrics endpoint. The default is the empty string. In this case, the default configuration  will be used. ETCD_ENDPOINT_URL: The base URL of the ETCD pod metrics endpoint. The default is the empty string. In this case, the default configuration  will be used. CONTROLLER_MANAGER_ENDPOINT_URL: The base URL of the controller manager pod metrics endpoint. The default is the empty string. In this case, the default configuration  will be used. API_SERVER_ENDPOINT_URL: The base URL of the API server pod metrics endpoint. The default is the empty string. In this case, the default configuration  will be used. Fixed:  A bug preventing attributes named like selector.<label_name> from being added to some entries in the K8sServiceSample. Changed:  The integration now uses newrelic/infrastructure-bundle  as the base image. The tag used is for the version 1.2.0. For more information on this image please see the New Relic Infrastructure Bundle releases notes .","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1150","eolDate":"2023-02-27"},{"agent":"kubernetes","date":"2020-02-13","downloadLink":null,"version":"1.14.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed:  Internal changes in the code without any expected customer impact.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1140","eolDate":"2023-02-13"},{"agent":"kubernetes","date":"2020-01-29","downloadLink":null,"version":"1.13.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed:  The integration now uses the Infrastructure agent v1.9.0. For more information refer to the Infrastructure agent release notes  between versions v1.8.32 and v1.9.0.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1132","eolDate":"2023-01-29"},{"agent":"kubernetes","date":"2020-01-23","downloadLink":null,"version":"1.13.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added : daemonsetName field to the K8sDaemonsetSample.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1131","eolDate":"2023-01-23"},{"agent":"kubernetes","date":"2020-01-23","downloadLink":null,"version":"1.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added : samples for Statefulsets, Daemonsets, Endpoints and Services. Added:  API Server metrics can now be queried using the secure port. Configure the port using the API_SERVER_SECURE_PORT environment variable. The ClusterRole has been updated to allow this query to happen. Changed:  The integration now uses the infrastructure agent v1.8.32-bundle. For more information, refer to the Infrastructure agent release notes  between versions v1.8.23 and v1.8.32. The bundle container contains a subset of On-host integrations  that are supported by New Relic. This also includes the ability to \"Auto Discover\" services running on Kubernetes in a similar way to our Container auto-discovery Changed:  The integration has been renamed from nr-kubernetes to nri-kubernetes.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1130","eolDate":"2023-01-23"},{"agent":"kubernetes","date":"2020-01-13","downloadLink":null,"version":"1.12.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added:  Control Plane components can now also be discovered using the tier and component labels, besides k8s-app. You can read more about this in the control plane monitoring section of the docs. Added:  the newrelic-infra-ctl binary is now included as part of the image. Changed:  The integration now uses the infrastructure agent v1.8.23. For more information refer to the infrastructure agent release notes  between versions v1.5.75 and v1.8.23.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1120","eolDate":"2023-01-13"},{"agent":"kubernetes","date":"2019-12-11","downloadLink":null,"version":"1.11.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added:  Control Plane Monitoring: from this release on the Kubernetes integration will automatically monitor your Control Plane, showing each component and their health status in the Kubernetes cluster explorer. Managed Kubernetes Clusters (GKE, EKS, AKS, DO, etc) are not supported, due to technical restrictions. Added : KSM can now be discovered using custom pod labels. By default we look for pods with the labels k8s-app, app or app.kubernetes.io/name with the value kube-state-metrics.If you want to use a custom label for the discovery, you should put the label name in the environment variable named KUBE_STATE_METRICS_POD_LABEL. If more than 1 pod is found with the label, it will always choose the first one based on a sorted list of IP addresses.Example: Update the newrelic-infrastructure-k8s manifest to use this labeled KSM pod:","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1110","eolDate":"2022-12-11"},{"agent":"kubernetes","date":"2019-11-05","downloadLink":null,"version":"1.10.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed:  The integration now uses the Infrastructure agent v1.5.75. For more information, please refer to the Infrastructure agent release notes  between versions v1.5.31 and v1.5.75.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1102","eolDate":"2022-11-05"},{"agent":"kubernetes","date":"2019-10-25","downloadLink":null,"version":"1.10.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Changed:  The integration reverts to the Infrastructure agent v1.5.31, because there were some issues, like clusters not showing in the New Relic entity list UI, caused by use of agent version v1.5.51.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1101","eolDate":"2022-10-25"},{"agent":"kubernetes","date":"2019-10-17","downloadLink":null,"version":"1.10.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added:  Node labels are now retrieved from the Kubernetes API and added to the K8sNodeSample. They can now be selected in the Narrow Down Entities  section of the infrastructure alerts page to filter entities when using the K8sNodeSample, and can also be used on any NRQL statement when querying the K8sNodeSample. Ex: By default, Information retrieved from the Kubernetes API is cached for 5 minutes. The cache time can be changed with the API_SERVER_CACHE_TTL environment variable. Changed:  The integration now uses the Infrastructure Agent v1.5.51. For more information, please refer to the infrastructure agent release notes  between versions v1.5.31 and v1.5.51.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-1100","eolDate":"2022-10-17"},{"agent":"kubernetes","date":"2018-08-02","downloadLink":null,"version":"1.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install  or update  the New Relic integration for Kubernetes. Changelog Added : Support for specifying the Kubernetes API Host and Port by setting the 'KUBERNETES_SERVICE_HOST' and 'KUBERNETES_SERVICE_PORT' environment variables. Changed : Improve readability of log messages, when verbose mode is enabled. Fixed : Kubernetes API URL discovery failures should stop happening.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-110","eolDate":"2021-08-02"},{"agent":"kubernetes","date":"2018-07-12","downloadLink":null,"version":"1.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Note Follow standard procedures to install  or update  the New Relic integration for Kubernetes. New General Availability release of New Relic integration for Kubernetes","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-integration-100","eolDate":"2021-07-12"},{"agent":"kubernetes","date":"2020-07-20","downloadLink":null,"version":"1.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install the New Relic integration for Kubernetes events . Changelog Updated the version of the k8s-events-forwarder sidecar container to 1.12.0 of the infrastructure agent. You can read the release notes for the infrastructure agent  for more information.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-events-integration-130","eolDate":"2023-07-20"},{"agent":"kubernetes","date":"2020-06-05","downloadLink":null,"version":"1.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install the New Relic integration for Kubernetes events . Changelog Updated the version of the k8s-events-forwarder sidecar container from 1.11.24 to 1.11.45 of the infrastructure agent.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-events-integration-120","eolDate":"2023-06-05"},{"agent":"kubernetes","date":"2020-04-29","downloadLink":null,"version":"1.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install the New Relic integration for Kubernetes events . Changelog Updated base image for the nri-kube-events container to alpine 3.11. Updated the version of the k8s-events-forwarder sidecar container from 1.5.31 to 1.11.24 of the Infrastructure agent. Updated the Deployment apiVersion from apps/v1beta2 to apps/v1. Updated the ClusterRoleBinding apiVersion from rbac.authorization.k8s.io/v1beta1 to rbac.authorization.k8s.io/v1 . Updated the ClusterRole apiVersion from rbac.authorization.k8s.io/v1beta1 to rbac.authorization.k8s.io/v1.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-events-integration-110","eolDate":"2023-04-29"},{"agent":"kubernetes","date":"2020-01-13","downloadLink":null,"version":"1.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Follow standard procedures to install the New Relic integration for Kubernetes events . Changelog Add custom attributes support. Custom attributes are added via environment variables of the form NRI_KUBE_EVENTS_<key>=<val>. Example: To add an attribute called environment with a value of staging to all the events, you need to add the following environment variable to the spec of the kube-events container: More detailed information can be found in the integration's documentation . Add retry with exponential back-off when sending events to the forwarder agent.","slug":"docs/release-notes/infrastructure-release-notes/kubernetes-integration-release-notes/kubernetes-events-integration-100","eolDate":"2023-01-13"},{"agent":"ruby","date":"2023-02-21","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.0.0.gem","version":"9.0.0","features":["Drop support for Ruby 2.2 and 2.3","Remove 37 previously deprecated configuration options","Enable Thread instrumentation by default","Add Fiber instrumentation","Remove instrumentation for Acts As Solr, Authlogic, DataMapper, Rainbows, and Sunspot","Remove support for Passenger 2.2.x-4.0.x, Puma 2.0.x, Grape 0.2.0, Padrino: 0.14.x, Rails 3.2.x, Sinatra 1.4.x and 1.5.x, Mongo 1.8.x-2.3.x, Sequel 3.37.x and 4.0.x, Delayed_Job 2.0.x-4.0.x, Sidekiq 4.2.x, Excon below 0.55.0, HttpClient 2.2.0-2.8.0, HttpRb 0.9.9-2.2.1, Typhoeus 0.5.3-1.2.x, Bunny 2.0.x-2.6.x, and ActiveMerchant 1.25.0-1.64.x","Update API method set_transaction_name","Remove API method NewRelic::Agent.disable_transaction_tracing","Improve ActiveJob metric naming"],"bugs":["Allow rails initialization to be deferred by environment variable"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version at most 90 days old. Read more about keeping agent up to date . As of this release, the oldest supported version is 6.10.0 v9.0.0 Version 9.0.0 of the agent removes several deprecated configuration options and API methods, enables Thread tracing by default, adds Fiber instrumentation, removes support for Ruby versions 2.2 and 2.3, removes instrumentation for several deprecated gems, changes how the API method set_transaction_name works, and updates rails_defer_initialization to be an environment variable only configuration option. Remove deprecated configuration options The following configuration options have been removed and will no longer work. Please update all configs to use the replacements listed below. PR#1782 Removed Replacement newrelic.yml example analytics_events.capture_attributes transaction_events.attributes.enabled transaction_events.attributes.enabled: false browser_monitoring.capture_attributes browser_monitoring.attributes.enabled browser_monitoring.attributes.enabled: false error_collector.capture_attributes error_collector.attributes.enabled error_collector.attributes.enabled: false resque.capture_params attributes.include attributes.include: [&#39;job.resque.args.*&#39;] sidekiq.capture_params attributes.include attributes.include: [&#39;job.sidekiq.args.*&#39;] transaction_tracer.capture_attributes transaction_tracer.attributes.enabled transaction_tracer.attributes.enabled: false error_collector.ignore_errors error_collector.ignore_classes error_collector.ignore_classes: [&#39;ActionController::RoutingError&#39;, &#39;CustomError&#39;] analytics_events.enabled transaction_events.enabled transaction_events.enabled: false analytics_events.max_samples_stored transaction_events.max_samples_stored transaction_events.max_samples_stored: 1200 disable_database_instrumentation disable_sequel_instrumentation disable_sequel_instrumentation: true disable_bunny instrumentation.bunny instrumentation.bunny: disabled disable_curb instrumentation.curb instrumentation.curb: disabled disable_dj instrumentation.delayed_job instrumentation.delayed_job: disabled disable_excon instrumentation.excon instrumentation.excon: disabled disable_grape instrumentation.grape instrumentation.grape: disabled disable_grape_instrumentation instrumentation.grape instrumentation.grape: disabled disable_httpclient instrumentation.httpclient instrumentation.httpcient: disabled disable_httprb instrumentation.httprb instrumentation.httprb: disabled disable_dalli instrumentation.memcache instrumentation.memcache: disabled disable_dalli_cas_client instrumentation.memcache instrumentation.memcache: disabled disable_memcache_client instrumentation.memcache-client instrumentation.memcache-client: disabled disable_memcache_instrumentation instrumentation.memcache instrumentation.memcache: disabled disable_memcached instrumentation.memcached instrumentation.memcached: disabled disable_mongo instrumentation.mongo instrumentation.mongo: disabled disable_net_http instrumentation.net_http instrumentation.net_http: disabled prepend_net_instrumentation instrumentation.net_http instrumentation.net_http: prepend disable_puma_rack instrumentation.puma_rack instrumentation.puma_rack: disabled disable_puma_rack_urlmap instrumentation.puma_rack_urlmap instrumentation.puma_rack_urlmap: disabled disable_rack instrumentation.rack instrumentation.rack: disabled disable_rack_urlmap instrumentation.rack_urlmap instrumentation.rack_urlmap: disabled disable_redis instrumentation.redis instrumentation.redis: disabled disable_redis_instrumentation instrumentation.redis instrumentation.redis: disabled disable_resque instrumentation.resque instrumentation.resque: disabled disable_sinatra instrumentation.sinatra instrumentation.sinatra: disabled disable_rake instrumentation.rake instrumentation.rake: disabled disable_rake_instrumentation instrumentation.rake instrumentation.rake: disabled disable_typhoeus instrumentation.typhoeus instrumentation.typhoeus: disabled Enable Thread instrumentation by default The configuration option instrumentation.thread.tracing is now enabled by default. This configuration allows the agent to properly monitor code occurring inside threads. In Ruby agent 9.0, instrumented code within threads will be recorded and associated with the current transaction when the thread was created. This may be a breaking change if you are currently using custom thread instrumentation. New transactions inside of threads will no longer be started if one already exists. PR#1767 Add Fiber instrumentation Fiber instances are now automatically instrumented similarly to Thread instances. This can be configured  using instrumentation.fiber. PR#1802 Removed support for Ruby 2.2 and 2.3 Ruby 2.2 and 2.3 are no longer supported by the Ruby agent. To continue using the latest Ruby Agent version, please updat…","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-900","eolDate":"2024-02-21"},{"agent":"ruby","date":"2024-04-17","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.9.0.gem","version":"9.9.0","features":["Serverless Mode for AWS Lambda","Add support for Elasticsearch 8.13.0"],"bugs":["Add 'request.temperature' to ruby-openai chat completion summaries"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.9.0 Version 9.9.0 introduces support for AWS Lambda serverless function observability, adds support for Elasticsearch 8.13.0, and adds the 'request.temperature' attribute to chat completion summaries in ruby-openai instrumentation. Feature: Serverless Mode for AWS Lambda The Ruby agent is now capable of operating in a quick and light serverless mode suitable for observing AWS Lambda function invocations. For serverless use, the agent is delivered by a New Relic Lambda layer  that can be associated with a Lambda function. All reported data will appear in New Relic's dedicated serverless UI views. Only AWS based Lambda functions are supported for now, though support for other cloud hosted serverless offerings may be added in future depending on Ruby customer demand. The serverless functionality is only intended for use with the official New Relic Ruby layers for Lambda. Any existing workflows that involve the manual use of the Ruby agent in an AWS Lambda context without a New Relic layer should not be impacted. Feature: Add support for Elasticsearch 8.13.0 Elasticsearch 8.13.0 increased the number of arguments used in the method the agent instruments, Elastic::Transport::Client#perform_request. Now, the agent supports a variable number of arguments for the instrumented method to prevent future ArgumentErrors. Bugfix: Add 'request.temperature' to ruby-openai chat completion summaries Previously, the agent was not reporting the request.temperature attribute on LlmChatCompletionSummary events through ruby-openai instrumentation. We are now reporting this attribute.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-9-0","eolDate":"2025-04-17"},{"agent":"ruby","date":"2024-03-26","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.8.0.gem","version":"9.8.0","features":["Add instrumentation for ruby-openai","Add AI monitoring APIs","Store tracer state on thread-level"],"bugs":["Harden the browser agent insertion logic","Prevent Exception in Active Support Broadcast logger instrumentation"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.8.0 Version 9.8.0 introduces instrumentation for ruby-openai, adds the option to store tracer state on the thread-level, hardens the browser agent insertion logic to better proactively anticipate errors, and prevents excpetions from being raised in the Active Support Broadcast logger instrumentation. Feature: Add instrumentation for ruby-openai Instrumentation has been added for the ruby-openai  gem, supporting versions 3.4.0 and higher (PR#2442) . While ruby-openai instrumentation is enabled by default, the configuration option ai_monitoring.enabled is disabled by default and controls all AI monitoring. ai_monitoring.enabled must be set to true in order to receive ruby-openai instrumentation. High-Security Mode must be disabled in order to receive AI monitoring. Calls to embedding and chat completion endpoints are automatically traced. These events can be enhanced with the introduction of two new APIs. Custom attributes can also be added to LLM events using the API NewRelic::Agent.add_custom_attributes, but they must be prefixed with llm.. For example, NewRelic::Agent.add_custom_attributes({'llm.user_id': user_id}). Feature: Add AI monitoring APIs This version introduces two new APIs that allow users to record additional information on LLM events: NewRelic::Agent.record_llm_feedback_event - Records user feedback events. NewRelic::Agent.set_llm_token_count_callback - Sets a callback proc for calculating token_count attributes for embedding and chat completion message events. Visit RubyDoc  for more information on each of these APIs. Feature: Store tracer state on thread-level A new configuration option, thread_local_tracer_state, stores New Relic's tracer state on the thread-level, as opposed to the default fiber-level storage. This configuration is turned off by default. Our thanks go to community member @markiz  who contributed the idea, code, configuration option, and tests for this new feature! PR#2475 . Bugfix: Harden the browser agent insertion logic With Issue#2462 , community member @miry  explained that it was possible for an HTTP response headers hash to have symbols for values. Not only would these symbols prevent the inclusion of the New Relic browser agent tag in the response body, but more importantly they would cause an exception that would bubble up to the monitored web application itself. With PR#2465  symbol based values are now supported and all other potential future exceptions are now handled. Additionally, the refactor to support symbols has been shown through benchmarking to give the processing of string and mixed type hashes a slight speed boost too. Bugfix: Prevent Exception in Active Support Broadcast logger instrumentation Previously, in certain situations the agent could cause an exception to be raised when attempting to interact with a broadcast log event. This has been fixed. Thanks to @nathan-appere  for reporting this issue and providing a fix! PR#2510","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-8-0","eolDate":"2025-03-26"},{"agent":"ruby","date":"2024-01-25","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.7.1.gem","version":"9.7.1","features":[],"bugs":["Stop suppressing ViewComponent errors","Enforce maximum size limits for custom event attributes"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.7.1 Version 9.7.1 fixes a ViewComponent instrumentation bug and enforces maximum size limits for custom event attributes. Bugfix: Stop suppressing ViewComponent errors Previously, the agent suppressed ViewComponent render errors. The agent now reports these errors and allows them to raise. Thank you @mjacobus  for reporting this bug and providing a fix! PR#2410 Bugfix: Enforce maximum size limits for custom event attributes Previously, the agent would allow custom event attributes to be any size. This would lead to the New Relic backend dropping attributes larger than the maximum size. Now, the agent will truncate custom event attribute values to 4095 characters, attribute names to 255 characters, and the total count of attributes to 64. PR#2401","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-7-1","eolDate":"2025-01-25"},{"agent":"ruby","date":"2024-01-10","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.7.0.gem","version":"9.7.0","features":["ViewComponent instrumentation","Use root path to access Elasticsearch cluster name","Remove base64 dependency, use direct calls to String methods","Add Falcon support","Remove spans with name Ruby/Thread and Ruby/Fiber"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.7.0 Version 9.7.0 introduces ViewComponent instrumentation, changes the endpoint used to access the cluster name for Elasticsearch instrumentation, removes the creation of the Ruby/Thread and Ruby/Fiber spans, and adds support for Falcon. Feature: ViewComponent instrumentation ViewComponent  is a now an instrumented library. PR#2367 Feature: Use root path to access Elasticsearch cluster name Previously, the agent used the cluster health endpoint (/_cluster/health) to access the cluster name. However, this has been found to make startup unstable for large clusters. Now, the agent uses the more performant root endpoint (/). Our thanks go to @erikkessler1 , @gremerritt , and @joshbranham  for reporting the issue, suggesting solutions, and testing them. Issue#2360  PR#2377 Feature: Remove base64 dependency, use direct calls to String methods In version 9.6.0, the agent required the Ruby base64 gem as a depdendency to prepare for deprecation warnings in Ruby 3.3 and the gem's removal from the Ruby standard libraries in 3.4. Including base64 as a dependency has caused problems with version resolution in some environments. To resolve this, the agent now directly calls the String methods used in the base64 library in the new NewRelic::Base64 module. Thank you, @Earlopain , for submitting this change. PR#2378 Feature: Add Falcon support The agent now supports the web server Falcon . PR#2383 Feature: Remove spans with name Ruby/Thread and Ruby/Fiber Due to the lack of helpful information and the confusion commonly caused by the spans named Ruby/Thread and Ruby/Fiber, these spans have been removed. However, the agents ability to monitor instrumented code running in a thread or fiber will remain unchanged. PR#2389","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-7-0","eolDate":"2025-01-10"},{"agent":"ruby","date":"2023-10-30","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.6.0.gem","version":"9.6.0","features":["Add instrumentation for Async::HTTP","Add instrumentation for Ethon","Add instrumentation for HTTPX","Prevent the agent from starting in \"rails\" commands in Rails 7","Glean Docker container ID for cgroups v2-based containers","Update events with additional synthetics attributes when available","Declare a gem dependency on the Ruby Base 64 gem 'base64'","Add Roda support for the newrelic_ignore\\* family of methods","Add additional span attributes for OpenTelemetry compatibility"],"bugs":["Stop sending duplicate log events for Rails 7.1 users","Resolve Sidekiq 8.0 error handler deprecation warning"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.6.0 Version 9.6.0 adds instrumentation for Async::HTTP, Ethon, and HTTPX, adds the ability to ignore specific routes with Roda, gleans Docker container IDs from cgroups v2-based containers, records additional synthetics attributes, fixes an issue with Rails 7.1 that could cause duplicate log records to be sent to New Relic, fixes a deprecation warning for the Sidekiq error handler, adds additional attributes for OpenTelemetry compatibility, and resolves some technical debt, thanks to the community. Feature: Add instrumentation for Async::HTTP The agent will now record spans for Async::HTTP requests. Versions 0.59.0 and above of the async-http gem are supported. PR#2272 Feature: Add instrumentation for Ethon Instrumentation has been added for the Ethon  HTTP client gem. Versions 0.12.0 and above are supported. The agent will now record external request segments for invocations of Ethon::Easy#perform and Ethon::Multi#perform. NOTE: The Typhoeus  gem is maintained by the same team that maintains Ethon and depends on Ethon for its functionality. To prevent duplicate reporting for each HTTP request, the Ethon instrumentation will be disabled when Typhoeus is detected. PR#2260 Feature: Add instrumentation for HTTPX The agent now offers instrumentation for the HTTP client HTTPX , provided the gem is at version 1.0.0 or above. PR#2278 Feature: Prevent the agent from starting in \"rails\" commands in Rails 7 Previously, the agent ignored many Rails commands by default, such as rails routes, using Rake-specific logic. This was accomplished by setting these commands as default values for the config option autostart.denylisted_rake_tasks. However, Rails 7 no longer uses Rake for these commands, causing the agent to start running and attempting to record data when running these commands. The commands have now been added to the default value for the config option autostart.denylisted_constants, which will allow the agent to recognize these commands correctly in Rails 7 and prevent the agent from starting during ignored tasks. Note that the agent will continue to start-up when the rails server and rails runner commands are invoked. PR#2239 Feature: Glean Docker container ID for cgroups v2-based containers Previously, the agent was only capable of determining a host Docker container's ID if the container was based on cgroups v1. Now, containers based on cgroups v2 will also have their container IDs reported to New Relic. PR#2229 . Feature: Update events with additional synthetics attributes when available The agent will now record additional synthetics attributes on synthetics events if these attributes are available.  PR#2203 Feature: Declare a gem dependency on the Ruby Base 64 gem 'base64' For compatibility with Ruby 3.4 and to silence compatibility warnings present in Ruby 3.3, declare a dependency on the base64 gem. The New Relic Ruby agent uses the native Ruby base64 gem for Base 64 encoding/decoding. The agent is joined by Ruby on Rails (rails/rails@3e52adf ) and others in making this change in preparation for Ruby 3.3/3.4. PR#2238 Feature: Add Roda support for the newrelic_ignore* family of methods The agent can now selectively disable instrumentation for particular requests within Roda applications. Supported methods include: newrelic_ignore: ignore a given route. newrelic_ignore_apdex: exclude a given route from consideration in overall Apdex calculations. newrelic_ignore_enduser: prevent automatic injection of the page load timing JavaScript when a route is rendered. For more information, see Roda Instrumentation . PR#2267 Feature: Add additional span attributes for OpenTelemetry compatibility For improved compatibility with OpenTelemetry's semantic conventions, the agent's datastore (for databases) and external request (for HTTP clients) segments have been updated with additional attributes. Datastore segments now offer 3 additional attributes: db.system: The database system. For Ruby we use the database adapter name here. server.address: The database host. server.port: The database port. External request segments now offer 3 additional attributes: http.request.method: The HTTP method (ex: 'GET') server.address: The target host. server.port: The target port. For maximum backwards compatibility, no existing attributes have been renamed or removed. PR#2283 Bugfix: Stop sending duplicate log events for Rails 7.1 users Rails 7.1 introduced the public API ActiveSupport::BroadcastLogger . This logger replaces a private API, ActiveSupport::Logger.broadcast. In Rails versions below 7.1, the agent uses the broadcast method to stop duplicate logs from being recoded by broadcasted loggers. Now, we've update…","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-6-0","eolDate":"2024-10-30"},{"agent":"ruby","date":"2023-09-12","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.5.0.gem","version":"9.5.0","features":["Add Stripe instrumentation","Report transaction HTTP status codes when middleware instrumentation is disabled","Permit capturing only certain Sidekiq job arguments"],"bugs":["Update Elasticsearch datastore instance metric to use port instead of path","Resolve inverted logic of NewRelic::Rack::AgentHooks.needed?"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.5.0 Version 9.5.0 introduces Stripe instrumentation, allows the agent to record additional response information on a transaction when middleware instrumentation is disabled, introduces new :'sidekiq.args.include' and :'sidekiq.args.exclude: configuration options to permit capturing only certain Sidekiq job arguments, updates Elasticsearch datastore instance metrics, and fixes a bug in NewRelic::Rack::AgentHooks.needed?. Feature: Add Stripe instrumentation Stripe  calls are now automatically instrumented. Additionally, new :'stripe.user_data.include' and :'stripe.user_data.exclude' configuration options permit capturing custom user_data key-value pairs that can be stored in Stripe events . No user_data key-value pairs are captured by default. The agent currently supports Stripe versions 5.38.0+. PR#2180 Feature: Report transaction HTTP status codes when middleware instrumentation is disabled Previously, when disable_middleware_instrumentation was set to true, the agent would not record the value of the response code or content type on the transaction. This was due to the possibility that a middleware could alter the response, which would not be captured by the agent when the middleware instrumentation was disabled. However, based on customer feedback, the agent will now report the HTTP status code and content type on a transaction when middleware instrumentation is disabled. PR#2175 Feature: Permit capturing only certain Sidekiq job arguments New :'sidekiq.args.include' and :'sidekiq.args.exclude' configuration options have been introduced to permit fine grained control over which Sidekiq job arguments (args) are reported to New Relic. By default, no Sidekiq args are reported. To report any Sidekiq options, the :'attributes.include' array must include the string 'jobs.sidekiq.args.*'. With that string in place, all arguments will be reported unless one or more of the new include/exclude options are used. The :'sidekiq.args.include' option can be set to an array of strings. Each of those strings will be passed to Regexp.new and collectively serve as an allowlist for desired args. For job arguments that are hashes, if a hash's key matches one of the include patterns, then both the key and its corresponding value will be included. For scalar arguments, the string representation of the scalar will need to match one of the include patterns to be captured. The :'sidekiq.args.exclude' option works similarly. It can be set to an array of strings that will each be passed to Regexp.new to create patterns. These patterns will collectively serve as a denylist for unwanted job args. Any hash key, hash value, or scalar that matches an exclude pattern will be excluded (not sent to New Relic). PR#2177 newrelic.yml examples: Any string in the :'sidekiq.args.include' or :'sidekiq.args.exclude' arrays will be turned into a regular expression. Knowledge of Ruby regular expression support  can be leveraged but is not required. If regular expression syntax is not used, inexact matches will be performed and the string \"Fortune\" will match both \"Fortune 500\" and \"Fortune and Glory\". For exact matches, use regular expression anchors . Bugfix: Update Elasticsearch datastore instance metric to use port instead of path Previously, the Elasticsearch datastore instance metric (Datastore/instance/Elasticsearch/<host>/*) used the path as the final value. This caused a metrics grouping issue  for some users, as every document ID created a unique metric. Now, the datastore instance metric has been updated to use the port as the final value. This also has the benefit of being more accurate for datastore instance metrics, as this port is directly associated with the already listed host. Bugfix: Resolve inverted logic of NewRelic::Rack::AgentHooks.needed? Previously, NewRelic::Rack::AgentHooks.needed? incorrectly used inverted logic. This has now been resolved, allowing AgentHooks to be installed when disable_middleware_instrumentation is set to true. PR#2175","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-5-0","eolDate":"2024-09-12"},{"agent":"ruby","date":"2023-08-18","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.4.2.gem","version":"9.4.2","features":[],"bugs":["Resolve NoMethodError"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.4.2 Version 9.4.2 of the agent re-addresses the 9.4.0 issue of NoMethodError seen when using the uppy-s3_multipart gem. Bugfix: Resolve NoMethodError Ruby agent 9.4.1 attempted to fix a NoMethodError introduced in 9.4.0. A missing require prevented a method from scoping appropriately and has now been added. Thanks to @spickermann  and @ColinOrr  for working with us to get this resolved. PR#2167","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-4-2","eolDate":"2024-08-18"},{"agent":"ruby","date":"2023-08-16","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.4.1.gem","version":"9.4.1","features":[],"bugs":["Resolve NoMethodError"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.4.1 Version 9.4.1 of the agent resolves a NoMethodError introduced in 9.4.0. Bugfix: Resolve NoMethodError Ruby agent 9.4.0 introduced Roda instrumentation , which caused a NoMethodError to be raised when attempting to name a Roda transaction. This has been fixed. Thanks to @spickermann  for reporting this issue. PR#2167","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-4-1","eolDate":"2024-08-16"},{"agent":"ruby","date":"2023-08-15","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.4.0.gem","version":"9.4.0","features":["Add Roda instrumentation","New allow_all_headers configuration option","Improved error tracking transaction linking","Use Net::HTTP native timeout logic"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.4.0 Version 9.4.0 of the agent adds Roda  instrumentation, adds a new allow_all_headers configuration option to permit capturing all HTTP headers, introduces improved error tracking functionality by associating a transaction id with each error, and uses more reliable network timeout logic. Feature: Add Roda instrumentation Roda  is a now an instrumented framework. The agent currently supports Roda versions 3.19.0+. PR#2144 Feature: New allow_all_headers configuration option A new allow_all_headers configuration option brings parity with the Node.js agent  to capture all HTTP request headers. This configuration option: Defaults to false Is not compatible with high-security mode Requires Rack version 2 or higher (as does Ruby on Rails version 5 and above) Respects all existing behavior for the attributes.include and attributes.exclude configuration options Captures the additional headers as attributes prefixed with request.headers. This work was done in response to a feature request submitted by community member @jamesarosen . Thank you very much, @jamesarosen! Issue#1029 Feature: Improved error tracking transaction linking Errors tracked and sent to the New Relic errors inbox will now be associated with a transaction id to enable improved UI/UX associations between transactions and errors. PR#2035 Feature: Use Net::HTTP native timeout logic In line with current Ruby best practices, make use of Net::HTTP's own timeout logic and avoid the use of Timeout.timeout() when possible. The agent's data transmissions and cloud provider detection routines have been updated accordingly. PR#2147","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-4-0","eolDate":"2024-08-15"},{"agent":"ruby","date":"2023-07-11","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.3.1.gem","version":"9.3.1","features":[],"bugs":["Fix NewRelic::Agent.require_test_helper"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.3.1 Version 9.3.1 of the agent fixes NewRelic::Agent.require_test_helper. Bugfix: Fix NewRelic::Agent.require_test_helper Version 9.3.0 of the agent made a change to the files distributed with the gem. This change unintentionally broke the NewRelic::Agent.require_test_helper API by removing the test/agent_helper.rb file. The file has been added back to the gem. This change also removes the lib/new_relic/build.rb file from the list because it is no longer created with our current release process. Our thanks go to @ajesler  for reporting this issue and writing a test for the bug. Issue#2113 , PR#2115 , Issue#2117 , PR#2118 Source Documentation: update the Rack spec URL Community member @olleolleolle  noticed that our source code was referencing a now defunct URL for the Rack specification and submitted PR#2121  to update it. He also provided a terrific recommendation that we automate the checking of links to proactively catch defunct ones in future. Thanks, @olleolleolle!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-3-1","eolDate":"2024-07-11"},{"agent":"ruby","date":"2023-06-26","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.3.0.gem","version":"9.3.0","features":["Filter forwarded logs based on level","Custom attributes for logs","Instrument transmit_subscription-related Action Cable actions"],"bugs":["Removed unwanted files from being included in file_list in gemspec","Report Code-Level Metrics for Rails controller methods","Code-Level Metrics for ActiveRecord models","Private method `clear_tags!` for NewRelic::Agent::Logging::DecoratingFormatter","Fix the way args are handled for Fibers"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.3.0 Version 9.3.0 of the agent adds log-level filtering, adds custom attributes for log events, and updates instrumentation for Action Cable. It also provides fixes for how Fiber args are treated, Code-Level Metrics, unnecessary files being included in the gem, and NewRelic::Agent::Logging::DecoratingFormatter#clear_tags! being incorrectly private. Feature: Filter forwarded logs based on level Previously, all log events, regardless of their level, were forwarded to New Relic when log forwarding was enabled. Now, you may specify the lowest log level you'd like forwarded to New Relic. | Configuration name                         | Default | Behavior                                                     | Valid values                                         |\n| ------------------------------------------ | ------- | ------------------------------------------------------------ | ---------------------------------------------------- |\n| application_logging.forwarding.log_level | debug | Sets the minimum log level for events forwarded to New Relic | debug, info, warn, error, fatal, unknown | This setting uses Ruby's Logger::Severity constants integer values  to determine precedence. Feature: Custom attributes for logs You can now add custom attributes to log events forwarded to New Relic! You can pass these attributes using an API and/or a configuration option. | Configuration name                                 | Default | Behavior                                                                                                                                                                                                |\n| -------------------------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| application_logging.forwarding.custom_attributes | {}    | A hash with key/value pairs to add as custom attributes to all log events forwarded to New Relic. If sending using an environment variable, the value must be formatted like: \"key1=value1,key2=value2\" | Call the API using NewRelic::Agent.add_custom_log_attributes and passing your attributes as a hash. For example, you could call: NewRelic::Agent.add_custom_log_attributes(dyno: ENV['DYNO'], pod_name: ENV['POD_NAME']), to add the attributes dyno and pod_name to your log events. Attributes passed to the API or the configuration will be added to all log events. Thanks to @rajpawar02  for raising this issue and @askreet  for helping us with the solution. Issue#1141 , PR#2084 , PR#2087 Feature: Instrument transmit_subscription-related Action Cable actions This change subscribes the agent to the Active Support notifications for: transmit_subscription_confirmation.action_cable transmit_subscription_rejection.action_cable Bugfix: Removed unwanted files from being included in file_list in gemspec Previously, the agent was including some files in the gem that were not needed but added to the size of the gem. These files will no longer be included. Thanks to @manuraj17  for the contribution! PR#2089 Bugfix: Report Code-Level Metrics for Rails controller methods Controllers in Rails automatically render views with names that correspond to valid routes. This means that a controller method may not have a corresponding method in the controller class. Code-Level Metrics now report on these methods and don't log false warnings. Thanks to @jcrisp  for reporting this issue. PR#2061 Bugfix: Code-Level Metrics for ActiveRecord models Classes that inherit from ActiveRecord were not reporting Code-Level Metrics due to an error in the agent when identifying the class name. This has been fixed and Code-Level Metrics will now report for ActiveRecord models. Thanks to @abigail-rolling  for reporting this issue. PR#2092 . Bugfix: Private method clear_tags! for NewRelic::Agent::Logging::DecoratingFormatter As part of a refactor included in a previous release of the agent, the method NewRelic::Agent::Logging::DecoratingFormatter#clear_tags! was incorrectly made private. This method is now public again. Thanks to @dark-panda  for reporting this issue. PR# Bugfix: Fix the way args are handled for Fibers Previously, the agent treated Fiber args the same as it was treating Thread args, which is not correct. Args are passed to Fiber#resume, and not Fiber.new. This has been fixed, and the agent will properly preserve args for both Fiber and Thread classes. This also caused an error to occur when using Async 2.6.2, due to mismatching initalize definitions for Fiber prepended modules. This has been …","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-3-0","eolDate":"2024-06-26"},{"agent":"ruby","date":"2025-12-02","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.24.0.gem","version":"9.24.0","features":["Deprecation reminder for SqlSampler#notice_sql API","Deprecation notice for second and third arguments in Datastores.notice_sql API","Deprecation notice for second argument in Datastores.notice_statement API","Deprecation notice for proc's second and third arguments in Datastores.wrap API"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.24.0 Feature: Deprecation reminder for SqlSampler#notice_sql API The NewRelic::Agent::SqlSampler#notice_sql method is deprecated and will be removed in a future major version. Instead, users should call NewRelic::Agent::Datastores.notice_sql. PR#3345 Feature: Deprecation notice for second and third arguments in Datastores.notice_sql API The second (scoped_metric) and third (elapsed) arguments in the NewRelic::Agent::Datastores.notice_sql method are deprecated. They have not been used by the method for some time. Instead, these values will be set based on the current segment when the API is called. PR#3345 Feature: Deprecation notice for second argument in Datastores.notice_statement API The second (elapsed) argument in the NewRelic::Agent::Datastores.notice_statement method is deprecated. It has not been used by the method for some time. Instead, this value will be set based on the current segment when the API is called. PR#3346 Feature: Deprecation notice for proc's second and third arguments in Datastores.wrap API The NewRelic::Agent::Datastores.wrap method is changing. In a future major version, proc will only accept a single argument, the result of the yield. The scoped metric name and elapsed arguments will be removed, as they are being removed from the Datastores.notice_sql method. The scoped metric name and elapsed values are derived from the current segment when the wrap yields. PR#3346","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-24-0","eolDate":"2026-12-02"},{"agent":"ruby","date":"2025-11-12","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.23.0.gem","version":"9.23.0","features":["Add sidekiq.ignore_retry_errors configuration option","Deprecation notice for recording deployments using Capistrano","Use remote parent sampling configurations for decisions in more scenarios"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.23.0 Feature: Add sidekiq.ignore_retry_errors configuration option A new configuration option, sidekiq.ignore_retry_errors, has been added to control if Sidekiq job retries are captured. Retry errors are captured by default, but now if sidekiq.ignore_retry_errors is set to true, the agent will ignore exceptions raised during Sidekiq's retry attempts and will only report the error if the job permanently fails. Thank you DonGiulio  for recognizing this improvement and contributing a solution. PR#3317 Feature: Deprecation notice for recording deployments using Capistrano Sending application deployment information using a Capistrano recipe is deprecated and will be removed in agent version 10.0.0. For recording deployments, please see our guide to Change Tracking  for a list of available options. Feature: Use remote parent sampling configurations for decisions in more scenarios Previously, the distributed_tracing.sampler.remote_parent_sampled and distributed_tracing.sampler.remote_parent_not_sampled configuration options were used for the sampling decision only when the traceparent and tracestate headers were present. Now, these configuration options are applied in cases when the tracestate header is missing and when only the newrelic header is available. This change makes distributed trace sampling more consistent and predictable. PR#3306","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-23-0","eolDate":"2026-11-12"},{"agent":"ruby","date":"2025-10-07","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.22.0.gem","version":"9.22.0","features":["One-step instrumentation for Kubernetes","Deprecation notice for Ruby 2.4 and Ruby 2.5","Deprecation notice for the `newrelic deployments` command","Deprecation reminder for cross application tracing","Ensure compatibility with Ruby 3.5 change to Method#source_location"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.22.0 Feature: One-step instrumentation for Kubernetes The Kubernetes APM auto-attach automatically instruments applications and manages agent upgrades within Kubernetes deployments. This feature has exited preview and is now generally avaliable. Learn more about Kubernetes auto-attach . PR#2635  PR#3287 Feature: Deprecation notice for Ruby 2.4 and Ruby 2.5 Ruby agent support for Ruby versions 2.4 and 2.5 is deprecated and will be removed in agent version 10.0.0. The new miniumum required Ruby version will become Ruby 2.6 and we will stop testing with Ruby 2.4 and 2.5. PR#3288 Feature: Deprecation notice for the newrelic deployments command Support for recording deployments using the newrelic deployments command is now deprecated and will be removed in agent version 10.0.0. Going forward, there are a number of automated and manual ways ways to record changes in New Relic. Please see our guide to Change Tracking  for a list of available options. PR#3262 Feature: Deprecation reminder for cross application tracing Cross application tracing has been deprecated since major version 8.0.0 of the Ruby agent. We will remove support for it entirely in version 10.0.0 of the agent. PR#3288 Feature: Ensure compatibility with Ruby 3.5 change to Method#source_location Updated the agent to correctly parse the return value of Method#source_location, which is changing in Ruby 3.5 from a two-element to a five-element array. This change maintains support for older Ruby versions while adding support for the future release. PR#3257","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-22-0","eolDate":"2026-10-07"},{"agent":"ruby","date":"2025-08-27","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.21.0.gem","version":"9.21.0","features":["In Serverless APM mode, use event source name as transaction name prefix"],"bugs":["Revert changed logic for how we track the thread the span starts in"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.21.0 Feature: In Serverless APM mode, use event source name as transaction name prefix The agent will now use the event source name as a prefix for the transaction name in Serverless APM mode. This will help to better identify the source of the transaction in the New Relic UI. PR#3245 Bugfix: Revert changed logic for how we track the thread the span starts in This change restores the previous behavior of tracking the thread the span starts in, addressing issues that arose from the updated logic. Thank you @david-zw-liu  for bringing this to our attention. PR#3248","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-21-0","eolDate":"2026-08-27"},{"agent":"ruby","date":"2025-07-31","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.20.0.gem","version":"9.20.0","features":["Add ECS Docker ID for Fargate","Add NewRelic::Helper.version_satisfied?","Add code.stacktrace attribute on datastore spans when duration exceeds configured threshold","Consolidate \"Unknown\" constant values"],"bugs":["Fix Brewfile source links","Fix error when using HTTPX 1.5.0","Bugfixes and improvements to debug level agent logs","Fix risk of server-side forgery for Slack workflow script","Replace JSON.load calls with JSON.parse"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.20.0 Feature: Add ECS Docker ID for Fargate Previously, the Ruby agent did not record the Docker ID when running in an AWS ECS Fargate environment. The Docker ID will now be recorded correctly. PR#3172 Feature: Add NewRelic::Helper.version_satisfied? The agent has a new helper method to simplify version comparison. NewRelic::Helper.version_satisfied? accepts three arguments: a left-side version number, the comparison operator as a string, and a right-side version number. Our thanks go to @kekke-n  for this contribution. PR#3182 Feature: Add code.stacktrace attribute on datastore spans when duration exceeds configured threshold The agent will now add the code.stacktrace attribute to datastore spans when the duration exceeds the configured threshold. The threshold is configured using the transaction_tracer.stack_trace_threshold configuration option. PR#3220 Feature: Consolidate \"Unknown\" constant values All references to the various capitalization styles for \"Unknown\" have been consolidated into two constants: NewRelic::UNKNOWN and NewRelic::UNKNOWN_LOWER. Thank you, @tsubasa1122 , for your contribution! PR#3185 Bugfix: Fix Brewfile source links Previously, the multiverse README's links to the Brewfile were broken. Our thanks go to @emmanuel-ferdman  for submitting a PR to fix them! PR#3191 Bugfix: Fix error when using HTTPX 1.5.0 The agent previously encountered an error when using the new HTTPX version 1.5.0. This was due to a change in the way HTTPX stores the response. The agent has been updated to handle this change correctly, and no longer encounters an error when using HTTPX 1.5.0. PR#3203 Bugfix: Bugfixes and improvements to debug level agent logs Improves the information logged at the debug level by the agent when the agent reads in a configuration source. PR#3221 Bugfix: Fix risk of server-side forgery for Slack workflow script Internally, we keep track of gems that are released using a GitHub actions workflow that posts updates on Slack. [@odaysec] identified a way we could reduce the risk of server-side forgery for this workflow. Thank you! PR#3184 Bugfix: Replace JSON.load calls with JSON.parse Generally, JSON.parse is seen as safer than JSON.load. Thank you, @odaysec , for bringing this to our attention! PR#3183  PR#3230","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-20-0","eolDate":"2026-07-31"},{"agent":"ruby","date":"2023-05-01","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.2.2.gem","version":"9.2.2","features":[],"bugs":["Transaction#finished? no longer throws a NoMethodError when initial_segment is nil"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.2.2 Version 9.2.2 of the agent fixes a bug with the Transaction#finished? method. Bugfix: Transaction#finished? no longer throws a NoMethodError when initial_segment is nil This change adds a safe navigation operator to Transaction#finished? to prevent NoMethodErrors when a transaction does not have any segments. Our thanks goes to @JulienDefrance  for reporting this issue. PR#1983","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-2-2","eolDate":"2024-05-01"},{"agent":"ruby","date":"2023-05-01","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.2.1.gem","version":"9.2.1","features":[],"bugs":["Finished transactions continue to store data on different threads","Expected Errors passed to notice_error are expected again"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.2.1 Version 9.2.1 fixes a bug causing the agent to continue storing data on finished transactions, and a bug preventing errors from being expected. Bugfix: Finished transactions continue to store data on different threads Previously, when a new thread was spawned the agent would continue using the current transaction to record data on, even if this transaction had finished already in a different thread. Now the agent will only use the current transaction in the new thread if it is not yet finished. Thank you to @fcheung  for reporting this bug and providing us with an extremely helpful reproduction to debug. PR#1969 Bugfix: Expected Errors passed to notice_error are expected again A bug was introduced in 9.1.0 that caused to agent not to mark errors as expected if the error was passed in to notice_error using the expected: true parameter. This has been fixed and errors will now be marked as expected, as expected. Thank you very much to @eiskrenkov  for finding this bug and contributing a fix for it! PR#1954","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-2-1","eolDate":"2024-05-01"},{"agent":"ruby","date":"2023-04-17","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.2.0.gem","version":"9.2.0","features":["Enhance performance for handling high numbers of nested actions","Deprecate memcached and memcache-client instrumentation"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.2.0 Version 9.2.0 of the agent introduces some performance improvements for working with high numbers of nested actions, and deprecates instrumentation for the memcached and memcache-client gems (with dalli still being supported). Feature: Enhance performance for handling high numbers of nested actions With Issue#1910 , community members @parkerfinch  and @travisbell  informed us of some CPU spikes and process hangs seen only when using the agent's thread instrumentation, which was enabled by default with v9.0. When thread instrumentation is enabled, instrumented actions taking place within threads are seen and reported on by the agent whereas they would have previously gone unnoticed. This is a great improvement to the agent's usefulness in an async context, and also makes it easier for higher numbers of nested actions to be observed.\nFor example, if an instrumented background job framework (Sidekiq, Resque) kicks off a job that the agent notices and then that job in turn performs actions such as database queries that the agent also instruments, nested actions are seen. However, with very high (10,000+) numbers of actions nested within a single instrumented outer action, the agent would struggle to efficiently crunch through all of the collected data at the time when the outer action finished.\nThe agent should now be much more efficient when any observed action with lots of nested actions is finished. Our performance testing was conducted with hundreds of thousands of nested actions taking place, and we hope that the benefits of thread tracing can now be enjoyed without any drawbacks. Thanks very much @parkerfinch  and @travisbell ! PR#1927 Feature: Deprecate memcached and memcache-client instrumentation Instrumentation for the memcached and memcache-client libraries is deprecated and will be removed during the next major release.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-2-0","eolDate":"2024-04-17"},{"agent":"ruby","date":"2025-04-30","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.19.0.gem","version":"9.19.0","features":["Add Thread ID as attribute to all spans","Add support for W3C TraceContext Trace Flag"],"bugs":["Include request.uri in Transaction events by default","Fix error in Active Job instrumentation when using perform_all_later"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.19.0 Feature: Add Thread ID as attribute to all spans The agent will now record the Thread ID as an attribute on each span. PR#3122 Feature: Add support for W3C TraceContext Trace Flag Previously, the agent would not use the trace flag field of the traceparent header for sampling decisions. This could lead to fragmented traces in the UI. While the default behavior remains unchanged, two new configuration options, distributed_tracing.sampler.remote_parent_sampled and distributed_tracing.sampler.remote_parent_not_sampled, have been introduced to allow more control over the way sampling decisions are made. PR#3135 Bugfix: Include request.uri in Transaction events by default The New Relic data dictionary expects Transaction events to have the request.uri attribute.  The Ruby agent now fulfills this expectation. If you would like to exclude request.uri from Transaction events, you can do so by setting transaction_events.attributes.exclude to 'request.uri'. PR#3103 Bugfix: Fix error in Active Job instrumentation when using perform_all_later Previously, when Active Job's perform_all_later method was called and the agent was running, a NoMethodError would be raised with the message undefined method 'queue_name' for nil. The error has been fixed and the name of the segment will reflect the first job in the queue. Our thanks goes to @tan-linx  for bringing this to our attention and providing a fix. PR#3110","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-19-0","eolDate":"2026-04-30"},{"agent":"ruby","date":"2025-04-02","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.18.0.gem","version":"9.18.0","features":["Add elasticsearch.capture_cluster_name configuration option","Add support for sidekiq-delay_extensions","Parallelize calls for vendor metadata"],"bugs":["Prevent a nil segment from causing errors in Net::HTTP instrumentation","JRuby multithreading improvements","Stop reporting rescued Sidekiq::OverLimit exceptions","Protect against nil agents or health checks","Ignore Solid Queue `ThreadError: queue empty` error message by default","Refactor URI host handling to accommodate downcasing frozen strings"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.18.0 Feature: Add elasticsearch.capture_cluster_name configuration option A new configuration option, elasticsearch.capture_cluster_name, has been added to control capturing Elasticsearch cluster names. Cluster names are captured by default, but can now be disabled as needed. PR#3038 Feature: Add support for sidekiq-delay_extensions Sidekiq delay extensions were removed from Sidekiq in 7.x and are now avaliable through the sidekiq-delay_extensions  gem. Thanks to @sobrinho , the agent now has continued support for delay extensions.PR#3056 Feature: Parallelize calls for vendor metadata Previously, the agent would make calls for vendor metadata in a serial fashion. This could lead to a delay in starting the agent. Now, the agent will make these calls in parallel, reducing the time it takes to start the agent. PR#3094 Bugfix: Prevent a nil segment from causing errors in Net::HTTP instrumentation When using JRuby, a race condition can happen that causes the segment creation to fail and return nil. This would cause an error to occur when methods were later called on the nil segment. These methods will no longer be called if the segment is nil, preventing that error from occurring. PR#3046 Bugfix: JRuby multithreading improvements Added some additional nil checks and mutexes to prevent issues when using the agent on JRuby with multiple threads. Thanks to @NC-piercej for bringing this to our attention Issue#3021  PR#3053 Bugfix: Stop reporting rescued Sidekiq::OverLimit exceptions When Sidekiq's concurrent rate limiters encounter an OverLimit exception, Sidekiq typically handles this by re-enqueuing the job. Previously, all occurrences of Sidekiq::OverLimit were logged as errors in New Relic, even when Sidekiq's middleware resolved the exception. New Relic will no longer report errors that are handled by Sidekiq's own middleware. Thanks to @97jaz  for reporting this issue. Issue#3037  PR#3047 Bugfix: Protect against nil agents or health checks In some cases the agent or health checks may be nil when they are called. Safe navigation operators have been added for protection on those occasions. PR#3049 Bugfix: Ignore Solid Queue ThreadError: queue empty error message by default When using the solid_queue gem, the agent previously generated excessive warn-level logs when the queue was empty. The agent now ignores queue empty error messages of the ThreadError class by default. This behavior can be adjusted using the error_collector.ignore_messages configuration option. PR#3060 Bugfix: Refactor URI host handling to accommodate downcasing frozen strings When URI host string was frozen, a FrozenError would be raised when the agent attempted to downcase the host as part of its data normalization process. Now, the update is friendly for frozen strings. Thank you @pedrol3001  for your contribution! PR#3097","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-18-0","eolDate":"2026-04-02"},{"agent":"ruby","date":"2025-01-29","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.17.0.gem","version":"9.17.0","features":["Support Ruby 3.4.0","Add instrumentation for aws-sdk-firehose","Kubernetes APM auto-attach - new agent version precedent","Add health checks when the agent runs within Agent Control","Add Redshift as recognized ActiveRecord adapter","Add instrumentation for aws-sdk-kinesis"],"bugs":["Stop emitting inaccurate debug-level log about deprecated configuration options","Do not attempt to decorate logs with `nil` messages","Stop renaming final Grape segment"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.17.0 Feature: Support Ruby 3.4.0 The agent now supports Ruby 3.4.0. We've made incremental changes throughout the preview stage to reach compatibility. This release includes an update to the Thread Profiler for compatibility with Ruby 3.4.0's new backtrace format. Issue#2992  PR#2997 Feature: Add instrumentation for aws-sdk-firehose The agent now has instrumentation for the aws-sdk-firehose  gem. PR#2973 Feature: Kubernetes APM auto-attach - new agent version precedent Previously, when a customer installed the Ruby agent via Kubernetes APM auto-attach  and also had the Ruby agent listed in their Gemfile, the agent version in Gemfile would take precedence. Now, the agent version installed by auto-attach takes priority. PR#3018 Feature: Add health checks when the agent runs within Agent Control When the agent is started within an Agent Control  environment, a health check file will be created at the configured file location for every agent process. By default, this location is: '/newrelic/apm/health'. The health check files will be updated at the configured frequency, which defaults to every five seconds. PR#2995 Feature: Add Redshift as recognized ActiveRecord adapter When the agent does not recognize an ActiveRecord adapter, the host, port, and database name information is not added to the datastore span. Redshift will now be treated like PostgreSQL, and the agent will save the host, port, and database name on the span. PR#3032 Feature: Add instrumentation for aws-sdk-kinesis The agent now has instrumentation for the aws-sdk-kinesis  gem. It will record message broker segments for get_records, put_record, and put_records operations. All other operations will record standard segments. PR#2974 Bugfix: Stop emitting inaccurate debug-level log about deprecated configuration options In the previous major release, we dropped support for many disable_library_name configuration options in favor of instrumentation.library_name. Previously, a DEBUG level log warning appeared whenever disable_* options were set to true, even for libraries (e.g. Action Dispatch) without equivalent instrumentation.* options: This inaccurate warning has been removed. If you are disabling instrumentation using instrumentation.library_name: disabled or NEW_RELIC_INSTRUMENTATION_LIBRARY_NAME=disabled, please verify the option exists by consulting our configuration documentation . If the option does not exist, check the 'Disabling' section  to see if there is a related option. We apologize for the confusion. PR#3005 Bugfix: Do not attempt to decorate logs with nil messages The agent no longer attempts to add New Relic linking metadata to logs with nil messages. Thank you, @arlando  for bringing this to our attention! Issue#2985  PR#2986 Bugfix: Stop renaming final Grape segment Previously, the agent renamed the final segment in Grape transactions to \"Middleware/Grape/#{class_name}/call\". This was a part of an old instrumentation pattern that is no longer relevant. Many thanks to @seriousdev-gh  for bringing this issue to our attention and along with a great reproduction and suggested fix. PR#2987 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-17-0","eolDate":"2026-01-29"},{"agent":"ruby","date":"2024-12-04","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.16.1.gem","version":"9.16.1","features":[],"bugs":["Add support for Trilogy database adapter"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.16.1 Bugfix: Added the support for the Trilogy database adapter. The agent now fully supports the Trilogy, a client library for MySQL-compatible database servers, and correctly lists MySQL as the corresponding database in the UI. PR#2966 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-16-1","eolDate":"2025-12-04"},{"agent":"ruby","date":"2024-11-19","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.16.0.gem","version":"9.16.0","features":["Instrumentation for aws-sdk-lambda","Add new configuration options to attach custom tags (labels) to logs","Update View Component instrumentation+"],"bugs":["Record explain plan traces on Rails 7.2+"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.16.0 Version 9.16.0 introduces the following features and bug fixes: Feature: Instrumentation for aws-sdk-lambda When the aws-sdk-lambda gem is available and used to invoke remote AWS Lambda functions, the timing and error details of the invocations will be reported to New Relic. PR#2926 . Feature: Add new configuration options to attach custom tags (labels) to logs The Ruby agent now allows you to opt-in to adding your custom tags (labels) to agent-forwarded logs. With custom tags on logs, platform engineers can easily filter, search, and correlate log data for faster and more efficient troubleshooting, improved performance, and optimized resource utilization. PR#2925 Feature: Update View Component instrumentation+ The .identifier method will be formally exposed as part of the View Component public API. The agent will now use this method for building metric names when available, ensuring ongoing compatibility with all View Component versions. PR#2956 Bugfix: Record explain plan traces on Rails 7.2+ Rails 7.2 removed adapter-specific connection methods (ex. ActiveRecord::Base.postgresql_connection) and replaced them with ActiveRecord::Base.with_connection. Our explain plan feature relies on making a connection to the database to create an explain plan trace. Due to a bug in our tests, we missed this regression. Now, the agent uses the new method to fetch explain plans on Rails 7.2+. Thank you, @gsar  and @gstark  for bringing this to our attention! Issue#2922  PR#2940","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-16-0","eolDate":"2025-11-19"},{"agent":"ruby","date":"2024-10-31","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.15.0.gem","version":"9.15.0","features":["New configuration option cloud.aws.account_id","Use default `View/component` metric name for unidentified View Components"],"bugs":["Instrumentation errors when using the karafka-rdkafka gem","Stop calling deprecated all_specs method to check for the presence of newrelic-grape","Instrumentation errors when using the ruby-kafka gem","Restore AWS Lambda layer operational functionality"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.15.0 Version 9.15.0 updates View Component instrumentation to use a default metric name when one is unavailable, adds a configuration option to associate the AWS account ID with the DynamoDB calls from the AWS SDK, resolves a bug in rdkafka instrumentation when using the karafka-rdkafka gem, resolves a bug in the ruby-kafka instrumentation, fixes a bug with Grape instrumentation, and addresses a bug preventing the agent from running in serverless mode in an AWS Lambda layer. Feature: New configuration option cloud.aws.account_id A new configuration option has been added, cloud.aws.account_id, that will allow New Relic to provide more details about certain calls made using the AWS SDK. For example, relationships between AWS services instrumented with New Relic's CloudWatch Metric Streams will have relationships formed in the service map with APM applications. Currently, the DynamoDB instrumentation is the only instrumentation that will make use of this configuration option, but this will be used in future instrumentation as well. PR#2904 Feature: Use default View/component metric name for unidentified View Components Previously, when a View Component metric name could not be identified, the agent would set the name as nil. Now, the agent defaults to using View/component as the metric name when one can not be identified. PR#2907 Bugfix: Instrumentation errors when using the karafka-rdkafka gem Due to version differences between the rdkafka gem and karafka-rdkafka gem, the agent could encounter an error when it tried to install rdkafka instrumentation. This has now been resolved. Thank you to @krisdigital for bringing this issue to our attention. PR#2880 Bugfix: Stop calling deprecated all_specs method to check for the presence of newrelic-grape In 9.14.0, we released a fix for calls to the deprecated Bundler.rubygems.all_specs, but the fix fell short for the agent's Grape instrumentation and deprecation warnings could still be raised. The condition has been simplified and deprecation warnings should no longer be raised. Thank you, @excelsior  for bringing this to our attention. Issue#2885  PR#2906 Bugfix: Instrumentation errors when using the ruby-kafka gem Kafka::Consumer#each_message takes keyword arguments, while the prepended method is defined with a single splat positional argument. In Ruby >= 3.0, this signature mismatch raises an ArgumentError. Thank you @patrickarnett  for providing this bugfix. PR#2915 Bugfix: Restore AWS Lambda layer operational functionality Version 9.14.0 of the agent introduced an optimization related to how the agent handles boolean configuration parameters which inadvertently caused the agent to stop operating properly in an AWS Lambda layer context. Issue#2919 PR#2920","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-15-0","eolDate":"2025-10-31"},{"agent":"ruby","date":"2024-09-30","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.14.0.gem","version":"9.14.0","features":["Add Apache Kafka instrumentation for the rdkafka and ruby-kafka gems","Add a configuration option to permit custom method tracers to be defined automatically","Collect just MIME type for ActionDispatch 7.0+ requests"],"bugs":["Corrected Boolean coercion for `newrelic.yml` configuration","JRuby not saving configuration values correctly in configuration manager","Update condition to verify Bundler.rubygems.installed_specs is available","Support view_component v3.15.0+"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.14.0 Version 9.14.0 adds Apache Kafka instrumentation for the rdkafka and ruby-kafka gems, introduces a configuration-based, automatic way to add custom instrumentation method tracers, correctly captures MIME type for ActionDispatch 7.0+ requests, properly handles Boolean coercion for newrelic.yml configuration, fixes a JRuby bug in the configuration manager, fixes a bug related to Bundler.rubygems.installed_specs, and fixes a bug to make the agent compatible with ViewComponent v3.15.0+. Feature: Add Apache Kafka instrumentation for the rdkafka and ruby-kafka gems The agent now has instrumentation for both the rdkafka and ruby-kafka gems. The agent will record transactions and message broker segments for produce and consume calls made using these gems. PR#2824  PR#2842 Feature: Add a configuration option to permit custom method tracers to be defined automatically A new :automatic_custom_instrumentation_method_list configuration parameter has been added to permit the user to define a list of fully qualified (namespaced) Ruby methods for the agent to automatically add custom instrumentation for without requiring any code modifications to be made to the classes that define the methods. The list should be an array of CLASS#METHOD (for instance methods) and/or CLASS.METHOD (for class methods) strings. Use fully qualified class names (using the :: delimiter) that include any module or class namespacing. Here is some Ruby source code that defines a render_png instance method for an Image class and a notify class method for a User class, both within a MyCompany module namespace: Given that source code, the newrelic.yml config file might request instrumentation for both of these methods like so: That configuration example uses YAML array syntax to specify both methods. Alternatively, a comma-delimited string can be used instead: Whitespace around the comma(s) in the list is optional. When configuring the agent with a list of methods via the NEW_RELIC_AUTOMATIC_CUSTOM_INSTRUMENTATION_METHOD_LIST environment variable, this comma-delimited string format should be used: PR#2851 Feature: Collect just MIME type for ActionDispatch 7.0+ requests Rails 7.0 introduced changes  to the behavior of ActionDispatch::Request#content_type, adding extra request-related details the agent wasn't expecting to collect. Additionally, the agent's use of content_type  was triggering deprecation warnings. The agent now uses ActionDispatch::Request#media_type to capture the MIME type. Thanks to @internethostage  for letting us know about this change. Issue#2500  PR#2855 Bugfix: Corrected Boolean coercion for newrelic.yml configuration Previously, any String assigned to New Relic configurations expecting a Boolean value were evaluated as true. This could lead to unexpected behavior. For example, setting application_logging.enabled: 'false' in newrelic.yml would incorrectly evaluate to application_logging.enabled: true due to the truthy nature of Strings. Now, the agent strictly interprets Boolean configuration values. It recognizes both actual Boolean values and certain Strings/Symbols: 'true', 'yes', or 'on' (evaluates to true) 'false', 'no', or 'off' (evaluates to false) Any other inputs will revert to the setting's default configuration value. PR#2847 Bugfix: JRuby not saving configuration values correctly in configuration manager Previously, a change made to fix a different JRuby bug caused the agent to not save configuration values correctly in the configuration manager when running on JRuby. This has been fixed. PR#2848 Bugfix: Update condition to verify Bundler.rubygems.installed_specs is available To address a recent Bundler deprecation warning, we started using Bundler.rubygems.installed_specs instead of Bundler.rubygems.all_specs in environments that seemed appropriate. We discovered the version constraint we used was too low. Now, rather than check the version, we check for the method using respond_to?. PR#2853 Bugfix: Support view_component v3.15.0+ Previously the agent had been making use of a private API to obtain a component identifier value. This private API was dropped in v3.15.0 of view_component, resulting in errors from the New Relic Ruby agent's continued attempts to use it. Many thanks to community member @navidemad  for bringing this issue to our attention and supplying a bugfix with PR#2870 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-14-0","eolDate":"2025-09-30"},{"agent":"ruby","date":"2024-08-22","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.13.0.gem","version":"9.13.0","features":["Enhance AWS Lambda function instrumentation","Add experimental OpenSearch instrumentation","Improve framework detection accuracy for Grape and Padrino","Silence Bundler `all_specs` deprecation warning"],"bugs":["Fix Falcon dispatcher detection","Fix for a Redis instrumentation error when Redis::Cluster::Client is present","Address JRuby concurrency issue with config hash accessing"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.13.0 Version 9.13.0 enhances support for AWS Lambda functions, adds experimental OpenSearch instrumentation, updates framework detection, silences a Bundler deprecation warning, fixes Falcon dispatcher detection, fixes a bug with Redis instrumentation installation, and addresses a JRuby-specific concurrency issue. Feature: Enhance AWS Lambda function instrumentation When utilized via the latest New Relic Ruby layer for AWS Lambda , the agent now offers enhanced support for AWS Lambda function instrumentation. The agent's instrumentation for AWS Lambda functions now supports distributed tracing. Web-triggered invocations are now identified as being \"web\"-based when an API Gateway call is involved, with support for both API Gateway versions 1.0 and 2.0. Web-based calls have the HTTP method, URI, and status code recorded. The agent now recognizes and reports on 12 separate AWS resources that are capable of triggering a Lambda function invocation: ALB, API Gateway V1, API Gateway V2, CloudFront, CloudWatch Scheduler, DynamoStreams, Firehose, Kinesis, S3, SES, SNS, and SQS. The type of the triggering resource and its ARN will be recorded for each resource, and for many of them, extra resource-specific attributes will be recorded as well. For example, Lambda function invocations triggered by S3 bucket activity will now result in the S3 bucket name being recorded.\nPR#2811 Feature: Add experimental OpenSearch instrumentation The agent will now automatically instrument the opensearch-ruby gem. We're marking this instrumentation as experimental because more work is needed to fully test it. OpenSearch instrumentation provides telemetry similar to Elasticsearch. Thank you, @Earlopain  for reporting the issue and @praveen-ks  for an initial draft of the instrumentation. Issue#2228  PR#2796 Feature: Improve framework detection accuracy for Grape and Padrino Previously, applications using the Grape framework would set ruby as their framework within the Environment Report. Now, Grape applications will be set to grape. Similarly, applications using the Padrino framework would be set to sinatra. Now, they will be set to padrino. This will help the New Relic security agent compatibility checks. Thank you, @prateeksen  for making this change. Issue#2777  PR#2789 Feature: Silence Bundler all_specs deprecation warning Bundler.rubygems.all_specs was deprecated in favor of Bundler.rubygems.installed_specs in Bundler versions 2+, causing the agent to emit deprecation warnings. The method has been updated when Bundler 2+ is detected and warnings are now silenced. Thanks to @jcoyne  for reporting this issue. Issue#2733  PR#2823 Bugfix: Fix Falcon dispatcher detection Previously, we tried to use the object space to determine whether the Falcon web server  was in use. However, Falcon is not added to the object space until after the environment report is generated, resulting in a nil dispatcher. Now, we revert to an earlier strategy that discovered the dispatcher using File.basename. Thank you, @prateeksen  for reporting this issue and researching the problem. Issue#2778  PR#2795 Bugfix: Fix for a Redis instrumentation error when Redis::Cluster::Client is present The Redis instrumentation previously contained a bug that would cause it to error out when Redis::Cluster::Client was present, owing to the use of a Ruby return outside of a method. Thanks very much to @jdelStrother  for not only reporting this bug but pointing us to the root cause as well. Issue#2814  PR#2816 Bugfix: Address JRuby concurrency issue with config hash accessing The agent's internal configuration class maintains a hash that occassionally gets rebuilt. During the rebuild, certain previously dynamically determined instrumentation values are preserved for the benefit of the New Relic Ruby security agent . After reports from JRuby customers regarding concurrency issues related to the hash being accessed while being modified, two separate fixes went into the hash rebuild logic previously: a Hash#dup operation and a synchronize do block. But errors were still reported. We ourselves remain unable to reproduce these concurrency errors despite using the same exact versions of JRuby and all reported software. After confirming that the hash access code in question is only needed for the Ruby security agent (which operates only in non-production dedicated security testing environments), we have introduced a new fix for JRuby customers that will simply skip over the troublesome code when JRuby is in play but the security agent is not. PR#2798","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-13-0","eolDate":"2025-08-22"},{"agent":"ruby","date":"2024-07-24","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.12.0.gem","version":"9.12.0","features":["Add support for the newrelic_security agent","Add instrumentation for LogStasher","Add instrumentation for redis-clustering","Produce metrics for 4 additional Action Controller Rails notifications"],"bugs":["Update Elasticsearch instrumentation to only attempt to get the cluster name once per client"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.12.0 Version 9.12.0 adds support for the newrelic_security agent, introduces instrumentation for the LogStasher gem, improves instrumentation for the redis-clustering gem, and updates the Elasticsearch instrumentation to only attempt to get the cluster name once per client, even if it fails. Feature: Add support for the newrelic_security agent New Relic Interactive Application Security Testing (IAST)  can help you prevent cyberattacks and breaches on your applications by probing your running code for exploitable vulnerabilities. The newrelic_security gem provides this feature for Ruby. It depends on newrelic_rpm. This is the first version of newrelic_rpm compatible with newrelic_security. At this time, the security agent is intended for use only within a dedicated security testing environment with data that can tolerate modification or deletion. The security agent is available as a separate Ruby gem, newrelic_security. It is recommended that this separate gem only be introduced to a security testing environment by leveraging Bundler grouping like so: In order to run the security agent, you need to update your configuration. At a minimum, security.agent.enabled and security.enabled must be set to true. They are false by default. Similar to the gem installation, we recommend you set these configurations for a special security testing environment only. Here's an example using newrelic.yml: The following configuration relate to the newrelic_security gem: | Configuration name                         | Default                    | Behavior                                                                                                                                                        |\n| ------------------------------------------ | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| security.agent.enabled                     | false                    | If true, the security agent is loaded (a Ruby 'require' is performed)                                                                                         |\n| security.enabled                           | false                    | If true, the security agent is started (the agent runs in its event loop)                                                                                     |\n| security.mode                              | 'IAST'                   | Defines the mode for the security agent to operate in. Currently only 'IAST' is supported                                                                       |\n| security.validator_service_url             | 'wss://csec.nr-data.net' | Defines the endpoint URL for posting security related data                                                                                                      |\n| security.detection.rci.enabled             | true                     | If true, enables RCI (remote code injection) detection                                                                                                        |\n| security.detection.rxss.enabled            | true                     | If true, enables RXSS (reflected cross-site scripting) detection                                                                                              |\n| security.detection.deserialization.enabled | true                     | If true, enables deserialization detection                                                                                                                    |\n| security.application_info.port             | nil                      | An Integer representing the port the application is listening on. This setting is mandatory for Passenger servers. Other servers should be detected by default. | Feature: Add instrumentation for LogStasher The agent will now record logs generated by LogStasher . Versions 1.0.0 and above of the LogStasher gem are supported. PR#2559 Feature: Add instrumentation for redis-clustering Version 5.x of the redis gem moved cluster behavior into a different gem, redis-clustering. This gem can access instrumentation registered through RedisClient::Middleware. Previously, the agent only instrumented the call_pipelined method through this approach, but now users of the redis-clustering gem will also have instrumentation registered for connect and call methods. In addition, the way the database_name attribute is set for Redis datastore spans is now compatible with all versions of Redis supported by the New Relic Ruby agent. Thank you, @praveen-ks  for bringing this to our attention. Issue#2444  PR#2720 Bugfix…","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-12-0","eolDate":"2025-07-24"},{"agent":"ruby","date":"2024-06-20","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.11.0.gem","version":"9.11.0","features":["Add instrumentation for SQS"],"bugs":["HTTP status code based expected errors will now have an \"expected\" value of \"true\"","Stripe metric names will no longer include full request paths to limit the unique name count"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.11.0 Version 9.11.0 introduces instrumentation for the aws-sdk-sqs gem, fixes a bug related to expected errors not bearing a \"true\" value for the \"expected\" attribute if expected as a result of an HTTP status code match and changes the way Stripe instrumentation metrics are named to prevent high-cardinality issues. Feature: Add instrumentation for SQS The agent has added instrumentation for the aws-sdk-sqs gem . The agent will now record message broker spans for SQS client calls made with the aws-sdk-sqs gem. PR#2679 Bugfix: HTTP status code based expected errors will now have an \"expected\" value of \"true\" Previously when an error was treated as expected by the agent as a result of a matching HTTP status code being found in the :'error_collector.expected_status_codes' configuration setting, the error would not appear with an \"expected\" attribute value of \"true\" in the errors in the errors inbox. PR#2710 Bugfix: Stripe metric names will no longer include full request paths to limit the unique name count The Stripe instrumentation introduced in agent version v9.5.0 produced instrumentation metric names that used the full Stripe request path. For any significant Stripe usage, this could quickly lead to very large number of distinct metric names. Now only the API version and the category part of the request path are included in the metric name which still includes the \"Stripe\" opener and method (ex: \"get\") closer. Thanks to @jdelStrother  and @jsneedles  for bringing this issue to our attention and providing terrific information explaining the problem and potential paths to resolution. PR#2716","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-11-0","eolDate":"2025-06-20"},{"agent":"ruby","date":"2024-06-06","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.10.2.gem","version":"9.10.2","features":[],"bugs":["DynamoDB instrumentation logging errors when trying to get account_id","Remove Rails::Command::RakeCommand from the default list of autostart.denylisted_constants"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.10.2 Version 9.10.2 fixes a bug related to the new DynamoDB instrumentation and removes Rails::Command::RakeCommand from the default list of denylisted constants. Bugfix: DynamoDB instrumentation logging errors when trying to get account_id When trying to access data needed to add the account_id to the DynamoDB span, the agent encountered an error when certain credentials classes were used. This has been fixed. Thanks to @kichik  for bringing this to our attention. PR#2864 Bugfix: Remove Rails::Command::RakeCommand from the default list of autostart.denylisted_constants The default value for the autostart.denylisted_constants configuration was changed in 9.10.0 to include Rails::Command::RunnerCommand and Rails::Command::RakeCommand. The inclusion of Rails::Command::RakeCommand prevented the agent from starting automatically when Solid Queue was started using bin/rails solid_queue:start. We recognize there are many commands nested within Rails::Command::RakeCommand and have decided to remove it from the default list. We encourage users who do not want the agent to run on Rails::Command::RakeCommand to add the constant to their configuration. This can be accomplished by adding the following to your newrelic.yml file: Thank you, @edariedl , for reporting this issue. Issue#2677  PR#2694","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-10-2","eolDate":"2025-06-06"},{"agent":"ruby","date":"2024-06-03","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.10.1.gem","version":"9.10.1","features":[],"bugs":["Incompatibility with Bootstrap"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.10.1 Bugfix: Incompatibility with Bootstrap Version 9.10.1 fixes an incompatibility between the agent and the Bootstrap  gem caused by agent v9.10.0's introduction of a lib/bootstrap.rb file. Thank you to @dorner  for reporting the bug and identifying the 'bootstrap' name collision as the root cause. BUG#2675  PR#2676","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-10-1","eolDate":"2025-06-03"},{"agent":"ruby","date":"2024-05-29","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.10.0.gem","version":"9.10.0","features":["Add instrumentation for DynamoDB","Automatically apply nonces from the Rails content security policy"],"bugs":["Expected errors related to HTTP status code, class, and message won't impact Apdex","Do not start the agent automatically when `rails runner` or `rails db` commands are ran"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.10.0 Version 9.10.0 introduces instrumentation for DynamoDB, adds a new feature to automatically apply nonces from the Rails content security policy, fixes a bug that would cause an expected error to negatively impact a transaction's Apdex, and fixes the agent's autostart logic so that by default rails runner and rails db commands will not cause the agent to start. Feature: Add instrumentation for DynamoDB The agent has added instrumentation for the aws-sdk-dynamodb gem. The agent will now record datastore spans for DynamoDB client calls made with the aws-sdk-dynamodb gem.  PR#2642 Feature: Automatically apply nonces from the Rails content security policy To auto-inject browser monitoring with the New Relic Ruby agent, you either need to set your content security policy to 'unsafe-inline' or provide a nonce. Previously, the only way to provide a nonce was by using the NewRelic::Agent.browser_timing_header  API. Now, when a Rails application uses the content security policy configuration to add a nonce , the nonce will be automatically applied to the browser agent. A new configuration option, browser_monitoring.content_security_policy_nonce , toggles this feature. It is on by default. Thank you @baldarn  for submitting this feature! PR#2544 Bugfix: Expected errors related to HTTP status code, class, and message won't impact Apdex The agent is supposed to prevent observed application errors from negatively impacting Apdex if the errors are either ignored or expected. There are two ways for the agent to expect an error: via the notice_error API receiving an expected: true argument or via matches made against user-configured lists for expected HTTP status codes (:'error_collector.expected_status_codes'), expected error classes (:'error_collector.expected_classes'), or expected error messages (:'error_collector.expected_messages'). Previously, only errors expected via the notice_error API were correctly prevented from impacting Apdex. Expected errors set by configuration incorrectly impacted Apdex. This behavior has been fixed and now both types of expected errors will correctly not impact Apdex. Thanks very much to @florianpilz  for bringing this issue to our attention. PR#2619 Bugfix: Do not start the agent automatically when rails runner or rails db commands are run PR#2239  taught the agent how to recognize bin/rails based contexts that it should not automatically start up in. But bin/rails runner and bin/rails db commands would still see the agent start automatically. Those 2 contexts will now no longer see the agent start automatically. Thank you to @jdelStrother  for both bringing the bin/rails context to our attention and for letting us know about the bin/rails runner and bin/rails db outliers that still needed fixing. PR#2623 Older agent versions that are still supported by New Relic can update to the new list of denylisted constants by having the following line added to the newrelic.yml configuration file:","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-10-0","eolDate":"2025-05-29"},{"agent":"ruby","date":"2023-03-29","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-9.1.0.gem","version":"9.1.0","features":["Error fingerprinting - supply your own errors inbox group names","User tracking - associate errors with a user id"],"bugs":["Remove Distributed Tracing related warnings from agent logs when headers are not present in Sidekiq","Log request headers in debug-level logs instead of human-readable Objects","Fix undefined method `controller_path` logged in Action Controller Instrumentation","Fix Transaction#finish exception and decrease log level for related warning during async transactions"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version at most 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v9.1.0 Version 9.1.0 of the agent delivers support for two new errors inbox  features: error fingerprinting and user tracking, identifies the Amazon Timestream data store, removes Distributed Tracing warnings from agent logs when using Sidekiq, fixes bugs, and is tested against the recently released JRuby 9.4.2.0. Feature: Error fingerprinting - supply your own errors inbox group names Are your error occurrences grouped poorly? Set your own error fingerprint via a callback function. A new set_error_group_callback public API method has been added that will accept a user defined proc. The proc will be invoked for each noticed error and whenever it returns a string, that string will be used as the error group name for the error and will take precedence over any server-side grouping that takes place with the New Relic errors inbox. This gives users much greater control over the grouping of their errors. The customer defined proc will be expected to receive exactly one input argument, a hash. The hash contains the following: | Key                  | Value                                                                        |\n| -------------------- | ---------------------------------------------------------------------------- |\n| :error             | The Ruby error class instance. Offers #class, #message, and #backtrace |\n| :customAttributes  | Any customer defined custom attributes for the current transaction           |\n| :'request.uri'     | The current request URI if available                                         |\n| :'http.statusCode' | The HTTP status code (200, 404, etc.) if available                           |\n| :'http.method'     | The HTTP method (GET, PUT, etc.) if available                                |\n| :'error.expected'  | Whether (true) or not (false) the error was expected                         |\n| :'options'         | The options hash passed to NewRelic::Agent.notice_error                    | The callback only needs to be set once per initialization of the New Relic agent. Example usage: Feature: User tracking - associate errors with a user id You can now see the number of users impacted by an error group. Identify the end user with a new set_user_id public API method that will accept a string representation of a user id and associate that user id with the current transaction. Transactions and errors will then have a new enduser.id agent attribute associated with them. This will allow agent users to tag transactions and errors as belonging to given user ids in support of greater filtering and alerting capabilities. Identify Amazon Timestream when the amazon_timestream AR adapter is used When the agent sees the activerecord-amazon-timestream-adapter  gem being used, it will now identify the data store as \"Timestream\". Thanks very much to @wagner  for contributing this enhancement! PR#1872 Bugfix: Remove Distributed Tracing related warnings from agent logs when headers are not present in Sidekiq Previously, the agent would log a warning to newrelic_agent.log every time it attempted to accept empty Distributed Tracing headers from Sidekiq jobs which could result in an excessive number of warnings. Now the agent will no longer create these warnings when using Sidekiq. PR#1834 Bugfix: Log request headers in debug-level logs instead of human-readable Objects Previously, the agent sometimes received children of the NewRelic::Agent::HTTPClients::AbstractRequest class as an argument when NewRelic::Agent::Transaction::DistributedTracers#log_request_headers was called. This caused debug-level log messages that print the request headers to show human-readable Objects (ex. #<NewRelic::Agent::HTTPClients::HTTPClientRequest:0x00007fd0dda983e0>) instead of the request headers. Now, the hash of the request headers should always be logged. PR#1839 Bugfix: Fix undefined method controller_path logged in Action Controller Instrumentation Previously, the agent could log an error when trying to determine the metric name in the Action Controller instrumentation if the controller class did not respond to controller_path. This has been resolved and the agent will no longer call this method unless the class responds to it. Thank you to @gsar  for letting us know about this issue. PR#1844 Bugfix: Fix Transaction#finish exception and decrease log level for related warning during async transactions Previously, the agent would raise a non-fatal error when a segment without a parent was unfinished when the transaction completed. This error was raised while constructing a warn-level log message. Now that Thread instrumentation is on by default, this log message emits more frequently and is less concerning. …","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-9-1-0","eolDate":"2024-03-29"},{"agent":"ruby","date":"2022-07-11","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.9.0.gem","version":"8.9.0","features":["Add support for Dalli 3.1.0 - 3.2.2"],"bugs":["Fix Infinite Tracing hanging on connection restart","Stop Resque jobs from intermittently getting stuck"],"security":[],"supportedOperatingSystems":null,"description":"v8.9.0 Add support for Dalli 3.1.0 to Dalli 3.2.2 Dalli versions 3.1.0 and above include breaking changes where the agent previously hooked into the gem. We have updated our instrumentation to correctly hook into Dalli 3.1.0 and above. At this time, 3.2.2 is the latest Dalli version and is confirmed to be supported. Bugfix: Infinite Tracing hung on connection restart Previously, when using infinite tracing, the agent would intermittently encounter a deadlock when attempting to restart the infinite tracing connection. This bug would prevent the agent from sending all data types, including non-infinite-tracing-related data. This change reworks how we restart Infinite Tracing to prevent potential deadlocks. Bugfix: Use read_nonblock instead of read on pipe Previously, our PipeChannelManager was using read which could cause resque jobs to get stuck in some versions. This change updates the PipeChannelManager to use read_nonblock instead to avoid this issue. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 6.5.0.357 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-890","eolDate":"2024-07-11"},{"agent":"ruby","date":"2022-06-02","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.8.0.gem","version":"8.8.0","features":["Add support for Makara database adapters with ActiveRecord","Provide Code Level Metrics for New Relic CodeStream"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v8.8.0 Support Makara database adapters with ActiveRecord Thanks to a community submission from lucasklaassen with PR #1177 , the Ruby agent will now correctly work well with the Makara gem . Functionality such as SQL obfuscation should now work when Makara database adapters are used with Active Record. Lowered the minimum payload size to compress Previously the Ruby agent used a particularly large payload size threshold of 64KiB that would need to be met before the agent would compress data en route to New Relic's collector. The original value stems from segfault issues that very old Rubies (older than 2.2) used to encounter when compressing smaller payloads. This value has been lowered to 2KiB (2048 bytes), which should provide a more optimal balance between the CPU cycles spent on compression and the bandwidth savings gained from it. Provide Code Level Metrics for New Relic CodeStream For Ruby on Rails applications and/or those with manually traced methods, the agent is now capable of reporting metrics with Ruby method-level granularity. When the new code_level_metrics.enabled configuration parameter is set to a true value, the agent will associate source-code-related metadata with the metrics for things such as Rails controller methods. Then, when the corresponding Ruby class file that defines the methods is loaded up in a New Relic CodeStream -powered IDE, the four golden signals  for each method will be presented to the developer directly. Supportability Metrics will always report uncompressed payload size New Relic's agent specifications call for Supportability Metrics to always reference the uncompressed payload byte size. Previously, the Ruby agent was calculating the byte size after compression. Furthermore, compression is only performed on payloads of a certain size. This means that sometimes the value could have represented a compressed size and sometimes an uncompressed one. Now the uncompressed value is always used, bringing consistency for comparing two instances of the same metric and alignment with the New Relic agent specifications. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 6.5.0.357 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-880","eolDate":"2024-06-02"},{"agent":"ruby","date":"2022-04-04","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.6.0.gem","version":"8.6.0","features":["Introduce APM Automatic logs in context, a feature to forward application logs directly to New Relic"],"bugs":["Satify Curb's method_with_tracing verb argument requirement","Improve the usage of the hostname executable and other executables to fix errors in AWS Lambda"],"security":[],"supportedOperatingSystems":null,"description":"v8.6.0 Telemetry-in-Context:  Automatic Application Logs, a quick way to view logs no matter where you are in the platform Adds support for forwarding application logs to New Relic. This automatically sends application logs that have been enriched to power Telemetry-in-Context. This is disabled by default in this release. This may be on by default in a future release. Adds support for enriching application logs written to disk or standard out. This can be used with another log forwarder to power Telemetry-in-Context if in-agent log forwarding is not desired. We recommend enabling either log forwarding or local log decorating, but not both features. This is disabled by default in this release. Improves speed and Resque support for logging metrics which shows the rate of log message by severity in the Logs chart in the APM Summary view. This is enabled by default in this release. To learn more about Telemetry-in-Context and the configuration options please see the documentation here . Bugfix: Curb - satify method_with_tracing's verb argument requirement When Curb instrumentation is used (either via prepend or chain), be sure to always pass the verb argument over to method_with_tracing which requires it. Thank you to @knarewski for bringing this issue to our attention, for providing a means of reproducing an error, and for providing a fix. That fix has been replicated by the agent team with permission. See Issue 1033  for more details. Improve the usage of the 'hostname' executable and other executables In all places where a call to an executable binary is made (currently this is done only for the 'hostname' and 'uname' binaries), leverage a new helper method when making the call. This new helper will a) not attempt to execute the binary if it cannot be found, and b) prevent STDERR/STDOUT content from appearing anywhere except New Relic's own logs if the New Relic logger is set to the 'debug' level. When calling 'hostname', fall back to Socket.gethostname if the 'hostname' binary cannot be found. When calling 'uname', fall back on using a value of 'unknown' if the 'uname' command fails. Many thanks to @metaskills and @brcarp for letting us know that Ruby AWS Lambda functions can't invoke 'hostname' and for providing ideas and feedback with Issue #697 . Documentation: remove confusing duplicate RUM entry from newrelic.yml The browser_monitoring.auto_instrument configuration option to enable web page load timing (RUM) was confusingly listed twice in the newrelic.yml config file. This option is enabled by default. The newrelic.yml file has been updated to list the option only once. Many thanks to @robotfelix for bringing this to our attention with Issue #955 . Bugfix: fix unit test failures when New Relic environment variables are present Previously, unit tests would fail with unexpected invocation errors when NEW_RELIC_LICENSE_KEY and NEW_RELIC_HOST environment variables were present. Now, tests will discard these environment variables before running. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 6.3.0.355 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-860","eolDate":"2024-04-04"},{"agent":"ruby","date":"2022-02-24","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.5.0.gem","version":"8.5.0","features":["Support IMDSv2 by using a token with metadata API calls","Update configuration options for transaction events","Deprecate and replace select configuration options"],"bugs":["Resolve Rails 5 + Puma errors","Muffle anticipated stderr warnings for hostname calls for OpenBSD users","Eliminate warnings for redefined constants in ParameterFiltering"],"security":[],"supportedOperatingSystems":null,"description":"v8.5.0 AWS: Support IMDSv2 by using a token with metadata API calls When querying AWS for instance metadata, include a token in the request headers. If an AWS user configures instances to require a token, the agent will now work. For instances that do not require the inclusion of a token, the agent will continue to work in that context as well. Muffle anticipated stderr warnings for \"hostname\" calls When using the hostname binary to obtain hostname information, redirect STDERR to /dev/null. Thanks very much to @frenkel for raising this issue on behalf of OpenBSD users everywhere and for providing a solution with PR #965 . Added updated configuration options for transaction events and deprecated previous configs \nThis release deprecates and replaces the following configuration options: Deprecated Replacement event_report_period.analytic_event_data event_report_period.transaction_event_data analytics_events.enabled transaction_events.enabled analytics_events.max_samples_stored transaction_events.max_samples_stored Eliminated warnings for redefined constants in ParameterFiltering Fixed the ParameterFiltering constant definitions so that they are not redefined on multiple reloads of the module. Thank you to @TonyArra for bringing this issue to our attention. Docker for development Docker and Docker Compose may now be used for local development and testing with the provided Dockerfile and docker-compose.yml files in the project root. See DOCKER.md  for usage instructions. Bugfix: Rails 5 + Puma errors in rack \"can't add a new key into hash during iteration\" When using rails 5 with puma, the agent would intermittently cause rack to raise a RuntimeError: can't add a new key into hash during iteration. We have identified the source of the error in our instrumentation and corrected the behavior so it no longer interferes with rack. Thanks to @sasharevzin for bringing attention to this error and providing a reproduction of the issue for us to investigate. CI: target JRuby 9.3.3.0 Many thanks to @ahorek for PR #919 , PR #921 , and PR #922  to keep us up to date on the JRuby side of things. The agent is now actively being tested against JRuby 9.3.3.0. NOTE that this release does not contain any non-CI related changes for JRuby. Old agent versions are still expected to work with newer JRubies, and the newest agent version is still expected to work with older JRubies. CI: Update unit tests for Rails 7.0.2 Ensure that the 7.0.2 release of Rails is fully compatible with all relevant tests. CI: Ubuntu 20.04 LTS To stay current and secure, our CI automation is now backed by version 20.04 of Ubuntu's long term support offering (previously 18.04).","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-850","eolDate":"2024-02-24"},{"agent":"ruby","date":"2022-01-25","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.4.0.gem","version":"8.4.0","features":["Add Rails 7.0 instrumentation","Improve the performance of NewRelic::Agent::GuidGenerator#generate_guid"],"bugs":["Fix Sinatra application crashes caused by calling controller instrumentation methods while agent was disabled"],"security":[],"supportedOperatingSystems":null,"description":"v8.4.0 Provide basic support for Rails 7.0 This release includes Rails 7.0 as a tested Rails version. Updates build upon the agent's current Rails instrumentation and do not include additional instrumentation for new features. Improve the performance of NewRelic::Agent::GuidGenerator#generate_guid This method is called by many basic operations within the agent including transactions, datastore segments, and external request segments. Thank you, @jdelstrother for contributing this performance improvement! Documentation: Development environment prep instructions The multiverse collection of test suites requires a variety of data handling software (MySQL, Redis, memcached, etc.) to be available on the machine running the tests. The project documentation  has been updated to outline the relevant software packages, and a Brewfile file has been added to automate software installation with Homebrew. Bugfix: Add ControllerInstrumentation::Shims to Sinatra framework When the agent is disabled by setting the configuration settings enabled, agent_enabled, and/or monitor_mode to false, the agent loads shims for public controller instrumentation methods. These shims were missing for the Sinatra framework, causing applications to crash if the agent was disabled. Thank you, @NC-piercej for bringing this to our attention! Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.7.0.350 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-840","eolDate":"2024-01-25"},{"agent":"ruby","date":"2022-01-10","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.3.0.gem","version":"8.3.0","features":["Add support for Ruby 3.1.0"],"bugs":["Encode ASCII-8BIT log messages correctly","Update AdaptiveSampler#sampled? algorithm"],"security":[],"supportedOperatingSystems":null,"description":"v8.3.0 Updated the agent to support Ruby 3.1.0 Most of the changes involved updating the multiverse suite to exclude runs for older versions of instrumented gems that are not compatible with Ruby 3.1.0. In addition, Infinite Tracing testing was updated to accommodate YAML::unsafe_load for Psych 4 support. Bugfix: Update AdaptiveSampler#sampled? algorithm One of the clauses in AdaptiveSampler#sampled? would always return false due to Integer division returning a result of zero. This method has been updated to use Float division instead, to exponentially back off the number of samples required. This may increase the number of traces collected for transactions. A huge thank you to @romul for bringing this to our attention and breaking down the problem! Bugfix: Correctly encode ASCII-8BIT log messages The encoding update for the DecoratingLogger in v8.2.0 did not account for ASCII-8BIT encoded characters qualifying as valid_encoding?. Now, ASCII-8BIT characters will be encoded as UTF-8 and include replacement characters as needed. We're very grateful for @nikajukic's collaboration and submission of a test case to resolve this issue. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.6.0.349 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-830","eolDate":"2024-01-10"},{"agent":"ruby","date":"2021-11-29","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.2.0.gem","version":"8.2.0","features":["Add instrumentation for Tilt gem","Remove Rails 2 instrumentation","Deprecate the configuration option error_collector.ignore_errors"],"bugs":["Don't record span events when using newrelic_ignore","Scrub non-unicode characters from DecoratingLogger","Stop distributed tracing headers from emitting errors when the agent is not connected"],"security":[],"supportedOperatingSystems":null,"description":"v8.2.0 New instrumentation for Tilt gem Template rendering using Tilt  is now instrumented. Tilt 2.x is supported for Ruby versions 2.2 and above and  1.x is supported for Ruby versions below 2.7. See PR #847  for details. Configuration error_collector.ignore_errors is marked as deprecated This setting has been marked as deprecated in the documentation since version 7.2.0 and is now flagged as deprecated within the code. Remove Rails 2 instrumentation Though any version of Rails 2 has not been supported by the Ruby agent since v3.18.1.330, instrumentation for ActionController and ActionWebService specific to that version were still part of the agent. This instrumentation has been removed. Remove duplicated settings from newrelic.yml Thank you @jakeonfire for bringing this to our attention and @kuroponzu for making the changes! Bugfix: Span events recorded when using newrelic_ignore Previously, the agent was incorrectly recording span events only on transactions that should be ignored. This fix will prevent any span events from being created for transactions using newrelic_ignore, or ignored through the rules.ignore_url_regexes configuration option. Bugfix: Print deprecation warning for cross-application tracing if enabled Prior to this change, the deprecation warning would log whenever the agent started up, regardless of configuration. Thank you @alpha-san for bringing this to our attention! Bugfix: Scrub non-unicode characters from DecoratingLogger To prevent JSON::GeneratorErrors, the DecoratingLogger replaces non-Unicode characters with the replacement character: �. Thank you @jdelStrother for bringing this to our attention! Bugfix: Distributed tracing headers emitted errors when agent was not connected Previously, when the agent had not yet connected it would fail to create a trace context payload and emit an error, \"TypeError: no implicit conversion of nil into String,\" to the agent logs. The correct behavior in this situation is to not create these headers due to the lack of required information. Now, the agent will not attempt to create trace context payloads until it has connected. Thank you @Izzette for bringing this to our attention! Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.5.0.348 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-820","eolDate":"2023-11-29"},{"agent":"ruby","date":"2023-02-06","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.16.0.gem","version":"8.16.0","features":["Add new Ruby on Rails library instrumentations. The agent newly supports or provides updated support for Action Cable, Action Controller, Action Mailbox, Action Mailer, Active Job, and Active Support"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version at most 90 days old. Read more about keeping agent up to date . As of this release, the oldest supported version is 6.9.0.363 v8.16.0 Version 8.16.0 introduces more Ruby on Rails instrumentation (especially for Rails 6 and 7) for various Action*/Active* libraries whose actions produce Active Support notifications events . Add Various Ruby on Rails Library Instrumentations New instrumentation is now automatically provided by several Action*/Active* libaries that generate Active Support notifications. With each Ruby on Rails release, new the Rails libraries add new events and sometimes existing events have their payload parameters updated as well. The New Relic Ruby agent will now automatically process more of these events and parameters with New Relic segments created for each event. At a minimum, each segment gives timing information for the event. In several cases, all non-sensitive event payload parameters are also passed along in the segment. The agent now newly supports or has updated support for the following libraries: Action Cable (for WebSockets) PR#1749 Action Controller (for the 'C' in MVC) PR#1744 Action Mailbox (for sending mail) PR#1740 Action Mailer (for routing mail) PR#1740 Active Job (for background jobs) PR#1742 Active Support (for caching operations) PR#1742 The instrumentations for each of these libaries are all enabled by default, but can be independently disabled via configuration by using the following parameters: | Configuration name          | Default | Behavior                                               |\n| --------------------------- | ------- | ------------------------------------------------------ |\n| disable_action_cable      | false | If true, disables Action Cable instrumentation.      |\n| disable_action_controller | false | If true, disables Action Controller instrumentation. |\n| disable_action_mailbox    | false | If true, disables Action Mailbox instrumentation.    |\n| disable_action_mailer     | false | If true, disables Action Mailer instrumentation.     |\n| disable_activejob         | false | If true, disables Active Job instrumentation.        |\n| disable_active_support    | false | If true, disables Active Support instrumentation.    |","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-8160","eolDate":"2024-02-06"},{"agent":"ruby","date":"2023-01-09","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.15.0.gem","version":"8.15.0","features":["Add support for Ruby 3.2.0","Add instrumentation for concurrent-ruby","Use batching and compression by default for Infinite Tracing","Add support for Padrino 0.15.2 running with Sinatra 3"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you are prevented from upgrading to the latest version, ensure that your agents are updated to a version at most 90 days old. Read more about keeping your agent up to date . As of this release, the oldest supported version is 6.9.0.363 v8.15.0 Version 8.15.0 of the agent confirms compatibility with Ruby 3.2.0, adds instrumentation for concurrent-ruby, and confirms Sinatra 3 compatibility with Padrino 0.15.2. It also enables batching and compression for Infinite Tracing. Add Support for Ruby 3.2.0 Following the 3.2.0 release of Ruby, the New Relic Ruby agent has confirmed compatibility with and now supports the official release of Ruby 3.2.0. PR#1715 Add instrumentation for concurrent-ruby The agent now instruments the concurrent-ruby  gem for versions 1.1.5 and above. This instrumentation provides visibility inside blocks passed to many of the gem's API methods, including Concurrent::Promises.future and Concurrent::Future.execute. | Configuration name                | Default | Behavior                                                                                                                        |\n| --------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------- |\n| instrumentation.concurrent_ruby | auto    | Controls auto-instrumentation of the concurrent-ruby library at start up. May be one of auto, prepend, chain, disabled. | Infinite Tracing: Use batching and compression For Infinite Tracing , which Ruby applications can leverage with the newrelic-infinite_tracing gem, payloads will now be batched and compressed to signficantly decrease the amount of outbound network traffic. PR#1723 | Configuration name                   | Default | Behavior                                                                                                         |     |        |                                                                               |\n| ------------------------------------ | ------- | ---------------------------------------------------------------------------------------------------------------- | --- | ------ | ----------------------------------------------------------------------------- |\n| infinite_tracing.batching          | true    | If true (the default), the Trace Observer will receive data in batches instead of sending each span individually |     |        |                                                                               |\n| infinite_tracing.compression_level | high    | Configure the compression level for data sent to the trace observer. May be one of [none                        | low | medium | high]. 'high' is the default. Set the level to 'none' to disable compression. | Add Support for Padrino 0.15.2 and Sinatra 3 We've added testing to confirm Padrino 0.15.2 and Sinatra 3 are compatible with the Ruby agent. Thank you @nesquena  for letting us know 0.15.2 was ready! PR#1712","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-8150","eolDate":"2024-01-09"},{"agent":"ruby","date":"2022-12-14","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.14.0.gem","version":"8.14.0","features":["Speed up GUID generation","Add instrumentation for Rails ActiveSupport::Notifications custom events"],"bugs":["Fix how the agent handles an unknown Redis database index in RedisClient v0.11 and older"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date . As of this release, the oldest supported version is 6.8.0.359 v8.14.0 Version 8.14.0 of the agent restores desired Capistrano-based changelog lookup functionality when a deployment is performed, speeds up GUID generation, delivers support for instrumenting Rails custom event notifications, fixes potential compatibility issues with the RedisClient gem, and fixes bugs related to initialization in Rails. Deployment Recipe: Restore desired Capistrano-based changelog lookup behavior The New Relic Ruby agent offers a Capistrano recipe for recording app deployments . The recipe code was significantly cleaned up with PR#1498  which inadvertently changed the way the recipe handles the changelog for a deployment. Community member @arthurwozniak  spotted and corrected this change in order to restore the desired changelog lookup functionality while retaining all of the previous cleanup. Thank you very much for your contribution, @arthurwozniak ! PR#1653 Speed up GUID generation The agent leverages random numbers in its GUID (globally unique identifier) generation and would previously always freshly calculate the result of 16^16 or 32^32 before generating a random number. Given that those 16^16 and 32^32 operations are expected, it makes sense to calculate their results up front and store them in constants to be referred to later. Doing so has resulted in a performance gain for the generation of GUIDs. Many thanks to @tungmq  for contributing this optimisation and the benchmarks to support it! PR#1693 Support for Rails ActiveSupport::Notifications for custom events When the new active_support_custom_events_names configuration parameter is set equal to an array of custom event names to subscribe to, the agent will now subscribe to each of the names specified and report instrumentation for the events when they take place. Creating custom events  is simple and now reporting instrumentation for them to New Relic is simple as well. PR#1659 Bugfix: Support older versions of the RedisClient gem, handle unknown Redis database index With version 8.13.0 of the agent, support was added for the redis-rb  gem v5+ and the new RedisClient  gem. With versions of RedisClient older than v0.11, the agent could cause the monitored application to crash when attempting to determine the Redis database index. Version 8.14.0 adds two related improvements. Firstly, support for RedisClient versions older than v0.11 has been added to get at the database index value. Secondly, the agent will no longer crash or impact the monitored application in the event that the database index cannot be obtained. Thank you very much to our community members @mbsmartee  and @patatepartie  for bringing this issue to our attention, for helping us determine how to best reproduce it, and for testing out the update. We appreciate your help! Issue#1650  PR#1673 ~~Bugfix: Defer agent startup in Rails until after application-defined initializers have run ~~ ~~In Rails, the agent previously loaded before any application-defined initializers. This allowed initializers to reference the add_method_tracer API. However, this had the side-effect of forcing some framework libraries to load before initializers ran, preventing any configuration values related to these libraries from being applied. This fix provides an option to split initialization into two parts: load add_method_tracer before application-defined initializers and start the agent after application-defined initializers. This may cause other initializers to behave differently.~~ ~~If you'd like to use this feature, set defer_rails_initialization to true. It is false by default, but may become true by default in a future release.~~ ~~Furthermore, our Action View instrumentation was missing an ActiveSupport.on_load block around the code that loads our instrumentation.~~ ~~Thank you @jdelStrother  for bringing this to our attention and collaborating with us on a fix. PR#1658 ~~ Unfortunately, this bugfix is unreachable as written because the configuration value used to access the bugfix won't be applied until after initialization. Follow along for updates at Issue#662 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-8140","eolDate":"2023-12-14"},{"agent":"ruby","date":"2022-11-21","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.13.1.gem","version":"8.13.1","features":[],"bugs":["Fix NoMethodError when using Sidekiq v7.0 with Redis Client v0.11"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date . As of this release, the oldest supported version is 6.8.0.359 v8.13.1 Version 8.13.1 of the agent provides a bugfix for Redis v5.0 instrumentation. Fix NoMethodError when using Sidekiq v7.0 with Redis Client v0.11 In some cases, the RedisClient object cannot directly access methods like db, port, or path. These methods are always available on the client.config object. This raised a NoMethodError in environments that used Sidekiq v7.0 and Redis Client  v0.11. Thank you to fcheung  and @stevenou  for bringing this to our attention! Issue#1639","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-8131","eolDate":"2023-11-21"},{"agent":"ruby","date":"2022-11-15","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.13.0.gem","version":"8.13.0","features":["Add support for Redis 5.0","Add support for Sidekiq 7.0","Update Rack 3.0 instrumentation to support the use of a block with Rack::Builder#run"],"bugs":["Fix identification of Unicorn, Rainbows, and FastCGI dispatchers with Rack v3.0","Fix recording of add_method_tracer code level metric attributes on private methods","Fix undefined method :category error for NewRelic::Agent::Transaction::Class"],"security":[],"supportedOperatingSystems":null,"description":"v8.13.0 Version 8.13.0 of the agent updates our Rack, Redis, and Sidekiq instrumentation. It also delivers some bugfixes. Support for Redis v5.0 Redis v5.0 restructures where some of our instrumented methods are located and how they are named. It also introduces a new instrumentation middleware API . This API is used for pipelined and multi calls to maintain reporting parity with previous Redis versions. However, it is introduced later in the chain, so you may see errors that used to appear at the segment level on the transaction instead. The agent's behavior when used with older supported Redis versions will remain unaffected. PR#1611 Support for Sidekiq v7.0 Sidekiq v7.0 removed Delayed Extensions and began offering client and server middleware  classes to inherit from. The agent's Sidekiq instrumentation has been updated accordingly. The agent's behavior when used with older Sidekiq versions will remain unaffected. PR#1615  NOTE:  an issue was discovered with Sidekiq v7.0+ and addressed by Ruby agent v8.13.1. If you are using Sidekiq, please skip Ruby agent v8.13.0 and use v8.13.1 or above. Support for Rack v3.0: Rack::Builder#new accepting a block Via rack/rack#1942  (released with Rack v3.0), Rack::Builder#run now optionally accepts a block instead of an app argument. The agent's instrumentation has been updated to support the use of a block with Rack::Builder#run. PR#1600 Bugfix: Correctly identify Unicorn, Rainbows and FastCGI with Rack v3.0 Unicorn, Rainbows, or FastCGI web applications using Rack v3.0 may previously have had the \"dispatcher\" value incorrectly reported as \"Webrick\" instead of \"Unicorn\", \"Rainbows\", or \"FastCGI\". This issue has now been addressed. PR#1585 Bugfix: add_method_tracer fails to record code level metric attributes on private methods When using add_method_tracer on a private method, the agent was unable to record code level metrics for the method. This resulted in the following being logged to the newrelic_agent.log file. Thank you @jdelStrother  for bringing this issue to our attention and suggesting a fix! PR#1593 Bugfix: Category is a required keyword arg for NewRelic::Agent::Tracer.in_transaction When support for Ruby 2.0 was dropped in version 8.0.0 of the agent, the agent API methods were updated to use the required keyword argument feature built into Ruby, rather than manually raising ArgumentErrors. The API method NewRelic::Agent::Tracer.in_transaction removed the ArgumentError raised by the agent, but did not update the method arguments to identify :category as a required keyword argument. This is now resolved. Thank you @tatzsuzuki  for bringing this to our attention. PR#1587 Support statement New Relic recommends that you upgrade the Ruby agent regularly and at a minimum of every 3 months. As of this release, the oldest supported version is 6.8.0.359 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-8130","eolDate":"2023-11-15"},{"agent":"ruby","date":"2022-10-26","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.12.0.gem","version":"8.12.0","features":["Add Elasticsearch instrumentation","Increase default custom event limit from 1000 to 3000 events per minute","Deprecate support for Ruby 2.3"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"v8.12.0 Version 8.12.0 of the Ruby agent delivers new Elasticsearch instrumentation. Version 8.12.0 of the Ruby agent also increases the default number of recorded custom events, announces the deprecation of Ruby 2.3, and brings some valuable code cleanup. Support for Elasticsearch instrumentation This release of the Ruby agent adds support to automatically instrument the elasticsearch  gem. Versions 7.x and 8.x are supported. PR#1525 | Configuration name                | Default | Behavior                                                                                                                      |\n| --------------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------- |\n| instrumentation.elasticsearch   | auto    | Controls auto-instrumentation of the elasticsearch library at start up. May be one of auto, prepend, chain, disabled. |\n| elasticsearch.capture_queries   | true    | If true, the agent captures Elasticsearch queries in transaction traces.                                                    |\n| elasticsearch.obfuscate_queries | true    | If true, the agent obfuscates Elasticsearch queries in transaction traces.                                                  | Custom Event Limit Increase This version of the Ruby agent increases the default limit of custom events from 1000 events per minute to 3000 events per minute. If your custom events were being limited, this change will allow more custom events to be sent to New Relic. There is also a new configurable maximum limit of 100,000 events per minute. To change the limits, see the documentation for max_samples_stored . To learn more about the change and how to determine if custom events are being dropped, see our Explorers Hub post . PR#1541 Deprecate support for Ruby 2.3 Ruby 2.3 reached end of life on March 31, 2019. The Ruby agent has deprecated support for Ruby 2.3 and will make breaking changes for this version in its next major release, v9.0.0 (release date not yet planned). All 8.x.x versions of the agent will remain compatible with Ruby 2.3. Cleanup: Remove orphaned code In both the agent and unit tests, changes have taken place over the years that have left certain bits of code unreachable. This orphaned code can complicate code maintenance and refactoring, so getting it squared away can be very helpful. Commmuniy member @ohbarye  contributed two separate cleanup PRs for this release; one for the agent and one for the tests. PR#1537  PR#1548 Thank you to @ohbarye  for contributing this helpful cleanup! Support statement New Relic recommends that you upgrade the Ruby agent regularly and at a minimum of every 3 months. As of this release, the oldest supported version is 6.7.0.359 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-8120","eolDate":"2023-10-26"},{"agent":"ruby","date":"2022-10-11","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.11.0.gem","version":"8.11.0","features":["Add support for New Relic REST API v2 when using newrelic deployments command"],"bugs":["Fix memory leak in Curb instrumentation"],"security":[],"supportedOperatingSystems":null,"description":"v8.11.0 Version 8.11.0 of the agent updates the newrelic deployments command to work with API keys issued to newer accounts, fixes a memory leak in the instrumentation of Curb error handling, further preps for Ruby 3.2.0 support, and includes several community member driven cleanup and improvement efforts. Thank you to everyone involved! Added support for New Relic REST API v2 when using newrelic deployments command Previously, the newrelic deployments command only supported the older version of the deployments api, which does not currently support newer license keys. Now you can use the New Relic REST API v2 to record deployments by providing your user API key to the agent configuration using api_key. When this configuration option is present, the newrelic deployments command will automatically use the New Relic REST API v2 deployment endpoint. PR#1461 Thank you to @Arkham  for bringing this to our attention! Cleanup: Performance tests, constants, rubocop-minitest assertions and refutations Community member @esquith  contributed a whole slew of cleanup successes for our performance test configuration, orphaned constants in our code base, and RuboCop related improvements. PR#1406  PR#1408  PR#1409  PR#1411 Thank you @esquith  for these great contributions! CI: Notify on a change from failure to success A super handy, much beloved feature of certain CI and build systems is to not only notify when builds start to fail, but also to notify again when the builds once again start to go green. Community member @luigieai  was able to figure out how to configure our existing complex, multiple-3rd-party-action based GitHub Actions pipeline to notify on a switch back to success from failure. PR#1519 This is much appreciated! Thank you, @luigieai . Spelling corrections Community member @jsoref , author of the Check Spelling  GitHub Action, contributed a significant number of spelling corrections throughout the code base. The intelligent issues that were flagged made for a more comprehensive review than a simple dictionary based check would have been able to provide, and the changes are much appreciated. PR#1508 Thank you very much, @jsoref ! Ruby 3.2.0-preview2 compatibility Ruby 3.2.0-preview1 introduced a change to the way that Ruby reports VM stats and the approach was changed yet again to a 3rd approach with the preview2 release. New Relic reports on Ruby VM stats and is keeping track of the Ruby 3.2 development process to help ensure our customers with a smooth and worthwhile upgrade process once Ruby 3.2.0 (non-preview) is released. PR#1436 Bugfix: Fix memory leak in the Curb instrumentation Community member @charkost  was able to rework the on_failure callback logic prepped via the agent's Curb instrumentation in order to avoid some nesting that was causing memory leaks. PR#1518 Many thanks for both the heads up on the issue and the fix, @charkost ! Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 6.7.0.359 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-8110","eolDate":"2023-10-11"},{"agent":"ruby","date":"2022-09-13","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.10.1.gem","version":"8.10.1","features":[],"bugs":["Fix how the agent stores and sends unscoped metrics when instrumentation.thread.tracing is enabled","Don't raise ArgumentError when both gRPC and other Google gems are present"],"security":[],"supportedOperatingSystems":null,"description":"v8.10.1 Bugfix: Missing unscoped metrics when instrumentation.thread.tracing is enabled Previously, when instrumentation.thread.tracing was set to true, some puma applications encountered a bug where a varying number of unscoped metrics would be missing. The agent now will correctly store and send all unscoped metrics. Thank you to @texpert for providing details of their situation to help resolve the issue. Bugfix: gRPC instrumentation causes ArgumentError when other Google gems are present Previously, when the agent had gRPC instrumentation enabled in an application using other gems (such as google-ads-googleads), the instrumentation could cause the error ArgumentError: wrong number of arguments (given 3, expected 2). The gRPC instrumentation has been updated to prevent this issue from occurring in the future. Thank you to @FeminismIsAwesome for bringing this issue to our attention. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 6.5.0.357 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-8101","eolDate":"2023-09-13"},{"agent":"ruby","date":"2022-08-17","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.10.0.gem","version":"8.10.0","features":["Add gRPC instrumentation","Enable code-level metrics functionality by default","Boost performance by defaulting to frozen string literals","Boost performace by reworking timing range overlap calculations for multiple transaction segments"],"bugs":["Identify the config value of transaction_tracer.transaction_threshold correctly","Check if a Logger object is frozen before attempting to modify"],"security":[],"supportedOperatingSystems":null,"description":"v8.10.0 New gRPC instrumentation The agent will now instrument gRPC  activity performed by clients and servers that use the grpc  RubyGem. Instrumentation is automatic and enabled by default, so gRPC users should not need to modify any existing application code or agent configuration to benefit from the instrumentation. The instrumentation makes use of distributed tracing for a comprehensive overview of all gRPC traffic taking place across multiple monitored applications. This allows you to observe your client and server activity using any service that adheres to the W3C standard. The following new configuration parameters have been added for gRPC. All are optional. | Configuration name                   | Default | Behavior                                                                                |\n| ------------------------------------ | ------- | --------------------------------------------------------------------------------------- |\n| instrumentation.grpc_client        | auto    | Set to 'disabled' to disable, set to 'chain' if there are module prepending conflicts   |\n| instrumentation.grpc_server        | auto    | Set to 'disabled' to disable, set to 'chain' if there are module prepending conflicts   |\n| instrumentation.grpc.host_denylist | \"\"      | Provide a comma delimited list of host regex patterns (ex: \"private.com$,exception.*\") | Code-level metrics functionality is enabled by default The code-level metrics functionality for the Ruby agent's CodeStream integration  is now enabled by default after we have received positive feedback and no open bugs for the past two releases. Performance: Rework timing range overlap calculations for multiple transaction segments Many thanks to GitHub community members @bmulholland and @hkdnet. @bmulholland alerted us to rmosolgo/graphql-ruby#3945 . That Issue essentially notes that the New Relic Ruby agent incurs a significant perfomance hit when the graphql RubyGem (which ships with New Relic Ruby agent support) is used with DataLoader to generate a high number of transactions. Then @hkdnet diagnosed the root cause in the Ruby agent and put together both a proof of concept fix and a full blown PR to resolve the problem. The agent keeps track multiple segments that are concurrently in play for a given transaction in order to merge the ones whose start and stop times intersect. The logic for doing this find-and-merge operation has been reworked to a) be deferred entirely until the transaction is ready to be recorded, and b) made more performant when it is needed. GraphQL DataLoader users and other users who generate lots of activity for monitoring within a short amount of time will hopefully see some good performance gains from these changes. Performance: Make frozen string literals the default for the agent The Ruby frozen_string_literal: true magic source code comment has now been applied consistently across all Ruby files belonging to the agent. This can provide a performance boost, given that Ruby can rely on the strings remaining immutable. Previously only about a third of the agent's code was freezing string literals by default. Now that 100% of the code freezes string literals by default, we have internally observed some related performance gains through testing. We are hopeful that these will translate into some real world gains in production capacities. Bugfix: Error when setting the yaml configuration with transaction_tracer.transaction_threshold: apdex_f Originally, the agent was only checking the transaction_tracer.transaction_threshold from the newrelic.yml correctly if it was on two lines. Example: When this was instead changed to be on one line, the agent was not able to correctly identify the value of apdex_f. Example: This would cause prevent transactions from finishing due to the error ArgumentError: comparison of Float with String failed. This has now been corrected and the agent is able to process newrelic.yml with a one line transaction_tracer.transaction_threshold: apdex_f correctly now. Thank you to @oboxodo for bringing this to our attention. Bugfix: Don't modify frozen Logger Previously the agent would modify each instance of the Logger class by adding a unique instance variable as part of the instrumentation. This could cause the error FrozenError: can't modify frozen Logger to be thrown if the Logger instance had been frozen. The agent will now check if the object is frozen before attempting to modify the object. Thanks to @mkcosta for bringing this issue to our attention. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 6.5.0.357 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-8100","eolDate":"2023-08-17"},{"agent":"ruby","date":"2021-10-27","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.1.0.gem","version":"8.1.0","features":["Add instrumentation for Ruby standard library Logger"],"bugs":["Stop deadlocks between New Relic thread and Delayed Job sampling thread","Allow Net::HTTP requests to IPv6 addresses","Fix installation of Padrino instrumentation","Allow integers to be passed to error_collector.ignore_status_codes configuration"],"security":[],"supportedOperatingSystems":null,"description":"v8.1.0 Instrumentation for Ruby standard library Logger The agent will now automatically instrument Logger, recording number of lines and size of logging output, with breakdown by severity. Bugfix for Padrino instrumentation A bug was introduced to the way the agent installs padrino instrumentation in 7.0.0. This release fixes the issues with the padrino instrumentation. Thanks to @sriedel for bringing this issue to our attention. Bugfix: Stop deadlocks between New Relic thread and Delayed Job sampling thread Running the agent's polling queries for the DelayedJobSampler within the same ActiveRecord connection decreases the frequency of deadlocks in development environments. Thanks @jdelStrother for bringing this to our attention and providing excellent sample code to speed up development! Bugfix: Allow Net::HTTP request to IPv6 addresses The agent will no longer raise an URI::InvalidURIError error if an IPv6 address is passed to Net::HTTP. Thank you @tristinbarnett and @tabathadelane for crafting a solution! Bugfix: Allow integers to be passed to error_collector.ignore_status_codes configuration Integers not wrapped in quotation marks can be passed to error_collector.ignore_status_codes in the newrelic.yml file. Our thanks goes to @elaguerta and @brammerl for resolving this issue! Bugfix: allow add_method_tracer to be used on BasicObjects Previously, our add_method_tracer changes referenced self.class which is not available on BasicObjects. This has been fixed. Thanks to @toncid for bringing this issue to our attention. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.4.0.347 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-810","eolDate":"2023-10-27"},{"agent":"ruby","date":"2021-09-22","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-8.0.0.gem","version":"8.0.0","features":["Enable distributed tracing by default","Deprecate Cross Application Tracing and disable by default","Update the default configuration value for span_events.max_samples_stored from 1000 to 2000","Use Module prepending instead of alias_method chaining for add_method_tracer","Add support for ARM64/Graviton2 using Ruby 3.0.2+","Remove previously deprecated method External.start_segment","Remove support for Excon versions below 0.19.0","Remove support for Mongo versions below 2.1","Remove support for Merb"],"bugs":["Load the configuration options error_collector.ignore_messages and error_collector.expected_messages from newrelic.yml correctly"],"security":[],"supportedOperatingSystems":null,"description":"v8.0.0 add_method_tracer refactored to use prepend over alias_method chaining This release overhauls the implementation of add_method_tracer, as detailed in issue #502 . The main breaking updates are as follows: A metric name passed to add_method_tracer will no longer be interpolated in an instance context as before. To maintain this behavior, pass a Proc object with the same arity as the method being traced. For example: Similarly, the :code_header and :code_footer options to add_method_tracer will only  accept a Proc object, which will be bound to the calling instance when the traced method is invoked. Calling add_method_tracer for a method will overwrite any previously defined tracers for that method. To specify multiple metric names for a single method tracer, pass them to add_method_tracer as an array. See updated documentation on the following pages for full details: Ruby Custom Instrumentation: Method Tracers MethodTracer::ClassMethods#add_method_tracer Distributed tracing is enabled by default Distributed tracing  tracks and observes service requests as they flow through distributed systems. Distributed tracing is now enabled by default and replaces cross application tracing . Bugfix: Incorrectly loading configuration options from newrelic.yml The agent will now  import the configuration options error_collector.ignore_messages  and error_collector.expected_messages  from the newrelic.yml file correctly. Cross Application is now deprecated, and disabled by default Distributed tracing  is replacing cross application tracing  as the default means of tracing between services. To continue using it, enable it with cross_application_tracer.enabled: true and distributed_tracing.enabled: false Update configuration option default value for span_events.max_samples_stored from 1000 to 2000 For more information about this congfiguration option, visit the Ruby agent documentation . Agent now enforces server supplied maximum value for configuration option span_events.max_samples_stored Upon connection to the New Relic servers, the agent will now enforce a maximum value allowed for the configuration option span_events.max_samples_stored  sent from the New Relic servers. Remove Ruby 2.0 required kwarg compatibility checks Our agent has code that provides compatibility for required keyword arguments in Ruby versions below 2.1. Since the agent now only supports Ruby 2.2+, this code is no longer required. Replace Time.now with Process.clock_gettime Calls to Time.now have been replaced with calls to Process.clock_gettime to leverage the system's built-in clocks for elapsed time (Process::CLOCK_MONOTONIC) and wall-clock time (Process::CLOCK_REALTIME). This results in fewer object allocations, more accurate elapsed time records, and enhanced performance. Thanks to @sdemjanenko and @viraptor for advocating for this change! Updated generated default newrelic.yml Thank you @wyhaines and @creaturenex for your contribution. The default newrelic.yml that the agent can generate is now updated with commented out examples of all configuration options. Bugfix: Psych 4.0 causes errors when loading newrelic.yml Psych 4.0 now uses safe load behavior when using YAML.load which by default doesn't allow aliases, causing errors when the agent loads the config file. We have updated how we load the config file to avoid these errors. Remove support for Excon versions below 0.19.0 Excon versions below 0.19.0 will no longer be instrumented through the Ruby agent. Remove support for Mongo versions below 2.1 Mongo versions below 2.1 will no longer be instrumented through the Ruby agent. Remove tests for Rails 3.0 and Rails 3.1 As of the 7.0 release, the Ruby agent stopped supporting Rails 3.0 and Rails 3.1. Despite this, we still had tests for these versions running on the agent's CI. Those tests are now removed. Update test Gemfiles for patched versions The gem has individual Gemfiles it uses to test against different common user setups. Rails 5.2, 6.0, and 6.1 have been updated to the latest patch versions in the test Gemfiles. Rack was updated in the Rails61 test suite to 2.1.4 to resolve a security vulnerability. Remove Merb Support This release removes the remaining support for the Merb  framework. It merged with Rails during the 3.0 release. Now that the Ruby agent supports Rails 3.2 and above, we thought it was time to say goodbye. Remove deprecated method External.start_segment The method NewRelic::Agent::External.start_segment has been deprecated as of Ruby Agent 6.0.0. This method is now removed. Added testing and support for the following gem versions activemerchant 1.121.0 bunny 2.19.0 excon 0.85.0 mongo 2.14.0, 2.15.1 padrino 0.15.1 resque 2.1.0 sequel 5.48.0 yajl-ruby 1.4.1 This version adds support for ARM64/Graviton2 platform using Ruby 3.0.2+ Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.4.0.347 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-800","eolDate":"2023-09-22"},{"agent":"ruby","date":"2021-07-02","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-7.2.0.gem","version":"7.2.0","features":["Add configuration options for expected/ignored errors by class name, status code, and message"],"bugs":["Add logic to avoid conflicts with use of Module#Prepend","Fix kwarg support for Rack middleware instrumentation","Resolve error when adding a new key into hash during iteration"],"security":[],"supportedOperatingSystems":null,"description":"v7.2.0 Expected Errors and Ignore Errors \nThis release adds support for configuration of expected/ignored errors by class name, status code, and message. The following configuration options are now available: error_collector.ignore_classes error_collector.ignore_messages error_collector.ignore_status_codes error_collector.expected_classes error_collector.expected_messages error_collector.expected_status_codes\nFor more details about expected and ignored errors, please see our configuration documentation Bugfix: resolves \"can't add a new key into hash during iteration\" Errors Thanks to @wyhaines for this fix that prevents \"can't add a new key into hash during iteration\" errors from occuring when iterating over environment data. Bugfix: kwarg support fixed for Rack middleware instrumentation Thanks to @walro for submitting this fix. This fixes the rack instrumentation when using kwargs. Update known conflicts with use of Module#Prepend With our release of v7.0.0, we updated our instrumentation to use Module#Prepend by default, instead of method chaining. We have received reports of conflicts and added a check for these known conflicts. If a known conflict with prepend is detected while using the default value of 'auto' for gem instrumentation, the agent will instead install method chaining instrumentation in order to avoid this conflict. This check can be bypassed by setting the instrumentation method for the gem to 'prepend'. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.2.0.345 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-720","eolDate":"2023-07-02"},{"agent":"ruby","date":"2021-05-28","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-7.1.0.gem","version":"7.1.0","features":["Allow distributed tracing to be set in server-side application configuration","Add support for the Browser agent to run on applications using CSP nonces","Add support for the agent to run in FIPS compliant environments"],"bugs":["Fix conflicts with use of Module#Prepend","Display spans correctly for ActiveRecord 6.1+ instrumentation","Fix nil Middlewares injection error for Sinatra","Fix agent support when running in a non-forking Resque worker process","Fix support for the use of **kwargs in Ruby 3+"],"security":[],"supportedOperatingSystems":null,"description":"v7.1.0 Add support for CSP nonces when using our API to insert the Browser agent We now support passing in a nonce to our API method browser_timing_header to allow the Browser agent to run on applications using CSP nonces. This allows users to inject the Browser agent themselves and use the nonce required for the script to run. In order to utilize this new feature, you must disable auto instrumentation for the Browser agent, and use the API method browser_timing_header to pass the nonce in and inject the script manually. Removed MD5 use in the SQL sampler In order to allow the agent to run in FIPS compliant environments, the usage of MD5 for aggregating slow sql traces has been replaced with SHA1. Enable server-side configuration of distributed tracing distributed_tracing.enabled may now be set in server-side application configuration. Bugfix: Fix for missing part of a previous bugfix Our previous fix of \"nil Middlewares injection now prevented and gracefully handled in Sinatra\" released in 7.0.0 was partially overwritten by some of the other changes in that release. This release adds back those missing sections of the bugfix, and should resolve the issue for Sinatra users. Update known conflicts with use of Module#Prepend With our release of v7.0.0, we updated our instrumentation to use Module#Prepend by default, instead of method chaining. We have received reports of conflicts and added a check for these known conflicts. If a known conflict with prepend is detected while using the default value of 'auto' for gem instrumentation, the agent will instead install method chaining instrumentation in order to avoid this conflict. This check can be bypassed by setting the instrumentation method for the gem to 'prepend'. Bugfix: Updated support for ActiveRecord 6.1+ instrumentation Previously, the agent depended on connection_id to be present in the Active Support instrumentation for sql.active_record\nto get the current ActiveRecord connection. As of Rails 6.1, connection_id has been dropped in favor of providing the connection\nobject through the connection value exclusively. This resulted in datastore spans displaying fallback behavior, including showing\n\"ActiveRecord\" as the database vendor. Bugfix: Updated support for Resque's FORK_PER_JOB option Support for Resque's FORK_PER_JOB flag within the Ruby agent was incomplete and nonfunctional. The agent should now behave\ncorrectly when running in a non-forking Resque worker process. Bugfix: Added check for ruby2_keywords in add_transaction_tracer Thanks @beauraF for the contribution! Previously, the add_transaction_tracer was not updated when we added support for ruby 3. In order to correctly support **kwargs,  ruby2_keywords was added to correctly update the method signature to use **kwargs in ruby versions that support that. Confirmed support for yajl 1.4.0 Thanks to @creaturenex for the contribution! yajl-ruby 1.4.0 was added to our test suite and confirmed all tests pass, showing the agent supports this version as well. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.2.0.345 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-710","eolDate":"2023-05-28"},{"agent":"ruby","date":"2021-04-23","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-7.0.0.gem","version":"7.0.0","features":["Drop support for Ruby 2.0 and 2.1","Remove previously deprecated config options, API methods, and attribute","Remove support for Rails 3.0 and 3.1","Add support for prepend auto-instrumentation strategies for most Ruby gems/libraries"],"bugs":["Make transaction nesting max depth consistent with length of segments"],"security":["Remove SSL cert bundle"],"supportedOperatingSystems":null,"description":"v7.0.0 Ruby Agent 6.x to 7.x Migration Guide Available Please see our Ruby Agent 6.x to 7.x migration guide  for helpful strategies and tips for migrating from earlier versions of the Ruby agent to 7.0.0.  We cover new configuration settings, diagnosiing and installing SSL CA certificates and deprecated items and their replacements in this guide. Ruby 2.0 and 2.1 dropped Support for Ruby 2.0 and 2.1 dropped with this release.  We do not know of code changes that would prevent the agent from continuing to\nwork with these releases.  However, Rubies 2.0 and 2.1 are no longer included in our test matrices and are not supported for 7.0.0 and onward. Implemented prepend auto-instrumentation strategies for most Ruby gems/libraries This release brings the auto-instrumentation strategies for most gems into the modern era for Ruby by providing both\nprepend and method-chaining (also known as method-aliasing) strategies for auto instrumenting.  Prepend, which has been available since\nRuby 2.0, is now the default strategy employed in auto-instrumenting. It's a known issue that some external gems lead to Stack Level too Deep exceptions when prepend and method-chaining are mixed. In such known cases, the auto-instrumenting strategy will fall back to method-chaining automatically. This release also deprecates many overlapping and inconsistently named configuration settings in favor of being able to control\nbehavior of instrumentation per library with one setting that can be one of auto (the default), disabled, prepend, or chain. Please see the above-referenced migration guide for further details. Removed SSL cert bundle The agent will no longer ship this bundle and will rely on system certs. Removed deprecated config options The following config options were previously deprecated and are no longer available: disable_active_record_4 disable_active_record_5 autostart.blacklisted_constants autostart.blacklisted_executables autostart.blacklisted_rake_tasks strip_exception_messages.whitelist Removed deprecated attribute The attribute httpResponseCode was previously deprecated and replaced with http.statusCode. This deprecated attribute has now been removed. Removed deprecated option in notice_error Previously, the :trace_only option to NewRelic::Agent.notice_error was deprecated and replaced with :expected. This deprecated option has been removed. Removed deprecated API methods Previously the API methods create_distributed_trace_payload and accept_distributed_trace_payload were deprecated. These have now been removed. Instead, please see insert_distributed_trace_headers and accept_distributed_trace_headers, respectively. Bugfix: Prevent browser monitoring middleware from installing to middleware multiple times In rare cases on jRuby, the BrowserMonitoring middleware could attempt to install itself\nmultiple times at start up.  This bug fix addresses that by using a mutex to introduce\nthread safety to the operation.  Sinatra in particular can have this race condition because\nits middleware stack is not installed until the first request is received. Skip constructing Time for transactions Thanks to @viraptor, we are no longer constructing an unused Time object with every call to starting a new Transaction. Bugfix: nil Middlewares injection now prevented and gracefully handled in Sinatra Previously, the agent could potentially inject multiples of an instrumented middleware if Sinatra received many\nrequests at once during start up and initialization due to Sinatra's ability to delay full startup as long as possible.\nThis has now been fixed, and the Ruby agent correctly instruments only once as well as gracefully handles nil middleware\nclasses in general. Bugfix: Ensure transaction nesting max depth is always consistent with length of segments Thanks to @warp for noticing and fixing the scenario where Transaction nesting_max_depth can get out of sync\nwith segment length resulting in an exception when attempting to nest the initial segment which does not exist. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 4.8.0 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-700","eolDate":"2023-04-23"},{"agent":"ruby","date":"2020-02-20","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.9.0.363.gem","version":"6.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Relic Ruby Agent Release Notes Added support for W3C Trace Context, with easy upgrade from New Relic trace context Distributed tracing now supports W3C Trace Context headers  for HTTP protocols when distributed tracing is enabled. Our implementation can accept and emit both the W3C trace header format and the New Relic trace header format. This simplifies agent upgrades, allowing trace context to be propagated between services with older and newer releases of New Relic agents. W3C trace header format will always be accepted and emitted. New Relic trace header format will be accepted, and you can optionally disable emission of the New Relic trace header format. When distributed tracing is enabled by setting distributed_tracing.enabled to true, the Ruby agent will now accept W3C's traceparent and tracestate headers when calling DistributedTracing.accept_distributed_trace_headers or automatically via http instrumentation. When calling DistributedTracing.insert_distributed_trace_headers, or automatically via http instrumentation, the Ruby agent will include the W3C headers along with the New Relic distributed tracing header, unless the New Relic trace header format is disabled by setting exclude_newrelic_header setting to true. Added DistributedTracing.accept_distributed_trace_headers API for accepting both New Relic and W3C TraceContext distributed traces. Deprecated DistributedTracing.accept_distributed_trace_payload which will be removed in a future major release. Added DistributedTracing.insert_distributed_trace_headers API for adding outbound distributed trace headers. Both W3C TraceContext and New Relic formats will be included unless distributed_tracing.exclude_newrelic_header: true. Deprecated DistributedTracing.create_distributed_trace_payload which will be removed in a future major release. Known issues and workarounds: If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream Ruby New Relic agents to this agent release. Official Ruby 2.7 support The Ruby agent has been verified to run with Ruby 2.7.0. Reduced allocations when tracing transactions using API calls Default empty hashes for options parameter were not frozen, leading to excessive and unnecessary allocations when calling APIs for tracing transactions. Thanks to Joel Turkel (jturkel) for the contribution! Bugfix for Resque worker thread race conditions Recent changes in Rack surfaced issues marshalling data for Resque, surfaced a potential race-condition with closing out the worker-threads before flushing the data pipe. This is now fixed. Thanks to Bertrand Paquet (bpaquet) for the contribution! Bugfix for Content-Length when injecting browser monitoring JS The Content-Length HTTP header would be incorrect after injecting the browser monitoring JS into the HEAD tag of the HTML source with Content-Length and lead to the HTML BODY content being truncated in some cases. The Content-Length is now correctly updated after injecting the browser monitoring JS script. Thanks to Slava Kardakov (ojab) for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-690363","eolDate":"2023-02-20"},{"agent":"ruby","date":"2019-12-30","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.8.0.360.gem","version":"6.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v6.8.0 Initial Ruby 2.7 support The Ruby agent has been verified to run with Ruby 2.7.0-preview1. New API method to add custom attributes to Spans New API method for adding custom attributes to spans . Previously, custom attributes were only available at the Transaction level. Now, with Span level custom attributes, more granular tagging is possible for easier isolation and review of traces. For more information: Agent#add_custom_span_attributes Enables ability to migrate to configurable security policies (CSP) on a per-agent basis for accounts already using high-security mode (HSM). When both HSM  and CSP  are enabled for an account, an agent (this version or later) can successfully connect with either high_security: true or the appropriate security_policies_token configured. high_security has been added as part of the preconnect payload. Bugfix for logs-in-context combined with act-fluent-logger-rails Previously, when using the Ruby agent's logs-in-context logger to link logging data with trace and entity metadata for an improved experience in the UI, customers who were also using the act-fluent-logger-rails gem would see a NoMethodError for clear_tags! that would interfere with the use of this feature. This error no longer appears, allowing customers to combine the use of logs-in-context with the use of this gem. Please note that the logs-in-context logger does not support tagged logging; if you are initializing your logger with a log_tags argument, your custom tags may not appear on the final version of your logs. Bugfix for parsing invalid newrelic.yml Previously, if the newrelic.yml configuration file was invalid, and the agent could not start as a result, the agent would not log any indication of the problem. This version of the agent will emit a FATAL message to STDOUT when this scenario occurs so that customers can address issues with newrelic.yml that prevent startup. Configuration options containing the terms \"whitelist\" and \"blacklist\" deprecated The following local configuration settings have been deprecated: autostart.blacklisted_constants: use autostart.denylisted_constants instead. autostart.blacklisted_executables: use autostart.denylisted_executables instead. autostart.blacklisted_rake_tasks: use autostart.denylisted_rake_tasks instead. strip_exception_messages.whitelist: use strip_exception_messages.allowed_classes instead. Bugfix for module loading and constant resolution in Rails Starting in version 6.3, the Ruby agent has caused module loading and constant resolution to sometimes fail, which caused errors in some Rails applications. These errors were generally NoMethodError exceptions or I18n errors translation missing or invalid locale. These errors would not appear if the agent was removed from the application's Gemfile. This version of the agent fixes these issues with module loading and constant resolution, so these errors no longer occur. Bugfix: failed to get urandom Previous versions of the agent would fail unexpectedly when the Ruby process used every available file descriptor. The failures would include this message: This version of the agent uses a different strategy for generating random IDs, and will not fail in the same way when no file descriptors are available.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-680360","eolDate":"2022-12-30"},{"agent":"ruby","date":"2019-10-01","downloadLink":null,"version":"6.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v6.7.0 Support for Real Time Streaming Event data is now sent to New Relic every five seconds, instead of every minute. As a result, transaction, error, and custom events will now be available in New Relic and Insights dashboards in near real time. For more information on how to view your events with a five-second refresh, see the real time streaming documentation . Note that the overall limits on how many events can be sent per minute have not changed. Also, span events, metrics, and trace data is unaffected, and will still be sent every minute. Trace and Entity Metadata API Several new API methods have been added to the agent: Agent#linking_metadata Tracer#trace_id Tracer#span_id Tracer#sampled? These API methods allow you to access information that can be used to link data of your choosing to a trace or entity. Logs in Context This version of the agent includes a logger, which can be used in place of ::Logger from the standard library, or ActiveSupport::Logger from Rails. This logger leverages the new trace and entity metadata API to decorate log statements with entity and trace metadata, so they can be correlated together in the New Relic UI. For more information on how to use logs in context, see https://docs.newrelic.com/docs/enable-logs-context-ruby Project metadata in Gemspec Project metadata has been added to the gemspec file. This means our Rubygems page will allow users to more easily access the agent's source code, raise issues, and read the changelog. Thanks to Orien Madgwick for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-670359","eolDate":"2022-10-01"},{"agent":"ruby","date":"2019-09-05","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.6.0.358.gem","version":"6.6.0.358","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v6.6.0 Bugfix for ActionCable Instrumentation Previous versions of the agent sometimes caused application crashes with some versions of ActionCable. The application would exit quickly after startup with the error: uninitialized constant ActionCable::Engine. Version 6.6.0 of the agent no longer crashes in this way. Handling of disabling Error Collection When the agent first starts, it begins collecting Error Events and Traces before fetching configuration from New Relic. In previous versions of the agent, those events or traces would be sent to New Relic, even if Error Collection  is disabled in the application's server-side configuration. Version 6.6.0 of the agent drops all collected Error Events and Traces if the configuration from the server disables Error Collection .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-660358","eolDate":"2022-09-05"},{"agent":"ruby","date":"2019-06-26","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.5.0.356.gem","version":"6.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Change to default setting for ActiveRecord connection resolution Due to incompatibilities between the faster ActiveRecord connection resolution released in Ruby agent v6.3.0 and other gems that patch ActiveRecord, backport_fast_active_record_connection_lookup will now be set to false by default. This will result in significant performance improvement. Recommendation:  If your environment includes ActiveRecord, change this setting to true. Exception:  If you are using other gems that measure ActiveRecord performance, they may lose functionality when combined with this setting. If you are unsure whether to enable backport_fast_active_record_connection_lookup, we recommend enabling it in a development environment to make sure other gems that patch ActiveRecord are still working as expected. Fixes Bugfix for ActiveStorage instrumentation error Version 6.4.0 of the agent introduced a bug that interfered with ActiveStorage callbacks, resulting in the agent being unable to instrument ActiveStorage operations. ActiveStorage segments are now correctly recorded. Bugfix for ActiveRecord 4.1 and 4.2 exception logging Version 6.3.0 of the agent introduced a bug that prevented ActiveRecord versions 4.1 and 4.2 from logging exceptions that occurred within a database transaction. This version of the agent restores the exception logging functionality from previous agent versions. Thanks to Oleksiy Kovyrin for the contribution! Notes The Ruby agent now enforces a maximum of 10,000 transaction events  and custom events  and 100 error events  per minute.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-650357","eolDate":"2022-06-26"},{"agent":"ruby","date":"2019-05-28","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.4.0.356.gem","version":"6.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v6.4.0 Custom Metadata Collection The agent now collects environment variables prefixed by NEW_RELIC_METADATA_. These may be added to transaction events to provide context between your Kubernetes cluster and your services. For details on the behavior, see this blog post . Bugfix for faster ActiveRecord connection resolution Version 6.3.0 of the agent backported the faster ActiveRecord connection resolution from Rails 6.0 to previous versions, but the implementation caused certain other gems which measured ActiveRecord performance to stop working. This version of the agent changes the implementation of this performance improvement so no such conflicts occur. Bugfix for Grape instrumentation error Previous versions of the agent would fail to install Grape instrumentation in Grape versions 1.2.0 and up if the API being instrumented subclassed Grape::API::Instance rather than Grape::API. A warning would also print to the newrelic_agent log: This version of the agent successfully installs instrumentation for subclasses of Grape::API::Instance, and these log messages should no longer appear. Bugfix for streaming responses Previous versions of the agent would attempt to insert JavaScript instrumentation into any streaming response that did not make use of ActionController::Live. This resulted in an empty, non-streamed response being sent to the client. This version of the agent will not attempt to insert JavaScript instrumentation into a response which includes the header Transfer-Encoding=chunked, which indicates a streaming response. This should exclude JavaScript instrumentation for all streamed responses. To include this instrumentation manually, see Manually instrument via agent API  in our documentation.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-640356","eolDate":"2022-05-28"},{"agent":"ruby","date":"2019-04-30","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.3.0.355.gem","version":"6.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v6.3.0 Official Rails 6.0 support This version of the agent has been verified against the Rails 6.0.0 release. As ActiveRecord 4, 5, and 6 use the same New Relic instrumentation, the disable_active_record_4 and disable_active_record_5 settings in NewRelic.yml are being deprecated in favor of the new disable_active_record_notifications. This new setting will affect the instrumentation of ActiveRecord 4, 5, and 6. The deprecated settings will be removed in a future release. Bugfix for newrelic deployments script For applications housed in the EU, the newrelic deployments script included with previous versions of the agent would fail with the following message: Deployment not recorded: Application does not exist. This is because the script would attempt to send the deployment notification to the US region. The deployment script now sends deployments to the correct region. Faster ActiveRecord connection resolution This version of the agent uses the faster ActiveRecord connection resolution that Rails 6.0 uses, even on previous versions of Rails. Thanks to Callum Jones for the contribution! Support non-ascii characters in hostnames Previous versions of the agent would frequently log warnings like: log writing failed. \"\\xE2\" from ASCII-8BIT to UTF-8 if the hostname contained a non-ascii character. This version of the agent will no longer log these warnings. Thanks to Rafael Petry for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-630355","eolDate":"2022-04-30"},{"agent":"ruby","date":"2019-03-18","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.2.0.354.gem","version":"6.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v6.2.0 Bugfix for superfluous Empty JSON response error messages Version 6.1.0 of the agent frequently logged error messages about an empty JSON response, when no error had occurred. These logs no longer appear. Bugfix for Unable to calculate elapsed transaction time warning messages Ruby Agent versions 5.4 through 6.1, when running in jruby without ObjectSpace enabled, would occasionally log a warning indicating that the agent was unable to calculate the elapsed transaction time. When this log statement appeared, the affected transactions would not be included in the data displayed on the capacity analysis page. These transactions are now correctly recorded.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-620354","eolDate":"2022-03-18"},{"agent":"ruby","date":"2021-01-19","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.15.0.gem","version":"6.15.0","features":["Add support for Ruby 3.0","Add support for Rails 6.1","Add support for Sidekiq 6.0, 6.1","Add force_install_exit_handler config flag"],"bugs":["Stop overwriting Sidekiq trace data in distributed tracing","Report errors correctly for spans with no other attributes","Record DistributedTracing.insert_distributed_trace_headers supportability metric"],"security":[],"supportedOperatingSystems":null,"description":"v6.15.0 Official Ruby 3.0 support The Ruby agent has been verified to run on Ruby 3.0.0. Added support for Rails 6.1 The Ruby agent has been verified to run with Rails 6.1. Special thanks to @hasghari for setting this up! Added support for Sidekiq 6.0, 6.1 The Ruby agent has been verified to run with both 6.0 and 6.1 versions of sidekiq. Bugfix: No longer overwrites sidekiq trace data Distributed tracing data is now added to the job trace info rather than overwriting the existing data. Bugfix: Fixes cases where errors are reported for spans with no other attributes Previously, in cases where a span does not have any agent/custom attributes on it, but an error is noticed and recorded against the span, a FrozenError: can't modify frozen Hash is thrown. This is now fixed, and errors are now correctly recorded against such span events. Bugfix: DistributedTracing.insert_distributed_trace_headers Supportability metric now recorded Previously, API calls to DistributedTracing.insert_distributed_trace_headers would lead to an exception about the missing supportability metric rather than flowing through the API implementation as intended. This would potentially lead to broken distributed traces, as the trace headers were not inserted on the API call. DistributedTracing.insert_distributed_trace_headers now correctly records the supportability metric and inserts the distributed trace headers as intended. Bugfix: child completions after parent completes sometimes throws exception attempting to access nil parent In scenarios where the child segment/span is completing after the parent in jRuby, the parent may have already been freed and no longer accessible. This would lead to attempting to calll descendant_complete on a nil object. This is fixed to protect against calling the descendant_complete in these cases. Feature: implements force_install_exit_handler config flag The force_install_exit_handler configuration flag allows an application to instruct the agent to install its graceful shutdown exit handler. This sends any locally cached data to the New Relic collector before the application shuts down. This is useful when the primary framework has an embedded Sinatra application that is otherwise detected and skips installing the exit hook for graceful shutdowns. Default prepend_net_instrumentation to false Previously, prepend_net_instrumentation defaulted to true. However, many gems are still using monkey patching on Net::HTTP, which causes compatibility issues with using prepend. Defaulting this to false minimizes instances of unexpected compatibility issues. Infinite tracing adds additional data to connection metadata Adds data from the agents connect response request_headers_map to the metadata for the connection to the infinite trace observer. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 4.8.0 .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-6150","eolDate":"2023-01-19"},{"agent":"ruby","date":"2020-11-17","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.13.1.gem","version":"6.14.0","features":["Add prepend implementation of Net::HTTP instrumentation","Recognize memory sampler in macOS Big Sur","Capture incoming and outgoing distributed tracing request headers"],"bugs":["Fix Delayed Job instrumentation for Ruby 2.7+","Fix compiler warnings for Ruby 2.7+","Fix Rack instrumentation behavior for Ruby 2.7+","Add newrelic.yml.erb to the configuration search path","Don't raise a dependency detection exception for Redis","Gracefully handle NilClass as a Middleware Class when instrumenting"],"security":[],"supportedOperatingSystems":null,"description":"v6.14.0 Bugfix: Method tracers no longer cloning arguments Previously, when calling add_method_tracer with certain combination of arguments, it would lead to the wrapped method's arguments being cloned rather than passed to the original method for manipulation as intended. This has been fixed. Bugfix: Delayed Job instrumentation fixed for Ruby 2.7+ Previously, the agent was erroneousy separating positional and keyword arguments on the instrumented method calls into Delayed Job's library. The led to Delayed job not auto-instrumenting correctly and has been fixed. Bugfix: Ruby 2.7+ methods sometimes erroneously attributed compiler warnings to the Agent's add_method_tracer The specific edge cases presented are now fixed by this release of the agent. There are still some known corner-cases that will be resolved with upcoming changes in next major release of the Agent. If you encounter a problem with adding method tracers and compiler warnings raised, please continue to submit small repoducible examples. Bugfix: Ruby 2.7+ fix for keyword arguments on Rack apps is unnecessary and removed A common fix for positional and keyword arguments for method parameters was implemented where it was not needed and led to RackApps getting extra arguments converted to keyword arguments rather than Hash when it expected one. This Ruby 2.7+ change was reverted so that Rack apps behave correctly for Ruby >= 2.7. Feature: captures incoming and outgoing request headers for distributed tracing HTTP request headers will be logged when log level is at least debug level. Similarly, request headers for exchanges with New Relic servers are now audit logged when audit logging is enabled. Bugfix: newrelic.yml.erb added to the configuration search path Previously, when a user specifies a newrelic.yml.erb and no newrelic.yml file, the agent fails to find the .erb file because it was not in the list of files searched at startup. The Ruby agent has long supported this as a means of configuring the agent programatically. The newrelic.yml.erb filename is restored to the search path and will be utilized if present. NOTE: newrelic.yml still takes precedence over newrelic.yml.erb If found, the .yml file is used instead of the .erb file. Search directories and order of traversal remain unchanged. Bugfix: dependency detection of Redis now works without raising an exception Previously, when detecting if Redis was available to instrument, the dependency detection would fail with an Exception raised (with side effect of not attempting to instrument Redis). This is now fixed with a better dependency check that resolves falsly without raising an Exception. Bugfix: Gracefully handles NilClass as a Middleware Class when instrumenting Previously, if a NilClass is passed as the Middleware Class to instrument when processing the middleware stack, the agent would fail to fully load and instrument the middleware stack. This fix gracefully skips over nil classes. Memory Sampler updated to recognize macOS Big Sur Previously, the agent was unable to recognize the platform macOS Big Sur in the memory sampler, resulting in an error being logged. The memory sampler is now able to recognize Big Sur. Prepend implementation of Net::HTTP instrumentation available There is now a config option (prepend_net_instrumentation) that will enable the agent to use prepend while instrumenting Net::HTTP. This option is set to true by default. Support Statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 4.5.0.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-6140","eolDate":"2022-11-17"},{"agent":"ruby","date":"2020-09-25","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.13.1.gem","version":"6.13.1","features":[],"bugs":["Don't modity original URI when obfuscating URLs to external services"],"security":[],"supportedOperatingSystems":null,"description":"v6.13.1 Bugfix: obfuscating URLs to external services no longer modifying original URI A recent change to the Ruby agent to obfuscate URIs sent to external services had the unintended side-effect of removing query parameters from the original URI. This is fixed to obfuscate while also preserving the original URI. Thanks to @VictorJimenezKwast for pinpointing and helpful unit test to demonstrate.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-6131","eolDate":"2023-09-25"},{"agent":"ruby","date":"2020-09-08","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.13.0.gem","version":"6.13.0","features":[],"bugs":["Use correct host for calls to preconnect","Don't modify caller params when calling add_custom_attributes","Obfuscate http.url query param spans","Reduce allocations for segment attributes","Eliminate errors around Rake::VERSION with Rails","Prevent connecting agent thread from hanging on shutdown","Fix error messages about Rake instrumentation"],"security":["Use system SSL certificates by default"],"supportedOperatingSystems":null,"description":"v6.13.0 Bugfix: never use redirect host when accessing preconnect endpoint When connecting to New Relic, the Ruby Agent uses the value in Agent.config[:host] to post a request to the New Relic preconnect endpoint. This endpoint returns a \"redirect host\" which is the URL to which agents send data from that point on. Previously, if the agent needed to reconnect to the collector, it would incorrectly use this redirect host to call the preconnect endpoint, when it should have used the original configured value in Agent.config[:host]. The agent now uses the correct host for all calls to preconnect. Bugfix: calling add_custom_attributes no longer modifies the params of the caller The previous agent's improvements to recording attributes at the span level had an unexpected side-effect of modifying the params passed to the API call as duplicated attributes were deleted in the process. This is now fixed and params passed in are no longer modified. Thanks to Pete Johns (@johnsyweb) for the PR that resolves this bug. Bugfix: http.url query parameters spans are now obfuscated Previously, the agent was recording the full URL of the external requests, including the query and fragment parts of the URL as part of the attributes on the external request span. This has been fixed so that the URL is obfuscated to filter out potentially sensitive data. Use system SSL certificates by default The Ruby agent previously used a root SSL/TLS certificate bundle by default. Now the agent will attempt to use the default system certificates, but will fall back to the bundled certs if there is an issue (and log that this occurred). Bugfix: reduce allocations for segment attributes Previously, every segment received an Attributes object on initialization. The agent now lazily creates attributes on segments, resulting in a significant reduction in object allocations for a typical transaction. Bugfix: eliminate errors around Rake::VERSION with Rails When running a Rails application with rake tasks, customers could see the following error: Prevent connecting agent thread from hanging on shutdown A bug in Net::HTTP's Gzip decoder can cause the (un-catchable) thread-kill exception to be replaced with a (catchable) Zlib exception, which prevents a connecting agent thread from exiting during shutdown, causing the Ruby process to hang indefinitely. This workaround checks for an aborting thread in the #connect exception handler and re-raises the exception, allowing a killed thread to continue exiting. Thanks to Will Jordan (@wjordan) for chasing this one down and patching with tests. Fix error messages about Rake instrumentation When running a Rails application with rake tasks, customers could see the following error in logs resulting from a small part of rake functionality being loaded with the Rails test runner: Such error messages should no longer appear in this context. Thanks to @CamilleDrapier for pointing out this issue. Remove NewRelic::Metrics The NewRelic::Metrics module has been removed from the agent since it is no longer used. Thanks to @csaura for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-6130","eolDate":"2023-09-08"},{"agent":"ruby","date":"2020-07-13","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.12.0.367.gem","version":"6.12.0","features":["Apply additional transaction information to Spans","Auto-instrument Mongo 2.6 - 2.12","Deprecate agent attribute httpResponseCode"],"bugs":["Capture Content-Length header in middleware tracing correctly","Handle MongoDB CommandFailed events","Fix priority sampling buffer for high-throughput environments"],"security":["Update all uses of Rake to 12.3.3+","Recommend review of include and exclude Transaction attributes"],"supportedOperatingSystems":null,"description":"New Relic Ruby Agent Release Notes v6.12.0 The New Relic Ruby agent is now open source under the Apache 2 license  and you can now observe the project roadmap. See our Contributing guide  and Code of Conduct  for details on contributing! Security: Updated all uses of Rake to >= 12.3.3 All versions of Rake testing prior to 12.3.3 were removed to address CVE-2020-8130 . No functionality in the agent was removed nor deprecated with this change, and older versions of rake are expected to continue to work as they have in the past. However, versions of rake < 12.3.3 are no longer tested nor supported. Bugfix: fixes an error capturing content length in middleware on multi-part responses In the middleware tracing, the Content-Length header is sometimes returned as an array of values when content is a multi-part response. Previously, the agent would fail with \"NoMethodError: undefined method to_i for Array\" Error. This bug is now fixed and multi-part content lengths are summed for a total when an Array is present. Added support for auto-instrumenting Mongo gem versions 2.6 to 2.12 Bugfix: MongoDB instrumentation did not handle CommandFailed events when noticing errors The mongo gem sometimes returns a CommandFailed object instead of a CommandSucceeded object with error attributes populated. The instrumentation did not handle noticing errors on CommandFailed objects and resulted in logging an error and backtrace to the log file. Additionally, a bug in recording the metric for \"findAndModify\" as all lowercased \"findandmodify\" for versions 2.1 through 2.5 was fixed. Bugfix: Priority Sampler causes crash in high throughput environments in rare cases Previously, the priority sampling buffer would, in rare cases, generate an error in high-throughput environments once capacity is reached and the sampling algorithm engages. This issue is fixed. Additional transaction information applied to Spans When distributed tracing and/or Infinite Tracing are enabled, the agent will now incorporate additional information from the Transaction event on to the root Span of the transaction. The following items are affected: Custom attribute values applied to the Transaction via our add_custom_attributes  API method. Request parameters: request.parameters.* Request headers: request.headers.* Response headers: response.headers.* Resque job arguments: job.resque.args.* Sidekiq job arguments: job.sidekiq.args.* Messaging arguments: message.* httpResponseCode (deprecated in this version; see note below)/http.statusCode response.status request.uri request.method host.displayName Security recommendation Review your Transaction attributes include  and exclude  configurations. Any attribute include or exclude settings specific to Transaction events should be applied to your Span attributes include  and exclude  configuration or your global attributes include  and exclude  configuration. Agent attribute deprecation: httpResponseCode Starting in this agent version, the agent attribute  httpResponseCode (string value) has been deprecated. Customers can begin using http.statusCode (integer value) immediately, and httpResponseCode will be removed in the agent's next major version update. Bugfix: Eliminate warnings for distributed tracing when using sidekiq Previously, using sidekiq with distributed tracing disabled resulted in warning messages\\ WARN : Not configured to accept distributed trace headers\\ WARN : Not configured to insert distributed trace headers\\ These messages no longer appear.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-6120367","eolDate":"2023-07-13"},{"agent":"ruby","date":"2020-06-03","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.10.0.364.gem","version":"6.11.0","features":["Introduce Infinite Tracing","Add distributed tracing for Sidekiq jobs"],"bugs":["Support Rails 6.1+ in the Environment Report","Eliminate add_method_tracer warnings when using Ruby 2.7","Add missing field to Cross Application Tracing"],"security":[],"supportedOperatingSystems":null,"description":"New Relic Ruby Agent Release Notes v6.11.0 Infinite Tracing This release adds support for Infinite Tracing . Infinite Tracing observes 100% of your distributed traces and provides visualizations for the most actionable data. With Infinite Tracing, you get examples of errors and long-running traces so you can better diagnose and troubleshoot your systems. Configure your agent to send traces to a trace observer in New Relic Edge. View distributed traces through New Relic’s UI. There is no need to install a collector on your network. Infinite Tracing is currently available on a sign-up basis. If you would like to participate, please contact your sales representative. Bugfix: Cross Application Tracing (CAT) adds a missing field to response Previously, the CAT header was missing a reserved field that would lead to an error in the Go Agent's processing of incoming headers from the Ruby Agent. This fix adds that missing field to the headers. Bugfix: Environment Report now supports Rails >= 6.1 The API changed for how database connections are accessed in Rails versions starting with 6.1 to support multiple database feature. The Environment report was enhanced to use the Rails >= 6.1 API with fallback to old API when that fails. Thanks to Sébastien Dubois (sedubois) for reporting this issue and contribution! Bugfix: Eliminate warnings appearing when using add_method_tracer with Ruby 2.7 Previously, using add_method_tracer with Ruby 2.7 to trace a method that included keyword arguments resulted in warning messages: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call. These messages no longer appear. Thanks to Harm de Wit and Atsuo Fukaya for reporting the issue! Added distributed tracing to Sidekiq jobs Thanks to andreaseger for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-6110365","eolDate":"2023-06-03"},{"agent":"ruby","date":"2019-02-26","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.1.0.352.gem","version":"6.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v6.1.0 Performance monitoring on Kubernetes This release adds Transaction event attributes that provide context between your Kubernetes cluster and services. For details on the benefits, see this blog post . Bugfix for Bunny instrumentation when popping empty queues When a customer calls Bunny::Queue#pop on an empty queue, Bunny returns a nil value. Previous Ruby Agent versions raised a NoMethodError when trying to process this result. Now, the agent correctly skips processing for nil values. Thanks to Matt Campbell for the contribution.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-610352","eolDate":"2022-02-26"},{"agent":"ruby","date":"2020-04-08","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.10.0.364.gem","version":"6.10.0","features":["Include error attributes on spans with an error or exception"],"bugs":["Calculate Content-Length HTTP header correctly"],"security":[],"supportedOperatingSystems":null,"description":"New Relic Ruby Agent Release Notes Error attributes now added to each span that exits with an error or exception Error attributes error.class and error.message are now included on the span event in which an error or exception was noticed, and, in the case of unhandled exceptions, on any ancestor spans that also exit with an error. The public API method notice_error now attaches these error attributes to the currently executing span. Spans with error details are now highlighted red in the Distributed Tracing UI , and error details will expose the associated error.class and error.message. It is also now possible to see when an exception leaves the boundary of the span, and if it is caught in an ancestor span without reaching the entry span. NOTE: This “bubbling up” of exceptions will impact the error count when compared to prior behavior for the same trace. It is possible to have a trace that now has span errors without the trace level showing an error. If multiple errors occur on the same span, only the most recent error information is added to the attributes. Prior errors on the same span are overwritten. These span event attributes conform to ignored errors  and expected errors . Added tests for latest Grape / Rack combination For a short period of time, the latest versions of Grape and Rack had compatibility issues. Generally, Rack 2.1.0 should be avoided in all cases due to breaking changes in many gems reliant on Rack. We recommend using either Rack <= 2.0.9, or using latest Rack when using Grape (2.2.2 at the time of this writing). Bugfix: Calculate Content-Length in bytes Previously, the Content-Length HTTP header would be incorrect after injecting the Browser Monitoring JS when the response contained Unicode characters because the value was not calculated in bytes. The Content-Length is now correctly updated. Thanks to thaim for the contribution! Bugfix: Fix Content-Length calculation when response is nil Previously, calculating the Content-Length HTTP header would result in a NoMethodError in the case of a nil response. These errors will no longer occur in such a case. Thanks to Johan Van Ryseghem for the contribution! Bugfix: DecoratingFormatter now logs timestamps as millisecond Integers Previously the agent sent timestamps as a Float with milliseconds as part of the fractional value. Logs in Context was changed to only accept Integer values and this release changes DecoratingFormatter to match. Added --force option to newrelic install cli command to allow overwriting newrelic.yml Bugfix: The fully qualified hostname now works correctly for BSD and Solaris Previously, when running on systems such as BSD and Solaris, the agent was unable to determine the fully qualified domain name, which is used to help link Ruby agent data with data from New Relic Infrastructure. This information is now successfully collected on various BSD distros and Solaris.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-6100364","eolDate":"2023-04-08"},{"agent":"ruby","date":"2019-01-28","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-6.0.0.351.gem","version":"6.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v6.0.0 Tracer API for flexible custom instrumentation With agent version 6.0, we are introducing the Tracer class, an officially supported public API for more flexible custom instrumentation. By calling its in_transaction method, you can instrument an arbitrary section of Ruby code without needing to juggle any explicit state. Behind the scenes, the agent will make sure that the measured code results in an APM segment inside a transaction. The same API contains additional methods for creating transactions and segments, and for interacting with the current transaction. For more details, see the custom instrumentation documentation . If you were previously using any of the agent's private, undocumented APIs, such as Transaction.wrap or Transaction.start/stop, you will need to update your code to use the Tracer API. The full list of APIs that were removed or deprecated are: External.start_segment Transaction.create_segment Transaction.start Transaction.stop Transaction.start_datastore_segment Transaction.start_segment Transaction.wrap TransactionState.current_transaction If are you using any of these APIs, please see the upgrade guide  for a list of replacements. Agent detects Rails 6.0 The agent properly detects Rails 6.0 and no longer logs an error when started in a Rails 6.0 environment. This does not include full Rails 6.0 support, which will be coming in a future release. Thanks to Jacob Bednarz for the contribution.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-600351","eolDate":"2022-01-28"},{"agent":"ruby","date":"2019-01-14","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-5.7.0.350.gem","version":"5.7.0.350","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v5.7.0 Ruby 2.6 support We have tested the agent with the official release of Ruby 2.6.0 made on December 25, 2018. Support for loading Sequel core standalone The agent will now enable Sequel instrumentation when an application loads Sequel's core standalone, which does not use the Sequel:Model class. Thanks to Vasily Kolesnikov for the contribution! Grape 1.2 support With agent versions 5.6 and earlier, Grape 1.2 apps reported their transactions under the name Proc#call instead of the name of the API endpoint. Starting with agent version 5.7, all existing versions of Grape will report the correct transaction name. Thanks to Masato Ohba for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-570350","eolDate":"2022-01-14"},{"agent":"ruby","date":"2018-12-12","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-5.6.0.349.gem","version":"5.6.0.349","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v5.6.0 Bugfix for transactions with ActionController::Live Previously, transactions containing ActionController::Live resulted in incorrect calculations of capacity analysis as well as error backtraces appearing in agent logs in agent versions 5.4 and later. The agent now correctly calculates capacity for transactions with ActionController::Live. Add ability to exclude attributes from span events and transaction segments Agent versions 5.5 and lower could selectively exclude attributes from page views, error traces, transaction traces, and transaction events. With agent version 5.6 and higher, you can also exclude attributes from span events (via the span_events.include/exclude options) and from transaction segments (via the transaction_segments.include/exclude options). As with other attribute destinations, these new options will inherit values from the top-level attributes.include/exclude settings. See the documentation  for more information. Increasing backoff sequence on failing to connect to New Relic If the agent cannot reach New Relic, it will now wait for an increasing amount of time after each failed attempt. We are also starting with a shorter delay initially, which will help customer apps bounce back more quickly from transient network errors. Truncation of long stack traces Previous versions of the agent would truncate long stack traces to 50 frames. To give customers more flexibility, we have added the error_collector.max_backtrace_frames configuration option. Thanks to Patrick Tulskie for the contribution! Update link in documentation The community forum link in README.md now goes to the updated location. Thanks to Sam Killgallon for the contribution! Active Storage instrumentation The agent now provides instrumentation for Active Storage, introduced in Rails 5.2. Customers will see Active Storage operations represented as segments within transaction traces.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-560349","eolDate":"2021-12-12"},{"agent":"ruby","date":"2018-11-08","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-5.5.0.348.gem","version":"5.5.0.348","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v5.5.0 Bugfix for perform instrumentation with curb gem Use of curb's perform method now no longer results in nil headers getting returned. Bugfix for parsing Docker container IDs The agent now parses Docker container IDs correctly regardless of the cgroup parent. Use lazy load hooks for ActiveJob instrumentation In some instances the ActiveJob instrumentation could trigger ActiveJob to load before it was initialized by Rails. This could result in configuration changes not being properly applied. The agent now uses lazy load hooks which fixes this issue. Documentation improvement The config.dot diagram of the agent's configuration settings no longer includes the deleted developer_mode option. Thanks to Yuichiro Kaneko for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-550348","eolDate":"2021-11-08"},{"agent":"ruby","date":"2018-09-11","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-5.4.0.347.gem","version":"5.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v5.4.0 Capacity analysis for multi-threaded dispatchers Metrics around capacity analysis did not previously account for multi-threaded dispatchers and consequently could result in capacities of over 100% being recorded. This version now properly accounts for multi-threaded dispatchers. NewRelic::Agent.disable_transaction_tracing deprecated NewRelic::Agent.disable_transaction_tracing has been deprecated. Users are encouraged to use NewRelic::Agent.disable_all_tracing or NewRelic::Agent.ignore_transaction instead. Bugfix for SQL over-obfuscation A bug, introduced in v5.3.0, where SQL could be over-obfuscated for some database adapters has been fixed. Bugfix for span event data in Resque processes Previously, some users encountered a bug where span events would not be sent from Resque processes due to a missing endpoint, resulting in errors containing the text NoMethodError: undefined method span_event_data. Span events can now be successfully sent from Resque processes.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-540347","eolDate":"2021-09-11"},{"agent":"ruby","date":"2018-07-31","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-5.3.0.346.gem","version":"5.3.0.346","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v5.3.0 Distributed tracing Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before. Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide  before you enable this feature. To enable distributed tracing, set thedistributed_tracing.enabled configuration option to true.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-530346","eolDate":"2021-07-31"},{"agent":"ruby","date":"2018-06-04","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-5.2.0.345.gem","version":"5.2.0.345","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v5.2.0 Use priority sampling for errors and custom events Priority sampling replaces the older reservoir event sampling method. With this change, the agent will maintain randomness across a given time period while improving coordination among transactions, errors, and custom events. Bugfix for wrapping datastore operations The agent will now complete the process of wrapping datastore operations even if an error occurs during execution of a callback.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-520345","eolDate":"2021-06-04"},{"agent":"ruby","date":"2018-04-30","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-5.1.0.344.gem","version":"5.1.0.344","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Rails 5.2 support The Ruby agent has been validated against the latest release of Ruby on Rails! Support for newer libraries and frameworks We have updated the multiverse suite to test the agent against current versions of several frameworks. Add custom_attributes.enabled configuration option This option is enabled by default. When it's disabled, custom attributes will not be transmitted on transaction events or error events. Fix Grape load order dependency The agent will now choose the correct name for Grape transactions even if the customer's app loads the agent before Grape. Thanks to Daniel Doubrovkine for the contribution! Add webpacker:compile to blacklisted tasks webpacker:compile is commonly used for compiling assets. It has been added to AUTOSTART_BLACKLISTED_RAKE_TASKS in the default configuration. Thanks to Claudio B. for the contribution! Make browser instrumentation W3C-compliant type=\"text/javascript\" is optional for the <script> tag under W3C. The type attribute has now been removed from browser instrumentation. Thanks to Spharian for the contribution! Deferred add_method_tracer calls If a third-party library calls add_method_tracer before the agent has finished starting, we now queue these calls and run them when it's safe to do so (rather than skipping them and logging a warning). Bugfix for Resque around / before hooks In rare cases, the agent was not instrumenting Resque around and before hooks. This version fixes the error. Truncation of long stack traces Occasionally, long stack traces would cause complications sending data to New Relic. This version truncates long traces to 50 frames (split evenly between the top and bottom of the trace).","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-510344","eolDate":"2021-04-30"},{"agent":"ruby","date":"2018-03-26","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-5.0.0.342.gem","version":"5.0.0.342","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes SSL connections to New Relic are now mandatory Prior to this version, using an SSL connection to New Relic was the default behavior, but could be overridden. SSL connections are now enforced (not overrideable). Additional security checking before trying to explain multi-statement SQL queries Customer applications might submit SQL queries containing multiple statements (e.g., SELECT * FROM table; SELECT * FROM table). For security reasons, we should not generate explain plans in this situation. Although the agent correctly skipped explain plans for these queries during testing, we have added extra checks for this scenario. Bugfix for RabbitMQ exchange names that are symbols The agent no longer raises a TypeError when a RabbitMQ exchange name is a Ruby symbol instead of a string. Bugfix for audit logging to stdout Previous agents configured to log to stdout would correctly send regular agent logs to stdout, but would incorrectly send audit logs to a text file named \"stdout\". This release corrects the error. Bugfix for Capistrano deployment notifications on v3.7 and beyond Starting with version 3.7, Capistrano uses a different technique to determine a project's version control system. The agent now works correctly with this new behavior. Thanks to Jimmy Zhang for the contribution.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-500342","eolDate":"2021-03-26"},{"agent":"ruby","date":"2018-01-31","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-4.8.0.341.gem","version":"4.8.0.341","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Initialize New Relic Agent before config initializers When running in a Rails environment, the agent registers an initializer that starts the agent. This initializer is now defined to run before config/initializers. Previously, the ordering was not specified for the initializer. This change guarantees the agent will started by the time your initializers run, so you can safely reference the Agent in your custom initializers. Thanks to Tony Ta for the contribution. Ruby 2.5 Support The Ruby Agent has been verified to run under Ruby 2.5. request.uri Collected as an Agent Attribute Users can now control the collection of request.uri on errors and transaction traces. Previously it was always collected without the ability to turn it off. It is now an agent attribute that can be controlled via the attributes config. For more information on agent attributes see here .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-480341","eolDate":"2021-01-31"},{"agent":"ruby","date":"2017-12-22","downloadLink":null,"version":"4.7.1.340","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Bugfix for Manual Browser Instrumentation There was a previous bug that required setting both rum.enabled: false and browser.auto_instrument: false to completely disable browser monitoring. An attempt to fix this in 4.7.0 resulted in breaking manual browser instrumentation. Those changes have been reverted. We will revisit this issue in an upcoming release.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-471340","eolDate":"2020-12-22"},{"agent":"ruby","date":"2017-12-19","downloadLink":null,"version":"4.7.0.339","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Expected Error API The agent now sends up error.expected as an intrinsic attribute on error events and error traces. When you pass expected: true to the notice_error method, both Insights and APM will indicate that the error is expected. Typhoeus Hydra Instrumentation The agent now has request level visibility for HTTP requests made using Typhoeus Hydra. Total Time Metrics are Recorded The agent now records Total Time metrics. In an application where segments execute concurrently, the total time can exceed the wall-clock time for a transaction. Users of the new Typhoeus Hydra instrumentation will notice this as changes on the overview page. Immediately after upgrading there will be an alert in the APM dashboard that states: \"There are both old and new time metrics for this time window\". This indicates that during that time window, some transactions report the total time metrics, while others do not. The message will go away after waiting for enough time to elapse and / or updating the time window. Add :message category to set_transaction_name public API method The agent now permits the :message category to be passed into the public API method set_transaction_name, which will enable the transaction to be displayed as a messaging transaction. Create prepend_active_record_instrumentation config option Users may now set the prepend_active_record_instrumentation option in their agent config to install Active Record 3 or 4 instrumentation using Module.prepend rather than alias_method. Use Lazy load hooks for ActionController::Base and ActionController::API The agent now uses lazy load hooks to hook on ActionController::Base and ActionController::API. Thanks Edouard Chin for the contribution! Use Lazy load hooks for ActiveRecord::Base and ActiveRecord::Relation The agent uses lazy load hooks when recording supportability metrics for ActiveRecord::Base and ActiveRecord::Relation. Thanks Joseph Haig for the contribution! Check that Rails::VERSION is defined instead of just Rails The agent now checks that Rails::VERSION is defined since there are cases where Rails is defined but Rails::VERSION is not. Thanks to Alex Riedler and nilsding for the contribution! Support fast RPC/direct reply-to in RabbitMQ The agent can now handle the pseudo-queue 'amq.rabbitmq.reply-to' in its Bunny instrumentation. Previously, using fast RPC led to a NoMethodError because the reply-to queue was expected to be a Queue object instead of a string.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-470339","eolDate":"2020-12-19"},{"agent":"ruby","date":"2017-11-13","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-4.6.0.338.gem","version":"4.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Public API for External Requests The agent now has public API for instrumenting external requests and linking up transactions via cross application tracing. See the API Guide  for more details on this new functionality.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-460338","eolDate":"2020-11-13"},{"agent":"ruby","date":"2017-09-28","downloadLink":null,"version":"4.5.0.337","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Send synthetics headers even when CAT disabled The agent now sends synthetics headers whenever they are received from an external request, even if cross-application tracing is disabled. Bugfix for DelayedJob Daemonization Customers using the delayed_job script that ships with the gem may encounter an IOError with a message indicating the stream was closed. This was due to the agent attempting to write a byte into a Pipe that was closed during the deamonization of the delayed_job script. This issue has been fixed. Collect supportability metrics for public API The agent now collects Supportability/API/{method} metrics to track usage of all methods in the agent's public API. Collect supportability metrics on Module#prepend The agent now collects Supportability/PrependedModules/{Module} metrics for ActiveRecord 4 and 5, ActionController 4 and 5, ActionView 4 and 5, ActiveJob 5, and ActionCable 5. These help track the adoption of the Module#prepend method so we can maintain compatibility with newer versions of Ruby and Rails. Collect explain plans when using PostGIS ActiveRecord adapter The agent will now collect slow SQL explain plans, if configured to, on connections using the PostGIS adapter. Thanks Ari Pollak for the contribution! Lazily Intialize New Relic Config The agent will lazily initialize the New Relic config. This allows the agent to pickup configuration from environment variables set by dotenv and similar tools.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-450337","eolDate":"2020-09-28"},{"agent":"ruby","date":"2017-08-28","downloadLink":"https://rubygems.org/gems/newrelic_rpm","version":"4.4.0.336","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Include test helper for 3rd party use In 4.2.0, all test files were excluded from being packaged in the gem. An agent class method NewRelic::Agent.require_test_helper was used by 3rd party gem authors to test extensions to the agent. The required file is now included in the gem. Collect cloud metadata from Azure, GCP, PCF, and AWS cloud platform The agent now collects additional metadata when running in AWS, GCP, Azure, and PCF. This information is used to provide an enhanced experience when the agent is deployed on those platforms. Install at_exit hook when running JRuby The agent now installs an at_exit hook when running JRuby, which wasn't done before because of constraints related to older JRuby versions that are no longer supported. User/Utilization and System/Utilization metrics not recorded after Resque forks The agent no longer records invalid User/Utilization and System/Utilization metrics, which can lead to negative values, in forks of Resque processes. Add identifier field to agent connect settings The agent now includes a unique identifier in its connect settings, ensuring that when multiple agents connect to multiple different apps, data are reported for each of the apps. Clear transaction state after forking now opt-in The agent waits to connect until the first web request when it detects it's running in a forking dispatcher. When clearing the transaction state in this situation we lose the first frame of the transaction and the subsequent trace becomes corrupted. We've made this feature opt-in and is turned off by default. This behavior only affects the first transaction after a dispatcher forks.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-440336","eolDate":"2020-08-28"},{"agent":"ruby","date":"2017-07-24","downloadLink":null,"version":"4.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v4.3.0 Instrumentation for the Bunny AMQP Client The Bunny AMQP Client is now automatically instrumented. The agent will report data for messages sent and received by an application. Data on messages is available in both APM and Insights. Applications connected through a RabbitMQ exchange will now also be visible on Service Maps as part of Cross Application Tracing. See the message queues documentation page  for more details. Safely normalize external hostnames The agent has been updated to check for nil host values before downcasing the hostname. Thanks Rafael Valério for the contribution! PageView events will not be generated for ignored transactions The agent now checks if transaction is ignored before injecting the New Relic Browser Agent. This will prevent PageView events from being generated for ignored transactions. Datastores required explicitly in agent The agent has been modified to explicity require the Datastores module whereas previously there were situations where the module could be implicitly defined. Thanks Kevin Griffin for the contribution! Clear transaction state after forking Previously, if a transaction was started and the process forks, the transaction state survived the fork and #after_fork call in thread local storage. Now, this state is cleared by #after_fork. Postgis adapter reports as Postgres for datastores The agent now maps the Postgis adapter to Postgres for datastore metrics. Thanks Vojtěch Vondra for the contribution! Deprecate :trace_only option The NewRelic::Agent.notice_error API has been updated to deprecate the :trace_only option in favor of :expected.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-430335","eolDate":"2020-07-24"},{"agent":"ruby","date":"2017-05-25","downloadLink":null,"version":"4.2.0.334","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v4.2.0 Sinatra 2.0 and Padrino 0.14.x Support The agent has been verified against the latest versions of Sinatra and Padrino. Rails 5.1 Support The Ruby agent has been validated against the latest release of Ruby on Rails! APP_ENV considered when determining environment The agent will now consider the APP_ENV environment when starting up. Test files excluded from gem The gemspec has been updated to exclude test files from being packaged into the gem. Thanks dimko for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-420334","eolDate":"2020-05-25"},{"agent":"ruby","date":"2017-04-12","downloadLink":null,"version":"4.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v4.1.0 Developer Mode removed The Ruby Agent's Developer Mode, which provided a very limited view of your application performance data, has been removed. For more information, check out our community forum . Support NEW_RELIC_ENV for Rails apps Previously, users could set the agent environment with NEW_RELIC_ENV only for non-Rails apps. For Rails app, the agent environment would use whatever the Rails environment was set to. Now, NEW_RELIC_ENV can also be used for Rails apps, so that it is possible to have an agent environment that is different from the Rails environment. Thanks Andrea Campolonghi for the contribution, as well as Steve Schwartz for also looking into this issue! Normalization of external hostnames Hostnames from URIs used in external HTTP requests are now always downcased to prevent duplicate metrics when only case is different.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-410333","eolDate":"2020-04-12"},{"agent":"ruby","date":"2017-03-16","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-4.0.0.332.gem","version":"4.0.0.332","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v4.0.0 Require Ruby 2.0.0+ The agent no longer supports Ruby versions prior to 2.0, JRuby 1.7 and earlier, and all versions of Rubinius. Customers using affected Rubies can continue to run 3.x agent versions, but new features or bugfixes will not be published for 3.x agents. For more information, check out our community forum . OkJson vendored library removed Ruby 1.8 did not include the JSON gem by default, so the agent included a vendored version of OkJson  that it would fall back on using in cases where the JSON gem was not available. This has been removed. YAJL workaround removed yajl-ruby  versions prior to 1.2 had the potential to cause a segmentation fault when working large, deeply-nested objects like thread profiles. If you are using yajl-ruby with the JSON monkey patches enabled by requiring yajl/json_gem, you should upgrade to at least version 1.2. Deprecated APIs removed Agent.abort_transaction! Agent.add_custom_parameters Agent.add_request_parameters Agent.browser_timing_footer Agent.get_stats Agent.get_stats_no_scope Agent.record_transaction Agent.reset_stats Agent.set_user_attributes Agent::Instrumentation::Rack ActionController#newrelic_notice_error ActiveRecordHelper.rollup_metrics_for (may be incompatible with newrelic_moped) Instrumentation::MetricFrame.recording_web_transaction? Instrumentation::MetricFrame.abort_transaction! MethodTracer.get_stats_scoped MethodTracer.get_stats_unscoped MethodTracer.trace_method_execution MethodTracer.trace_method_execution_no_scope MethodTracer.trace_method_execution_with_scope MetricSpec#sub MetricStats#get_stats MetricStats#get_stats_no_scope NoticedError#exception_class Rack::ErrorCollector StatsEngine::Samplers.add_sampler StatsEngine::Samplers.add_harvest_sampler The above methods have had deprecation notices on them for some time and have now been removed. Assistance migrating usage of these APIs is available at https://docs.newrelic.com/docs/agents/ruby-agent/troubleshooting/update-...  . The agent no longer deletes deprecated keys passed to add_method_tracer. Passing in deprecated keys can cause an exception. Ensure that you are not passing any of the following keys: :force, :scoped_metric_only, :deduct_call_time_from_parent to add_method_tracer. The agent no longer deletes deprecated keys passed in as options to NewRelic::Agent.notice_error. If you are passing any of these deprecated keys: :request_params, :request, :referer to the notice_error API, please delete them otherwise they will be collected as custom attributes. Error handling changes The agent now only checks for original_exception in environments with Rails versions prior to 5. Checking for Exception#cause has been removed. In addition, the agent now will match class name with message and backtrace when noticing errors that have an original_exception.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-400332","eolDate":"2020-03-16"},{"agent":"ruby","date":"2014-12-31","downloadLink":"http://rubygems.org/gems/newrelic_rpm/versions/3.9.9.275","version":"3.9.9.275","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Support for Ruby 2.2 A new version of Ruby is available, and the Ruby agent is ready to run on it. We've been testing things out since the early previews so you can upgrade to the latest and greatest and use New Relic right away to see how the new Ruby's performing for you. Support for Rails 4.2 and ActiveJob Not only is a new Ruby available, but a new Rails is out too! The Ruby agent provides all the usual support for Rails that you'd expect, and we instrument the newly released ActiveJob framework that's part of 4.2. Security fix for handling of error responses from New Relic servers This release fixes a potential security issue wherein an attacker who was able to impersonate New Relic's servers could have triggered arbitrary code execution in agent's host processes by sending a specially-crafted error response to a data submission request. This issue is mitigated by the fact that the agent uses SSL certificate checking in order to verify the identity of the New Relic servers to which it connects. SSL is enabled by default by the agent. It can be enforced account-wide by enabling High-security mode  for your account. Fix for transactions with invalid URIs If an application used the agent's ignore_url_regexes config setting to ignore certain transactions, but received an invalid URI, the agent would fail to record the transaction. This has been fixed. Fixed incompatibility with newrelic-grape The 3.9.8 release of the Ruby agent included disabled prototyped instrumentation for the Grape API framework. This introduced an incompatibility with the existing third party extension newrelic-grape. This has been fixed. Newrelic-grape continues to be the right solution until full agent support for Grape is available.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-399275","eolDate":"2017-12-31"},{"agent":"ruby","date":"2014-12-03","downloadLink":"http://rubygems.org/gems/newrelic_rpm/versions/3.9.8.273","version":"3.9.8.273","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Custom Insights events API In addition to attaching custom parameters to the events that the Ruby agent generates automatically for each transaction, you can now record custom event types into Insights with the new NewRelic::Agent.record_custom_event API. For details, see https://docs.newrelic.com/docs/insights/new-relic-insights/adding-queryi... Reduced memory usage for idling applications Idling applications using the agent could previously appear to leak memory because of native allocations during creation of new SSL connections to our servers. These native allocations didn't factor into triggering Ruby's garbage collector. The agent will now re-use a single TCP connection to our servers for as long as possible, resulting in improved memory usage for applications that are idling and not having GC triggered for other reasons. Don't write to stderr during CPU sampling The Ruby agent's code for gathering CPU information would write error messages to stderr on some FreeBSD systems. This has been fixed. LocalJumpError on Rails 2.x Under certain conditions, Rails 2.x controller instrumentation could fail with a LocalJumpError when an action was not being traced. This has been fixed. Fixed config lookup in warbler packaged apps When running a Ruby application from a standalone warbler .jar file on JRuby, the packaged config/newrelic.yml was not properly found. This has been fixed, and thanks to Bob Beaty for the help getting it fixed! Hash iteration failure in middleware If a background thread iterated over the keys in the Rack env hash, it could cause failures in New Relic's AgentHooks middleware. This has been fixed.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-398273","eolDate":"2017-12-03"},{"agent":"ruby","date":"2014-11-14","downloadLink":"http://rubygems.org/gems/newrelic_rpm/versions/3.9.7.266","version":"3.9.7.266","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Support for synthetic monitors The Ruby agent now gives you additional information for requests from synthetic monitors. More transaction traces and events give you a clearer look into how your application is performing around the world. For more details, see https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/getting-s... Support for multiple job per fork gems with Resque The resque-jobs-per-fork and resque-multi-job-forks gems alter Resque to fork every N jobs instead of every job. This previously caused issues for the Ruby agent, but those have been resolved. These gems are fully supported. Running Resque with the FORK_PER_JOB=false environment variable setting is also supported now. For more details on our Resque support, see https://docs.newrelic.com/docs/agents/ruby-agent/background-jobs/resque-... Support agent when starting Resque Pool from Rake task When running resque-pool with its provided rake tasks, the agent would not start up properly. Thanks Tiago Sousa for the fix! Fix for DelayedJob + Rails 4.x queue depth metrics The Ruby agent periodically records DelayedJob queuedepth as a metric, but this didn't work properly in Rails 4.x applications. This has been fixed. Thanks Jonathan del Strother for his help with the issue! Fix for failure in background transactions with rules.ignore_url_regexes The recently added feature for ignoring transactions via URL regexes caused errors for non-web transactions. This has been fixed. Rename the TransactionNamer.name method to TransactionNamer.name_for The internal TransactionNamer class had a class method called 'name', with a different signature than the existing Class#name method and could cause problems when trying to introspect instances of the class. Thanks to Dennis Taylor for contributing this fix!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-397266-0","eolDate":"2017-11-14"},{"agent":"ruby","date":"2014-10-20","downloadLink":"http://rubygems.org/gems/newrelic_rpm/versions/3.9.6.257","version":"3.9.6.257","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Rails 4.2 ActiveJob support A new version of Rails is coming! One of the highlight features is ActiveJob, a framework for interacting with background job processors. This release of the Ruby agent adds instrumentation to give you insight into ActiveJob, whether you're just testing it out or running it for real. Metrics are recorded around enqueuing ActiveJobs, and background transactions are started for any ActiveJob performed where the agent didn't already provide specific instrumentation (such as DelayedJob, Resque and Sidekiq). Since Rails 4.2 is still in beta we'd love to hear any feedback on this instrumentation so it'll be rock solid for the general release! Ruby 2.2.0-preview1 updates Ruby 2.2.0 is on its way later in the year, and the Ruby agent is ready for it. Updates to the GC stats and various other small changes have already been applied, and our automated tests are running against 2.2.0 so the agent will be ready on release day. Ignoring transactions by URL While you could always ignore transactions by controller and action, the Ruby agent previously lacked a way to ignore by specific URLs or patterns without code changes. This release adds the config setting, rules.ignore_url_regexes to ignore specific transactions based on the request URL as well. For more information, see the documentation at: https://docs.newrelic.com/docs/agents/ruby-agent/installation-configurat... Better dependency detection in non-Rack applications The Ruby agent runs dependency detection at key points in the Rack and Rails lifecycle, but non-Rails apps could occasionally miss out instrumenting late loaded libraries. The agent now runs an additional dependency detection during manual_start to more seamlessly install instrumentation in any app. Excluding /newrelic routes from developer mode Recent changes to track time in middleware resulted in New Relic's developer mode capturing its own page views in the list. This has been fixed. Thanks to Ignatius Reza Lesmana for the report! Spikes in external time Timeouts during certain external HTTP requests could result in incorrect large spikes in the time recorded by the agent. This has been fixed. Recognize browser_monitoring.auto_instrument setting in non-Rails apps The browser_monitoring.auto_instrument config setting disables auto-injection of JavaScript into your pages, but was not properly obeyed in Sinatra and other non-Rails contexts. This has been fixed. Failures to gather CPU thread time on JRuby JRuby running on certain JVM's and operating systems (FreeBSD in particular) did not always support the method being used to gather CPU burn metrics. This would result in a failure during those transactions. This has been fixed. Fix for rare race condition in Resque instrumentation A race condition in the agent's Resque instrumentation that could cause rare Resque job failures in high-throughput Resque setups has been fixed. This bug would manifest as an exception with the following error message: \"RuntimeError: can't add a new key into hash during iteration\" and a backtrace leading through the PipeChannelManager class in the agent.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-396257","eolDate":"2017-10-20"},{"agent":"ruby","date":"2014-09-29","downloadLink":null,"version":"3.9.5.251","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Per-dyno data on Heroku When running on Heroku, data from the agent can now be broken out by dyno name, allowing you to more easily see what's happening on a per-dyno level. Dynos on Heroku are now treated in the same way that distinct hosts on other platforms work. By default, 'scheduler' and 'run' dyno names will be aggregated into scheduler.* and run.* to avoid unbounded growth in the number of reported hostnames. Read more about this feature on our Heroku docs page: https://docs.newrelic.com/docs/agents/ruby-agent/miscellaneous/ruby-agen... HTTP response codes in Insights events The Ruby agent will now capture HTTP response codes from Rack applications (including Rails and Sinatra apps) and include them under the httpResponseCode attribute on events sent to Insights. Stricter limits on memory usage of metrics and SQL traces The agent now imposes stricter limits on the number of distinct SQL traces and metrics that it will buffer in memory at any point in time, leading to more predictable memory consumption even in exceptional circumstances. Improved reliability of thread profiling Several issues that would previously have prevented the successful completion and transmission of thread profiles to New Relic's servers have been fixed. These issues were related to the use of recursion in processing thread profiles, and have been addressed by both limiting the maximum depth of the backtraces recorded in thread profiles, and eliminating the agent's use of recursion in processing profile data. Allow tracing Rails view helpers with add_method_tracer Previously, attempting to trace a Rails view helper method using add_method_tracer on the view helper module would lead to a NoMethodError when the traced method was called (undefined method `trace_execution_scoped'). This has been fixed. This issue was an instance of the Ruby 'dynamic module inclusion' or 'double inclusion' problem. Usage of add_method_tracer now no longer relies upon the target class having actually picked up the trace_execution_scoped method from the NewRelic::Agent::MethodTracer module. Improved performance of queue time parsing The number of objects allocated while parsing the frontend timestamps on incoming HTTP requests has been significantly reduced. Thanks to Aleksei Magusev for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-395251","eolDate":"2017-09-29"},{"agent":"ruby","date":"2014-09-08","downloadLink":null,"version":"3.9.4.245","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Allow agent to use alternate certificate stores When connecting via SSL to New Relic, the Ruby agent verifies its connection via a certificate bundle shipped with the agent. This caused problems with certain proxy configurations, so the ca_bundle_path setting in newrelic.yml can now override the default cert bundle location. For more information, see custom SSL certificates Rails 4.2 beta in tests Although still in beta, a new version of Rails is on its way! We're already running our automated test suites against the beta to ensure New Relic is ready the day the next Rails is released. ActiveRecord 4 cached queries fix Queries against the ActiveRecord 4.x query cache were incorrectly being counted as database time by the agent. Fix for error in newrelic.yml loading If your application used a RAILS_ENV value that was not listed in newrelic.yml recent agent versions would return a NameError rather than a helpful message. This has been fixed. Thanks Oleksiy Kovyrin for the patch!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-394245","eolDate":"2017-09-08"},{"agent":"ruby","date":"2014-08-25","downloadLink":null,"version":"3.9.3.241","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fix to prevent proxy credentials transmission This update prevents proxy credentials set in the agent config file from being transmitted to New Relic.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-393241","eolDate":"2017-08-25"},{"agent":"ruby","date":"2014-08-21","downloadLink":null,"version":"3.9.2.239","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Added API for ignoring transactions This release adds three new API calls for ignoring transactions: NewRelic::Agent.ignore_transaction NewRelic::Agent.ignore_apdex NewRelic::Agent.ignore_enduser ignore_transaction ignores a transaction completely: nothing about it will be reported to New Relic. ignore_apdex ignores only the Apdex metric for a single transaction. ignore_enduser disables Javascript injection for browser monitoring for the current transaction. These methods differ from the existing newrelic_ignore_* method in that they may be called during  a transaction based on some dynamic runtime criteria, as opposed to at the class level on startup. For more information, see ignoring specific transactions . Improved SQL obfuscation SQL queries containing string literals ending in backslash \\ characters were not correctly obfuscated by the Ruby agent prior to transmission to New Relic. In addition, SQL comments were left un-obfuscated. This has been fixed, and the test coverage for SQL obfuscation has been improved. newrelic_ignore* methods now work when called in a superclass The newrelic_ignore* family of methods previously did not apply to subclasses of the class from which it was called, meaning that Rails controllers inheriting from a single base class where newrelic_ignore had been called would not be ignored. This has been fixed. Fix for rare crashes in Rack::Request#params on Sinatra apps Certain kinds of malformed HTTP requests previously caused unhandled exceptions in the Ruby agent's Sinatra instrumentation, in the Rack::Request#params method. This has been fixed. Improved handling for rare errors caused by timeouts in Excon requests In some rare cases, the agent would emit a warning message in its log file and abort instrumentation of a transaction if a timeout occurred during an Excon request initiated from within that transaction. This has been fixed. Improved behavior when the agent is misconfigured When the agent is misconfigured by attempting to shut it down without it ever having been started, or by attempting to disable instrumentation after instrumentation has already been installed, the agent will no longer raise an exception, but will instead log an error to its log file. Fix for ignore_error_filter not working in some configurations The ignore_error_filter method allows you to specify a block to be evaluated in order to determine whether a given error should be ignored by the agent. If the agent was initially disabled, and then later enabled with a call to manual_start, the ignore_error_filter would not work. This has been fixed. Fix for Capistrano 3 ignoring newrelic_revision New Relic's Capistrano recipes support passing parameters to control the values recorded with deployments, but user-provided :newrelic_revision values were incorrectly overwritten. This has been fixed. Agent errors logged with ruby-prof in production If the ruby-prof gem was available in an environment without New Relic's developer mode enabled, the agent would generate errors to its log. This has been fixed. Tighter requirements on naming for configuration environment variables The agent would previously assume any environment variable containing NEWRELIC was a configuration setting. It now looks for this string as a prefix only. Thanks to Chad Woolley for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-392239","eolDate":"2017-08-21"},{"agent":"ruby","date":"2014-07-31","downloadLink":null,"version":"3.9.1.236","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Ruby 1.8.7 users: upgrade or add JSON gem now Ruby 1.8.7 is end-of-lifed, and not receiving security updates, so we strongly encourage all users with apps on 1.8.7 to upgrade. If you're not able to upgrade yet, be aware that a coming release of the Ruby agent will require users of Ruby 1.8.7 to have the 'json' gem available within their applications in order to continue sending data to New Relic. Support for new Cross Application Trace view This release enhances cross application tracing with a visualization of the cross application calls that a specific Transaction Trace is involved in. The new visualization helps you spot bottlenecks in external services within Transaction Traces and gives you an end-to-end understanding of how the transaction trace is used by other applications and services. This leads to faster problem diagnosis and better collaboration across teams. All agents involved in the cross application communication must be upgraded to see the complete graph. You can view cross application traces from in the Transaction Trace drill-down. High-security mode v2 The Ruby agent now supports v2 of New Relic's high-security mode. To enable it, you must add 'high_security: true' to your newrelic.yml  file, and enable high-security mode through the New Relic web interface. The local agent setting must be in agreement with the server-side setting, or the agent will shut down and no data will be collected. Customers who already had the server-side high-security mode setting enabled must add 'high_security: true' to their agent configuration files when upgrading to this release. For details on high-security mode, see: http://docs.newrelic.com/docs/accounts-partnerships/accounts/security/hi... Improved memcached instrumentation More accurate instrumentation for the 'cas' command when using version 1.8.0 or higher of the memcached gem. Previous versions of the agent would count all time spent in the block given to 'cas' as memcache time, but 1.8.0 or higher allows us to more accurately measure just the time spent talking to memcache. Many thanks to Francis Bogsanyi for contributing this change! Improved support for Rails apps launched from outside the app root directory The Ruby agent attempts to resolve the location of its configuration file at runtime relative to the directory that the host process is started from. In cases where the host process was started from outside of the application's root directory (for example, if the process is started from from '/'), it will now also attempt to locate its configuration file based on the value of Rails.root for Rails applications. Better compatibility with ActionController::Live Browser Application Monitoring auto-injection can cause request failures under certain circumstances when used with ActionController::Live, so the agent will now automatically detect usage of ActionController::Live, and not attempt auto-injection for those requests (even if auto-instrumentation is otherwise enabled). Many thanks to Rodrigo Rosenfeld Rosas for help diagnosing this issue! Fix for occasional spikes in external services time Certain kinds of failures during HTTP requests made by an application could have previously resulted in the Ruby agent reporting erroneously large amounts of time spent in outgoing HTTP requests. This issue manifested most obviously in spikes on the 'Web external' band on the main overview graph. This issue has now been fixed. Fix 'rake newrelic:install' for Rails 4 applications The newrelic:install rake task was previously not working for Rails 4 applications and has been fixed. Thanks to Murahashi Sanemat Kenichi for contributing this fix!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-391236","eolDate":"2017-07-31"},{"agent":"ruby","date":"2014-06-25","downloadLink":null,"version":"3.9.0.229","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Rack middleware instrumentation The Ruby agent now automatically instruments Rack middlewares! This means that the agent can now give you a more complete picture of your application's response time, including time spent in middleware. It also means that requests which previously weren't captured by the agent because they never made it to the bottom of your middleware stack (usually a Rails or Sinatra application) will now be captured. After installing this version of the Ruby agent, you'll see a new 'Middleware' band on your application's overview graph, and individual middlewares will appear in transaction breakdown charts and transaction traces. The agent can instrument middlewares that are added from a config.ru file via Rack::Builder, or via Rails' middleware stack in Rails 3.0+. This instrumentation may be disabled with the disable_middlware_instrumentation configuration setting. For more details, see the documentation for this feature: http://docs.newrelic.com/docs/ruby/rack-middlewares http://docs.newrelic.com/docs/ruby/middleware-upgrade-changes Capistrano 3.x support Recording application deployments using Capistrano 3.x is now supported. Many thanks to Jennifer Page for the contribution! Better support for Sidekiq's Delayed extensions Sidekiq jobs executed via the Delayed extensions (e.g. the #delay method) will now be named after the actual class that #delay was invoked against, and will have their job arguments correctly captured if the sidekiq.capture_params configuration setting is enabled. Many thanks to printercu for the contribution! Improved Apdex calculation with ignored error classes Previously, a transaction resulting in an exception that bubbled up to the top level would always be counted as failing for the purposes of Apdex calculations (unless the transaction name was ignored entirely). Now, exceptions whose classes have been ignored by the error_collector.ignore_errors configuration setting will not cause a transaction to be automatically counted as failing. Allow URIs that are not parseable by stdlib's URI if addressable is present There are some URIs that are valid by RFC 3986, but not parseable by Ruby's stdlib URI class. The Ruby agent will now attempt to use the addressable gem to parse URIs if it is present, allowing requests against these problematic URIs to be instrumented. Many thanks to Craig R Webster and Amir Yalon for their help with this issue! More robust error collection from Resque processes Previously, traced errors where the exception class was defined in the Resque worker but not in the Resque master process would not be correctly handled by the agent. This has been fixed. Allow Sinatra apps to set the New Relic environment without setting RACK_ENV The NEW_RELIC_ENV environment variable may now be used to specify the environment the agent should use from its configuration file, independently of RACK_ENV. Many thanks to Mario Izquierdo for the contribution! Better error handling in Browser Application Monitoring injection The agent middleware that injects the JavaScript code necessary for Browser Application Monitoring now does a better job of catching errors that might occur during the injection process. Allow disabling of Net::HTTP instrumentation Most instrumentation in the Ruby agent can be disabled easily via a configuration setting. Our Net::HTTP instrumentation was previously an exception, but now it can also be disabled with the disable_net_http configuration setting. Make Rails constant presence check more defensive The Ruby agent now guards against the (rare) case where an application has a Rails constant defined, but no Rails::VERSION constant (because Rails is not actually present). Many thanks to Vladimir Kiselev for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-390229","eolDate":"2017-06-25"},{"agent":"ruby","date":"2014-05-16","downloadLink":null,"version":"3.8.1.221","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Better handling for Rack applications implemented as middlewares When using a Sinatra application as a middleware around another app (for example, a Rails app), or manually instrumenting a Rack middleware wrapped around another application, the agent would previously generate two separate transaction names in the New Relic UI (one for the middleware, and one for the inner application). As of this release, the agent will instead unify these two parts into a single transaction in the UI. The unified name will be the name assigned to the inner-most traced transaction by default. Calls to NewRelic::Agent.set_transaction_name will continue to override the default names assigned by the agent's instrumentation code. This change also makes it possible to run X-Ray sessions against transactions of the 'inner' application in cases where one instrumented app is wrapped in another that's implemented as a middleware. Support for mongo-1.10.0 The Ruby agent now instruments version 1.10.0 of the mongo gem (versions 1.8.x and 1.9.x were already supported, and continue to be). Allow setting configuration file path via an option to manual_start Previously, passing the :config_path option to NewRelic::Agent.manual_start would not actually affect the location that the agent would use to look for its configuration file. This has been fixed, and the log messages emitted when a configuration file is not found should now be more helpful.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-381221","eolDate":"2017-05-16"},{"agent":"ruby","date":"2014-04-22","downloadLink":null,"version":"3.8.0.218","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Better support for forking and daemonizing dispatchers (e.g. Puma, Unicorn) The agent should now work out-of-the box with no special configuration on servers that fork or daemonize themselves (such as Unicorn or Puma in some configurations). The agent's background thread will be automatically restarted after the first transaction processed within each child process. This change means it's no longer necessary to set the 'restart_thread_in_children setting' in your agent configuration file if you were doing so previously. Rails 4.1 support Rails 4.1 has shipped, and the Ruby agent is ready for it! We've been running our test suites against the release candidates with no significant issues, so we're happy to announce full compatibility with this new release of Rails. Ruby VM measurements The Ruby agent now records more detailed information about the performance and behavior of the Ruby VM, mainly focused around Ruby's garbage collector. This information is exposed on the new 'Ruby VM' tab in the UI. For details about what is recorded, see: http://docs.newrelic.com/docs/ruby/ruby-vm-stats Separate in-transaction GC timings for web and background processes Previously, an application with GC instrumentation enabled, and both web and background processes reporting in to it would show an overly inflated GC band on the application overview graph, because data from both web and non-web transactions would be included. This has been fixed, and GC time during web and non-web transactions is now tracked separately. More accurate GC measurements on multi-threaded web servers The agent could previously have reported inaccurate GC times on multi-threaded web servers such as Puma. It will now correctly report GC timings in multi-threaded contexts. Improved ActiveMerchant instrumentation The agent will now trace the store, unstore, and update methods on ActiveMerchant gateways. In addition, a bug preventing ActiveMerchant instrumentation from working on Ruby 1.9+ has been fixed. Thanks to Troex Nevelin for the contribution! More robust Real User Monitoring script injection with charset meta tags Previous versions of the agent with Real User Monitoring enabled could have injected JavaScript code into the page above a charset meta tag. By the HTML5 spec, the charset tag must appear in the first 1024 bytes of the page, so the Ruby agent will now attempt to inject RUM script after a charset tag, if one is present. More robust connection sequence with New Relic servers A rare bug that could cause the agent's initial connection handshake with New Relic servers to silently fail has been fixed, and better logging has been added to the related code path to ease diagnosis of any future issues. Prevent over-counting of queue time with nested transactions When using add_transaction_tracer on methods called from within a Rails or Sinatra action, it was previously possible to get inflated queue time measurements, because queue time would be recorded for both the outer transaction (the Rails or Sinatra action) and the inner transaction (the method given to add_transaction_tracer). This has been fixed, so only the outermost transaction will now record queue time.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-380218","eolDate":"2017-04-22"},{"agent":"ruby","date":"2014-03-11","downloadLink":null,"version":"3.7.3.204","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fix for Puma 2.8.0 cluster mode (3.7.3.204) Puma's 2.8.0 release renamed a hook New Relic used to support Puma's cluster mode. This resulted in missing data for users running Puma. Thanks Benjamin Kudria for the fix! Fix for deployment command bug (3.7.3.204) Problems with file loading order could result in newrelic deployments failing with an unrecognized command error. This has been fixed.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-373204","eolDate":"2017-03-11"},{"agent":"ruby","date":"2014-03-05","downloadLink":null,"version":"3.7.3.199","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Obfuscation for PostgreSQL explain plans Fixes an agent bug with PostgreSQL where parameters from the original query could appear in explain plans sent to New Relic servers, even when SQL obfuscation was enabled. Parameters from the query are now masked in explain plans prior to transmission when transaction_tracer.record_sql is set to 'obfuscated' (the default setting). For more information, see: https://docs.newrelic.com/docs/traces/security-for-postgresql-explain-plans More accurate categorization of SQL statements Some SQL SELECT statements that were previously being mis-categorized as 'SQL - OTHER' will now correctly be tagged as 'SQL - SELECT'. This particularly affected ActiveRecord users using PostgreSQL. More reliable Typhoeus instrumentation Fixed an issue where an exception raised from a user-specified on_complete block would cause our Typhoeus instrumentation to fail to record the request.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-373199","eolDate":"2017-03-05"},{"agent":"ruby","date":"2014-02-18","downloadLink":null,"version":"3.7.2.195","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Update gem signing cert (3.7.2.195) The certificate used to sign newrelic_rpm expired in February. This patch updates that for clients installing with verification.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-372195","eolDate":"2017-02-18"},{"agent":"ruby","date":"2014-02-05","downloadLink":null,"version":"3.7.2.192","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Mongo instrumentation improvements Users of the 'mongo' MongoDB client gem will get more detailed instrumentation including support for some operations that were not previously captured, and separation of aggregate metrics for web transactions from background jobs. An issue with ensure_index when passed a symbol or string was also fixed. Thanks Maxime RETY for the report! More accurate error tracing in Rails 4 Traced errors in Rails 4 applications will now be correctly associated with the transaction they occurred in, and custom attributes attached to the transaction will be correctly attached to the traced error as well. More accurate partial-rendering metrics for Rails 4 View partials are now correctly treated as sub-components of the containing template render in Rails 4 applications, meaning that the app server breakdown graphs for Rails 4 transactions should be more accurate and useful. Improved Unicorn 4.8.0 compatibility A rare issue that could lead to spurrious traced errors on app startup for applications using Unicorn 4.8.0 has been fixed. meta_request gem compatibility An incompatibility with the meta_request gem has been fixed. Typhoeus 0.6.4+ compatibility A potential crash with Typhoeus 0.6.4+ when passing a URI object instead of a String instance to one of Typhoeus's HTTP request methods has been fixed. Sequel single threaded mode fix The agent will no longer attempt to run EXPLAIN queries for slow SQL statements issued using the Sequel gem in single-threaded mode, since doing so could potentially cause crashes. Additional functionality for add_custom_parameters Calling add_custom_parameters adds parameters to the system codenamed Rubicon. For more information, see http://newrelic.com/software-analytics","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-372192","eolDate":"2017-02-05"},{"agent":"ruby","date":"2014-01-20","downloadLink":null,"version":"3.7.1.188","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Correct first reported metric timespan for forking dispatchers (3.7.1.188) The first time a newly-forked process (in some configurations) reported metric data, it would use the startup time of the parent process as the start time for that metric data instead of its own start time. This has been fixed.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-371188","eolDate":"2017-01-20"},{"agent":"ruby","date":"2013-12-31","downloadLink":null,"version":"3.7.1.182","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fix for Mongo ensure_index instrumentation (3.7.1.182) The Mongo instrumentation for ensure_index in 3.7.1.180 was not properly calling through to the uninstrumented version of this method. This has been fixed in 3.7.1.182. Thanks to Yuki Miyauchi for the fix!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-371182","eolDate":"2016-12-31"},{"agent":"ruby","date":"2013-12-20","downloadLink":null,"version":"3.7.1.180","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 MongoDB support The Ruby agent provides support for the mongo gem, versions 1.8 and 1.9! Mongo calls are captured for transaction traces along with their parameters, and time spent in Mongo shows up on the Database tab. Support for more Mongo gems and more UI goodness will be coming, so watch http://docs.newrelic.com/docs/ruby/mongo  for up-to-date status. Harvest thread restarts for forked and daemonized processes Historically framework specific code was necessary for the Ruby agent to successfully report data after an app forked or daemonized. Gems or scripts with daemonizing modes had to wait for agent support or find workarounds. With 3.7.1 setting restart_thread_in_children: true in your newrelic.yml automatically restarts the agent in child processes without requiring custom code. For now the feature is opt-in, but future releases may default it on. Fix for missing HTTP time The agent previously did not include connection establishment time for outgoing Net::HTTP requests. This has been corrected, and reported HTTP timings should now be more accurate.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-371180","eolDate":"2016-12-20"},{"agent":"ruby","date":"2013-12-05","downloadLink":null,"version":"3.7.0.177","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Official Rubinius support (for Rubinius >= 2.2.1) We're happy to say that all known issues with the Ruby agent running on Rubinius have been resolved as of Rubinius version 2.2.1! See New Relic on Rubinius  for the most up-to-date status. RUM injection updates The Ruby agent's code for both automatic and manual injection of Real User Monitoring scripts has been improved. No application changes are required, but the new injection logic is simpler, faster, more robust, and paves the way for future improvements to Real User Monitoring. More robust communication with New Relic Failures when transmitting data to New Relic could cause data to be held over unnecessarily to a later harvest. This has been improved both to handle errors more robustly and consistently, and to send data as soon as possible. Fix for agent not restarting on server-side config changes A bug in 3.6.9 caused the agent to not reset correctly after server-side config changes. New settings would not be received without a full process restart. This has been fixed. Adding rake spec tasks to your deny list A deny list helps the agent avoid starting during rake tasks. Some default RSpec tasks were missing. Thanks for the contribution Kohei Hasegawa!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-370177","eolDate":"2016-12-05"},{"agent":"ruby","date":"2013-11-07","downloadLink":null,"version":"3.6.9.171","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Experimental Rubinius 2.x support The agent is now being tested against the latest version of Rubinius. While support is still considered experimental, you can track the progress at https://docs.newrelic.com/docs/ruby/rubinius  for up to date status. Capture arguments for Resque and Sidekiq jobs The agent can optionally record arguments for your Resque and Sidekiq jobs on transaction traces and traced errors. This is disabled by default, but may be enabled by setting resque.capture_params or sidekiq.capture_params. Thanks to Juan Ignacio Pumarino, Ken Mayer, Paul Henry, and Eric Saxby for their help with this feature! Supported versions rake task and documentation We've improved our documentation for what Ruby and gem versions we support. Run rake newrelic:supported_versions or see the latest agent's versions at https://docs.newrelic.com/docs/ruby/supported-frameworks . ActiveRecord 4.0 explain plans for JRuby and Rubinius The agent's ActiveRecord 4.0 instrumentation could not gather SQL explain plans on JRuby by default because of a dependency on ObjectSpace, which isn't available by default. This has been fixed. Fix for Curb http_put_with_newrelic A bug in the agent caused PUT calls in the Curb gem to crash. This has been fixed. Thanks to Michael D'Auria and Kirk Diggler for the contributions! Fix for head position on RUM injection Certain unusual HTML documents resulted in browser monitoring injecting incorrect content. Thanks Alex McHale for the contribution! Specify the Content-Type header in developer mode Thanks Jared Ning for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-369171","eolDate":"2016-11-07"},{"agent":"ruby","date":"2013-10-19","downloadLink":null,"version":"3.6.8.168","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Percentiles and Histograms The Ruby Agent now captures data that provides percentile and histogram views in the New Relic UI. Missing Resque transaction traces A bug in 3.6.8.164 prevented transaction traces in Resque jobs from being communicated back to New Relic. 3.6.8.168 fixes this. Retry on initial connect. Failure to contact New Relic on agent start-up would not properly retry. This has been fixed. Fix potential memory leak on failure to send to New Relic. 3.6.8.164 introduced a potential memory leak when transmission of some kinds of data to New Relic servers failed. 3.6.8.168 fixes this.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-368168","eolDate":"2016-10-19"},{"agent":"ruby","date":"2013-10-09","downloadLink":null,"version":"3.6.8.164","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 X-Ray Sessions support X-Ray Sessions provide more targeted transaction trace samples and thread profiling for web transactions. For full details see our X-Ray sessions documentation at https://newrelic.com/docs/site/xray-sessions . CPU metrics re-enabled for JRuby >= 1.7.0 To work around a JRuby bug, the Ruby agent stopped gathering CPU metrics on that platform. With the bug fixed, the agent can gather those metrics again. Thanks Bram de Vries for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-368164","eolDate":"2016-10-09"},{"agent":"ruby","date":"2013-09-23","downloadLink":null,"version":"3.6.7.159","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Additional locking option for Resque There have been reports of worker process deadlocks in Resque when using the Ruby agent. An optional lock is now available to avoid those deadlocks. See https://newrelic.com/docs/ruby/resque-instrumentation  for more details. HTTP connection setup timeout HTTP initialization in the agent lacked an appropriate timeout, leading to dropouts in reporting under certain network error conditions. Unnecessary requests from Resque jobs An issue causing Resque jobs to unnecessarily make requests against New Relic servers was fixed.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-367159","eolDate":"2016-09-23"},{"agent":"ruby","date":"2013-09-09","downloadLink":null,"version":"3.6.7.152","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Resque-pool support Resque processes started via the resque-pool gem weren't recognized by the Ruby agent. The agent now starts correctly in those worker processes. Environment-based configuration All settings in newrelic.yml can now be configured via environment variables. See https://newrelic.com/docs/ruby/ruby-agent-configuration  for full details. Fix compatibility issues with excon and curb instrumentation This release of the agent fixes a warning seen under certain circumstances with the excon gem (most notably, when excon was used by fog), as well as a bug with the curb instrumentation that conflicted with the feedzirra gem. Allow license key to be set by Capistrano variables A license key can be passed via a Capistrano variable where previously it could only be in newrelic.yml. Thanks Chris Marshall for the contribution! Make HTTP client instrumentation aware of \"Host\" request header If a \"Host\" header is set explicitly on an HTTP request, that hostname will be used for external metrics. Thanks Mislav Marohnić for the contribution! Fix ActiveSupport::Concern warnings with MethodTracer Including NewRelic::Agent::MethodTracer in a class using Concerns could cause deprecation warnings. Thanks Mike Połtyn for the contribution! Fix Authlogic constant name Code checking for the Authlogic module was using in the wrong case. Thanks Dharam Gollapudi for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-367152","eolDate":"2016-09-09"},{"agent":"ruby","date":"2013-07-25","downloadLink":null,"version":"3.6.6.147","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 HTTPClient and Curb support The Ruby agent now supports the HTTPClient and Curb HTTP libraries! Cross application tracing and more is fully supported for these libraries. For more details see https://newrelic.com/docs/ruby/ruby-http-clients . Sinatra startup improvements In earlier agent versions, newrelic_rpm had to be required after Sinatra to get instrumentation. Now the agent should start when your Sinatra app starts up in rackup, thin, unicorn, or similar web servers. Puma clustered mode support Clustered mode in Puma was not reporting data without manually adding a hook to Puma's configuration. The agent will now automatically add this hook. SSL certificate verification Early versions of the agent's SSL support provided an option to skip certificate verification. This option has been removed.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-366147","eolDate":"2016-07-25"},{"agent":"ruby","date":"2013-06-27","downloadLink":null,"version":"3.6.5.130","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Rails 4.0 Support The Ruby agent is all set for the recent general release of Rails 4.0! We've been tracking the RC's, and that work paid off. Versions 3.6.5 and 3.6.4 of the Ruby agent should work fine with Rails 4.0.0. Excon and Typhoeus support The Ruby agent now supports the Excon and Typhoeus HTTP libraries! For more details see https://newrelic.com/docs/ruby/ruby-http-clients .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-365130","eolDate":"2016-06-27"},{"agent":"ruby","date":"2013-06-18","downloadLink":null,"version":"3.6.4.122","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Exception list We've improved exception message handling for applications running in high-security mode. Enabling 'high_security' now removes exception messages entirely rather than simply obfuscating any SQL. By default this feature affects all exceptions, although you can configure an allow list of exceptions for messages you want to remain intact. More details: https://newrelic.com/docs/ruby/ruby-agent-configuration Fix a race condition affecting some Rails applications at startup Some Rails applications using 'newrelic_rpm' were affected by a race condition at startup that manifested as an error when model classes with associations were first loaded. The cause of these errors has been addressed by moving the generation of the agent's 'EnvironmentReport' on startup from a background thread to the main thread.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-364122","eolDate":"2016-06-18"},{"agent":"ruby","date":"2013-05-30","downloadLink":null,"version":"3.6.3.111","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Better Sinatra Support A number of improvements have been made to our Sinatra instrumentation. More details: https://newrelic.com/docs/ruby/sinatra-support-in-the-ruby-agent Sinatra instrumentation has been updated to more accurately reflect the final route that was actually executed, taking pass and conditions into account. New Relic middlewares for error collection, real user monitoring, and cross application tracing are automatically inserted into the middleware stack. Ignoring routes, similar to functionality available to Rails controllers, is now available in Sinatra as well. Routes in 1.4 are properly formatting in transaction names. Thanks Zachary Anker for the contribution! Padrino Support Along with improving our support of Sinatra, we've also extended that to supporting Padrino, a framework that builds on Sinatra. Web transactions should show up in New Relic now for Padrino apps automatically. The agent has been tested against the latest Padrino in versions 0.11.x and 0.10.x. Main overview graph only shows web transactions In the past database times from background jobs mixed with other web transaction metrics in the main overview graph. This often skewed graphs. A common workaround was to send background jobs to a separate application, but that should no longer be necessary as the overview graphs now only represent web transactions.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-363111","eolDate":"2016-05-30"},{"agent":"ruby","date":"2013-05-09","downloadLink":null,"version":"3.6.2.96","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Sequel support The Ruby agent now supports Sequel, a database toolkit for Ruby. This includes capturing SQL calls and model operations in transaction traces, and recording slow SQL calls. See https://newrelic.com/docs/ruby/sequel-instrumentation  for full details. Thread profiling fix The prior release of the agent (version 3.6.1) broke thread profiling. A profile would appear to run, but return no data. This has been fixed. Fix for over-counted Net::HTTP calls Under some circumstances, calls into Net::HTTP were being counted twice in metrics and transaction traces. This has been fixed. Missing traced errors for Resque applications Traced errors weren't displaying for some Resque workers, although the errors were factored into the overall count graphs. This has been fixed, and traced errors should be available again after upgrading the agent.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-36296","eolDate":"2016-05-09"},{"agent":"ruby","date":"2013-04-29","downloadLink":null,"version":"3.6.1.88","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Full URIs for HTTP requests are recorded in transaction traces When recording a transaction trace node for an outgoing HTTP call via Net::HTTP, the agent will now save the full URI (instead of just the hostname) for the request. Embedded credentials, the query string, and the fragment will be stripped from the URI before it is saved. Simplify Agent Autostart Logic Previously the agent would only start when it detected a supported \"Dispatcher\", meaning a known web server or background task framework. This was problematic for customers using webservers that the agent was not configured to detect (e.g. Puma). Now the agent will attempt to report any time it detects it is running in a monitored environment (e.g. production). There are two exceptions to this. The agent will not autostart in a rails console or irb session or when the process was invoked by a rake task (e.g. rake assets:precompile). The NEWRELIC_ENABLE environment variable can be set to true or false to force the agent to start or not start. Don't attempt to resolve collector hostname when proxy is in use When a proxy is configured, the agent will not attempt to lookup and cache the IP address of New Relic server to which it is sending data, since DNS may not be available in some environments. Thanks to Bill Kirtley for the contribution Added NewRelic::Agent.set_transaction_name and NewRelic::Agent.get_transaction_name Ordinarily the name of your transaction is defined up-front, but if you'd like to change the name of a transaction while it is still running you can use NewRelic::Agent.set_transaction_name() . Similarly, if you need to know the name of the currently running transaction, you can use NewRelic::Agent.get_transaction_name() .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-36188","eolDate":"2016-04-29"},{"agent":"ruby","date":"2013-03-20","downloadLink":null,"version":"3.6.0.83","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Sidekiq supprt The Ruby agent now supports the Sidekiq background job framework. Traces from Sidekiq jobs will automatically show up in the Background tasks on New Relic similar to Resque and Delayed::Job tasks. Improved thread safety The primary metrics data structures in the Ruby agent are now thread safe. This should provide better reliability for the agent under JRuby and threaded scenarios such as Sidekiq or Puma. More robust environment report The agent's analysis of the local environment (e.g. OS, Processors, loaded gems) will now work in a wider variety of app environments, including Sinatra. Experimental Rainbows! support The Ruby agent now automatically detects and instruments the Rainbows! web server. This support is considered experimental at present, and has not been tested with all dispatch modes. Thanks to Joseph Chen for the contribution. Fix a potential file descriptor leak in Resque instrumentation A file descriptor leak that occurred when DontPerform exceptions were used to abort processing of a job has been fixed. This should allow the Resque instrumentation work correctly with the resque-lonely_job gem.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-36083","eolDate":"2016-03-20"},{"agent":"ruby","date":"2013-02-28","downloadLink":null,"version":"3.5.8.72","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Key Transactions The Ruby agent now supports Key Transactions! Check out more details on the feature at https://newrelic.com/docs/site/key-transactions . Ruby 2.0 The Ruby agent is compatible with Ruby 2.0.0 which was just released. Improved Sinatra instrumentation Several cases around the use of conditions and pass in Sinatra are now better supported by the Ruby agent. Thanks Konstantin for the help! Cross Application Tracing See https://newrelic.com/docs/features/cross-application-traces  for details. Adds a 'X-NewRelic-ID' header to outbound Net::HTTP requests. This change helps improve the correlation of performance between services in a service- oriented architecture. Automatically detect Resque dispatcher The agent does better auto-detection for the Resque worker process. This should reduce the need to set NEW_RELIC_DISPATCHER=resque directly.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-35872","eolDate":"2016-02-28"},{"agent":"ruby","date":"2013-02-20","downloadLink":null,"version":"3.5.7.59","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Resolved some issues with tracking of frontend queue time, particularly when the agent is running on an app hosted on Heroku. The agent will now more reliably parse the headers described in https://newrelic.com/docs/features/tracking-front-end-time  and will automatically detect whether the times provided are in seconds, milliseconds or microseconds.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-35759","eolDate":"2016-02-20"},{"agent":"ruby","date":"2013-02-14","downloadLink":null,"version":"3.5.6.55","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Use HTTPS by default The agent now defaults to using SSL when it communicates with New Relic's servers. By defaults already configured, New Relic does not transmit any sensitive information (e.g. SQL parameters are masked), but SSL adds another layer of security. Upgrading customers may need to remove the \"ssl: false\" directive from their newrelic.yml to enable ssl. Customers on Jruby may need to install the jruby-openssl gem to take advantage of this feature. Fix two Resque-related issues Fixes a possible hang on exit of an instrumented Resque master process (https://github.com/resque/resque/issues/578 ), as well as a file descriptor leak that could occur during startup of the Resque master process. Fix for error graph over 100% Some errors were double counted toward the overall error total. This resulted in graphs with error percentages over 100%. This duplication did not impact the specific error traces captured, only the total metric. Notice gracefully handled errors in Sinatra When show_exceptions was set to false in Sinatra, errors weren't caught by New Relic's error collector. Now handled errors also have the chance to get reported back. Ruby 2.0 compatibility fixes Ruby 2.0 no longer finds protected methods by default, but will with a flag. http://tenderlovemaking.com/2012/09/07/protected-methods-and-ruby-2-0.html Thanks Ravil Bayramgalin and Charlie Somerville for the fixes. Auto-detect Trinidad as dispatcher Code already existing for detecting Trinidad as a dispatcher, but was only accessible via an ENV variable. This now auto-detects on startup. Thanks Robert Rasmussen for catching that. Coercion of types in collector communication Certain metrics can be recorded with a Ruby Rational type, which JSON serializes as a string rather than a floating point value. We now treat coerce each outgoing value, and log issues before sending the data. Developer mode fix for chart error Added require to fix a NameError in developer mode for summary page. Thanks to Ryan B. Harvey. Don't touch deprecated RAILS_ROOT if on Rails 3 Under some odd startup conditions, we would look for the RAILS_ROOT constant after failing to find the ::Rails.root in a Rails 3 app, causing deprecation warnings. Thanks for Adrian Irving-Beer for the fix.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-35655","eolDate":"2016-02-14"},{"agent":"ruby","date":"2013-01-09","downloadLink":null,"version":"3.5.5.38","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Add thread profiling support Thread profiling performs statistical sampling of backtraces of all threads within your Ruby processes. This feature requires CRuby >= 1.9.2, and is controlled via the New Relic web UI. JRuby support (in 1.9.x compat mode) is considered experimental, due to issues with JRuby's Thread#backtrace. Add audit logging capability The agent can now log all of the data it sends to the New Relic servers to a special log file for human inspection. This feature is off by default, and can be enabled by setting the audit_log.enabled configuration key to true. You may also control the location of the audit log with the audit_log.path key. Use config system for dispatcher, framework, and config file detection Several aspects of the agent's configuration were not being handled by the configuration system. Detection/configuration of the dispatcher (e.g. passenger, unicorn, resque), framework (e.g. rails3, sinatra), and newrelic.yml location are now handled via the Agent environment, manual, and default configuration sources. Updates to logging across the agent We've carefully reviewed the logging messages that the agent outputs, adding details in some cases, and removing unnecessary clutter. We've also altered the startup sequence to ensure that we don't spam STDOUT with messages during initialization. Fix passing environment to manual_start() Thanks to Justin Hannus. The :env key, when passed to Agent.manual_start, can again be used to specify which section of newrelic.yml is loaded. Rails 4 support This release includes preliminary support for Rails 4 as of 4.0.0.beta. Rails 4 is still in development, but the agent should work as expected for people who are experimenting with the beta.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-35538","eolDate":"2016-01-09"},{"agent":"ruby","date":"2012-12-26","downloadLink":null,"version":"3.5.4.34","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Fix incompatibility with logging gem by renaming NewRelic::Agent::Thread to NewRelic::Agent::AgentThread.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-35434","eolDate":"2015-12-26"},{"agent":"ruby","date":"2012-12-18","downloadLink":null,"version":"3.5.4.33","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Add queue time support for sinatra apps Sinatra applications can now take advantage of frontend queue time reporting. Thanks to Winfield Peterson for this contribution. Simplify queue time configuration for nginx 1.2.6+ Beginning in version 1.2.6, recently released as a development version, the $msec variable can be used to set an http header. This change allows frontend queue time to be tracked in New Relic simply by adding this line to the nginx config: proxy_set_header X-Queue-Start \"t=${msec}000\" It will no longer be necessary to compile a patched version of nginx or compile in the perl or lua module to enable this functionality. Thanks to Lawrence Pit for the contribution. Report back build number and stage along with version info In the 3.5.3 series the agent would fail to report its full version number to NewRelic's environment report. For example it would report its version as 3.5.3 instead of 3.5.3.25 or 3.5.3.25.beta. The agent will now report its complete version number as defined in newrelic_rpm.gemspec. The host and the port that the agent reports to can now be set from environment vars The host can be set with NEW_RELIC_HOST and the port with NEW_RELIC_PORT. These setting will overrride any other settings in your newrelic.yml. Fix RUM reporting to multiple applications When the agent is configured to report to multiple \"roll up\" applications RUM did not work correctly.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-35433","eolDate":"2015-12-18"},{"agent":"ruby","date":"2012-12-05","downloadLink":null,"version":"3.5.3.25","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Update the collector protocol to use JSON and Ruby primitives The communication between the agent and the NewRelic will not longer be marshaled Ruby objects, but rather JSON in the case of Ruby 1.9 and marshaled Ruby primitives in the case of 1.8. This results in greater harvest efficiency as well as feature parity with other New Relic agents. Fix incorrect application of conditions in sinatra instrumentation The agent's sinatra instrumentation was causing sinatra's condidtions to be incorrectly applied in some obscure cases. The bug was triggered when a condition was present on a lower priority route that would match the current request, except for the presence of a higher priority route.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-35325","eolDate":"2015-12-05"},{"agent":"ruby","date":"2012-11-15","downloadLink":null,"version":"3.5.2.17","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Simplified process of running agent test suite and documented code contribution process in GUIDELINES_FOR_CONTRIBUTING .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-35217","eolDate":"2015-11-15"},{"agent":"ruby","date":"2012-11-13","downloadLink":null,"version":"3.5.1.14","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Enabling Memory Profiling on Lion and Mountain Lion The agent's list of supported platforms for memory profiling wasn't correctly checking for more recent versions of OS X. Fixed an arity issue encountered when calling newrelic_notice_error from Rails applications. End user queue time was not being properly reported, works properly now. Server-side configuration for ignoring errors was not being heeded by agent. Better handling of a thread safety issue. Some issues may remain, which we are working to address, but they should be gracefully handled now, rather than crashing the running app. Use \"java_import\" rather than \"include_class\" when require Java Jars into a JRuby app. Thanks to Jan Habermann for the pull request Replaced alias_method mechanism with super call in DataMapper instrumentation. Thanks to Michael Rykov for the pull request Fixed the Rubinius GC profiler. Thanks to Dirkjan Bussink Use ActiveSupport.on_load to load controller instrumentation Rails 3. Thanks to Jonathan del Strother Reduce the number of thread local reference in a particular high traffic method Thanks to Jeremy Kemper","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-35114","eolDate":"2015-11-13"},{"agent":"ruby","date":"2012-10-23","downloadLink":null,"version":"3.5.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes (performance) Gradual slowdown on Phusion Passenger This release resolves a performance issue that effected sites running on some versions of Phusion Passenger. The issue manifests as a slow degradation of response time and increased CPU usage. This issue was only present in version 3.5.0 of the agent. Drop support for Passenger versions less than 2.1.1 In order to implement the above fix we have dropped official support for Passenger versions 2.1.0 and older. These early versions of Passenger do not support an after_fork event which is necessary for the smooth operation of the agent.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3501","eolDate":"2015-10-23"},{"agent":"ruby","date":"2012-10-09","downloadLink":null,"version":"3.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes (Fix) RUM Stops Working After 3.4.2.1 Agent Upgrade v3.4.2.1 introduced a bug that caused the browser monitor auto instrumentation (for RUM) default to be false. The correct value of true is now used When the Ruby Agent detects Unicorn as the dispatcher it creates an INFO level log message with additional information To help customers using Unicorn, if the agent detects it (Unicorn) is being used as the dispatcher an INFO level log message it created that includes a link to New Relic online doc that has additional steps that may be required to get performance data reporting. (Fix) In version 3.4.2 of the Ruby Agent the server side value for Apdex T was disgregarded With version 3.4.2 of the agent, the value set in the newrelic.yml file took precedence over the value set in the New Relic UI. As of version 3.5.0 only the value for Apdex T set in the New Relic UI will be used. Any setting in the yaml file will be ignored. Improved Error Detection/Reporting capabilities for Rails 3 apps Some errors are missed by the agent's exception reporting handlers because they are generated in the rails stack, outside of the instrumented controller action. A Rack middleware is now included that can detect these errors as they bubble out of the middleware stack. Note that this does not include Routing Errors. The Ruby Agent now logs certain information it receives from the New Relic servers After connecting to the New Relic servers the agent logs the New Relic URL of the app it is reporting to. GC profiling overhead for Ruby 1.9 reduced For Ruby 1.9 the amount of time spent in GC profiling has been reduced. Know issue with Ruby 1.8.7-p334, sqlite3-ruby 1.3.0 or older, and resque 1.23.0 The Ruby Agent will not work in conjunction with Ruby 1.8.7-p334, sqlite3-ruby 1.3.3 or earlier, and resque 1.23.0. Your app will likely stop functioning. This is a known problem with Ruby versions up to 1.8.7-p334. Upgrading to the last release of Ruby 1.8.7 is recommended. This issue has been present in every version of the agent we've tested going back for a year.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-350","eolDate":"2015-10-09"},{"agent":"ruby","date":"2012-09-13","downloadLink":null,"version":"3.4.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Fix issue when app_name is nil If the app_name setting ends up being nil an exception got generated and the application wouldn't run. This would notably occur when running a Heroku app locally without the NEW_RELIC_APP_NAME environment variable set. A nil app_name is now detected and an error logged specifying remediation.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3421","eolDate":"2015-09-13"},{"agent":"ruby","date":"2012-09-06","downloadLink":null,"version":"3.4.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Support for Apdex T in server side configuration For those using server side configuration the Ruby Agent now supports setting the Apdex T value via the New Relic UI. The RUM NRAGENT tk value gets more robustly sanitized to prevent potential XSS vulnerabilities The code that scrubs the token used in Real User Monitoring has been enhanced to be more robust. Refactoring of agent config code The code that reads the configuration information and configures the agent got substantially reorganized, consolidated, simplified, and made more robust.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-342","eolDate":"2015-09-06"},{"agent":"ruby","date":"2012-07-26","downloadLink":null,"version":"3.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bug Fixes Fix edge case in RUM auto instrumentation where X-UA-Compatible meta tag is present but </head> tag is missing. There is a somewhat obscure edge case where RUM auto instrumentation will crash a request. The issue seems to be triggered when the X-UA-Compatible meta tag is present and the </head> tag is missing. Fixed reference to @service.request_timeout to @request_timeout in new_relic_service.rb. (Thanks to Matthew Savage) When a timeout occurred during connection to the collector an \"undefined method request_timeout for nil:NilClass\" would get raised. preserve visibility on traced methods. Aliased methods now have the same visibility as the original traced method. A couple of the esoteric methods created in the process weren't getting the visibility set properly. Agent service does not connect to directed shard collector after connecting to proxy After connecting to collector proxy name of real collector was updated, but ip address was not being updated causing connections to go to the proxy. Agent now looks up ip address for real collector. corrupt marshal data from pipe children crashing agent If the agent received corrupted data from the Reqsue worker child agent it could crash the agent itself. fixed. should reset RubyBench GC counter between polls On Ruby REE, the GC profiler does not reset the counter between polls. This is only a problem if GC could happen between  transactions, as in, for example, out-of-band GC in Unicorn. fixed.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-341","eolDate":"2015-07-26"},{"agent":"ruby","date":"2012-06-27","downloadLink":null,"version":"3.4.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Prevent the agent from resolving the collector address when disabled. Fix for error collector configuration that was introduced during beta.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3401","eolDate":"2015-06-27"},{"agent":"ruby","date":"2012-06-04","downloadLink":null,"version":"3.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Feature(s) Major refactor of data transmission mechanism. This enabled child processes to send data to parent processes, which then send the data to the New Relic service. This should only affect Resque users, dramatically improving their experience. Bug Fixes Resolve issue with configuring the Error Collector when using server-side configuration. Changes Moved Resque instrumentation from rpm_contrib to main agent. Resque users should discontinue use of rpm_contrib or upgrade to 2.1.11.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-340","eolDate":"2015-06-04"},{"agent":"ruby","date":"2012-05-31","downloadLink":null,"version":"3.3.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Replaced \"Custom/DJ Locked Jobs\" metric with three new metrics for monitoring DelayedJob: queue_length, failed_jobs, and locked_jobs, all under Workers/DelayedJob Fix allowing instrumentation of methods ending in '?' or '!' Limit scanning first 50k of the response in RUM auto-instrumentation. Fix keeping exception from being raised when when extracting metrics from SQL queries with non UTF-8 bytes","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-335","eolDate":"2015-05-31"},{"agent":"ruby","date":"2012-04-26","downloadLink":null,"version":"3.3.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Bug fix when rendering empty collection in Rails 3.1+","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3341","eolDate":"2015-04-26"},{"agent":"ruby","date":"2012-04-19","downloadLink":null,"version":"3.3.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Rails 3 view instrumentation","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-334","eolDate":"2015-04-19"},{"agent":"ruby","date":"2012-03-29","downloadLink":null,"version":"3.3.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Improved Sinatra instrumentation Limit the number of nodes collected in long running transactions to prevent leaking memory","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-333","eolDate":"2015-03-29"},{"agent":"ruby","date":"2012-03-15","downloadLink":null,"version":"3.3.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . fix for cookie handling by End User Monitoring instrumentation","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3321","eolDate":"2015-03-15"},{"agent":"ruby","date":"2012-02-16","downloadLink":null,"version":"3.3.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . deployments recipe change: truncate git SHAs to 7 characters Fixes for obfuscation of PostgreSQL and SQLite queries Fix for lost database connections when using a forking framework Workaround for RedHat kernel bug which prevented blocking reads of /proc fs Do not trap signals when handling exceptions","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-332","eolDate":"2015-02-16"},{"agent":"ruby","date":"2011-12-15","downloadLink":null,"version":"3.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Performance and stability improvements Restored compatibility with Ruby 1.8.6","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-331","eolDate":"2014-12-15"},{"agent":"ruby","date":"2011-11-07","downloadLink":null,"version":"3.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New slow SQL tracing feature New expanded browser tracing","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-330","eolDate":"2014-11-07"},{"agent":"ruby","date":"2011-10-13","downloadLink":null,"version":"3.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Yet more work on Delayed Job instrumentation Threading fixes More Heroku friendly logging system","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-320","eolDate":"2014-10-13"},{"agent":"ruby","date":"2017-02-09","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-3.18.1.330.gem","version":"3.18.1.330","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v3.18.1 Ensure Mongo aggregate queries are properly obfuscated Instrumentation for the Mongo 2.x driver had a bug where the pipeline attribute of Mongo aggregate queries was not properly obfuscated. Users who have sensitive data in their aggregate queries are strongly encouraged to upgrade to this version of the agent. Users who are unable to upgrade are encouraged to turn off query collection using by setting mongo.capture_queries to false in their newrelic.yml files. This release fixes New Relic Security Bulletin NR17-03 . Early access Redis 4.0 instrumentation Our Redis instrumentation has been tested against Redis 4.0.0.rc1.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3181330","eolDate":"2020-02-09"},{"agent":"ruby","date":"2017-01-23","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-3.18.0.329.gem","version":"3.18.0.329","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v3.18.0 Ruby 2.4.0 support The agent is now tested against the official release of ruby 2.4.0, excluding incompatible packages. Agent-based metrics will not be recorded outside of active transactions The agent has historically recorded metrics outside of a transaction. In practice, this usually occurs in applications that run background job processors. The agent would record metrics for queries the background job processor is making between transactions. This can lead to display issues on the background overview page and the presence of metrics generated by the background job processor can mask the application generated metrics on the database page. The agent will no longer generate metrics outside of a transaction. Custom metrics recorded using NewRelic::Agent.record_metric will continue to be recorded regardless of whether there is an active transaction. Include ControllerInstrumentation module with ActiveSupport.on_load The agent will now use the on_load :action_controller hook to include the ControllerInstrumentation module in to both the Base and API classes of ActionController for Rails 5. This ensures that the proper load order is retained, minimizing side-effects of having the agent in an application. Ensure values for revisions on Capistrano deploy notices Previously, running the task to look up the changelog could generate an error, if there weren't previous and current revisions defined. This has now been fixed. Thanks Winfield Peterson for the contribution! External Segment Rewrites The agent has made internal changes to how it represents segments for external web requests.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3180329","eolDate":"2020-01-23"},{"agent":"ruby","date":"2016-12-13","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-3.17.2.327.gem","version":"3.17.2.327","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v3.17.2 Compatibility with Ruby 2.4.0-preview3 The Ruby agent has been updated to work on Ruby 2.4.0-preview3. Early Access Sinatra 2.0 instrumentation Our Sinatra instrumentation has been updated to work with Sinatra 2.0.0.beta2. Include controller instrumentation module in Rails 5 API The agent now includes the ControllerInstrumentation module into ActionController::API. This gives Rails API controllers access to helper methods like newrelic_ignore in support of the existing event-subscription-based action instrumentation. Thanks Andreas Thurn for the contribution! Use Module#prepend for ActiveRecord 5 Instrumentation Rails 5 deprecated the use of alias_method_chain in favor of using Module#prepend. Mixing Module#prepend and alias_method_chain can lead to a SystemStackError when an alias_method_chain is applied after a module has been prepended. This should ensure better compatibility between our ActiveRecord Instrumentation and other third party gems that modify ActiveRecord using Module#prepend. Use license key passed in to NewRelic::Agent.manual_start Previously, the license key passed in when manually starting the agent with NewRelic::Agent.manual_start was not referenced when setting up the connection to report data to New Relic. This is now fixed. Account for DataMapper database connection errors Our DataMapper instrumentation traces instances of DataObjects::SQLError being raised and removes the password from the URI attribute. However, when DataObjects cannot connect to the database (ex: could not resolve host), it will raise a DataObjects::ConnectionError. This inherits from DataObjects::SQLError but has nil for its URI attribute, since no connection has been made yet. To avoid the password check here on nil, the agent catches and re-raises any instances of DataObjects::ConnectionError explicitly. Thanks Postmodern for this contribution! Account for request methods that require arguments When tracing a transaction, the agent tries to get the request object from a controller if it wasn't explicitly passed in. However, this posed problems in non-controller transactions with their own request methods defined that required arguments, such as in Resque jobs. This is now fixed.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3172327","eolDate":"2019-12-13"},{"agent":"ruby","date":"2016-11-08","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-3.17.1.326.gem","version":"3.17.1.326","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v3.17.1 Datastore instance reporting for Redis, MongoDB, and memcached The agent now collects datastore instance information for Redis, MongoDB, and memcached. This information is displayed in transaction traces and slow query traces. For memcached only, multi requests will expand to individual server nodes, and the operation and key(s) will show in the trace details \"Database query\" section. Metrics for get_multi nodes will change slightly. Parent nodes for a get_multi will be recorded as generic segments. Their children will be recorded as datastore segments under the name get_multi_request and represent a batch request to a single Memcached instance. Rescue errors from attempts to fetch slow query explain plans For slow queries through ActiveRecord 4+, the agent will attempt to fetch an explain plan on SELECT statements. In the event that this causes an error, such as being run on an adapter that doesn't implement exec_query, the agent will now rescue and log those errors. n","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3171326","eolDate":"2019-11-08"},{"agent":"ruby","date":"2016-10-18","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.17.0.325","version":"3.17.0.325","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v3.17.0 Datastore instance reporting for ActiveRecord The agent now collects database instance information  for ActiveRecord operations, when using the MySQL and Postgres adapters. This information (database server and database name) is displayed in transaction traces and slow query traces. For more information, see Ruby instance-level database information .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3170325","eolDate":"2019-10-18"},{"agent":"ruby","date":"2016-09-27","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.16.3.323","version":"3.16.3.323","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Add :trace_only option to notice_error API Previously, calling notice_error would record the trace, increment the error count, and consider the transaction failing for Apdex purposes. This method now accepts a :trace_only boolean option which, if true, will only record the trace and not affect the error count or transaction. HTTP.rb support The agent has been updated to add instrumentation support for the HTTP gem, including Cross Application Tracing. Thanks Tiago Sousa for the contribution! Prevent redundant Delayed::Job instrumentation installation This change was to handle situations where multiple Delayed::Worker instances are being created but Delayed::Job has already been instrumented. Thanks Tony Brown for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3163323","eolDate":"2019-09-27"},{"agent":"ruby","date":"2016-08-22","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.16.2.321","version":"3.16.2.321","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v3.16.2 Fix for \"Unexpected frame in traced method stack\" errors Our ActiveRecord 4.x instrumentation could have generated \"Unexpected frame in traced method stack\" errors when used outside of an active transaction (for example, in custom background job handlers). This has been fixed.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3162321","eolDate":"2019-08-22"},{"agent":"ruby","date":"2016-08-15","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.16.1.320","version":"3.16.1.320","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v3.16.1 Internal datastore instrumentation rewrites The agent's internal tracing of datastore segments has been rewritten, and instrumentation updated to utilize the new classes. Fix Grape endpoint versions in transaction names Grape 0.16 changed Route#version (formerly #route_version) to possibly return an Array of versions for the current endpoint. The agent has been updated to use rack.env['api.version'] set by Grape, and fall back to joining the version Array with '|' before inclusion in the transaction name when api.version is not available. Thanks Geoff Massanek for the contribution! Fix deprecation warnings from various Rails error subclasses Rails 5 deprecates #original_exception on a few internal subclasses of StandardError in favor of Exception#cause from Ruby stdlib. The agent has been updated to try Exception#cause first, thus avoiding deprecation warnings. Thanks Alexander Stuart-Kregor for the contribution! Fix instrumentation for Sequel 4.35.0 The latest version of Sequel changes the name and signature of the method that the Ruby Agent wraps for instrumentation. The agent has been updated to handle these changes. Users using Sequel 4.35.0 or newer should upgrade their agent. Fix DataMapper instrumentation for additional versions Different versions of DataMapper have different methods for retrieving the adapter name, and Postmodern expanded our coverage. Thanks for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3161320","eolDate":"2019-08-15"},{"agent":"ruby","date":"2016-06-27","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.16.0.318","version":"3.16.0.318","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v3.16.0 Official Rails 5.0 support This version of the agent has been verified against the Rails 5.0.0 release. Early access Action Cable instrumentation The Ruby agent instruments Action Cable channel actions and calls to ActionCable::Channel#Transmit in Rails 5. Feedback is welcome! Obfuscate queries from oracle_enhanced adapter correctly This change allows the oracle_enhanced adapter to use the same obfuscation as oracle adapters. Thanks Dan Drinkard for the contribution! Make it possible to define a newrelic_role for deployment with Capistrano 3 Thanks NielsKSchjoedt for the contribution! Retry initial connection to New Relic in Resque master if needed Previously, if the initial connection to New Relic in a monitored Resque master process failed, the agent would not retry, and monitoring for the process would be lost. This has been fixed, and the agent will continue retrying in its background harvest thread until it successfully connects.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3160","eolDate":"2019-06-27"},{"agent":"ruby","date":"2016-04-25","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.15.2.317","version":"3.15.2.317","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v3.15.2 Run explain plans on parameterized slow queries in AR4 In our ActiveRecord 4 instrumentation, we moved to tracing slow queries using the payloads from ActiveSupport::Notifications sql.active_record events. As a result, we were unable to run explain plans on parameterized queries. This has now been updated to pass along and use the parameter values, when available, to get the explain plans. Fix getMore metric grouping issue in Mongo 2.2.x instrumentation A metric grouping issue had cropped up when using the most recent Mongo gem (2.2.0) with the most recent release of the server (3.2.4). We now have a more future-proof setup for preventing these. Restore older DataMapper support after password obfuscation fix Back in 3.14.3, we released a fix to avoid inadvertently sending sensitive information from DataMapper SQLErrors. Our implementation did not account for DataMapper versions below v0.10.0 not implementing the #options accessor. Thanks Bram de Vries for the fix to our fix! Padrino 0.13.1 Support Users with Padrino 0.13.x apps were previously seeing the default transaction name \"(unknown)\" for all of their routes. We now provide the full Padrino route template in transaction names, including any parameter placeholders. Thanks Robert Schulze for the contribution! Update transaction naming for Grape 0.16.x In Grape 0.16.x, route_ methods are no longer prefixed. Thanks to Daniel Doubrovkine for the contribution! Fix name collision on method created for default metric name fix We had a name collision with the yard gem, which sets a class_name method on Module. We've renamed our internal method to derived_class_name instead.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3152317","eolDate":"2019-04-25"},{"agent":"ruby","date":"2016-03-24","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.15.1.316","version":"3.15.1.316","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"v3.15.1 Rack 2 alpha support This release includes experimental support for Rack 2 as of 2.0.0.alpha. Rack 2 is still in development, but the agent should work as expected for those who are experimenting with Rack 2. Rails 5 beta 3 support We've tweaked our Action View instrumentation to accommodate changes introduced in Rails v5.0.0.beta3. Defer referencing ::ActiveRecord::Base to avoid triggering its autoloading too soon In 3.12.1 and later versions of the agent, the agent references (and therefore loads) ActiveRecord::Base earlier on in the Rails loading process. This could jump ahead of initializers that should be run first. We now wait until ActiveRecord::Base is loaded elsewhere. Fix explain plans for non-parameterized queries with single quote literals The agent does not run explain plans for queries still containing parameters (such as SELECT * FROM UNICORNS WHERE ID = $1 LIMIT 1). This check was unfortunately mutating the query to be obfuscated, causing an inability to collect an explain plan. This has now been fixed. Fix default metric name for tracing class methods When using add_method_tracer on a class method but without passing in a metric_name_code, the default metric name will now look like Custom/ClassName/Class/method_name. We also addressed default metric names for anonymous classes and modules. Fix issue when rendering SQL strings in developer mode When we obfuscate SQL statements, we rewrite the Statement objects as SQL strings inline in our sample buffers at harvest time. However, in developer mode, we also read out of these buffers when rendering pages. Depending on whether a harvest has run yet, the buffer will contain either Statement objects, SQL strings, or a mix. Now, developer mode can handle them all! Fix DelayedJob Sampler reporting incorrect counts in Active Record 3 and below When fixing various deprecation warnings on ActiveRecord 4, we introduced a regression in our DelayedJob sampler which caused us to incorrectly report failed and locked job counts in ActiveRecord 3 and below. This is now fixed. Thanks Rangel Dokov for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3151316","eolDate":"2019-03-24"},{"agent":"ruby","date":"2016-02-17","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.15.0.314","version":"3.15.0.314","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Rails 5 support This release includes experimental support for Rails 5 as of 5.0.0.beta2. Please note that this release does not include any support for ActionCable, the WebSockets framework new to Rails 5. Don't include extension from single format Grape API transaction names Starting with Grape 0.12.0, an API with a single format no longer declares methods with .:format, but with an extension such as .json. Thanks Daniel Doubrovkine for the contribution! Fix warnings about shadowing outer local variable when running tests Thanks Rafael Almeida de Carvalho for the contribution! Check config first for Rails middleware instrumentation installation Checking the config first avoids issues with mock classes that don't implement VERSION. Thanks Jesse Sanford for the contribution! Remove a trailing whitespace in the template for generated newrelic.yml Thanks Paul Menzel for the contribution! Reference external resources in comments and readme with HTTPS Thanks Benjamin Quorning for the contribution!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3150314","eolDate":"2019-02-17"},{"agent":"ruby","date":"2016-02-09","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.14.3.313","version":"3.14.3.313","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Don't inadvertently send sensitive information from DataMapper SQLErrors DataObjects::SQLError captures the SQL query, and when using versions of data_objects prior to 0.10.8, built a URI attribute that contained the database connection password. The :query attribute now respects the obfuscation level set for slow SQL traces and splices out any password parameters to the URI when sending up traced errors to New Relic. Improved SQL obfuscation algorithm To help standardize SQL obfuscation across New Relic language agents, we've improved the algorithm used and added more test cases. Configurable longer sql_id attribute on slow SQL traces The sql_id attribute on slow SQL traces is used to aggregate normalized queries together. Previously, these IDs would generally be 9-10 digits long, due to a backend restriction. If slow_sql.use_longer_sql_id is set to true, these IDs will now be 18-19 digits long.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3143313","eolDate":"2019-02-09"},{"agent":"ruby","date":"2016-01-25","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.14.2.312","version":"3.14.2.312","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Improved transaction names for Sinatra The agent will now use sinatra.route for transaction names on Sinatra 1.4.3+, which sets it in the request environment. This gives names that closer resemble the routes defined in the Sinatra DSL. Thanks to Brian Phillips for the suggestion! Bugfix for error flag on transaction events There was an issue causing the error flag to always be set to false for Insights transaction events that has been fixed. Official support for Sidekiq 4 The Ruby agent now officially supports Sidekiq 4. Additional attributes collected The agent now collects the following information in web transactions: Content-Length HTTP response and Content-Type HTTP request headers.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3142312","eolDate":"2019-01-25"},{"agent":"ruby","date":"2015-12-10","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.14.1.311","version":"3.14.1.311","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Add support for setting a display name on hosts You can now configure a display name for your hosts using process_host.display_name, to more easily distinguish dynamically assigned hosts. For more info, see Change display name of hosts Fixes automatic middleware instrumentation for Puma 2.12.x Starting with version 2.12.x the Puma project inlines versions of Rack::Builder and Rack::URLMap under the Puma namespace. This had the unfortunate side effect of breaking automatic Rack middleware instrumentation. We now instrument Puma::Rack::Builder and Puma::Rack::URLMap and once again have automatic Rack middleware instrumentation for applications running on Puma. Do not use a DelayedJob's display_name for naming the transaction A DelayedJob's name may be superseded by a display_name, which can lead to a metric grouping issue if the display_name contains unique identifiers. We no longer use job name methods that may lead to an arbitrary display_name. Instead, we use the appropriate class and/or method names, depending what makes sense for the job and how it's called. Improvements to Mongo 2.1.x instrumentation Fixes issue where getMore operations in batched queries could create metric grouping issues. Previously when multiple Mongo queries executed in the same scope only a single query was recorded as part of a transaction trace. Now transaction trace nodes will be created for every query executed during a transaction. Bugfix for NewRelic::Agent.notice_error Fixes issue introduced in v3.14.0 where calling NewRelic::Agent.notice_error outside of an active transaction results in a NoMethodError. Bugfix for Resque Transaction Error events Fixes error preventing Transaction Error events generated in Resque tasks from being sent to New Relic.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3141311","eolDate":"2018-12-10"},{"agent":"ruby","date":"2015-10-19","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-3.14.0.305.gem","version":"3.14.0.305","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes pruby  marshaller removed The deprecated pruby marshaller has now been removed; the marshaller config option now only accepts json. Customers still running Ruby 1.8.7/REE must add the json gem to their Gemfile, or (preferably) upgrade to Ruby 1.9.3 or higher. Log dates in ISO 8601 format The agent will now log dates in ISO 8601 (YYYY-MM-DD) format, instead of MM/DD/YY. Additional attributes collected The agent now collects the following information in web transactions: Accept, Host, User-Agent, Content-Length HTTP request headers, HTTP request method, and Content-Type HTTP response header. TransactionErrors reported for APM error advanced analytics With this release, the agent reports TransactionError events. These new events power the beta feature Advanced Analytics for APM errors. The error events are also available today through New Relic Insights. Advanced Analytics for APM errors lets you see all of your errors, with granular detail. Filter and group by any attribute to analyze them. Take action to resolve issues through collaboration. For more information, see View APM errors and error traces .","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3140305","eolDate":"2018-10-19"},{"agent":"ruby","date":"2015-09-28","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-3.13.2.302.gem","version":"3.13.2.302","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes Don't fail to send data when using mathn  library Version 3.12.1 introduced a bug with applications using the mathn  library that would prevent the agent from sending data to New Relic. This has been fixed.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3132302","eolDate":"2018-09-28"},{"agent":"ruby","date":"2015-09-21","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.13.1.300","version":"3.13.1.300","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Don't use a pager when running git log command This would cause Capistrano deploys to hang when a large number of commits were being deployed. Thanks to John Naegle for reporting and fixing this issue! Official support for JRuby 9.0.0.0 The Ruby agent is now officially fully tested and supported on JRuby 9.0.0.0. Instrumentation for MongoDB 2.1.x Visibility in your MongoDB queries returns when using version 2.1.0 of the Mongo driver or newer. Thanks to Durran Jordan of MongoDB for contributing the Mongo Monitoring instrumentation! Fix for ArgumentError \"invalid byte sequence in UTF-8\" This would come up when trying to parse out the operation from a database query containing characters that would trigger a invalid byte sequence in UTF-8 error. Thanks to Mario Izquierdo for reporting this issue! Improved database metric names for ActiveRecord::Calculations queries Aggregate metrics recorded for queries made via the ActiveRecord::Calculations module (#count, #sum, #max, etc.) will now be associated with the correct model name, rather than being counted as generic 'select' operations. Allow at_exit handlers to be installed for Rubinius Rubinius can support the at_exit block used by install_exit_handler. Thanks to Aidan Coyle for reporting and fixing this issue!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3131300","eolDate":"2018-09-21"},{"agent":"ruby","date":"2015-08-10","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-3.13.0.299.gem","version":"3.13.0.299","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Bugfix for uninitialized constant NewRelic::Agent::ParameterFiltering Users in some environments encountered a NameError: uninitialized constant NewRelic::Agent::ParameterFiltering from the Rails instrumentation while running v3.12.x of the Ruby agent. This issue has been fixed. Rake task instrumentation The Ruby agent now provides opt-in tracing for Rake tasks. If you run long jobs via Rake, you can get all the visibility and goodness of New Relic that your other background jobs have. For more information, see Rake instrumentation . Redis instrumentation Redis operations will now show up on the Databases tab and in transaction traces. By default, only command names will be captured; to capture command arguments, set transaction_tracer.record_redis_arguments to true in your configuration. For more information, see Redis instrumentation . Fix for over-obfuscated SQL Traces and PostgreSQL An issue with the agent obfuscating column and table names from Slow SQL Traces when using PostgreSQL has been resolved. Rubinius 2.5.8 VM metric renaming support Rubinius 2.5.8 changed some VM metric names and eliminated support for total allocated object counters. The agent has been updated accordingly. Fix agent attributes with a value of false not being stored An issue introduced in v3.12.1 prevented attributes (like those added with add_custom_attributes) from being stored if their value was false. This has been fixed.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3130","eolDate":"2018-08-10"},{"agent":"ruby","date":"2015-06-30","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.12.1.298","version":"3.12.1.298","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes More granular Database metrics for ActiveRecord 3 and 4 Database metrics recorded for non-SELECT operations (UPDATE, INSERT, DELETE, etc.) on ActiveRecord 3 and 4 now include the model name that the query was being executed against, allowing you to view these queries broken down by model on the Datastores page. Thanks to Bill Kayser for reporting this issue! Support for Multiverse testing third party gems The Ruby agent has rich support for testing multiple gem versions, but previously that wasn't accessible to third party gems. Now you can now simply require 'task/multiverse' in your Rakefile to access the same test:multiverse task that New Relic uses itself. For more details, see Multiverse: Test against multiple gem versions Use Sidekiq 3.x's error handler Sidekiq versions 3.0 or higher provide an error handler for internal and middleware related failures. Failures at these points were previously unseen by the Ruby agent, but now they are properly traced. Better error messages for common configuration problems with Capistrano Templating errors in newrelic.yml  would result in obscure error messages during Capistrano deployments. These messages now more properly reflect the root cause of the errors. newrelic_ignore methods allow strings The newrelic_ignore methods previously only supported passing symbols, and would quietly ignore any strings passed. Now strings can be passed as well to get the intuitive ignoring behavior you'd expect. Replace DNS resolver for Resque jobs with Resolv In some circumstances customers with a very high number of short-lived Resque jobs were experiencing deadlocks during DNS resolution. Resolv is an all Ruby DNS resolver that replaces the libc implementation to prevent these deadlocks.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3121298","eolDate":"2018-06-30"},{"agent":"ruby","date":"2015-05-07","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.12.0.288","version":"3.12.0.288","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Flexible capturing of attributes The Ruby agent now allows you more control over exactly which request parameters and job arguments are attached to transaction traces, traced errors, and Insights events. For details, see: https://docs.newrelic.com/docs/agents/ruby-agent/ruby-agent-attributes Fixed missing URIs in traces for retried Excon requests If Excon's idempotent option retried a request, the transaction trace node for the call would miss having the URI assigned. This has been fixed. Capturing request parameters from rescued exceptions in Grape If an exception was handled via a rescue_from in Grape, request parameters were not properly set on the error trace. This has been fixed. Thanks to Ankit Shah for helping us spot the bug.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3120288","eolDate":"2018-05-07"},{"agent":"ruby","date":"2015-04-05","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.11.2.286","version":"3.11.2.286","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Better naming for Rack::URLMap If a Rack app made direct use of Rack::URLMap, instrumentation would miss out on using the clearest naming based on the app class. This has been fixed. Avoid performance regression in makara database adapter Delegation in the makara database adapter caused performance issues when the agent looked up a connection in the pool. The agent now uses a faster lookup to work around this problem in makara, and allocates less as well. Thanks Mike Nelson for the help in resolving this! Allow audit logging to STDOUT Previously audit logs of the agent's communication with New Relic could only write to a file. This prevented using the feature on cloud providers like Heroku. Now STDOUT is an allowed destination for audit_log.path. Logging can also be restricted to certain endpoints via audit_log.endpoints. For more information see https://docs.newrelic.com/docs/agents/ruby-agent/installation-configurat... Fix for crash during startup when Rails required but not used If an application requires Rails but wasn't actually running it, the Ruby agent would fail during startup. This has been fixed. Use IO.select explicitly in the event loop If an application adds their own select method to Object/Kernel or mixes in a module that overrides the select method (as with ActionView::Helpers) we would previously have used their implementation instead of the intended IO.select, leading to all sorts of unusual errors. We now explicitly reference IO.select in the event loop to avoid these issues. Fix for background thread hangs on old Linux kernels When running under Ruby 1.8.7 on Linux kernel versions 2.6.11 and earlier, the background thread used by the agent to report data would hang, leading to no data being reported. This has been be fixed.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3112286","eolDate":"2018-04-05"},{"agent":"ruby","date":"2015-03-23","downloadLink":null,"version":"3.11.1.284","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fix for segmentation fault with sequel_pg 1.6.11 The Ruby agent incorrectly rescued exceptions at a point which caused sequel_pg 1.6.11 to segfault. This has been fixed. Thanks to Oldrich Vetesnik for the report!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3111284","eolDate":"2018-03-23"},{"agent":"ruby","date":"2015-03-18","downloadLink":null,"version":"3.11.0.283","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Unified view for SQL database and NoSQL datastore products. The response time charts in the application overview page will now include NoSQL datastores, such as MongoDB, and also the product name of existing SQL databases such as MySQL, Postgres, etc. The Databases page will now enable the filtering of metrics and operations by product, and includes a table listing all operations. For existing SQL databases, in addition to the existing breakdown of SQL statements and operations, the queries are now also associated with the database product being used. For NoSQL datastores, such as MongoDB, we have now added information about operations performed against those products, similar to what is being done for SQL databases. Because this introduces a notable change to how SQL database metrics are collected, it is important that you upgrade the agent version on all hosts. If you are unable to transition to the latest agent version on all hosts at the same time, you can still access old and new metric data for SQL databases, but the information will be split across two separate views. For more information see https://docs.newrelic.com/docs/apm/applications-menu/monitoring/database... Track background transactions as Key Transactions In prior versions of the Ruby agent, only web transactions could be tracked as Key Transactions. This functionality is now available to all transactions, including custom Apdex values and X-Ray sessions. For more information see https://docs.newrelic.com/docs/apm/selected-transactions/key-transaction... More support and documentation for third-party extensions It's always been possible to write extension gems for the Ruby agent, but now there's one location with best practices and recommendations to guide you in writing extensions. Check out https://docs.newrelic.com/docs/agents/ruby-agent/frameworks/third-party-... We've also added simpler APIs for tracing datastores and testing your extensions. It's our way of giving back to everyone who's helped build on the agent over the years. <3 Fix for anonymous class middleware naming Metric names based off anonymous middlewares lacked a class name in the UI. The Ruby agent will now look for a superclass, or default to AnonymousClass in those cases. Improved exit behavior in the presence of Sinatra The agent uses an at_exit hook to ensure data from the last < 60s before a process exits is sent to New Relic. Previously, this hook was skipped if Sinatra::Application was defined. This unfortunately missed data for short-lived background processes that required, but didn't run, Sinatra. Now the agent only skips its at_exit hook if Sinatra actually runs from at_exit.","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3110283","eolDate":"2018-03-18"},{"agent":"ruby","date":"2011-07-28","downloadLink":null,"version":"3.1.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 works with the Rails 3.1 release candidates. More reliable loading of several types of instrumentation, most notably Delayed Job","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-311","eolDate":"2014-07-28"},{"agent":"ruby","date":"2015-02-17","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.10.0.279","version":"3.10.0.279","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Support for the Grape framework We now instrument the Grape REST API framework! To avoid conflicts with the third-party newrelic-grape gem, our instrumentation will not be installed if newrelic-grape is present in the Gemfile. For more details, see https://docs.newrelic.com/docs/agents/ruby-agent/frameworks/grape-instru... Automatic Cross Application Tracing support for all Rack applications Previously Rack apps not using Rails or Sinatra needed to include the AgentHooks middleware to get Cross Application Tracing support. With these changes, this is no longer necessary. Any explicit references to AgentHooks can be removed unless the disable_middleware_instrumentation setting is set to true. Metrics no longer reported from Puma master processes When using Puma's cluster mode with the preload_app! configuration directive, the agent will no longer start its reporting thread in the Puma master process. This should result in more accurate instance counts, and more accurate stats on the Ruby VMs page (since the master process will be excluded). Better support for Sinatra apps used with Rack::Cascade Previously, using a Sinatra application as part of a Rack::Cascade chain would cause all transactions to be named after the Sinatra application, rather than allowing downstream applications to set the transaction name when the Sinatra application returned a 404 response. This has been fixed. Updated support for Rubinius 2.3+ metrics Rubinius 2.3 introduced a new system for gathering metrics from the underlying VM. Data capture for the Ruby VM's page has been updated to take advantage of these. Thanks Yorick Peterse for the contribution! Fix for missing ActiveJob traced errors ActiveJobs processed by backends where the Ruby agent lacked existing instrumentation missed reporting traced errors. This did not impact ActiveJobs used with Sidekiq or Resque, and has been fixed. Fix possible crash in middleware tracing In rare circumstances, a failure in the agent early during tracing of a web request could lead to a cascading error when trying to capture the HTTP status code of the request. This has been fixed. Thanks to Michal Cichra for the fix!","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-3100279","eolDate":"2018-02-17"},{"agent":"ruby","date":"2011-06-15","downloadLink":null,"version":"3.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Support for aggregating data from short-running processes to reduce reporting overhead Fixed: Issue with RUM and empty response bodies Patch: Clear GC::Profiler statistics under 1.9.2 to prevent memory leakage (user contribution from Stephan Mees) Feature: Added sorting by SQL query time in Developer Mode","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-310","eolDate":"2014-06-15"},{"agent":"ruby","date":"2011-05-20","downloadLink":null,"version":"3.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Updated Real User Monitoring to reduce JavaScript size and improve compatibility, fix a few known bugs","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-301","eolDate":"2014-05-20"},{"agent":"ruby","date":"2011-05-11","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/3.0.0","version":"3.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Support for Real User Monitoring Backend work on internals to improve reliability Added a log_file_name and log_file_path configuration variable to allow setting the path and name of the agent log file Improved reliability of statistics calculations Removed some previously deprecated methods Removed Sequel instrumentation pending more work","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-300","eolDate":"2014-05-11"},{"agent":"ruby","date":"2026-09-14","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/10.8.0","version":"10.8.0","features":["Report a unique hostname for Google Cloud Run Worker Pools and Jobs","Add `browser_monitoring.version` configuration option","Add span.kind to background job libraries"],"bugs":["DelayedJob instrumentation no longer reinstalls itself on every worker under prepend mode","Allowlisted configuration values are no longer case sensitive","Puma instrumentation works when Puma is lazy-loaded"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v10.8.0 Feature: Report a unique hostname for Google Cloud Run Worker Pools and Jobs Cloud Run hostname support, added in PR#3609 , detected Cloud Run only through K_REVISION, the environment variable set by Cloud Run Services . The agent now also recognizes CLOUD_RUN_REVISION  (Worker Pools) and CLOUD_RUN_EXECUTION (Jobs), so utilization.gcp_cloud_run.use_instance_as_host now applies to all three resource types. When utilization.gcp_cloud_run.include_revision_in_host is true, the hostname is built from whichever of these variables is present — for example, {CLOUD_RUN_EXECUTION}-{instance id} for a Job. Issue#3651  PR#3652 Feature: Add browser_monitoring.version configuration option Customers can now pin the exact browser agent loader version New Relic injects by setting the new browser_monitoring.version configuration option. See the browser agent EOL policy  for which versions are currently available and supported. PR#3663 Feature: Add span.kind to background job libraries Now, the span.kind attribute will be added to produce and consume operations from background job libraries. This includes ActiveJob, Sidekiq, Resque and DelayedJob. PR#3636 Bugfix: DelayedJob instrumentation no longer reinstalls itself on every worker under prepend mode When DelayedJob instrumentation is installed via prepend (the default), creating more than one Delayed::Worker in the same process caused the agent to log \"Installing DelayedJob instrumentation\" and reinitialize the plugin again for each additional worker. This was harmless but noisy; it's now only done once per process, matching the existing chain-instrumentation behavior. PR#3654 Bugfix: Allowlisted configuration values are no longer case sensitive Previously, allowlisted configuration options required an exact case match, so a value with unexpected casing — like OBFUSCATED or ObFuScAtEd for slow_sql.record_sql — would silently fall back to the default. Configuration options that validate against an allowlist now match values regardless of case, so both are treated the same as obfuscated. Issue#3613  PR#3645 Bugfix: Puma instrumentation works when Puma is lazy-loaded With gem \"puma\", require: false, Puma was not yet loaded when the agent's dependency check ran, so Puma instrumentation would fail to install. The agent now recognizes Puma::RackHandler as evidence that Puma is present, fixing this issue. Issue#3641  PR#3650","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-10-8-0","eolDate":"2027-09-14"},{"agent":"ruby","date":"2026-08-20","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/10.7.1","version":"10.7.1","features":[],"bugs":["Resolve ArgumentError on multi-key operations with Dalli 5.1.0","Async::HTTP requests no longer raise `NoMethodError` when a segment fails to start"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v10.7.1 Bugfix: Resolve ArgumentError on multi-key operations with Dalli 5.1.0 This fix updates Dalli instrumentation to accept and forward optional request options arguments in multi and pipelined operations. Our thanks go to @dbackeus  for contributing a fix! PR#3642 Bugfix: Async::HTTP requests no longer raise NoMethodError when a segment fails to start If the agent encountered an internal error while creating the segment for an Async::HTTP request, the instrumentation went on to use that missing segment and could raise a NoMethodError. This is now fixed, thanks to @ydah . PR#3640","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-10-7-1","eolDate":"2027-08-20"},{"agent":"ruby","date":"2026-08-06","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/10.7.0","version":"10.7.0","features":["Add transaction_tracer.cap_segment_artifacts configuration option","Add Puma server-statistics instrumentation","Report a unique hostname for Google Cloud Run instances"],"bugs":["Slow SQL no longer recorded after transaction_tracer.limit_segments exceeded","Explain plans could target the wrong database in multi-database Rails apps (Rails >= 7.2)","Browser monitoring instrumentation no longer fails with `FrozenError`","Normalize boolean configuration values to allow all casing"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v10.7.0 Feature: Add transaction_tracer.cap_segment_artifacts configuration option Long-running transactions with many segments can cause continuously increasing memory usage for the lifetime of the transaction. The agent now offers an opt-in transaction_tracer.cap_segment_artifacts configuration option (defaults to false). When enabled, once transaction_tracer.limit_segments  is reached, the agent also stops recording exclusive time for any segments created afterward in that transaction, reducing memory usage at the cost of less accurate timing data for the transaction. PR#3615 Feature: Add Puma server-statistics instrumentation The agent now samples Puma's cluster-wide server statistics and reports them as Ruby/Puma/* timeslice metrics, including backlog, running, pool_capacity, max_threads, and requests_count. Statistics are sampled in single mode and in clustered mode when preload_app! is enabled. This instrumentation is disabled by default. Enable it by setting disable_puma_instrumentation to false. When enabled, the agent starts a reporting thread in the Puma master process to deliver these metrics, which runs an additional agent connection alongside the Puma workers. The sampling interval is configurable via the new puma.sample_rate setting (default 60 seconds). Requires Puma 6.6 or later. See our docs  for more information. PR#3578 Feature: Report a unique hostname for Google Cloud Run instances The agent now detects Cloud Run and reports the GCP instance id as the hostname so individual instances can be distinguished. Before this change, all Google Cloud Run hostnames were localhost. This feature is controlled by the new utilization.gcp_cloud_run.use_instance_as_host configuration option (default true). Set utilization.gcp_cloud_run.include_revision_in_host (default false) to true to report the hostname as {K_REVISION}-{instance id} instead, where K_REVISION  is the Cloud Run revision name. Issue#3295  PR#3609 Bugfix: Slow SQL no longer recorded after transaction_tracer.limit_segments exceeded Once a transaction exceeded transaction_tracer.limit_segments , datastore segments created afterward still could have their slow SQL recorded. The agent now stops recording slow SQL for any segment created after the limit is reached. PR#3615 Bugfix: Explain plans could target the wrong database in multi-database Rails apps (Rails >= 7.2) On Rails 7.2+, the agent gathered explain plans using a connection from the app's default/shared pool rather than a dedicated one. This primarily affected multi-database apps. Explain plans could be generated against the wrong database, and a failed explain could leave a shared connection in a bad state, affecting unrelated requests. The agent now uses its own dedicated connection for explain plans, as it did before Rails 7.2, and resets or discards that connection whenever an explain attempt fails, so a bad connection is never reused. Issue#3610  PR#3612 Bugfix: Browser monitoring instrumentation no longer fails with FrozenError When a response body's first fragment was a frozen String and there were multiple fragments, browser instrumentation hit a FrozenError and the browser timing header was never injected. This began appearing with ERB 6.0.3+, which started freezing more of its compiled strings. This issue is now fixed. Issue#3624  PR#3625 Bugfix: Normalize boolean configuration values to allow all casing In version 9.x, the agent accepted capitalized boolean values, like \"FALSE\", and mixed-case values like \"True\". Version 10.0.0 included PR#3341 , which unintentionally removed the case-insensitive requirement. This caused users who had any casing besides all lowercase to have their configuration options fall back to the defaults. Now, the agent uses case-insensitive checks again. Issue#3632  PR#3633","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-10-7-0","eolDate":"2027-08-06"},{"agent":"ruby","date":"2026-06-25","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/10.6.0","version":"10.6.0","features":["SpanLink events are now supported for the Hybrid Agent","SpanEvent events are now supported for the Hybrid Agent","Set Span Kind on all Hybrid Agent spans","Add support for OpenTelemetry::Tracer#start_root_span"],"bugs":["Fix `instrumentation.rails_event_logger: false` not disabling the instrumentation","Normalize boolean-like values to `disabled` for instrumentation config keys","Per-library logging supportability metrics now reflect each library's instrumentation state"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v10.6.0 Feature: SpanLink events are now supported for the Hybrid agent Spans created by an OpenTelemetry API can now have Span Links  associated with them. Links can be added on a span's start, by passing them to the links argument, or by calling the OpenTelemetry::Trace::Span#add_link API. PR#3586 Feature: SpanEvent events are now supported for the Hybrid agent Spans created by an OpenTelemetry API can now have SpanEvent events  associated with them via the OpenTelemetry::Trace::Span#add_event API. SpanEvent events capture timestamped annotations on a span and are sent to New Relic alongside the parent span. PR#3587 Feature: Set span kind on all Hybrid agent spans Previously, only OpenTelemetry spans translated into external request segments or datastore segments added span kind as an attribute. Now, the agent adds span kind to all OpenTelemetry spans where the value is available. PR#3589 Feature: Add support for OpenTelemetry::Tracer#start_root_span The OpenTelemetry::Tracer#start_root_span API can now be used to force a transaction to start for a given span, provided it has a :server or :consumer span kind. For any other span kinds, it will no-op. This method is most commonly used in background job instrumentation. PR#3588 Bugfix: Fix instrumentation.rails_event_logger: false not disabling the instrumentation Previously, setting instrumentation.rails_event_logger to false didn't disable the Rails.event instrumentation as expected; it would still be installed during Rails boot. This is now fixed. PR#3564 Bugfix: Normalize boolean-like values to disabled for instrumentation config keys Previously, only disabled would turn off an instrumentation.* config key. Now, boolean-like values such as false, no, or off also resolve to disabled and prevent the instrumentation from being installed. PR#3579 Bugfix: Per-library logging supportability metrics now reflect each library's instrumentation state Previously, the Supportability/Logging/Ruby/{library}/{enabled|disabled} metrics reported the value of the global application_logging.enabled setting for every library, rather than each library's actual state. As a result, the metric reported enabled even when you had disabled logging instrumentation for a specific library or weren't using that library's gem at all. Now, each library's metric reflects whether its own logging instrumentation is enabled. PR#3571","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-10-6-0","eolDate":"2027-06-25"},{"agent":"ruby","date":"2026-05-14","downloadLink":"https://rubygems.org/gems/newrelic_rpm/versions/10.5.0","version":"10.5.0","features":["Add Dalli 5.0 support and fix meta protocol instrumentation","Add active_record_use_table_name configuration option","Partially redact license keys in agent logs"],"bugs":["Fix Semantic Logger instrumentation incompatibility with `rails_semantic_logger`"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v10.5.0 Feature: Add Dalli 5.0 support and fix meta protocol instrumentation The agent now supports Dalli 5.0+, which removed Dalli::Protocol::Binary in favor of the meta protocol exclusively. For Dalli 3.2.0+, pipelined_get instrumentation now correctly targets Dalli::Protocol::Base (where the method is defined) rather than Dalli::Protocol::Binary, fixing a gap where get_multi calls went uninstrumented when using the meta protocol. For Dalli 5.0+, the agent additionally instruments Dalli::Protocol::Meta#read_multi_req, which is invoked by Dalli's single-server get_multi optimization. PR#3541 Feature: Add active_record_use_table_name configuration option A new configuration option, active_record_use_table_name, uses an Active Record model's table name instead of its class name when naming metrics, spans, and transaction trace segments. This can particularly be helpful to reduce cardinality in applications using single-table inheritance. The option defaults to false to preserve existing behavior. PR#3540 Feature: Partially redact license keys in agent logs Previously, the agent would fully redact New Relic license keys in agent logs. Now, the first 10 characters are visible while the rest are replaced with *. This preserves enough to troubleshoot region-related issues without exposing the secret portion of the key. PR#3547 Bugfix: Fix Semantic Logger instrumentation incompatibility with rails_semantic_logger Previously, an ArgumentError would be raised when an exception reached ActionDispatch::DebugExceptions while using rails_semantic_logger. This has been fixed. Thank you to @jdelStrother  for reporting this! PR#3548","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-10-5-0","eolDate":"2027-05-14"},{"agent":"ruby","date":"2026-04-16","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-10.4.0.gem","version":"10.4.0","features":["Add Rails.event instrumentation for structured logging","Add instrumentation for Rails Active Job Continuations","Add sidekiq.separate_transactions configuration option"],"bugs":["Update regexes that may have been vulnerable to ReDOS attacks","Prevent crashes during HTTPX segment creation","Make Transaction#finish idempotent","Log deprecation warning for Datastores.wrap API once"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v10.4.0 Feature: Add Rails.event instrumentation for structured logging The agent now supports Rails.event as structured log events. When enabled, events published via Rails.event.notify are captured and forwarded to New Relic as log events. Event payloads, tags, context, timestamps, and source locations are automatically captured as log attributes. This instrumentation can be configured with the following options: instrumentation.rails_event_logger - Controls whether Rails.event instrumentation is enabled. Defaults to use the value of application_logging.enabled. instrumentation.rails_event_logger.event_names - An array of specific event names to capture. When empty (default), all Rails.event notifications are captured. Use this to filter events by name, for example: ['user.signup', 'payment.processed']. PR#3526 Feature: Add instrumentation for Rails Active Job Continuations The agent now instruments Rails Active Job Continuations, providing visibility into individual step execution within long-running jobs. Step names are included in segment metrics (e.g., Ruby/ActiveJob/default/MyJob/step/process_records) and step-specific attributes like cursor position, resumed status, and interrupted status are captured. A new configuration option, disable_active_job_step_names, allows users to exclude step names from metric names to reduce metric cardinality if needed (defaults to false). PR#3493 Feature: Add sidekiq.separate_transactions configuration option A new configuration option, sidekiq.separate_transactions, allows Sidekiq jobs executed during a web transaction to run in their own separate transaction. When enabled, this prevents Sidekiq job execution time from being included in web transaction metrics, providing more accurate performance data. The feature is opt-in (default: false) to maintain backward compatibility. This only affects jobs executed during active web transactions; jobs starting independently or nested within other background jobs are unaffected. Issue#3364  PR#3514 Bugfix: Update regexes that may have been vulnerable to ReDOS attacks Previously, the agent had a few regexes identified as possible targets for polynomial time complexity (ReDOS) attacks. Those regexes are now updated to address the concerns. PR#3520 Bugfix: Prevent crashes during HTTPX segment creation Previously, if start_external_request_segment encountered an error and returned nil, the agent would trigger a NoMethodError when attempting to add headers to the missing segment. We've added a guard check to ensure the instrumentation handles these cases gracefully. Bravo to @thebravoman  for the report! Issue#3509  PR#3510 Bugfix: Make Transaction#finish idempotent Previously, if the Transaction#finish method was called multiple times, more than one transaction could be created for the same operation. Now, a mutex protects calls to Transaction#finish to make sure finish operations only run once. PR#3513 Bugfix: Log deprecation warning for Datastores.wrap API once Previously, this warning was being logged on every call to Datastores.wrap. Now, it will be logged only on the first call. In addition, the documentation has been updated to note the deprecated status of the second and third callback arguments. Issue#3516  PR#3519","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-10-4-0","eolDate":"2027-04-16"},{"agent":"ruby","date":"2026-04-09","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-10.3.0.gem","version":"10.3.0","features":["Add database query naming via SQL comments","Add Semantic Logger instrumentation","Add new 'ignored_middleware_classes' configuration","Add new `NewRelic::Agent.add_transaction_log_attributes` API"],"bugs":["Provide config option to reduce cardinality of ActionCable broadcast metrics","Remove dead 'digest/md5' require for FIPS/FedRAMP compliance","Prevent agent from starting during `rails test` to avoid shutdown delay","Fix \"Unable to calculate elapsed transaction time\" warnings when using Falcon web server","Fix typo in harvest.rb causing NoMethodError","Remove usage of deprecated ObjectSpace._id2ref","Fix NoMethoError in Logging instrumentation"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v10.3.0 Feature: Add database query naming via SQL comments Database queries can now be explicitly named using SQL comments. Queries can include /* NewRelicQueryName: CustomName */ comments to assign stable names for better tracking and identification. This is especially useful for tracking specific database queries during performance regressions or incidents. PR#3480 Feature: Add Semantic Logger instrumentation The agent now supports Semantic Logger log forwarding and decoration for the semantic_logger gem versions 4.6.0+. If you were previously using Semantic Logger's built-in New Relic appender, it is recommended to choose one approach to avoid sending duplicate logs. New Relic's Semantic Logger instrumentation can be disabled by setting instrumentation.semantic_logger to disabled. PR#3467 Thanks to @jdelStrother  for providing valuable feedback that helped shape this instrumentation. Feature: Add new 'ignored_middleware_classes' configuration A new configuration option, ignored_middleware_classes, allows users to exclude specific middlewares from instrumentation (ex. Rack::Cors). It defaults to an empty array. Issue#1814  PR#3481 Feature: Add new NewRelic::Agent.add_transaction_log_attributes API A new API, NewRelic::Agent.add_transaction_log_attributes, allows users to add transaction-scoped custom attributes to log events for the current transaction. These attributes will only be applied to logs created within the scope of the current transaction. PR#3472 Bugfix: Provide config option to reduce cardinality of ActionCable broadcast metrics By default, the metrics for ActionCable broadcast method calls include the value of the broadcasting. This value can have very high cardinality. Now, the :simplify_action_cable_broadcast_metrics configuration option allows users to remove the broadcasting value from the metric name. This creates a metric that looks like: Ruby/ActionCable/broadcast. When this configuration option is enabled, the broadcasting value will be added as a span attribute. PR#3463 Bugfix: Remove dead 'digest/md5' require for FIPS/FedRAMP compliance In version 7.1.0 of the agent, MD5 usage was replaced with SHA1 for FIPS compliance (PR) . However, the old require for 'digest/md5' was not removed. We have removed the require to help our FIPS/FedRAMP users. Thank you to @ashleyboehs  for bringing this to our attention! Issue#3469  PR#3470 Bugfix: Prevent agent from starting during rails test to avoid shutdown delay Previously, the agent would cause a ~3 second shutdown delay when running the rails test command. The Rails::Command::TestCommand constant has been added to the default autostart.denylisted_constants list to prevent the agent from starting during Rails test runs. Thanks to @varyform  for bringing this to our attention. PR#3478 Bugfix: Fix \"Unable to calculate elapsed transaction time\" warnings when using Falcon web server The agent now uses Fiber.current.object_id instead of Thread.current.object_id to track transaction state when running under Falcon, preventing collisions from concurrent requests sharing the same thread. Also fixes a \"NameError: uninitialized constant Async::HTTP::VERSION\" when using Falcon. Thanks to @97jaz  and @gsar  for bringing this to our attention. PR#3483 Bugfix: Fix typo in harvest.rb causing NoMethodError A typo in lib/new_relic/agent/agent_helpers/harvest.rb caused a NoMethodError: undefined method 'agent' for NewRelic:Module. Thanks to @oakbow  for reporting this issue. PR#3484 Bugfix: Remove usage of deprecated ObjectSpace._id2ref The agent now uses an alternative approach instead of the deprecated ObjectSpace._id2ref method, eliminating deprecation warnings when running on Ruby 4.0+. PR#3490 Bugfix: Fix NoMethoError in Logging instrumentation Previously, when the Logging gem instrumentation attempted to decorate local logs, it would raise a NoMethodError if it encountered a non-string object. This is now fixed. PR#3501","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-10-3-0","eolDate":"2027-04-09"},{"agent":"ruby","date":"2026-02-18","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-10.2.0.gem","version":"10.2.0","features":["Introduce Hybrid Agent for OpenTelemetry Tracing Support","Add configuration option error_collector.backtrace_truncate_location","Add Logging gem instrumentation","Add configuration option utilization.detect_in_parallel"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v10.2.0 Feature: Introduce Hybrid Agent for OpenTelemetry Tracing Support OpenTelemetry Tracing APIs can now be translated into New Relic telemetry with the New Relic Ruby agent's new Hybrid Agent features . This allows the newrelic_rpm gem to behave similarly to an OpenTelemetry SDK, accepting OpenTelemetry API calls and turning them into New Relic Transactions and Segments with familiar attributes and names. The following configuration options relate to Hybrid Agent features: | Configuration name | Default | Behavior |\n| ------------------ | ------- |----------|\n| opentelemetry.enabled | false | A global configuration option for disabling all OpenTelemetry signals sent through New Relic. |\n| opentelemetry.traces.enabled | true |  Enables the creation of Transaction Trace segments and timeslice metrics from OpenTelemetry Spans |\n| opentelemetry.traces.include | '' | A comma-delimited list of OpenTelemetry Tracers, represented as a string (e.g. \"AppTracer1,OpenTelemetry::Instrumentation::Bunny::Instrumentation\"), that will  have their trace signals sent to New Relic.|\n| opentelemetry.traces.exclude | '' | A comma-delimited list of OpenTelemetry Tracers, represented as a string (e.g. \"AppTracer1,OpenTelemetry::Instrumentation::Bunny::Instrumentation\"), that will not  have their trace signals sent to New Relic. All known tracers for instrumentation that conflicts with New Relic instrumentation are excluded by default. | Feature: Add configuration option error_collector.backtrace_truncate_location A new configuration option has been added, error_collector.backtrace_truncate_location, which allows the user to specify where in the backtrace to truncate when the number of frames exceeds error_collector.max_backtrace_frames. Options are 'top' (removes frames from the beginning), 'middle' (removes frames from the middle, preserving the beginning and end), or 'end' (removes frames from the end). The default is 'middle'. PR#3424 Feature: Add Logging gem instrumentation The agent will now record logs generated by the Logging gem . PR#3420 Feature: Add configuration option utilization.detect_in_parallel A new configuration option has been added, utilization.detect_in_parallel, which controls whether the agent uses threads when detecting cloud vendor information to speed up agent startup. When set to false, vendor detection runs sequentially without creating threads. The default is true. PR#3439","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-10-2-0","eolDate":"2027-02-18"},{"agent":"ruby","date":"2026-02-03","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-10.1.0.gem","version":"10.1.0","features":["Add support for forking processes in Parallel gem instrumentation","Add support for Grape v3.1.0"],"bugs":["Create health check files in forked processes"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v10.1.0 Feature: Add support for forking processes in Parallel gem instrumentation Parallel gem instrumentation has been added to allow more consistent monitoring in processes forked using the Parallel gem. PR#3405 Feature: Add support for Grape v3.1.0 Grape's release of v3.1.0 introduced changes that were incompatible with the agent's instrumentation, causing issues when collecting transaction names. The agent has been updated to properly extract class names for transaction naming in the updated Grape API structure. PR#3413 Bugfix: Create health check files in forked processes The agent now properly initializes health check loops after forking, ensuring each process generates its own health check file. This fix also has the effect of correctly including entity.guid values in the health check files. PR#3409  Issue#3408 Bugfix: Fix sidekiq.ignore_retry_errors The configuration option sidekiq.ignore_retry_errors: true was continuing to report retry errors. The agent now correctly ignores retry errors and only reports when jobs permanently fail. PR#3399","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-10-1-0","eolDate":"2027-02-03"},{"agent":"ruby","date":"2026-01-14","downloadLink":"https://rubygems.org/downloads/newrelic_rpm-10.0.0.gem","version":"10.0.0","features":["Remove support for Ruby 2.4 and 2.5","Removal of Cross Application Tracing (CAT)","Rename ActiveJob metrics and segments","Rename `bin/newrelic` command to `bin/newrelic_rpm`","Remove the `newrelic deployments` CLI command","Remove the NewRelic::Agent::SqlSampler#notice_sql method","Remove unused arguments from various NewRelic::Agent::Datastores APIs","Remove experimental feature Configurable Security Policies (CSP)","Remove support for Puma versions below 3.9.0","Improve configuration validation and coercion","Replace 'default' option with 'adaptive' for distributed tracing remote parent samplers","Add `logger` as a dependency","Add Active Support notification allowlist configuration option","Use Ruby's built-in Gzip compression","Add argument validation for the `NewRelic::Agent#record_custom_event` API","Add root sampling configuration options","Add Trace ID Ratio Based sampling options","Add Entity GUID to Agent Control health check files"],"bugs":["Resolve a `NoMethodError` in GCP utilization detection."],"security":[],"supportedOperatingSystems":null,"description":"Major Version Update:  This version of the Ruby agent is a SemVer MAJOR update and contains breaking changes. MAJOR versions may drop support for language runtimes that have reached End-of-Life according to the maintainer. Additionally, MAJOR versions may drop support for and remove certain instrumentation. For more details on these changes please see the migration guide here . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Ruby agent EOL policy  for information about agent releases and support dates. v10.0.0 Breaking Change: Remove support for Ruby 2.4 and 2.5 Support for Ruby versions 2.4 and 2.5 has been removed. The new minimum required Ruby version is now 2.6. PR#3314 Breaking Change: Removal of Cross Application Tracing (CAT) Previously, Cross Application Tracing (CAT) was deprecated in favor of Distributed Tracing. CAT functionality has now been removed. The configuration option cross_application_tracer.enabled has been removed. Public API methods NewRelic::Agent::External.process_request_metadata, NewRelic::Agent::External.get_response_metadata, NewRelic::Agent::Transaction::ExternalRequestSegment#process_response_metadata, NewRelic::Agent::Transaction::ExternalRequestSegment#get_request_metadata, and NewRelic::Agent::Transaction::ExternalRequestSegment#read_response_headers have also been removed. PR#3333 Breaking Change: Rename ActiveJob metrics and segments ActiveJob metrics have been updated to include the job's class name for more specific reporting. This is a breaking change and may require updating custom dashboards or alerts. PR#3370  PR#3320 Old format: Ruby/ActiveJob/<QueueName>/<Method> New format: Ruby/ActiveJob/<QueueName>/<ClassName>/<Method> In addition, segments created for Active Job enqueuing actions now include the job class. Old format: ActiveJob/<QueueAdapter>/Queue/<Event>/Named/<QueueName> New format: ActiveJob/<QueueAdapter>/Queue/<Event>/Named/<QueueName>/<ClassName> Breaking Change: Rename bin/newrelic command to bin/newrelic_rpm The executable file for the agent's CLI has been renamed from bin/newrelic to bin/newrelic_rpm. This change resolves a name collision with the standalone New Relic CLI tool. PR#3323 Breaking Change: Remove the newrelic deployments CLI command The deprecated newrelic deployments CLI command has been removed. To track changes and deployments in New Relic, please see our guide to Change Tracking  for a list of available options. PR#3299 Breaking Change: Remove the NewRelic::Agent::SqlSampler#notice_sql method Users should call NewRelic::Agent::Datastores.notice_sql instead. PR#3338 Breaking Change: Remove unused arguments from various NewRelic::Agent::Datastores APIs The following APIs from the NewRelic::Agent::Datastores class have had method arguments removed: NewRelic::Agent::Datastores.notice_sql, previously had three positional arguments, query, scoped_metric and elapsed. Now, it only has query. NewRelic::Agent::Datastores.notice_statement, previously had two positional arguments query and elapsed. Now it only has query. NewRelic::Agent::Datastores.wrap requires a proc. Previously the proc received three arguments: the result of the yield, the most specific scoped metric name, and the elapsed time of the call. Now, it only receives one: the result of the yield. The values of the removed arguments are derived from the current segment at the time of the call. PR#3347 Breaking Change: Remove experimental feature Configurable Security Policies (CSP) The experimental feature, Configurable Security Policies (CSP), is no longer supported and has been removed. PR#3292 Breaking Change: Remove support for Puma versions  3.9.0 The minimum version of Puma now supported is 3.9.0 or higher. PR#3326 Breaking Change: Improve configuration validation and coercion The internals used to coerce and validate the values provided for agent configuration are now more performant and more accurate. Warning messages will now be logged to the newrelic_agent.log file when nil is provided as a config value for a setting that does not support it. Integer values are permitted for Float configuration types Float values are permitted for Integer configuration types Fatal interruptions are prevented when a default value can be found to replace an invalid input value\nPR#3341 Breaking Change: Replace 'default' option with 'adaptive' for distributed tracing remote parent samplers Previously, the default option for distributed_tracing.sampler.remote_parent_sampled and distributed_tracing.sampler.remote_parent_not_sampled was default, which used the pre-existing adaptive sampler. The default option has been renamed to adaptive. PR#3363 Feature: Add logger as a dependency The logger gem is now listed as a dependency of the agent to ensure continued logging functionality and support for Ruby 4.0.0…","slug":"docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-10-0-0","eolDate":"2027-01-14"},{"agent":"php","date":"2012-10-23","downloadLink":null,"version":"3.0.5.95","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release marks the start of a brand new series of PHP agent releases. This represents many months of performance tuning, stability improvements and additional new features. All existing users are highly encouraged to upgrade to the latest agent. There are many changes in this version, the most interesting of which are listed below. All users who are upgrading from a previous release are encouraged to read the upgrade notes  document to fully understand some of the impacts of upgrading. Highlights of this release include: Drastic memory usage reduction. The agent overhead is down from approximately 35% to just 4%. Significantly less stack space used (down from 40K per PHP function call to just 84 bytes). This affects users with deeply recursive functions. License keys are now set in the INI file and not the daemon configuration file, and they are settable on a per-directory or per-virtual host basis. This very frequently requested feature will allow multi-tenant sites to use different keys for each tenant. The New Relic daemon can now be started automatically by the agent. For upgrade customers it will still be started the way it always was with the init scripts, but you can now change that by configuring the daemon in your INI file. Please see this page on daemon startup modes  for details. Several bugs related to auto-RUM (Real User Monitoring) have been fixed, including a fix for non-standard HTML (where the head element is at the end of the document). The agent startup \"banner\" now contains much more useful information that can be included in the initial dialog with support, and will short-circuit the typical \"what OS and PHP version are you using exactly?\" preamble to getting a ticket resolved. The agent and daemon no longer use a UNIX-domain socket for their communications. Now a standard TCP socket (port 33142 by default) is used, which makes deploying in a chroot environment a lot easier. The RPM and Debian packages have been split into three separate packages: the agent, the daemon and common scripts between the two. This was primarily done so that the agent was in its own package, and on 64-bit systems the agent package now only contains the 64-bit agent. This means that 64-bit users do not have to install the entire 32-bit runtime just to install the PHP agent. The 32-bit agent can always be installed alongside the 64-bit one. The phpinfo() output has been changed to more clearly distinguish between global and per-directory settings. It now also correctly displays the per-directory value if the script was invoked from within a directory that changed default values. The newrelic.transaction_tracer.top100 setting has been renamed to newrelic.transaction_tracer.detail. You can now arbitrarily begin and end transactions (for example, at the beginning and end of each job queue unit of work). This is done using the new newrelic_end_transaction and newrelic_start_transaction API calls. The daemon has been considerably simplified and uses fewer locks, thus reducing the potential for entering a \"spin\" state. Many other improvements to speed and stability.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent","eolDate":"2015-10-23"},{"agent":"php","date":"2020-04-01","downloadLink":"https://download.newrelic.com/php_agent/archive/9.9.0.260","version":"9.9.0.260","features":[],"bugs":["Fix Drupal 8 transaction naming"],"security":[],"supportedOperatingSystems":null,"description":"Bug fixes Under some circumstances, Drupal 8 transactions were named after generic controllers. These names were not useful for troubleshooting. Drupal 8 transaction naming is now improved and hooks into Symfony routing to resolve the main controller associated with a route.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-990260","eolDate":"2023-04-01"},{"agent":"php","date":"2020-03-25","downloadLink":"https://download.newrelic.com/php_agent/archive/9.8.0.259","version":"9.8.0.259","features":["Add support for W3C Trace Context for distributed tracing"],"bugs":["Fix increased memory usage when newrelic.transaction_tracer.max_segments_cli limit is reached","Fix segment datastructures causing crashes for long-running transactions"],"security":[],"supportedOperatingSystems":null,"description":"New Features Support for W3C Trace Context, with easy upgrade from New Relic trace context Distributed Tracing now supports W3C Trace Context headers for HTTP protocols when distributed tracing is enabled. Our implementation can accept and emit both W3C trace header format and New Relic trace header format. This simplifies agent upgrades, allowing trace context to be propagated between services with older and newer releases of New Relic agents. W3C trace header format will always be accepted and emitted. New Relic trace header format will be accepted, and you can optionally disable emission of the New Relic trace header format. When distributed tracing is enabled, there are two new API function calls available that now support W3C tracestate and traceparent distributed tracing headers in addition to the New Relic distributed tracing header information: newrelic_insert_distributed_trace_headers()  is used to add distributed tracing headers newrelic_accept_distributed_trace_headers()  is used to accept distributed tracing headers When distributed tracing is enabled, you can use the new configuration setting newrelic.distributed_tracing_exclude_newrelic_header  to exclude the New Relic distributing tracing header and only rely on W3C Trace Context headers. Bug fixes Fixed a case where the memory usage of the PHP agent increases when newrelic.transaction_tracer.max_segments_cli  limit is reached. In rare cases, optimized segment data structures could cause crashes for long-running transactions that hit the segment limit set via newrelic.transaction_tracer.max_segments_cli  or newrelic.transaction_tracer.max_segments_web . This has been fixed. Known Issues and Workarounds If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream PHP New Relic agents to this agent release.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-980259","eolDate":"2023-03-25"},{"agent":"php","date":"2020-02-11","downloadLink":"https://download.newrelic.com/php_agent/archive/9.7.0.258","version":"9.7.0.258","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Avoid potential memory exhaustion for long running transactions The configuration settings newrelic.transaction_tracer.max_segments_cli  and newrelic.transaction_tracer.max_segments_web  were added. These settings can be used to limit the number of segments the PHP agent records during a CLI transaction and a web transaction respectively. newrelic.transaction_tracer.max_segments_cli defaults to 100000 and thus avoids potential memory exhaustion for long running CLI transactions. newrelic.transaction_tracer.max_segments_web defaults to 0, meaning that the PHP Agent shall capture all segments during a web transaction. For more information, see the documentation about the PHP agent configuration . Performance improvements The PHP agent now creates segments in a more efficient way, which results in improved performance. Bug fixes The Debian init script now uses pidof instead of ps. This solves issues related to starting the daemon with systemctl on Debian. Previously, the daemon would start and immediately stop.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-970258","eolDate":"2023-02-11"},{"agent":"php","date":"2020-01-22","downloadLink":"https://download.newrelic.com/php_agent/archive/9.6.1.256","version":"9.6.1.256","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes In 9.6.0, custom outbound headers added to curl requests could be silently removed if both newrelic.cross_application_tracer.enabled and newrelic.distributed_tracing_enabled are disabled. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-961256","eolDate":"2023-01-22"},{"agent":"php","date":"2020-01-16","downloadLink":"https://download.newrelic.com/php_agent/archive/9.6.0.255","version":"9.6.0.255","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Enhanced visibility into curl_multi_exec calls Previously, curl_multi_exec requests appeared as one segment with one total time. Now, we expose the individual segments of a curl_multi_exec request that include individual times and host details. This provides greater visibility as to which URLs are being called and improved ability to troubleshoot slow curl calls. Configurable daemon start timeout The PHP Agent has introduced a new configuration newrelic.daemon.start_timeout. Customers may use this to specify a timeout for the agent to wait for the daemon after a daemon was launched by the agent. With this timeout set, the agent will not immediately drop a transaction when the launched daemon hasn't acquired a socket yet, but rather grants the daemon time to do so. It is recommended to only set this timeout when instrumenting long-lived background tasks, as in case of daemon start problems the agent will block for the given timeout at every transaction start. Upgrade Notice For cross agent conformance, the agent attribute httpResponseCode has been renamed to http.statusCode. In PHP agent release 9.4 , we erroneously introduced httpResponseCode as the replacement for response.statusCode. The new http.statusCode agent attribute name will align with other agents and enables standardized alerts and INSIGHTS queries based on a common attribute name. Attributes are reported with both the new http.statusCode name and thelegacy httpResponseCode and response.statusCode attribute names. Support for legacy attribute names will be removed in future agent versions. Known issues and workarounds Potential memory exhaustion for long running transactions See description and recommendations under Known issues and workarounds  in the PHP 9.0.0.242 release notes .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-960255","eolDate":"2023-01-16"},{"agent":"php","date":"2020-01-06","downloadLink":"https://download.newrelic.com/php_agent/archive/9.5.0.252","version":"9.5.0.252","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Support for Real Time Streaming Event data is now sent to New Relic every five seconds, instead of every minute. As a result, transaction, error, and custom events will now be available in New Relic and Insights dashboards in near real time. For more information on how to view your events with a five-second refresh, see the real time streaming documentation . Note that the overall limits on how many events can be sent per minute have not changed. Also, span events, metrics, and trace data is unaffected, and will still be sent every minute. Laravel 6 is now fully supported by the PHP agent. Known issues and workarounds Potential memory exhaustion for long running transactions See description and recommendations under Known issues and workarounds  in the PHP 9.0.0.242 release notes .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-950252","eolDate":"2023-01-06"},{"agent":"php","date":"2019-12-11","downloadLink":"https://download.newrelic.com/php_agent/archive/9.4.1.250","version":"9.4.1.250","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes A potential segfault when using PHP 7.4 in connection with framework instrumentation has been fixed. Known issues and workarounds Potential memory exhaustion for long running transactions See description and recommendations under Known issues and workarounds  in the PHP 9.0.0.242 release notes .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-941250","eolDate":"2022-12-11"},{"agent":"php","date":"2019-12-05","downloadLink":"https://download.newrelic.com/php_agent/archive/9.4.0.249","version":"9.4.0.249","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Known issues and workarounds Potential memory exhaustion for long running transactions See description and recommendations under Known issues and workarounds  in the PHP 9.0.0.242 release notes . New features in 9.4 Added support for PHP 7.4 The PHP agent can detect libraries and frameworks that were preloaded via the opcache.preload  setting. You can disable this feature by using the following configuration setting: newrelic.preload_framework_library_detection = false . Request URI attribute is now captured We now capture the request.uri  attribute. The request URI appears in transaction queries in New Relic Insights. You can disable this attribute by using the following configuration setting: newrelic.attributes.exclude = \"request.uri\" . Upgrade Notices For cross agent conformance, the agent attributes request.headers.User-Agent and httpResponseCode are renamed to request.headers.userAgent and response.statusCode. The value response.StatusCode is changed to an integer. Attributes are reported with both the new and the legacy attribute names. Support for legacy attribute names will be removed in future agent versions. Bug Fixes Since 9.0, transaction traces and span events were not created when newrelic_end_transaction was called inside a PHP function. newrelic_end_transaction now creates transaction traces and span events in any case. It reports all traces and span events for segments that weren't ended at the time of its invocation as unknown. Since 9.0, Predis calls weren't instrumented when the Predis client was loaded from a path ending in Predis/Client.php. This has been fixed. For inbound distributed tracing payloads with invalid or missing values for pr (priority) and/or sa (sampled) the agent used to assign a default priority of -1 and/or a default sampled value of false to the transaction. This has been fixed, the agent now keeps initial priority and sampled values if the respective values in the inbound distributed tracing payload are missing or invalid. The daemon used to erroneously send SIGUSR1 signals to its parent process group in case one of the flags --foreground or --watchdog-foreground was given. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-940249","eolDate":"2022-12-05"},{"agent":"php","date":"2019-11-11","downloadLink":"https://download.newrelic.com/php_agent/archive/9.3.0.248","version":"9.3.0.248","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Known issues and workarounds Potential memory exhaustion for long running transactions See description and recommendations under Known issues and workarounds  in the PHP 9.0.0.242 release notes . New features in 9.3 Trace and entity metadata API calls A new API function newrelic_is_sampled()  has been added. This call returns true if the current transaction is part of a sampled distributed trace. A new API function for obtaining linking metadata been added. newrelic_get_linking_metadata() . This call returns an opaque map of key/value pairs that can be used to correlate this application to other data in the New Relic backend. A new API function newrelic_get_trace_metadata()  has been added. This call returns a collection of metadata used to identify a trace: trace.id, which provides the currently executing trace's identifier; and span.id, which provides the span identifier associated with the currently executing span. Configurable connection timeout The PHP agent has introduced a new configuration newrelic.daemon.app_connect_timeout . Customers may use this to specify a timeout for the agent to wait for a daemon connection. With this timeout set, the agent will not immediately drop a transaction when the daemon hasn't connected to the backend yet, but rather grant the daemon time to establish the connection. It is recommended to only set this timeout when instrumenting long-lived background tasks, as in case of connection problems the agent will block for the given timeout at every transaction start.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-930248","eolDate":"2022-11-11"},{"agent":"php","date":"2022-04-26","downloadLink":"https://download.newrelic.com/php_agent/archive/9.21.0.311","version":"9.21.0.311","features":["Distributed tracing enabled by default","Increase Distributed Tracing default reservoir size"],"bugs":["Fix misdetection of Alpine Linux","Improve stability of Laravel with opcache and PHP 8.1"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v9.21.0 New features Distributed Tracing  is now turned on by default. Distributed Tracing span reservoir size  now has a default of 2000 (up from 1000) and a maximum of 10000. Cross Application Tracing is deprecated. Bug fixes Fixed an install script bug where it detects Alpine Linux as Debian when phpize dependencies are installed. Improved stability of using Laravel framework when using opcache with PHP 8.1. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines please consult the following document .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9210311","eolDate":"2024-04-26"},{"agent":"php","date":"2019-10-07","downloadLink":"https://download.newrelic.com/php_agent/archive/9.2.0.247/","version":"9.2.0.247","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features in 9.2 More flexibility for container deployments The PHP daemon and agent no longer have to reside on the same host and can now communicate over a IPv4 or IPv6 TCP socket. This can be configured via the newrelic.daemon.address setting in the agent and the --address command line option for the daemon. When terminating the New Relic PHP daemon via the SIGTERM signal (and/or the SIGINT signal if started with the -f, --foreground flag), the daemon will now send all buffered data to New Relic prior to exiting. The PHP daemon has introduced a new configuration --watchdog-foreground. This keeps the daemon watchdog process in the foreground, whereas the --foreground configuration keeps the daemon worker process in the foreground. The new configuration makes it possible to use the daemon in a blocking way, without losing the additional stability provided by the watchdog process. Upgrade notices The PHP agent has introduced a new configuration newrelic.daemon.address which serves as an alias to newrelic.daemon.port. You may use either to specify the location of the New Relic PHP daemon. If both values are set, newrelic.daemon.address takes precedence. Similarly, the PHP daemon has introduced a new configuration --address which serves as an alias to --port. Customers may use either to specify the location of the New Relic PHP daemon. If both values are set, --address takes precedence. When starting the daemon as an external process, the daemon will now wait for up to three seconds for the listening port to be ready to receive connections before forking into the background. This usually occurs in (much) less than a second, and most users with this configuration will notice no difference in practice. The time that the daemon will wait can be controlled by setting the --wait-for-port setting with a duration. This duration may be 0 to prevent any blocking. If the option is omitted, the default value is 3s. Note that this is not the default configuration shipped with the PHP agent, and generally is only used in conjunction with the PHP agent configured with newrelic.daemon.dont_launch set to 3. Daemons started in foreground mode (with the --foreground flag) are unaffected, and will behave as before. Bug fixes When duplicating database connections to generate explain plans, the agent will no longer make those connections persistent, even if the original connection was persistent. The daemon now synchronously handles critical code paths related to harvesting and merging transaction data. This prevents crashes caused by race conditions. Previously, the PHP agent was silently ignoring the setting newrelic.daemon.port if the value was outside of the range 1 - 65535. In this case, it used the default value of /tmp/.newrelic.sock. The PHP agent no longer silently ignores these port values; it now logs these errors in php_agent.log. Known issues and workarounds Potential memory exhaustion for long running transactions.  See description under Known issues and workarounds  in the PHP 9.0.0.242 release notes .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-920247","eolDate":"2022-10-07"},{"agent":"php","date":"2022-03-14","downloadLink":"https://download.newrelic.com/php_agent/archive/9.20.0.310","version":"9.20.0.310","features":["Add AWS IMDSv2 support"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v9.20.0 New features AWS instance metadata service (IMDS) feature now allows AWS IMDSv2 by @robertprast. New Contributors @robertprast made their first contribution.  Thanks!! End of Life Notices Support for the Centos 6 / RHEL6 operating systems are deprecated and will be removed by June 2022. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines please consult the following document .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9200310","eolDate":"2024-03-14"},{"agent":"php","date":"2022-03-02","downloadLink":"https://download.newrelic.com/php_agent/archive/9.19.0.309","version":"9.19.0.309","features":["Add support for 64-bit PHP 8.1"],"bugs":["Fix Symfony 5 auto detection"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP Agent v9.19.0 New Features Added support for 64-bit PHP 8.1! (#177 ). Compatibility note: Support for PHP 8.1 does not include Fibers. Bug Fixes Fixed Symfony 5 auto detect (#113 , #256 ). Thank you @piotrantosik for your contribution! Fixed URL of New Relic for PHP docs website used in error messages (#334 ) Fixed URL of New Relic of PHP docs website in README (#254 ). Thank you @revilon1991 for your contribution! End of Life Notices 32-bit support for PHP versions 5.5, 5.6, 7.0, 7.1, 7.2, 7.3, 7.4 is deprecated and will be removed by June 2022. Support for FreeBSD operating system is deprecated and will be removed by June 2022. This will be the last release in which ZTS builds are supported. In the future, ZTS builds may not be provided and support may be completely pulled from the codebase. Support Statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 8.6.0 .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9190309","eolDate":"2024-03-02"},{"agent":"php","date":"2021-08-23","downloadLink":"https://download.newrelic.com/php_agent/archive/9.18.1.303","version":"9.18.1.303","features":["Add Docker development environment support","Add support for Route caching in Laravel 7.x","Add support for \"Redis::mget\" and \"Redis::mset\" functions"],"bugs":["Fix curl_multi instrumentation memory leak","Fix supportability metric causing a segfault","Fix incorrect handling of PHP versions with unknown API version during Debian package install","Fix parent.transportDuration value of 0 between two PHP applications instrumented through distributed tracing","Fix incorrect install of newrelic.ini"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v9.18.1 New features Added  a Docker development environment. It's now possible for contributors to both develop and test (unit tests and integration tests) without setting up a specific environment on their own system. Please see our documentation  for more information. Route caching in Laravel 7.x is now supported! . Transaction naming now works with routes cached via php artisan route:cache. @stockalexander, thanks for your contribution! Redis::mget and Redis::mset functions are now supported . @b-viguier, thanks for your contribution! Bug fixes Fixed  instances where a memory leak was occurring with our curl multi instrumentation. Fixed  an issue where a supportability metric used to track an edge case was causing a segfault. Fixed  an issue where PHP versions with an unknown API version were incorrectly handled during Debian package install. Fixed  instances where parent.transportDuration values are 0 for transactions between two PHP applications instrumented through distributed tracing. @b-viguier, thanks for your contribution! Fixed  an issue where the newrelic.ini configuration file was incorrectly installed. @b-viguier, thanks for your contribution! Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 8.6.0 .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9181303","eolDate":"2023-08-23"},{"agent":"php","date":"2021-04-28","downloadLink":"https://download.newrelic.com/php_agent/archive/9.17.1.301","version":"9.17.1.301","features":[],"bugs":["Fix mysqli_commit instrumentation returning NULL","Fix parameters not being passed by reference in PDO instrumentation","Fix \"Unknown PHP version: 8.0\" error on Debian and Ubuntu systems"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP Agent v9.17.1 Bug Fixes Fixed  instances where the agent's mysqli_commit instrumentation returned a NULL instead of a boolean. Fixed  an issue where parameters were not passed by reference in the agent's pdo instrumentation. This caused a warning in PHP 8. Fixed  instances where an Unknown PHP version: 8.0 error was occurring when installing on Debian and Ubuntu systems. Support Statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 8.6.0 .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9171301","eolDate":"2023-04-28"},{"agent":"php","date":"2021-04-21","downloadLink":"https://download.newrelic.com/php_agent/archive/9.17.0.300","version":"9.17.0.300","features":["Add support for 64-bit PHP 8.0","Add instrumentation for mysqli_commit"],"bugs":["Fix memory leak caused by exceptions in short-lived spans","Fix duplicate distributed tracing headers caused by file_get_contents","Fix Laravel Lumen transaction naming"],"security":[],"supportedOperatingSystems":null,"description":"End of life notices This will be the last release in which ZTS builds are supported. In the future, ZTS builds may not be provided, and support may be completely pulled from the codebase. New Relic no longer supports PHP 5.3 or PHP 5.4. New Relic highly encourages upgrading to a supported version of PHP. If you would like to continue running the New Relic PHP agent with PHP 5.3 or 5.4, we recommend using version 9.16 of the agent. However, please note that we can only offer limited support in this case. Ubuntu LTS versions earlier than 14.04, Ubuntu non-LTS versions earlier than 19.04, and Debian versions earlier than 7 \"wheezy\" are no longer supported. The following frameworks or framework versions are no longer supported and may be removed from future agent builds: Cake PHP 1.x Joomla 1.5, 1.6, and 2.x Kohana Silex 1.x and 2.x Symfony 1.x and 2.x New features The agent now supports 64-bit PHP 8.0! Compatibility note: When PHP 8.0 detects the New Relic agent, it disables JIT. mysqli_commit is now instrumented . Bug fixes Fixed a memory leak  that occurred when short lived segments throw exceptions. Fixed a build up  of duplicate distributed tracing headers that sometimes occurred when using file_get_contents. Fixed an issue where Laravel Lumen transactions were not being properly named . Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 8.6.0 .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9170300","eolDate":"2023-04-21"},{"agent":"php","date":"2021-01-25","downloadLink":"https://download.newrelic.com/php_agent/archive/9.16.0.295","version":"9.16.0.295","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes The Drupal instrumentation now guards  against rare conditions that led to PHP processes exiting with an allocation error. Additionally, the allocation routines now log stack traces when they fail. When initially building the agent, a parallel build is no longer required  to avoid an error about a missing header file (v1.pb-c.h). SOAP transactions when using Magento 2.3.2+ are now properly named  instead of being attributed to Magento's internal SOAP interceptor. Thanks @steven-hoffman-jomashop  for the issue report and fix suggestion! Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 8.5.0 .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9160295","eolDate":"2023-01-25"},{"agent":"php","date":"2020-12-07","downloadLink":"https://download.newrelic.com/php_agent/archive/9.15.0.293","version":"9.15.0.293","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"End of Life Notices Support for PHP 5.3 and PHP 5.4 in the New Relic PHP Agent is deprecated and will be removed in a future version. New Relic highly encourages upgrading to a supported version of PHP  - 7.3 or higher as of the date of this release. If you would like to continue running the New Relic PHP agent with PHP 5.3 and 5.4, we recommend using version 9.15 of the agent for maximum compatibility. However please note that we can only offer limited support in this case. This release marks the last officially supported New Relic PHP Agent for CentOS 5. MacOS builds of the New Relic PHP Agent will no longer be provided, and we will no longer ensure compatibility on MacOS platforms. For more information about these EOL notices, see our Explorers Hub post . New features Support has been added for Laminas 3.x. Support has been added for Laravel Lumen 6.x, 7.x, and 8.x Experimental support has been added for excluding subpaths from Wordpress instrumentation.  This lowers the overall Wordpress instrumentation overhead since it reduces the number of files being instrumented, but at the cost of losing visibility into the code in the excluded subpaths. This can be enabled using the ini file setting newrelic.framework.wordpress.hooks_skip_filename. Bug fixes Corrected string representation of arginfo parameter names . Thank you @TysonAndre for this contribution. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 8.4.0 .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9150293","eolDate":"2022-12-07"},{"agent":"php","date":"2020-10-29","downloadLink":"https://download.newrelic.com/php_agent/archive/9.14.0.290/","version":"9.14.0.290","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features The PHP agent  is now open source! The agent source code is available and open to contributions. You can now report issues and make feature requests for the agent directly on GitHub. See our README  for more information. Bug Fixes Under some circumstances, the agent reported a total time higher than the response time when using Zend_Http_Client. This has been fixed. The agent leaked a small amount of memory for each fulfilled Guzzle promise. This has been fixed. Calls to newrelic_insert_distributed_trace_headers could cause crashes on PHP 7.0, 7.1, and 7.2. This has been fixed. In rare cases, using Guzzle with WordPress and PHP 7.4 caused crashes. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9140290","eolDate":"2022-10-29"},{"agent":"php","date":"2020-08-17","downloadLink":"https://download.newrelic.com/php_agent/archive/9.13.0.270/","version":"9.13.0.270","features":["Add support for Slim 4.x","Add support for Laravel 7.x"],"bugs":["Fix datastore segments reporting total transaction time as higher than response time","Fix caching for Wordpress plugins referred to by pathname"],"security":[],"supportedOperatingSystems":null,"description":"New Features Support has been added for Slim Framework 4.x. Support has been added for Laravel 7.x. Bug Fixes Users of newrelic_record_datastore_segment may have experienced situations where the total transaction time was higher than the response time. This was fixed and users will see behavior consistent with automatically created datastore segments. Previously, WordPress plugins referred to by their path names were not accounted for in caching. This behavior has been fixed, and users to which this applies to should see improvements in overhead.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9130270","eolDate":"2023-08-17"},{"agent":"php","date":"2020-07-21","downloadLink":"https://download.newrelic.com/php_agent/archive/9.12.0.268/","version":"9.12.0.268","features":["Add span attributes","Add Infinite Tracing support"],"bugs":["Fix agent to daemon IP address resolution for separate hosts"],"security":[],"supportedOperatingSystems":null,"description":"New Features With the addition of attributes on spans, the PHP agent now fully supports Infinite Tracing on New Relic Edge . Infinite Tracing observes 100% of your distributed traces and provides visualizations for the most actionable data so you have the examples of errors and long-running traces so you can better diagnose and troubleshoot your systems. You configure your agent  to send traces to a trace observer in New Relic Edge. You view your distributed traces through the New Relic’s UI. There is no need to install a collector on your network. Infinite Tracing is currently available on a sign-up basis. If you would like to participate, please contact your sales representative. Added support for attributes on spans. All custom attributes and some agent attributes previously applied as “Transaction events” are now also applied to the currently executing span, subject to the new span configuration settings. Added the transaction.name to spans. Added http.statusCode to external spans, representing the status code on an http response. Added error attributes to each span that exits with an error or exception. error.class and error.message are now included on the span in which an error or exception was noticed, and, in the case of unhandled exceptions, on any ancestor spans that also exit with an error. Also, the public API method newrelic_notice_error  now attaches these error attributes to the currently executing span, while still creating a Transaction Error event. Spans with error details are now highlighted red in the distributed tracing UI , and error details will expose the associated error.class and error.message. It is also now possible to see when an exception leaves the boundary of the span, and if it is caught in an ancestor span without reaching the entry span. NOTE: This “bubbling up” of exceptions will impact the error count when compared to prior behavior for the same trace. It is possible now to have a trace that has span errors without showing an error on the root span or entry spans. Added a new API method newrelic_add_custom_span_parameter  that allows adding custom attributes to spans. This is independent of the transaction; using this new API to add custom attributes to spans does not add them to transactions. If the maximum number of custom attributes is reached, span-level custom attributes take precedence over transaction-level custom attributes. Added the following span event attributes configuration to enable attribute filtering for spans: newrelic.span_events.attributes.enabled newrelic.span_events.attributes.include newrelic.span_events.attributes.exclude Note: Security recommendation—Review your Transaction attributes configuration. Any attribute include or exclude settings specific to Transaction events, should be applied to your Span attributes configuration or your global attributes configuration. Bug Fixes In cases where the agent is configured to connect to the hostname of a daemon that exists in a separate container/host, after successfully connecting, the agent would not attempt to resolve the IP address again. This was seen when the daemon container/host goes down and then comes up again with a new IP address. Now, the agent will wait 45 seconds since either the last known good connection or the last IP address resolution and will attempt to resolve an IP address again.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9120268","eolDate":"2023-07-21"},{"agent":"php","date":"2020-06-16","downloadLink":"https://download.newrelic.com/php_agent/archive/9.11.0.267","version":"9.11.0.267","features":["Add support for Infinite Tracing","Add support for Symfony 5 auto-instrumentation","Add support for Drupal 9 auto-instrumentation"],"bugs":["Fix Daemon socket connect causing infinite loop on startup"],"security":[],"supportedOperatingSystems":null,"description":"New Features Added support for New Relic Infinite Tracing. Note:  the PHP agent does not yet support attributes on spans. This will be available in the next minor release. Added the following Infinite Tracing configuration options: newrelic.infinite_tracing.trace_observer.host newrelic.infinite_tracing.trace_observer.port newrelic.infinite_tracing.span_events.queue_size Support for auto-instrumenting Symfony 5 applications has been added. Support for auto-instrumenting Drupal 9 applications has been added. Bug Fixes In some cases the newrelic-daemon got caught in an infinite loop on startup when the socket it tried to connect to was already acquired by another process. This behavior has been accounted for and fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9110267","eolDate":"2023-06-16"},{"agent":"php","date":"2019-09-04","downloadLink":"https://download.newrelic.com/php_agent/archive/9.1.0.246/","version":"9.1.0.246","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features in 9.1 Symfony 4 support added. Web transactions that use the Symfony 4 framework will now be automatically named based on the route or controller name. Addition of the ability to migrate to Configurable Security Policies (CSP)  on a per agent basis for accounts already using High-security mode (HSM) . When both HSM and CSP are enabled for an account, an agent (this version or later) can successfully connect with either high_security: true or the appropriate security_policies_token configured. Upgrade notices Requests handled by PHP-FPM that result in a 404 error because the script does not exist, or a 403 error because PHP-FPM does not have permission to access the script, will now result in a transaction called 404 or 403, respectively, rather than being named after the request URI. This change was made to prevent metric grouping issues , particularly when sites are being probed by potential attackers. If you wish to capture the actual request URI for analysis, it can be attached to the transaction event under the request.uri attribute using the following configuration setting: newrelic.transaction_events.attributes.include=request.uri Bug fixes In version 9.0, Guzzle and Predis execution time could be double counted on application overview and transaction charts in APM, as time could be attributed to both PHP execution and the external or datastore time, respectively. This has been fixed, and charts should now revert back to their previous behavior. Restarting a transaction from within a Drupal or WordPress hook could result in a segfault. This has been fixed. Known issues and workarounds Potential memory exhaustion for long running transactions.  See description under Known issues and workarounds  in the PHP 9.0.0.242 release notes .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-910246","eolDate":"2022-09-04"},{"agent":"php","date":"2020-05-05","downloadLink":"https://download.newrelic.com/php_agent/archive/9.10.1.263","version":"9.10.1.263","features":[],"bugs":["Fix Laravel queue with distributed tracing segfault"],"security":[],"supportedOperatingSystems":null,"description":"Bug Fixes In some cases, instrumenting Laravel queue applications while having distributed tracing turned on could potentially lead to a segfault. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9101263","eolDate":"2023-05-05"},{"agent":"php","date":"2020-04-29","downloadLink":"https://download.newrelic.com/php_agent/archive/9.10.0.262","version":"9.10.0.262","features":[],"bugs":["Fix PHP Daemon panic caused by the Go HTTP library when cloud provider metadata endpoints are blocked"],"security":[],"supportedOperatingSystems":null,"description":"Bug Fixes In some rare cases where requests to cloud provider metadata endpoints are blocked via certain methods, the PHP Daemon logged panics from the underlying Go HTTP library. This scenario is now accounted for and handled gracefully. Upgrade notices On Linux systems, the default value for newrelic.daemon.address  changed from /tmp/.newrelic.sock to @newrelic. This means that by default on Linux, agent and daemon communicate via abstract sockets instead of socket files. The PHP Agent installer for Ubuntu/Debian systems now requires Python 3. Debian based distributions with Python 2 are no longer supported. End of life notices The distributing tracing API functions newrelic_create_distributed_trace_payload()  newrelic_accept_distributed_trace_payload() , and newrelic_accept_distributed_trace_payload_httpsafe()  used to manually instrument applications have been deprecated, and will be removed in a future release. Instead, use the API functions compatible with W3C Trace Context support, added in agent version 9.8: newrelic_insert_distributed_trace_headers() , and newrelic_accept_distributed_trace_headers()","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-9100262","eolDate":"2023-04-29"},{"agent":"php","date":"2019-08-19","downloadLink":"https://download.newrelic.com/php_agent/archive/9.0.2.245/","version":"9.0.2.245","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes A bug that could result in segfaults when transactions were restarted (either directly through newrelic_start_transaction() or indirectly through newrelic_set_appname()) was fixed. This also affected customers using Laravel Queue instrumentation, as this uses transaction restarts internally. PHPUnit may not have been detected on case sensitive filesystems on 9.0.0. This has been fixed. A bug that could result in segfaults for CodeIgniter applications on PHP 7 when call_user_func_array() inlining failed was fixed. Known issues and workarounds Potential memory exhaustion for long running transactions.  See description under Known issues and workarounds  in the PHP 9.0.0.242 release notes .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-902245","eolDate":"2022-08-19"},{"agent":"php","date":"2019-08-08","downloadLink":"https://download.newrelic.com/php_agent/archive/9.0.0.242/","version":"9.0.2.242","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features in 9.0 Detailed transaction traces now available when distributed tracing is enabled. This release includes a refactor of segment storage to allow the agent to sort and apply different prioritization of segments that are used for transaction traces instead of distributed tracing. The PHP agent 8.4 release included limited support for distributed tracing, which resulted in the loss of detailed transaction traces for individual PHP services when distributed tracing was enabled. The refactor in this new release allows the agent to send up the segments (spans) you want to view for a distributed trace that includes PHP services. It also separately provides as much segment detail as possible when exploring transaction traces for an individual PHP service. Notes: The instructions to enable distributed tracing  have not changed with this release. The behavior of newrelic.transaction_tracer.detail has changed when distributed tracing is on. In the 8.4 - 8.7 PHP agent releases, newrelic.transaction_tracer.detail was disabled when distributed tracing was enabled. That is no longer the case. For more information, see the documentation for configuring trace level detail when using distributed tracing . To enable the improved support for distributed tracing, the PHP agent's memory allocation strategy has changed in 9.0. The PHP agent will more aggressively allocate memory when a transaction starts, and the system allocator may choose not to release that memory back to the operating system immediately, depending on the configuration of the operating system kernel and C library. As a result, the memory usage of the PHP processes may now be higher than it was with previous versions of the PHP agent. Upgrade notices for 9.0 With these distributed tracing enhancements, please check threshold values . In the 8.4 - 8.7 PHP agent releases, we recommended that customers set newrelic.transaction_tracer.threshold = 0 so that the agent would report complete distributed traces even when a lightweight PHP service was part of the trace. This is no longer necessary. When upgrading to the 9.0 release, we recommend that you review your newrelic.transaction_tracer.threshold settings, and return this value to its default or some higher value that is sensible for the application. The daemon will now issue a warning if it cannot find a root certificate bundle on startup. The daemon includes its own certificates and will still operate, but a future version of the PHP agent will remove the built-in certificates. At that point the PHP agent will not be able to communicate with New Relic's servers. Recommendation:  Ensure a root certificate bundle is installed on your host or in your container before using the PHP agent. This is generally available on most Linux distributions as a ca-certificates package. On FreeBSD, a bundle is available via the security/ca_root_nss package in ports. The daemon may no longer be invoked with the --tls flag. As of PHP agent version 8.0.0 the newrelic.daemon.ssl ini setting had been removed to increase security, but you could still invoke the daemon from the command line with --tls true. Command-line invocations of the daemon with the --tls flag will cause the invocation to fail. As with all PHP agent versions since 8.0.0, TLS is always used for communication with New Relic servers. Bug fixes A potential segfault when using drupal_http_request under PHP 7.3 has been fixed. In some cases, starting a new transaction during a request (via newrelic_start_transaction or newrelic_set_appname) could result in an incomplete state of framework and user function instrumentation. When obfuscating SQL, comments are stripped without any loss of the SQL itself. Predis 0.8 commands that used the synchronous executeCommand() code path (for example, HSET) on a clustered connection did not generate metrics. This has been fixed. Known issues and workarounds Potential memory exhaustion for long running transactions PHP agent 9.x uses more memory than previous versions, as it is less aggressive about freeing the memory used to track function calls and segments during transactions: in the normal case, memory is only freed at the end of each transaction. This tends to manifest mainly for users with long running transactions, such as background jobs to process message queues, transform or report on data, or send e-mails. We apologize for the inconvenience this issue has caused, and are actively working to fix it. In the short term, we have four potential workarounds to mitigate this issue. Workarounds: 1. Start/stop transactions manually.  If the affected transaction is one that performs a series of repetitive processes, such as a message queue consumer, you can manually instrument each iteration as a separate transaction. This provides you more fine-grained data on how the process is operating. By doing this, the memory used will be freed after each transaction. To implement this, you would ignore the initial automatic trans…","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-900242","eolDate":"2022-08-08"},{"agent":"php","date":"2019-03-14","downloadLink":"https://download.newrelic.com/php_agent/archive/8.7.0.242/","version":"8.7.0.242","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes Transaction globals are now cleanly separated from request globals. This fixes crashes related to the initialization of multiple transactions during one request (mostly triggered by newrelic_set_appname()).","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-870242","eolDate":"2022-03-14"},{"agent":"php","date":"2019-03-14","downloadLink":"https://download.newrelic.com/php_agent/archive/8.6.0.238/","version":"8.6.0.238","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Support Laravel's handling of CORS HTTP OPTIONS. Requests for Laravel's built-in automatic handling of CORS HTTP OPTIONS requests will now be given the transaction name _CORS_OPTIONS. Bug Fixes A potential segfault when using PHP 7.3, opcache and multiple PHP workers has been fixed. Uncaught exceptions within a job being executed by a Laravel Queue worker are now reported correctly. Invoking function_exists()  on a function disabled with the disable_functions  configuration directive will now correctly return false.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-860238","eolDate":"2022-03-14"},{"agent":"php","date":"2018-12-19","downloadLink":"https://download.newrelic.com/php_agent/archive/8.5.0.235/","version":"8.5.0.235","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added support for PHP 7.3. Keeping up with the latest and greatest from the PHP Core team, the New Relic PHP Agent now supports PHP 7.3. Distributed Tracing Improvements! The PHP Agent's Distributed Tracing support (introduced in version 8.4 of the PHP Agent) now includes the `http.method` attributes for External spans. Up to date PHPUnit support. The PHP Agent now supports automatic creation of custom events for PHPUnit 6, PHPUnit 7, and PHPUnit 8.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-850235","eolDate":"2021-12-19"},{"agent":"php","date":"2018-12-05","downloadLink":"https://download.newrelic.com/php_agent/archive/8.4.0.231/","version":"8.4.0.231","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Support for Distributed tracing Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before. Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide  before you enable this feature. To enable distributed tracing, two parameters should be changed in the newrelic.ini file: and Read more about about distributed tracing in the PHP Agent . Bug Fixes A bug in the PHP agent resulted in databaseCallCount attributes no longer being attached to Transaction events. The 8.4 release restores these attributes. Predis 2 cluster connections could not be instrumented due to internal changes in Predis. The 8.4 release fixes this.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-840231","eolDate":"2021-12-05"},{"agent":"php","date":"2018-10-15","downloadLink":"https://download.newrelic.com/php_agent/archive/8.3.0.226/","version":"8.3.0.226","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes In rare cases, during a reset of the apache web server, the agent and mod_php would hang with 100% CPU utilization. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-830226","eolDate":"2021-10-15"},{"agent":"php","date":"2018-09-05","downloadLink":"https://download.newrelic.com/php_agent/archive/8.2.0.221/","version":"8.2.0.221","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes Fixed an entire category of bugs where a Drupal hook whose hook name matched its module name resulted in the generation of empty metric names. Operating Systems Support This release of the PHP Agent removes support for the Solaris operating system. For Solaris support, please install agent version 8.1 or prior.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-820221","eolDate":"2021-09-05"},{"agent":"php","date":"2018-04-30","downloadLink":"https://download.newrelic.com/php_agent/archive/8.1.0.209/","version":"8.1.0.209","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Upgrade Notices The PHP Agent API call newrelic_set_appname  has been updated with security improvements in anticipation of future releases.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-810209","eolDate":"2021-04-30"},{"agent":"php","date":"2018-03-12","downloadLink":null,"version":"8.0.0.204","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Upgrade Notices The newrelic.daemon.ssl ini setting has been removed to increase security. Transport Layer Security (TLS) will now always be used in communication with the New Relic collector . Laravel Queue support has now been enabled for all users. If newrelic.feature_flag=laravel_queue is set, it will now be ignored. Bug Fixes On FreeBSD and Solaris, when newrelic.daemon.port is configured to use TCP to connect the agent to the daemon, the agent would have difficulty receiving application configuration data from the daemon due to the default timeout of 100 milliseconds matching the delay enforced by the FreeBSD kernel as part of its implementation of Nagle's algorithm. The PHP agent will now set the TCP_NODELAY flag when connecting to the daemon via TCP, which increases the reliability of the agent:daemon connection.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-800204","eolDate":"2021-03-12"},{"agent":"php","date":"2018-01-10","downloadLink":null,"version":"7.7.0.203","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Support for PHP 7.2 has been added. Bug Fixes Datastore metrics would not be generated for Predis users who stopped and started the transaction after instantiating a Predis\\Client object. This included users using the newrelic_set_appname()  API. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-770203","eolDate":"2021-01-10"},{"agent":"php","date":"2017-10-10","downloadLink":null,"version":"7.6.0.201","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Internal functions can now be instrumented by enabling the newrelic.transaction_tracer.internal_functions_enabled configuration setting. When enabled, internal functions will appear in transaction traces like PHP functions. Note that enabling this option may result in transactions being slower, especially when collecting many traces from PHP 5.x. Enabling this option is only recommended when specifically debugging performance issues where an internal function is suspected to be slow. Bug Fixes In some cases, Magento 2's UI Component JSON data sources return with an (incorrect) Content-Type of text/html. This resulted in auto instrumentation insertions into JSON data that contained a <head> string. We now identify these specific JSON data sources and ensure the auto instrumentation is not inserted into this JSON data. On PHP 7, using file_get_contents() to get a HTTP URL in a function which also read from $http_response_header resulted in the external call not being linked correctly in the APM UI: the external call would appear in transaction traces without a link to the receiving application. This has been fixed. Using curl_setopt_array()  to set options on a cURL handle could result in cross application tracing failing. This has been fixed. When generating explain plans for queries issued with MySQLi, the PHP agent could bind parameters from the wrong query if the PHP object ID had been reused internally. This has been fixed. Due to a change in Laravel 5.5's router API, the PHP agent would crash when automatically naming a Laravel transaction. This has been fixed. On PHP 7, when naming transactions for the Laravel 5 framework, well-formed transaction names were being replaced by the too-generic $METHOD/index.php. This has been fixed. Invoking newrelic_record_datastore_segment() before the PHP agent had connected to New Relic would result in the query callback silently failing to execute. This has been fixed; the callback will always be invoked provided parameters of the correct type are given to the function, otherwise an E_WARNING will be generated.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-760201","eolDate":"2020-10-10"},{"agent":"php","date":"2017-08-29","downloadLink":null,"version":"7.5.0.199","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features A new API function for timing datastore functions that the PHP agent doesn't natively instrument has been added: newrelic_record_datastore_segment(). Documentation and usage examples can be found on the New Relic Documentation  site. The agent now collects additional metadata when running within AWS, GCP, Azure, and PCF. This information is used to provide an enhanced experience when the agent is deployed on those platforms. Bug Fixes On Laravel 5.4, previous versions of the PHP agent named transactions handled by routes without explicit names based on the request method and front controller name, instead of using the route URI as with other versions of Laravel. This has been fixed, and automatic transaction names are once again consistent across all Laravel versions. When generating explain plans for queries issued with MySQLi, the PHP agent could bind parameters from the wrong query if the PHP object ID had been reused internally. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-750199","eolDate":"2020-08-29"},{"agent":"php","date":"2017-07-05","downloadLink":null,"version":"7.4.0.198","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes On the first request served by a PHP process, a Drupal 6 or 7 hook that was invoked with module_invoke() before it had been invoked by module_invoke_all() could have its module name reported as an empty string. This has been fixed. On PHP 7.0 and 7.1, a Drupal 6 or 7 hook invoked via module_invoke_all() could report the module name as an empty string in some situations. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-740198","eolDate":"2020-07-05"},{"agent":"php","date":"2017-06-27","downloadLink":null,"version":"7.3.1.197","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes Users of Guzzle 4 or 5 may have seen crashes in version 7.3.0 of the PHP agent due to a bug in the agent's request shutdown instrumentation for that library. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-731197","eolDate":"2020-06-27"},{"agent":"php","date":"2017-06-26","downloadLink":null,"version":"7.3.0.193","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Upgrade Notices Laravel Queue instrumentation has been updated to better interoperate with other New Relic APM features. It is possible that messages sent from PHP installs running version 7.3 (or later) of the PHP agent may not be correctly linked to the message queue worker transaction if the worker is running with version 7.2 or earlier of the PHP agent. If you use the Laravel Queue instrumentation, we recommend ensuring that all agents used to produce and consume messages are upgraded to version 7.3 simultaneously to avoid unexpected service map issues. Bug Fixes Compatibility with extensions that install opcode handlers on PHP 7 has been improved, most notably with uopz. While we still do not recommend using other extensions that hook deeply into PHP (such as uopz, runkit, or xdebug) with the New Relic PHP agent, this change should result in improved functionality. A potential segfault when using Predis in a session handler invoked at request shutdown has been fixed. External requests issued using Guzzle 6 are now properly instrumented when the GuzzleHttp\\Client class has been extended.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-730193","eolDate":"2020-06-26"},{"agent":"php","date":"2017-04-19","downloadLink":null,"version":"7.2.0.191","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Upgrade Notices Users of the newrelic-php5 Debian package with PHP 5.2: due to discontinued support of PHP 5.2, upgrading to version 7.x of the PHP agent may result in your applications no longer reporting to New Relic. We advise that you upgrade to a supported version of PHP. If upgrading PHP is not possible, you can use apt-get and dpkg to install version 6.9 of the PHP agent and then hold that installed version by running these commands as root: Bug Fixes Automatic transaction naming has been fixed for Symfony 1  users who replaced the controller class via factories.yml  with one that did not call sfFrontWebController::dispatch() or sfController::forward(). Datastore metrics could not be generated for Predis  0.7 and 0.8 in version 7.1 of the PHP agent. This has been fixed. The agent would not report Zend_Http_Client  external calls when the Zend Framework was used directly as a library or indirectly by a framework like Symfony or Magento. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-720191","eolDate":"2020-04-19"},{"agent":"php","date":"2017-03-23","downloadLink":null,"version":"7.1.0.187","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added support for the MongoDB library The PHP agent now supports the MongoDB userland library, which is the recommended interface to the mongodb extension. Users of this library will see new metrics in the Databases tab, nodes in transaction traces, and breakdown metrics on individual transaction pages. Database instance information available for Redis, Predis, and MongoDB Queries and commands issued using the PECL Redis extension, the Predis library, and the MongoDB library now capture instance information. Transaction traces now include the name of the host (including the port or socket) and database that the query was run against. Collection of host information can be disabled by setting newrelic.datastore_tracer.instance_reporting.enabled = false in the newrelic.ini. Similarly, the database name can be omitted with newrelic.datastore_tracer.database_name_reporting.enabled = false. Upgrade Notices Commands in Predis pipelines are now reported individually, rather than being rolled into a single pipeline query. Bug Fixes When using PHP 7.0 or 7.1, calling curl_setopt() with the CURLOPT_HTTPHEADER option and an array with elements that have been accessed by reference (for example, with foreach ($array as $k => &$v)) would result in the headers used by New Relic to track external calls overwriting other custom headers. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-710187","eolDate":"2020-03-23"},{"agent":"php","date":"2017-02-21","downloadLink":null,"version":"7.0.0.186","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Relic PHP Agent Release Notes End of Life Notices The New Relic PHP agent no longer supports PHP 5.2. New Relic highly encourages upgrading to a supported version of PHP - 5.6 or higher. If you would like to continue running the New Relic PHP agent with PHP 5.2, we recommend using version 6.9 of the agent, however please note that we can only offer limited support in this case. New Features Automatic transaction naming for Magento 2  has been improved. Previously, only requests that were handled by Magento's normal routing were automatically named, which resulted in request types that utilized Magento's interceptor/plugin  functionality being named as unknown. This primarily affected users of the REST or SOAP web services. REST and SOAP requests will now be named in the Webapi/Rest and Webapi/Soap namespaces, respectively, and will be named according to the service class and method that handle the request. Third party modules that add an interceptor on Magento\\Framework\\App\\FrontControllerInterface to override the dispatch() method will result in transaction names that are based on the interceptor class name. New Relic recommends using the newrelic_name_transaction()  API function from within the module to name the transaction if you require more precision.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-700186","eolDate":"2020-02-21"},{"agent":"php","date":"2017-01-19","downloadLink":null,"version":"6.9.0.182","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"End of Life Notices Support for PHP 5.2 in the New Relic PHP agent is deprecated and will be removed in a future version. New Relic highly encourages upgrading to a supported version of PHP - 5.6 or higher. If you would like to continue running the New Relic PHP agent with PHP 5.2, we recommend using version 6.9 of the agent, however please note that we can only offer limited support in this case. New Features Instance information for the pgsql and PDO pgsql extensions is now captured. Slow database queries and transaction traces now include the name of the host (including the port or socket) and database that the query was run against. Collection of host information can be disabled by setting newrelic.datastore_tracer.instance_reporting.enabled = false in the newrelic.ini. Similarly, the database name can be omitted with newrelic.datastore_tracer.database_name_reporting.enabled = false.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-690182","eolDate":"2020-01-19"},{"agent":"php","date":"2016-11-09","downloadLink":null,"version":"6.8.0.177","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"End of Life Notices Support for PHP 5.2 in the New Relic PHP agent is deprecated and will be removed in a future version. New Relic highly encourages upgrading to a supported version of PHP - 5.6 or higher. If you would like to continue running the New Relic PHP agent with PHP 5.2, we recommend using version 6.8 of the agent, however please note that we can only offer limited support in this case. New Features Support for PHP 7.1 has been added. The elapsed time after which an application will be considered inactive can now be configured using the newrelic.daemon.app_timeout setting. This setting is useful when the only transactions being executed are very infrequent, such background processing using a cron job. Previously, an application was considering inactive after ten minutes with no transactions. Instance information  for the mysql, mysqli, and PDO mysql extensions is now captured. Slow database queries and transaction traces now include the name of the host (including the port or socket) and database that the query was run against. Collection of host information can be disabled by setting newrelic.datastore_tracer.instance_reporting.enabled = false in the newrelic.ini. Similarly, the database name can be omitted with newrelic.datastore_tracer.database_name_reporting.enabled = false. Bug Fixes Automatic transaction naming for MediaWiki versions 1.18 and later was broken in version 6.3 of the New Relic PHP agent. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-680177","eolDate":"2019-11-09"},{"agent":"php","date":"2016-09-21","downloadLink":null,"version":"6.7.0.174","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features PHPUnit test events Support has been added for the popular unit test library PHPUnit (versions 3.7 to 5.5, inclusive). When enabled, the agent reports test results as custom Insights events. Test suite summary data are sent as TestSuite events, while individual test cases are sent as Test events. You can enable this feature in your newrelic.ini file with newrelic.phpunit_events.enabled = true. Depending on your events retention policy, enabling this setting may impact your New Relic billing statement. Read more about this feature on our documentation site . Support has been added for Slim Framework 2.x and 3.x. Upgrade Notices To avoid potential deadlocks, MySQL SELECT queries that use the FOR UPDATE or LOCK IN SHARE MODE  suffixes will no longer generate explain plans. Bug Fixes Automatic page load timing instrumentation was broken on PHP 5.4-7.0 in certain edge cases: most notably, when the <head> element was not in the first 40kB of the page content, or when the </body> element was not in the last few kilobytes of content. This has been fixed. Prevent real user monitoring JavaScript injection when the Content-Type is first set to text/html then subsequently changed to something else (for example, application/json). This was a regression introduced in version 6.2.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-670174","eolDate":"2019-09-21"},{"agent":"php","date":"2016-08-25","downloadLink":null,"version":"6.6.1.172","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes When using version 6.6.0 of the PHP agent, instantiating a PDO object with options set could result in PHP crashing at the end of handling a request. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-661172","eolDate":"2019-08-25"},{"agent":"php","date":"2016-08-23","downloadLink":null,"version":"6.6.0.169","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Support has been added for Laravel 5.3. Experimental Laravel Queue support. Experimental support for the Laravel Queue component  has been added. This supports all versions of Laravel from 4.0 to 5.3, inclusive. Whether run via artisan queue:listen or artisan queue:work, queue workers will now generate a separate background transaction for each job that is processed. These transactions will be named with the class name of the job, or IlluminateQueueClosure if a closure was queued. Additionally, a transaction that queues one or more jobs will be linked to the background transaction(s) that processed those jobs on the transaction map in the New Relic UI. To enable this support, you will need to set the laravel_queue feature flag in newrelic.ini. For most users, this will simply involve adding this line: newrelic.feature_flag=laravel_queue As this is presently an experimental feature, we would welcome feedback — both positive and negative — on whether this feature helps users using the Laravel Queue component better visualise the structure and performance of their applications. If all goes well, it is anticipated that Laravel Queue support will be enabled by default in a future version of the agent. Upgrade Notices Symfony 1 transactions that generate 404 errors due to no routes being matched will now be named based on the module and action that are actually used, rather than the module and action inferred from the request URL. In most cases, this will result in the transaction name being based on the error_404_module and error_404_action Symfony settings. Note that, as a result of this change, if the configured 404 action calls sfAction::forward() to forward to another action, the transaction name will be based on the final action. All other uses of sfAction::forward() are unaffected. Bug Fixes Previously, calling PDO::query with more than one argument resulted in the query being counted under the 'other' category on the Datastores page in the New Relic UI. This has been fixed. The agent will now correctly categorize the query as 'select', 'insert', 'update', or 'delete'. Previously, calling PDO::query with more than one argument resulted in the agent reporting \"(unknown sql)\" if the query was slow. (i.e., it exceeded the threshold given by the newrelic.transaction_tracer.explain_threshold  setting.) This has been fixed. Previously, calling SQLite3::querySingle with two arguments resulted in the query being counted under the 'other' category on the Datastores page in the New Relic UI. This has been fixed. The agent will now correctly categorize the query as 'select', 'insert', 'update', or 'delete'. Previously, calling SQLite3::querySingle with two arguments resulted in the agent reporting \"(unknown sql)\" if the query was slow. (i.e. It exceeded the threshold given by the newrelic.transaction_tracer.explain_threshold  setting.) This has been fixed. Transient Magento 2 tables now have the unique numbers removed from their names to avoid metric grouping issues. Pressflow 6 applications were incorrectly detected as Drupal 7 applications. This could cause POST requests made using drupal_http_request to be converted into GET requests. This has been fixed. Explain plan generation is now always performed on a separate database connection. This has been changed to avoid issues when using MySQL's SELECT FOUND_ROWS() feature. Previously, instrumenting method calls that resolved to __call() or __callStatic() calls could result in crashes on PHP 7. This primarily manifested in crashes for users of certain WordPress plugins (for example, wp-external-links) that registered hooks or actions that used magic methods. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-660169","eolDate":"2019-08-23"},{"agent":"php","date":"2016-07-28","downloadLink":null,"version":"6.5.0.166","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Support has been added for Zend Framework 3 . Bug Fixes The behavior of the installer when attempting to detect PHP installations has been tightened up. Previously, a directory structure such as /usr/local/php/php/* would be detected as an installation of PHP in /usr/local/php, as the nested php directory would be wrongly assumed to be a PHP CLI binary. The installer now checks if the nested php (or php-config) is a directory, and ignores the path if so. Although this is likely to improve the installer in multiple environments, most noticeably, this fix removes erroneous messages about there being multiple PHP installations when installing the PHP agent within the Docker Hub's official PHP images . Spurious messages like ALERT: oops, unknown child could appear in the PHP FPM log when a New Relic daemon process was started. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-650166","eolDate":"2019-07-28"},{"agent":"php","date":"2016-06-14","downloadLink":null,"version":"6.4.0.163","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Ignore Errors A new newrelic.error_collector.ignore_errors  setting has been added. When configured, this setting can be used to prevent errors, such as E_WARNING, from being reported to New Relic. This setting does not affect errors reported via the newrelic_notice_error API. Ignore Exceptions A new newrelic.error_collector.ignore_exceptions  setting has been added. This setting accepts a comma-separated list of fully-qualified class names. When an uncaught exception occurs, the agent will not report the exception to New Relic if it is an instance of a class in this list. This setting does not affect errors reported via the newrelic_notice_error API. Upgrade Notices Guzzle support is now enabled by default. It can be disabled by setting the new newrelic.guzzle.enabled setting to false. The guzzle feature flag that was previously used to enable Guzzle support is now ignored. Bug Fixes The first request in each PHP process would remove any output handlers installed using the output_handler configuration setting for users of PHP 5.4 and later. This has been fixed: existing output handlers will now remain untouched. Transient WordPress hooks now have the unique numbers removed from their names to avoid metric grouping issues. In cases where WordPress' WP_CONTENT_DIR directory was set to a custom value, WordPress plugin metrics were not reported on PHP 5.2 to 5.4, inclusive. This affected users of the popular WP-Skeleton project. This has been fixed. A regression in version 6.3 could cause Guzzle 6 users to lose support for cross application tracing and service maps, in particular when Guzzle 6 was autoloaded as a result of instantiating the only GuzzleHttp\\Client object used within the lifetime of the script. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-640163","eolDate":"2019-06-14"},{"agent":"php","date":"2016-05-18","downloadLink":null,"version":"6.3.0.161","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Support for Postgres prepared statements has been added when the pg_prepare and pg_execute functions are used. The agent will now report Datastore metrics as well as capture slow queries. Bug Fixes Added a workaround for a stack corruption bug in very old versions of the Suhosin extension when used with PHP 5.3 or higher. The bug exists in Suhosin 0.9.29 and older versions only. Newer versions are not affected. Automatic transaction naming could fail in certain circumstances on Laravel 4.1 or higher on PHP 5 when a before route filter was installed. This has been fixed. Automatic transaction naming could fail on Laravel 5.x when a global middleware handled the request without forwarding it deeper into the application. For example, the default Authenticate middleware returns a 401 Forbidden response to unauthenticated requests, preventing proper transaction naming. This has been fixed. A segfault could occur in memory constrained environments, particularly on PHP 7. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-630161","eolDate":"2019-05-18"},{"agent":"php","date":"2016-05-02","downloadLink":null,"version":"6.2.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features We're proud to announce initial support for Alpine Linux 3.1 and newer. Currently, manual installation  is required.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-6210","eolDate":"2019-05-02"},{"agent":"php","date":"2016-04-12","downloadLink":null,"version":"6.2.0.158","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features The PHP agent now has support for Doctrine 2 DQL Queries. When running a DQL query, it will appear alongside the SQL in both Slow SQLs and Transaction Traces. Notes The agent now includes attributes for HTTP response headers in web transactions: response.headers.contentType response.headers.contentLength Bug Fixes newrelic.transaction_events.enabled wasn't being observed. This has been fixed. The PHP in SUSE and OpenSUSE Linux was incompatible with some of the agent's features, including RUM and CAT. This issue has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-620158","eolDate":"2019-04-12"},{"agent":"php","date":"2016-03-17","downloadLink":null,"version":" 6.1.0.157","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Support has been added for Magento 2. Bug Fixes Support for Laravel 5.2 has been added. Previously, Laravel 5.2 applications would fail to start with a BadMethodCallException. This was due to the agent's attempted use of a route filter for automatic transaction naming. Automatic transaction naming for Laravel 5.2 no longer relies on a route filter preventing the error. Automatic transaction naming for older versions of Laravel is unaffected. Calling phpversion(\"newrelic\") could return \"unreleased\" instead of the actual version number. In turn, this caused composer show --platform to report a version of 0. This has been fixed. The version number reported by phpinfo() was not affected by this bug. Fixed a potential segfault when using Zend_Http_Client under PHP 5.5 or 5.6 with OPcache enabled.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-610157","eolDate":"2019-03-17"},{"agent":"php","date":"2016-03-09","downloadLink":null,"version":"6.0.1.156","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug Fixes Fixed a bug that could cause segfaults on PHP 7.0 when a __call() method was invoked and was slow enough to generate a trace node.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-601156","eolDate":"2019-03-09"},{"agent":"php","date":"2016-03-07","downloadLink":null,"version":"6.0.0.155","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Support has been added for PHP 7.0.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-600155","eolDate":"2019-03-07"},{"agent":"php","date":"2016-02-18","downloadLink":null,"version":"5.5.0.154","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features The agent will now gather more information about the host system, including whether the system is running on Docker or AWS. This will be used to support upcoming features. Notes We've changed the timestamp source for error events, which drive the Error Analytics page. Previously, the event's timestamp was the transaction's start time. It is now the time when the error occurred.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-550154","eolDate":"2019-02-18"},{"agent":"php","date":"2016-01-26","downloadLink":null,"version":"5.4.0.150","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Experimental support for instrumenting Guzzle has been added. We are very pleased to announce that we've added experimental support for instrumenting Guzzle 3, 4, 5, and 6. Requests made using Guzzle will now show up as externals in the same way as requests made using other instrumented libraries, like curl, drupal_http_request(), and file_get_contents(). To enable the experimental support, you will need to add a feature flag to your newrelic.ini: newrelic.feature_flag = guzzle. NOTE: We intend to enable the Guzzle support by default in a future release. More information can be found on our Guzzle documentation page .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-540150","eolDate":"2019-01-26"},{"agent":"php","date":"2016-01-19","downloadLink":null,"version":"5.3.0.148","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features WordPress tab in the New Relic UI We're pleased to announce a new UI tab just for WordPress-specific data! WordPress applications now show information about their hooks, plugins, and themes. For more information, see WordPress-specific functionality .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-530148","eolDate":"2019-01-19"},{"agent":"php","date":"2015-12-15","downloadLink":null,"version":"5.2.0.141","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features On Linux, abstract sockets are now supported for agent to daemon communication. An abstract socket can be created by prefixing the value of the port setting in your newrelic.ini file (e.g. newrelic.daemon.port = \"@newrelic-daemon\") or newrelic.cfg file (e.g. port = \"@newrelic-daemon\"). The daemon can now be passed a --define <setting>=<value> flag that allows setting arbitrary parameters from your newrelic.cfg file. These parameters will take precedence over settings from that file. Drupal 8 requests that are successful full page cache hits for anonymous users (handled by Drupal\\page_cache\\StackMiddleware\\PageCache) are now given the name WebTransaction/Action/page_cache. Support for automatically naming transactions has been added for Symfony 2.8 and 3.0. Support for automatically naming transactions has been added for MediaWiki 1.18.0 and newer. Upgrade Notices It is now possible to disable reporting of errors for exceptions that are handled by an exception handler installed with set_exception_handler() by enabling the newrelic.error_collector.ignore_user_exception_handler setting. Calls to newrelic_notice_error with improper parameters will no longer record an error with the message \"?\". Instead, no error will be recorded. newrelic_notice_error will now return true if an error is saved, null if the arguments are invalid, and false otherwise. If newrelic_notice_error is called with two parameters and the second parameter is not a valid exception, no error will be recorded: The first parameter is now entirely unused. Bug Fixes On Redhat Enterprise Linux 7 and related systems such as CentOS and Fedora, the systemctl start|stop newrelic-daemon commands were not working due to a bug in the newrelic-daemon init script when executed by systemd. This has been fixed. On some Linux systems, an SELinux policy could prevent the newrelic-daemon from determining the correct hostname. Affected systems were unable to report data because a valid hostname is required by New Relic. This has been fixed. This issue could also prevent the newrelic-daemon from determining the correct hostname when running in a chrooted environment, or any environment in which access to the /proc filesystem is limited. Detection of Zend Framework 2.5 and later was unreliable when the framework was installed via Composer. This has been fixed. Detection of Laravel 5.1 and later was unreliable when artisan optimize was used. This has been fixed. The agent now sends the attribute request.headers.contentLength as an integer rather than a string.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-520141","eolDate":"2018-12-15"},{"agent":"php","date":"2015-11-17","downloadLink":null,"version":"5.1.1.130","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features With this release, the agent reports TransactionError  events. These new events power the beta feature Advanced Analytics for APM Errors  (apply here  to participate). The error events are also available through New Relic Insights .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-511130","eolDate":"2018-11-17"},{"agent":"php","date":"2015-11-09","downloadLink":null,"version":"5.1.0.129","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features To easily distinguish dynamically assigned hosts, users can now assign a display name to a host with the setting newrelic.process_host.display_name . The New Relic PHP Agent now supports the latest Production Release of 64-bit FreeBSD , which is currently at 10.2-RELEASE. Upgrade Notices Transactions run under PHP's CLI Web server will now report as Web transactions instead of background transactions. If you want the agent to continue reporting them as background transactions, use the newrelic_background_job()  API function to mark the transaction as a background job. Notes The agent now collects the following information in web transactions (not yet shown in the New Relic UI): Accept, Host, Content-Length, and Content-Type HTTP request headers, and HTTP request method.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-510129","eolDate":"2018-11-09"},{"agent":"php","date":"2015-10-26","downloadLink":null,"version":"5.0.0.115","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Users can now delete applications from the UI after 20 minutes of inactivity. Previously, this required a restart of the New Relic PHP daemon. Upgrade Notices We rearchitected the daemon to enable future improvements. Daemon log levels are now simpler. While verbose and verbosedebug will still work, debug now gives you all the debugging information. Agent log levels remain unchanged. End of Life Notices For the few customers who start the daemon manually, the newly renamed command-line flags can be found with the -h or --help flags. The following old flags will be removed in a future release: [-p pidfile] [-d level] [-c config] [-l logfile] [-P port] [-s] [-n] [-b SSL-certificate-bundle] [-S SSL-certificate-path] [-H host] [-x proxy] [-a auditlog]","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-500115","eolDate":"2018-10-26"},{"agent":"php","date":"2014-05-20","downloadLink":null,"version":"4.9.0.54","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features Added new local setting to enable high-security mode. newrelic.high_security = false This setting is false by default. When set to true, this setting has the following effects: Data will not be sent to New Relic unless the newrelic-daemon is using SSL. Raw SQL strings will never be gathered, regardless of the value of newrelic.transaction_tracer.record_sql. Request parameters will never be captured, regardless of the value of newrelic.capture_params. The following API functions will have no effect, and will return false: newrelic_add_custom_parameter newrelic_set_user_attributes If you change this setting, you must also change the RPM UI security setting. If the two settings do not match, then no data will be collected. Introduce new attribute configuration scheme. All parameters captured by the agent and created by the newrelic_add_custom_parameter API call are now considered attributes and have a new set of INI configuration options. As a result, the newrelic.capture_params and newrelic.ignored_params configuration options have been deprecated. The newrelic.ignored_params comparison will now be case-sensitive. For full information, please see the documentation . Bug Fixes The Laravel 4.0 framework is now supported in a manner analogous to the existing support for Laravel 4.1. (The portion of the routing code that is instrument changed the function names and arguments slightly going from Laravel 4.0 to Laravel 4.1.) Fix potential metric grouping issue with Kohana transaction naming. Previously, the agent would treat the first two segments of the request URI as the controller and action when no route was found. Now the agent will use 'unknown' as the transaction name when no route is found. This is consistent with the behavior for other frameworks.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-49054","eolDate":"2017-05-20"},{"agent":"php","date":"2014-04-24","downloadLink":null,"version":"4.8.0.47","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features Upgraded to cURL version 7.35 from 7.30. Upgraded to OpenSSL 1.0.1g from 1.0.1e. Bug Fixes Fixed an issue that would cause New Relic cross application tracing headers to accumulate during multiple curl_exec() calls. Fixed an issue with the installer when the path includes spaces. When newrelic-install.sh was run from a path that included spaces, such as /tmp/new relic/newrelic-php5-4.6.5.40-linux, the installation would fail. This has been corrected. Fixed an issue where not all Drupal 8 hooks were instrumented. While most Drupal 8 hooks are executed via ModuleHandlerInterface::invoke() and ModuleHandlerInterface::invokeAll(), a handful such as page_build are executed via variable functions by Drupal 8 as they require their arguments to be passed by reference. These hooks are now instrumented correctly.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-48047","eolDate":"2017-04-24"},{"agent":"php","date":"2014-04-01","downloadLink":null,"version":"4.7.5.43","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features Support for custom SSL trust stores It is now possible to configure the agent to use a custom SSL trust store to authenticate New Relic's servers. In most cases this should not be necessary. The agent ships with the necessary certificates and will use them unless configured not to do so. Caution should be used with these settings. If the trust store does not contain the necessary certificates, the agent will be unable to report data to New Relic. See the documentation  for more details. Bug Fixes drupal_http_request responses that redirect are no longer double counted External metrics created when drupal_http_request received a HTTP response that was a redirect, such as a 302 Found response, would have their execution time counted and call count incremented twice. The double counting has been removed, and the entire external time will be counted including any redirects. Fixed potential OpenSUSE 11.4 segmentation fault during Apache graceful restart","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-47543","eolDate":"2017-04-01"},{"agent":"php","date":"2014-02-27","downloadLink":null,"version":"4.6.5.40","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 End of Life Notices This release no longer supports BSD (either 32-bit or 64-bit) or the 32-bit variant of Mac OS X. New Features Add Laravel 4.0 support Laravel version 4.0 or greater is now supported natively. The naming scheme that we use follows the scheme developed by Patrick Leckey at Intouch Insight, and we are very grateful for his assistance. If you are already using the LaravelNewrelicServiceProvider from https://packagist.org/packages/intouch/laravel-newrelic  then we recommend removing that from the list of service providers, and relying on our native support instead. However, if you are using the custom naming mechanism with 'name_provider' from the intouch/laravel-newrelic package, then those transaction names will take precedence over our automatically generated transaction names. If you do use 'name_provider', please write us and let us know what your namer does so we might extend our built in capabilities. Bug Fixes Improved real user monitoring Javascript insertion. The real user monitoring Javascript loader will now be injected after any meta charset tag, ensuring that the meta charset tag is close to the beginning of the page. The real user monitoring Javascript footer will no longer be inserted into HTML comments or nested HTML iframes. Properly observe newrelic.ignored_params when capturing the request's URL. If newrelic.capture_params is true then the agent will capture the values within the $_REQUEST parameter and the full raw URL of the request. The contents of newrelic.ignored_params are used to selectively ignore values from $_REQUEST. The presence of newrelic.ignored_params will now also prevent the capturing of query parameters in the request URL. Fix transaction naming when newrelic.webtransaction.name.functions is present. When newrelic.webtransaction.name.functions had a non-empty value, the URL was being used as the default web transaction name instead of the PHP filename. Print backtrace to log file in the event of a segmentation fault. This functionality has been missing since release 4.4.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-46540","eolDate":"2017-02-27"},{"agent":"php","date":"2014-02-13","downloadLink":null,"version":"4.5.5.38","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 We're happy to announce the availability of version 4.5.5.38 of the New Relic PHP Agent, featuring Drupal 8 instrumentation. More details below. End of Life Notices This release no longer supports any backdoor exceptions to run threaded Apache MPM. PHP itself is unstable in this environment. This is the last release of the PHP agent for BSD (either 32-bit or 64-bit.) This is the last release for the 32-bit variants of Mac OSX. 64-bit Mac OSX will still be supported. This release no longer ships with any backdoor support for PHP 5.1. New Features Experimental Drupal 8 support Drupal 8 is now supported by the PHP agent's framework detection code. This support should be considered \"experimental\" given the pre-release nature of Drupal 8. Drupal 8 applications will have their transactions named correctly, and will also generate the same module, hook and view metrics as Drupal 6 and 7 applications. This support can be forced by setting the newrelic.framework configuration setting to drupal8 if auto-detection fails. Upgrade Notices All customers running on old x86 hardware that does not support the SSE3 instruction set (such as early releases of the AMD Opteron) should upgrade to this release as soon as possible. Prior to this release, the daemon inadvertently contained SSE3 instructions which would cause an illegal instruction on such hardware. The only way the SSE3 instructions were executed was when we changed the choice and priority of SSL cipher algorithms at our data center, and we would like to change those priorities by the end of 2Q2014. Bug Fixes Fixed a bug with file_get_contents instrumentation. Fixed a bug which would cause the default context to be ignored by file_get_contents when a context parameter was not provided. This issue was causing customer API calls to fail in certain situations. The previous remedy was to disable cross-application tracing to work around the issue. This is now fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-45538","eolDate":"2017-02-13"},{"agent":"php","date":"2014-01-08","downloadLink":null,"version":"4.4.5.35","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the New Relic PHP Agent improves real user monitoring and adds support for custom parameters in transaction analytics events. These changes were made to create a solid foundation for future enhancements. Additionally, an emphasis was placed on reducing the download size of the agent. As a result, the download size has been reduced by 75%. New Features Improve Real User Monitoring The PHP agent's code for both automatic and manual injection of Real User Monitoring scripts has been improved. No application changes are required, but the new injection logic is simpler, faster, more robust, and paves the way for future improvements to Real User Monitoring. Attach custom parameters to analytics events Custom parameters given to the agent through the API functions newrelic_add_custom_parameter and newrelic_set_user_attributes can now be automatically attached to transaction and page view analytics events. By default custom parameters will be attached to traces, errors, and transaction analytics events. Optionally, custom parameters can also be included in the JavaScript injected for Real User Monitoring. This allows custom parameters to be attached to page view analytics events. The behavior of custom parameters can be controlled through the following configuration settings, which are shown with their default values. newrelic.transaction_tracer.capture_attributes = true newrelic.error_collector.capture_attributes = true newrelic.analytics_events.capture_attributes = true newrelic.browser_monitoring.capture_attributes = false","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-44535","eolDate":"2017-01-08"},{"agent":"php","date":"2013-12-11","downloadLink":null,"version":"4.3.5.33","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the PHP agent automatically marks Drupal cron requests as background tasks, improves the categorization of PHP errors within the New Relic UI, and fixes several bugs. Additionally, the internals of the agent have been significantly refactored to improve the stability and performance of the agent. New Features Treat Drupal cron requests as background tasks Drupal cron requests (identified by calls to drupal_cron_run()) will now be counted as background tasks (not web transactions) regardless of how they are started. Previously, it was necessary to use the newrelic_background_job() API to explicitly mark Drupal cron requests as background tasks. Use the exception class as the category for errors Errors created using the newrelic_notice_error() API function with an exception will be grouped according to the exception's class. Previously, all errors were grouped under 'NoticedError'. See https://docs.newrelic.com/docs/php/the-php-api#api-notice-error Limit the maximum number of nested PHP function calls The agent will now limit the maximum number of nested function calls within PHP applications. This is to provide protection against stack overflows due to infinite recursion. Previously, this would result in a segmentation fault. The agent will now log an error and terminate the process by raising a fatal PHP error. By default, this limit is set to a very high value of 500. Exceeding this limit should be extremely rare. Improve the stability and performance of the agent The internals of the agent and its background daemon process have been significantly refactored to improve interprocess communication, stability and performance. The maximum number of connections to the background daemon process has been doubled to 4096. Bug Fixes Fix for installing on Ubuntu 13.10 when using PHP-FPM Previously the installer would fail to install a newrelic.ini file in the configuration directory for PHP-FPM (/etc/php5/fpm/conf.d), if one was present. This has been fixed, and the installer will correctly install a newrelic.ini for CLI, DSO and FPM configuration directories. Fix for drupal_http_request() always returning NULL under PHP 5.5 Version 3.9.5.13 added support for external calls made using drupal_http_request(). Due to the way the agent instruments this function under PHP 5.5, this function would always return NULL instead of the correct return value. This has been fixed. Fix for real user monitoring when a Content-Length response header is present. When automatic real user monitoring is enabled, the agent will only perform JavaScript injection into HTML pages when a Content-Length header is not already present in the response. In some cases, this check was not working correctly leading to the value in the Content-Length header not matching the actual number of bytes sent to the client. Fixed a segmentation fault when Zend Thread Safety is enabled. Attempts to use the agent under Apache using a threaded MPM (e.g. worker or event) and mod_php would result in segmentation faults. This has been fixed, but New Relic does not recommend  using the agent in these circumstances. Fixed high CPU usage under heavy load Under very high loads with thousands of PHP processes, the background daemon process could consume 100% CPU when the per-process file descriptor limit was exceeded. This has been fixed. The agent will now throttle the number of new connections accepted when per-process file descriptor limit is reached. A message is also printed to the log file.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-43533","eolDate":"2016-12-11"},{"agent":"php","date":"2013-11-20","downloadLink":null,"version":"4.2.5.27","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fix a segfault that could occur when the daemon was unable to bind to its listening socket during startup. The watcher process would then attempt to spawn a new daemon process leading to another segfault creating a loop. This loop would then cause the daemon log file to grow indefinitely. All customers are encouraged to upgrade.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-42527","eolDate":"2016-11-20"},{"agent":"php","date":"2013-11-13","downloadLink":null,"version":"4.2.5.26","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 We've added support for Symfony 2. Symfony 2 controller names will now show up in the web transactions view. This is an intermediate step leading up towards future Drupal 8 support. We have improved Zend Framework 1 transaction naming in order to reduce instances of metric grouping issues. We have tidied up our code for handling slow SQL statements.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-42526","eolDate":"2016-11-13"},{"agent":"php","date":"2015-07-24","downloadLink":null,"version":"4.23.4.113","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bug Fixes A memory leak that could occur when a large number of PDO or mysqli statements were prepared and executed has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-4234113","eolDate":"2018-07-24"},{"agent":"php","date":"2015-07-20","downloadLink":null,"version":"4.23.3.111","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bug Fixes This release fixes a rare bug where applications that had the ionCube loader enabled and called set_exception_handler() repeatedly could crash. New Features Exceptions that are ignored by Laravel 5's default exception handler will also now be ignored by the PHP agent's error reporting feature. This can be controlled by adding or removing entries in the dontReport property of Laravel's default exception handler, as described in the Laravel documentation .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-4233111","eolDate":"2018-07-20"},{"agent":"php","date":"2015-07-10","downloadLink":null,"version":"4.23.1.107","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bug Fixes Under certain circumstances, version 4.23.0 of the PHP agent could crash when newrelic_set_appname() or newrelic_end_transaction() were called and a custom exception handler had been installed via set_exception_handler(). This has been fixed. Under certain circumstances, Drupal applications that rely on the newrelic_set_appname() API function to start transactions would not see the Drupal tab in the New Relic UI. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-4231107","eolDate":"2018-07-10"},{"agent":"php","date":"2015-07-08","downloadLink":null,"version":"4.23.0.102","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Exceptions that are uncaught and handled only by a last resort exception handler installed via set_exception_handler()  will now generate errors that can be viewed in the APM UI. Previously they would not be sent to New Relic at all. As a result of this, some customers will see more errors in the APM UI than they had previously seen. Bug Fixes In certain circumstances, such as an exception being thrown during database connection, errors generated by uncaught exceptions could result in the stack trace shown in APM including function argument values, which could potentially expose database passwords and other sensitive information. This problem has been fixed. We now catch these formerly-uncaught exceptions and thus have control over how the stack trace is built, ensuring that function argument values will no longer show up in those stack traces.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-423","eolDate":"2018-07-08"},{"agent":"php","date":"2015-06-03","downloadLink":null,"version":"4.22.0.99","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Support for the Predis library The PHP agent now supports the Predis library. Users of this library will see new metrics in the Database tab, nodes in transaction traces, and breakdown metrics on individual transaction pages. Pipelining multiple commands will result in those commands being grouped and treated as a single command metric named pipeline. Note that our Predis support does not include instrumentation for commands wrapped in MULTI and EXEC via the Predis client's transaction method. We also do not instrument the executeRaw or monitor methods of Predis, nor its PubSub functionality. Increased specificity of PECL Redis metrics Metrics made for the PECL Redis extension will now more closely match the name of the function called. For example, the redis::setex method will now create a metric with the text setex, rather than simply set. Named Laravel Artisan commands Background transactions that are Laravel Artisan commands are now named. Instead of being named unknown, Laravel Artisan commands will now be named based on the command. For instance, the command ./artisan cache:clear will result in a background transaction named Artisan/cache:clear. UTC offsets in agent logfiles The log file format has been extended to include the UTC offset of the local time zone. This makes it easier to match log entries to time windows in the New Relic UI.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-422099","eolDate":"2018-06-03"},{"agent":"php","date":"2015-04-30","downloadLink":null,"version":"4.21.0.97","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Zend Framework 2 transaction naming support Support has been added for naming transactions automatically based on ZF2 route names. Transaction naming will work with routes set in module.config.php, or anything else using the setMatchedRouteName method of Zend\\Mvc\\Router\\RouteMatch (or the same methods of the corresponding HTTP and Console routers). For example: 'router' => array( 'routes' => array( 'route1' => array( ... ) 'route' => '/foo[/:bar][/:baz]', 'constraints' => array( ... ), 'defaults' => array( ... 'route2' => array( ... ) Anything the router matches to route1 will be named route1 regardless of URL, parameters or controller. 404 errors and similar will be named \"unknown\". Silex transaction naming support Support has been added for naming transactions automatically based on Silex controller names. If a route name has been set using the Controller::bind() method, then that will be used, otherwise the default controller name generated by Silex will be used instead. For example: // This will be named with the autogenerated \"GET_hello_name\". $app->get('/hello/{name}', function ($name) { ... }); // This will be named \"hello\", as bound. $app->get('/hello/{name}', function ($name) { ... })->bind('hello'); Automatic transaction naming will work on all Silex 1.x versions provided the default kernel service has not been replaced with an object of a type other than Symfony\\Component\\HttpKernel\\HttpKernel. If the kernel service has been replaced with something else, you will need to continue to use the newrelic_name_transaction function to name your transactions. End of Life Notices memcacheDuration attributes have been removed. A bug in version 4.19 of the PHP agent removed support for memcacheDuration attributes in Transaction events. We have decided not to restore this functionality, as these durations are now accounted for in databaseDuration attribute values. Bug Fixes databaseDuration attributes have been restored. A bug in versions 4.19 and 4.20 of the PHP agent resulted in databaseDuration attributes no longer being attached to Transaction events. These have been restored, with one change: they now also include time spent in Memcached operations, as these are now unified with other datastores in New Relic APM. Fix application name rollup ordering issue. When using application rollup names, the agent had the restriction that any name could only appear as the first rollup name once, which prevented the simultaneous connection of a;b and a;c. This restriction has been removed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-421097","eolDate":"2018-04-30"},{"agent":"php","date":"2015-04-13","downloadLink":null,"version":"4.20.2.95","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bug Fixes Support for mixed Laravel 4 and 5 environments has been improved. Web servers serving both Laravel 4 and Laravel 5 applications from the same process pool could see autoloader errors in the Laravel 4 applications after the first load of a Laravel 5 page. This has been fixed, and mixed environments should now work as expected. Laravel detection has been improved. Starting with Laravel 5.0.15, applications with an optimized classloader use a new location for the optimized \"compiled.php\" file. Previously, the agent would fail to detect Laravel in this circumstance. The agent now looks in this new location as well as the old location for Laravel auto-detection.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-420295","eolDate":"2018-04-13"},{"agent":"php","date":"2015-04-02","downloadLink":null,"version":"4.20.1.93","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bug Fixes MySQLi segfaults fixed. Version 4.20.0 could cause the PHP agent to segfault when certain types of parameters were bound to mysqli_stmt objects. This has been fixed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-420193","eolDate":"2018-04-02"},{"agent":"php","date":"2015-04-01","downloadLink":null,"version":"4.20.0.92","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Release Unavailable Due to a bug in this release related to the new explain plan support for MySQLi, we have decided to remove it from our download servers. Instead, we recommend installing version 4.20.1 , which includes a fix for this bug. New Features Support for Laravel 5.0. We are pleased to announce support for the latest Laravel release: Laravel 5. Sites and applications using Laravel 5.0 are now automatically detected and named in the same way as Laravel 4 applications. Support for explain plans with MySQLi. The existing support for generating explain plans for slow SELECT queries with the PDO MySQL driver has been extended to MySQLi. Explain plans are controlled by the newrelic.transaction_tracer.explain_enabled  and newrelic.transaction_tracer.explain_threshold  settings. These plans can be seen in the query analysis section of the slow SQL trace  page in APM. Explain plans will be generated for queries issued through mysqli_query, mysqli_real_query, and mysqli_stmt_execute, as well as their OO equivalents mysqli::query, mysqli::real_query, and mysqli_stmt::execute. Please note that the mysqli_multi_query API is not currently supported, and that explain plans are not generated for multiple (semicolon separated) queries. Added Memcache connection monitoring. The connect and pconnect functions (and their OO counterparts) of the Memcache extension are now instrumented, and will generate metrics. As a result, if there is a problem with calling those functions, it will now be visible within New Relic. Bug Fixes Laravel 4 App::after() filters are no longer overridden. In certain circumstances, the improved Laravel transaction naming code in version 4.19 of the PHP agent could result in filters registered using Laravel 4's App::after() method no longer being executed. This has been fixed. Upgrade Notices The daemon now uses openssl 1.0.1m, rather than 1.0.1l. The daemon now uses curl 7.41.0 rather than 7.40.0.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-420092","eolDate":"2018-04-01"},{"agent":"php","date":"2015-03-04","downloadLink":null,"version":"4.19.0.90","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Unified view for SQL database and NoSQL data stores The agent will now provide a breakdown of SQL operations according to the database product being used. This is in addition to the existing breakdown of SQL statements and operations. For NoSQL data stores, the agent will now provide a similar breakdown of the operations performed. Memcached and Redis time reported separately Previously, the agent grouped Memcached and Redis operations into a single Memcached category. This is no longer the case. Time spent performing Memcached or Redis operations are separate. Bug Fixes Laravel transaction naming improvements Prior to this version, Laravel applications that had replaced the default router service could find that, in some circumstances, their transactions would be named as \"unknown\" rather than being correctly named from the route. This has been improved: replacement router services will now get appropriate transaction naming provided that they either implement filtering or ensure that the same events are fired as the default Laravel router.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-419090","eolDate":"2018-03-04"},{"agent":"php","date":"2015-02-17","downloadLink":null,"version":"4.18.0.89","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Support for synthetic monitoring. The PHP agent now gives you additional information for requests from synthetic monitors when the newrelic.synthetics.enabled setting is enabled. The agent records more transaction traces and events for synthetic-originated requests to give you a clearer look into how your application is performing around the world. For more details, see https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/getting-s... Add a new newrelic_record_custom_event API function. This API function allows you to add custom events to New Relic's Insights product. For more information, please see: https://docs.newrelic.com/docs/insights/new-relic-insights/adding-queryi... The daemon now uses openssl 1.0.1k, rather than 1.0.1j. Bug Fixes The agent properly recognizes prepared statements constructed with mysqli_stmt::__construct(). The newrelic-install script has been fixed to once again work for users with custom extension_dir settings. Notes The ability to set the appname to a string like: %{FOO} and have FOO expand into the environment variable was removed.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-418089","eolDate":"2018-02-17"},{"agent":"php","date":"2015-01-02","downloadLink":null,"version":"4.17.0.83","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bug Fixes Fix a memory leak affecting newrelic_add_custom_parameter API function.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-417083","eolDate":"2018-01-02"},{"agent":"php","date":"2014-12-19","downloadLink":null,"version":"4.17.0.79","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bug Fixes The agent now uses the route pattern as the transaction name for unnamed, closure-based routes under Laravel. For example, the following route will now be named hello/{name}  instead of GET/index.php . Route::get('hello/{name}', function($name) { return \"Hello ${name}!\"; }); Previously the agent could fail to detect the Laravel framework when artisan optimize was used. This has been fixed. When the agent cannot determine a transaction name for the Laravel framework, the name \"unknown\" will be used instead of \"laravel-routing-error\". The latter implied the cause of the failure may have originated within Laravel itself rather than solely within the agent's instrumentation.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-417079","eolDate":"2017-12-19"},{"agent":"php","date":"2013-10-28","downloadLink":null,"version":"4.1.5.24","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Transaction traces containing many consecutive calls to curl_multi_exec will now show the cumulative time as a single node. Previously the transaction trace would show one node for each call. We fixed segmentation faults when restarting Apache on Darwin and FreeBSD. We corrected an issue in the newest Debian-based Linux distributions that prevented the newrelic.ini file from being installed properly. A warning message is put in the agent log when newrelic_name_transaction() fails.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-41524","eolDate":"2016-10-28"},{"agent":"php","date":"2014-10-28","downloadLink":null,"version":"4.15.0.74","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features The daemon now uses openssl 1.0.1j, rather than 1.0.1h. Support for generating explain plans for SELECT queries issued using the PDO MySQL driver has been added. When the newrelic.transaction_tracer.explain_enabled  setting is enabled and a SELECT query is issued through a PDO connection to MySQL that takes longer than newrelic.transaction_tracer.explain_threshold , an explain plan will be generated and will appear within the query analysis section of the slow SQL trace . Bug Fixes Fix an issue that could cause some background task metrics to be attributed to web transactions and some web transaction metrics to be attributed to background tasks. This could affect Drupal customers whose applications use drupal_cron_run. This release changes the handling of HTTP Referer headers to always strip query parameters before reporting to New Relic. Previously, any query parameters present in a Referer header would be reported to New Relic by the PHP agent. Fix an issue where urls using the file: protocol scheme with curl_exec() would cause the agent to record external metrics. This has been corrected and the agent will no longer treat file urls as external services.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-415074","eolDate":"2017-10-28"},{"agent":"php","date":"2014-09-24","downloadLink":null,"version":"4.14.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Support for agent-side configuration of application labels using the newrelic.labels INI setting has been added.\nNew Relic enables you to label and organize your apps so they \"roll up\" into an unlimited number of meaningful categories. You can also easily sort, filter, and page through all the applications on your account's Applications list.\nSee the New Relic APM documentation  and the PHP agent (newrelic.ini) settings documentation  for more details. Bug Fixes Fixed issue that could prevent capturing database table name for prepared statements on PHP 5.6.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-4140","eolDate":"2017-09-24"},{"agent":"php","date":"2014-09-11","downloadLink":null,"version":"4.13.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bug Fixes Fix an edge case segfault that could occur in situations where the daemon failed to initialize.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-4131","eolDate":"2017-09-11"},{"agent":"php","date":"2014-09-10","downloadLink":null,"version":"4.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features [#features] Added support for the PHP Agent on Heroku We now support running PHP Applications on Heroku using the New Relic for Web Apps  add-on. For more information, see PHP agent and Heroku  and the Heroku Dev Center documentation .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-4130","eolDate":"2017-09-10"},{"agent":"php","date":"2014-08-28","downloadLink":null,"version":"4.12.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features [#features] Added two new attributes to transaction events: errorMessage and errorType. These attributes allow for the tracking of errors within the Insights product. As a result, error messages will no longer be recorded if the agent is in high-security mode. Background tasks will now create Transaction events which can be tracked in the Insights product. Bug Fixes [#bugs] Fixed request queuing metrics support\nThe PHP Agent will now allow the leading t= prefix to be optional when parsing HTTP_X_REQUEST_START and X-Request-Start headers. Previously, the header would be treated as absent if no leading t= was included. Fixed presentation of the newrelic.daemon.proxy setting in phpinfo() \nThe phpinfo()  function will now display a value of no value as the default for the newrelic.daemon.proxy setting. Previously, it would incorrectly display a value of ***INVALID FORMAT***.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-4120","eolDate":"2017-08-28"},{"agent":"php","date":"2014-08-25","downloadLink":null,"version":"4.11.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"<div id=\"watermark\">End of Life</div> <div class=\"callout-important\"><p>The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see <a href=\"/docs/agents/manage-apm-agents/installation/update-new-relic-agent\">Update the agent</a>. For more information, see <a href=\"/docs/agents/manage-apm-agents/maintenance/new-relic-agent-plugin-end-life-policy\">End-of-life policy</a>.</p></div> Bug Fixes Fix to prevent proxy credentials transmission This update prevents proxy credentials set in the agent config file from being transmitted to New Relic.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-4111","eolDate":"2017-08-25"},{"agent":"php","date":"2014-07-31","downloadLink":null,"version":"4.11.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Our long-awaited support for Joomla 2.x and 3.x have been added. The PHP agent now instruments and names Joomla transactions without the need for additional plugins. Bug Fixes Prevent injection of page load timing JavaScript when the Content-Type is first set to text/html  then changed to something else, such as application/json . Fix Zend Framework transaction naming when exit() is called during request processing. Previously, it was possible to exit before the agent set the transaction name. This caused the transaction to be reported as index.php , an issue that most commonly occurs with the Redirect action helper. The agent now correctly names these transactions. Fix segfault triggered by JSON encoding when strings to be encoded are marked as UTF-8, yet contain invalid UTF-8 byte sequences.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-4110","eolDate":"2017-07-31"},{"agent":"php","date":"2014-07-01","downloadLink":null,"version":"4.10.1.62","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Bug Fixes Fixed an issue whereby Debian and Ubuntu users running the daemon via the init script may have been unable to start the daemon after upgrading to 4.10.0. This has been fixed by reverting back to the init script used in 4.9.0 and earlier versions.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-410162","eolDate":"2017-07-01"},{"agent":"php","date":"2014-06-30","downloadLink":null,"version":"4.10.0.60","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 End of Life Notices The MacOSX/Darwin agent and daemon are now compiled only for Mac OS X 10.6 or higher. New Features Changed the daemon to use openssl 1.0.1h, rather than 1.0.1g. Logging to stdout and stderr is now supported when running the daemon in the foreground. Created new installer for Ubuntu/Debian systems. If the application name is not present, the installation process will ask for one. Also, Debian/Ubuntu users do not have to run the newrelic-install script. Upgrade Notices The agent now supports PHP 5.6beta4. Bug Fixes Zend externals could be double counted when the cURL adapter was used. In previous versions of the agent, using Zend_Http_Client::setAdapter() with an instance of Zend_Http_Client_Adapter_Curl caused the agent to double count the external call. This has been fixed. Prevent real user monitoring javascript injection when a Content-Type header has not been set and the default mimetype is not text/html.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-410060","eolDate":"2017-06-30"},{"agent":"php","date":"2013-09-30","downloadLink":null,"version":"4.0.5.18","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 histograms and percentiles PHP 5.5 support added PHP 5.1 deprecated Various bug fixes and stability improvements.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-40518","eolDate":"2016-09-30"},{"agent":"php","date":"2013-09-12","downloadLink":null,"version":"3.9.5.13","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 two additional external calls has been added to cross application tracing . Zend_Http_Client::request() drupal_http_request()","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-39513","eolDate":"2016-09-12"},{"agent":"php","date":"2013-08-29","downloadLink":null,"version":"3.8.5.11","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Preliminary support for Cross Application Tracing  has been added. The following external calls are supported. curl_exec() file_get_contents() httprequest::send() Communication between the agent and the daemon process has been improved, fixing a rare issue that could affect data quality. Fixes a rare issue where too many daemon processes could be launched. Various bug fixes and stability improvements.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-38511","eolDate":"2016-08-29"},{"agent":"php","date":"2013-06-11","downloadLink":null,"version":"3.7.5.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Magento transaction naming has been refined MySQL errors will now be recorded properly under PHP 5.1 Request queue timing can be specified with X-Request-Start as well as HTTP_X_REQUEST_START Other small bugfixes","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-3757","eolDate":"2016-06-11"},{"agent":"php","date":"2013-06-03","downloadLink":null,"version":"3.6.5.178","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Data uploads to the New Relic collectors now default to SSL. SSL can be disabled through the configuration file. The agent now carries its own SSL certificate bundle, improving portability across platforms. Queuing time display has been corrected for certain dispatcher configurations. Various stability and performance enhancements.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-365178","eolDate":"2016-06-03"},{"agent":"php","date":"2013-05-22","downloadLink":null,"version":"3.5.5.172","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Patch release to fix an occasional segmentation fault when using Drupal.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-355172","eolDate":"2016-05-22"},{"agent":"php","date":"2013-05-15","downloadLink":null,"version":"3.5.5.170","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Drupal module instrumentation has been enhanced. The agent can now instrument Drupal hooks and view execution. The agent now reports the 50 most frequently called functions and the 50 slowest functions for individual requests. This data is now used on the Transaction Trace Summary tab allowing a more accurate and complete display of slowest components. Auto-detection of local SSL certificates has been improved. Various stability and performance enhancements.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-355170","eolDate":"2016-05-15"},{"agent":"php","date":"2013-05-01","downloadLink":null,"version":"3.4.5.167","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 can now write an audit log that shows an unencrypted stream of all information sent to New Relic’s servers. The audit log can potentially use up a lot of disk space, so it’s best to use this on an as-needed basis. In addition to wall-clock time, CPU time (a.k.a. “burn”) is included at the top of transaction traces in the New Relic user interface. SSL connections to New Relic collectors are now kept alive for the entire application data harvest, rather than re-negotiated for each application during the harvest. The agent will attempt to auto-detect client SSL certificates on FreeBSD. This agent release also includes various bug fixes, including ones concerning obfuscated SQL processing and cross-application data leakage.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-345167","eolDate":"2016-05-01"},{"agent":"php","date":"2013-04-25","downloadLink":null,"version":"3.3.5.161","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 previous fix for the daemon spin was incomplete. This release correctly fixes the problem we identified.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-335161","eolDate":"2016-04-25"},{"agent":"php","date":"2013-04-23","downloadLink":null,"version":"3.3.5.160","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 a bug that was causing the daemon to spin and consume 100% of a CPU Removed the 45 application limit","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-335160","eolDate":"2016-04-23"},{"agent":"php","date":"2013-04-11","downloadLink":null,"version":"3.3.5.154","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Increase visibility into errors by adding error type (eg E_WARNING) to captured errors. Refactor changes to local daemon to increase simplicity and stability. Prevent duplicate log file descriptors on Apache restart.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-335154","eolDate":"2016-04-11"},{"agent":"php","date":"2013-02-27","downloadLink":null,"version":"3.2.5.147","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Prevent potential memory leak by daemon when connecting applications. Ensure that the agent will not block when attempting to connect to the daemon. Fix potential locking bug during daemon's application harvest cycle.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-325147","eolDate":"2016-02-27"},{"agent":"php","date":"2013-02-12","downloadLink":null,"version":"3.2.5.143","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Show full URL of external calls in transaction trace nodes. Username, password, and query parameters are stripped from the URL. Fixed a bug causing time spent in background CLI tasks to be included in main overview graph. Fixed a bug causing incorrect custom tracer metrics in the event of out of order clock times. Look for and respond to 'X-NewRelic-ID' header in all incoming http requests. This change helps improve the correlation of performance between services in a service-oriented architecture for a forthcoming feature. In the meantime, if you wish to disable the header, set 'newrelic.cross_process.enabled=0' in your .ini file.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-325143","eolDate":"2016-02-12"},{"agent":"php","date":"2013-01-25","downloadLink":null,"version":"3.1.5.141","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bugfixes Correctly destroy a thread mutex that was sometimes not being destroyed. Correctly obey newrelic.capture_params INI setting in regards to URL get parameters.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-315141","eolDate":"2016-01-25"},{"agent":"php","date":"2013-01-16","downloadLink":null,"version":"3.1.5.137","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bugfixes Fixed an issue where massive log files were created if the agent received a SIGSEGV. Fixed an issue that occasionally caused SIGSEGV's when using RUM2.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-315137","eolDate":"2016-01-16"},{"agent":"php","date":"2013-01-08","downloadLink":null,"version":"3.1.5.136","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Revert to using a UNIX-domain socket for agent to daemon communication. This is the same mechanism used in the 2.x and 1.x series of agents. This was done for speed purposes. The default socket path is the same as it was for the older versions of the agent: /tmp/.newrelic.sock. The newrelic.daemon.port option in the INI file and the portoption in the daemon configuration file (newrelic.cfg) can now take either a path to a UNIX-domain socket, or an integer in the range 1-65534. If you use a path, then a UNIX-doman socket will be used. If you use an integer, then a TCP socket will be used on the specified port. Correct the \"banner\" displayed in the log file to show the version of the running PHP. Previously it was incorrectly showing the version that we had compiled with. On platforms that support it, now attempt to display a stack dump in the unlikely event that the agent receives a SIGSEGV signal due to a bug. Displaying this stack is not always possible but when it works it is a big help for technical support to diagnose the exact cause of the problem. This feature existed in the 2.x series of agent but was not working correctly in the 3.x series until now. Fixed a problem where a communications failure between the agent and daemon when sending a transaction trace would result in a core dump (rare). Fixed a problem with Memcache metrics using the wrong metric name. Fixed a coredump that would occur when sending SQL tracers that were both un-obfuscated and contained lots of UNICODE characters (very rare). If a SIGSEGV signal is ever received make sure the daemon exits completely so that it can be respawned. Under certain conditions it could become \"stuck\" which would slow down the agent and stop all data from being sent to New Relic.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-315136","eolDate":"2016-01-08"},{"agent":"php","date":"2012-12-03","downloadLink":null,"version":"3.1.5.120","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bugfixes This release is a bug-fix release only and adds no new features to the agent. The following bugs introduced in 3.0/3.1 have been fixed: Fixed two segmentation violations that would occur after calling the newrelic_set_appname() API call. One had the potential to affect all users, the other was restricted to customers who used prepared SQL statements both before and after the call to newrelic_set_appname(). Fixed a problem with the Solaris init scripts which made the incorrect assumption about the process ID of init. Fixed a small memory leak that affected CodeIgniter, CakePHP and Drupal applications.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-315120","eolDate":"2015-12-03"},{"agent":"php","date":"2012-11-20","downloadLink":null,"version":"3.1.5.111","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the New Relic PHP agent adds two major new features, and includes several important bug fixes and stability improvements. The new features are: Key Transaction Support, and Real User Monitoring improvements. Key transactions (discussed here ) allow you to mark transactions that are important to your specific business needs and can have their own Apdex settings and error metrics. The Real User Monitoring (RUM) improvements allow you to link select transaction traces with browser traces. Other improvements include the ability for RUM to work with multiple application names, and delivery of the RUM JavaScript file will only use the https protocol if the main page was also delivered via https. The new newrelic_set_user_attributes() API call can now also be used to add additional data to browser traces. Please see this page  for details. The following smaller improvements and bug fixes have been made: Fixed an agent segmentation fault that occurred during Slow SQL processing at the end of a transaction. Fixed a daemon segmentation fault that occurred if the agent communication with the daemon was interrupted for any reason. Fixed a memory leak in the agent when the maximum number of Slow SQL statements for a transaction was reached. Fixed an error that was preventing the daemon from re-spawning a copy of itself if the worker daemon died due to a segmentation fault. Updated the newrelic_set_appname API call to no longer send the transaction thus far to the daemon unless you give it an argument explicitly requesting this behavior. This considerably reduces the overhead of changing application names on the fly. Updated the newrelic_end_transaction API call to allow you to decide whether or not the transaction should be sent to the daemon. It is by default. Fixed an error in the installer script where the license key was not being inserted into the INI file correctly. Functions with custom instrumentation (newrelic.transaction_tracer.custom) will now produce metrics that can be used in custom dashboards. If your application produces a Content-Length header, automatic RUM (\"auto-RUM\") will no longer inject the RUM header and footer, which would invalidate the content length calculated by your application. The NR_INSTALL_KEY environment variable is now correctly obeyed. The daemon is now compiled to support showing a backtrace in the event of a segmentation violation.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-315111","eolDate":"2015-11-20"},{"agent":"php","date":"2012-06-07","downloadLink":null,"version":"2.9.5.78","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: This is a very minor patch release to the 2.9 series of PHP agent. It contains only 1 small fix which only affects customers who use more than 1024 Apache worker processes: Added missing ulimit command to daemon startup script to correctly set the maximum number of open file descriptors that the daemon can handle, in case the system default is too low.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-29578","eolDate":"2015-06-07"},{"agent":"php","date":"2012-05-24","downloadLink":null,"version":"2.9.5.76","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: Added support as an external service for HttpRequest::Send Added limited support for curl_multi_exec. This will now show up as an external services call but will not provide insight as to how many or which web sites were handled by the function. CakePHP transaction naming considerably improved The daemon and agent now support up to 2048 file descriptors (up from 1024 on Linux). This is most relevant to larger sites that have > 1024 Apache worker processes. The daemon behaves better if the maximum number of open file descriptors is exceeded. The Debian installer no longer changes the permissions of the log directory if the system administrator had changed them. Also, if the log directory didnt exist (first time installation) default the ownership of the directory to the Apache user and group, if Apache is installed. SQL parser fix to avoid being confused by the words \"from\" or \"into\" appearing in table names.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-29576","eolDate":"2015-05-24"},{"agent":"php","date":"2012-04-24","downloadLink":null,"version":"2.8.5.73","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: Considerably more detailed transaction traces, reducing to almost nil the amount of \"uninstrumented time\" in TT graphs. Detailed TT's (the so-called \"top100\" feature) are now enabled by default. Reduced the overhead for detailed TT's dramatically, bringing it to within 2-3% of the agent speed without them enabled. Fixed a memory bug that was causing garbage metric names to be sent to the daemon and then on to RPM. Fixed erroneous behavior of the \"newrelic_end_of_transaction()\" API call. Previously it did not correctly end the transaction. The fix to reduce metric grouping issues with WordPress table names no longer causes the table names to produce a warning in the logfile.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-28573","eolDate":"2015-04-24"},{"agent":"php","date":"2012-03-15","downloadLink":null,"version":"2.7.5.69","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: Updated to work with Apache 2.4 The auto-RUM buffer is now erasable, but doing so will obviously prevent auto-RUM from inserting the RUM header and/or footer. Fixed a problem where WordPress blogs would result in metric explosion due to their database table naming scheme Support transactions that last longer than 35 minutes. Long-running cron jobs will no longer report negative time.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-27569","eolDate":"2015-03-15"},{"agent":"php","date":"2012-02-21","downloadLink":null,"version":"2.7.5.64","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 PHP 5.4RC8 or higher. Please note that versions prior to RC8 will not work correctly, especially not with auto-RUM. Also please heed the advice that the PHP developers themselves give about using the 5.4 release candidates: do not use it in production. Added the frequently-requested newrelic_set_appname() API that will allow you to change the name of the application on the fly. This should be called as early as possible, and cannot be called after the RUM footer has been sent. Fixed an occasional segmentation violation caused by the Slow SQL feature, especially when using the command line version of PHP. Fixed an occasional segmentation violation caused by auto-RUM. Fixed a problem where the ZTS-enabled version of the agent would cause a segmentation violation when used on the command line. Removed the colon from the list of characters that are invalid in SQL table names, and provide a mechanism to disable table name checking completely. Fixed a small (about 10 bytes per request) memory leak. Fixed an issue that would sometimes cause PHP execution time to not show up in the application overview graph. If you call the newrelic_ignore_transaction() API function, no longer produce automatic RUM headers and footers for that transaction.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-27564","eolDate":"2015-02-21"},{"agent":"php","date":"2012-01-16","downloadLink":null,"version":"2.6.5.57","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 using file_get_contents() could end up being mis-interpreted as an SQL node and cause a core-dump. This would only happen when Slow-SQL traces were enabled.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-26557","eolDate":"2015-01-16"},{"agent":"php","date":"2012-01-09","downloadLink":null,"version":"2.6.5.55","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 several issues that would cause Apache to core-dump. Not all users would see these faults, but a few did and those bugs have been fixed. Removed support for the PHP-only MediaWiki memcached client that was added in 2.6.5.41, as the code that was added to support this was part of what was causing random core dumps. It will be re-added in a future release. Use less system stack space when hooking PHP functions so that PHP code that is massively recursive runs less risk of overflowing the stack. Corrected the way the Mac OSX client was being built so it works on OSX 10.5. Fixed a potential buffer over-run error in the Zend and Magento framework code that would be provoked if a controller name was significantly longer than the module name. Removed the backslash from the list of illegal characters in SQL table names as some customers actually use it. Prevent a file descriptor leak if you do a soft restart of Apache.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-26555","eolDate":"2015-01-09"},{"agent":"php","date":"2011-12-16","downloadLink":null,"version":"2.6.5.44","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: There is an outstanding issue with the Zend View component where it kills the output buffer that auto-RUM relies on, so for this environment you will need to disable auto-RUM by setting newrelic.browser_monitoring.auto_instrument = 0 and doing manual instrumentation for the time being. Fixed a potential spin-loop that would cause the agent to consume 100% of the CPU if the underlying OS did not allow the daemon connection (even if the daemon was up and running). Only apply Real User Monitoring scripts to HTML content. Fix an issue if auto-RUM encountered content it couldn't parse, it would cause a segmentation violation and cause Apache to core-dump.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-26544","eolDate":"2014-12-16"},{"agent":"php","date":"2011-12-13","downloadLink":null,"version":"2.6.5.41","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 apt repository is now digitally signed, and in order to update the agent from this repository for Ubuntu or other Debian-like systems you will need to import the new GPG key using the following command (please note the trailing minus sign!): wget -O - https://download.newrelic.com/NEWRELIC_APT_2DAD550E.public | sudo gpg --import --batch --no-default-keyring --keyring /usr/share/keyrings/download.newrelic.com-newrelic.gpg A very special and big thank you to Nick Calugar of IGN Entertainment for suggesting improvements to the way in which Zend and Magento transactions are named. For these two frameworks the transaction naming is now more accurate and adds less overhead than the previous mechanism used to name transactions. This also fixed an issue where Magento transaction names sometimes had garbage characters in them or sometimes even PHP script fragments. In both cases the transaction is named 'module/controller/action' as it is for other frameworks. Another very special thank you to Roderick Smyth of Arithon in Dublin for absolutely invaluable help during the beta testing period and for testing the OCI8 support. Significant improvements to automatic Real User Monitoring (auto-RUM). The most important change is that auto-RUM is now implemented as an output filter so it now works for all frameworks, not just Drupal and Wordpress. It is also considerably more reliable as a result, as modules and other changes to the framework no longer impact how we insert the RUM header and footer. If you previous had to manually insert RUM headers and footers, you are strongly encouraged to re-enable auto-RUM and comment out your existing manual calls. To go with this change there is a new API call, 'newrelic_disable_autorum()' that you can call to prevent auto-RUM from running for a given transaction. For example you may want to disable auto-RUM for AJAX calls. Regardless of how it is invoked, the RUM footer will now never be ejected if the header was not also ejected in the same transaction. This prevents JavaScript errors if the header somehow fails to get inserted. The RUM header and footer have been very slightly modified to add a missing semicolon after the last script command. This also prevents some browsers and compliance analyzers from complaining about the JavaScript. Support for the MemCache-like features of Redis has been added. This is by no means full support for Redis, just those portions of the Redis API that map cleanly onto the existing MemCache metrics. They will show up in the overview graphs as MemCache activity, so if you use both MemCache and Redis the data will be merged, just as the overview for different SQL databases is merged. Considerably improved support for multi-framework sites (where more than one framework is in use for multiple parts of the same site). Instrumentation for framework-specific functions is now isolated on a per-request basis, so multiple requests handled by one PHP instance will no longer be confused by by the sudden change in framework. The logrotate script no longer conflicts with the version installed by the New Relic Server Monitor. Implemented a timeout for agent-to-daemon communication so that if the daemon becomes unresponsive for whatever reason, the agent will no longer hang (and thus appear to crash Apache) waiting for the daemon to recover. Correctly ignore user notice errors in the error handler. Added support for the deprecated but still frequently used mysql_db_query function. Added support for the Zend framework's Zend_Http_Client::request() method to track external service calls better in Zend. Added the ability to use the syntax newrelic.appname=\"%{VARIABLE}\"when setting the application name. This will use the SAPI's environment variable lookup mechanism to find VARIABLE and set the application name accordingly. The REPLACE SQL command verb will now be recognized and unique metrics generated for it rather than being lumped into \"other\". A thread mutex deadlock issue on OpenSolaris has been resolved. Support for the pure PHP MemCached client from Wikia has been added. file_get_contents() now shows up in the external services tab if the object being retrieved is remote and uses HTTP or HTTPS. The newrelic_notice_error() now has a third invocation form, which takes a string and an Exception object. If the string is provided it is used as the error message. If it is empty then a default string in a format similar to Exception::__toString() is automatically generated and used as the error message. The exception object provided will be used to create the stack trace for the exception so that you can see the stack trace at the time of the exception, rather than the stack trace at the time of displaying the exception. If you enable the capturing of request parameters by setting newrelic…","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-26541","eolDate":"2014-12-13"},{"agent":"php","date":"2011-11-10","downloadLink":null,"version":"2.5.5.29","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: New feature: slow SQL. This is very similar to transaction traces but instead records the 10 slowest SQL statements, along with a stack trace of where the SQL was executed from in your program. Fixed a bug in the automatic insertion of RUM headers and footers where they could sometimes be inserted multiple times (especially the footer). The \"Drupal Modules\" feature can now be enabled and disabled on a per-directory basis like most other configuration settings. A few minor bug fixes that had the potential for causing random agent crashes, although these were very infrequent.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-25529","eolDate":"2014-11-10"},{"agent":"php","date":"2011-11-01","downloadLink":null,"version":"2.4.5.26","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: Very minor change to change the KB URL paths in error messages and to correct the LICENSE.txt file to include the full copyright and permissions notices for various open source components used withing the agent.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-24526","eolDate":"2014-11-01"},{"agent":"php","date":"2011-10-07","downloadLink":null,"version":"2.4.5.25","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: Very minor change to the daemon to remove a pause on startup if the daemon happened to start within 30 seconds of the top of the minute.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-24525","eolDate":"2014-10-07"},{"agent":"php","date":"2011-10-04","downloadLink":null,"version":"2.4.5.24","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 several coredump issues related to Drupal Modules. Updated SQL parser to ignore C-style comments in SQL. Added OpenSolaris x64 support. Now possible to instrument internal PHP functions but only after consultation with technical support, as it adds additional overhead.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-24524","eolDate":"2014-10-04"},{"agent":"php","date":"2011-09-22","downloadLink":null,"version":"2.3.5.21","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: Version number change. Starting with this release version numbers only use 2 segments, as in 2.3. The remaining bits simply reflect the build level. Naming web transactions for several new frameworks has been added: Joomla (1.5 and 1.6), Kohana (3.1 and 3.2), Magento 1.6 and MediaWiki 1.16. Drupal auto-RUM has been modified to inject the header earlier so that all CSS and JavaScript loading is taken into account, and it now also works when the advagg module is installed. Drupal modules support. This needs to be enabled by setting newrelic.framework.drupal.modules=1. This will display how much time is being spent in each Drupal module, including sub-modules. When enabled this feature is accessed from the \"Modules\" tab of the App Server menu. Support for MongoDB has been added. New API call newrelic_ignore_apdex() has been added. This allows users to ignore certain time-consuming activities (such as downloading a file) from their overall apdex score. PHP namespace separator () no longer causes a malformed JSON error when it appears in a transaction trace. SQL parser improved to better detect table names and avoid database metric explosion on certain SQL statements. Calls to Drupal's drupal_http_request()are now correctly identified as external service calls. Several speed improvements to further reduce the impact when Drupal Modules support or top100 is enabled. MacOSX agent no longer aborts when PCRE isn't loaded. RUM scripts improved to load the footer script after the page has fully loaded so that it does not impact user-visible performance. API functions newrelic_get_browser_timing_header() and newrelic_get_browser_timing_footer() now take an optional bool argument (that defaults to true) that indicates whether or not script start and end tags should be inserted around the returned JavaScript. Small memory leak when adding metric names fixed. Daemon startup scripts now correctly ignores comment lines","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-23521","eolDate":"2014-09-22"},{"agent":"php","date":"2011-08-18","downloadLink":null,"version":"2.2.3.196","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 up not detecting background jobs when run from cpanel Corrected url path problems resulting in 500 errors for web transactions when on CakePHP","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-223196","eolDate":"2014-08-18"},{"agent":"php","date":"2011-08-16","downloadLink":null,"version":"2.2.2.193","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 a SIGSEGV that happened when Zend Guard encoded files were encountered Corrected the way we were determining the domain names of external services that was causing a Transaction Traces display problem (500 error)","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-222193","eolDate":"2014-08-16"},{"agent":"php","date":"2011-08-06","downloadLink":null,"version":"2.2.1.185","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: Fixes up a problem in our SQL parser that was causing Magento app segfaults when accessing admin pages","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-221185","eolDate":"2014-08-06"},{"agent":"php","date":"2011-08-03","downloadLink":null,"version":"2.2.1.181","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: QDrupal support. SQL parsing fixes. Framework auto-detection when multiple frameworks in use is working now.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-221181","eolDate":"2014-08-03"},{"agent":"php","date":"2011-07-26","downloadLink":null,"version":"2.1.3.164","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: We now support reporting to multiple applications simultaneously. We had a bug where a large data string could cause a segmentation fault. A few bug fixes around Wordpress RUM, CakePHP transaction names, and auto-detecting the Zend Framework.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-213164","eolDate":"2014-07-26"},{"agent":"php","date":"2011-07-13","downloadLink":null,"version":"2.1.1.134","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: RUM and Web Transaction data is available a lot earlier. You no longer need to drive specific amounts of load to get RUM data to appear and early WT's are now recorded. Thread safety in the agent has been considerably improved. While we do not officially support the worker MPM, this change will make the agent behave correctly when using a ZTS (Zend Thread Safety) enabled PHP host. We can now change the agent log file and log level on the fly, without forcing you to restart your web server just to debug a problem. This is a considerable improvement in the user experience if things go awry and you need to contact support. A few minor bugs in the installer script were fixed, most notably creating /etc/newrelic if it did not exist. The PHP agent data reporting has been verified to be UTF-8 safe.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-211134","eolDate":"2014-07-13"},{"agent":"php","date":"2011-06-11","downloadLink":null,"version":"2.0.5.98","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: There was a bug in the newrelic-install script that under some circumstances would cause the script to use 100% of the CPU when installed via aptyum. This has been fixed. The particular User-Agent that was used when a slow transaction is recorded will now be displayed in the \"Parameters\" drop-down when viewing a transaction trace.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-20598","eolDate":"2014-06-11"},{"agent":"php","date":"2011-06-06","downloadLink":null,"version":"2.0.3.89","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: Previously, auto-RUM did not work when certain Drupal modules were used (for example the ajax module). All fixed up now.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-20389","eolDate":"2014-06-06"},{"agent":"php","date":"2011-05-25","downloadLink":null,"version":"2.0.2.65","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: Versions 2.0.0 and 2.0.1 had an error in the spec file that will cause problems for Redhat and CentOS users. After doing an upgrade, the daemon will not be running, and the agent will not be installed. After upgrading to 2.0.2 or later, you must run newrelic-install and ensure that the daemon is running. Upgrades from 2.0.2 and onwards will no longer have this bug. On OpenSolaris, the daemon will now always be installed in /opt/newrelic/bin rather than /usr/bin, as /usr is a read-only filesystem for many users. The init script will look in this new location first, and none of the other files have moved.","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-20265","eolDate":"2014-05-25"},{"agent":"php","date":"2026-07-27","downloadLink":"https://download.newrelic.com/php_agent/archive/12.9.0.38","version":"12.9.0.38","features":["Wordress 7 verified and supported"],"bugs":null,"security":["Upgrade golang to 1.26.5","go.mod dependency updates","bump google.golang.org/grpc from 1.82.0 to 1.82.1"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v12.9.0.38 New Features Wordress 7 verified and supported Security updates Upgraded golang to 1.26.5 (#1258 ) go.mod dependency updates (#1247 ) bump google.golang.org/grpc from 1.82.0 to 1.82.1 (#1259 ) Support Statement PHP Agent support for the following library & framework versions will be discontinued and New Relic recommends you upgrade to the latest version supported by the vendor: Slim 2 support will be discontinued in all PHP Agent Versions after July 31, 2026 Drupal 7: Support ends October 15, 2026 (updated from September 30) Drupal 9: Support ends October 15, 2026 (updated from September 30) Laravel 11 support will be discontinued in all PHP Agent Versions after September 30, 2026 Joomla: All Joomla support ends September 30, 2026 New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-9-0-38","eolDate":"2027-07-27"},{"agent":"php","date":"2026-06-29","downloadLink":"https://download.newrelic.com/php_agent/archive/12.8.0.37","version":"12.8.0.37","features":["Add Redis Cluster instrumentation"],"bugs":["Fix realpath buffer overrun in install-util","Avoid stack overflow","Report correct Instance/Reporting count","Mitigate possible snprintf overflow","Remove double allocation of request_uri string"],"security":["Upgrade golang to 1.26.4","Update outdated dependencies"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v12.8.0.37 New Features Added Redis Cluster instrumentation (#1212  / #1206 ). Resolves #130 . Security updates Upgraded golang to 1.26.4 (#1232 ) Updated outdated dependencies (1241 ) Bug Fixes Fixed realpath buffer overrun in install-util (#1221 ) Fixed a stack overflow (#1222 ) Corrected the Instance/Reporting count (#1231 ) Mitigated a possible snprintf overflow (#1223 ) Removed double allocation of the request_uri string (#1236 ) Support Statement PHP Agent support for the following library & framework versions will be discontinued and New Relic recommends you upgrade to the latest version supported by the vendor: Slim 2 support will be discontinued in all PHP Agent Versions after July 31, 2026 Drupal 7 support will be discontinued in all PHP Agent Versions after September 30, 2026 Drupal 9 support will be discontinued in all PHP Agent Versions after September 30, 2026 Laravel 11 support will be discontinued in all PHP Agent Versions after September 30, 2026 Joomla 3 support will be discontinued in all PHP Agent Versions after September 30, 2026 New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-8-0-37","eolDate":"2027-06-29"},{"agent":"php","date":"2026-05-12","downloadLink":"https://download.newrelic.com/php_agent/archive/12.7.0.36","version":"12.7.0.36","features":[],"bugs":["Changed log level of transaction truncation fiber messages","Ensure unnamed spans are not recorded for infinite tracing","Correct daemon seen/sent metric generation","Allow mysqli parameter binding in execute"],"security":["Bump go version to 1.26.3"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v12.7.0.36 Security updates Bump go version to 1.26.3 (#1220 ). Addresses #1201 . Bug Fixes Changed log level of transaction truncation fiber messages (#1207 ). Addresses #1200 . Ensure unnamed spans are not recorded for infinite tracing (#1197 ). Correct daemon seen/sent metric generation (#1174 ). Allow mysqli parameter binding in execute (#1172 ). Support Statement As previously communicated , for best practices and security, the rpm signing key has been rotated and the rpm installation  page reflects the up to date changes. PHP Agent support for the following library & framework versions will be discontinued and New Relic recommends you upgrade to the latest version supported by the vendor: Drupal 7 support will be discontinued in all PHP Agent Versions after September 30, 2026 Drupal 9 support will be discontinued in all PHP Agent Versions after September 30, 2026 Laravel 11 support will be discontinued in all PHP Agent Versions after September 30, 2026 Joomla 3 support will be discontinued in all PHP Agent Versions after September 30, 2026 New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-7-0-36","eolDate":"2027-05-12"},{"agent":"php","date":"2026-03-31","downloadLink":"https://download.newrelic.com/php_agent/archive/12.6.0.34","version":"12.6.0.34","features":["Laravel 13 verified and supported","Disable instrumentation on unsupported Fiber detection."],"bugs":["Fixed installing ini into mods available on debian and ubuntu","Fixed backoff tier when retrying daemon connections","Fixed SQL parsing logic"],"security":["upgrade golang to 1.26.1","update golang grpc dependencies","rotate RPM signing key"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v12.6.0.34 New Features Laravel 13 verified and supported. Instrumentation will be disabled per request when PHP Fiber  usage is detected. (#1178 ) Security updates Bump go version to 1.26.1 (#1179 ). Addresses #1173 . Update golang grpc dependencies (#1185 ). Bug Fixes Fixed backoff tier when retrying daemon connections (#1169 ) Fixed installing newrelic.ini into mods-available on Debian/Ubuntu (#1170 ). Addresses (https://github.com/newrelic/newrelic-php-agent/issues/1168). Improved SQL parsing logic (#1164 ) Support Statement As previously communicated , for best practices and security, the rpm signing key has been rotated and the rpm installation  page reflects the up to date changes. PHP Agent support for the following library & framework versions will be discontinued and New Relic recommends you upgrade to the latest version supported by the vendor: Drupal 7 support will be discontinued in all PHP Agent Versions after September 30, 2026 Drupal 9 support will be discontinued in all PHP Agent Versions after September 30, 2026 As previously communicated, the PHP Agent support for the following library & framework versions is discontinued in all PHP Agent releases after February 28th, 2026: For the following library & framework versions, New Relic recommends you upgrade to the latest version supported by the vendor: Symfony 4.x Laravel 7.x, 9.x, 10.x Slim 3.x Support for the following libraries & frameworks will be discontinued for all versions: MediaWiki Zend Framework Lumen New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-6-0-34","eolDate":"2027-03-31"},{"agent":"php","date":"2026-02-10","downloadLink":"https://download.newrelic.com/php_agent/archive/12.5.0.30","version":"12.5.0.30","features":["Symfony 8 verified and supported","Add support for MongoDB 2.x"],"bugs":["Fix table naming for queries with `EXTRACT` function","Fix drupal hook instrumentation"],"security":["upgrade golang to 1.25.7"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v12.5.0.30 New Features Symfony 8 verified and supported. #1147  - agent: update instrumentation to be compatible with MongoDB 2.x #1154 , #1158 Security updates #1160  - daemon: bump go toolchain to 1.25.7 #1163 Bug Fixes agent: fix table naming for queries with EXTRACT function #1159 agent: fix drupal hook instrumentation #1157 Support Statement In an upcoming release, for best practices and security, the rpm signing key will be rotated. Closer to that release, specific dates and necessary actions for rpm users will be provided. PHP Agent support for the following library & framework versions will be discontinued in all PHP Agent releases after February 28th, 2026: For the following library & framework versions, New Relic recommends you upgrade to the latest supported version: Symfony 4.x Laravel 7.x, 9.x, 10.x Slim 3.x Support for the following libraries & frameworks will be discontinued for all versions: MediaWiki Zend Framework Lumen New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-5-0-30","eolDate":"2027-02-10"},{"agent":"php","date":"2026-01-12","downloadLink":"https://download.newrelic.com/php_agent/archive/12.4.0.29","version":"12.4.0.29","features":["add support for PHP 8.5"],"bugs":["addressed deprecation warnings in Symfony 7.4 / 8.0"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v12.4.0.29 New Features Added PHP 8.5 support Bug Fixes Addressed deprecation warnings which could be seen when using Symfony 7.4 and 8.0 Support Statement In an upcoming release, for best practices and security, the rpm signing key will be rotated. Closer to that release, specific dates and necessary actions for rpm users will be provided. PHP Agent support for the following library & framework versions will be discontinued in all PHP Agent releases after February 28th, 2026: For the following library & framework versions, New Relic recommends you upgrade to the latest supported version: Symfony 4.x Laravel 7.x, 9.x, 10.x Slim 3.x Support for the following libraries & frameworks will be discontinued for all versions: MediaWiki Zend Framework Lumen New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-4-0-29","eolDate":"2027-01-12"},{"agent":"php","date":"2025-12-15","downloadLink":"https://download.newrelic.com/php_agent/archive/12.3.0.28","version":"12.3.0.28","features":["add aws-sdk-php Kinesis Data Streams Instrumentation"],"bugs":["fixed issue where daemon did not clear package cache on restart"],"security":["bump golang version to 1.25.5"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v12.3.0.28 New Features Added aws-sdk-php Kinesis Data Streams Instrumentation Security Bump golang version to 1.25.5 Bug Fixes Fixed issue where daemon did not clear package cache on restart Support Statement In an upcoming release, for best practices and security, the rpm signing key will be rotated. Closer to that release, specific dates and necessary actions for rpm users will be provided. PHP Agent support for the following library & framework versions will be discontinued in all PHP Agent releases after February 28th, 2026: For the following library & framework versions, New Relic recommends you upgrade to the latest supported version: Symfony 4.x Laravel 7.x, 9.x, 10.x Slim 3.x Support for the following libraries & frameworks will be discontinued for all versions: MediaWiki Zend Framework Lumen New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-3-0-28","eolDate":"2026-12-15"},{"agent":"php","date":"2025-11-19","downloadLink":"https://download.newrelic.com/php_agent/archive/12.2.0.27","version":"12.2.0.27","features":["add laravel 12 support","add laravel horizon support"],"bugs":["fix laravel queue job exception handling"],"security":["bump golang version to 1.25.3"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v12.2.0.27 New Features Laravel 12 verified and supported. Laravel Horizon is now supported on Laravel 10.x+ and PHP 8.1+. Security #1129  - Bump golang version 1.25.3 - #1130 Bug Fixes fix(agent): Fix Laravel queue job exception handling - #1122 Support Statement In an upcoming release, for best practices and security, the rpm signing key will be rotated. Closer to that release, specific dates and necessary actions for rpm users will be provided. As previously announced, PHP Agent support for the following library/framework versions has officially ended as of September 30th, 2025: WordPress 5.9 Drupal 8.x Laravel 6.x, 8.x PHPUnit (all versions) PHP Agent support for the following library & framework versions will be discontinued in all PHP Agent releases after February 28th, 2026: For the following library & framework versions, New Relic recommends you upgrade to the latest supported version: Symfony 4.x Laravel 7.x, 9.x, 10.x Slim 3.x Support for the following libraries & frameworks will be discontinued for all versions: MediaWiki Zend Framework Lumen New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-2-0-27","eolDate":"2026-11-19"},{"agent":"php","date":"2026-08-31","downloadLink":"https://download.newrelic.com/php_agent/archive/12.10.0.39","version":"12.10.0.39","features":["PHP Fibers support","Guzzle 8 support","Magento 2.4.8 support","Magento 2.4.9 support"],"bugs":null,"security":["Upgrade golang to 1.26.6","go.mod dependency updates"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v12.10.0.39 New Features Fibers now fully instrumented (#1198 ) Guzzle 8 supported (#1279 ) Magento 2.4.8/2.4.9 verified and supported. Security updates Upgraded golang to 1.26.6 (#1272 ) go.mod dependency updates (#1268 ) (#1274 ) (#1275 ) Support Statement PHP Agent support for the following library & framework versions will be discontinued and New Relic recommends you upgrade to the latest version supported by the vendor: Slim 2 support has been discontinued Drupal 7: Support ends October 15, 2026 (updated from September 30) Drupal 9: Support ends October 15, 2026 (updated from September 30) Laravel 11 support will be discontinued in all PHP Agent Versions after September 30, 2026 Joomla: All Joomla support ends September 30, 2026 Guzzle 5 and 6: Support ends October 15, 2026 New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-10-0-39","eolDate":"2027-08-31"},{"agent":"php","date":"2025-09-09","downloadLink":"https://download.newrelic.com/php_agent/archive/12.1.0.26","version":"12.1.0.26","features":["upsteam w3c sampling control","option to skip framework exception handler instrumentation"],"bugs":["fix potential memleak","no instrumentation when not recording"],"security":["bump golang version to 1.25.1"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v12.1.0.26 New features Add sampling controls based on upstream w3c trace sampling decision - #1104 See new ini values here Add configuration option to skip instrumentation of framework exception handlers - #1113 See new ini value here Security Bump golang version to 1.25.1 Bug fixes Fix potential memleak when calling newrelic_end_transaction(true) - #1072 Don't attempt any instrumentation when not recording - #1112 Support statement PHP Agent support for the following library/framework versions will end September 30, 2025: WordPress 5.9 Drupal 8.x Laravel 6.x, 8.x PHPUnit 8.x New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-1-0-26","eolDate":"2026-09-09"},{"agent":"php","date":"2025-08-11","downloadLink":"https://download.newrelic.com/php_agent/archive/12.0.0.25","version":"12.0.0.25","features":["Observability in IDE: Code-Level metrics is disabled by default.","Removed code for instrumenting Guzzle 3.x","Removed code for instrumenting Kohana","Removed code for instrumenting Silex","Removed code for instrumenting Symfony 1.x-3.x","Removed code for instrumenting Zend 1.x-2.x"],"bugs":["Improve drupal hook map error logging.","Fix legacy package detection issues"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v12.0.0.25 Bug fixes Improve drupal hook map error logging. Fix legacy package detection issues for Security RX . Notice Default value for newrelic.code_level_metrics.enabled INI has changed in this release As previously communicated, the default Code Level Metrics Observability in IDE  configuration will change in an this release from enabled to disabled.  If you do not use Code Level Metrics, you should see no impact and will not have to take any action.  If you do rely on Code Level Metrics , ensure that your newrelic.ini configuration file has the  newrelic.code_level_metrics.enabled INI setting uncommented and set to true.\ne.g: This change only impacts the default configuration value. Manually set configuration values will be honored, and core CLM behavior will remain unaffected. Support statement As previously communicated, the following frameworks/libraries that the PHP Agent has previously EOL'd support for will be removed in the this release: Guzzle 3.x Kohana Silex Symfony 1.x-3.x Zend 1.x-2.x PHP Agent support for the following library/framework versions will end September 30, 2025: WordPress 5.9 Drupal 8.x Laravel 6.x, 8.x PHPUnit 8.x New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-12-0-0-25","eolDate":"2026-08-11"},{"agent":"php","date":"2024-09-30","downloadLink":"https://download.newrelic.com/php_agent/archive/11.2.0.15","version":"11.2.0.15","features":["Use composer API for vulnerability package management detection","Add Symfony 6 & 7 support"],"bugs":["Fixes newrelic_notice_error API for PHP 8+"],"security":["Upgrade Golang version to 1.23.1"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v11.2.0.15 New features If possible, use composer runtime API to collect information about PHP packages used by the application for New Relic Vulnerability Management . This feature is controlled via the new newrelic.vulnerability_management.composer_api.enabled INI value (off by default). Symfony 6 & 7 support verified. Security Daemon Golang version upgraded to 1.23.1. Bug fixes Fixes newrelic_notice_error() API for PHP 8+ when using the 4 parameter API variant. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-11.2.0.15","eolDate":"2025-09-30"},{"agent":"php","date":"2025-05-13","downloadLink":"https://download.newrelic.com/php_agent/archive/11.9.0.23","version":"11.9.0.23","features":["Drupal hook attribute instrumentation (Drupal 11.1)","instrumentation optimization"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v11.9.0.23 New features feat(agent): Add auto-instrumentation of object oriented hook implementations introduced in Drupal 11.1 Other refactor(agent): Improve performance of user functions instrumentation for PHPs 8.0+ Notice The default Code Level Metrics configuration will change in an upcoming release from enabled to disabled.\nIf you do not use Code Level Metrics, you should see no impact and will not have to take any action.\nIf you do rely on Code Level Metrics, ensure that your newrelic.ini configuration file has the\nnewrelic.code_level_metrics.enabled INI setting uncommented and set to true.\ne.g:\nnewrelic.code_level_metrics.enabled = true\nThis change only impacts the default configuration value. Manually set configuration values will be honored, and core CLM behavior will remain unaffected. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-9-0-23","eolDate":"2026-05-13"},{"agent":"php","date":"2025-04-21","downloadLink":"https://download.newrelic.com/php_agent/archive/11.8.0.22","version":"11.8.0.22","features":["Add AWS DynamoDB Instrumentation"],"bugs":[],"security":["Upgrade golang to 1.24.2","Upgrade Golang x/net version to 0.38.0"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v11.8.0.22 New features feat(agent): Add AWS DynamoDB Instrumentation Security security(daemon): bump golang to 1.24.2 security(daemon): bump golang.org/x/net from 0.36.0 to 0.38.0 Notice The default Code Level Metrics configuration will change in an upcoming release from enabled to disabled.\nIf you do not use Code Level Metrics, you should see no impact and will not have to take any action.\nIf you do rely on Code Level Metrics, ensure that your newrelic.ini configuration file has the\nnewrelic.code_level_metrics.enabled INI setting uncommented and set to true.\ne.g:\nnewrelic.code_level_metrics.enabled = true\nThis change only impacts the default configuration value. Manually set configuration values will be honored, and core CLM behavior will remain unaffected. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-8-0-22","eolDate":"2026-04-21"},{"agent":"php","date":"2025-03-19","downloadLink":"https://download.newrelic.com/php_agent/archive/11.7.0.21","version":"11.7.0.21","features":["Add label forwarding to log events","Add AWS Lambda Relationship"],"bugs":[],"security":["Upgrade Golang x/net version to 0.36.0"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v11.7.0.21 New features feat(agent): Adds label forwarding to log events feat(agent): Add AWS Lambda Relationship Security security(daemon): bump golang.org/x/net from 0.33.0 to 0.36.0 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-7-0-21","eolDate":"2026-03-19"},{"agent":"php","date":"2025-02-18","downloadLink":"https://download.newrelic.com/php_agent/archive/11.6.0.19","version":"11.6.0.19","features":["Add aws-sdk-php 3 SQS support","Add php-amqplib 3.7 RabbitMQ support","Add Yii 1.1 RabbitMQ support","Add message segment MessageBroker functionality"],"bugs":["Fixes memory leak in Laravel Queue Instrumentation","Fixes nr_header_create_distributed_trace_map memory leak","Fixes daemon to enable go_vet check"],"security":["Upgrade Golang version to 1.23.6"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v11.6.0.19 New features Added support for aws-sdk-php SQS version 3 instrumentation Added support for php-amqplib version 3.7 RabbitMQ instrumentation Added support for Yii version 1.1 instrumentation The agent will now generate MessageBroker metrics and attributes Security Daemon Golang version upgraded to 1.23.6 Bug fixes Fixed daemon to enable go vet check on pull requests Fixed memory leak in Laravel Queue Instrumentation Fixed nr_header_create_distributed_trace_map memory leak Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-6-0-19","eolDate":"2026-02-18"},{"agent":"php","date":"2025-01-13","downloadLink":"https://download.newrelic.com/php_agent/archive/11.5.0.18","version":"11.5.0.18","features":["Adds support for PHP 8.4"],"bugs":["Fix Drupal error and exception handling","externalCallCount should be added to transaction","Address aws-sdk-php versioning change"],"security":["Daemon golang.org/x/net module upgraded to v0.33.0"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v11.5.0.18 New feature Adds support for PHP 8.4 Bug Fixes Fix Drupal error and exception handling This fix may conflict with the error and exception handling of the Drupal new_relic_rpm  module. If you have this module installed and you aren't seeing your errors reported natively by the agent, try disabling the new_relic_rpm module. If you still experience issues after disabling this module, please reach out to New Relic Support. Fix error where externalCallCount should be added to the transaction and not just the error event. Address aws-sdk-php versioning change. Security Daemon golang.org/x/net module upgraded to v0.33.0 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every three months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-5-0-18","eolDate":"2026-01-13"},{"agent":"php","date":"2024-12-09","downloadLink":"https://download.newrelic.com/php_agent/archive/11.4.0.17","version":"11.4.0.17","features":["Support for CakePHP 4.x and 5.x"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v11.4.0.17 New feature Added support for CakePHP framework versions 4.x and 5.x. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every three months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-4-0-17","eolDate":"2025-12-09"},{"agent":"php","date":"2024-10-21","downloadLink":"https://download.newrelic.com/php_agent/archive/11.3.0.16","version":"11.3.0.16","features":["Memcached instance metrics with hostname","Dockerized Daemon supports arm64"],"bugs":["Fixes possible duplicate INI files on Debian","Fixes argument skipping during mysqli::real_connect"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v11.3.0.16 New Features Memcached instance metrics with host name Dockerized Daemon  now supports arm64 Bug Fixes Improve magic file recognition performance Tarball installer checks for existing ini in mods-available directory Don't skip arguments when calling mysqli::real_connect Huge thanks to @kovshenin for their community contribution!! Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-3-0-16","eolDate":"2025-10-21"},{"agent":"php","date":"2025-06-25","downloadLink":"https://download.newrelic.com/php_agent/archive/11.10.0.24","version":"11.10.0.24","features":["Security RX: Composer runtime API will be used by default to detect packages used by PHP applications"],"bugs":["Fix undefined behavior when Composer runtime API is used"],"security":["upgrade golang to 1.24.4","rotate New Relic's public key used to verify signature of APT repository"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v11.10.0.24 New features Security RX : Composer runtime API will be used by default to detect packages used by PHP applications #1055 Security updates #1089  - security(daemon): upgrade golang to 1.24.4 #1090 #973  - security: rotate New Relic's public key used to verify signature of http://apt.newrelic.com/debian/ APT repository. See here  for details. Bug fixes fix(agent): Fix undefined behavior when Composer runtime API is used #1086 Notice Default value for newrelic.code_level_metrics.enabled INI changes in next release The default Code Level Metrics configuration will change in an upcoming release from enabled to disabled.  If you do not use Code Level Metrics, you should see no impact and will not have to take any action.  If you do rely on Code Level Metrics, ensure that your newrelic.ini configuration file has the  newrelic.code_level_metrics.enabled INI setting uncommented and set to true.\ne.g: This change only impacts the default configuration value. Manually set configuration values will be honored, and core CLM behavior will remain unaffected. Support statement The following frameworks/libraries that the PHP Agent has previously EOL'd support for will be removed in the next release: Guzzle 3.x Kohana Silex Symfony 1.x-3.x Zend 1.x-2.x PHP Agent support for the following library/framework versions will end September 30, 2025: WordPress 5.9 Drupal 8.x Laravel 6.x, 8.x PHPUnit 8.x New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-10-0-24","eolDate":"2026-06-25"},{"agent":"php","date":"2024-08-26","downloadLink":"https://download.newrelic.com/php_agent/archive/11.1.0.14","version":"11.1.0.14","features":["Drupal 11 verified and supported"],"bugs":["Fixes unresolved strlcpy symbol error on Linux platforms using glibc >= 2.39"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v11.1.0.14 New features Drupal 11 verified and supported. Bug fixes Fixes an issue where newrelic.so was not able to resolve the strlcpy symbol on Linux using glibc version 2.39 or higher. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-1-0-14","eolDate":"2025-08-26"},{"agent":"php","date":"2024-07-30","downloadLink":"https://download.newrelic.com/php_agent/archive/11.0.0.13","version":"11.0.0.13","features":["PHP 7.0 and 7.1 are EOL","Add countDocuments for MongoDB for PHP 7.x","Doctrine 3.x verified and supported","Fix Doctrine 2.18+ detection","Laravel 11 verified and supported"],"bugs":[],"security":["Upgrade golang to 1.22.5","Updated install guidance to not use deprecated apt-key"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v11.0.0.13 New features Add countDocuments mongodb instrumentation for PHP 7.x (#926 ) Doctrine 3.x verified and supported. Laravel 11 verified and supported. Note: excludes Laravel Horizon support. Security updates security(daemon): Upgrade golang to 1.22.5 (#940 ) Instructions for configuring New Relic apt repository have been updated to no longer use deprecated apt-key utility. Please use the updated instructions Important end-of-life information Support for PHP versions 7.0 and 7.1 has been EOLed and is removed in this release. If you are still using these PHP versions, please make sure to pin your agent version to 10.22.0.12. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-11-0-0-13","eolDate":"2025-07-30"},{"agent":"php","date":"2022-09-19","downloadLink":"https://download.newrelic.com/php_agent/archive/10.1.0.313","version":"10.1.0.313","features":["Add APM logs in context for Monolog 2 and 3","Enhanced redis and PhpRedis support"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New features APM logs in context support for Monolog 2 and 3 The PHP agent will now generate logging metrics for Monolog (versions 2 and 3) to allow seeing the rate of log messages by severity. These metrics are enabled by default and are controlled by a config file directive. The PHP agent can also now forward log messages from Monolog for viewing on the New Relic platform. Log forwarding is currently disabled by default (can be enabled by a config file directive), and will be enabled by default in a future release. To learn more about APM logs in context, see the logs in context docs . For more information about logs in context and the PHP agent check the PHP logs in context docs . Enhanced redis/PhpRedis support\nThank you to Michael Grunder  for contributing to the PHP agent and extending the existing redis/PhpRedis support! New contributors As mentioned above, community member Michael Grunder  made his first contribution to the New Relic PHP agent. Thanks!!! Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines please consult the following document .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-1010313","eolDate":"2023-09-19"},{"agent":"php","date":"2022-06-29","downloadLink":"https://download.newrelic.com/php_agent/archive/10.0.0.312","version":"10.0.0.312","features":["Add support for Agent tags"],"bugs":["Disable Infinite tracing on startup if distributed tracing is disabled","Remove a debug statement causing excessive log file messages","Significant reduction of duplicate log messages"],"security":[],"supportedOperatingSystems":null,"description":"New features The agent now incorporates updated backend communications which will pave the way to efficiently add new features. Agent tags  are now supported by the PHP agent. Bug fixes Infinite tracing is now disabled at startup if distributed tracing is disabled since it is required (Issue 452 ). Removed a debugging statement that was no longer needed and could lead to large log file usage if verbose debugging was enabled (Issue 447 ). Additional fixes to significantly reduce the number of duplicated log messages in some situations where large log consumption had been observed in the past. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines please consult the following document .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-1000312","eolDate":"2024-06-29"},{"agent":"php","date":"2023-04-05","downloadLink":"https://download.newrelic.com/php_agent/archive/10.9.0.324","version":"10.9.0.324","features":[],"bugs":[],"security":["Update Daemon Golang version from 1.9 to 1.20"],"supportedOperatingSystems":null,"description":"New Relic PHP Agent v10.9.0.324 Security Updated the Golang version used to build the Daemon from 1.9 to 1.20 New features Bug Fixes Important end-of-life information Support for PHP versions 5.5 and 5.6 will end June 2023. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform (32 bit, FreeBSD, ZTS, etc), it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages which are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-9-0-324","eolDate":"2024-04-05"},{"agent":"php","date":"2023-03-22","downloadLink":"https://download.newrelic.com/php_agent/archive/10.8.0.323","version":"10.8.0.323","features":["Add healthcheck daemon log level"],"bugs":["Fix Debian package installation addition step","Fix warning when passing null to curl_multi_exec"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP Agent v10.8.0.323 New features Added healthcheck log level for the daemon, allowing for precise monitoring of the number of connected applications. Bug Fixes Fixed debian package installation occasionally requiring an additional manual step #634 Fixed a warning from agent when passing null as the second parameter to curl_multi_exec #605 . Special thanks to dejanceltra  for finding and fixing this issue! New Contributors This release contains the first contribution to the New Relic PHP Agent from community member dejanceltra ! Thanks!! Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform (32 bit, FreeBSD, ZTS, etc), it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages which are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-8-0-323","eolDate":"2024-03-22"},{"agent":"php","date":"2023-03-08","downloadLink":"https://download.newrelic.com/php_agent/archive/10.7.0.319","version":"10.7.0.319","features":["Add support for PHP 8.2"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP Agent v10.7.0.319 Important note If the following error occurs when installing the newrelic-php5 Debian package: Please run the newrelic-install installation program which will complete the installation of the PHP agent and set up the correct symlink to the PHP extension directory. New features Added Support for PHP 8.2. Important end-of-life information Support for PHP versions 5.5 and 5.6 will end June 2023. Support statement Support for 32 bit and FreeBSD ended with release v9.19.0.309 and those binaries are no longer provided . Support for ZTS builds ended with release v9.19.0.309. New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform (32 bit, FreeBSD, ZTS, etc), it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages which are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-7-0-319","eolDate":"2024-03-08"},{"agent":"php","date":"2023-02-13","downloadLink":"https://download.newrelic.com/php_agent/archive/10.6.0.318","version":"10.6.0.318","features":["Code Level Metrics on by default"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP Agent v10.6.0.318 New features Code Level Metrics (CLM) is now enabled by default. CLM allows you to gather more data associated with each span, including line numbers, function names, filepaths, and namespaces. CLM was introduced in release 10.4.0.316 . Use this ini value  to configure CLM. Important end-of-life information Support for PHP versions 5.5 and 5.6 will end June 2023. Support statement Support for 32 bit and FreeBSD ended with release v9.19.0.309 and those binaries are no longer provided . Support for ZTS builds ended with release v9.19.0.309. New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform (32 bit, FreeBSD, ZTS, etc), it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages which are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-6-0-318","eolDate":"2024-02-13"},{"agent":"php","date":"2023-01-18","downloadLink":"https://download.newrelic.com/php_agent/archive/10.5.0.317","version":"10.5.0.317","features":[],"bugs":["Fix 10.3 performance regression","Fix opcache warning message","Send application logging configuration metrics"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP Agent v10.5.0.317 Bug Fixes agent: Fixed #577  - Large performance regression in 10.3.0. #588 agent: Fixed #594  - Instrumentation from opcache.preload for PHP 8.1. #595 agent: Fixed sending Supportability/Logging/Forwarding/PHP/% and Supportability/Logging/Metrics/PHP/% application logging configuration metrics. #575 Support statement Support for 32 bit and FreeBSD ended with release v9.19.0.309 and those binaries are no longer provided . Support for ZTS builds ended with release v9.19.0.309. New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform (32 bit, FreeBSD, ZTS, etc), it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages which are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-5-0-317","eolDate":"2024-01-18"},{"agent":"php","date":"2022-12-12","downloadLink":"https://download.newrelic.com/php_agent/archive/10.4.0.316","version":"10.4.0.316","features":["Add Code Level Metrics","Add configuration for Custom Event Limit"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP Agent v10.4.0.316 We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date . Important end-of-life information Support for ZTS binaries was deprecated with release v9.17.0.300 and will be removed in a January 2023 release . For installations using an unsupported PHP version or platform (32 bit, FreeBSD, ZTS, etc), it is highly recommended to disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades.  Alternatively, the PHP agent packages can be version pinned to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed, removing support for the required, unsupported features. This would disrupt APM data collection.The PHP agent packages which are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon You should check the PHP agent compatibility and requirements  page for the latest information on supported PHP versions and platforms. New features Code Level Metrics (CLM) has been introduced and is set to off by default. CLM allows you to gather more data associated with each span, including line numbers, function names, filepaths, and namespaces. Use this ini value  to start using CLM! Improvements Custom Event Limit default reservoir size has been increased and is now configurable. The default maximum number of custom events gathered per minute has been increased from 10,000 to 30,000. This value can now be modified with this ini value .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-4-0-316","eolDate":"2023-12-12"},{"agent":"php","date":"2022-11-03","downloadLink":"https://download.newrelic.com/php_agent/archive/10.3.0.315","version":"10.3.0.315","features":["Logs in Context enabled by default"],"bugs":["Ensure datastore segments do not create children segments","Fix \"All transactions unknown\" error"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP Agent v10.3.0.315 We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date . Important end-of-life information Support for 32 bit and FreeBSD binaries were deprecated with release v9.19.0.309 and are no longer shipped starting with this release . Support for ZTS binaries was deprecated with release v9.17.0.300 and will be removed in a release in the near future . For installations using an unsupported PHP version or platform (32 bit, FreeBSD, ZTS, etc), it is highly recommended to disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades.  Alternatively, the PHP agent packages can be version pinned to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed, removing support for the required, unsupported features. This would disrupt APM data collection.The PHP agent packages which are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. New features APM logs in context. Automatic application log forwarding is now enabled by default. This version of the agent will automatically send enriched application logs to New Relic. To learn more about this feature see PHP: Configure logs in context , and additional configuration options are available PHP agent configuration: Config file . To learn about how to toggle log ingestion on or off by account see Disable automatic logging . #556 Bug fixes agent: Fix to ensure datastore segments do not create children segments. #511 agent: Updates instrumentation lookups for PHP 7.4+. Using reserved field of zend_func's op_array is no longer reliable as other extensions are unreliably using this shared area which then corrupts the opcache enough that it no longer provides lookups. The new method no longer relies on the agent storing any information in the reserved array of a  zend_function.   Fixes: Laravel 9 PHP8.1 Not reporting errors, All transactions are \"unknown\" bug","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-3-0-315","eolDate":"2023-11-03"},{"agent":"php","date":"2024-06-26","downloadLink":"https://download.newrelic.com/php_agent/archive/10.22.0.12","version":"10.22.0.12","features":[],"bugs":["Fix MongoDB instrumentation for PHP 8.0+","Fix Guzzle 7+ error","Install correctly on minimalist OSs","Fix Doctrine 2.18+ detection","Slim transaction naming updates","Fix rhel and alpine init scripts"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v10.22.0.12 Bug fixes Fix MongoDB instrumentation for PHP 8.0+ Fix error where Guzzle 7+ was sending up major version for VM Install correctly on minimalist operating systems Fix Doctrine 2.18+ detection Slim transaction naming updates Fix rhel and alpine init scripts Important end-of-life information Support for PHP versions 7.0 and 7.1 has been EOL'd and will be removed in the next release. If you are still using these versions, please make sure to pin your agent version. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-22-0-12","eolDate":"2025-06-26"},{"agent":"php","date":"2024-05-20","downloadLink":"https://download.newrelic.com/php_agent/archive/10.21.0.11","version":"10.21.0.11","features":[],"bugs":["end guzzle external segments for rejected request"],"security":["Upgrade golang to 1.22"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v10.21.0.11 Bug fixes fix(agent): End guzzle's external segment for rejected request (https://github.com/newrelic/newrelic-php-agent/pull/883 ) Security updates security(daemon): Upgrade golang to 1.22 (https://github.com/newrelic/newrelic-php-agent/pull/890 ) Important end-of-life information Support for PHP versions 7.0 and 7.1 will EOL  on June 1st, 2024 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-21-0-11","eolDate":"2025-05-20"},{"agent":"php","date":"2024-05-06","downloadLink":"https://download.newrelic.com/php_agent/archive/10.20.0.10","version":"10.20.0.10","features":["Add support for Yii v2","Verified support for Drupal 10","Add supportability metrics for PHP package","Update default for `newrelic.framework.wordpress.hooks.options`"],"bugs":["Fix error reporting for errors converted by PHP to exceptions","Improve user exception handler instrumentation for PHPs 8.0+","Fix warning from mysqli","Fix json struct tag for docker id","Improve communications of PHP packages data to the backend"],"security":["Bump google.golang.org/protobuf from 1.32.0 to 1.33.0","Bump golang.org/x/net from 0.20.0 to 0.23.0"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v10.20.0.10 New features Add support for Yii v2 framework Verified support for Drupal 10 framework Add supportability metrics for PHP packages that provide major version Update default for newrelic.framework.wordpress.hooks.options to \"plugin_callbacks\" Bug fixes Fix error reporting for errors converted by PHP to exceptions Improve user exception handler instrumentation for PHPs 8.0+ Fix warning from mysqli when explaining slow SQL queries Fix json struct tag for docker id Improve communications of PHP packages data to the backend Security Bump google.golang.org/protobuf from 1.32.0 to 1.33.0 in newrelic-daemon Bump golang.org/x/net from 0.20.0 to 0.23.0 in newrelic-daemon Important end-of-life information Support for PHP versions 7.0 and 7.1 will EOL  on June 1st, 2024 Support statement New Relic recommends upgrading the agent regularly and at least every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . For the latest information on supported PHP versions and platforms, consult the PHP agent compatibility and requirements  page. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. The PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-20-0-10","eolDate":"2025-05-06"},{"agent":"php","date":"2022-10-03","downloadLink":"https://download.newrelic.com/php_agent/archive/10.2.0.314","version":"10.2.0.314","features":["Alert when number of connected applications falls below 25 or exceeds 200"],"bugs":["Fix SIGSEGV in Drupal 7 instrumentation","Fix PHPinfo output for \"newrelic.application_logging*.enabled\"","Fix JSON string formatting for application log messages","Reduce severity of log message when the agent does not detect environmental variables"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP Agent v10.2.0.314 New Features newrelic-daemon: Informational messages will be logged if the number of connected applications falls below 25 or exceeds 200. #534 Bug Fixes agent: Fixed SIGSEGV in Drupal 7 drupal_http_request instrumentation for PHP 7.4, 8.0 and 8.1. #538 agent: Fixed displaying newrelic.application_logging*.enabled value in PHP info output. #535 agent: When forwarding application logs, send the log message as a well-formed JSON string that is correctly escaped. #540 agent: Reduce the severity of a log message when an agent does not detect environmental variables. #539 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy .","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-2-0-314","eolDate":"2023-10-03"},{"agent":"php","date":"2024-03-18","downloadLink":"https://download.newrelic.com/php_agent/archive/10.19.0.9","version":"10.19.0.9","features":["Link error traces using transaction ID"],"bugs":["Fix Magento 2 detection","Fix errors prioritization","Fix error recording for PHPs 8.0+"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v10.19.0.9 New features Always link error traces using transaction ID Bug fixes Fixes a bug where the agent would not properly automatically detect the Magento 2 framework Fixes error categorization and prioritization by adding support for E_RECOVERABLE_ERROR, E_DEPRECATED, E_USER_DEPRECATED error types. E_RECOVERABLE_ERROR, E_DEPRECATED, E_USER_DEPRECATED are no longer recorded as Error. Fixes error recording for PHPs 8.0+: user_error_handler is honored, and the agent will not record an error if user_error_handler handled the error. Important end-of-life information Support for PHP versions 7.0 and 7.1 will EOL  on June 1st, 2024 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-19-0-9","eolDate":"2025-03-18"},{"agent":"php","date":"2024-03-04","downloadLink":"https://download.newrelic.com/php_agent/archive/10.18.0.8","version":"10.18.0.8","features":["Adds JIT support"],"bugs":["Fix Lumen detection"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v10.18.0.8 New features PHP's Just-In-Time Compilation is no longer disabled when the PHP Agent is enabled. PHP has this on-by-default starting with PHP 8.0. Bug fixes Fixes a bug where the agent would not properly automatically detect the Lumen framework Important end-of-life information Support for PHP versions 7.0 and 7.1 will EOL  on June 1st, 2024 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-18-0-8","eolDate":"2025-03-04"},{"agent":"php","date":"2024-02-21","downloadLink":"https://download.newrelic.com/php_agent/archive/10.17.0.7","version":"10.17.0.7","features":["Adds package detection information"],"bugs":["Fix DT W3C trace state header generation"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v10.17.0.7 New features The PHP agent now sends up package detection information that can be viewed on the environment page. This feature will be enabled by default and you can find more information about this INI configuration here . Bug fixes Fixes a locale bug in DT W3C trace state header generation Important end-of-life information Support for PHP versions 7.0 and 7.1 will EOL  on June 1st, 2024 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-17-0-7","eolDate":"2025-02-21"},{"agent":"php","date":"2024-01-23","downloadLink":"https://download.newrelic.com/php_agent/archive/10.16.0.5","version":"10.16.0.5","features":["Adds Wordpress hooks options"],"bugs":[],"security":["Agent debugging log obfuscation improved for relevant agent configuration values"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v10.16.0.5 Security Agent debugging log obfuscation improved for relevant agent configuration values. New features INI value newrelic.framework.wordpress.hooks.options that allows tailoring WordPress instrumentation. Using plugins_callbacks or threshold values offer different instrumentation levels with reduced agent’s overhead. See https://docs.newrelic.com/docs/apm/agents/php-agent/configuration/php-agent-configuration/#inivar-framework-wordpress-hooks-options  and https://docs.newrelic.com/docs/apm/agents/php-agent/frameworks-libraries/wordpress-specific-functionality/  for more details. Miscellaneous improvements Several performance-related improvements for agent when using the Wordpress framework. Important end-of-life information Support for PHP versions 7.0 and 7.1 will EOL  on June 1st, 2024 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-16-0-5","eolDate":"2025-01-23"},{"agent":"php","date":"2023-12-20","downloadLink":"https://download.newrelic.com/php_agent/archive/10.15.0.4","version":"10.15.0.4","features":["Add support for PHP 8.3"],"bugs":["Remove NULL Docker ID warning message"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v10.15.0.4 New features Adds support for PHP 8.3 Bug fixes Removes a warning message for NULL Docker ID Miscellaneous improvements Several performance-related improvements Important end-of-life information Support for PHP versions 7.0 and 7.1 will EOL  on June 1st, 2024 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-15-0-4","eolDate":"2024-12-20"},{"agent":"php","date":"2023-11-13","downloadLink":"https://download.newrelic.com/php_agent/archive/10.14.0.3","version":"10.14.0.3","features":["Add APM Log Context Attributes","Add Docker v2 container ID support"],"bugs":["Fixes deprecation warnings with mysqli and PHP 8.1+","Fix errors for PHP 8+ in debug mode","Resolved an issue impacting duplicative telemetry data"],"security":["Update Daemon Golang version from 1.20 to 1.21.1"],"supportedOperatingSystems":null,"description":"New Relic PHP agent v10.14.0.3 Security Updated the Golang version used to build the Daemon from 1.20 to 1.21.1. New features The PHP agent now supports APM log context attributes.  See the PHP Logs In Context  page for more information. The agent now supports detecting Docker container IDs via cgroup v2. Bug fixes A fix was added that removes erroneous deprecation warnings which could appear using the mysqli extension with PHP 8.1 and later. When PHP 8+ is built in debug mode, zpp/arginfo mismatches are now Fatal Errors. Fixed the mismatches that existed in the code base. Resolved an issue impacting duplicative telemetry data. Important end-of-life information Support for PHP versions 7.0 and 7.1 will EOL  in early 2024. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection. This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s).\nThe PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-14-0-3","eolDate":"2024-11-13"},{"agent":"php","date":"2023-10-03","downloadLink":"https://download.newrelic.com/php_agent/archive/10.13.0.2","version":"10.13.0.2","features":["Add APM Log Decorating"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v10.13.0.2 New features The PHP agent now supports APM local log decoration. See the PHP Agent Logs In Context  page for more information. Important end-of-life information Support for PHP versions 7.0 and 7.1 will EOL  in early 2024. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-13-0-2","eolDate":"2024-10-03"},{"agent":"php","date":"2023-09-20","downloadLink":"https://download.newrelic.com/php_agent/archive/10.12.0.1","version":"10.12.0.1","features":["Improve Guzzle detection","Add API for custom error grouping","Add API to assign a unique ID to a transaction","Add docs link to install error message","Verified support for Laravel 9 and 10","Verified support for Guzzle 7"],"bugs":["Fix Drupal message log level","Fix 8T Distributed Traces"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP agent v10.12.0.1 New features Improved Guzzle 5 and 6 detection. Adds newrelic_set_error_group_callback API, allowing an application to register a callback function with the PHP Agent that will generate a custom error group name. Read more about this API here . Adds newrelic_set_user_id API, allowing an application to assign a unique user ID to a transaction. Read more about this API here . Adds a link to documentation to the install error message when installing an unsupported version of PHP. Verified support for Guzzle 7. Verified support for Laravel 9 and 10. Bug fixes Reduces the log level for a Drupal-specific message to a more appropriate value. Fixes a bug in Infinite Tracing where distributed traces were missing a parentID attribute that caused issues displaying a distributed application in the UI. Important end-of-life information Support for PHP versions 7.0 and 7.1 will EOL  in early 2024. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages that are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-12-0-1","eolDate":"2024-09-20"},{"agent":"php","date":"2023-06-13","downloadLink":"https://download.newrelic.com/php_agent/archive/10.11.0.3","version":"10.11.0.3","features":["Drupal 9.4 hooks support"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP Agent v10.11.0.3 Security New features Drupal 9.4 now reports hooks and modules Bug Fixes Important end-of-life information Support for PHP versions 5.5 and 5.6 IS DEPRECATED . We recommend upgrading to at least PHP 7.0 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform (32 bit, FreeBSD, ZTS, etc), it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages which are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-11-0-3","eolDate":"2024-06-13"},{"agent":"php","date":"2023-05-30","downloadLink":"https://download.newrelic.com/php_agent/archive/10.10.0.1","version":"10.10.0.1","features":["Add ARM64 binaries for PHP 8.0, 8.1, 8.2"],"bugs":["Better handling for cases where both DT and CAT are enabled"],"security":[],"supportedOperatingSystems":null,"description":"New Relic PHP Agent v10.10.0.1 Security New features ARM64 binaries are now available for PHP 8.0, 8.1, and 8.2.  Please see our docs  for installation instructions. Bug Fixes Additional handling/msg in the case of both DT and CAT being enabled #658 Important end-of-life information Support for PHP versions 5.5 and 5.6 will end  June 2023. Support statement Support for ZTS builds ended with release v9.19.0.309 and those binaries are no longer provided . New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our PHP EOL policy . The PHP agent compatibility and requirements  page should be consulted for the latest information on supported PHP versions and platforms. For installations using an unsupported PHP version or platform (32 bit, FreeBSD, ZTS, etc), it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages.  This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and removal of support for the required, unsupported features. This would disrupt APM data collection.\nThe PHP agent packages which are affected are: newrelic-php5 newrelic-php5-common newrelic-daemon","slug":"docs/release-notes/agent-release-notes/php-release-notes/php-agent-10-10-0-1","eolDate":"2024-05-30"},{"agent":"python","date":"2024-08-08","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.13.0","features":["Add instrumentation for upload_file in boto3","Add support for new Redis commands","Capture AWS SQS information on message spans","Add server.address attribute to RabbitMQ"],"bugs":["Fix OpenAI client instrumentation","Fix missing parameters in MessageTrace"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds the following: Support for boto3's upload_file command Support for newly added Redis commands AWS SQS information on spans server.address attribute on RabbitMQ This release also fixes an issue with OpenAI's client instrumentation and missing parameters in Botocore SQS. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add instrumentation for upload_file in boto3 Add instrumentation to the s3transfer  BoundExecutor submit function, allowing the agent to support the upload_file operation in boto3 . Add support for new Redis commands Add instrumentation for the following commands in Redis : hexpire hexpireat hexpiretime hpersist hpexpire hpexpireat hpexpiretime hpttl httl Capture AWS SQS information on message spans: The Python Agent now captures the following AWS SQS information on message spans, allowing the UI to link AWS information with AWS SQS: messaging.system - aws_sqs cloud.region - AWS region cloud.account.id - AWS account ID messaging.destination.name - AWS queue name Add server.address attribute to RabbitMQ: Add server.address attribute to RabbitMQ , allowing the UI to link AWS information with AWS MQ. Bug fixes Fix TypeError in OpenAI instrumentation: Newer versions of OpenAI  include an additional argument, resulting in an error with the base client instrumentation.  This has been fixed. Fix missing parameters in MessageTrace: Resolved issue where parameters were not being passed from the MessageTraceWrapper to the MessageTrace. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-91300","eolDate":"2025-08-08"},{"agent":"python","date":"2024-07-11","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.12.0","features":["Add instrumentation for aiomcache","Add support for collect_ai serverside config","Capture stack traces in NewRelicContextFormatter logs"],"bugs":["Fix crash in package capture in Python 2.7","Fix attribute check in OpenAI","Fix casing on LangChain metric and span names"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds instrumentation for aiomcache , support for an internally set collect_ai serverside configuration setting, formatting stack traces in NewRelicContextFormatter, fixes a crash in package catpuring in Python 2.7, an attribute check in OpenAI  instrumentation, and casing on LangChain  metric and span names. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add instrumentation for aiomcache: Add instrumentation support for aiomcache . Thank you Jair Henrique  for the contribution! Add support for collect_ai serverside config: Add support for an internally set collect_ai serverside configuration setting. Note this is returned in the connect response when a particular feature flag is set on an account. Adds support for formatting stack traces in NewRelicContextFormatter: NewRelicContextFormatter now implements the format_exc_info class method that formats stack traces. Thank you Daniel Fritz  for the contribution! Bug fixes Fix crash in package capture in Python 2.7: Previously, when capturing packages on Python 2.7 an UnboundLocalError would be raised. This has been fixed. Fix attribute check in OpenAI: Fix a typo in an attribute check inside the OpenAI  instrumentation. Thank you Liam Niehus-Staab  for the contribution! Fix casing on LangChain metric and span names: Previously, if LangChain  was being used in combination with an unsupported Large Language Model library (aka not Bedrock or OpenAI) then the AI dashboard tab would not appear in the UI because the metric name was not cased correctly. This has been fixed and the Span names have been updated to match the casing of the metric name. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-91200","eolDate":"2025-07-11"},{"agent":"python","date":"2024-06-13","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.11.0","features":["Add agent_language to lambda metadata","Optimize plugins list capturing","Add support for injecting the agent into Kubernetes","Add support for psycopg 3.0+"],"bugs":["Fix Large Language Model event duration units","Fix crash when using OpenAI with_raw_response","Fix crash when using OpenAI with_streaming_response","Fix a crash in ASGI when the Content-Length header is missing"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds agent_language to lambda metadata, support for injecting the agent into Kubernetes, support for psycopg 3.0+ , optimizes plugins list capturing, fixes the Large Language Model event duration units, a crash in ASGI when the Content-Length header is missing, a crash when using OpenAI 's .with_raw_response. and .with_streaming_response.. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add agent_language to lambda metadata Add agent_language to collected lambda metadata. Optimize plugins list capturing Skip checking for a package version on newrelic hooks that we know do not have versions. Add support for injecting the agent into Kubernetes Updates the bootstrap sitecustomize file to support injecting the agent into a Kubernetes cluster. A full product for agent injection in Kubernetes will be coming soon in public preview. A new informational only setting called k8s_operator.enabled (with NEW_RELIC_K8S_OPERATOR_ENABLED as an environment variable) was added, which is used to report when the agent is injected into a Kubernetes cluster. This setting does not  enable/disable this function of the agent. Add support for psycopg 3.0+ New instrumentation for psycopg 3.0+ has been added, providing database tracing for both the Connection and AsyncConnection classes. Bug fixes Fix Large Language Model event duration units Previously, durations on LLM events were recorded in seconds which did not match some of the other language agents. This has been changed to be milliseconds. Fix crash when using OpenAI 's .with_raw_response. Previously, an exception would be raised inside the instrumentation when .with_raw_response. was used. This no longer happens, the instrumentation successfuly records LLM data when .with_raw_response. is used. Fix crash when using OpenAI 's .with_streaming_response. Previously, an exception would be raised inside the instrumentation when .with_streaming_response. was used. This no longer happens, the instrumentation is just skipped. Fix a crash in ASGI when the Content-Length header is missing Previously, an exception would be raised inside the instrumentation that injects the browser agent when an ASGI response was missing the Content-Length header. This issue has been fixed. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-91100","eolDate":"2025-06-13"},{"agent":"python","date":"2024-05-23","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.10.0","features":["Add support for AIOBotocore","Add support for Meta Llama3","Add support for Mistral AI"],"bugs":["Fix OpenAI error parsing","Record loguru timing in milliseconds"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent: Adds instrumentation for AIOBotocore Adds support for Meta Llama3 and Mistral AI in Amazon Bedrock Fixes an error parsing issue in OpenAI Updates Loguru 's instrumentation to use milliseconds instead of seconds Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add AIOBotocore  instrumentation Add instrumentation for AIOBotocore.  Supports proxy mode in addition to standard operation. Add new Amazon Bedrock  models Add instrumentation for the following Amazon Bedrock  models: Meta Llama3 Mistral AI Bug fixes Fix OpenAI  error parsing Previously, if an error in OpenAI was encountered, the Python Agent would attempt to override the default error.message within notice_error() with the one used in OpenAI.  However, if there was no message attribute in the error, the Python Agent would crash.  Now it defaults to the original methodology of error handling by the Python Agent. Record timing in Loguru  in milliseconds Timing in Loguru is recorded as an integer and if that value was less than 1 second, it would record it as 0s.  This changes the units to be in milliseconds instead.  Thanks, (@julia-tadej-wwtech)[https://github.com/julia-tadej-wttech] for the contribution! Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-91000","eolDate":"2025-05-23"},{"agent":"python","date":"2024-05-13","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.9.1","features":["Add new Langchain vectorstores"],"bugs":["Update Celery instrumentation","Add HTTP method attributes to urllib3 traces","Fix gRPC URI detection"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes Celery  instrumentation on worker processes, adds new Langchain vectorstores, adds HTTP method attributes to urllib3 traces, and fixes an issue with URI detection in gRPC clients. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add new Langchain  vectorstores Support for the following Langchain vectorstores: Relyt, OracleVS, UpstashVectorStore, VLite Bug fixes Fix Celery  instrumentation on worker processes Instrumentation updates in v9.9.0 introduced a bug where Celery workers running with worker optimizations enabled would overwrite instrumentation. This has been fixed and instrumentation should now function the same with and without worker optimizations enabled. Add HTTP method attributes to urllib3  traces urllib3 traces did not include the HTTP method as an attribute previously.  This has now been added. Fix gRPC URI detection for client ExternalTraces The latest version of gRPC changed the format of URIs used in clients, which caused the hostname to be reported as \"dns\" for all client requests. This has been fixed and hostnames should be reported correctly again. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90901","eolDate":"2025-05-13"},{"agent":"python","date":"2024-04-18","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.9.0","features":["Update Celery instrumentation","Add new Langchain vectorstores","Add configuration to capture memory usage runtime metrics per process"],"bugs":["Report only raw content dictionary for Anthropic Claude"],"security":["Upgrade internal version of urllib3 to v1.26.18"],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent updates Celery instrumentation, adds new Langchain vectorstores, adds configuration to capture memory usage runtime metrics per process, fixes a content reporting issue in Anthropic Claude, and upgrades internal version of urllib3 to v1.26.18. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Security Upgrade internal version of urllib3 to v1.26.18 Upgrade the internal version of urllib3  used in the Python Agent to v1.26.18 to resolve security warnings. New features Update Celery instrumentation Add support for distributed tracing in Celery  over AMQP headers. Remove duplicate function traces for some methods of running tasks. All tasks should now only be instrumented once, and will report either an OtherTransaction, or a FunctionTrace if run under an existing transaction. Fix instrumentation for grouped celery tasks APIs, such as task.map(), celery.group(), and celery.chunks(). Tasks run using task.map() or task.starmap() will now name tasks in the format Celery/celery.map/my_task to allow you to differentiate between map tasks. Individual task runs created by the map() and starmap() tasks will be traced with a FunctionTrace to capture individual timings. Add new Langchain  vectorstores Support for the following Langchain vectorstores: DuckDB, EcloudESVectorStore, InMemoryVectorStore, PathwayVectorClient, VDMS Add configuration setting to enable capturing of memory usage runtime metrics per process Add memory_runtime_pid_metrics.enabled configuration setting to toggle capturing of memory usage metrics (per process ID only) to reduce Metric Grouping Issues (MGI). Bug fixes Report only raw content dictionary for Anthropic Claude Previously, AWS Bedrock's Anthropic Claude model would report a list of dictionaries of message content. Now it reports a single dictionary of message content. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90900","eolDate":"2025-04-18"},{"agent":"python","date":"2024-03-27","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.8.0","features":["Add support for asgiref 3.8.0 and above","AI monitoring","AI monitoring configuration","AI monitoring public API methods","Add support for OpenAI","Add support for Langchain","Add support for AWS Bedrock"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for the latest versions of asgiref  and support for AI monitoring when using the following libraries: OpenAI , AWS Bedrock , and Langchain . Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for asgiref  3.8.0 and above Asgiref released a new version that resulted in missing transaction context. This has been fixed. AI monitoring New Relic AI monitoring is the industry’s first APM solution that provides end-to-end visibility for AI Large Language Model (LLM) applications. It enables end-to-end visibility into the key components of an AI LLM application. With AI monitoring, users can monitor, alert, and debug AI-powered applications for reliability, latency, performance, security and cost. AI monitoring also enables AI/LLM specific insights (metrics, events, logs and traces) which can easily integrate to build advanced guardrails for enterprise security, privacy and compliance. AI monitoring offers custom-built insights and tracing for the complete lifecycle of an LLM’s prompts and responses, from raw user input to repaired/polished responses. AI monitoring provides built-in integrations with popular LLMs and components of the AI development stack. This release provides instrumentation for OpenAI , AWS Bedrock , and Langchain . When AI monitoring is enabled with ai_monitoring.enabled = true, the agent will now capture AI LLM related data. This data will be visible under a new APM tab called AI Responses. See our AI Monitoring documentation  for more details. AI monitoring configuration New configuration options are available specific to AI monitoring . These settings include: ai_monitoring.enabled ai_monitoring.streaming.enabled ai_monitoring.content.enabled AI monitoring public API methods Two new AI monitoring related public API methods have been added: record_llm_feedback_event set_llm_token_count_callback Add support for AWS Bedrock Support for AWS Bedrock Large Language Model instrumentation has been added. Chat completion and embedding data for streaming and non-streaming is recorded for the following models: amazon.titan-* ai21.j2-* anthropic.claude-* cohere.command-* meta.llama2-* amazon.titan-embed* cohere.embed* Add support for Langchain Support for Langchain Large Language Model instrumentation has been added. Langchain Agents, Chains, Tools, OpenAI, and Bedrock LLM data is recorded. Note streaming is not supported at this time. Add support for OpenAI Support for OpenAI Large Language Model instrumentation has been added. Synchronous and asynchronous chat completion and embedding data is recorded. Note streaming is only supported in chat completions at this time. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90800","eolDate":"2025-03-27"},{"agent":"python","date":"2024-03-11","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.7.1","features":[],"bugs":["Fix log attribute dropping in NewRelicContextFormatter"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes a bug in the NewRelicContextFormatter where attributes were dropped from logs. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Bug fixes Fix log attribute dropping in NewRelicContextFormatter In v9.5.0, a bug in the NewRelicContextFormatter was introduced where message was added to the default set of keys to exclude. This caused extra attributes not in the default list to be dropped. This bug has been fixed. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90701","eolDate":"2025-03-11"},{"agent":"python","date":"2024-02-22","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.7.0","features":["Remove reporting of attributes with None values"],"bugs":["Add transaction trace ID to the error traces even when Distributed Tracing is not enabled"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent no longer reports attributes with None values. It also attaches a transaction trace ID to the error traces even when distributed tracing is disabled. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Remove reporting of attributes with None values Previously, the agent recorded attributes with a value of None type as the string \"None\".  The agent will no longer record user or agent attributes that have None type values. Bug fixes Add transaction trace ID to the error traces even when distributed tracing is disabled Previously, certain trace attributes in error traces such as stack traces were only visible in the UI if distributed tracing was enabled.  Linking the transaction trace to error traces by including the transaction trace ID on the error traces allows the user to have access to the transaction trace attributes in the UI. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90700","eolDate":"2025-02-22"},{"agent":"python","date":"2024-01-25","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.6.0","features":["Support dictionary type logs in NewRelicLogForwardingHandler","Support logging formatters in NewRelicLogForwardingHandler"],"bugs":["Fix a bug when specifying processors in structlog"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes a bug when specifying processors in structlog , and updates the NewRelicLogForwardingHandler to support dictionary type logs and formatters. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Support dictionary type logs in NewRelicLogForwardingHandler Dictionary type log messages are now supported in NewRelicLogForwardingHandler when passed as the log message, or when a custom formatter returns a dictionary. The key message will be extracted if available and treated as the log message, and any other items will be considered context data attributes and prefixed with message.. These attributes are subject to the same filtering rules as other context data. The message. prefix is not considered when filtering attributes from logs. To report these attributes, enable context data forwarding  and optionally configure include  and exclude  rules to filter the allowed attributes. Support logging formatters in NewRelicLogForwardingHandler Logging formatters added with setFormatter() are now supported, and may return a string or dicitionary log message type to be forwarded to New Relic. Bug fixes Fix a bug when specifying processors in structlog Previously, there was a bug in the structlog instrumentation where processors was assumed to be list type. Now the instrumentation supports processors of all iterable types. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90600","eolDate":"2025-01-25"},{"agent":"python","date":"2024-01-11","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.5.0","features":["Add context data attributes to logs","Add support for dictionary type log messages","Obfuscate license keys and user API keys in logs","Add attribute support to `record_log_event` API"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds context data attributes to logs, support for dictionary type log messages, adds attribute support to record_log_event API, and obfuscates logged license keys and user API keys. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add context data attributes to logs Context data available from logging frameworks can now be recorded as attributes on logs. These attributes are prefixed with context., which is not considered when filtering attributes from logs. Context data may include extras, dictionary message attributes, and attributes provided by logging frameworks. To report these attributes, enable context data forwarding  and optionally configure include  and exclude  rules to filter the allowed attributes. Add support for dictionary type log messages Dictionary type log messages are now supported for logging frameworks which support dictionary type log messages (including the builtin logging module and structlog). The key message will be extracted if available and treated as the log message, and any other items will be considered context data attributes and prefixed with message.. These attributes are subject to the same filtering rules as other context data. Add attribute support to record_log_event API The record_log_event API now allows passing context data in using the optional attributes keyword argument, and allows the message argument to be a dictionary as described above. Obfuscate license keys and user API keys in logs The agent now obfuscates all instances of license keys or user API keys in agent logs and audit logs. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90500","eolDate":"2025-01-11"},{"agent":"python","date":"2024-01-08","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.4.0","features":["Add nonced context security policy support","Add wheels for Python 3.12 and musl","Publish newrelic.agent.CallableObjectProxy API","Deprecate ObjectWrapper API","Deprecate get_browser_timing_footer API"],"bugs":["Fix distributed tracing headers in kafka","Fix case sensitive header search in ASGIBrowserMiddleware"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for nonced content security policies for browser agent injection, adds new wheels for Python 3.12 and musl Linux systems such as Alpine, deprecates the ObjectWrapper and get_browser_timing_footer APIs, fixes a crash with Kafka instrumentation when using distributed tracing, and removes a case sensitive header check in ASGIBrowserMiddleware. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Deprecations Deprecated newrelic.agent.ObjectWrapper API Removes custom newrelic.agent.ObjectWrapper implementation and instead creates a pass through to wrapt.FunctionWrapper. Deprecated get_browser_timing_footer API Previously get_browser_timing_footer was an API that would be used to supply information to the browser agent loaded by get_browser_timing_header. This step is now included in get_browser_timing_header, making get_browser_timing_footer obsolete. This function now returns an empty string to avoid breaking existing applications. New features Added nonced content security policies (CSPs) for browser agent injection The browser agent injection API get_browser_timing_header has a new parameter nonce that takes a cryptographic nonce for use with content security policies. The nonce will be automatically inserted into the generated HTML. Added additional wheel options for Python 3.12 and musl Linux Added pre-built binary wheel support for Python 3.12 as well as alternative wheels for musl-based Linux operating systems (such as Alpine). Added newrelic.agent.CallableObjectProxy to public APIs Previously CallableObjectProxy was never exposed for general use with custom instrumentation, but was present in internal modules used by the agent. This API has been added to newrelic.agent.CallableObjectProxy for general use. Bug fixes Fixed a crash with kafka-python  and confluent-kafka  when using distributed tracing Previously Kafka instrumentation packages would sometimes fail to generate distributed tracing headers and cause a crash. This has been fixed and distributed tracing headers should now generate correctly. Removed case sensitive header check in ASGIBrowserMiddleware The agent previously only supported HTML insertion for headers that were lowercase in ASGI applications. The header check is now case insensitive in compliance with the ASGI specification. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90400","eolDate":"2025-01-08"},{"agent":"python","date":"2023-12-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.3.0","features":["Add support for Python 3.12","Add support for Docker cgroups v2","Add new synthetics information header","Upgrade internal wrapt to v1.16.0"],"bugs":["Fix structlog CallsiteParameter processor bug"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds Python 3.12 support. It also includes support for sending utilization data for Docker with cgroups v2, adds a new synthetics information header, upgrades the agent's internal wrapt  version, and includes a bug fix for structlog . Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for Python 3.12 \nThe agent now supports applications running in Python 3.12. Add support for Docker cgroups v2 \nThe agent now includes functionality to parse Docker IDs in later versions of Docker using cgroups v2. Add new synthetics information header \nThe agent now retransmits and processes information contained in a new synthetics header: X-NewRelic-Synthetics-Info. Changes Upgrade internal wrapt to v1.16.0 \nThe agent's internal copy of wrapt  has been upgraded to v1.16.0 in conjunction with Python 3.12 support. Bug fixes Fix structlog CallsiteParameter processor bug \nCall site parameter values in structlog  no longer produce incorrect values. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90300","eolDate":"2024-12-06"},{"agent":"python","date":"2023-11-16","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.2.0","features":["Add configuration option package_reporting.enabled"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds a new configuration option that allows users to disable capturing package and version information at agent startup. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add new configuration option package_reporting.enabled. \nThis option allows users to disable capturing package and version information at agent startup. On some applications with a high number of packages some users were seeing a spike in CPU usage. Disabling this setting provides a workaround for that issue. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90200","eolDate":"2024-11-16"},{"agent":"python","date":"2023-11-13","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.1.2","features":[],"bugs":["Fix package version performance regression"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes a regression in package version performance that was introduced in 8.10.1. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Bug fixes Fix package version performance regression \nAddressed issue that was introduced in 8.10.1 where there is increased CPU usage and time on startup and when using certain libraries at runtime. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90102","eolDate":"2024-11-13"},{"agent":"python","date":"2023-10-19","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.1.1","features":["Add get_package_version caching"],"bugs":["Fix redis generator instrumentation"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes generator instrumentation issue with Redis and adds caching to package versions to address some performance issues. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add caching to get_package_version to address performance issues Bug fixes Fix generator and async generator instrumentation issue in Redis.asyncio Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90101","eolDate":"2024-10-19"},{"agent":"python","date":"2023-09-25","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.1.0","features":["Add support for sklearn","Add instrumentation for redis.asyncio.Connection"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for sklearn  and redis.asyncio connections. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for sklearn \nThe Python agent now supports monitoring for machine learning models created with sklearn. Check out our documentation  for details on how to view and query for your prediction events and ML related metrics directly in the New Relic user interface. Machine learning instrumentation will be disabled by default in this release. To enable it, visit our configuration page  for further information.\nThis release also introduces two new APIs to support customization of machine learning monitoring: wrap_mlmodel  and record_ml_event . Add instrumentation for redis.asyncio.Connection \nAdd instrumentation support for connections initiated from the redis.asyncio module Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90100","eolDate":"2024-09-25"},{"agent":"python","date":"2023-08-28","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"9.0.0","features":["Add support for async graphql-core 3.0","Drop support for async graphql-core 2.0"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for async graphql-core  and drops support for graphql-core 2. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Framework Support Drop support for graphql-core 2 \nRemove support for graphql-core 2.0. Enhancements Add support for async graphql-core \nAdd support for async graphql-core 3.0 and above. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-90000","eolDate":"2024-08-28"},{"agent":"python","date":"2023-08-23","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.11.0","features":["Add support for structlog"],"bugs":["Fix certificate fallback logic","Fix missing database metric"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for structlog  and some bug fixes. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Enhancements Add support for structlog \nAdds instrumentation support for structlog . Bug fixes Fix certificate fallback logic \nFixed the fallback logic for the certificate bundle such that it only uses the builtin bundle when both the cafile AND capath are None. Fix missing database metric \nFixed an issue where certain databases were not recording the Datastore/instance/<db>/<host>/<port> metric and so the database was not showing up in the service map. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-81100","eolDate":"2024-08-23"},{"agent":"python","date":"2023-08-17","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.10.1","features":["Add support for new commands introduced in Redis v5"],"bugs":["Fix crash in MetricNormalizationRules","Fix DeprecationWarning in package version detection for Python 3.10+"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes an issue with MetricNormalizationRules, fixes a DeprecationWarning in package version detection, and adds support for new commands introduced in Redis v5 . Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Enhancements Add support for new commands introduced in Redis v5 \nAdds full instrumentation support for Redis v5 . Bug fixes Fix crash in MetricNormalizationRules \nFixed a crash when using client side MetricNormalizationRules to ignore metrics (set through NerdGraph and available under a feature flag). The metrics should now be properly ignored. Fix DeprecationWarning in package version detection for Python 3.10+ \nFixed a DeprecationWarning emitted by package version detection used internally for Python 3.10+. When importlib.metadata is available, prefer using it to avoid checking deprecated version  attributes on modules. (Thanks @renanivo for the contribution!) Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-81001","eolDate":"2024-08-17"},{"agent":"python","date":"2023-08-10","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.10.0","features":["Add support for firestore","Add support for Redis async","Add automatic wrapping for async generators","Drop support for redis 3 and below"],"bugs":["Fix crash on throw for wrapped generator"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent drops support for Redis v3 and below and adds support for Google Cloud Firestore , async Redis , and fixes a crash that occurs when wrapping generators. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Deprecations Drop support for Redis v3 and below \nAs of v8.10.0, Redis  v3 and below are outside New Relic's supportability window and therefore no longer supported. Because Redis v4 and above no longer support Python 2.7, this means Python 2.7 support has been dropped from Redis as well. Enhancements Add support for Firestore \nAdds instrumentation support for Google Cloud Firestore . Add support to Redis Async \nAdds instrumentation support for Redis' async features.  Thanks, ahmedhr  and bc291  for your contribution! Automatic wrapping for async generators \nExisting tracing decorator APIs now support async generators out of the box. Bug fixes Fixed a crash when consecutive calls to throw() on wrapped generators \nPreviously consecutive calls to throw() would raise an exception rather than inject the exception into the wrapped generator. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-81000","eolDate":"2024-08-10"},{"agent":"python","date":"2023-07-27","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.9.0","features":["Add support for redisclusters"],"bugs":["Fix crash on generalimport package","Remove deprecated drop_transaction calls","Fix serverless distributed tracing"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for RedisCluster . Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Enhancements Add support for RedisCluster \nAdds instrumentation support for RedisCluster . Bug fixes Resilient Environment Settings \nFixed a crash when using generalimport  with the agent.  Thanks for the contribution, aaeabdo ! Remove deprecated drop_transaction calls from agent \nThe drop_transaction function had been removed from the agent but references to it still existed, so this version of the agent removes any remaining calls. Fix logic in serverless distributed tracing to work by default Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-80900","eolDate":"2024-07-27"},{"agent":"python","date":"2023-06-26","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.8.1","features":["Add support for redis 4.6.0","Add support for loguru 0.7.0"],"bugs":["Fix reporting of locally scoped packages"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes a bug in package reporting and adds support for redis 4.6.0 and loguru 0.7.0. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Enhancements Add support for redis 4.6.0 \nAdds instrumentation support for new waitaof method. Add support for loguru 0.7.0 \nAdds support for loguru v0.7.0. Bug fixes Fix reporting of locally scoped packages \nPreviously, locally scoped Python packages (such as those installed into user scope) were not reported on agent connect. This has been fixed. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-80801","eolDate":"2024-06-26"},{"agent":"python","date":"2023-03-30","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.8.0","features":["Add new Errors Inbox features"],"bugs":["Add guard for GraphQL settings lookup","Fix Redis instance information"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for two new errors inbox features: error fingerprinting and user tracking. It also includes bug fixes. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features New Errors Inbox features User tracking : You can now see the number of users impacted by an error group. Identify the end user with the set_user_id method. Error fingerprinting : Are your error occurrences grouped poorly? Set your own error fingerprint via a callback function. Bug fixes Guard GraphQL settings lookup \nIn v8.7.1, a bug was introduced in GraphQL instrumentation when not running within a transaction. This crash has been addressed. Fix Redis instance information \nRedis v4.5.2 included a change that broke detection for socket based redis instance information. The agent now correctly detects socket paths again. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.12.0.140 . More information can be found in the EOL Policy Page .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-80800","eolDate":"2024-03-30"},{"agent":"python","date":"2023-03-20","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.7.1","features":["Add support for a new config option to capture GraphQL introspection query transactions"],"bugs":["Fix introspection query recognition for GraphQL"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for a new config option to capture GraphQL introspection query transactions. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for a new config option to capture GraphQL introspection query transactions. Added new config setting instrumentation.graphql.capture_introspection_queries and corresponding environment variable NEW_RELIC_INSTRUMENTATION_GRAPHQL_CAPTURE_INTROSPECTION_QUERIES to control capturing of GraphQL introspection transactions. Defaults to false which retains previous behavior of ignoring transactions with introspection queries. Bug fixes Fix introspection query recognition for GraphQL. Fix introspection query recognition for GraphQL to allow introspection fields to be queried alongside real fields in traces. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.12.0.140 . Find more information in the EOL Policy Page .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-80701","eolDate":"2024-03-20"},{"agent":"python","date":"2023-02-16","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.7.0","features":["Add support batching and compression of infinite tracing"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for batching and compression. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support batching and compression of infinite tracing Adds configuration options infinite_tracing.compression and infinite_tracing.batching and sets both to on by default. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.8.0.136 . Find more information in the EOL Policy Page .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-80700","eolDate":"2024-02-16"},{"agent":"python","date":"2023-02-09","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.6.0","features":["Add support for eleasicsearch 8","Add support for redis v4.4.1 and v4.4.2","Add support for redis.asyncio","Add apdexPerfZone to web transaction event attribute intrinsics"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for elasticsearch 8, redis.asyncio, and exposes apdexPerfZone. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for eleasicsearch 8 \nAdd instrumentation support for elasticsearch version 8. Add support for redis v4.4.1 and v4.4.2 \nAdd support for new methods in the latest versions of redis. Add support for redis.asyncio \naioredis is included to redis-py since version 4.2.0rc1 as redis.asyncio. Support this\nnew location.\nThank you @pauk-slon  for your contribution! Add apdexPerfZone to web transaction event attribute intrinsics \nExpose nr.apdexPerfZone as apdexPerfZone in Web transaction event attribute intrinsics. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.6.0.135 . More information can be found in the EOL Policy Page .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-80600","eolDate":"2024-02-09"},{"agent":"python","date":"2022-12-07","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.5.0","features":["Add support for redis v4.3.5 and v4.4.0 methods","Add record_log_event API"],"bugs":["Fix RuntimeError: dictionary changed size during iteration","Fix confluent-kafka producer arguments","Patch sentry SDK to correct ASGI v2/v3 detection","Fix missing information issue with Celery workers when using MAX_TASKS_PER_CHILD","Fix support for dynamically generated types in Code Level Metrics","Fix external node properties initialization"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds the record_log_event API and includes some bug fixes. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for redis v4.3.5 and v4.4.0 methods New methods added in redis v4.3.5 and v4.4.0 will now be automatically instrumented. Add record_log_event API This records a log event  that can be viewed and queried in the New Relic UI. See record_log_event  for details. Bug fixes Fix RuntimeError: dictionary changed size during iteration Properly guard trace_cache from RuntimeErrors raised due to concurrent iteration and size changes of the TraceCache. Fix confluent-kafka producer arguments Fixes a bug where topic provided as a keyword argument can crash Confluent Kafka producers. Patch sentry SDK to correct ASGI v2/v3 detection Patches sentry-sdk to fix a bug that causes incorrect ASGI application version detection with our wrapt function wrappers. To fix this, we now instrument the _looks_like_asgi3() function to bind out the wrapped app in sentry in order to unwrap it to be able to detect the proper ASGI version. Fix missing information issue with Celery workers when using MAX_TASKS_PER_CHILD A bug was introduced in v7.8.0.174 when Celery was run with the --loglevel=INFO flag to not report any data after the original worker processes shut down. This has been fixed. Fix support for dynamically generated types in Code Level Metrics A bug in code level metrics attribute extraction prevented attributes from being applied to types created using the 3 argument type constructor . This has been fixed. Fix external node properties initialization A bug caused by uninitialized external node properties when making web requests has been fixed. Thank you @kmorey  for your contribution! Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.4.1.134 . More information can be found in the EOL Policy Page .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-80500","eolDate":"2023-12-07"},{"agent":"python","date":"2022-10-26","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.4.0","features":["Increase custom event limit"],"bugs":["Fix NewRelicContextFormatter attribute error"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date . As of this release, the oldest supported version is 5.2.2.130 . Notes This release of the Python agent increases the custom event limit and includes a bug fix. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Changes Increase custom event limit This agent version increases the default limit of custom events from 1,200 events per minute to 3,600 events per minute. In the scenario that custom events were being limited, this change will allow more custom events to be sent to New Relic. There is also a new configurable maximum limit of 100,000 events per minute. To change the limits, see the docs for event_harvest . To learn more about the change and how to determine if custom events are being dropped, see our Explorers Hub post . Bug fixes Fix NewRelicContextFormatter attribute error A bug was introduced in v8.3.0 that caused an AttributeError when using the NewRelicContextFormatter. This has been corrected in this release version.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-80400","eolDate":"2023-10-26"},{"agent":"python","date":"2022-10-24","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.3.0","features":["Add support for Python 3.11","Add usage metrics for Kafka clients, Daphne, and Hypercorn"],"bugs":["Fix Flask view support for Code Level Metrics","Fix aioredis version crash"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds Python 3.11 support, deprecates the add_custom_parameter(s) API, adds usage metrics for multiple libraries, and includes bug fixes. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Deprecations add_custom_parameter(s) API is now deprecated \nThe add_custom_parameter(s) API has been renamed to add_custom_attribute(s). A deprecation warning will be emitted when calling add_custom_parameter() from this agent version and higher. New features Add support for Python 3.11 \nThe agent now supports applications running in Python 3.11. Add usage metrics for Kafka clients, Daphne, and Hypercorn \nThe agent now emits a messagebroker metric for Kafka clients and a dispatcher metric for Daphne and Hypercorn. This metric is similar to the framework metric already being emitted for all web frameworks supported by the agent. Bug fixes Fix Flask view support for Code Level Metrics \nThe agent was previously reporting the class name for the code.function attribute in the case of Flask method dispatching. This has been corrected to report the instrumented function name. Fix aioredis version crash \nA fix has been implemented to address a crash in aioredis in cases where the agent was initialized before importing aioredis on aioredis>=2.0.1. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.2.2.130 . More information can be found in the EOL Policy Page .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-80300","eolDate":"2023-10-24"},{"agent":"python","date":"2022-10-10","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.2.1","features":["Update Sanic middleware support","Update wrapt to v1.14.1","Add support for Protobuf v4"],"bugs":["Fix a RuntimeError in the trace cache when using the coroutine profiler","Fix an issue with case sensitivity in record-deploy","Fix an issue with newer installers failing to install the agent","Fix instrumentation for aioredis interfering with transactions","Fix a crash when completing various kinds of traces inside a stopped transaction","Fix a bug where instrumentation caused certain arguments to confluent-kafka producers to stop working"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent provides numerous bug fixes, including several community contributions, provides updates to Sanic instrumentation, Protobuf v4 compatiblity, and updates internal packages for Python 3.11 support. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Version numbering change The version number of the agent did not previously follow Semantic Versioning  properly. This has been changed. Going forward build numbers have been removed from the version number, and version increments will follow semantic versioning fully. No retroactive changes will be made to previous version numbers. Instrumentation updates Update Sanic middleware support Sanic recently changed their APIs surrounding middleware, and instrumentation has been updated to support it. Package updates Update wrapt to v1.14.1 The internal copy of the wrapt library used by the agent has been updated to v1.14.1 for Python 3.11 compatibility. Add support for Protobuf v4 The agent is now fully compatible with Protobuf v4 when using Infinite Tracing. Backwards compatibility with Protobuf v3 has been preserved. Bug fixes Fix a RuntimeError in the trace cache when using the coroutine profiler A RuntimeError occurred if traces were started or stopped while the coroutine profiler was sampling the active traces. This should no longer be possible. Thank you @lovmat  for your contribution! Fix an issue with case sensitivity in record-deploy Previously application names were incorrectly being treated as case-sensitive when running newrelic-admin record-deploy. Thank you @michalborkowski96  for your contribution! Fix an issue with newer installers failing to install the agent Due to the inclusion of both scripts and entry_points configuration options, the agent would fail to install with newer installers. This has been corrected and newer PEP compliant installers should have no trouble installing the agent. Thank you @admp-fh  for your contribution! Fix instrumentation for aioredis interfering with transactions The agent does not currently support transactions for Redis clients, and previous instrumentation broke transaction functionality in AioRedis. This has been fixed to provide no instrumentation within transactions at this time. Fix a crash when completing various kinds of traces inside a stopped transaction Previously certain types of traces could throw exceptions and fail to complete when inside stopped transactions. This has been corrected and should no longer be possible. Fix a bug where instrumentation caused certain arguments to confluent-kafka producers to stop working Previously callback and on_delivery arguments were passed through improperly leading to them not working as expected. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.2.2.130 . More information can be found in the EOL Policy Page .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-80201","eolDate":"2023-10-10"},{"agent":"python","date":"2022-09-27","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.2.0.181","features":["Add kafka-python instrumentation","Add confluent-kafka instrumentation"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds automatic instrumentation for Kafka Python as well as Confluent Kafka. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add kafka-python instrumentation Instrumentation has been added for Kafka Python . Add confluent-kafka instrumentation Instrumentation has been added for Confluent Kafka . More information can be found in the Message Queue documentation Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.2.0.127 .  More information can be found in the EOL Policy Page .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-80200181","eolDate":"2023-09-27"},{"agent":"python","date":"2022-09-12","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.1.0.180","features":["Add Hypercorn instrumentation"],"bugs":["Fix instrumentation for Sanic v21.9","Fix incorrect PID reported by memory sampler","Fix issue with database traces causing crashes"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds automatic instrumentation for Hypercorn, and includes bug fixes for Sanic v21.9+, memory sampler reporting, and database traces. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add Hypercorn instrumentation Instrumentation has been added for Hypercorn , an ASGI web server. Bug fixes Fix instrumentation for Sanic v21.9+ Instrumentation for newer versions of Sanic (>=21.9) have either not reported data or crashed due to an incompatibility with Sanic's internal metaprogramming. Fix incorrect PID reported by memory sampler The PID reported by the memory sampler when sampling processes was incorrectly attributed to the process the agent was initialized from. Fix issue with database traces causing crashes In rare instances a database trace could result in a setting not being found, causing a crash. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.2.0.127 .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-80100180","eolDate":"2023-09-12"},{"agent":"python","date":"2022-08-15","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"8.0.0.179","features":["Add Daphne instrumentation","Add module version reporting'"],"bugs":["Fix a bug in file path detection for Loguru"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent removes support for Python 3.6. It also includes new instrumentation for Daphne, reporting installed module versions, and a fix for a bug affecting Loguru file paths. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Deprecations Removed support for Python 3.6 Python 3.6 is no longer supported by the agent. Please consider upgrading your application to a supported version of Python in order to continue to receive updates to the Python Agent. New features Add Daphne instrumentation Instrumentation has been added for Daphne , a Django project ASGI web server and the recommended server for Django Channels . Add module version reporting Installed python packages now have their versions reported and are visible in the Environment tab for your application in New Relic One. Bug fixes Fix a bug in file path detection for Loguru Wrappers from the agent interfered with Loguru file path detection for templating messages. This has been corrected on all versions. Thank you to @rafaelclp  for your contribution! Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.0.2.126 .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-80000179","eolDate":"2023-08-15"},{"agent":"python","date":"2022-07-21","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"7.16.0.178","features":["Add APM logs in context","Add top level aggregated data usage supportability metric","Change data usage supportability metric name"],"bugs":["Fix data usage supportability metric compression payload calculation"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent enables log forwarding to New Relic by default. It also addresses a bug related to compressed bytes calculations and adds a new top level data usage supportability metric to the agent. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add APM logs in context Automatic application log forwarding is now enabled by default. This version of the agent will automatically send enriched application logs to New Relic. To learn more about about this feature, see the APM logs in context documentation . For additional configuration options, see the Python logs in context documentation . To learn about how to toggle log ingestion on or off by account, see our documentation to disable automatic logging  via the UI or API. Add top level aggregated data usage supportability metric The agent now reports a top level data usage supportability metric: Supportability/Python/Collector/Output/Bytes. This aggregates all uncompressed bytes across all agent methods sent to New Relic. Changes Change data usage supportability metric name Previously, the agent reported data usage supportability metrics in the format Supportability/Python/Collector/Output/Bytes/<agent_method>. This has been changed to be in the format Supportability/Python/Collector/<agent_method>/Output/Bytes to align with the agent specification. Bug fixes Fix data usage supportability metric compression payload calculation Previously, the agent was reporting the compressed bytes for the Supportability/Python/Collector/Output/Bytes metric group and uncompressed bytes for the Supportability/Python/Collector/ZLIB/Bytes metric group. This was incorrect and has been fixed in this release. Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.0.0.124 .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-71600178","eolDate":"2024-07-21"},{"agent":"python","date":"2022-06-27","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"7.14.0.177","features":["Add support for aioredis","Enhance support for redis and aredis"],"bugs":["Fix `threading.currentThread` deprecation"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for aioredis, enhances support for redis and aredis, and fixes a deprecation. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for aioredis The agent will now automatically instrument and send metrics for applications using the Redis and StrictRedis clients for aioredis. Improvements Enhance support for redis and aredis The agent now instruments a more extensive list of commands for redis and aredis clients. This includes commands under the search, graph, time series, json, sentinel, and bf modules. Bug Fixes Fix threading.currentThread deprecation threading.currentThread was deprecated in Python 3.10  and has been replaced with threading.current_thread. Thank you hugovk  for your contribution to the agent! Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 5.0.0.124 .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-71400177","eolDate":"2024-06-27"},{"agent":"python","date":"2022-06-09","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"7.12.0.176","features":["Add APM logs in context","Add support for logging metrics","Adds support for forwarding application logs to New Relic","Add support for enriching application logs written to disk or standard out","Rename whitelist setting to allowlist"],"bugs":["Fix incompatibility with gRPC v4","Fix Starlette v0.19.1+ instrumentation","Fix unhelpful error messages appearing outside of debug logs"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds APM logs in context. Additionally this release fixes issues in Starlette and gRPC version compatibility, renames whitelist settings, and removes unwanted error logs. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add APM logs in context A quick way to view logs no matter where you are in the platform. To learn more, see the documentation about APM logs in context . Add support for logging metrics Logging metrics show the rate of log messages by severity in the logs chart in the APM Summary  view. This is enabled by default in this release. Add support for forwarding application logs to New Relic This automatically sends application logs that have been enriched to power APM logs in context. This is disabled by default in this release. This will be on by default in a future release. For more information, see our documentation about logs in context for Python . Add support for enriching application logs written to disk or standard out This can be used with another log forwarder to power APM logs in context if in-agent log forwarding is not desired. We recommend enabling either log forwarding or local log decorating, but not both features. This is disabled by default in this release. Changes Rename Whitelist Setting to Allowlist The setting strip_exception_messages.whitelist has been renamed to the more modern name strip_exception_messages.allowlist. The original setting will continue to function but issue a deprecation warning. Bug Fixes Fix incompatibility with gRPC v4 Previously a crash was possible in the agent when gRPC v4 was installed when not using the infinite tracing feature. This has been corrected and the agent can safely be used with gRPC v4. Fix Starlette v0.19.1+ instrumentation A crash in CustomRoutes in Starlette v0.19.1 has been addressed and fixed. Starlette v0.20.1 reorganized important files which were then uninstrumented. This has been fixed. Fix unhelpful error messages appearing outside of debug logs Error messages related to context propagation have been demoted to debug logs to avoid unwanted and unhelpful messages appearing in logs.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-71200176","eolDate":"2024-06-09"},{"agent":"python","date":"2022-04-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"7.10.0.175","features":["Add integration with CodeStream"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds CodeStream integration support which includes code level metrics. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add integration with CodeStream \nNow Introducing Code-Level Metrics! Golden Signals visible in your IDE through New Relic CodeStream.\nLearn more here . For any issues or direct feedback, please reach out to support@codestream.com","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-71000175","eolDate":"2024-04-06"},{"agent":"python","date":"2022-03-31","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"7.8.0.174","features":["Add support for GraphQL Server","Add a log handler","Add more robust `should_ignore_error` calls"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for GraphQL Server, adds a log handler which forwards logs to the New Relic API, and increases functionality to notice_error. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for GraphQL Server \nThe agent will now automatically instrument and send metrics for applications using the GraphQL Server. Add a Log Handler \nThe agent is now able to forward logs to the New Relic API.  Thank you to iamr0b0tx  for your contribution! Changes More Robust should_ignore_error calls \nPass references to settings where possible to should_ignore_error and makes custom _nr_ignored logic more defined and incorporated into notice_error.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-70800174","eolDate":"2024-03-31"},{"agent":"python","date":"2022-02-25","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"7.6.0.173","features":["Add support for Aredis"],"bugs":["Fix garbage collection sampler attribute errors","Safeguards against lost data with infinite tracing"],"security":["Upgrades to the AWS metadata endpoint"],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Aredis, upgrades to the AWS metadata endpoint to IMDSv2, and fixes attribute errors with the garbage collector sampler. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for Aredis \nThe agent will now automatically instrument and send metrics for applications using the StrictRedis client from Aredis. Changes Upgrades to the AWS Metadata Endpoint \nUpgrades the AWS metadata endpoint to IMDSv2. Bug fixes Fix Garbage Collection Sampler Attribute Errors \nA crash caused by an attribute error on the garbage collector sampler has been fixed. Safeguards Against Lost Data with Infinite Tracing \nFixed race condition between agent and gRPC that resulted in loss of data on agent reconnect.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-70600173","eolDate":"2024-02-25"},{"agent":"python","date":"2022-01-20","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"7.4.0.172","features":["Add support for Django v4","Add support for Redis v4","Add support for graphql-core v3.2.0"],"bugs":["Fix Graphene framework details","Fix memory sample exception","Fix import hook warnings for Python 3.10"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Django v4, Redis v4, GraphQL v3.2, as well as fixes to the memory sample exception, Graphene framework, and import hook warnings for Python 3.10. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for Django v4 \nThe agent will now automatically instrument and send metrics for applications using Django v4. Add support for Redis v4 \nThe agent will now automatically instrument and send metrics for applications using Redis v4. Add support for graphql-core v3.2.0 \nThe agent will support the latest version of GraphQL. Changes Fix Graphene framework details \nData on graphene framework details was missing on newer versions, this has been fixed. Bug fixes Fix memory sample exception \nThis fixes the crash in memory sampler on non-supported systems. Fix import hook warnings for Python 3.10 \nAn ImportWarning that was emitted when importing the agent in Python 3.10 has been corrected.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-70400172","eolDate":"2024-01-20"},{"agent":"python","date":"2021-11-11","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"7.2.4.171","features":[],"bugs":["Fix gRPC retry logic","Fix crash in database trace"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes an issue with infinite tracing's usage of gRPC allowing subchannels to retry, and fixes failing database traces. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Bug Fixes Fix gRPC retry logic Previously gRPC subchannels left open by infinite tracing could cause network congestion and strain our trace observers. This issue has been corrected. As such, specific versions of gRPC are no longer required. Fix crash in database trace A crash in database traces resulting from nullified settings (seen rarely in Django) has been corrected.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-70204171","eolDate":"2023-11-11"},{"agent":"python","date":"2021-11-04","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"7.2.3.170","features":[],"bugs":["Fix FastAPI context propagation error","Fix gRPC incompatibilities"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes an issue with FastAPI instrumentation, as well as restricts gRPC to compatible versions. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Bug Fixes Fix FastAPI context propagation error A runtime instrumentation error stemming from context propagation in FastAPI has been fixed. Fix gRPC incompatibilities The version of gRPC has been pinned until compatiblity can be ensured with newer versions. gRPC recently enabled retries by default on channel connections, potentially causing a storm of requests and open threads to starve the host of resources, as well as strain our trace observers. This pin should alleviate these issues until retries can be properly configured.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-70203170","eolDate":"2023-11-04"},{"agent":"python","date":"2021-10-15","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"7.2.2.169","features":[],"bugs":["Fix urllib3 recursion regression","Fix import error caused by non-ASCII character in comments"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes an issue with urllib recursion as well as an import error caused by non-ASCII characters in comments Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Bug Fixes Fix urllib3 recursion regression Urllib3 recursion regression issue that was seen in Gevent has been fixed Fix import error caused by non-ASCII character in comments An import error caused by non-ASCII characters has been fixed to the correct quotation formatting","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-70202169","eolDate":"2023-10-15"},{"agent":"python","date":"2021-10-12","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"7.2.1.168","features":[],"bugs":["Fix wheels for Python 3.10"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds a patch to correctly build wheels for Python 3.10. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Bug Fixes Fix wheels for Python 3.10 An incorrect version of cibuildwheel failed to create Python 3.10 wheels. This has been fixed and wheels should now be available.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-70201168","eolDate":"2023-10-12"},{"agent":"python","date":"2021-10-12","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"7.2.0.167","features":["Add Python 3.10 wheels","Upgrade internal urllib3 to v1.26.7"],"bugs":["Ensure errors are ignored by server-side config","Deprecation warnings for imp module removed"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds supported builds for Python 3.10 and fixes bugs. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New Features Add Python 3.10 wheels Wheels for Python 3.10 are now available and supported. Changes Upgrade internal urllib3 to v1.26.7 The internal copy of urllib3 has been upgraded to v1.26.7 to address Python 3.10 issues and deprecation warnings. Bug Fixes Ensure errors are ignored by server-side config Previously it was possible on transaction exit to have an error fail to be ignored when the settings were supplied via server-side config. This has been fixed. Deprecation warnings for imp module removed The imp module has been deprecated for some time, and has been issuing warnings. This module has been replaced with importlib when available. Older versions of Python may still require the use of imp, but no deprecation warnings should be emitted.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-70200167","eolDate":"2023-10-12"},{"agent":"python","date":"2021-09-22","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"7.0.0.166","features":["Reservoir sizes now configurable using settings and environment variables","Distributed tracing is enabled by default"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent enables Distributed Tracing by default, deprecates Cross Application Tracing. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New Features Reservoir sizes now configurable using settings and environment variables Reservoir sizes for span events, transaction events, error events, and custom events are now configurable via environment variables. These reservoirs limit both the maximum number of events that can be sent as well as local memory usage. The agent reservoir can be expanded to accommodate more spans in case more traces are needed or there are dropped spans. The default setting for event_harvest_config.harvest_limits.span_event_data has been increased from 1000 to 2000 for better performance. This variable can be increased up to a size of 10,000. These settings previously existed via config file but were undocumented. For details, see the new documentation . Deprecations Cross Application Tracing is now deprecated, and disabled by default Distributed Tracing is replacing Cross Application Tracing as the default means of tracing between services. Cross Application Tracing will soon be removed entirely with a future release. The default setting for cross_application_tracer.enabled is now False, disabling Cross Application Tracing. To continue using it temporarily while transitioning to Distributed Tracing, enable it with cross_application_tracer.enabled = True and distributed_tracing.enabled = False. Changes Distributed Tracing is enabled by default The default setting for distributed_tracing.enabled is now True, enabling Distributed Tracing by default. To disable Distributed Tracing, please set the distributed_tracing.enabled setting to False.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-70000166","eolDate":"2023-09-22"},{"agent":"python","date":"2021-02-25","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"6.2.0.156","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes new garbage collection runtime metrics as well as improved metrics for CPU and memory usage. This release also includes bug fixes for Uvicorn instrumentation and FIPS compliant systems. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Adds garbage collection runtime metrics. Records statistics as metrics after garbage collection sweeps. This feature is disabled by default and can be enabled and configured with these settings . Improved Features Improved CPU metric sampling. Adds separate metrics for user time, system time, and total time as well as utilization as a percentage for each. Improved memory metric sampling. Adds memory utilization as a percentage, and adds PID to metrics to allow faceting in NRQL queries. Increased custom attribute limit from 64 to 128. The custom attribute limit affects user added attributes on spans, events, and transactions. Bug Fixes Fixed a TypeError with Uvicorn and unix sockets. Fixed a crash when using a FIPS compliant system with Cross Agent Tracing enabled.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-620156","eolDate":"2023-02-25"},{"agent":"python","date":"2021-09-16","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"6.10.0.165","features":["Add new instrumentation for Strawberry","Add new instrumentation for Ariadne","Add new and changed metrics for Graphene applications","Improve tracing in Starlette GraphQL applications"],"bugs":["TimeTrace.**str** recursion"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds new instrumentation for the GraphQL frameworks Strawberry and Ariadne, updates to Graphene and Starlette GraphQL instrumentation, a change to logging configuration, and includes bug fixes. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New Features Add new instrumentation for Strawberry GraphQL applications built using Strawberry will now be automatically instrumented. Add new instrumentation for Ariadne GraphQL applications built using Ariadne will now be automatically instrumented. Improvements Add new and changed metrics for Graphene applications Metrics specifying the framework details for Graphene have been added, and GraphQL metrics now include Graphene as a product field. (eg. GraphQL/operation/Graphene/query/<query_name>/<query_path>) Improve tracing in Starlette GraphQL applications GraphQL applications using Starlette now support all executor classes. Previously, only async executor classes were supported. Changes New Relic agent logs no longer propagate to the root logger by default Previously, logs using the logging module sent to the newrelic logger would propagate to the root logger, potentially causing duplicate logs to appear or be sent to New Relic. This has been changed to no longer propagate to the root logger by default. To reverse this behavior, in your application you can run logging.getLogger(\"newrelic\").propagate = True at any point after initializing the agent. If you use the newrelic-admin wrapper, this can be done at any time inside your application. Bug Fixes TimeTrace.str  recursion A case of infinite recursion with TimeTrace.__str__ has been corrected in this release. Calling str(), repr() or print() on a TimeTrace object or subclass instance will now display helpful debugging information about it.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-61000165","eolDate":"2023-09-16"},{"agent":"python","date":"2021-08-24","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"6.8.1.164","features":["Update log_file location in default `newrelic.ini"],"bugs":["Handle `cherryPy.HTTPRedirects","Address DeprecationWarning for invalid escape sequence"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent updates the log file location in the default newrelic.ini file, and includes multiple bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index , or it can be downloaded directly from the New Relic download site . Improved Features Update log_file location in default newrelic.ini The newrelic.ini generated using newrelic-admin generate-config has been updated to set the default log_file location to stdout for improved initial visibility. This setting can still be customized to log to stderr or a user-specified file as well. Bug Fixes Handle cherryPy.HTTPRedirects cherrypy.HttpRedirects were incorrectly being reported as errors. This has now been corrected thanks to a contribution from @bdeeney ! Address DeprecationWarning for invalid escape sequence A deprecation warning concerning unrecognized escape sequences in Python 3.6 (and higher) has been fixed. Thank you @urianchang  for your contribution!","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-6081164","eolDate":"2023-08-24"},{"agent":"python","date":"2021-08-04","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"6.8.0.163","features":["Add wheel support for ARM64 (a.k.a. AArch 64, ARMv8)"],"bugs":["Fix a crash in unsupported GraphQL versions"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds ARM64 wheels and fixes a crash in unsupported GraphQL versions. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New Features Add wheel support for ARM64 (a.k.a. AArch 64, ARMv8) The agent now provides prebuilt wheels for ARM64 for Python versions >=3.6. This requires a version of pip>=19.3. Bug Fixes Fix a crash in unsupported GraphQL versions A crash in GraphQL could occur when using an older version not supported by our instrumentation (ie. graphql-core<2.1). This has been corrected.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-60800163","eolDate":"2023-08-04"},{"agent":"python","date":"2021-07-29","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"6.6.0.162","features":["Add support for Graphene","Add support for Graphene schemas in Starlette/FastAPI with use of an AsyncioExecutor"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds new GraphQL instrumentation support for the Graphene  library and Graphene schemas created in Starlette/ FastAPI. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Add support for Graphene Graphene applications will now be automatically instrumented. Add support for Graphene schemas in Starlette/FastAPI with use of an AsyncioExecutor Starlette/ FastAPI applications using GraphQL in conjunction with an AsyncioExecutor  will now be automatically instrumented.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-6060162","eolDate":"2023-07-29"},{"agent":"python","date":"2021-07-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"6.4.4.161","features":["Add wildcard matching to instrumentation via config file"],"bugs":["Fix a crash in memory sampling on BSD kernels"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds wildcarding to instrumentation config and fixes a crash in the memory metric sampler. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Improvements Add wildcard matching to instrumentation via config file The agent now supports wildcards for classes and functions when instrumenting via config file. Note: this does not include module paths. Bug Fixes Fix a crash in memory sampling on BSD kernels A crash in the memory metric sampler was possible when using kernels besides MacOS and Linux. This has been corrected.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-60404161","eolDate":"2023-07-06"},{"agent":"python","date":"2021-06-23","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"6.4.3.160","features":[],"bugs":["Fix Starlette/ FastAPI transaction naming and classification"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes a bug fix related to middleware and background tasks in Starlette/ FastAPI. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Fix Starlette/ FastAPI transaction naming and classification Starlette/ FastAPI routes that contained middleware and background tasks were being incorrectly classified as non-web transactions and named after the background task rather than the route. This has been corrected in this release.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-60403160","eolDate":"2023-06-23"},{"agent":"python","date":"2021-06-22","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"6.4.2.159","features":["Update Sanic instrumentation","Update Pyramid transaction naming"],"bugs":["Fix inspect.formatargspec deprecation warning","Fix HTTPX crash"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent updates Sanic instrumentation to support all available versions. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Improvements Update Sanic instrumentation The agent has updated support for all Sanic versions, with testing done on all versions >=18.12.0. Additionally, blueprint middleware is now supported. Update Pyramid transaction naming Previously, transaction names from exception views overrode route names. We've reversed this priority to be more in line with other instrumentation. Bug Fixes Fix inspect.formatargspec deprecation warning A deprecation warning concerning inspect.formatargspec has been fixed. Fix HTTPX crash Initializing the agent after creating an HTTPX client could cause a crash in HTTPX. This has been corrected.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-60402159","eolDate":"2023-06-22"},{"agent":"python","date":"2021-06-04","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"6.4.1.158","features":["Add support for Flask v2","Improve logging for 410 status codes"],"bugs":["Non-PID specific memory metric being reported","Reintroduce non-PID specific memory metrics"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Flask v2 , improves logging for HTTP exceptions, and includes a bug fix. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Add support for Flask v2 The agent will automatically instrument error handlers, nested blueprints, and async views. Improvements Improve logging for 410 status codes The agent now logs the content of a data collector response which specifies the reason for a disconnect for 410 status codes. Bug Fixes Reintroduce non-PID specific memory metrics In agent version v6.2.0.156, memory metrics were modified to add the PID to each metric name. This release reintroduces non-PID specific memory metrics.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-60401158","eolDate":"2023-06-04"},{"agent":"python","date":"2021-05-25","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"6.4.0.157","features":["Add new notice_error API","Add new expected errors feature","Improve NewRelicContextFormatter","error_collector.ignore_status_codes is now configurable in server-side configuration"],"bugs":["Fix Infinite Tracing crash","Fix RuntimeInstrumentationError crash","Fix SQLite instrumentation consuming generator objects passed to executemany"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent deprecates the old record_exception API, replaces the error_collector.ignore_errors setting, adds a new notice_error API, adds expected errors  functionality, improves the NewRelicContextFormatter, and fixes multiple bugs including a few potential crashes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Deprecations Deprecated record_exception API record_exception has been superseded by the new notice_error API. The old API will forward exceptions to notice_error with a deprecation warning. Deprecated error_collector.ignore_errors setting error_collector.ignore_errors has been replaced with error_collector.ignore_classes to match other agents. Please update your config files to use the new setting. The old setting will continue to function with a deprecation warning. New Features Added new notice_error API This new API falls much more in line with other language agents . It also includes expected errors  functionality and a status code parameter. To see all changes, view the documentation  for this API. Added new expected errors feature This feature implements expected errors  as documented here. To enable them, use the following new settings. error_collector.expected_classes error_collector.expected_status_codes Improved Features Improved NewRelicContextFormatter Adds new log_record_to_dict function to separate logic for JSON serialization and converting to a dictionary, enabling custom formatters to access the data more easily. Custom attributes now attempt JSON serialization by default and fallback to strings, meaning dictionaries and other serializable types are now supported. Thank you to @chrislawlor  and @qvik-olli  for your contributions! error_collector.ignore_status_codes is now configurable in server-side configuration Previously this setting was only available in the config file, but is now available via server-side configuration. Bug Fixes Infinite tracing crash fix Crashes had occurred in infinite tracing following the inclusion of some startup timeout changes in v6.0.0. These changes have been rolled back. RuntimeInstrumentationError crash removed Crashes occurred when a RuntimeInstrumentationError was reached, indicating a potential problem with existing instrumentation. The exception is now caught and replaced with error level log messages to avoid crashing applications. SQLite instrumentation consumes generator objects passed to executemany A generator passed to Connection.executemany would unexpectedly be consumed by our instrumentation. This has been corrected and generators are now properly supported. Known Issues Flask v2.0.0 support Flask released a new major version recently that we do not yet support, but expect to in the near future. Sanic support Sanic has released large changes to the framework recently that have broken some of our instrumentation on certain versions, and can crash the agent on others. We expect to correct these issues in the near future.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-60400157","eolDate":"2023-05-25"},{"agent":"python","date":"2021-01-21","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"6.0.1.155","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes a bug fix for httpx  instrumentation. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes httpx process response attribute error In httpx instrumentation, an attribute error was occurring during processing of the HTTP response. This issue was resolved in this release.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-601155","eolDate":"2023-01-21"},{"agent":"python","date":"2021-01-21","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"6.0.0.154","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds instrumentation for httpx , removes support for Python 3.5, and includes performance enhancements. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Deprecations Removed support for Python 3.5 Python 3.5 is no longer supported by the agent. Please consider upgrading your application to a supported version of Python in order to continue to receive updates to the Python Agent. New Features Added httpx instrumentation External web service requests made with the httpx client module will now be automatically instrumented. Added Django ASGI instrumentation Django's ASGI mode will now be supported through automatic instrumentation. Improved Features Improved startup performance The loading of urllib3 is now delayed and happens on a background thread which improves overall initialization time. Bug Fixes Non-ASCII HTTP referers crash fix Crashes had occurred when non-ASCII HTTP referers were passed to ASGI applications. This crash no longer occurs as of this release.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-600154","eolDate":"2023-01-21"},{"agent":"python","date":"2020-02-24","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.8.0.136","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes a new API for adding custom attributes on span events, improvements to external type spans, deprecations, and bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New features Add new api newrelic.agent.add_custom_span_attribute There is now a public API method allowing users to add custom attributes directly to spans. Improved features External spans now contain HTTP response code External HTTP spans will now contain a new attribute http.statusCode with the http response code for each external call made. This attribute will be added when using any supported HTTP client. Deprecations LambdaHandlerWrapper and lambda_handler APIs are deprecated The Lambda API functionality has been moved to a separate package called newrelic-lambda . All future lambda implementations should use the new package for lambda monitoring. Bug fixes Fix application crash when using a non-WSGI framework with synthetics When synthetic monitors were used with an application utilizing a non-WSGI web framework (such as aiohttp), a crash could have occurred if an outbound HTTP request was attempted from within the transaction. This crash has now been fixed. The Python agent generates an invalid nr tracestate entry Under certain random conditions, the agent may have generated an invalid New Relic w3c tracestate entry, resulting in potentially missing parts of traces. This invalid tracestate entry would not impact propagation of tracestate values from other vendors. Known issues and workarounds If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream New Relic Python agents to this agent release.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-580136","eolDate":"2023-02-24"},{"agent":"python","date":"2020-02-03","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.6.0.135","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes an implementation for w3c trace context, support for uvloop, and various bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features New APIs for creating / accepting distributed trace headers This version of the agent deprecates newrelic.agent.create_distributed_trace_payload and newrelic.agent.accept_distributed_trace_payload in favor of newrelic.agent.insert_distributed_trace_headers and newrelic.agent.accept_distributed_trace_headers. See the Python agent API documentation for details. Support for W3C Trace Context, with easy upgrade from New Relic Trace Context Distributed Tracing now supports W3C Trace Context headers for HTTP and gRPC protocols when distributed tracing is enabled. Our implementation can accept and emit both W3C trace header format and New Relic trace header format. This simplifies agent upgrades, allowing trace context to be propagated between services with older and newer releases of New Relic agents. W3C trace header format will always be accepted and emitted. New Relic trace header format will be accepted, and you can optionally disable emission of the New Relic trace header format. When distributed tracing is enabled with distributed_tracing.enabled = true, the Python agent will now accept W3C's traceparent and tracestate headers when calling accept_distributed_trace_headers. When calling insert_distributed_trace_headers, the Python agent will include the W3C headers along with the New Relic distributed tracing header, unless the New Relic trace header format is disabled using distributed_tracing.exclude_newrelic_header = true Also, see the \"Known Issues and Workarounds\" section of these Release notes. Improved Features Add support for uvloop Transaction context may not have been propagated when using uvloop. This could have resulted in incomplete traces or instrumentation failures when using uvloop. uvloop is now supported. Bug Fixes Fix crash when using aiohttp_cors Customers using the agent with aiohttp_cors may have experienced a crash when the aiohttp_cors framework was used in conjunction with aiohttp class based views. This crash has now been fixed. Fix grpc v1.26 instrumentation errors Customers using grpc v1.26 and above may have experienced an error message in the New Relic agent logs indicating there was an instrumentation error. Additionally, some data may have been missing when this error was encountered. This issue has now been fixed. Known Issues and Workarounds If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream New Relic Python agents to this agent release.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-560135","eolDate":"2023-02-03"},{"agent":"python","date":"2019-12-19","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.4.1.134","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes a bug fix for reporting inaccurate metric values. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Metrics may be reported with an incorrect throughput after communication failure with New Relic For agent versions 5.2.0 through 5.4.0, metric throughput may have been reported inaccurately after experiencing network / communication failures with New Relic. The throughput reported for all metrics after this failure may have been abnormally high.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-541134","eolDate":"2022-12-19"},{"agent":"python","date":"2019-11-26","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.4.0.132","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes the logs in context feature and bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Features Logs In Context The logs in context feature is now supported by the PythonaAgent. For more information, see the Python logs-in-context page . Bug Fixes The plugin list in the environment page may have been inaccurately reported When using absolute imports in Python 2, the agent may have reported relative imports that were attempted but unsuccessful. Python 3 is not impacted. Modules are now reported correctly in Python 2.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-540132","eolDate":"2022-11-26"},{"agent":"python","date":"2020-12-22","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.24.0.153","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes minor bug fixes. Bug Fixes Fix incorrect wrapper in grpc  instrumentation. _MultiThreadedRendezvous._next was wrapped with the instrumentation designed for _MultiThreadedRendezvous.result. This issue has been resolved as of this agent version.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5240153","eolDate":"2022-12-22"},{"agent":"python","date":"2019-11-13","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.2.3.131","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes support for Python 3.8 and restores the original record-deploy command interface. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Updates Added Support for Python 3.8 Python 3.8 support has been added in this release. Restore newrelic-admin record-deploy command interface The newrelic-admin command was previously updated to require an application id via the command line. The requirement has been removed, restoring the original record-deploy CLI arguments.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-523131","eolDate":"2022-11-13"},{"agent":"python","date":"2019-11-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.2.2.130","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Fix thread utilization data on agent versions v5.x.x Thread utilization data was not reported for agents v5.x.x, resulting in missing data on the capacity analysis page. The agent will now report thread utilization data. Fix untraced database calls when using pymysql context manager assignments When using context managers to create and assign a cursor in pymysql, database calls on that cursor object were not traced. Database calls in pymysql are now properly traced.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-522130","eolDate":"2022-11-06"},{"agent":"python","date":"2020-10-28","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.22.1.152","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent updates transaction naming for Starlette  and FastAPI , and includes bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Improved Features Updated transaction naming for middleware in Starlette and FastAPI The transaction naming hierarchy has been updated for Starlette and FastAPI applications. The web transaction name is named after the route handler, or after middleware if an exception is raised in the middleware. Bug Fixes RuntimeError for imports occurring on a background thread A RunTimeError was being raised in the event of imports occurring on a background thread during iteration over sys.modules. This issue has been resolved in this agent version. Fixed region aware license key default host setting This agent version contains a fix for setting the default host value based on the license key for EU license keys. Setting the host manually will still override the default host value set by the license key.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5221152","eolDate":"2022-10-28"},{"agent":"python","date":"2020-10-22","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.22.0.151","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds instrumentation for Starlette  and FastAPI . The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Deprecations Python 3.5 has been deprecated Python 3.5 has reached end of life  and support will be dropped in a future release. Using the agent with Python 3.5 will generate a deprecation warning. Updating Python versions is recommended. New Features Adds Starlette framework instrumentation Starlette applications will now be automatically instrumented. Transaction data will be collected and recorded for application routes, background tasks, exception handlers, and installed middleware. Exception logging has also been added. Adds FastAPI framework instrumentation FASTAPI applications will also now be automatically instrumented. See above for instrumentation details. Bug Fixes Fix deprecation warning for find_loader in python 3 Using the agent no longer generates a deprecation warning for find_loader. The call to find_loader has been replaced with find_spec.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5220151","eolDate":"2022-10-22"},{"agent":"python","date":"2019-10-09","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.2.1.129","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Fix a crash when using future-based interfaces on Tornado's http client Tornado's http client returns a future when fetch is called. Prior to this release, the agent caused a coroutine object to be returned rather than a future, causing a potential crash when application code assumed a future would be returned. A future will now be returned from http client fetch as expected. Fix a crash when running a coroutine created in another transaction When running a coroutine outside of the transaction that created it, the agent may have crashed if a separate transaction was active.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-521129","eolDate":"2022-10-09"},{"agent":"python","date":"2019-10-01","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.2.0.127","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes a bug fix for tornado and support for recording deployment markers in the EU region as well as specifying a deploy timestamp. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Features Support for Real Time Streaming Event data is now sent to New Relic every five seconds, instead of every minute. As a result, transaction, error, and custom events will now be available in New Relic and Insights dashboards in near real time. For more information on how to view your events with a five-second refresh, see the real time streaming documentation . Note that the overall limits on how many events can be sent per minute have not changed. Also, span events, metrics, and trace data is unaffected, and will still be sent every minute. Added timestamp and EU region support for recording deployment markers When using the newrelic-admin record-deploy script an optional timestamp can be provided to specify when the deployment marker should be created. Furthermore support for accounts in the EU region have been added in this release. Bug Fixes Fixed a crash in tornado versions >= 6.1 Tornado 6.1 internals changed in a way that may have caused the agent's built-in instrumentation to fail. The instrumentation has been updated to alleviate this issue.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-520127","eolDate":"2022-10-01"},{"agent":"python","date":"2020-10-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.20.1.150","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Python 3.9 and includes bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Duplicate warnings were logged repeatedly when using the agent with Python 3 The agent internally suppressed any warnings generated when data was sent via HTTP to New Relic in a way that caused the warning filters to mutate. This caused the cache of already printed warnings to be cleared, resulting in duplicate warnings after every data harvest. The agent no longer mutates the process warning filters on a background thread, resulting in consistent warning behavior. AttributeError when passing an inactive transaction into ExternalTrace.generate_request_headers When passing an inactive transaction into ExternalTrace.generate_request_headers, an AttributeError was generated. This agent version contains additional validation for the transaction argument in ExternalTrace.generate_request_headers. The infinite tracing host configuration value did not have sufficient validation When passing a URL or other invalid host to the infinite tracing host configuration, the agent accepted this value unchecked to use in the host parameter for later connections via grpc. The agent now validates this configuration and attempts to correct for invalid hosts if it is able to detect the host. If a host is not detected, the agent automatically falls back to infinite tracing disabled and logs an error.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5201150","eolDate":"2022-10-06"},{"agent":"python","date":"2020-09-21","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.20.0.149","features":["Add uvicorn instrumentation","Add asyncpg instrumentation","Add db.operation attribute"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds instrumentation for uvicorn  and asyncpg . The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Adds uvicorn instrumentation ASGI applications are now automatically wrapped when using the uvicorn ASGI server. Adds asyncpg instrumentation Support has been added for recording database transactions when using asyncpg database client module for PostgresSQL. Improved Features Adds db.operation attribute A new attribute, db.operation, was introduced for datastore traces. This value is recorded only when db.statement is not reported, and represents an operation triggered by methods other than running a DB statement.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5200149","eolDate":"2023-09-21"},{"agent":"python","date":"2020-08-31","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.18.0.148","features":["Add support for ASGI applications via built-in APIs"],"bugs":[],"security":["Upgrade wrapt to 1.12.1"],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds new ASGI apis and upgrades wrapt. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Adds support for ASGI applications via built in APIs ASGI applications can now be timed via middleware-like API calls. Browser monitoring JS is automatically injected into HTML pages by the ASGI browser monitoring middleware for instrumented applications. See the asgi_application docs for details on API usage. Upgrades wrapt to 1.12.1 This version of the agent ships with wrapt 1.12.1.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5180148","eolDate":"2023-08-31"},{"agent":"python","date":"2020-08-24","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.16.2.147","features":[],"bugs":["Fix invalid payloads generated when using serverless mode"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug fixes Fix invalid payloads generated when using serverless mode When using serverless mode on the Python Agent versions v5.16.0 and v5.16.1, invalid serverless/lambda payloads were generated. The agent now generates the proper payloads in serverless mode.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5162147","eolDate":"2023-08-24"},{"agent":"python","date":"2020-08-17","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.16.1.146","features":[],"bugs":["Fix data erroneously discarded when an HTTP protocol error occurred","Fix error when installing with an incompatible setuptools_scm version"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent introduces manylinux wheels and includes bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug fixes Data was erroneously discarded when an HTTP protocol error occurred When an unexpected HTTP error occurred (such as a timeout), data was erroneously discarded. Data is now downsampled and retransmitted when an HTTP protocol error occurs. Error when installing with an incompatible setuptools_scm version The version requirements were not correctly set for the setuptools_scm build time requirement, which may have resulted in an error at installation. The version requirements for setuptools_scm are now set appropriately.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5161146","eolDate":"2023-08-17"},{"agent":"python","date":"2020-08-10","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.16.0.145","features":["The NewRelicContextFormatter now records extras","The agent now internally uses urllib3"],"bugs":["Fix gRPC application crash when credentials are supplied","Fix Tornado framework crashes when finish is called from a different task"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent changes the internal http client from requests to urllib3, updates logging, and includes bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Improved Features The NewRelicContextFormatter now records extras When using the NewRelicContextFormatter log formatter, extras are now automatically captured and recorded in the New Relic agent logs product. The agent now internally uses urllib3 The python agent previously used requests as its http client. The agent now uses urllib3 internally for HTTP communication with New Relic data ingest services. Bug fixes Fix gRPC application crash when credentials are supplied When using the credentials argument, the agent's built in gRPC instrumentation caused an application crash. This crash has been fixed. Fix Tornado framework crashes when finish is called from a different task When finish is called from a different task, applications using the Tornado framework may crash. This crash has been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5160145","eolDate":"2023-08-10"},{"agent":"python","date":"2020-06-18","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.14.1.144","features":[],"bugs":["Fix applications failing to start when using newrelic-admin run-program on Python 2.7 applications"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes a bug fix. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug fixes When using newrelic-admin run-program on Python 2.7 applications failed to start Using the newrelic-admin run-program on Python 2.7 with the 5.14.0 agent resulted in an application crash. Applications now start as expected on Python 2.7.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5141144","eolDate":"2023-06-18"},{"agent":"python","date":"2020-06-02","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.14.0.142","features":["Add new span attribute transaction.name","Transaction attributes are now added to the root span","Custom attributes are now added to the root span","Error attributes are now added to each span/segment"],"bugs":["Fix asyncio application crash when a transaction that started on a completed parent task exits","Error attributes are no longer added if the error collector is disabled"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes improvements to distributed tracing, and bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Add new span attribute transaction.name A new attribute, transaction.name, has been added to the root span. Improved features Transaction attributes are added to the root span Transaction attributes, including response attributes, are now added to the root span. Custom attributes are added to the root span The public API methods newrelic.agent.add_custom_param and newrelic.agent.add_custom_params now add the specified custom attribute to the root span in addition to the transaction. If the maximum number of custom attributes is reached, span-level custom attributes take precedence over transaction-level custom attributes. Error attributes added to each span/segment Error attributes error.class and error.message to all spans that exit without handling an exception. Bug fixes asyncio: application crash when a transaction that started on a completed parent task exits When a transaction that started on a completed parent task exited, an exception was raised. This error has been fixed. Error attributes are no longer added if the error collector is disabled If the error collector is disabled via error_collector.enabled, error attributes error.class and error.message are not added to the currently executing span. Security Updates Note that changes were made that add attributes to the root span. Transaction-level attribute filtering via the transaction.attribute.exclude configuration setting will not filter the attribute(s) for the root span. Those attributes may unexpectedly start to appear on the root span.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5140142","eolDate":"2023-06-02"},{"agent":"python","date":"2020-05-04","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.12.1.141","features":[],"bugs":["Fix AIOHTTP http client urls displayed as unknown.url when using YARL URLs","Fix data not being recorded when using tornado's RequestHandler.finish","Fix asyncio.ensure_future / asyncio.create_task being unable to spawn new transactions","Fix a runtime instrumentation error occurring when transactions were finalized on Python 3","Fix application crash when starting a transaction when one is already active","Fix a crash when creating a message transaction with distributed tracing enabled"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug fixes AIOHTTP http client urls displayed as unknown.url when using YARL URLs When passing a YARL url object to the aiohttp client, the agent did not properly parse this URL, resulting in unknown.url being displayed in the UI. The URL is now parsed correctly in both the YARL url case and the string url case. Data may not be recorded when tornado's RequestHandler.finish Using RequestHandler.finish in tornado caused the transaction to exit before all traces (inserted by automatic instrumentation) were complete, resulting in missing data. All traces now exit when RequestHandler.finish is called. asyncio.ensure_future / asyncio.create_task is unable to spawn new transactions Calling asyncio.create_task / asyncio.ensure_future was unable to spawn a new transaction if these methods were called from within an existing transaction. New transactions can now be created when ensure_future/create_task is called from within an existing transaction and no traces have been started on the spawned task. py3: A runtime instrumentation error may have occurred when transactions were finalized When transactions became garbage (if the reference to the transaction was lost as part of a circular reference for example), a runtime instrumentation error may have been logged. The error conditions have been relaxed to allow for certain states within the agent when a transaction becomes garbage. Application crash when starting a transaction when one is already active Starting a transaction via the context manager APIs when a transaction is already active no longer causes an application crash. An error is logged when this case is detected. Creating a message transaction with distributed tracing enabled may have resulted in a crash The agent crashed with an AttributeError when using message transactions with distributed tracing enabled when headers were not provided. This error has been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5121141","eolDate":"2023-05-04"},{"agent":"python","date":"2020-04-13","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.12.0.140","features":["Adds a new product called Infinite Tracing"],"bugs":["Fix record transaction failure in async applications"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes support for a new product called Infinite Tracing, and it also has some bug fixes The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Feature This release adds support for Infinite Tracing . Infinite Tracing observes 100% of your distributed traces and provides visualizations for the most actionable data. With Infinite Tracing, you get examples of errors and long-running traces so you can better diagnose and troubleshoot your systems. Configure your agent to send traces to a trace observer in New Relic Edge. View distributed traces through New Relic’s UI. There is no need to install a collector on your network. Infinite Tracing is currently available on a sign-up basis. If you would like to participate, please contact your sales representative. Bug fixes Fix record transaction failure in async applications When the agent attempted to record information as part of event loop diagnostics, an AttributeError may have occurred during the record transaction phase causing data to not be recorded for that transaction. This issue has now been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5120140","eolDate":"2023-04-13"},{"agent":"python","date":"2020-03-09","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.10.0.138","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes an update to the API for recording exceptions, default request attributes, optional function trace attributes, and bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Improved features newrelic.agent.record_exception now adds attributes to spans The public API method newrelic.agent.record_exception now attaches exception details to the currently executing span. Spans with error details are now highlighted red in the distributed tracing UI. Also, the attributes error.class and error.message are added to the span. If multiple errors are recorded for a single span, only the final error's attributes will be added to the span. Note: Exceptions recorded on spans may be double counted in the distributed tracing UI. New default web request attributes. The previously optional attributes request.headers.accept, request.headers.host, and request.headers.userAgent are now included by default on all web transactions. These attributes can be excluded through agent configuration . peer.address and peer.hostname can now be excluded from spans through configuration peer.address and peer.hostname may be excluded from span events through attribute.exclude options in the agent configuration . Bug fixes Fix issue which could potentially lead to missing event data When the agent was shutting down, event harvest may have been skipped causing any events captured in the final 5 seconds of application execution to be discarded. This has now been fixed. Runtime instrumentation error messages for calling __exit__ before __enter__ were erroneously logged Under certain conditions, the agent may have logged an error message for transaction __exit__ being called before trace __enter__. This error message is now printed only if the error condition is true. Known issues and workarounds If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream New Relic Python agents to this agent release.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-5100138","eolDate":"2023-03-09"},{"agent":"python","date":"2019-08-12","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.0.2.126","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes bug fixes for feedparser and django-piston. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Fixed a crash when using feedparser When running with the feedparser library the agent would crash on attempting to parse an RSS feed. This issue has now been corrected. Fixed a crash when using django-piston When running with the django-piston library the agent would crash on attempting to service a request. This issue has now been corrected.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-502126","eolDate":"2022-08-12"},{"agent":"python","date":"2019-08-09","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.0.1.125","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes a bug fix for the mako library instrumentation. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Fixed a crash when using the Mako template library When running with the Mako template library the agent would crash on attempting to render a template. This issue has now been corrected.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-501125","eolDate":"2022-08-09"},{"agent":"python","date":"2019-08-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"5.0.0.124","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent introduces: Event loop diagnostics feature Tornado instrumentation for versions 6 or higher Improved context manager API functionality and interfaces This release also drops support for Python 3.4. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Event loop diagnostics Introducing event loop diagnostics for asyncio! The Python agent can now surface information about transactions that block the event loop. The agent will be able to generate information about transactions that have waited a significant amount of time to acquire control of the event loop. Event loop diagnostic information will be available in both APM and via NRQL query. Event loop metrics will appear in the transaction Breakdown table : Time spent waiting on other transactions will be shown in the transaction Trace details  page, as shown here: eventLoopTime and eventLoopWait attributes will be available via NRQL query. An example query might be:SELECT count(*) as 'count', average(eventLoopTime) as 'loopTime', average(eventLoopWait) as 'loopWait' FROM Transaction facet name In New Relic Insights, this might show a result like this: Diagnostics will be available by default through our existing aiohttp, sanic, and Tornado instrumentation. Diagnostic information will also be available for coroutines that use our background_task and web_transaction decorator APIs. Tornado 6 Instrumentation Instrumentation for Tornado framework version 6.x is supported without any feature flags. Support for versions earlier than Tornado 6.x has been dropped. The Tornado web server, framework, and http client are instrumented and information will show up in both APM and insights. Important:  Using the tornado.gen.coroutine with instrumentation is not supported. Any usage of tornado.gen.coroutine should be replaced with an asyncio coroutine. Before After Improved APIs for time trace context managers Context managers (such as FunctionTrace, ExternalTrace, DatastoreTrace) may now be used from within asyncio coroutines! Additionally, the transaction argument is no longer used for any context manager API. In order to transition to the new API, the transaction argument must be removed . Before After Updated WebTransaction context manager The WebTransaction context manager is no longer WSGI dependent. The context manager takes generic HTTP arguments, which you can use to build web transactions that appear in the APM product. For more information, see our API documentation .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-500124","eolDate":"2022-08-06"},{"agent":"python","date":"2018-12-03","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.8.0.110","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Falcon framework, and includes various bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Features Add support for Falcon web framework This release adds support for the Falcon web framework. Data will now be automatically collected for applications using Falcon framework. The data will appear in both APM and Insights and will include performance details as well as information on application errors. Bug Fixes \"newrelic-admin record_deploy\" now functions with proxies. The newrelic-admin record_deploy command previously did not function when a proxy was defined by the newrelic.ini configuration file or the `NEW_RELIC_PROXY_*` environment variables. This bug has now been fixed. Cross Application Tracing HTTP response headers were inserted on a 304 response When cross application tracing is enabled and the agent received a HTTP request from an application utilizing cross application tracing, the agent may have inserted additional response headers on a 304 HTTP response. The agent will no longer insert headers on a 304 response.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-480110","eolDate":"2021-12-03"},{"agent":"python","date":"2018-11-12","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.6.0.106","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes changes to the agent to enable monitoring of Lambda functions, improves the built-in Sanic instrumentation, and includes various bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Features Monitoring of Lambda functions This release includes changes to the agent to enable monitoring of Lambda functions. If you are interested in learning more or previewing New Relic Lambda monitoring please email lambda_preview@newrelic.com . Improve naming of Sanic HTTPMethodView view handlers Sanic views that were defined using the HTTPMethodView class were previously all named HTTPMethodView.as_view.<locals>.view regardless of the actual class in use. The agent will now name transactions after the actual view handler class. Bug Fixes Fix ignored error reporting in CherryPy instrumention When missing query parameters, unexpected query parameters, unexpected positional arguments, or duplicate arguments were present in the CherryPy framework, a TypeError exception was recorded even when an ignored response status code (such as a 404) was generated. An error is no longer recorded when it results in the generation of an ignored status code. Excluding request.uri from transaction trace attributes hides it in the UI When request.uri is added to either attributes.exclude or transaction_tracer.attributes.exclude, the value will now no longer be sent to New Relic. Ability to disable sending request.uri as part of error traces When request.uri is added to either attributes.exclude or error_collector.attributes.exclude, the value will now no longer be sent to New Relic. Fix tracing of functions returning generators When tracing generators whose parent traces have ended an error was seen in the logs \"Transaction ended but current_node is not Sentinel.\" This has now been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-460106","eolDate":"2021-11-12"},{"agent":"python","date":"2018-09-24","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.4.1.104","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent contains bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes The creation of sampled events sometimes raised an exception in Python 3 When more events (Transaction, Transaction Error, Custom, or Span) were created than allowed per harvest period in Python 3, sometimes a TypeError: '<' not supported between instances of 'dict' and 'dict' was raised. This issue has now been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-441104","eolDate":"2021-09-24"},{"agent":"python","date":"2018-09-11","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.4.0.103","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent introduces instrumentation for Sanic, and contains bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Features Add instrumentation for Sanic framework Data is now automatically collected for applications using the Sanic framework. Data for Sanic applications will appear in both APM and Insights. Additionally, cross application tracing and distributed tracing is supported for incoming requests for Sanic applications. In addition to service maps, Sanic applications will now show the calling application in transaction traces. See the instrumented packages page  for more details. Bug Fixes Explain plans were not generated when using psycopg2 named cursors When using named cursors in psycopg2, the agent attempted to generate an explain plan using the same named cursor. This resulted in a syntax error when the query was issued to the database. When using the default connection and cursor factories, the agent will now execute the explain query using only unnamed cursors. Convert bytes-like SQL statements to strings before obfuscating If a bytes-like object is used instead of a string when making a SQL call, a traceback was seen in the logs with TypeError: cannot use a string pattern on a bytes-like object. This issue has now been fixed. Save settings to MessageTrace objects If an external call using an instrumented http external library (for example requests) was used within a MessageTrace, a traceback was seen in the logs with AttributeError: 'MessageTrace' object has no attribute 'settings'. This issue has now been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-440103","eolDate":"2021-09-11"},{"agent":"python","date":"2019-06-24","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.20.1.121","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes bug fixes, deprecations, and improved naming behavior for gRPC. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Feature Enhancements Improved gRPC support The external and transaction pages now show the gRPC method being called in addition to the host and port. Ability to disable sending db.statement as part of traces When db.statement is added to either attributes.exclude or transaction_segments.attributes.exclude, the value will now no longer be sent to New Relic as part of transaction traces or spans. Deprecations TransactionContext API is now deprecated The TransactionContext API will be removed in a future release. Tornado instrumentation + feature flag deprecation The existing introductory support for Tornado and feature flags will be removed from a future release. Versions 6.x and newer will be the only versions of Tornado supported in future releases. See this discussion  on the New Relic forums for more details. Bug Fixes Fixed a crash when using uvicorn workers with gunicorn When running ASGI applications with gunicorn, the agent would attempt to instrument the application as a WSGI application, resulting in a crash. The agent will no longer attempt to instrument gunicorn applications that are coroutines. Remove logging of license keys The agent logged license keys when data failed to send to New Relic. The agent will no longer log license keys to the agent logs under any circumstance. Fix operation of distributed tracing and cross application tracing when httplib connections are reused When making multiple requests via a single connection with httplib, httplib2, or urllib3, the proper headers will be added to each outgoing request. As a result, cross application tracing and distributed tracing will now operate as expected when reusing connection objects.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-4201121","eolDate":"2022-06-24"},{"agent":"python","date":"2018-07-31","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.2.0.100","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent introduces distributed tracing, adds improvement to our Pyramid instrumentation, adds support for custom CA bundles, and contains bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Features Distributed tracing support Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before. Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide  before you enable this feature. To enable distributed tracing, add distributed_tracing.enabled = true to your newrelic.ini file or use the environment variable NEW_RELIC_DISTRIBUTED_TRACING_ENABLED=true. Add support for tracing Pyramid tweens Pyramid tweens  are now automatically timed and added to the transaction detail view. The time spent in a Pyramid tween will be displayed in the transaction breakdown table and in the trace details of a transaction trace. Provide configuration option for custom CA bundle Customers can now use the ca_bundle_path configuration option or set the NEW_RELIC_CA_BUNDLE_PATH environment variable to set the path to a local CA bundle. This CA bundle will be used to validate the SSL certificate presented by New Relic's data collection service. Bug Fixes Custom Insights event data attached to transactions in excess of 100 events were omitted The agent may have failed to send custom event data (record_custom_event) to insights when recorded as part of a Transaction containing over 100 custom events. This issue has now been corrected.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-420100","eolDate":"2021-07-31"},{"agent":"python","date":"2019-05-22","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.20.0.120","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes bug fixes and adds new API methods to retrieve the current trace ID and current span ID. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Features Added a new API to retrieve the current trace ID Retrieving the current trace ID can now be accomplished with a call to newrelic.agent.current_trace_id(). This method will return the id of the current trace, or None if no transaction is in progress. Added a new API to retrieve the current span ID Retrieving the current span ID can now be accomplished with a call to newrelic.agent.current_span_id(). This method will return the id of the current span, or None if no span is in progress. Bug Fixes Exclusive time incorrectly displayed when using concurrent asyncio The New Relic UI may have shown times equaling greater than 100 percent of the total time when executing concurrent tasks in asyncio. The exclusive times reported by the agent will now be correctly displayed in APM and insights.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-4200120","eolDate":"2022-05-22"},{"agent":"python","date":"2019-04-17","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.18.0.118","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds improvements to the gRPC instrumentation package and includes bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Features Improved gRPC support Support for measuring inbound gRPC requests has now been added. Inbound gRPC requests will now show as web transactions in APM. Additionally, distributed tracing is now supported as part of the gRPC instrumentation package. Bug Fixes Update pika instrumentation to support the 1.x releases When using the agent with pika versions 1.x and up, the agent may have caused an application crash. The agent now correctly collects data on newer versions of pika. The startup_timeout setting may not have been honored in a multithreaded application When startup_timeout is set to a number greater than 0, the servicing of transactions is blocked until the agent has fully activated. In multithreaded applications, only the first thread would block due to improper locking. The agent will now block on all threads.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-4180118","eolDate":"2022-04-17"},{"agent":"python","date":"2019-03-29","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.16.1.117","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes a memory leak that occurs on Python 2 when monitoring WSGI applications. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Fix memory leak on Python 2 WSGI applications When using the 4.16.0 agent on Python 2 to monitor WSGI applications, the agent would cause memory to be allocated on each request. On Python 2, this memory was never deallocated due to a reference cycle. This has now been corrected.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-4161117","eolDate":"2022-03-29"},{"agent":"python","date":"2019-03-25","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.16.0.116","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for native coroutines and generators with a new web_transaction API, as well as bugfixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Features Add a new web_transaction API This method is now exposed both as a public API through newrelic.agent.api.wrap_web_transaction, and as a decorator with newrelic.agent.api.web_transaction. It can be used to instrument non-WSGI web transactions. For usage of this API see https://docs.newrelic.com/docs/agents/python-agent/python-agent-api/webt... Bug Fixes The presence of unicode values in a SQL query on Python 2 may cause an application crash The agent was not properly handling unicode values when recording SQL queries in Python 2. As a result, the presence of unicode values in SQL queries in Python 2 applications may have resulted in an application crash. Unicode values in Python 2 SQL queries are now properly handled. The Python Agent may have improperly biased the random sampling of distributed traces Distributed traces are randomly sampled across services. The agent is responsible for propagating the state of its sampling decision to other services. In propagating that decision, an improper sampling bias may have been introduced in downstream services. The agent will no longer report the command arguments used to start newrelic-admin The agent previously reported the startup command and arguments when using newrelic-admin run-program and newrelic-admin run-python. The command and arguments are no longer sent to New Relic. This data may continue to be logged to the agent log files when debug level logs are enabled.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-4160116","eolDate":"2022-03-25"},{"agent":"python","date":"2019-02-13","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.14.0.115","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for native coroutines and generators with the background task API and adds support for Kubernetes detection. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Features @background_task can now be used with coroutines The background_task decorator API can now be used with native coroutines and generators. Add support for collection of Kubernetes metadata The agent will now collect environment variables prefixed by NEW_RELIC_METADATA_ as additional metadata. Some of this metadata may be added to Transaction events to provide context between your Kubernetes cluster and your services. For details on the benefits (currently in beta) see this blog post . The agent now also collects the KUBERNETES_SERVICE_HOST environment variable to detect when the application is running on Kubernetes. The data is used to link the application to the host machine when using the New Relic infrastructure product. Bug Fixes Using time trace decorators allowed coroutines to become Iterables and generators to become awaitables When using time trace decorators native coroutines were converted to iterables. Additionally generators were converted to awaitables. The behavior of generators, native coroutines, and awaitable generators is now unchanged when using time trace decorators.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-4140115","eolDate":"2022-02-13"},{"agent":"python","date":"2019-01-22","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.12.0.113","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent extends support of Amazon's boto3  library and includes bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Features AWS operation and request ID will now be reported in transaction traces and spans when using boto3 and botocore. The agent will now report aws.requestId and aws.operation for all calls to AWS made using botocore and boto3. DynamoDB calls are now reported under the Databases tab. The agent will now record DynamoDB query performance in the Databases tab in APM in addition to table name for the following calls: put_item get_item update_item delete_item create_table delete_table query scan Certain SQS calls will now report additional data for spans and transaction traces. The agent will now record the queue name in spans and transaction traces for the following SQS calls: send_message send_message_batch receive_message SNS publish will now report additional data for spans and transaction traces. The SNS topic, target, or the string literal PhoneNumber will be reported to New Relic inside of spans and transaction traces. The full URL path will now be recorded on span events and transaction traces when using boto3 or botocore. The agent will now record the full URL path for API calls made to AWS through the boto3 / botocore libraries. The path will be available through span events and transaction traces. Bug Fixes Using newrelic-admin to start a GunicornWebWorker with an aiohttp application factory resulted in an application crash. The agent would fail to start if using the newrelic-admin command to start an aiohttp application factory with GunicornWebWorker. This issue has now been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-4120113","eolDate":"2022-01-22"},{"agent":"python","date":"2019-01-10","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.10.0.112","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for excluding attributes from span events and transaction trace segments, adds a new api called add_custom_parameters, and includes various bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Features Add ability to exclude attributes from span events and transaction trace segments This release adds support to exclude attributes (such as http.url) from span events (via the span_events.include/span_events.exclude options) and from transaction segments (via the transaction_segments.include/transaction_segments.exclude option). As with other attribute destinations, these new options will inherit values from the top-level attributes.include/attributes.exclude settings. See the documentation for more information. Add public add_custom_parameters API The method add_custom_parameters on Transaction is now exposed through newrelic.agent.add_custom_parameters Bug Fixes Transaction counts were not reported for aiohttp's built-in error pages When a built-in error route was reached in aiohttp (such as a 404 due to a missing route), transactions were not recorded. As a result, the transaction counts may have been artificially low. aiohttp system route traffic will now be reported. aiohttp cross application tracing linking to non-Python applications may have been omitted if using multidict<3.0 For aiohttp users using multidict versions less than 3.0, cross application tracing HTTP headers may have been generated in a way that was incompatible with non-Python applications. Headers are now generated in a format compatible with all New Relic agents. aiohttp 3.5.x versions generated agent instrumentation errors The agent previously failed to instrument aiohttp applications running versions 3.5.0 and greater. The agent now supports aiohttp versions up to 3.5.1.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-4100112","eolDate":"2022-01-10"},{"agent":"python","date":"2018-07-23","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"4.0.0.99","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent removes previously deprecated APIs, and removes support for Python 2.6 and Python 3.3. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Deprecations Removed previously deprecated APIs The following APIs have been removed: Transaction.add_user_attribute (use Transaction.add_custom_parameter) Transaction.add_user_attributes (use Transaction.add_custom_parameters) wrap_callable (use FunctionWrapper) Removed support for Python 2.6 and Python 3.3 Python 2.6 and Python 3.3 are no longer supported. Please consider upgrading your application to a supported version of Python in order to continue to receive updates to the Python Agent.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-40099","eolDate":"2021-07-23"},{"agent":"python","date":"2018-07-12","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"3.4.0.95","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Python 3.7 and contains various bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Support Python 3.7 The New Relic Python Agent now supports Python 3.7. Bug Fixes Agent raises a KeyError: 'NEW_RELIC_ADMIN_COMMAND' exception causing a crash Under certain conditions, using the newrelic-admin wrapper script could cause an application to crash shortly after startup with a KeyError exception. The cause of the crash has been addressed. Agent raises an AttributeError on Python 3 when using WSGI overrides with multiple app names When using WSGI environ overrides to specify multiple app names as described in the docs https://docs.newrelic.com/docs/agents/manage-apm-agents/app-naming/use-m...  the agent will raise an AttributeError. This error has been corrected. Agent raises an AttributeError exception under rare conditions when halting a trace Under certain rare conditions, the agent might raise an exception when trying to trace an external call in a transaction that has been forcibly halted. The cause of the exception has been addressed. Agent raises a RuntimeError exception under particular conditions when using the Tornado r3 instrumentation When attempting to yield many times from a wrapped tornado.gen.coroutine when using Tornado's r3 instrumentation, a RuntimeError due to hitting the maximum recursion limit can occur. The cause of this exception has been patched.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-34095","eolDate":"2021-07-12"},{"agent":"python","date":"2018-06-11","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"3.2.2.94","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent contains various bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Improved handling of celery max-tasks-per-child Data recorded by the Python Agent may not have been reported when celery was operated with the max-tasks-per-child setting. All data is now reported independent of the max tasks per child setting. Improve support for PyMongo v3.x PyMongo v3 added many new methods on the pymongo.Collection object that did not exist in v2. These methods have now been instrumented. Calls to these methods will now appear in APM. Scheduling tasks that run after a transaction ends causes an error Coroutines scheduled to execute after a transaction ends using create_task or ensure_future may have caused the runtime instrumentation error and subsequent crash: Coroutines that execute beyond the end of a transaction will no longer cause an error.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-32294","eolDate":"2021-06-11"},{"agent":"python","date":"2018-05-16","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"3.2.1.93","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent contains various bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Do not run explain plans for psycopg2 connections using the async_ kwarg As \"async\" is now a keyword in Python 3.7, psycopg2 now allows \"async_\" as an alias for its \"async\" kwarg for psycopg2.connect as of psycopg2 v2.7.4. Previously, explain plans were attempted for these connections and a traceback would be seen in the logs. This has now been fixed. Fix traceback when using callbacks as partials in pika consumers When passing a callback that is a functools partial to pika channel consumers, a traceback occurred in some instances. This issue has now been fixed. cx_Oracle database calls that use SessionPool objects were not recorded When using the cx_Oracle SessionPool interace, database transactions made through the acquired pool connection may not have been reported. Database transactions that using connections generated by SessionPool are now reported as expected. SQL targets for call statements may contain a period For a SQL command like CALL foo.bar(:baz), APM would show metrics under the target name foo instead of the full name foo.bar. This has been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-32193","eolDate":"2021-05-16"},{"agent":"python","date":"2018-04-04","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"3.2.0.91","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds the request.uri attribute  on transaction events in insights, adds built-in cheroot instrumentation, adds support for recording flask-restful/flask-restplus exceptions, and contains bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Improved Features Add request.uri attribute to transaction and error events The Python agent will now report request.uri as an attribute on transaction events and error events. To disable this feature, add request.uri to the attributes.exclude list in the newrelic.ini configuration file. Record Flask RESTful and Flask RestPlus exceptions Since Flask RESTful  and Flask RestPlus  handle all errors that are raised in their handlers, these errors were not being captured by the normal Flask instrumentation in the Python agent. Exception handling has now been added for these two components. Add instrumentation hooks for the Cheroot WSGI server Any customers using Cheroot  with an unsupported application framework will now see data reported in New Relic APM. Bug Fixes Fix CherryPy ignore by status code for exceptions using reason phrases CherryPy accepts string values for HTTPError status (reason phrases). When creating HTTPError exceptions in this way, responses were not properly ignored by status code. Responses generated by HTTPError exceptions using reason phrases are now properly ignored. Using send_file with Flask Compress middleware may have caused an application crash When using browser monitoring auto instrumentation on an application using Flask Compress, the use of the Flask send_file helper to send html files resulted in an application crash. This issue has now been resolved. Fix incorrect parenting for traces of coroutines scheduled with asyncio gather/ensure_future Coroutines scheduled with asyncio gather/ensure_future may have been reported as being a child of the wrong function. This issue has now been corrected.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-32091","eolDate":"2021-04-04"},{"agent":"python","date":"2018-03-14","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"3.0.0.89","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent removes previously deprecated APIs, makes SSL communication with New Relic mandatory, and updates support for aiohttp middleware. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Deprecations Removed previously deprecated APIs The following APIs have been removed: transaction (use current_transaction) name_transaction (use set_transaction_name) Application.record_metric (use Application.record_custom_metric) Application.record_metrics (use Application.record_custom_metrics) Transaction.notice_error (use Transaction.record_exception) Transaction.record_metric (use Transaction.record_custom_metric) Transaction.name_transaction (use Transaction.set_transaction_name) Deprecate Transaction.add_user_attribute Transaction.add_user_attribute has been deprecated in favor of Transaction.add_custom_parameter. Transaction.add_user_attribute will be removed in a future release. Deprecate Transaction.add_user_attributes Transaction.add_user_attributes has been deprecated in favor of Transaction.add_custom_parameters. Transaction.add_user_attributes will be removed in a future release. Deprecate wrap_callable wrap_callable has been deprecated in favor of FunctionWrapper. wrap_callable will be removed in a future release. Remove data-source admin command The platform API (used by newrelic-admin data-source) has been removed. Please use data sources  in place of the platform API. SSL SSL connections to New Relic are now mandatory Prior to this version, using an SSL connection to New Relic was the default behavior. SSL connections are now enforced (not overrideable). AIOHTTP Updates Add automatic tracing of AIOHTTP 3 middleware In addition to the old-style middleware previously supported, the AIOHTTP 3 style middleware is now automatically traced as part of the AIOHTTP instrumentation package.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-30089","eolDate":"2021-03-14"},{"agent":"python","date":"2017-11-30","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.98.0.81","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds improvements to django instrumentation, improvements to django rest framework instrumentation, and various bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Improved Features Enabled reporting of handled exceptions in Django REST Framework Exceptions handled by django rest framework are now reported if the resulting response code is not ignored (see ignore_status_codes  for details). Add support for the error_collector.ignore_status_codes setting in Django Ignoring exceptions in Django was previously limited to the error_collector.ignore_errors configuration option. Ignoring exceptions by response status code is now supported for Django through the use of the error_collector.ignore_status_codes configuration option. Bug Fixes Servicing aiohttp websocket requests results in an application crash Servicing a websocket request in an aiohttp application may have resulted in an application crash when using the New Relic python agent. The application will now operate as expected when handling a websocket request. Ignore incomplete aiohttp transactions In aiohttp, connections can be terminated prior to the HTTP response being generated and sent. In those cases, the request handler may be cancelled. These transactions are no longer reported. Fix HTTP status reporting for Tornado transactions HTTP status was not properly added to Tornado transaction events and transaction traces. HTTP status is now automatically added to Tornado transaction events in Insights and transaction traces in APM. Fix reporting of concurrent external requests in Tornado External requests that execute in parallel in a tornado application may not have been recorded. This issue has been addressed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-298081","eolDate":"2020-11-30"},{"agent":"python","date":"2017-10-16","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.96.0.80","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds instrumentation for aiohttp framework, adds support for displaying Heroku dyno names, and various bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Add instrumentation for aiohttp framework Data is now automatically collected for applications using the aiohttp framework. Data for aiohttp applications will appear in both APM and Insights. Additionally, cross application tracing is supported for incoming requests for aiohttp applications. In addition to service maps, aiohttp applications will now show the calling application in transaction traces. Add support for displaying Heroku dyno names Heroku-friendly logic is now applied to how dyno names are displayed. This includes being able to collapse dyno hostnames based on prefix. Bug Fixes Fix crash for gunicorn gaiohttp driver Using gunicorn's gaiohttp worker with New Relic Browser monitoring enabled may have resulted in an application crash. This crash has been fixed and the gaiohttp worker is now fully supported with the New Relic Python Agent. Fix crash for pika versions 0.9.x and earlier Using the agent with pika versions 0.9.x and earlier could have resulted in an application crash. This issue has now been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-296080","eolDate":"2020-10-16"},{"agent":"python","date":"2017-09-19","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.94.0.79","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds instrumentation for aiohttp client. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Add instrumentation for aiohttp client Outbound HTTP requests through the aiohttp library are now recorded. aiohttp Cross Application Tracing is now supported for outbound requests. In addition to Service Maps, applications accessed through the aiohttp client will now appear in transaction traces. Bug Fixes Fix crash when using psycopg2 v2.7 composable queries The psycopg2 library introduced a module to generate SQL dynamically (psycopg2.sql) in version 2.7. Passing a Composable type object (psycopg2.sql.Composable) to execute or executemany resulted in an application crash. The agent now correctly handles psycopg2 Composable objects.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-294079","eolDate":"2020-09-19"},{"agent":"python","date":"2017-09-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.92.0.78","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for monitoring of outbound gRPC requests and adds an API for cross application tracing of custom non-HTTP transports. For details on APIs for cross application tracing see the cross application tracing document. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Add API for cross application tracing of non-HTTP external services 
 A new API is now exposed for implementing cross application tracing in custom instrumentation of non-HTTP transport libraries. For usage of this API see the cross application tracing document.
 Add instrumentation for gRPC client calls 
 Outbound gRPC requests will now show up in APM under the External Services tab and in transaction traces.
 Bug Fixes Fixes erroneous recording of TastyPie NotFound exceptions 
When a TastyPie API view raised a NotFound exception resulting in a 404 response, the agent may have erroneously recorded the exception. This has now been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-292078","eolDate":"2020-09-06"},{"agent":"python","date":"2017-07-31","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.90.0.75","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes bug fixes and improvements to the builtin pika instrumentation. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Improved Feature Naming of Pika Message Transactions This release improves the naming of message transactions . Message consumer transactions are now split based on the name of the consume callback. Improved metadata collection for cloud providers The agent now collects additional metadata when running in AWS, GCP, Azure, and PCF. This information is used to provide an enhanced experience when the agent is deployed on those platforms. Bug Fixes CherryPy WSGI Server automatic instrumentation This release fixes a bug where cherrypy.wsgiserver.CherryPyWSGIServer was not being instrumented. This bugfix impacts CherryPy versions v6.1.0 to v8.9.1.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-290075","eolDate":"2020-07-31"},{"agent":"python","date":"2017-07-12","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.88.1.73","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes bug fixes for the pika RabbitMQ library  instrumentation . The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Using pika to make RPC-style calls from Tornado could result in an application crash When making a remote procedure call from a tornado web application using the pika RabbitMQ library's Tornado connection, it is possible for the tornado web application to crash. Pika Tornado connections no longer result in an application crash. AttributeError generated from an unregistered application starting a MessageTransaction Applications which consume message transactions and do not call register_application can raise an AttributeError resulting in an application crash. This issue has now been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-288173","eolDate":"2020-07-12"},{"agent":"python","date":"2017-07-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.88.0.72","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds built-in instrumentation  for the pika RabbitMQ library , a message broker API which can be used to add custom instrumentation for additional message brokers, and various bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Pika Instrumentation The RabbitMQ pika library is now automatically instrumented. The agent will report data for messages sent and received by an application. Data on messages is available in both APM and Insights. Applications connected through a RabbitMQ exchange will now also be visible on Service Maps as part of Cross Application Tracing. Message Broker API A Message Broker API is now available for use in custom instrumentation. The Message Broker API will send data to APM  and Insights (through message.routingKey and message.queueName attributes) for message broker related operations. Tornado 4.5 Support The Python Agent's out-of-the-box Tornado 4 instrumentation now supports Tornado version 4.5. Tornado AsyncIO Loop In addition to the Tornado PollIOLoop, the AsyncIO loop is now supported as part of our Tornado instrumentation. When Tornado is configured to use the AsyncIO loop, data will now be sent to New Relic. Note that AsyncIO is not yet generally supported. Bug Fixes SQL comments beginning with a \"--\" resulted in an improperly parsed query When executing SQL queries with comments that used the \"--\" comment syntax, the database operation and table was not properly parsed resulting in queries being absent from the Databases tab. Queries with \"--\" comments should now show up in the Database tab. AttributeError generated when using Tornado 4 HTTPRequest objects in an external web call When using the Tornado 4 HTTPRequest object as an argument to HTTPClient.fetch, it was possible to generate an AttributeError. The web call now completes as expected. Slow network connections may result in lost data When, due to a slow network, a 408 error is returned from New Relic data was not retransmitted. Data is now retransmitted when a 408 is received.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-288072","eolDate":"2020-07-06"},{"agent":"python","date":"2017-05-26","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.86.3.70","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes various bug fixes as described below. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Handle exceptions generated by Tornado 4  AsyncHTTPClient during fetch Exceptions generated by a call to the AsyncHTTPClient resulted in an agent instrumentation error. Exceptions generated by AsyncHTTPClient are now recorded and properly handled. Using gevent/eventlet on Python 3.6 resulted in a RecursionError Python 3.6 introduced a change  to the ssl library. This change can result in a recursion error  when the New Relic agent imports ssl prior to eventlet/gevent patching the ssl library (as is the case with use of the newrelic-admin script). This recursion error has been fully mitigated.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-286370","eolDate":"2020-05-26"},{"agent":"python","date":"2017-05-23","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.86.2.68","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release is the same as 2.86.0.65  except it has been re-published to pypi due to an issue with 2.86.1.66 .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-286268","eolDate":"2020-05-23"},{"agent":"python","date":"2017-05-17","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.86.1.66","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release has been superseded. Please use version 2.86.2.68  or higher. This release of the Python agent includes various bug fixes as described below. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Handle exceptions generated by Tornado 4 AsyncHTTPClient during fetch Exceptions generated by a call to the Tornado 4 AsyncHTTPClient resulted in an agent instrumentation error. Exceptions generated by AsyncHTTPClient are now recorded and properly handled. Using gevent/eventlet on Python 3.6 resulted in a RecursionError Python 3.6 introduced a change  to the ssl library. This change can result in a recursion error  when the New Relic agent imports ssl prior to eventlet/gevent patching the ssl library (as is the case with use of the newrelic-admin script). This recursion error has been mitigated when using newrelic-admin to start applications.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-286166","eolDate":"2020-05-17"},{"agent":"python","date":"2017-05-03","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.86.0.65","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes improvements to our introductory support for Tornado 4 applications as well as bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Feature Tornado 4 Outbound Cross Application Tracing Tornado 4 Cross Application Tracing  is now supported for outbound web transactions. In addition to Service Maps, Tornado 4 transaction traces will now contain links to the application it called. With this update, Cross Application Tracing is now fully supported for Tornado 4 applications. Bug Fixes Django 1.10+ browser monitoring with new-style gzip middleware Browser monitoring was not automatically inserted when using new style Django 1.10+ gzip middleware. Browser monitoring code is now inserted as expected. Using motor versions 1.X generated instrumentation errors Motor 1.0 removed the MotorReplicaSetClient class which resulted in the New Relic Python Agent generating an instrumentation error when attempting to access that class. The instrumentation has been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-286065","eolDate":"2020-05-03"},{"agent":"python","date":"2017-04-25","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.84.0.64","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes bug fixes and improvements to the precision of the duration data recorded for transaction traces. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Improved Feature Transaction trace precision This release improves the precision of transaction traces. Duration of functions in a transaction trace are now recorded at sub-millisecond precision. Bug Fixes Custom classmethod traces may incorrectly return the parent class Wrapping classmethods in classes that are subclassed could cause the subclassed classmethod to be improperly bound to the parent class. This would result in the classmethod returning an instance of the parent class when the method was called on a child class. Handle incomplete Tornado coroutine traces Tracing a Tornado coroutine that never completed and was later garbage collected, could result in an application hang. This has been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-284064","eolDate":"2020-04-25"},{"agent":"python","date":"2017-04-17","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.82.1.63","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes a bug fix for our introductory support for Tornado 4 applications. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Bug Fixes Ending Tornado 4 transactions inside of a traced function results in an internal agent error Ending a Tornado 4 web transaction within a traced function previously resulted in the generation of an agent traceback. The agent now completes tracing the function before ending the transaction, resulting in the correct reporting of these transactions to New Relic.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-282163","eolDate":"2020-04-17"},{"agent":"python","date":"2017-03-15","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.82.0.62","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent improves our introductory support for Tornado 4 applications by adding Cross Application Tracing  for web transactions that are sent to a Tornado 4 application. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Feature Tornado 4 applications will now appear in Service Maps Tornado 4 Cross Application Tracing  is now supported for inbound web transactions. In addition to Service Maps, the calling application's APM will now have links to the Tornado 4 application it called in the External Services tab and in Transaction Traces. Bug Fixes Record exceptions outside of view handlers in Django 1.10 Unhandled exceptions that occurred outside of a view handler in Django 1.10 were not reported. In addition to middleware exceptions, these unhandled exceptions can be generated when a view handler returns a TemplateResponse and rendering that template would result in an exception. Consistent WSGI/Application and WSGI/Response segments Prior to this release, the agent would group segments under WSGI/Application and WSGI/Response differently, depending on whether or not browser monitoring  was enabled. This has now been made consistent. Improved New Relic WSGI middleware behavior The New Relic agent is now resilient when called by non-conforming middleware. Transactions will continue to be reported normally when the New Relic agent is called by WSGI middleware that does not call the close() method as described in the PEP 333  specification.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-282062","eolDate":"2020-03-15"},{"agent":"python","date":"2013-12-13","downloadLink":null,"version":"2.8.0.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent marks the official introduction of support for pypy. Instrumentation has also been updated to address issues arising from the release of Celery 3.1. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . New Features: The agent has worked with and has already been used by customers with pypy for some time, but we have not officially acknowledged that we support pypy. We have now integrated pypy into our test procedures and now officially support this implementation of the Python language. Bug fixes/Improvements: Instrumentation for Celery has been updated to accommodate changes in Celery 3.1. The changes in Celery 3.1 resulted in no metrics being reported in prior versions of the agent. When collecting data on external web service calls, the agent now drops port 80/443 from the name of the host when used with the standard http/https protocol schemes. This ensures that a URL with or without the ports are seen as the same service in the external web services page in the UI. When using newrelic.agent.initialize() explicitly, if no arguments are provided, the values for the config file and environment arguments will now be read from the NEW_RELIC_CONFIG_FILE and NEW_RELIC_ENVIRONMENT arguments if specified. Flask instrumentation was not correctly mapping URLs related to a HTTP 404 response to a known framework or application handler function. Instead the web transaction was named after the URL, which could result in metric grouping issues if an application was hit with a large number of URLs which couldn't be mapped by the application. Such requests will now be mapped to flask.app:Flask.handle_http_exception. Pyramid instrumentation should no longer report as errors instances of exceptions derived from HTTPRedirection, raised to generate a HTTP redirect response. Improvements to the newrelic-admin wrapper script and agent bootstrapping procedure to better deal with a local sitecustomize.py file. Changes will also better handle the case where the newrelic-admin wrapper script was used around a Python script using a different Python installation than that which the newrelic package was installed in, avoiding possible errors when the wrapped script was run, due to the mismatch.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-2807","eolDate":"2016-12-13"},{"agent":"python","date":"2017-02-27","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.80.1.61","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent is a hotfix release to address a problem with the Tornado 4 instrumentation for curl_httpclient introduced in our last release (v2.80.0.60). Under the circumstances described below, calling CurlAsyncHTTPClient.fetch_impl() could result in an agent error. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . Bug Fix Fix CurlAsyncHTTPClient.fetch_impl() instrumentation If fetch_impl() was called by passing the request argument positionally, but passing callback as a keyword argument, then the agent would throw an error. In practice, this only affected customers who implemented a custom version of fetch_impl(), but for those affected customers, this is now fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-280161","eolDate":"2020-02-27"},{"agent":"python","date":"2017-02-23","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.80.0.60","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent enhances our introductory support for Tornado 4 , most notably by adding support for tornado.curl_httpclient. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Tornado 4 curl_httpclient support Previously, the agent's Tornado 4 instrumentation only supported the default tornado.simple_httpclient. With this release, support has been added for tornado.curl_httpclient as well. Tornado 4 ZeroMQ IOLoop support Using ZMQIOLoop in place of the default Tornado IOLoop is now supported for Tornado 4 applications. Improved Feature Improved transaction names for Django REST Framework When using the Python agent with Django REST Framework and Python 3, function-based views wrapped with the rest_framework.decorators.api_view decorator would result in transactions with names based on the decorator (WrappedAPIView.handler) rather than names based on the original view function. (This did not affect applications running with Python 2.) With this release, the transaction names for these wrapped views are now based on the name of the original view function in both Python 2 and Python 3. Bug Fix End transactions correctly with Tornado 4 @asynchronous decorator When the agent records a transaction for a Tornado 4 RequestHandler method that is decorated with the @tornado.web.asynchronous decorator, the transaction should remain open until RequestHandler.finish() is called. Prior to this release, there were some circumstances where the agent closed the transaction prematurely, resulting in transaction durations that were too short. This has now been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-280060","eolDate":"2020-02-23"},{"agent":"python","date":"2017-01-04","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.78.0.57","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for reporting datastore instance information for the elasticsearch  library. Over the past few releases, support has been added to the agent for collecting datastore instance information for a number of drivers. See a complete list of supported packages . The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Feature Datastore instance information for elasticsearch For operations made using the official Elasticsearch client , the Python agent will collect the host and port of the elasticsearch server. This data will be displayed in transaction traces and in slow query traces in APM. Bug Fix Cornice 2.3.0 TypeError When using the latest version of Cornice ,the Python agent would raise a TypeError exception due to not handling the changed signature of cornice.Service.decorate_view(). Earlier versions of Cornice were not affected, and with this release, the Python agent no longer raises an error for version 2.3.0.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-278057","eolDate":"2020-01-04"},{"agent":"python","date":"2016-12-14","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.76.0.55","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for reporting datastore instance information for the python-memcached  library. It also addresses a couple of Python 3 issues related to naming metrics and transactions. Over the past few releases, support has been added to the agent for collecting datastore instance information for a number of drivers. See a complete list of supported packages . The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Datastore instance information for python-memcached For most memcached operations made using the python-memcached  package, the Python agent will collect the host and port of the memcached server, as well as the memcached database index number. This data will be displayed in transaction traces and in slow query traces in APM. Supported operations include: add, append, cas, decr, delete, get, gets, incr, prepend, replace, set. Currently, the Python agent does not collect instance information for operations that interact with multiple memcached instances. These include: delete_multi, flush_all, get_multi, get_slabs, get_stats, set_multi. Bug Fixes Names for subclass methods in Python 3 Previously, when using Python 3, if a method was defined on a base class, but was called as a method on an instance of a subclass, the agent would generate a metric name or transaction name for that method using the base class. It would also use the module name of the base class in the metric or transaction name. With this release, the metric name or transaction name will use the class name of the subclass, as well as the module name of the subclass. This is consistent with how the naming works for Python 2. Names for Flask pluggable views in Python 3 When monitoring Python 3 Flask applications, the agent would create metric and transaction names for Flask pluggable (or, class-based) views using the name of the View.as_view() classmethod, making it impossible to distinguish between different views in APM. Now, the metric and transaction name uses the name that is passed into View.as_view(). For example, a view defined as view_func=ShowUsersView.as_view('show_users') would use show_users as the view name. This is consistent with how the naming works for Python 2. Redis client with custom connection pool If a custom connection pool was used with the redis  client, the agent could throw an AttributeError when attempting to gather datastore instance information. One library known to define a custom connection pool that encountered this issue is Redis Blaster . With this release, the agent will no longer throw an error for custom connection pools. In addition, the agent will now be able to gather datastore instance information for some operations, even when using a custom connection pool. Developer Mode error message during \"fake\" harvest When using the configuration setting of developer_mode = True, the agent does not transmit any data to New Relic. Instead, it performs a \"fake harvest\". In some cases, it was possible for the agent to log an AssertionError during the \"fake harvest\", but this issue has now been fixed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-276055","eolDate":"2019-12-14"},{"agent":"python","date":"2016-11-14","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.74.0.54","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for reporting datastore instance information  for both the redis and MySQLdb drivers. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . New Features Datastore instance information for redis For redis operations made using the redis-py  package, the Python agent will collect the host and port of the redis server, as well as the redis database index number. This data will be displayed in transaction traces and in slow query traces in APM. Datastore instance information for MySQLdb For queries made with the MySQLdb  driver, the Python agent will collect the host and port of the database server, as well as the database name. This data will be displayed in transaction traces and in slow query traces in APM.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-274054","eolDate":"2019-11-14"},{"agent":"python","date":"2016-10-25","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.72.1.53","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent is a hotfix release to address a problem introduced in our last release (v2.72.0.52) where users of the psycopg2 Postgresql database adapter could see extra Datastore entries in the Breakdown Table on the Transactions page in APM. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . Bug Fix Remove extra Datastore segments from the Transactions Breakdown Table Due to the extra Datastore segments in the Breakdown Table on the Transactions page in APM, the \"% Time\" column would add up to greater than 100%. This problem has now been fixed. Users of psycopg2 who are using v2.72.0.52 of the Python agent are encouraged to upgrade to this latest version.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-272153","eolDate":"2019-10-25"},{"agent":"python","date":"2016-10-18","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.72.0.52","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for reporting datastore instance information  for the psycopg2 Postgresql driver. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . New Feature Datastore instance information for psycopg2 For queries made with the psycopg2 Postgresql driver, the Python agent will collect the host and port of the database server, as well as the database name. This data will be displayed in transaction traces and in slow query traces in APM.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-272052","eolDate":"2019-10-18"},{"agent":"python","date":"2016-09-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.70.0.51","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for the improved Django middleware introduced in Django v1.10, and also adds instrumentation for the boto3 and awscli packages. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . New Features Django 1.10 Middleware Support As described in Django Enhancement Proposal 5  and in the Django v1.10 middleware documentation , Django introduced a new style of middleware in version 1.10. Previously, Django allowed you to define certain methods on middleware classes: process_request() methods would run before the view handler was invoked, and process_response() methods would run after the response was generated. Accordingly, the Python agent would instrument these as separate, self-contained methods, and in the Transaction Trace Details view, they would be displayed at the same level as the view handler in the segments hierarchy. With the improved version in Django v1.10, the middleware classes form a \"chain\", and each middleware calls the next middleware, until it reaches the end of the chain and calls the actual view. This means that new-style middleware acts as a wrapper, and each one is nested inside the previous one. As a result, in the Transaction Trace Details view, each middleware will be nested inside the previous one, and the actual view handler will be displayed nested inside the innermost middleware class. Furthermore, the duration of each middleware segment will include the duration of the middleware nested inside it. Because Django v1.10 is backwards-compatible with the old-style middleware, the agent also supports instrumenting old-style middleware in Django v1.10 Boto3 and AWS CLI Support With this release, API calls to Amazon Web Services endpoints made with the boto3 and awscli packages will be recorded as External Traces and will be visible in the External Services tab in APM. This is achieved by instrumenting the botocore library, which both boto3 and awscli utilize. Bug Fixes Proxy Scheme Output of network-config Command Prior to this release, the newrelic-admin network-config command would output the incorrect proxy scheme. That is now fixed. Debug Console Works with Python 3 The newrelic-admin debug-console is now compatible with Python 3.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-270051","eolDate":"2019-09-06"},{"agent":"python","date":"2016-07-19","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.68.0.50","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent is a bug fix release that addresses several recently reported issues. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . Bug Fixes WebSocket requests could cause application errors When an application is using gevent-websocket  to serve a mixture of WSGI and WebSocket endpoints, it is possible for WebSocket requests to interfere with the instrumentation of non-WebSocket requests, and cause application errors. While a fix  for this has been added to the 'gevent-websocket` main branch, that fix has not been released to PyPI yet. To address the problem now, the Python agent explicitly ignores WebSocket requests. Disabling browser monitoring inadvertently disabled other features Disabling browser monitoring had the unintended effect of disabling certain other Response-related features of the agent. Specifically, the response.status attribute was not recorded, and the Cross Application Tracing  headers were not added to the HTTP headers of the outgoing response. With this release, those features now work when using the configuration setting of browser.monitoring.enabled = False. Calling a Celery task within another task could cause a RuntimeError The Python agent would throw a RuntimeError('transaction already active') when instrumenting a Celery task that performed the following combination of actions: Utilized the agent API to end the transaction early (end_of_transaction ), or to ignore the transaction altogether (ignore_transaction ). After ending or ignoring the transaction, called another Celery task that would run synchronously. This scenario, which most commonly occurs when taking advantage of Celery Workflows  to compose multiple tasks together, will no longer result in a RuntimeError.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-268050","eolDate":"2019-07-19"},{"agent":"python","date":"2016-05-26","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.66.0.49","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent is a bug fix release that addresses several outstanding issues. In addition, the agent's instrumentation for the Pyramid web framework was updated to handle changes introduced in version 1.7 of Pyramid. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . New Feature Support for Pyramid 1.7 In version 1.7 of the Pyramid web framework, the ViewDeriver class was removed and replaced with a custom view pipeline, composed with view derivers. This required a change to where the agent applied it's instrumentation, since we were previously instrumenting the ViewDeriver class. Bug Fixes Gevent and Python 3.4+ When running the agent with gevent in Python 3.4+, the agent would throw an AttributeError when accessing the _sleep attribute in the threading module, which was removed in Python 3.4. The agent now handles this properly. Possible missing application exceptions in APM Error Analytics Using the record_exception() API, it is possible to record an exception against the application, but outside of a transaction. If there was a time window in which no transaction exceptions were recorded, but only application exceptions were recorded, then no exceptions would be displayed when viewing that time window in APM Error Analytics. With this release, application exceptions show up as expected, whether or not transaction exceptions were also recorded. CherryPyWSGIServer and keyword arguments Previously, the agent would fail to instrument CherryPyWSGIServer correctly when it was initialized using keyword arguments. That is now handled correctly. Missing attributes in Transaction Events In version 2.60.0.46  of the agent, two response header attributes were renamed, but they were not added to Transaction Events as they should have been. response.headers.contentLength response.headers.contentType These attributes are now included in Transaction Events. Changed Feature Capture port for all HTTP requests to External Services Prior to this release, the agent would capture the port for HTTP requests to external services for only some of the HTTP libraries that the agent instruments. Notably, the port was missing when using these libraries directly: httplib, httplib2, and urllib3. The agent now captures the port for these libraries.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-266049","eolDate":"2019-05-26"},{"agent":"python","date":"2016-04-20","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.64.0.48","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent is a bug fix release which improves our introductory support for instrumenting Tornado 4 applications. Full details about the status of our Tornado 4 support can be found on our Introductory Tornado 4 support  page. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . New Feature New attributes captured for Tornado 4 applications The following attributes are now captured for requests made to Tornado 4 applications: request.headers.accept request.headers.host port Bug Fixes Potentially too many metrics created for tornado.httpclient function traces The tornado.httpclient instrumentation for Tornado 4 applications could cause a \"metric grouping issue\"  in the function traces it created, if it was used to make requests to a large number of unique URLs. To address this issue, the URL is no longer included in the name of the function trace. Transactions in Tornado 4 applications could be created with invalid agent settings In the prior release, if a transaction started before the agent had completed registration with the collector, the transaction could have invalid settings, which would result in various errors in the agent log, including an AttributeError when an external call was made during the transaction. These errors only happened at application startup until registration was complete. With this release, transactions cannot start with invalid settings. The httplib2 instrumentation did not process the cross application tracing headers in the response Failing to process the response headers resulted in the inability to link to cross application tracing details in the Transaction Trace Details view , as well as missing ExternalTransaction and ExternalApp metrics. Now, the httplib2 instrumentation in the agent processes the cross application tracing headers correctly. Known Tornado 4 Limitations Addressed Explain plans for queries made with psycopg2's \"async mode\" are disabled automatically Currently, the Python agent does not support explain plans for queries made in psycopg2's \"async mode.\" In the prior release, it was necessary to add the configuration setting transaction_tracer.explain_enabled = false to disable explain plans, or else errors would occur during data harvest, potentially causing loss of data. With this release, the agent disables explain plans automatically when async mode is detected. Added support for synthetics transaction traces Tornado 4 applications will now recognize incoming requests from synthetics and generate transaction traces for Synthetic requests . Status of Tornado 4 Support A current list of known limitations can be found on our Introductory Tornado 4 support  page. No new known limitations have been added since our introductory release (v2.62.0.47). In the next few releases, we plan to continue addressing these issues.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-264048","eolDate":"2019-04-20"},{"agent":"python","date":"2016-03-30","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.62.0.47","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds introductory support for instrumenting Tornado 4 applications. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . New Feature Introductory Support for Tornado 4. (See below for details.) Bug Fix Django Template Tags for Browser Monitoring Fixed for Django 1.9 For manual insertion of the browser monitoring javascript for page load timing, the Python agent offers two Django template tags: newrelic_browser_timing_header and newrelic_browser_timing_footer. Starting in Django version 1.9 , the output of simple_tag is now escaped, which results in the browser monitoring javascript being included as escaped text in the HTML output. To fix this issue, the agent now uses django.utils.safestring:mark_safe() to prevent automatic escaping for these two template tags. Introductory Support for Tornado 4 New Relic is pleased to announce introductory support for Tornado 4. While not all features are supported at this point, providing it at an early stage allows interested customers to preview our Tornado 4 support, and provide feedback on what works well and what doesn't. We strongly advise running the introductory Tornado 4 instrumentation in a testing or staging environment before considering using it in a production environment. For detailed information about the introductory Tornado 4 support, including Supported Features, Design Decisions, and Known Limitations, see Introductory Tornado 4 support . Status of Tornado 4 Support The following is a list of known limitations for our Tornado 4 support as it exists in the current version of the agent. In the next few releases, we plan to address these issues. If you use psycopg2 in aynchronous mode, you must disable explain plans in the Python agent, or else the agent will throw an error when it attempts to run an explain plan query. Add this setting to your newrelic.ini configuration file: Metric names should be more consistent. For a method of a class, the metric name should contain both the name of the class and the method, but sometimes, the metric name will be missing the class name. The nesting of segments in a Transaction Trace should be improved. Right now, transaction traces give a good indication of the order that callbacks run on the IOLoop, but they do not group together callbacks that belong to the same coroutine, nor do they show how callbacks relate to each other. Transaction Traces mislabel time spent in \"Application code\". Because the Tornado 4 instrumentation traces all callbacks that run on the IOLoop, nearly everything that happens in a transaction is recorded. Very little is uninstrumented \"Application code\". When you see \"Application code\" time in a transaction trace, that usually means that the IOLoop was either busy running callbacks belonging to another transaction, or was waiting and not doing any work. This will be made clearer in a future release. In the current version of the agent, the Total Time for a transaction will always equal the duration of the transaction. In future versions, we may begin measuring the time spent waiting for asynchronous External Traces and Datastore Traces to return results, which will increase the Total Time for a transaction, making it possible to have a Total Time greater than the duration of the transaction. When using tornado.httpclient, no Cross Application Tracing headers are added to the outgoing requests. (This is true for both HTTPClient and AsyncHTTPClient.) That means that the application that the httpclient connects to will not show up in any of the following: trace maps, transaction maps, and service maps. Asynchronous External Traces only trace the initial HTTP connection. They do not trace the time for the response to come back. If you monitor your Tornado 4 application with synthetic monitoring, the Python agent will not capture transaction traces for synthetic checks, so you will be unable to connect your synthetic results to APM transaction traces. Measuring thread utilization is disabled for Tornado applications. Exceptions thrown in RequestHandler.initialize() are not recorded. Use of Tornado's built-in multi-process mode to start multiple processes and have them all share the same port is untested and unsupported. Use of tornado.wsgi.WSGIAdapter and tornado.wsgi.WSGIContainer is untested and unsupported. Use of tornado.platform.asyncio to bridge between asyncio and Tornado IOLoop is untested and unsupported. Currently, the agent only supports the use of the tornado.ioloop.IOLoop. Use of the async and await keywords is untested and unsupported. Integration with Twisted is untested and unsupported.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-262047","eolDate":"2019-03-30"},{"agent":"python","date":"2013-11-02","downloadLink":null,"version":"2.6.0.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent contains support for web applications and worker processes using 'gearman' for background task execution. The agent also switches to using the 'json' package from the standard library instead of a separate 'simplejson' package. This should result in potential reductions in base level memory usage by the agent and a reduction of CPU overhead for some environments. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . New Features: Instrumentation now provided for the gearman  package. The support covers use of both the gearman client and worker interfaces. In the case of workers, each task executed by the worker will be recorded as a background task and be displayed as such in the New Relic UI. The ignore_errors argument to newrelic.agent.record_exception() can now be a callable in addition to being able to pass a sequence. When it is a callable, the callback will be called with the three arguments exc, value and tb, being the same values as returned by sys.exc_info(). The callback should return True if the exception is to be ignored. False if the exception should never be ignored regardless of any other checks, and None if subsequent checks and inbuilt rules should determine if the exception should be ignored. A callback would normally return either True or None. Bug fixes/Improvements: The bundled 'simplejson' package has now been removed and is no longer used. This was previously used due to the requirement to support Python 2.5, for which support was removed in version 2.0.0 of the agent. Instead of simplejson, the 'json' package contained in the Python standard library is now used instead. This should see the base level memory usage of the agent drop as a result. Further, in environments where a C compiler was not available and the C extension modules could not be compiled, there should now be a minimal reduction in the CPU overhead when the agent is uploading data to our backend. This is because the optimised C extension in the json package will always be available as part of the Python standard library and will always be able to be used. If a WSGI application was returning an iterable such as a generator, and an exception was raised when a specific part of the response content was yielded from the generator, the details of the exceptions were not being recorded. In a multithreaded web application where deferred module imports were being performed in secondary threads, agent registration could fail the first time due to concurrent changes made by the secondary threads to sys.modules. Registration would succeed on a subsequent attempt. This bug was only occurring in Python 2 and was introduced in version 2.0.0 of the agent when Python 3 support was added. Custom parameters which were explicitly supplied to newrelic.agent.record_exception() were being ignored and were not appearing in the error details page in the UI. Instead, only custom parameters added using newrelic.agent.add_custom_parameters() against the web transaction or background task itself were being shown. This bug was introduced in version 1.13.0 of the agent when support for cross application tracing was added. The port number used in the URL for a web external call, was not being retained when the URL was added as a parameter against the web external node for transaction traces. The port would therefore not be displayed when drilling down into the details of a web external node in a transaction trace. The newrelic-admin validate-config command will now work for enterprise high-security mode accounts, provided of course that no setting is otherwise specified in the agent configuration file which is in conflict with that mode. That is, features such as SSL would still need to be enabled by the ssl setting and the capture_params setting indicating whether URL query string parameters should be captured, also set to false. When using CherryPy, in addition to the explicit exception type 'NotFound' being ignored as an error, raising of a 'HTTPError' exception where the status is 404 will also be ignored. Similarly, instances of the 'HTTPError' exception will be ignored as an error when they are for a HTTP error in the 30X range.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-2605","eolDate":"2016-11-02"},{"agent":"python","date":"2015-12-14","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.60.0.46","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent enables the ability to add Custom Insights Events through a new record_custom_event() API. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . New Feature Custom Events Prior to this release, the Python agent had the capability to record two types of Insights events automatically: Transaction and TransactionError events. In addition, custom attributes could be added to those events. Now, with the addition of the record_custom_event()  API, it is possible to define your own custom event types, enabling greater flexibility about what types of events you can view and query in Insights. For details, see the Insights documentation on Inserting Custom Events . Changed Feature Attributes renamed Two attributes have been renamed, in order to be consistent with the naming convention of other New Relic agents. The affected attributes are: response.headers.contentLength (was response.contentLength) response.headers.contentType (was response.contentType)","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-260046","eolDate":"2018-12-14"},{"agent":"python","date":"2015-11-25","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.58.2.45","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent is a hotfix release to address a problem where the agent could fail to validate the SSL certificate of the New Relic collector in some environments. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . Bug Fix If the Python agent was used in an environment where the certifi package was installed, the Python agent would use the certifi CA certificates bundle to validate the certificate of the New Relic collector. However, the latest release of certifi (November 20, 2015) removed some older CA certificates with 1024-bit keys. The SSL certificate for the New Relic collector is cross-signed with both a 1024-bit certificate and a 2048-bit certificate, but in some circumstances, the stronger root certificate was not used for validation. When the 1024-bit certificate was no longer included in the certifi bundle, SSL validation would fail. Affected customers would see warnings in their agent log stating \"Data collector is not contactable\" due to an SSLError. To address this issue, the agent no longer uses the certifi CA certificates bundle, nor the certificates bundled with requests. Instead, it only uses the CA bundle included with the agent to validate the New Relic collector certificate.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-258245","eolDate":"2018-11-25"},{"agent":"python","date":"2015-11-17","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.58.1.44","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent is a hotfix release to address a problem where the package failed to install under certain circumstances. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . Bug Fix The README.rst file contained non-ASCII characters, which could result in a UnicodeDecodeError during installation. Those characters have been removed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-258144","eolDate":"2018-11-17"},{"agent":"python","date":"2015-11-16","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.58.0.43","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent reports error events to Insights and captures enhanced error data to support the new Advanced Error Analytics feature in APM. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . New Feature Error Events The Python agent now sends TransactionError  events for Advanced Error Analytics, which power the new APM Errors functionality (currently in Beta). This allows users to create charts that facet and filter their error data by attributes, as well as explore their error events in Insights. For details, see the APM Errors documentation . Changed Feature Additional Attributes collected The agent now collects additional attributes  for web transactions: HTTP request headers: Host and Accept HTTP response header :Content-Length Bug Fix Improved unicode support for exception messages Unicode exception messages will still be preserved, even if sys.setdefaultencoding() has been called to change the default encoding.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-258043","eolDate":"2018-11-16"},{"agent":"python","date":"2015-09-30","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.56.0.42","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds much more flexibility around what attributes are sent to New Relic, and where they are displayed. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . New Feature Flexible capturing of attributes Attributes are key-value pairs that contain additional information to be added to an event or transaction. These key-value pairs can be viewed within transaction traces in New Relic APM, traced errors in New Relic APM, transaction events in Insights, and page views in Insights. A number of new configuration settings have been introduced to allow you to customize exactly which attributes will be sent to each of these destinations. For details, see Python agent attributes . Deprecated Settings Several configuration settings have been deprecated. The most commonly used of the deprecated settings are capture_params and ignored_params. It is still possible to achieve the same functionality as the old settings by using the new attributes.include and attributes.exclude settings. For examples, see Python agent attribute examples . A complete list of deprecated settings can be found in deprecated configuration settings . While the usage of deprecated settings is still supported, we recommend upgrading your configuration to use the new settings as soon as possible. Changed Feature Previously, it was possible to save a list, dict, or tuple as an attribute value that could be displayed in transaction and error traces. However, these same attributes could not be displayed in Insights events. Now, all attributes are handled in a consistent manner, which means that all attribute values must be one of the following types: All values which are not one of these types are automatically converted by calling str(value).","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-256042","eolDate":"2018-09-30"},{"agent":"python","date":"2015-07-29","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.54.0.41","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds the ability to strip exception messages from error traces, in order to prevent the inadvertent capture of sensitive information. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . New Features Allowing Exception Messages Because an exception message can contain sensitive information, the agent now provides the ability to strip exception messages before sending error traces to APM. Exception messages will be stripped automatically in high-security mode . For exception messages you know to be safe, you can add them to an allow list so that those messages are passed unaltered to APM. Two new configuration settings control this feature: strip_exception_messages.enabled  and strip_exception_messages.whitelist. Bug Fixes capture_request_params API disabled for high-security mode When operating in high-security mode, the agent should not capture query string parameters. However, prior to this release, it was possible to call newrelic.agent.capture_request_params(flag=True), even if the agent was in high-security mode, and the agent would capture and report query string parameters. Now, the capture_request_params API call does not override the capture_params setting when the agent is in high-security mode, so query parameters are not captured.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-254041","eolDate":"2018-07-29"},{"agent":"python","date":"2015-06-11","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.52.0.40","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds the ability to customize the hostname displayed in the APM UI, as well as updating the solrpy and pysolr instrumentation so that Solr metrics will now appear in the Databases tab in the UI. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . New Features Customize hostname displayed in APM A new configuration setting has been added: process_host.display_name . When set in the newrelic.ini configuration file, the display name will be used in the APM UI , in place of the hostname that the agent automatically captures. In addition, the display name can be set using the NEW_RELIC_PROCESS_HOST_DISPLAY_NAME environment variable. Features Changed Update solrpy and pysolr instrumention Previously, solrpy and pysolr instrumentation reported metrics in the Solr namespace. Now, to align them with our recent changes to SQL and NoSQL instrumentation, solrpy and pysolr have been updated to report metrics in the Datastore namespace, which means that time spent in calls to Solr will be listed in both the main overview chart, as well as in the Databases tab in the UI.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-252040","eolDate":"2018-06-11"},{"agent":"python","date":"2015-04-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.50.0.39","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Django 1.8. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . New Features Support for Django 1.8. Features Changed The list of modules loaded by the application will no longer include version numbers. In certain cases, attempting to determine the version numbers of packages can potentially generate excessive CPU overhead, so it has been preemptively disabled to prevent any such occurrence. Bugs Fixed When using the psycopg2 Postgres database adapter, if the pscyopg2.extras.register_json() function was used, then instrumentation for the psycopg2 module would fail. Now, register_json() is instrumented correctly. If a Django class based view was registered as the view handler in urls.py , the transaction was named after the class name, and not the method of the class based view which handled the request. Now, the transaction is named after the method.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-250039","eolDate":"2018-04-06"},{"agent":"python","date":"2015-03-25","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.48.0.38","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds instrumentation for Elasticsearch as a new datastore product and a more granular breakdown of various SQL operations in the “Databases” tab in the APM UI. In addition, the stack traces captured by the agent are now being trimmed to remove any code snippets. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . New Features Improved SQL Breakdown This agent release adds the ability to see the breakdown of time spent in SQL statements such as CREATE, DROP, ALTER, SET, CALL, EXEC, EXECUTE, COMMIT and ROLLBACK. Execution of stored procedures through the callproc() or CALL statements will provide further breakdown based on the name of the stored procedure. Elasticsearch Support Instrumentation support for the official Elasticsearch client module and the separate pyelasticsearch module have been added. Time spent in calls made to Elasticsearch will be listed in both the main overview chart, as well as in the Databases tab in the UI. Previously, calls to Elasticsearch would have been shown as time spent in external web service calls. Features Changed Remove code snippets in stack traces Stack traces captured for errors and slow SQL queries will no longer include code snippets. This change is to prevent the possibility of capturing sensitive data embedded within the code. It reduces the overhead in capturing stack trace information, and also avoids a potential problem caused when the code on disk has changed in the time since the process was started. Bugs Fixed Ensure that messages sent to the data collector containing parts which were already compressed and encoded, were not being compressed a second time at the HTTP request level causing additional overhead. Guard against a potential agent error where an invalid URL was being passed to an instrumented external web service client. Motor (an asynchronous MongoDB library) incorrectly returns a non string object when the agent tries to access the __name__ attribute on Motor objects. This caused the agent to fail when calculating the name for an object, since we rely on this value being a string as specified by the Python object model definition. The agent now overrides the incorrect behavior of Motor to ensure that we can still generate names of objects correctly. When using Python 3 and audit logging was enabled, if messages being sent to our data collector were large enough that they were being compressed at the HTTP request level, the audit logging code would fail due to a bytes/Unicode mismatch. Instrumentation for the decr() method of umemcache client for Memcached was incorrectly calling the stats() method.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-248038","eolDate":"2018-03-25"},{"agent":"python","date":"2015-03-04","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.46.0.37","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent is a minor bug fix release, including changes which may help to reduce the incidence of spurious warnings about being able to communicate with our service. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . Bugs Fixed Improved management of the network connection to our service When the agent registered itself with our data collector, it wasn't closing the socket connection immediately and instead it was holding it open for up to a minute when the first batch of data would be reported. If the socket connection was being closed remotely during that time, a BadStatusLine exception would be seen in the logs when the attempt was made to upload data. When the agent received an internal restart request from our data collector as the result of a server side configuration change, the socket connection wasn't being closed explicitly. In the case of CPython it would still be cleaned up and closed immediately due to reference counting, but under PyPy when it was closed was dependent on when PyPy garbage collection occurred. This could mean that the socket descriptor could stay in use for a while. Compatibility modules for transitioning from Python 2 to Python 3 When compatibility modules for Python 2/3 migration such as pies2overrides and future were installed in a Python 2 installation, they were installing modules which mimic modules which would normally only ever exist in a Python 3 installation. The presence of these modules were confusing the agent's instrumentation mechanisms. The result of this was that use of http.client from Python 3 in a Python 2 application would fail. Failures when making calls to external web services If a HTTP client module was supplied None as the value for the URL being requested, this would cause an exception when the agent was recording the data for that transaction. Use of the ExternalTrace context manager class directly, for recording external web services calls, would fail if there was no active transaction. This could occur in the time before the agent has successfully been able to register with our data collector. Setting of response content length when using Django The Django middleware installed by the agent to perform insertion of RUM monitoring code into responses, would always set the Content-Length even if it was not previously set. This could cause issues where a frontend had been set up with an expectation that Content-Length headers would never exist.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-246037","eolDate":"2018-03-04"},{"agent":"python","date":"2015-02-11","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.44.0.36","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes a major update to how we capture and represent metrics for both SQL databases and NoSQL datastores. Metrics for both types of products will now be displayed in a unified \"Databases\" tab in the APM UI, and these metrics will also be associated with the specific product being used. In addition, we have enabled support for having key transactions on other transactions, such as background tasks. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . New Features Unified view for SQL database and NoSQL datastore products. The response time charts in the application overview page will now include NoSQL datastores such as Memcached, Redis and MongoDB and also the product name of existing SQL databases such as MySQL, Postgres, Oracle etc. We also introduced a new unified view  within the APM UI for visualizing time spent in queries made against SQL databases and NoSQL datastore products. For existing SQL databases, in addition to the existing breakdown of SQL statements and operations, the queries are now also associated with the database product being used. For NoSQL datastores such as Memcached, Redis and MongoDB, we have now added information about operations performed against those products, similar to what is being done for SQL databases. Because this introduces a notable change to how SQL database metrics are collected, it is important that you upgrade the Python agent version on all hosts. If you are unable to transition to the latest agent version on all hosts at the same time, you can still access old and new metric data for SQL databases, but the information will be split across two separate views. Key transactions for other transactions. In addition to being able to create key transactions for web transactions, it is now possible to create key transactions  for other transactions, such as background tasks executed by Celery. Key transactions enable the setting of a per transaction Apdex and alerts, as well as the ability to run X-Ray sessions , including transaction specific thread profiling. No SQL datastore instrumentation. To complement our new unified view for SQL database and NoSQL datastore products in the APM UI, we have upgraded our existing instrumentation for Redis and MongoDB. Previously, these only provided a function breakdown in transaction summaries and sample transaction traces, but now they will report into the unified view for database and datastore products under their respective product categories. Existing instrumentation for Memcached clients have similarly been updated, as well as new support for the pymemcache module being added.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-244036","eolDate":"2018-02-11"},{"agent":"python","date":"2015-01-18","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.42.0.35","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes bug fixes for issues with agent registration and use of proxies which could result in no data being reported. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . Bug Fixes Agent not recovering when errors occur during registration If the agent initially registered with our data collector successfully, but subsequently failed to upload agent setting information due to a transient backend or network issue, the agent was not recovering from the error properly. The consequence of this was that the agent would not completely start up and no data would be collected or reported by that process. The operation of the web application as a whole would not have been affected. This issue, which was introduced in version 2.36.0.30 of the agent, is now fixed. Agent not able to connect via some proxy servers The Python agent was not able to connect to our data collector to register when certain proxy server installations or configurations were being used. We have updated the version of the internal HTTP client library used to resolve the issue. Identification of Python web server being used The Python agent was incorrectly reporting the Python web server being used as Tornado when both the 'gunicorn' and 'tornado' Python modules were being imported, even if the Tornado web server module wasn't actually being used. This did not affect the operation of the agent but could lead to confusion when trying to debug deployment issues.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-242035","eolDate":"2018-01-18"},{"agent":"python","date":"2013-10-16","downloadLink":null,"version":"2.4.0.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent is a bug fix release primarily to address a number of issues introduced in version 2.2.0.2 which have effected a small number of users. This version of the agent is also the minimum recommended agent version required to be able to see percentiles and histogram charts. All reporting hosts for an application must be upgraded to the minimum agent version for the feature to be visible. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directory from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . Bug fixes/Improvements: Fixed issues with instrumentation wrappers which caused failure of WSGI application integration for FASTCGI/SCGI/AJP using flup. Fixed issues with instrumentation wrappers which caused failure of wrappers for external web service calls in certain uses cases. Fixes issues with instrumentation wrappers which caused failure when queuing Celery tasks from within a web application using django-celery. When using the ErrorTrace context manager to capture details of exceptions within a certain context, None can now be passed for the transaction and an assertion failure will not be raised. This avoids the need to check explicitly to see if a web request is being monitored and avoid using ErrorTrace where there isn't.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-2404","eolDate":"2016-10-16"},{"agent":"python","date":"2014-12-03","downloadLink":null,"version":"2.40.0.34","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent enables the collection of transaction traces for synthetic requests by default, and adds the individual trip trace visualization for Cross Application Tracing. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see Status of the Python agent . New Features Cross Application Tracing for individual transactions Version 2.38.0.31 of the Python agent introduced aggregated transaction maps. In this release, we have built on that feature to add the ability to view an end-to-end visualization of an individual transaction, in order to better understand what backend applications and external services were called during the course of a single transaction. Features Changed Synthetic support enabled by default When the Python agent added support for the collection of transaction traces for synthetics requests  in version 2.32.0.28, the feature had to be explicitly enabled in the agent configuration file. With this release, support for synthetics is enabled by default. Bug Fixes Non ASCII characters in transaction names If a transaction name contained a Unicode character outside of the ASCII range, the generation of the cross application tracing attributes would result in a UnicodeEncodeError. This bug affected versions 2.38.0.31 through 2.38.2.33. The issue is fixed in the current release. Parsing SQL statements referencing the database schema Previously, SQL statements that referenced a table from a database schema namespace, such as “schema.table_name”, would not always be parsed correctly, resulting in the table being identified as just “schema”. The agent now handles this case correctly, and the table is reported as “schema.table_name”. Additional support for Tornado 1.X If Tornado 1.X was being used, the instrumentation would fail at run time causing all web requests to fail. Monitoring of Tornado 1.X applications should now work correctly.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-240034","eolDate":"2017-12-03"},{"agent":"python","date":"2014-11-25","downloadLink":null,"version":"2.38.2.33","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent fixes a memory leak which affects our Tornado instrumentation, and which was a factor in the recent issues we had with the Django template instrumentation. The agent can be installed using easy_install/pip/distribute  via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see Status of the Python agent . Bug Fixes Due to an issue with the low level function wrappers we use to instrument third party Python modules, memory was being leaked and process memory usage could increase over time. This issue affects version 2.32.0 through 2.38.0 of the Python agent and has been impacting on our Tornado instrumentation. The memory leak has also been identified as the root cause for memory leaks in our Django template instrumentation, affecting versions 2.32.0.28 through 2.36.0.30. The Django template instrumentation was disabled in the prior 2.38.0.31 release while we investigated the cause. It remains disabled by default.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-238233","eolDate":"2017-11-25"},{"agent":"python","date":"2014-11-12","downloadLink":null,"version":"2.38.0.31","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent adds support for the mapping features of Cross Application Tracing, which provide a visualization of how requests flow through multiple applications within a distributed system. The agent can be installed using easy_install/pip/distribute  via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see Status of the Python agent . New Features Cross Application Tracing The Cross Application Tracing feature is now enhanced with the aggregate transaction map  visualizations. This new visualization will help users spot bottlenecks in external services and give them an end-to-end understanding of what other applications and services are called within a transaction. All agents involved in the cross application communication must be upgraded to see the complete graph. Improvements Tornado 3.x Instrumentation The newly refactored Tornado instrumentation is turned on by default. This was introduced in the python agent version 2.32.0.28 under an optional feature flag. This change improves upon the stability of our Tornado instrumentation and accounts for the incremental changes introduced to the Tornado 3.x source tree. It also provides a more granular view of where the time is spent in a WebTransaction, by distinguishing the time spent doing work vs time spent waiting on a asynchronous call. Please be advised that we currently do not have instrumentation for Tornado 4.x, but we are working to add support for it. Capacity Analysis for mod_wsgi The capacity analysis  report shows how many instances of your web application is running and how busy they are. For a web application, the measure of how busy the application is, is calculated by looking at how much of the time the total available set of request handler threads are busy. For the case of using Apache/mod_wsgi in daemon mode, the measure of how busy your application is, has been getting over reported due to the nature of how threads are managed by mod_wsgi. If you are using mod_wsgi version 4.1.0 or higher, this measure will now be more accurately reported as it will use information provided by mod_wsgi about the total number of request handler threads which are available, rather than trying to calculate it based on what threads have been seen to be handling requests. Bug Fixes In version 2.28.0.26 and 2.32.0.28 of the agent, we added new features to track template includes and inclusion tags when using the Django template rendering system. We have had a few reports that indicate that for some users, but not everyone, that the instrumentation implementing these features may be causing an ongoing growth in memory usage for the web application processes over time. Right now, we don't understand the root cause for why this might be occurring in some instances, so to be on the safe side we have disabled these two features while we investigate further. The consequence of these features being disabled is that the web transaction performance breakdown and sample transaction traces will no longer show as a separate metric or entry where one template has been included in another. Further, if the tracking of special inclusion tags had been configured, they will also no longer be shown. We anticipate re-enabling the features once we have worked out what is occurring and made changes to ensure it does not occur again.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-238031","eolDate":"2017-11-12"},{"agent":"python","date":"2014-10-29","downloadLink":null,"version":"2.36.0.30","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent provides improvements to how we report agent configuration information. This enables us to better help you debug any issues you may experience with configuring the agent. The agent can be installed using easy_install/pip/distribute  via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see Status of the Python agent . New Features Configuration Information Agent configuration information displayed in the New Relic UI will now reflect the final configuration used by the agent for an application. This includes the result of any server side configuration settings, which are applied on top of the agent defaults, agent configuration file or environment variables. Previously, the result of applying the server side configuration settings was not being displayed. Bug Fixes If running a system with a Linux 3.X kernel, the agent could fail when attempting to register with our data collector. No data would subsequently be collected or reported. This would occur for versions of Python 2 prior to Python 2.7.3 and versions of Python 3 prior to Python 3.3, if they were built on a system with a Linux 3.X kernel.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-236030","eolDate":"2017-10-29"},{"agent":"python","date":"2014-10-15","downloadLink":null,"version":"2.34.0.29","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent provides support for Labels and Rollups, making it possible to organize your applications in the APM UI into meaningful categories. The agent can be installed using easy_install/pip/distribute  via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see Status of the Python agent . New Features Labels and Rollups The Python agent now supports the ability to apply labels to applications, so that you can easily sort, filter, and page through all of the applications on your account's Applications list. Configuration can be done in the newrelic.ini file: Labels can also be configured by setting a NEW_RELIC_LABELS environment variable: More information on using labels to categorize your applications can be found in the New Relic APM documentation . New CPU Reporting in Environment Snapshot Previously, the Python agent captured two CPU-related values to report to the Environment Snapshot: Logical Processors and Physical Processors. Now, it captures the following three values: Logical Processors : The total number of hyper-threaded execution contexts available, including execution contexts that may exist on the same core. This value remains unchanged from previous agents. Physical Cores : The total number of physical CPU cores available, counting hyper-threaded siblings as a single core. This value was previously reported as \"Physical Processors.\" Physical Processor Packages : The total number of processor packages or dies (each of which may contain multiple physical cores). This value is new with this agent release. Bug Fixes A \"Runtime Error: transaction already active\" will no longer be seen in the case where the agent created nested transaction wrappers and newrelic.agent.ignore_transaction() was called within the outer wrapper but outside the inner wrapper. Previously, this error could have also been triggered when using the WSGI environment setting for newrelic.ignore_transaction set by SetEnv in mod_wsgi. Prior to this version, the HTTP_REFERER URL reported for a transaction contained query parameters, even if the capture_params setting was set to False. Now, the capture_params setting is respected when reporting the HTTP_REFERER URL.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-234029","eolDate":"2017-10-15"},{"agent":"python","date":"2014-09-29","downloadLink":null,"version":"2.32.0.28","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent provides a preview of a significant overhaul of our instrumentation for Tornado version 3.2 and earlier. Further improvements to our Django instrumentation are also included, allowing time spent in rendering Django sub templates to be viewed separately. The agent can be installed using easy_install/pip/distribute  via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see Status of the Python agent . New Features Breakout of Django template rendering Previously when using Django templates, if the Django include  tag was being used, the time spent rendering that sub template was shown under the generic Template/Render category. When the include tag is now used, a distinct metric is instead created corresponding to the rendering time for that sub template. This will appear in the transaction performance breakdown and also in sample transaction traces. In the case of sample transaction traces, as the name of the template will be included in the metric name, it now also provides additional context for understanding where any time is being spent when rendering that template. Features Changed Preview of improved Tornado instrumentation Our instrumentation for Tornado version 3.2 and earlier has been experiencing a number of issues which could result in recording of data stopping and in some cases cause runtime exceptions which would affect the outcome of the executing web request. Upon investigation we found this has come about due to incremental changes in the internals of Tornado which were performed after we originally implemented the instrumentation for Tornado and which we didn't pick up as having being made. The Tornado developers have also recently released version 4.0 of Tornado. This version of Tornado has much more significant internal changes that result in our instrumentation failing completely. Before we could embark on trying to support version 4.0 of Tornado, we deemed it necessary to completely overhaul our existing instrumentation for older versions first in order to gives us good foundation on which to then implement support for version 4.0 of Tornado. This release of the agent provides a preview of the improved instrumentation for older versions of Tornado prior to version 4.0. The new instrumentation is not enabled by default and you will need to explicitly enable it. We have provided it as an opt in change at this point to allow you to properly test with the update first and provide us with any feedback on it and any remaining issues you may find. To enable the preview of the new Tornado instrumentation, you will need to add to the [newrelic]section of the agent configuration file the setting: If you are running on Heroku and are not using an agent configuration file, you can instead set the NEW_RELIC_FEATURE_FLAG environment variable. You can do this by running the Heroku command: Bug Fixes When an exception was raised by a WSGI application during the yielding of response content via a generator, the recording of that web request by the agent may not be closed off properly. This would result in no further web requests handled by that thread being recorded and reported. If this occurred for all request handler threads, then no data would then be reported for the whole web process. This issue relates to behaviour of the Python garbage collector and when Python objects are destroyed. At this point in time we believe this only affects users of pypy and does not affect users of CPython as the reference counting model of CPython usually gives more deterministic behaviour around when Python objects are destroyed. We don't however rule out that it could affect CPython and may explain a situation matching this problem we have seen in a couple of cases where users were using uWSGI. When attempting to use Tornado as a worker for gunicorn, an exception could occur on startup which would result in gunicorn failing immediately and exiting. In order to use this combination it was previously necessary to disable the gunicorn specific instrumentation related to WSGI applications by adding to your agent configuration file: If you were using the Tornado worker with gunicorn and using this workaround, the underlying problem has now been addressed and you should be able to remove that section from your agent configuration file. The mechanism we used for applying function wrappers for instrumentation was not being performed in the most optimal way for methods of classes. This could result in problems, including unexpected runtime exceptions, especially when trying to apply instrumentation to class methods, or methods of an existing instance of a type.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-232028","eolDate":"2017-09-29"},{"agent":"python","date":"2014-09-16","downloadLink":null,"version":"2.30.0.27","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent improves instrumentation for the Flask web framework and adds database monitoring support when using the pymssql client with a Microsoft SQL Server database. The agent can be installed using easy_install/pip/distribute  via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see Status of the Python agent . New Features Improved instrumentation for Flask The Python agent now provides better web transaction naming and performance breakdown metrics when Flask style middleware are being used. This means that time spent in Flask @before_request and @after_request functions will now be broken out as their own metrics. If a @before_request function actually returns a response, the web transaction will be correctly named after that function rather than the Flask WSGI application entry point. These changes, in addition to being applied on middleware functions registered directly against the Flask application, will also work when Flask blueprints are used to encapsulate behavior. Browser monitoring auto-instrumentation when using Flask-Compress When the Flask-Compress package is used to perform response compression with Flask, insertion of browser monitoring tracking code into HTML responses is now automatically performed. Previously, if Flask-Compress was being used, manual instrumentation of HTML responses would have been required. Monitoring of MSSQL database Instrumentation is now provided for the pymssql database client module to monitor database calls made against a Microsoft SQL Server database. Bug Fixes When using high-security mode, the use of newrelic.capture_request_params in the per request WSGI environ to enable capture of request parameters, possibly by setting it using the SetEnv directive when using Apache/mod_wsgi, was not being overridden and disabled as required. When using the DatabaseTrace context manager or associated wrappers explicitly to implement a custom monitoring mechanism for database calls, the instrumentation wrappers could fail with a TypeError exception when trying to internally derive the name of the database product being used.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-230027","eolDate":"2017-09-16"},{"agent":"python","date":"2014-08-26","downloadLink":null,"version":"2.28.0.26","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent improves data collection with the Django web framework. These improvements include better-targeted web transaction naming with the Django REST framework, better coverage of Django template inclusion tags, and better background task monitoring for Django management commands. The agent can be installed using easy_install/pip/distribute  via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see Status of the Python agent . New Features Improved Django REST Framework naming Previously, when using the Django REST framework, web transactions were being named after the class based view that implemented the Django REST framework resources. Now, where such a view provides custom handler methods for different HTTP request method types or actions, the web transaction will be named after that custom handler method rather than the class as a whole. A new function breakdown metric will also be added for the custom handler method. This change will allow web requests using different HTTP request method types to be viewed separately. Django inclusion tag monitoring Usage of inclusion tags  in Django templates can now be monitored and will appear in the transaction breakdown table, charts and sample transaction traces. Due to the possibility that a large range of custom inclusion tags might be used and that they may be invoked a large number of times in tight loops, tracking of all inclusion tags may not be practical or may not produce worthwhile results in the transaction breakdown or sample transaction traces. As a result, monitoring of inclusion tags is off by default, with the preferred approach being that specific inclusion tags of interest be individually enabled through the agent configuration file. To enable monitoring of specific inclusion tags, a new section called import-hook:django should be added to the agent configuration: The instrumentation.templates.inclusion_tag setting within that section should then be set to a space separated list of the names of the inclusion tags to monitor. If there is any confusion over the identity of the inclusion tag, the full name of the inclusion tag function, with module name, can instead be listed. For example, data_hierarchy can also be identified using django.contrib.admin.templatetags.admin_list:date_hierarchy. In addition to specifying the names of the specific inclusion tags, it is also possible to specify * for instrumentation.templates.inclusion_tag in order to have usage of all inclusion tags be monitored: Enabling monitoring of all inclusion tags in this way is only recommended in development or test environments so as to get an initial idea of what inclusion tags are worth tracking. Once identified, the specific inclusion tags of interest should thereafter be listed individually in a production environment. Better monitoring of Django management commands Previously, the Python agent required you to manually set up the instrumentation for each specific Django management command in the agent configuration file. We have now made that easier by integrating the functionality as part of the agent itself. Due to the limitations on what Django management commands can be monitored, you will still need to list explicitly the commands you want monitored, but it can now be done in a single location as a space separated list under the setting instrumentation.scripts.django_admin of the import-hook:django section: By default, we automatically specify the startup timeout to be 10.0 seconds when monitoring the Django management commands. If you need to override the startup timeout, you can set the instrumentation.background_task.startup_timeout setting within the same import-hook:django configuration section.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-228026","eolDate":"2017-08-26"},{"agent":"python","date":"2014-08-25","downloadLink":null,"version":"2.26.2.24","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent is a hotfix release to prevent proxy credentials set in the agent configuration file from being transmitted to New Relic. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see Status of the Python agent . Bug fixes Previously, the agent stripped the proxy_user and proxy_pass settings when it transmitted configuration settings to New Relic, so as not to expose credentials. However, the proxy_host setting was transmitted unaltered, even if it was a URI containing a username and/or password. With this release, proxy usernames and passwords specified in a URI in the proxy_host setting are obfuscated before being transmitted. In addition, the proxy_user and proxy_pass settings are obfuscated, and are also transmitted.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-226224","eolDate":"2017-08-25"},{"agent":"python","date":"2014-08-20","downloadLink":null,"version":"2.26.0.22","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent includes improvements to browser monitoring , with the primary change being that the Python agent is now able to perform automatic browser monitoring for a wider range of Python web frameworks running on a traditional WSGI server. This includes popular web frameworks such as Flask, Pyramid and Bottle. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . New Features Prior to this version, automatic browser monitoring for HTML pages served up by a Python web application was only available if using the Django web framework. With this release this capability has now been expanded in most cases to cover any Python web framework being hosted on top of a web server with a direct interface for hosting Python WSGI applications. WSGI servers this covers include the popular Python web hosting packages Apache/mod_wsgi, gunicorn and uWSGI. Support does however not currently extend to Python web hosting mechanisms which provide a bridge to a WSGI application from a native Python web application API, such as is the case if using the Tornado or Twisted WSGI containers. What the change means is that if using a previously unsupported web framework such as Flask, Pyramid or Bottle, and you were not manually instrumenting your HTML page responses to make use of browser monitoring, you will now start to see automatically end user performance metrics being captured and displayed in the New Relic APM UI. You will also have access to the optionally enabled browser monitoring agent, enabling access to details of AJAX calls made by your pages and also the details of any client side Javascript errors which might have been raised. If you were previously manually instrumenting your HTML page responses to enable browser monitoring, you should in most cases now be able to discontinue such manual instrumentation. Note that at this time, in addition to lack of support for Tornado and Twisted WSGI containers, we do still have a few restrictions in place which mean we may not always be able to enable automatic browser monitoring support. The key restriction is that when using a web framework, the automatic support for browser monitoring will be disabled if you are using a middleware or plugin for the framework, which performs compression of responses, or which otherwise modifies the content encoding for the response. For example, automatic browser monitoring will still not be available if using the flask.ext.compress plugin with Flask, or the paste.gzipper middleware with any WSGI application. We are working on extending coverage to cases where such middleware or plugins are being employed, but if you are using them, for now you will still need to resort to manually instrumenting your responses to enable browser monitoring. The only exception to this is the Django web framework, where we already previously had support for automatic browser monitoring even if the Django GZipMiddleware was being used. For further details on the updated browser monitoring support and manually instrumenting your HTML page responses, see our documentation on page load timing when using the Python agent . If browser monitoring support is not currently enabled for your application or you need to disable it, then see our documentation on browser settings . Bug fixes/Improvements The agent was in some cases incorrectly inserting our instrumentation to HTML page responses which were marked as an attachment by way of a Content-Disposition HTTP response header or HTML page meta tag.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-226022","eolDate":"2017-08-20"},{"agent":"python","date":"2014-08-06","downloadLink":null,"version":"2.24.0.21","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent includes fixes related to tracking of external web service calls and minor improvements to automatic real user monitoring HTML insertion for Django. An offline developer mode has also be added to verify the operation of the agent with your application in a development or test environment. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . New Features An offline developer mode for the agent now exists to allow for verification that the operation of the agent will not affect the monitored web application in a development or test environment, without sending any actual data to New Relic. As it is an offline mode, no additional hosts will be recorded against your New Relic account for billing purposes. The offline mode does not allow for any viewing of collected metric information and other data for the purposes of monitoring your application, so it is not a solution for running New Relic locally. Being able to run it however, will allow you determine if a newer version of the agent, or an upgrade of any third party package in conjunction with the agent, will still function correctly before you jump to upgrading the packages in your production environment. The offline developer mode can be enabled by setting the developer_mode setting in the agent configuration file, or the NEW_RELIC_DEVELOPER_MODE environment variable, to true. Audit logging can also be enabled in conjunction with the offline developer mode so as to allow for the investigation of what data would be set to New Relic, resulting from the monitoring of your application, without actually sending any data to New Relic. Audit logging itself can be enabled by setting the the audit_log_file setting in the agent configuration file, or the NEW_RELIC_AUDIT_LOG environment variable. It is not recommended that audit logging be enabled for any extended period as the resulting log file will be quite large. Bug fixes/Improvements When using the Bottle web framework, the setting error_collector.ignore_status_codes, for ignoring exceptions linked to specific HTTP response status codes, was being ignored in the case of using Bottle plugins and a plugin raised a HTTPError exception. This only affected Bottle versions 0.11 or higher. The New Relic feature for cross application tracing  between two monitored web applications was not working when a Python web application was using recent versions of the urllib3 and requests modules for initiating the call to the backend web application service. This affected version 1.8 or higher of urllib3 and version 2.3.0 of the requests module. External web service calls were not being monitored when using the prepared requests  feature of the requests module directly. When using the urllib or urllib2 modules, if a URI of the form file://..., corresponding to a local file on the file system, was passed to any function monitored by our instrumentation, a metric and transaction trace node were being generated corresponding to an external web service with host name of 'unknown'. The instrumentation now correctly filters out URIs which do not correspond to an actual remote web service. The automatic means for inserting page load timing  tracking code for real user monitoring (RUM) into HTML page responses returned from a Django application now works no matter the case used for HTML elements. Previously automatic insertion would only be performed where HTML elements were lower case. RUM tracking code inserted automatically into HTML page responses from Django is now more optimally placed when a X-UA-Compatible meta tag appeared in the head element of the HTML page. Previously the RUM code was placed at the end of the head element when such a meta tag existed. This would have meant that page loading times would not have accurately reflected time spent in loading assets from any script elements appear after the meta tag. The RUM code is now placed immediately after the meta tag. Placement is not done before the meta tag as some browsers require that the meta tag appear prior to any script elements. RUM tracking code inserted automatucally into HTML page responses from Django is now placed after any Content-Type meta tag which also contains a charset attribute. This is necessary as some browsers will not recognise such a meta tag if it does not occur early in the page content. If a script tag was therefore placed before this meta tag it could have resulted in the meta tag being pushed down sufficiently far enough in the page content so as not to be recognised. Data corresponding to a long running transaction monitored by the a…","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-224021","eolDate":"2017-08-06"},{"agent":"python","date":"2014-07-01","downloadLink":null,"version":"2.22.1.20","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent is a hot fix release to address an issue introduced in version 2.22.0.19 when applying additional function traces from the agent configuration. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . Bug fixes: When using the transaction_tracer.function_trace setting in the agent configuration file to apply additional function traces, the trace was not being applied and a message indicating an instrumentation error would appear in the Python agent log file. The error in itself would not have prevented the agent from starting and running, but no data would be collected for the designated functions as intended.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-222120","eolDate":"2017-07-01"},{"agent":"python","date":"2014-06-24","downloadLink":null,"version":"2.22.0.19","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent introduces a means to enforce High-security mode from the agent configuration, as well as enabling capture of Insights events for background tasks. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . New Features: Insights events are now also recorded for background tasks, in addition to the existing events already captured for web transactions. The application to record an exception against can now be explicitly provided using the keyword argument application when calling newrelic.agent.record_exception(). This enables the ability to record exceptions outside of the context of a monitored web transaction or background task. A suitable application object can be retrieved using newrelic.agent.application(). Features Changed: Enforcing High-security mode from the agent configuration 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 an SSL connection to be used. Prevents capture of request parameters. Suppresses capture of custom parameters. The default setting for High-security mode is false. If you already have high-security mode enabled within the New Relic APM UI, you will need to add: to your local agent configuration file. Or if using Heroku, set the NEW_RELIC_HIGH_SECURITY environment variable by running: When using the gunicorn WSGI server, the request URL which appears in transaction trace samples and error details will now be sourced from the RAW_URI variable passed by gunicorn in the WSGI environ dictionary. This will ensure that what is displayed is the raw URL before % escape sequences have been decoded. This avoids the problem of the URL being shown as a raw byte sequence. When audit logging is enabled, the responses returned from our data collector service will now also be logged. Bug fixes/Improvements: An incorrect module name was being derived for methods of classes, when used in web transaction and function trace naming, where the method was from a base class defined in a different module, but invoked via a derived class. When using Django class based views, if a class based view was used explicitly from within a view handler, the name of the class based view method was overriding the web transaction name, which at that point would have been set to the view handler. The class based view method name will now only be used for the web transaction name when it is actually registered as the view handler. Explain plans for SQL queries were not working when the SQL database cursor had been configured to return a dictionary rather than a tuple for each row set when the original query was made.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-222019","eolDate":"2017-06-24"},{"agent":"python","date":"2013-10-11","downloadLink":null,"version":"2.2.1.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent is a hot fix version to address a Celery instrumentation issue introduced with version 2.2.0.2. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directory from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . Bug fixes/Improvements: Fixed bug with Celery instrumentation introduced with version 2.2.0.2 of the agent. The bug was causing a Python exception to be raised when the instrumentation was trying to derive the task name to use as the name of the background task.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-2213","eolDate":"2016-10-11"},{"agent":"python","date":"2013-10-11","downloadLink":null,"version":"2.2.0.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent is an incremental release and includes minor feature changes and enhancements. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directory from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . New Features: Use of HTTP proxies over SSL using the HTTP CONNECT tunnelling mechanism is now supported. Set the 'proxy_scheme' to 'http' to invoke this mode. This will become the default in a future version of the agent. If migrating from an older agent version and need to keep the existing behaviour going forward, set 'proxy_scheme' to 'https'. Alternatively, ensure you provide the scheme in the form of a URI as part of the 'proxy_host' setting. Added request queueing support to the instrumentation for the Tornado ASYNC framework. Request queueing times should start showing in the APM Overview page when a frontend web server such as Nginx, has been configured to add the appropriate headers. For more details see our documentation on setting up tracking of queueing time . The 'newrelic.agent.record_exception()' can now be called without actually passing it any exception details. In this case, the details of any current exception being handled will be used instead. Added a new mechanism for automatic discovery of third party instrumentation modules as an alternative to having to list them explicitly in the agent configuration file. Any such instrumentation module should register entry points under the 'newrelic.hooks' group in 'setup.py' for that package. The entries should be of the form 'target-module = instrumentation-module:function'. When the 'target-module' is imported, the function 'instrumentation-module:function' will be executed and passed the module. Any instrumentation module should then use functions provided by our agent API under 'newrelic.agent' to instrument the module as necessary. Bug fixes/Improvements: When using the CherryPy web framework, the NotFound, InternalRedirect and HTTPRedirect exceptions if raised are now ignored and not treated as errors. When using the Pyramid web framework, if a view could not be found to handle a request, it could cause the agents' Pyramid instrumentation to fail, causing an exception. When using the Pyramid web framework, the PredicateMismatch exception if raised when trying to resolve a URL to a view handler is now ignored and not treated as an error. Updated the instrumentation for the pywapi module to drop support for the now discontinued Google weather API. Overhauled the mechanisms used to wrap instrumentation around functions to be monitored. When the agent is installed, if the optional C extension module can be compiled and installed, then the new wrappers should have a reduced overhead compared to the pure Python versions of the wrappers otherwise used. Running thread profiles on coroutine (gevent/eventlet) based systems no longer cause a timeout in the UI. Although the UI now no longer times out, as explained in our status of the Python agent  documentation, we still however do not generate any results when running thread profiling on coroutine based systems.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-2202","eolDate":"2016-10-11"},{"agent":"python","date":"2014-06-13","downloadLink":null,"version":"2.20.1.18","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent addresses a bug which in some cases caused database connection parameters, which could include login credentials, to be logged to the local system by the monitored application if Python agent debug logging is being captured. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . Bugs Fixed When Python agent debug logging was enabled by setting log_level to debug in the Python agent configuration, database connection details, including login credentials could be logged in the local Python agent log file. The details may also have been logged even if log_level had not been set to debug, but the Python logging module had been configured to collect and log messages logged at the log level of logging.DEBUG. This issue was introduced in version 2.20.0.17 of the Python agent.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-220118","eolDate":"2017-06-13"},{"agent":"python","date":"2014-05-29","downloadLink":null,"version":"2.20.0.17","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent provides various improvements to database client module instrumentation and execution of explain plans. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent, see our online help article on the status of the Python agent . New Features Added a 'license-info' command to the 'newrelic-admin' script for displaying the LICENSE file for the 'newrelic' package. Bug fixes/Improvements: The bottle instrumentation was causing a secondary exception when a web request was not actually being monitored and an un-handled exception occurred in the web request. Added support for accepting additional arguments to the execute() method of database cursors implemented by the oursql and cx_Oracle modules which are not covered by the Python DBAPI 2 (PEP 249) specification. The time taken for connect() calls of database client modules will now be counted in Database  time (on the APM Overview page). The automatic rollback or commit performed on exit of the context manager for a database connection was not being monitored and reported when using the psycopg2, psycopg2cffi and postgresql database client modules for the PostgreSQL database. Improved how database connections are managed when performing explain plans and also applied caps to the number of process wide explain plans that are done in each reporting period. This should have the result of reducing overhead in situations where there was a large number of candidate SQL statements on which to perform explain plans. Any additional overhead from the agent in the past would have been most notable when performing an X-Ray session against a key transaction.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-220017","eolDate":"2017-05-29"},{"agent":"python","date":"2014-03-28","downloadLink":null,"version":"2.18.1.15","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent adds improved audit logging functionality and an admin script sub command for recording deployments. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . New Features Record Deployments : A new 'record-deploy' sub command has been added to the 'newrelic-admin' script installed with the Python agent. This is a wrapper around the HTTP API provided by New Relic for recording deployments  against your application. To use the sub command, add your API-KEY in the agent configuration file under the 'api_key' setting. The path to the config file, description for the deploy and optional revision, change log and user information can then be supplied as arguments to the sub command. Audit Logging : An improved audit logging feature has been added to the agent for capturing details of what is being sent up to our data collectors. Information is now captured into a separate log file in a more human-readable format to aid any review process carried out to determine what the agent is sending. The audit logging feature can be enabled by setting the the 'audit_log_file' setting in the agent configuration file, or the 'NEW_RELIC_AUDIT_LOG' environment variable. It is not recommended that audit logging be enabled for any extended period as the resulting log file will be quite large. Bug fixes/Improvements: The agent now ensures that the certificate bundle packaged with the agent is always used when certifying SSL connections back to our data collector. Previously the location of the certificate bundle could be overridden by a number of environment variables. This could cause SSL connection failures when the referenced certificate bundle didn't exist or had incorrect permissions and could not be accessed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-218115","eolDate":"2017-03-28"},{"agent":"python","date":"2014-03-05","downloadLink":null,"version":"2.16.0.12","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent adds obfuscation of explain plans as the default when using PostgreSQL, as well as including bug fixes related to the instrumentation for some MySQL database client modules. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . Bug fixes/Improvements: Fixes an agent bug with PostgreSQL where parameters from the original query could appear in explain plans sent to New Relic servers, even when SQL obfuscation was enabled. Parameters from the query are now masked in explain plans prior to transmission when transaction_tracer.record_sql is set to 'obfuscated' (the default setting). The automatic rollback or commit performed on exit of the context manager for a database connection was not being monitored and reported when using the MySQLdb, pymysql and oursql database client modules for the MySQL database.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-216012","eolDate":"2017-03-05"},{"agent":"python","date":"2014-02-17","downloadLink":null,"version":"2.14.0.11","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent adds support for the Cornice REST component library for the Pyramid web framework, as well as a number of minor feature improvements and bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . New Features: Instrumentation added for the Cornice REST component library for the Pyramid web framework. Bug fixes/Improvements: Enhance the instrumentation for the Bottle web framework to work around the problem that the Bottle framework was not using 'functools.wraps()' correctly in the implementation of its 'auth_basic()' decorator. This was resulting in the web transaction being named after the 'wrapper' function closure used in the implementation of the decorator rather than the wrapped request handler the decorator was applied to. A pull request was made against the Bottle framework and the change will be included in a future version of Bottle. Our change ensures that the correct result is also obtained with older Bottle versions. When using the database connection object created by the sqlite3 database client module as a context manager, the automatic rollback or commit performed by the context manager when the scope of the context manager is exited, will now be tracked. If a function trace was applied to the bound method of a class implemented in a C extension module, the name of the module shown in the name of the function was being wrongly designated as the Python 'builtins' module. Updated memcache instrumentation wrappers to use our latest function wrapper implementation. Our latest function wrappers better preserve the ability to introspect wrapped functions/methods and so return the same result as one would expect if no wrapper had been applied.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-214011","eolDate":"2017-02-17"},{"agent":"python","date":"2014-02-03","downloadLink":null,"version":"2.12.0.10","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent includes improved instrumentation for the Bottle framework and new instrumentation support for gevent WSGI servers. It also allows reporting of data to multiple applications in New Relic to be specified via an environment variable, in addition to the existing 'app_name' setting in the agent configuration file. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . New Features: Provide automatic instrumentation of the WSGI application entry point when using the 'gevent.wsgi' and 'gevent.pywsgi' servers. This means that if you are not using a web framework we already support and instrument, are using a WSGI component library, or implementing your WSGI application from scratch, it is no longer necessary to wrap the WSGI application entry point with our special decorator or wrappers when using the gevent WSGI servers. Features Changed: Previously it was only possible to list multiple applications in New Relic to report data to via the 'app_name' setting in the agent configuration file. Attempting to list multiple application names (separated by the requisite semi colon), in the 'NEW_RELIC_APP_NAME' environment variable was ignored with the complete value (including semi colons), being used as the application name. This limitation has now been lifted and a list of applications to report to can now be specified using the 'NEW_RELIC_APP_NAME' environment variable. Bug fixes/Improvements: The instrumentation for the Bottle web framework has been improved. The changes include the request handler now being broken out properly as a separate item in the transaction breakdown, the web transaction being named after an error handler when appropriate and requests which could not be mapped to a request handler being named as being a 404 if no error handler was provided. Handling of exceptions for HTTP errors has also been improved and are now being correctly matched against our internal list of HTTP status codes to be ignored as exceptions. Previously the instrumentation was too liberally ignoring all HTTP error exceptions. When using the Flask web framework, a NotFound exception raised within the underlying Werkzeug library was not being ignored. It is now no longer necessary to explicitly ignore the exception type 'werkzeug.exceptions:NotFound' in the agent configuration. When an unhanded exception was raised by a Pylons application, a bug in the implementation of the agent's error trace wrappers would cause a subsequent exception to be raised from the agent itself, masking the details of the original exception. When trying to determine how much memory was available on a system, the agent would fallback to trying to the use the 'psutil' module, if installed, if our standard ways of checking failed. This would cause the agent to fail on a PaaS such as PythonAnyWhere, which prohibits access to the /proc filesystem. Use of 'psutil' as a fallback has now been removed to avoid any potential for a failure. The version of the bundled 'requests' module the agent used to perform HTTP requests to our data collector did not work with Python 2.6.2 or older. A fix to 'urllib3' used by the 'requests' module has been back ported to address the issue. Our updated database instrumentation wrappers released in the last agent version, would incorrectly return that a database connection or cursor object were callable. This could confuse code which was trying to introspect those objects to perform traversal in order to get access to inner details of the implementation of the database modules.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-212010","eolDate":"2017-02-03"},{"agent":"python","date":"2018-03-07","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.106.1.88","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent includes a fix for security bulletin nr18-07 . The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-2106188","eolDate":"2021-03-07"},{"agent":"python","date":"2018-02-28","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.106.0.87","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for AIOHTTP version 3. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Improved AIOHTTP Support Support for AIOHTTP 3 AIOHTTP major version 3 is now supported by the New Relic Python agent.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-2106087","eolDate":"2021-02-28"},{"agent":"python","date":"2018-02-20","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.104.0.86","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds a deprecation warning for customers that disable SSL, and adds bugfixes for supported async frameworks that use asyncio. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Mandatory SSL Disabling SSL connections to New Relic has been deprecated SSL connections are enabled by default. In a future release, the option to disable SSL will be removed. Bug Fixes Using asyncio.gather or asyncio.ensure_future now tracks transaction context Prior to this release, using asyncio.gather or asyncio.ensure_future may result in certain traces (such as external calls) not being reported in the transaction. Traces scheduled with asyncio.gather or asyncio.ensure_future from within the context of a transaction should now be properly attributed to the transaction.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-2104086","eolDate":"2021-02-20"},{"agent":"python","date":"2018-02-05","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.102.0.85","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent contains improvements to the time tracing API as well as bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Time Trace API Improvements Time trace APIs (such as function_trace) can now be used with coroutines The following decorator APIs can now be used with native coroutines and generators: function_trace database_trace datastore_trace external_trace message_trace memcache_trace Example: Bug Fixes gRPC instrumentation used on Python 2.x can cause a memory leak When using gRPC on Python 2, gRPC futures would not be garbage collected resulting in a memory leak. gRPC futures will now be garbage collected. Instrumentation for Dropbox v8.0 and newer caused error log messages Dropbox client version 8.0 or higher raised instrumentation errors. These errors did not prevent metrics on Dropbox from being sent. These errors have been removed. Values from negated ranges were sometimes added to ignore_status_codes Negated status codes not found in the current ignore_status_codes were added if they were part of a range of values. This issue has been addressed.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-2102085","eolDate":"2021-02-05"},{"agent":"python","date":"2014-01-24","downloadLink":null,"version":"2.10.1.9","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent is a hot fix version to address an issue related to cross process application traces  introduced in 2.10.0.8. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directory from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . Bug fixes/Improvements: The value of headers inserted into the HTTP response returned from the WSGI application to support cross process application tracing were being incorrectly passed as Unicode strings on Python 2. This would cause a strictly compliant WSGI server such as Apache/mod_wsgi or uWSGI to raise an error when the headers were being set. In general, pure Python WSGI servers are not as strict in their WSGI compliance and would have silently accepted the value anyway, converting it to a byte string using the Python system default encoding.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-21019","eolDate":"2017-01-24"},{"agent":"python","date":"2014-01-17","downloadLink":null,"version":"2.10.0.8","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent includes various improvements and bug fixes related to instrumentation for database client modules, as well as a notable fix to our 'newrelic-admin' script affecting some users who referenced Python virtual environments via a symbolic link. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . New Features: Instrumentation of the WSGI application entry point will now add a new breakdown metric to web transactions corresponding to the finalization of the WSGI request. Within the workings of the interaction between the WSGI server and the WSGI application, this is the point at which the WSGI server will call any close() method on the iterable returned by the WSGI application. The name of this new breakdown metric is 'WSGI/Finalize'. In the case where there was actually a 'close()' method, a further breakdown metric will also appear corresponding to that method. Added support to instrumentation for MySQL and PostgreSQL database client modules for monitoring database queries when the database connection object is used as a context manager. Such context manager features are outside of the scope of the Python DBAPI2 (PEP 249)  specification, not all database client modules support it and nor do they all work the same. Although supported, we would suggest consideration should be given to not using these context manager features if you need your code to be portable between databases. Added support to instrumentation for MySQL database client modules for monitoring database queries when the database connection object was created using the Connect() function. The Connect() function falls outside of the scope of the Python DBAPI2 (PEP 249)  specification. Although supported, we would suggest consideration should be given to not using this Connect() function if you need your code to be portable between databases. Added database instrumentation support for the mysql-connector-python  database client module. Custom parameters for a transaction which are a string or numeric value will now be added to and reported with analytic events reported to our analytics system code named Rubicon . This can be disabled using the agent configuration setting 'analytics_events.capture_attributes'. The capture of custom parameters against a transaction trace can now be disabled using the agent configuration setting 'transaction_tracer.capture_attributes'. The capture of custom parameters against error details can now be disabled using the agent configuration setting 'error_collector.capture_attributes'. Features Changed: The agent API function add_user_attribute() is now deprecated and functionality merged with the add_custom_parameter() function. The latter function should now be used instead. The display of such parameters in browser traces is now optionally enabled with the agent configuration setting 'browser_monitoring.capture_attributes'. Bug fixes/Improvements: If the 'newrelic' package was installed into a Python virtual environment, but the 'newrelic-admin' script was executed via a path that traversed a symlink to the virtual environment, the protections within the agent bootstrapping procedure was detecting that the agent was trying to be used with an application running against a different virtual environment when it was actually the same. This would result in the application not being monitored. This issue was introduced in version 2.8.0 of the agent when additional protections were added against mixing application/modules from different Python virtual environments. Explain plans were not being performed on SQL queries made via the executemany() method of a database cursor object. When explain plans are now done, the data inputs from the first row of input data for the executemany() call will be used. When using Python 2, if strings were supplied for the web transaction name, custom parameters, in error details etc, and that string contained a series of characters which could not be decoded as valid UTF-8, then an exception would occur. In the case of a web transaction name, this could result in the exception affecting the current web transaction and result in an error response being sent back to a user. For the case of a transaction trace or error details, the exception would prevent the sending of the captured data up to our data collector and it would be discarded. This was a regression within the agent behaviour introduced when Python 3 support was added to the agent. Fixed instrumentation for sqlite database modules which could result in instrumentation not being applied correctly, and so no database metrics coll…","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-21008","eolDate":"2017-01-17"},{"agent":"python","date":"2018-01-09","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"2.100.0.84","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent contains security related updates as well as bug fixes. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directly from the New Relic download site . Security Updates See the associated security bulletins for custom API parameters in high-security mode  and for SQL params for SQLite . Bug Fixes Using the aiohttp client may result in an application crash Under certain circumstances, using the aiohttp client may have resulted in an application crash. This issue has been addressed. Database queries made with psycopg2 may not have been recorded When using the \"with\" statement to create a cursor, time spent on database calls may not have been properly recorded. This issue has been addressed. Usage of the pika library resulted in a memory leak When using the pika library with New Relic, Channel objects would not be cleared from memory as expected. This would result in abnormally high memory utilization in some cases. The memory leak has now been fixed. DeprecationWarning generated for async/await keywords Using the agent may have generated a DeprecationWarning around async/await being reserved keywords. The DeprecationWarning should no longer be generated.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-2100084","eolDate":"2021-01-09"},{"agent":"python","date":"2013-09-04","downloadLink":null,"version":"2.0.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent is a major new version and primarily focuses on the addition of support for Python 3. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directory from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . New Features: Python 3.3 or later is now supported. This includes support for popular web frameworks that have been ported to Python 3, such as CherryPy, Django, Flask, Pyramid and Tornado. Added new instrumentation to track as external service calls, requests made by the 'thrift' client module. Added new instrumentation to track memcache calls made by the 'bmemcached' client module. Features Removed: Python 2.5 is no longer supported. The minimum required Python version is now 2.6. If using Python 2.5, you should ensure that any requirement for the 'newrelic' module listed in a 'setup.py' or pip requirements file says 'newrelic<2.0.0.0'. Bug fixes/Improvements: Fixed broken instrumentation for 'httplib' module, which would cause an exception where the 'httplib' connect() method was being invoked via the Connection class type rather than an instance of the Connection class. Fixed issue where if the host system clock was wound backwards, then the response time of active requests could be set as being zero, resulting in a ZeroDivisionError when calculating thread utilization. Fixed issue where the use of SSL via a HTTP proxy by the agent to connect to the New Relic data collector to report data would fail. Fixed broken instrumentation for sqlite database client module which resulted in the executescript() API call failing. Add workaround for uWSGI issue where when using gevent mode of uWSGI, it would attempt to wait on all greenlets on process shutdown, instead of only on non daemon threads, specifically the request threads. The issue was causing processes to hang for 60 seconds on shutdown before the uWSGI master process killed the process. We are in discussion with uWSGI authors about a permanent fix to uWSGI.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-2001","eolDate":"2016-09-04"},{"agent":"python","date":"2012-12-19","downloadLink":null,"version":"1.9.0.21","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: This release of the Python agent addresses an issue with under reporting of memory use on Linux, as well as other minor bug fixes and enhancements. For a list of known issues with the Python agent see our online help article on the status of the Python agent . New features: Added support for automatically wrapping the WSGI application entry point when using the Paste HTTP server. Custom metrics can now be reported via the public agent API by supplying an appropriate application object as an additional argument to 'newrelic.agent.record_custom_metric()'. Added support for the 'psycopg2ct' database client module for PostgreSQL. When needing to communicate via a firewall, the proxy settings can now be set via environment variables in addition to being able to be set in the agent configuration file. The number of CPU cores is now being reported in the agent environment and displayed in the UI. A warning will now be logged in the agent log file if an older version of uWSGI is being used which has bugs with its conformance to the WSGI specification. Such older uWSGI versions would see incorrect data being reported due to the bug in uWSGI. A warning will now be logged in the agent log file if uWSGI is being used and the 'enable-threads' option is not being supplied to uWSGI to enable threading within the Python interpreter, a feature which is a mandatory requirement for the Python agent to be able to work. A range of additional logging and debugging options have been added to allow our support team to better help you when you are having issues with setting up the agent. Bug fixes/Improvements: Addressed problem where memory usage was being under reported on Linux systems. The degree to which memory usage was under reported was dependent on the memory page size the system was using. If affected you can expect to see memory usage being reported jump up as it reports the correct value. If the local Python installation is already using a 'sitecustomize.py' file, the agent's own 'sitecustomize.py' file will ensure that the existing copy is imported and code in it executed so that existing definitions are still applied. Installation of the agent could fail under buildout due to a missing Python future import for the Python with statement under Python 2.5. Made parsing of URLs more tolerant to malformed URLs in web external calls. The agent was encountering an error when the port number of a URL was not an integer, resulting in the data for that transaction being discarded. Use of raw greenlets from within a transaction was failing causing an exception and the users web request to typically fail with a HTTP 500 error response. Configuration of the agent will no longer fail on startup if there is no 'newrelic' section in the configuration file.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-19021","eolDate":"2015-12-19"},{"agent":"python","date":"2012-11-14","downloadLink":null,"version":"1.8.0.13","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: This release of the Python agent enables the ability to set apdex values and alerts for key transactions (discussed here ) For a list of known issues with the Python agent see our online help article on the status of the Python agent . New features: Added support in the agent required to enable apdex values to be specified for key transactions. Added support for tracking SQL database queries when using the 'oursql' database client module for MySQL. Bug fixes/Improvements: The sqlite3 instrumentation was preventing the use of a sqlite3 database connection object as a context manager together with the 'with' statement. Suppressed the logging produced by the urllib3 module included within the bundled requests module, when making socket connections.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-18013","eolDate":"2015-11-14"},{"agent":"python","date":"2012-11-07","downloadLink":null,"version":"1.7.0.31","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: This release of the Python agent focuses on providing a low-overhead thread profiler which can monitor and record executing threads for a specified time, without affecting the customer experience. For a list of known issues with the Python agent see our online help article on the status of the Python agent . New features: Low-overhead thread profiler. A profiling session can be initiated for a period from 2 to 10 minutes. The profiler will periodically sample what all the executing threads are doing, aggregating the results together to get a statistical snapshot of where in your application most time is being spent. Bug fixes/Improvements: Importing of the greenlet module was resulting in the capacity analysis report metrics being disabled, even though it was meant to only be disabled when specifically using a coroutine based WSGI server such as gevent and eventlet mode of gunicorn. Improvements to the instrumentation wrapper applied to the Django view handler function so that code which tries to compare the view handler to an expected value should work. Note that this is dependent upon using an equality test rather than an identity test. Reverted prior change which stripped the instrumentation wrapper from the Django view handler when it was passed to any Django view middleware. Improvements to the instrumentation wrapper should remove the need to do this. Having the view handler passed in with the wrapper applied is required to ensure that calls to the view handler are tracked properly where the view handler is called from within the view middleware. Although not strictly required due to improvements to the instrumentation wrapper applied to a Django view handler, strip the wrapper when a view handler is passed into django.core.urlresolvers.reverse() function to ensure it can correctly determine the URL mapping to the view handler. Disable automatic RUM header/footer insertion when using Django 1.5 and the new streaming HTTP response object is returned. This is being disabled so that the response is not buffered, thereby interfering with the streaming process. If streaming a HTML response and RUM reporting is still required, the RUM header and footer will need to be added manually . Instrumentation of the feedparser module was causing an exception when a file like object rather than a string was passed to the feedparser.parse() function. Tastypie instrumentation was failing to be applied if using Python 2.5.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-17031","eolDate":"2015-11-07"},{"agent":"python","date":"2012-10-16","downloadLink":null,"version":"1.6.0.13","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: This release of the Python agent is a minor feature and bug fix release. For a list of known issues with the Python agent see our online help article on the status of the Python agent . New features: When reporting web application performance data against multiple applications in the New Relic UI at the same time, any end user metric data will now also be reported against all applications. Previously end user metric data would only be reported against the first application. The environment variable 'NEW_RELIC_SSL' can now be set to enable use of a SSL connection when reporting data to our data collector. Enabling values are 'true', 'on' or '1'. This can be used on platforms such as Heroku where configuration is performed using environment variables instead of an agent configuration file. Added instrumentation for tracking database queries when using the 'pymysql' module for the MySQL database. Bug fixes/Improvements: Fix to algorithm calculating name of function for case where function was wrapped with a decorator implemented using a class. Previously was using the name of the decorator class rather than the name of the wrapped function. Fix for ZeroDivision error when calculating per request CPU burn, where due to clock granularity for system the request was quick enough to effectively have zero duration. Fix for AttributeError when trying to process None as a slow transaction trace when in a harvest period there were browser traces but no application server traces.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-16013","eolDate":"2015-10-16"},{"agent":"python","date":"2012-09-04","downloadLink":null,"version":"1.5.0.103","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: This release of the Python agent contains capacity analysis reporting, an improved sampling algorithm to ensure a wider sampling of slow transactions and added support for TastyPie, dropbox and facepy modules. For a list of known issues with the Python agent see our online help article on the status of the Python agent . New features: Enable capacity analysis reporting where web application is single threaded or multithreaded (but not coroutine based system such as gevent and eventlet). This report helps you determine if you have enough instances deployed to keep up with request load and so tune your configuration for optimal performance. Criteria by which slow transaction samples are captured has been changed so as to include slow transactions for a broader range of transactions. Previously the transaction with the slowest overall response time would always be captured and reported. Whether a specific transaction will be preserved as a sample of a slow transaction will now also depend on whether a recent slow transaction had already been captured for it and give preference to recording slow transactions for a different transaction, rather than the same transaction all the time, if it is always the slowest. Where TastyPie is being used with Django, instead of all web transactions being handled by TastyPie being labeled against the TastyPie wrapper, the web transactions will now be aggregated against the specific methods of the resource or API object handling the request. Added instrumentation for the 'dropbox' Python module to track time spent calling out to the DropBox web service. A call to this web service would have been tracked previously by virtue of the 'dropbox' module internally using the 'httplib' module. This added instrumentation however makes the data collected more accurate as will properly track time spent sending the request and receiving the response. It will also attribute the call to the 'dropbox' module in transaction traces and performance breakdown data. Added instrumentation for the 'facepy' Python module to track time spent calling out to the Facebook web service. A call to this web service would have been tracked previously by virtue of the 'facepy' module internally using the 'requests' module. This added instrumentation however allows the call to be attributed to the 'facepy' module in transaction traces and performance breakdown data. Added support for gevent < 0.13.7 by way of patching an existing bug in gevent. The specific problem in gevent was patched in version 0.13.7 of that package. This change will allow older versions of gevent to also be used if there is a requirement. Bug fixes/Improvements: Instrumentation for Genshi templates was failing when the OR operator was used inside of a template. If an exception occurred in the first call to read data from wsgi.input to get the request content, it would cause a subsequent exception when recording of response time was being finalised. This wasn't causing any impact on user requests, but would result in any metrics for that request being discarded and an error being logged in the agent log.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-150103","eolDate":"2015-09-04"},{"agent":"python","date":"2012-08-01","downloadLink":null,"version":"1.4.0.137","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: This release of the Python agent introduces a number of new features including improvements to RUM browser traces. Performance of the agent has also been improved though reducing some of the overheads when dealing with tracking SQL database queries. For a list of known issues with the Python agent see our online help article on the status of the Python agent . New features: The agent now collects additional application tier transaction trace samples for slow transactions and will correlate them with any corresponding RUM browser trace . Slow transaction traces will now show a figure corresponding to the amount of CPU burn that occurred during the period the transaction was running. This can be used to get an indication of whether code being executed was CPU intensive or principally waiting on I/O. Slow transaction traces for web requests will now provide an indication of how many concurrent requests were executing at the same time in the process the request was being handled. This can be used to determine how busy the process was at that time, but would also be used in conjunction with the recorded CPU burn to determine whether CPU burn was all from the one transaction or could also be due to parallel executing web requests in a multithreaded application. Note that this measure is dependent on an optional C extension component of the agent being able to be installed at the time of installation of the agent. Slow transaction traces for web requests will now display information about the amount of request content read and the amount of response content generated. This will include details about what methods of 'wsgi.input' were used to read content and how long it in total took to read the request content. Similar details are also provided about how response content was generated and how long it took from start to finish. Slow transaction traces for web requests will now display the value of any frontend queueing time within the server stack which pertained to that specific request. Note that this is dependent on the server stack having being configured to introduce the required header  to allow queueing time to be measured. The Python agent recognises the 'X-Queue-Start' header. Automatic support is now provided for tracking frontend queueing time within the server stack when an application is deployed to Heroku. An API call and means via the WSGI environ dictionary is now provided for indicating that a transaction should not be a candidate for slow transaction traces. This is to allow one to ignore transactions which are known to always be slow. The API call is 'newrelic.agent.suppress_transaction_trace()'. Calls to Django APIs for sending emails will now be tracked in the performance breakdown for transactions, as well as being displayed in slow transaction traces. Support for Celery 3.0. Bug fixes/Improvements: Overheads within the agent which could affect performance of the application have been reduced. The improvements specifically revolve around the processing of SQL database queries. This is principally to address larger than expected overheads seen by a very small subset of users which had large or more complicated SQL queries. The changes could though still result in a small general reduction in overhead and CPU usage directly attributable to the monitoring down by the agent when SQL database queries are being tracked. Where it is possible to build C extension components at the time the agent is installed, optional C speedups for JSON will now be installed. This reduces the overhead of JSON encoding when data is being sent by the agent to the New Relic data collector on each one minute harvest cycle. If the C extension cannot be compiled, the agent will fall back to using pure Python code as it has done in prior versions of the agent. Django instrumentation has been improved and issues addressed with the way that instrumentation wrappers were applied to view handlers. For example, when a view handler is passed to a view middleware, any instrumentation wrapper is now removed. This is because the wrapper could cause issues for some code which tried to do a direct comparison between the view handler passed and an expected value. It is believed this change will fix issues when using Mezzanine. A sporadic issue with the data collector rejecting uploaded data due to what it believes was malformed JSON should be addressed. This was due to some metric values being aggregated as integers rather than as float values. This resulted in overflow of 64 bit values in the data collector due to Python supporting arbitrary length integers and thus being able to send values larger than 64 bits. The agent will now no longer fail on import when -OO option is used with the Python interpreter to enable highest level of optimisation. This was an i…","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-140137","eolDate":"2015-08-01"},{"agent":"python","date":"2026-08-20","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"13.5.0","features":["Add support for Azure CosmosDB","Add support for HTTPX2","Add LangChain/LangGraph streaming events instrumentation","Add support for newer OpenTelemetry database semantic conventions"],"bugs":["Fix incomplete package reporting to New Relic","Reduce overhead of package version lookups","Fix get_linking_metadata to properly pass through the specified application","Fix MySQL database name reporting when using the database keyword argument","Fix warning when accessing LangGraph v1.1+ GraphOutput values"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Azure CosmosDB, adds instrumentation for HTTPX2 and new LangChain/LangGraph streaming events APIs, adds support for newer OpenTelemetry database semantic conventions, and resolves several issues including incomplete package reporting, a package lookup performance penalty, and a MySQL database name reporting bug. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . New features Added support for Azure CosmosDB The Python agent now instruments Azure Cosmos DB  client operations, reporting datastore metrics and traces for database, container, and user operations performed through the azure-cosmos SDK. Added support for HTTPX2 The Python agent now supports HTTPX2 , a fork of HTTPX  actively maintained by the Pydantic team. External call instrumentation for HTTPX2 mirrors the agent's existing HTTPX support for both synchronous and asynchronous clients. Added LangChain/LangGraph streaming events instrumentation Added astream_events instrumentation support for LangChain  agents. Added stream_events/astream_events instrumentation for LangChain /LangGraph  v3, covering iteration over GraphRunStream objects. Added support for newer OpenTelemetry database semantic conventions When running the Python agent alongside OpenTelemetry (Hybrid Agent mode), the agent now reads both the legacy and newer OpenTelemetry database span attribute names (db.name/db.namespace, db.statement/db.query.text, db.mongodb.collection/db.collection.name), so database tracing continues to work correctly regardless of which semantic convention version the OpenTelemetry instrumentation library emits. Bugs Fixed incomplete package reporting to New Relic Previously, the Python agent could omit some installed packages from the Environment data reported to New Relic if module discovery took longer than the fixed time window allotted during the slow harvest cycle, and the package list wasn't refreshed after an agent restart. Package capture now runs during the fast harvest cycle and is fully re-captured on agent shutdown/restart, so the reported package list is complete. Reduced overhead of package version lookups Previously, looking up installed package versions rescanned the filesystem for every package on every lookup, incurring an O(n^2) time penalty that scaled with the number of installed packages during agent initialization. The result of importlib.metadata.packages_distributions() is now cached after the first lookup to avoid this overhead. Fixed get_linking_metadata to properly pass through the specified application Previously, calling newrelic.agent.get_linking_metadata(application=...) ignored the application argument and always returned linking metadata for the default application. This affected processes reporting to more than one application. The specified application is now correctly passed through. Thank you ckarnell  for the contribution! Fixed MySQL database name reporting when using the database keyword argument Previously, the agent only checked the legacy db keyword argument when parsing the database name from mysql-connector-python  connection arguments, so connections made using the modern database keyword argument reported no database name in datastore metrics. The agent now checks database first, falling back to db. Fixed warning when accessing LangGraph v1.1+ GraphOutput values Previously, LangGraph  v1.1+ instrumentation accessed GraphOutput return values using deprecated item-access syntax, triggering a deprecation warning. The agent now reads GraphOutput.value directly. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-130500","eolDate":"2027-08-20"},{"agent":"python","date":"2026-07-30","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"13.4.0","features":["Add Redis commands introduced in Redis v8.10.0 and redis-py v8.1.0"],"bugs":["Fix missing LlmChatCompletion events in Gemini when using tools","Swap to trace cache ID in LangChain and AgentFramework"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Redis commands introduced in Redis v8.10.0 and redis-py v8.1.0. This release also resolves the issue of missing LlmChatCompletion events in LangChain when using MCP tools. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . New features Added Redis commands introduced in Redis v8.10.0 and redis-py v8.1.0 The Python agent now supports the following recently added commands in Redis : himport_discard_all himport_discard himport_prepare lmovem nrange nrevrange querylabels read sdiffcard sunioncard aliaslist Bugs Fixed missing LlmChatCompletion events in Gemini when using MCP tools Previously, LlmChatCompletionMessages and LlmChatCompletionSummary events were missing in Gemini  when using tools in a LangChain  agent, if the response format was not the default JSON.  This has been resolved. Swapped to trace cache ID in LangChain and Agent Framework For context propagation purposes, swap the LangChain  and Agent Framework  instrumentation to only store the trace cache ID rather than the full trace in a reference attribute. This is to prevent these objects from getting serialized unexpectedly in the case of leaks. The ID is a much smaller object while the trace could contain MBs of data. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-130400","eolDate":"2027-07-30"},{"agent":"python","date":"2026-07-23","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"13.3.0","features":["Add support for AI Monitoring server-side configuration","Add context propagation for Bedrock invocations through Microsoft Agent Framework"],"bugs":["Fix inconsistent transaction names when using Wagtail","Fix duplicate tool entities for LangChain tools backed by a remote MCP server","Fix missing User Input field for LangChain and LangGraph MCP tool calls","Reduce race condition risk in the garbage collection data sampler","Remove byte encoding from outbound Kombu distributed tracing headers"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for AI Monitoring server-side configuration, adds context propagation for Bedrock invocations made through Microsoft Agent Framework , fixes duplicate tool entities for LangChain  tools backed by a remote MCP server, reduces race condition risk in the garbage collection data sampler, fixes inconsistent transaction names when using Wagtail , and removes byte encoding from outbound Kombu  distributed tracing headers. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . New Features Add support for AI Monitoring server-side configuration The Python agent now supports server-side configuration  of AI Monitoring. When configured, the server-side ai_monitoring.enabled, ai_monitoring.record_content.enabled, and ai_monitoring.streaming.enabled values take precedence over the local settings. Add context propagation for Bedrock invocations through Agent Framework Propagates trace context across thread boundaries created by Microsoft Agent Framework 's Bedrock integration. This allows the agent's existing botocore  instrumentation to capture LLM events for Bedrock invocations made through Agent Framework. This does not add full instrumentation of Agent Framework itself. Bugs Fix inconsistent transaction names when using Wagtail Previously, transaction names for apps built on Wagtail  were inconsistent and could be the same for different page views. This has been fixed. Fix duplicate tool entities for LangChain tools backed by a remote MCP server Previously, when a LangChain  tool was backed by a remote MCP server that was also separately instrumented, duplicate tool entities appeared in the UI. This has been fixed by gating subcomponent attributes off of LangChain tools when a known remote tool is detected. Fix missing User Input field for LangChain and LangGraph MCP tool calls Previously, when LangChain  or LangGraph used tools from an MCP server, the User Input field could be missing from AI monitoring data if the input message wasn't the last message in the streamed sequence. This has been fixed, and the agent now correctly extracts the input message in these cases. Reduce race condition risk in the garbage collection data sampler Previously, the agent always called gc.get_objects() to sample garbage collector object counts, regardless of configuration. This has been changed so gc.get_objects() is only called when top_object_count_limit is configured above 0, avoiding unnecessary heap iteration for customers who don't track object types collected by the garbage collector. Remove byte encoding from outbound Kombu distributed tracing headers Previously, distributed tracing headers added by Kombu  instrumentation were byte-encoded, which broke transports that serialize payloads with the standard library json module (for example, SQLAlchemy-backed transports). The byte encoding has been removed so these transports work correctly. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-130300","eolDate":"2027-07-23"},{"agent":"python","date":"2012-06-12","downloadLink":null,"version":"1.3.0.289","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: This release of the Python agent has focused on improving the way the agent communicates with the New Relic core application. This includes improved logging and error handling, but also adds support for SSL and connecting via a proxy when the monitored host is located behind a firewall. For a list of known issues with the Python agent see our online help article on the status of the Python agent . Changed features: The request method for a call to an external web service, when able to be collected by instrumentation, is now shown against a web external node in a slow transaction trace where as previously it showed the path segment of the URL. The URL, minus embedded user/password and query string is instead now shown as a label when hovering over the web external node in the slow transaction trace details. Improved logging and error handling when communicating with the New Relic core application. Many messages previously logged as errors will now be logged as warnings and an error only logged when a recurring problem is detected. This should reduce emails triggered from errors logged via the Python logging module to only those that may actually require action. Significant error messages or warnings will be output to standard output when running the agent test via the 'newrelic-admin validate-config' command. This ensures that it will be easier to detect when the test has failed due to network connectivity or license key issues. New features: Connecting to the New Relic core application using a secure SSL connection is now supported. This is enabled by setting the 'ssl' setting in the agent configuration file to 'true'. Connecting to the New Relic core application via a proxy is now supported. This is enabled by setting the 'proxy_host' and 'proxy_port' settings in the agent configuration file. If a secure SSL connection is desired, the 'ssl' setting can be set to 'true' at the same time. If the proxy requires a user name and password, the 'proxy_user' and 'proxy_pass' settings can be additionally set. When sending collected data to the New Relic core application it will be compressed when over a certain size to cut down on the amount of data being sent. The Python agent now includes its own self instrumentation and profiling capabilities to allow New Relic to monitor the performance of the agent itself and help debug any performance issues reported by a user which may occur in rare circumstances with certain web applications. Bug fixes: Where a user name and password were being included as part of a URL for a call to an external web service, eg., 'user:pass@localhost /', that the Python agent was instrumenting, the details were not always being scrubbed properly from details being reported to the New Relic core application.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-130289","eolDate":"2015-06-12"},{"agent":"python","date":"2026-07-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"13.2.0","features":["Add instrumentation for Google ADK","Add token counting for Anthropic, Gemini, OpenAI, and Bedrock"],"bugs":["Fix instrumentation crash for graphql-core v3.2.10","Remove spanId from outbound tracestate header"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds instrumentation support for Google ADK , adds token counting for multiple AI providers (Anthropic , Google GenAI , OpenAI , and AWS Bedrock ), reduces outbound tracestate header size, and fixes a crash in graphql-core  instrumentation. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . Improved Features Added instrumentation for Google ADK The Python agent now instruments Google ADK  (Agent Development Kit) AI agent workflows. Instrumented components include: LlmAgent linked to Gemini or VertexAI backends via google.genai User-defined FunctionTool instances Sub-agent workflows including child agents and AgentTool instances Multi-agent workflows including the Workflow class and deprecated LoopAgent, ParallelAgent, and SequentialAgent classes Added token counting for Anthropic, Gemini, OpenAI, and Bedrock The Python agent now reports token counts for all LLM invocations across multiple AI providers: Anthropic SDK Google GenAI SDK OpenAI SDK AWS Bedrock via botocore  and aiobotocore Bugs Fixed instrumentation crash for graphql-core v3.2.10 Previously, graphql-core  v3.2.10 renamed the errors attribute to collected_errors in ExecutionContext, causing the agent to crash. This has been fixed, and the agent now works correctly with graphql-core v3.2.10 and later. Removed spanId from outbound tracestate header Previously, the agent included spanId in the outbound tracestate header. Because spanId is already present in the traceparent header, this was unnecessary duplication. The spanId has been removed from tracestate to reduce outbound header size. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-130200","eolDate":"2027-07-06"},{"agent":"python","date":"2026-06-04","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"13.1.1","features":["Add additional model information to LangChain Chain LLM events"],"bugs":["Fix crash in LangGraph streaming instrumentation"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds additional model information to LangChain  Chain LLM events, and fixes a bug in LangGraph  streaming instrumentation. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . Improved Features Add additional model information to LangChain Chain LLM events Add request.model and response.model attributes to LLM events produced by LangChain  Chains. This information is pulled on a best effort basis and may not always be available. Bugs Fix TypeError in LangGraph streaming instrumentation Previously, when using a subset of streaming APIs in LangGraph , the agent would encounter a TypeError due to the use of weakref.WeakMethod by LangGraph. This has been fixed, and the agent should now work correctly with those LangGraph streaming methods. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-130101","eolDate":"2027-06-04"},{"agent":"python","date":"2026-06-01","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"13.1.0","features":["Add support for new Redis v8.8.0 commands"],"bugs":["Fix crash in LangGraph instrumentation","Improve handling and logging of harvest limit settings"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for multiple new Redis  commands, fixes a bug in LangGraph  instrumentation, and improves handling and logging of harvest limit settings. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . Improved Features Add instrumentation for new Redis v8.8.0 commands Add instrumentation for the following new Redis commands  from redis-py  v8.8.0: Misc commands: INCREX, XNACK Array commands: ARCOUNT, ARDEL, ARDELRANGE, ARGET, ARGETRANGE, ARGREP, ARINFO, ARINSERT, ARLASTITEMS, ARLEN, ARMGET, ARMSET, ARNEXT, AROP, ARRING, ARSCAN, ARSEEK, ARSET Bugs Fix crash in LangGraph instrumentation Previously, when using LangGraph  instrumentation, the agent would crash due to an issue with context propagation to jobs in AsyncBackgroundExecutor. This has been fixed, and the agent should now work correctly with LangGraph. Improved handling and logging of harvest limit settings The agent now more accurately reports the list of harvest methods and limits to the Environment tab in New Relic One. The agent now has more consistent debug logging on startup for harvest limit settings. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-130100","eolDate":"2027-06-01"},{"agent":"python","date":"2026-05-21","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"13.0.1","features":[],"bugs":["Fix context progagation in LangChain and LangGraph","Fix an OpenAI chat completion recording issue","Fix an issue when using OpenAI streaming through LiteLLM as a proxy"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes a context propagation issue in LangChain  and LangGraph , an OpenAI  chat completion recording issue, and an issue when using OpenAI(https://pypi.org/project/openai) streaming through LiteLLM as a proxy. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . Bugs Fix context propagation in LangChain and LangGraph Adds additional transaction context propagation to LangChain  and LangGraph  to support a wider range of application structures. Fix an OpenAI chat completion recording issue OpenAI  reintroduced logic that closes the streaming response even if the consumer hasn't read all data. Previously, the chat completion data was only recorded when reaching the stream's end which resulted in chat completion data not being recorded at the closing of the stream. Logic has now been added to capture the chat completion data even if the stream has not been fully read. Fix an issue when using OpenAI streaming through LiteLLM as a proxy Previously when using the OpenAI  SDK connected through a LiteLLM  proxy server it was possible to lose reporting of LLM response data due to a missing finish reason. This has been fixed, and the response should now always be recorded. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-130001","eolDate":"2027-05-21"},{"agent":"python","date":"2026-05-07","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"13.0.0","features":["Exclude newrelic header by default","Add exclude and include settings for Hybrid Agent traces","Add `http.statusCode` attribute to transaction events","Anthropic streaming instrumentation","Improve caching of IS_PYPY in gc_data.py for performance","Gemini response streaming"],"bugs":["Resend modules during reconnect","Guard garbage collection metrics against re-entrant calls","Enable Task Propagation in Async Generators","Fix Starlette Context Propagation in StreamingResponse"],"security":["Remove support for Python lambda functions in the config file"],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent removes support for Python lambda function in the config file, excludes the newrelic header by default, adds support for exclude and include settings for Hybrid Agent traces, anthropic  instrumentation, gemini  response streaming, improves caching of IS_PYPY in gc_data.py for performance, and adds http.statusCode attribute in transaction events. This release also resends modules during reconnect ensuring they are recorded, guards garbage collection metrics against re-entrant calls, fixes task propagation in async generators and starlette  context propagation in StreamingResponse. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . Removed features Remove support for Python lambda functions in the config file Previously, the agent allowed specifying a Python lambda function to dynamically name transactions, background task, database trace, profile trace, external trace url and method, function trace, generator trace, and memcache trace. Since support for this feature exposes a security vulnerability in the agent this feature is being removed. Deprecations The response.status attribute in WebTransactions is considered deprecated and will be removed in the upcoming 14.0.0 release.  It is being replaced by http.statusCode. We recommend replacing all references to response.status with http.statusCode. New features Exclude the newrelic header by default The newrelic distributed tracing header is now no longer sent by default. Only the W3C traceparent and tracestate headers will be sent. Add exclude and include settings for Hybrid Agent traces opentelemetry.traces.include for the configuration file or NEW_RELIC_OPENTELEMETRY_TRACES_INCLUDE to be used as an environment variable opentelemetry.traces.exclude for the configuration file or NEW_RELIC_OPENTELEMETRY_TRACES_EXCLUDE to be used as an environment variable The Hybrid Agent's default behavior will be different as well.  Now, only libraries and tracers that are supported by OpenTelemetry but not already supported by New Relic will utilize OpenTelemetry's instrumentation.  Otherwise, the agent will default to the New Relic instrumentation hooks. More information about these settings can be found in the Python Agent configuration  page as well as the OpenTelemetry API support  page. Add Anthropic streaming instrumentation Adds instrumentation support for anthropic . Improve caching of IS_PYPY in gc_data.py for performance Now checks and caches IS_PYPY once when the module is loaded. Add Gemini response streaming Add response streaming support to Gemini through the google-genai  package. Add http.statusCode attribute to transaction events To conform with the rest of the language agents, the Python agent now sends the http status to the WebTransaction attribute http.statusCode.  The Python agent will continue to send the attribute to response.status as well, but the response.status attribute will be removed in the future. Bugs Resend modules during reconnect The agent previously only sent the module list periodically after the first connect cycle.  If the agent reconnected to the collector, this data would not be resubmitted, so the UI would no longer show the module data.  This has now been fixed. Guard garbage collection metrics against re-entrant calls Adds a flag to prevent re-entrant calls to _GCDataSource.record_gc() to prevent infinite recursion on Python 3.13+. Enable task propagation in async generators Fixes an issue where AsyncGeneratorProxy would not properly handle transaction context propagation if spread over multiple tasks. Fix Starlette context propagation in StreamingResponse Adds trace context propagation to starlette  StreamingResponse for both synchronous and asynchronous generators. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-130000","eolDate":"2027-05-07"},{"agent":"python","date":"2012-04-25","downloadLink":null,"version":"1.2.1.265","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bug fixes: Fix assertion violations when greenlets were used explicitly in the context of a normal thread based request handler. Installation of package using Python 2.5 was giving warnings when trying to byte code compile installed .py files due to missing import for 'with_statement' from __future__ module in some modules. The newrelic-admin script is now installed correctly when installing the package as an egg under buildout. The newrelic.agent.stop_recording() function was causing errors when using any WSGI hosting mechanism other than Apache/mod_wsgi and wasn't working as intended even under mod_wsgi. Disable CPU sampling when os.times() is not available, such as when using Jython. Derivation of name when instrumenting the __init__() method of a class could fail if the class had a __len__() method which accessed methods/attributes which were only setup during the constructor. Move importing of multiprocessing module to global scope to avoid logging module bug  in Python versions up to 2.6.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-121265","eolDate":"2015-04-25"},{"agent":"python","date":"2012-03-27","downloadLink":null,"version":"1.2.0.246","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Bug fixes: Added full support for being able to use agent package with buildout. Previously the 'newrelic-admin' script was not installed correctly when buildout was being used to manage package installation. Added support for versions 2.2 and 2.5 of the distributed task queuing system Celery . Added support for older 'redis' client versions which did not separate commands into 'StrictRedis' and 'Redis' client objects. The database table name was not always extracted properly from SQL queries where sub selects were being used, especially when additional bracketing was being used for readability. Usually this was occuring where hand crafted SQL was being generated rather than being automatically generated through an ORM or DAL. Type handler registration in psycopg2 client module would fail due to agent instrumentation wrapper around connection and cursor objects. Javascript header added into response of type 'text/html' when Django being used and end user monitoring enabled, would be placed into wrong location of '' element if 'X-UA-Compatible' meta tag existed. This would cause issues for IE browser clients which meta tag related to. New features: Server side configuation is now available for the Python agent. This will be of most use for Heroku installations where there is by default no agent configuration file for defining local override settings. Distiguish time spent invoking the WSGI application for a request and the subsequent processing of any iterable returned by the WSGI application. These will show as nodes 'WSGI/Application' and 'WSGI/Response' in performance breakdowns and slow transaction traces. This mainly helps where iterable is a generator which performs work for each yielded item as provides proper context. Time spent in writing back a large reponse to a slow HTTP client will also be more visible. Distinguish separately the time spent in the top level WSGI application callable where the agent WSGI middleware wrapper is being applied. This will be the node which gets listed immediately under 'WSGI/Application' in a slow transaction trace. For Django, record separately time spent in processing certain types of form POSTs. This helps to show where being spent processing a large data upload. Show content length and content type details for a request in slow transaction and error details. Show content length for a response in slow transaction and error details. Features changed: Longer timeout when doing an agent test using the 'validate-config' command of the 'newrelic-admin' script. The short timeout was previously causing some users with slow DNS or networks to see the test as failing.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-120246","eolDate":"2015-03-27"},{"agent":"python","date":"2026-03-26","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"12.1.0","features":["Add time to first token"],"bugs":["Fix Flask add_url_rule signature"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for time to first token and fixes an incompatible Flask  add_url_rule function signature. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . New features Added time to first token for LLM response streams: The agent records a new attribute,time_to_first_token on LlmChatCompletionSummary events for OpenAI  and Bedrock  response streams. This attribute measures the duration between the initial request and the first token received in the response. Bugs fixes Resolved Flask  add_url_rule function signature mismatch Updated the instrumentation for Flask 's to align its add_url_rule function signature with the native Flask implementation. This fix prevents potential application crashes caused by the previous signature mismatch. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-120100","eolDate":"2027-03-26"},{"agent":"python","date":"2026-03-12","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"12.0.0","features":["Remove Cross Application Tracing in favor of Distributed Tracing","Remove support for Python 3.8","Install certificate bundle using optional extra","Add Free-Threaded Python support","Add Windows support","Improved instrumentation for Microsoft AG2 (Autogen)"],"bugs":["Fix duplicate exceptions in Strands"],"security":["Update internal packages to their latest versions"],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent removes support for Cross Application Tracing (CAT), Python 3.8, and the bundled SSL certificates. It also updates all vendored packages to their latest versions, and adds support for free-threaded CPython, Windows operating systems, and improved instrumentation for Microsoft AG2 (Autogen). Additionally, this release includes a new optional extra for installing SSL certificates through certifi. This release also fixes a bug in Strands Agents instrumentation which caused duplicate exceptions to be reported. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . Removed features Cross Application Tracing (CAT) has been removed in favor of Distributed Tracing (DT). Cross Application Tracing (CAT) was deprecated in agent version 7.0.0.166, and has been removed in this release. If you are still using Cross Application Tracing (CAT), we recommend migrating to Distributed Tracing (DT) as soon as possible to avoid disruption. The bundled SSL certificates have been removed. If you require certificates for your environment, you can either install them via your operating system's package manager or install the agent with the optional newrelic[certificates] extra. Python 3.8 support has been removed. Python 3.8 reached End-of-Life on 2024-10-07 and is no longer supported by the agent. Please consider upgrading your application to a supported version of Python in order to continue to receive updates to the Python Agent. Security All internal packages updated to their latest versions. urllib3 updated to v2.6.3 This fixes all open CVEs on urllib3 as of the date of this release. opentelemetry_proto updated to v1.40.0 wrapt updated to v2.1.2 asgiref updated to v3.11.1 New features New newrelic[certificates] extra for installing SSL certificates through certifi . The agent now provides an optional newrelic[certificates] extra which can be used to install the bundled SSL certificates. This is intended for users who require certificates but are unable to install them via their operating system's package manager. Free-Threaded CPython support Starting with Python 3.13, CPython releases builds of Python with the Global Interpreter Lock (GIL) disabled, allowing for true multi-threading. This release adds support for this behavior, allowing the agent to safely run in a free-threaded environment. This release also includes pre-built binaries for free-threaded CPython on Linux and Windows, allowing for easy installation in these environments. Windows Support This release includes pre-built binaries for CPython 3.13 or higher on Windows. Note that Python 3.12 or lower is not officially supported on Windows due to large variances in the resolution of timers. It's still possible to install and use the agent from source, but users may experience issues with inaccurate timing data and should upgrade to Python 3.13 or higher for the best experience. Improved instrumentation for Microsoft AG2 (Autogen) Added support for streaming responses through the asynchronous generator method on_messages_stream(). Instrumentation now includes a subcomponent attribute on spans that represent tool or agent calls. This is used to provide more enhanced entity mapping in the New Relic UI. Bugs Duplicate exceptions in Strands Agents After an update to Strands Agents which encapsulates some exceptions in a new EventLoopException type, duplicate errors could be reported. This has been fixed and the underlying error should only be reported once. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-120000","eolDate":"2027-03-12"},{"agent":"python","date":"2013-07-05","downloadLink":null,"version":"1.13.1.31","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent includes a hot fix to address an issue whereby external web service calls made via HTTPS connections were failing. This issue was introduced with version 1.13.0.30 of the agent. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directory from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . Bug fixes/Improvements: The Cross Application Tracing feature added in version 1.13.0.30 of the agent was causing failure of external web service calls made over HTTPS connections when that call was made via the 'httplib' module. As the 'httplib' module is used internally in other HTTP client libraries such as the 'urllib', 'urllib2', 'urllib3' and 'requests' modules, they would also have been affected. Setting the 'cross_application_tracer.enabled' setting in the agent configuration file to 'false' to disable Cross Application Tracing would cause an exception when an external web service call was being made via the 'httplib' module.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-113131","eolDate":"2016-07-05"},{"agent":"python","date":"2013-07-03","downloadLink":null,"version":"1.13.0.30","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent adds support for Cross Application Tracing. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directory from our download site . For a list of known issues with the Python agent see our online help article on the status of the Python agent . New features: Support for New Relic's Cross Application Tracing  feature is now available for the Python agent. This feature enables correlation of transaction traces between different services in your stack. It works on external calls made between applications monitored by any New Relic agents (Java, .NET, Ruby and Python), which support this feature. At this time the Python agent supports this feature on outgoing calls when using the 'httplib' module or any other module which uses 'httplib', such as the 'urllib', 'urllib2', 'urllib3' and 'requests' modules. Any inbound calls from other agents which support the feature will also be handled. Added instrumentation for the weberror  package. This provides visibility into potentially blocking operations such as sending of email for exceptions which are being reported. Added instrumentation for the umemcache  package. Added instrumentation for the DBAPI2 compliant interface for the IBM DB2 ibm_db_dbi  database client package. Bug fixes/Improvements: When running a WSGI application under the Tornado WSGI container, data reporting would stop if an unhandled exception managed to propagate back up to the Tornado WSGI container. This was due to a bug  in Tornado in respect of its compliance with the WSGI specification. A workaround is provided to avoid the problems this caused to the Python agent. Tornado versions prior to 3.2 will still carry that bug however and we make no attempt to address the bug in Tornado. The Tornado instrumentation was causing template rendering to fail where a relative path was used to refer to the template and no template path had been specified for the RequestHandler instance or globally. The Tornado instrumentation was causing exceptions when using the @tornado.gen decorators under Tornado 2.X. When using Django, web transactions will now be named after individual view handlers when using class based views, rather than being named after the class itself. When using Pyramid, web transactions will now be named after individual view handlers when using view classes, rather than being named after the class itself. Celery instrumentation had stopped working correctly for Celery versions 2.5.3 through 2.5.5. No data was being reported where a monitored process was being shutdown within a couple of seconds of being started even if the agent was able to register. This could result in custom metrics in particular not being reported. SSL certificate validation was failing on older Debian systems due to the OpenSSL libraries not being able to process a couple of the certificates bundled with the Python agent. Those certificates were not required and have been removed. Calculation of a time string was failing on Windows due to using a strftime() formatter which only existed on UNIX systems.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-113030","eolDate":"2016-07-03"},{"agent":"python","date":"2013-05-28","downloadLink":null,"version":"1.12.0.56","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent removes the experimental label from our Tornado Web and Pyramid support, with support now being enabled by default. The agent can be installed using easy_install/pip/distribute via the Python Package Index  or can be downloaded directory from our download site . For a list of known issues with the Python agent, see Status of the Python agent . New features: The previously experimental support for the native Tornado Web API has been greatly expanded and is now enabled by default. This is in addition to the tornado.wsgi.WSGIContainer support we previously provided and includes the native Tornado Web API for constructing async applications. Running a limited subset of the native Tornado Web API within a separate WSGI server using the tornado.wsgi.WSGIApplication adapter is also now supported. The previously experimental support for the Pyramid web framework has been improved and is now enabled by default. When using a DBAPI2 compliant database client, calls to stored procedures via the callproc() method of the database cursor are now tracked. Previously, only calls made to stored procedures by explicitly using a CALL SQL statement were being tracked. All calls to stored procedures currently appear under the category of 'SQL - Other'. A future agent update is planned which will split out calls to stored procedures separately and report them on the databases tab. Added instrumentation for automatically wrapping the WSGI application when using the CherryPy WSGI server bundled with the CherryPy framework. Added instrumentation for automatically wrapping the WSGI application when using the WSGI server from the Python standard library wsgiref module. Be aware that due to non conformance with the WSGI specification, it is not recommended that the WSGI server from the wsgiref module be used unless using Python 2.7.4 or higher. Issues with older versions of the WSGI server in the wsgiref module will cause incorrect reporting of data. More details are provided in our status of the Python agent . Bug fixes/Improvements: External web calls made using the 'requests' module from a session were not being correctly monitored, resulting in such requests being picked up as being performed by the lower level 'httplib' module and the time taken not being inclusive of the whole request. The collection of explain plans by the agent in a background thread when performing a data harvest, was not explicitly performing a rollback. This could result in database proxies such as pgbouncer believing the database connection was now dirty and force closing the connection and ejecting it from the current database connection pool. The wrapper used by the agent around wsgi.input passed in the WSGI request environment was preventing non standard WSGI applications directly reaching down to the original socket connection so as to implement extensions such as websockets. The object wrapper used in our instrumentation for function traces has been improved so that it will pass type checks performed using builtin Python calls such as isinstance(), isfunction() and isclass(). This addresses issues where the object wrappers could interfere with the correct operation of web frameworks which derived the calling convention to be used when invoking a handler function from the type of the handler. Note that using type() on the wrapper object will still yield its true type, so functions such as isinstance() should always be used where possible. The agent could fail on startup when running on a system with a non English locale using a custom date/time format.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-112056","eolDate":"2016-05-28"},{"agent":"python","date":"2013-04-09","downloadLink":null,"version":"1.11.0.55","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent introduces a major new feature called X-Ray Sessions. This feature allows you to gain deeper insights into a key transaction's performance by showing transaction traces alongside long-running profiler results. For a list of known issues with the Python agent see our online help article on the status of the Python agent . New features: X-Ray Sessions provide more targeted transaction trace samples and thread profiling for web transactions. For full details see our X-Ray sessions documentation . For new agent installations, the agent will now default to using a SSL connection when connecting to our data collector to report any data. If updating from an older agent version, you will however need to manually update your agent configuration file and change the 'ssl' setting to 'true' to always use SSL connections. When connecting direct to our data collector over a SSL connection, SSL certificate validation will now be performed to mitigate the possibility of man in the middle attacks. Breakdown metrics for transactions are now recorded as unscoped metrics as well as the existing metrics scoped to a web transaction. As custom dashboards can only chart unscoped metrics, what this means is that it is now possible to create custom dashboards that display data on specific breakdown metrics, such as time spent in traced functions. For example, you may wish to chart time spent in creating database connections, or specific middleware and view handler functions. When displaying error details, the full path of the exception is now displayed and not just the class name. This makes it easier to correctly identify the full name, with that name then being able to be directly copied into the 'error_collector.ignore_errors' setting of the agent configuration file if it is desired that that exception be ignored. Added the 'newrelic.agent.record_custom_metrics()' function to the public API for the agent to allow the recording of many custom metrics in one function call to the agent. XXXFeatures Changed: We have temporarily disabled the generation of CPU burn information for transaction traces. This was displaying inaccurate values after a UI change, but also had an underlying issue whereby it was reporting CPU burn by the whole process and not just the thread handling the request. We are withdrawing the feature until we can improve the accuracy of the reported value. We have disabled the ability to get thread profiling information when a WSGI server makes use of coroutine libraries such as gevent or eventlet. This is because the nature of how coroutines are implemented, means we were are not able to generate accurate usable data. Bug fixes/Improvements: When queueing Celery tasks from a web application, those web transactions were in some cases being wrongly categorised as background tasks. The name of the transaction was also being labelled with a string with the object representation, resulting in metric grouping issues. The older version of the 'requests' package we were bundling and were using for any HTTP calls was not closing socket descriptors immediately when a requests session object was disposed of. This could result in a small number of open socket descriptors being held open until the Python garbage collector kicked in and closed them. Login credentials supplied as part of a URL, could in some circumstances appear with the URL parameter associated with a web external node in a transaction trace sample. Django 1.5 moved which module the 'Http404' exception was declared in. As a result we were no longer correctly ignoring it when catching exceptions to process as errors. A check designed to warn against the use of uWSGI versions prior to 1.2.6, which contain a bug which results in the agent recording incorrect response times, was failing on very old uWSGI versions. Updated our gevent instrumentation to accommodate a prototype change in gevent 1.0rc1. Updated our bottle instrumentation to handle the non numeric version string used in bottle development versions. After five minutes of being unable to connect to our data collector to report data, the agent will now internally reset itself, discarding accumulated metric data and require the agent to reregister itself with our core application before collecting data once again. This is to ensure that we do not unnecessarily keep accruing data and causing an increase in memory usage while we cannot contact our data collector. Avoid the potential for a web request to deadlock in a situation where a web framework transaction management system made a copy of the object we use to record details about web transactions or background tasks.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-111055","eolDate":"2016-04-09"},{"agent":"python","date":"2026-02-19","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"11.5.0","features":["Add hybrid agent tracing support","Add Trace ID Ratio based sampler","Add subcomponent attributes to agentic AI instrumentation","Add entity GUID to Agent Control health check files","Add instrumentation for new Redis methods"],"bugs":["Fix duplicate ImportHookFinder instances","Fix incorrect signature on OracleDB Cursor.callproc()"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds trace/span support for Hybrid Agent, New Relic's integration with OpenTelemetry. It also adds entity GUIDs to Agent Control health check files,  subcomponent attributes to agentic AI instrumentation, support for new Redis  client methods, fixes a bug where there may be duplicate ImportHookFinder instances and a bug in OracleDB  Cursor.callproc() instrumentation. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . Features Add Hybrid Agent tracing support Hybrid Agent is designed to bridge the gap for teams looking to adopt OpenTelemetry standards while maintaining backwards compatibility with their existing New Relic dashboards. Hybrid Agent offers a \"best-of-both-worlds\" experience by combining New Relic’s deep visibility with OpenTelemetry API compatibility. It provides an observability solution with integrated support for the following OpenTelemetry APIs: Tracing Standalone library and native framework instrumentation Key enhancements like Span Links and Events on Spans are now available, ensuring seamless interoperability in mixed-mode environments. Introduces a new Trace ID Ratio based sampler A new Trace ID Ratio based sampler. This sampling algorithm is based off the sampler of the same name from OpenTelemetry, and can be configured to sample a set percentage of transactions. Add subcomponent attributes to agentic AI instrumentation Instrumentation for LangChain , MCP , and Strands  now includes a subcomponent attribute on spans that represent tool or agent calls. This is used to provide more enhanced entity mapping in the New Relic UI. Add entity GUID to Agent Control health check files When the agent is started within an Agent Control environment, a health check file is created at the configured file location for every agent process. This file now includes the GUID of the entity related to the agent when available. Add instrumentation for new Redis  methods Add instrumentation for the following methods new methods on Redis clients: hotkeys_get hotkeys_reset hotkeys_start hotkeys_stop vrange xcfgset Bugs Fix duplicate ImportHookFinder instances Previously it was possible for duplicates of the import hook finder to be added to sys.meta_path. Fix incorrect signature on OracleDB  Cursor.callproc() Previously attempting to use keyword arguments with Cursor.callproc() would cause crashes as the argument names were incorrect in our instrumentation. This has been fixed, and the additional argument keyword_parameters is now also supported. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-110500","eolDate":"2027-02-19"},{"agent":"python","date":"2026-01-29","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"11.4.0","features":["Add support for LangGraph agents"],"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for LangGraph  agents. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . Features Add support for LangGraph  agents Adds instrumentation for LangGraph agent invocations via create_agent() in LangChain. This includes agent calls to invoke(), ainvoke(), stream(), and astream(). Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-110400","eolDate":"2027-01-29"},{"agent":"python","date":"2026-01-22","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"11.3.0","features":["'Add support for exception instances as arguments to notice_error()' 'Add support for gpt-5 and newer OpenAI LLM models', 'Add support for Strands-Agent synchonous tool error capturing'"],"bugs":["Guard against crashes in Azure Functions utilization"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds new ways of passing errors to notice_error(), adds support for Strands-Agent  synchronous tool error capturing, adds support for gpt-5 and newer OpenAI LLM models, and fixes a crash in Azure Functions' utilization logic. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . Features Add support for exception instances as arguments to notice_error() notice_error() can now accept a caught exception instance (such as one from a try/except block) for the error argument, rather than an exception tuple from sys.exc_info(). This is in addition to and does not replace the existing behavior. Previous usage of notice_error() with zero arguments or with an exception tuple should still function correctly. Add support for gpt-5 and newer OpenAI LLM models Add updates to OpenAI instrumentation to support newer attribute names used with later OpenAI models Add support for Strands-Agent  synchronous tool error capturing Synchronous Python functions used as tools in Strands-Agents now have proper error capturing, and capture traces within tools such as database lookups. Bug fixes Guard against crashes in Azure Functions utilization Previously, some users experienced edge cases where Azure Functions utilization detection would crash when attempting to match regular expressions. The crash has been fixed, and should no longer be possible in the future. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-110300","eolDate":"2027-01-22"},{"agent":"python","date":"2013-02-23","downloadLink":null,"version":"1.10.2.38","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent fixes an issue when floating point values were used in headers used to calculate queueing time. For a list of known issues with the Python agent see our online help article on the status of the Python agent . Bug fixes/Improvements: When a float value was provided in the X-Request-Start or X-Queue-Start headers as the time stamp, it was not being parsed correctly and the fractional part was being discarded. This was resulting in loss off accuracy.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-110238","eolDate":"2016-02-23"},{"agent":"python","date":"2025-12-08","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"11.2.0","features":["Add support for Strands instrumentation","Add support for AWS Bedrock Converse Streaming instrumentation","Add support for Redis methods hybrid_search and msetex","Add support for loop_factory parameter in asyncio.Runner","Capture Langchain role assignments in LLM events","Capture LLM event timestamp at time of LLM request"],"bugs":["Fix ASGI header consumption"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for the following: Strands AWS Bedrock Converse Streaming Redis  methods hybrid_search and msetex Langchain  role assignments for LLM events LLM event timestamp captured at time of LLM request loop_factory parameter in asyncio.Runner This release also addresses a bug in ASGI instrumentation where headers are not reported by the web server. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . Features Add support for Strands Add instrumentation for Strands tools and agents in single and multi-agent (swarms, graphs, etc.) setups Add support for AWS Bedrock Converse Streaming Add monitoring support for streaming Converse API. This includes support for Converse chat completion calls made with boto3 and aioboto3 clients using converse_stream(). Add support for Redis  methods Add support for the following methods: hybrid_search msetex Add support for loop_factory in asyncio.Runner In Python 3.11, the asyncio.Runner class was added as well as the loop_factory parameter. The loop_factory parameter provides a replacement for loop policies.  Now, the loop that is created is instrumented, regardless of whether it is through a global event loop setting or a custom event loop. Capture Langchain  role assignments in LLM events Langchain LlmChatCompletionMessage events now contains the assigned role from Langchain . Capture LLM event timestamp at time of LLM request Previously, the LLM event's timestamp was captured at the time of event creation. Now, it is more accurately captured at the time of the LLM request. Bug fixes ASGI header consumption When an ASGIWebTransaction consumes the headers from a http.response.start event, it was doing so without regard to the allowable input types. When the headers are a generator, the generator was consumed by the call to process_response() leaving no headers remaining for the web server to send.  This has now been fixed. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-110200","eolDate":"2026-12-08"},{"agent":"python","date":"2012-01-10","downloadLink":null,"version":"1.1.0.192","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes: Addressed a performance issue which would cause high CPU load, when parsing SQL queries which had a large number of values for a SQL 'IN' clause. Agent version was not reported in form A.B.C.D in all cases. This was causing UI to warn that Python agent was out of date even when running version newer than the minimum recommended version. When 'feedparser' module is used, now correctly track external web service requests where URI used 'feed' or feed:http' for scheme. Illegal non ASCII characters in a URL could cause the agent to generate Unicode conversion warnings or outright fail a request with an exception where the character sequence could not be decoded to Unicode using the Python system default encoding. The table name for a SQL query was not being correctly derived when the SQL contained a select sub query or table name aliases were being used. Number of nodes captured for a slow transaction trace was not being capped properly resulted in too much data being sent through to core application. This could result in details of slow transaction being rejected by core application, or result in a timeout in UI when attempting to display the slow transaction trace. SQL calls made using 'psycopg2' were failing where optional parameters argument was not supplied to database cursor 'execute()' method and the SQL contained a '%' character such as in a 'LIKE' clause. Was not ignoring exception of type 'bottle.HTTPError' raised within application using Bottle. This is not a true exception but is used to programmatically indicate a non 200 HTTP response so shouldn't have been recorded as an error. The 'django-piston' instrumentation was failing when an error occurred in users handler and it tried to generate an error response. This was because 'django-piston' was assuming that a handler would always be a normal function. It would therefore fail for a decorator/wrapper implemented using a class object as is used by the agent instrumentation. New features: Added support for capturing explain plans for slow SQL when using MySQL and PostgreSQL. Added preliminary public API for manually instrumenting additional functions in user code and interacting with the current transaction to override how and what details about the transaction are recorded. Added the 'transaction_tracer.function_trace' setting in the agent configuration file for providing a simplified way of specifying additional Python functions for which time metrics should be collected. Time spent in these functions will then appear in web transaction performance break down and slow transaction traces. Added new or improved support for tracking external web service requests made using the 'urllib', 'urllib2', 'urllib3', 'httplib', 'httplib2' and 'requests' modules. Note that only time taken for the initial connect for the HTTP connection may be recorded. Uninstrumented time which appears immediately after an external web service request in a slow transaction trace made using one of these modules, will therefore possibly be the time then taken to send request data, wait for a response and consume that response data. Added support for tracking external requests to a Solr service using the 'pysolr' and 'solrpy' modules. Time spent making the request will show on the overview charts as Solr time. Metrics for individual types of requests will also be listed in web transaction performance breakdown and slow transaction traces. Added Django application called 'newrelic.extras.framework_django' which explicitly adds in 'newrelic_tags' tag library containing template tags for manually adding in RUM header and footer. Reliance on the old method whereby template tag library was added automatically is now deprecated and will be removed in a future version. Added support for Bottle 0.10.X in Bottle specific instrumentation. Added support for Redis using the 'redis' module. Support consists of tracking time spent connecting to and issuing commands against the Redis service. Added support for MongoDB using the 'pymongo' module. Support consists of tracking time spent connecting to and issuing commands against the MongoDB service. Features changed: The 'capture_params' setting was defaulting to 'true' rather than 'false' resulting in the request query string parameters being reported against errors and slow transaction traces. If upgrading you will need to change the agent configuration file you are already using to change it to 'false' if capturing parameters is not desired. Rollup metrics against web transactions for external web service requests will now only be recorded against the host and will not be broken out based on resource requested on the remote service.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-110192","eolDate":"2015-01-10"},{"agent":"python","date":"2013-02-22","downloadLink":null,"version":"1.10.1.36","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent contains improvements in the way that queueing time is calculated. For a list of known issues with the Python agent see our online help article on the status of the Python agent . Bug fixes/Improvements: Resolved some issues with tracking of front-end queue time, particularly when the agent is running on an app hosted on Heroku. The agent will now more reliably parse the headers described in https://newrelic.com/docs/features/tracking-front-end-time  and will automatically detect whether the times provided are in seconds, milliseconds or microseconds.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-110136","eolDate":"2016-02-22"},{"agent":"python","date":"2025-11-03","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"11.1.0","features":["Add new environment variables for attribute filter settings","Add support for async generators in transaction decorators","Add support for additional models in AWS Bedrock","Add instrumentation for new methods in AWS Kinesis","Add support for Python 3.14"],"bugs":["Fix a bug in aiomysql which caused RecursionError when using ConnectionPool","Fix a bug where properties were not properly passed in the producer for kombu","Fix an error when shutdown_agent is called from within the harvest thread"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds Python 3.14 support, new environment variables for attribute filter settings, support for async generators in transaction decorators, additional models in AWS Bedrock , and new methods in AWS Kinesis .  This release also fixes a bug in aiomysql  which caused RecursionError when using ConnectionPool where it was wrapped multiple times, a bug where properties were not properly passed in kombu 's producer, and an error when shutdown_agent is called from within the harvest thread. Install the agent using easy_install/pip/distribute via the Python Package Index , using conda via the Conda-Forge Package Index , or download it directly from the New Relic download site . Features Add support for Python 3.14 Add support for Python 3.14. Add environment variables for attribute filters settings The following settings now have the option to be set through environment variables: | Configuration Setting                     | Environment variable                                |\n|-------------------------------------------|-----------------------------------------------------|\n| attributes.enabled                      | NEW_RELIC_ATTRIBUTES_ENABLED                      |\n| attributes.exclude                      | NEW_RELIC_ATTRIBUTES_EXCLUDE                      |\n| attributes.include                      | NEW_RELIC_ATTRIBUTES_INCLUDE                      |\n| browser_monitoring.attributes.enabled   | NEW_RELIC_BROWSER_MONITORING_ATTRIBUTES_ENABLED   |\n| browser_monitoring.attributes.exclude   | NEW_RELIC_BROWSER_MONITORING_ATTRIBUTES_EXCLUDE   |\n| browser_monitoring.attributes.include   | NEW_RELIC_BROWSER_MONITORING_ATTRIBUTES_INCLUDE   |\n| error_collector.attributes.enabled      | NEW_RELIC_ERROR_COLLECTOR_ATTRIBUTES_ENABLED      |\n| error_collector.attributes.exclude      | NEW_RELIC_ERROR_COLLECTOR_ATTRIBUTES_EXCLUDE      |\n| error_collector.attributes.include      | NEW_RELIC_ERROR_COLLECTOR_ATTRIBUTES_INCLUDE      |\n| span_events.attributes.enabled          | NEW_RELIC_SPAN_EVENTS_ATTRIBUTES_ENABLED          |\n| span_events.attributes.exclude          | NEW_RELIC_SPAN_EVENTS_ATTRIBUTES_EXCLUDE          |\n| span_events.attributes.include          | NEW_RELIC_SPAN_EVENTS_ATTRIBUTES_INCLUDE          |\n| transaction_events.attributes.enabled   | NEW_RELIC_TRANSACTION_EVENTS_ATTRIBUTES_ENABLED   |\n| transaction_events.attributes.exclude   | NEW_RELIC_TRANSACTION_EVENTS_ATTRIBUTES_EXCLUDE   |\n| transaction_events.attributes.include   | NEW_RELIC_TRANSACTION_EVENTS_ATTRIBUTES_INCLUDE   |\n| transaction_segments.attributes.enabled | NEW_RELIC_TRANSACTION_SEGMENTS_ATTRIBUTES_ENABLED |\n| transaction_segments.attributes.exclude | NEW_RELIC_TRANSACTION_SEGMENTS_ATTRIBUTES_EXCLUDE |\n| transaction_segments.attributes.include | NEW_RELIC_TRANSACTION_SEGMENTS_ATTRIBUTES_INCLUDE |\n| transaction_tracer.attributes.enabled   | NEW_RELIC_TRANSACTION_TRACER_ATTRIBUTES_ENABLED   |\n| transaction_tracer.attributes.exclude   | NEW_RELIC_TRANSACTION_TRACER_ATTRIBUTES_EXCLUDE   |\n| transaction_tracer.attributes.include   | NEW_RELIC_TRANSACTION_TRACER_ATTRIBUTES_INCLUDE   | Add support for async generators in transaction decorators Previously, transaction decorators did not support being wrapped around async generators. This support has been added, and async generator transactions will now automatically measure event loop wait time and other statistics. Add support for additional models in AWS Bedrock instrumentation Updates AWS Bedrock instrumentation through botocore and aiobotocore to support the following additional models Claude Sonnet 3+ models Models that are prefixed with a region (region-aware) Add instrumentation for new Kinesis methods Adds botocore instrumentation to support new AWS Kinesis methods describe_account_settings update_account_settings update_max_record_size update_stream_warm_throughput Bug fixes Prevent a RecursionError in aiomysql  ConnectionPool Previously, a RecursionError would be raised in aiomysql  when using pooled connections. Deep ObjectProxy chains were created around pooled connections due to repeated wrapping. This has been fixed. Fixed a bug where properties were not properly passed in kombu 's producer Fixed a bug where instrumentation for kombu.messaging.Producer.publish() was causing properties to accidentally be nested inside of the dictionary, causing the properties to be in the wrong spot and not read by downstream packages. Fix error when shutdown_agent is called from within the harvest thread Previously, a RuntimeError could occur when shutdown_agent was called from within the harvest thread. This fixes that issue by adding a guard to prevent the crash. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about…","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-110100","eolDate":"2026-11-03"},{"agent":"python","date":"2013-01-23","downloadLink":null,"version":"1.10.0.28","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release of the Python agent contains a fix for when reporting to multiple applications, as well as other minor bug fixes and enhancements. For a list of known issues with the Python agent see our online help article on the status of the Python agent . New features: On the Linux platform, the agent environment now reports the total amount of system memory available. Added support for psycopg2cffi database module. Custom parameters can be associated with function trace nodes for display against transaction traces in the UI. The URL associated with a call to an external service will now be shown in the custom parameters section for the node in a transaction trace. Previously would have been shown as a label when hovering other the node. Bug fixes/Improvements: The agent was not reporting any data where multiple applications were being listed in in the app_name configuration setting. Calling register_application() in the context of a module import could cause a temporary deadlock when a timeout period was specified. The potential for deadlock will now be detected and the function will return without waiting. When the agent was configured to capture query string parameters, a key with an empty value was being discarded and not reported. When using gevent mode of gunicorn, the SystemExit exception was being logged on process shutdown due to gevent sending the SystemExit exception to all greenlets and not just the main thread when sys.exit() was called. Instrumentation wrapping the Django reverse() function was not accepting named parameters. If custom parameters were used with a transaction, the HTTP response STATUS was duplicated in details related to an error raised from that transaction. Changes to Django instrumentation to avoid metric grouping issues resulting from raw URLs leaking through as transaction name.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-110028","eolDate":"2016-01-23"},{"agent":"python","date":"2025-10-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"11.0.1","features":[],"bugs":["Prevents early activation in Django Instrumentation","Fix server configuration to local configuration sync issues","Guard against crashes from trace_cache.pop()"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent provides fixes for early activation in Django  instrumentation, server side overrides for max_samples_stored being ignored, and guards against crashes from trace_cache.pop(). Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Bug fixes Prevents early activation in Django instrumentation Remove calls to application_settings() in Django  instrumentation to prevent issues with early activations in pre-fork applications. Fix server configuration to local configuration sync issues This fixes a bug created when event_harvest_config.harvest_limits.* settings were deprecated in favor of *.max_samples_stored settings. Some server side configurations were not overriding the client side configurations, resulting in data being sent to the collector despite the user disabling this. Guard against crashes from trace_cache.pop() In the ContextOf class, there was an unsafe access of the trace_cache via pop(key) without a default value. This caused crashes when the weakref in the dictionary was already garbage collected. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-110001","eolDate":"2026-10-06"},{"agent":"python","date":"2025-09-25","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"11.0.0","features":["Removes support for Python 3.7","Removes and or deprecates various APIs and settings","Deprecates [aioredis](https://pypi.org/project/aioredis/) instrumentation","Raises the minimum supported version of `setuptools` and `setuptools_scm`","Adds new instrumentation for [AutoGen](https://github.com/microsoft/autogen)","Adds new instrumentation for [Pyzeebe](https://pypi.org/project/pyzeebe/)","Adds new MCP (Model Context Protocol) named spans"],"bugs":["Fixes a crash in psycopg","Ensures MCP spans are only recorded when AI monitoring is enabled"],"security":null,"supportedOperatingSystems":null,"description":"Notes This version of the agent has been yanked. This release of the Python agent makes the following changes: Removes support for Python 3.7 Removes and or deprecates various APIs and settings Deprecates aioredis  instrumentation Raises the minimum supported version of setuptools and setuptools_scm Adds new instrumentation for AutoGen Adds new instrumentation for Pyzeebe Adds new MCP (Model Context Protocol) named spans Fixes a crash in psycopg Ensures MCP spans are only recorded when AI monitoring is enabled Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Removed features Removes support for Python 3.7 Python 3.7 was EOL'd June 27, 2023. The Python agent has dropped support for it. Removes various deprecated APIs The following APIs have been removed: | Legacy API                                | Replacement API                                                                                                                                                                    |\n|-------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| accept_distributed_trace_payload        | accept_distributed_trace_headers                                                     |\n| add_custom_parameter                    | add_custom_attribute                                                                        |\n| add_custom_parameters                   | add_custom_attributes                                                                      |\n| create_distributed_trace_payload        | insert_distributed_trace_headers                                                 |\n| get_browser_timing_footer               | The functionality of this has been wrapped into get_browser_timing_header()             |\n| record_exception                        | notice_error()                                                                                                         |\n| NewRelicLogHandler                      | NewRelicLogForwardingHandler                                                                                                                                                     |\n| lambda_handler & LambdaHandlerWrapper | These APIs have moved to the newrelic-lambda  package. | Removes various deprecated settings The following settings have been removed: | Legacy Setting                          | Replacement Setting                                                                                                                                                                                                          |\n|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| transaction_tracer.capture_attributes | transaction_tracer.attributes.enabled                                                                                  |\n| error_collector.capture_attributes    | error_collector.attributes.enabled                                                                                  |\n| browser_monitoring.capture_attributes | browser_monitoring.attributes.enabled                                                                             |\n| analytics_events.enabled              | transaction_events.enabled                                                                                             |\n| analytics_events.capture_attributes   | transaction_events.attributes.enabled                                                                              |\n| error_collector.ignore_errors         | error_collector.ignore_classes                                                                                                       |\n| strip_exception_messages.whitelist    | strip_exception_messages.allowlist                                                                            |\n| ssl                                   | This is now hardcoded to true so it has been removed as a setting option.                                                                                                                                                  |\n| ignored_params                        | Use newrelic.attributes.exclude = request.parameters.{name} instead. Add each request parameter key to the newrelic.attributes.exclude list,  delimited by commas. Be sure to prepend the key with request.parameters. |\n| agent_limits.merge_stats_maximum      | This is now completely ignored in favor of serverside config.                                                                                                                                                                | Dep…","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-110000","eolDate":"2026-09-25"},{"agent":"python","date":"2011-11-30","downloadLink":null,"version":"1.0.5.156","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes: Details of errors were not being captured and passed back to the core application to be displayed by the UI when the URL for the request had query string parameters. The problem was not causing failure of the overall web application but that a problem was occuring would have been identifiable though a Python agent exception and traceback being recorded in the Python agent log file with message: NameError: global name 'request_params' is not defined Slow transactions were never being recorded when agent run using method where no agent configuration file was being used. This is the case for example when using Heroku. New features: Added support for the distributed task queuing system Celery. Tasks executed by a Celery  server can be tracked and reported as background tasks against an application in the New Relic UI. Added support for tracking as external web service requests calls made out via the pywapi  module. Added support for automatic wrapping of WSGI application entry point when using flup  WSGI adapter for FASTCGI, SCGI and AJP. Added support for meinheld  as standalone WSGI server and also as a worker class when using gunicorn. Added support for recording database transactions when using pyodbc .","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-105156","eolDate":"2014-11-30"},{"agent":"python","date":"2011-11-15","downloadLink":null,"version":"1.0.3.138","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes: Where instrumentation was not available for the web framework or toolkit being used and web transactions were being named according to the original URL, metric normalization rules were not being correctly applied when metric grouping issues occurred due to a large number of unique URLs. This was resulting in grouping of web transactions metrics under incorrect names leading to the data presented by the UI being unhelpful or misleading. Agent would fail when collecting WSGI hosting environment information when an older version of Tornado web server was used which did not provide version information. This would lead to no web transactions metrics being reported as failure occured when agent was trying to register with the New Relic core application. Instrumentation of the feedparser module was not catering for the fact that the parse() function could be supplied arguments beyond just the URL to be retreived. This would result in an exception and the web transaction always failing when such additional arguments were supplied. Instrumentation for Django was improved so that view handler function name was reported against a web transaction rather than URL when using Django static files mechanism. Instrumentation for Django was improved so that technical 404 and 500 response handler function name was used for web transaction when appropriate. Instrumentation for Django was improved to ensure that request middleware function name was always used for web transaction name when it returned a valid response. Features changed: Attributes captured from WSGI request environment such as 'REQUEST_METHOD', 'HTTP_REFERER' and 'HTTP_USER_AGENT' are now shown under the 'Request environment' category in error details and slow transaction traces rather than under 'Custom parameters'. The HTTP response status for a web transaction is now shown as 'STATUS' under the 'Response properties' category in error details and slow transaction traces rather than under 'Custom parameters'.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-103138","eolDate":"2014-11-15"},{"agent":"python","date":"2011-11-14","downloadLink":null,"version":"1.0.2.130","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 first general release of the Python agent. If you are using an older BETA version of the Python agent you should upgrade as soon as possible as many outstanding issues were fixed leading up to this release. No change history for older versions will be made available.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-102130","eolDate":"2014-11-14"},{"agent":"python","date":"2025-09-04","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.17.0","features":["Adds support for custom tasks in Celery","Adds support for graphene-django","Adds support for middleware filtering in Django","Adds support for AWS Bedrock Converse API","Adds support for W3CTraceParent header sampled flag"],"bugs":["Safeguard for deepest unique path in GraphQL","Safeguard for web request parsing","Fix crash in GraphQL","Fix crash in ElasticSearch"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for the following: Custom tasks in Celery Graphene-Django  monitoring Middleware filtering in Django AWS Bedrock Converse  API W3CTraceParent header sampled flag This release also provides the following fixes: Safeguards for the deepest unique path in GraphQL Safeguards for web URL request parsing Fallback for ElasticSearch and GraphQL when trace.settings==None Remove options method from async ElasticSearch client list Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Adds support for custom tasks in Celery Add monitoring support for custom task classes in Celery .  Previously, only tasks using the default task class were able to be monitored.  Note: This version of the Python agent will no longer support Celery versions less than v5.2.0 . Adds support for Graphene-Django Add monitoring support for synchronous schemas created with Graphene-Django .  Previously, schemas created with Graphene-Django would only be partially monitored, resulting in missing GraphQL  related attributes. Adds support for middleware filtering in Django Users are now able to filter which Django  middleware to monitor.  There are now three additional settings : instrumentation.middleware.django.enabled (Default is true) instrumentation.middleware.django.exclude instrumentation.middleware.django.include See the Django Middleware Filtering page  for more information and examples. Adds support for AWS Bedrock Converse API Add monitoring support for non-streaming Converse  API. This includes support for converse chat completion calls made using boto3 and aioboto3 clients. Adds support for W3CTraceParent header sampled flag When an upstream service sends the W3CTraceParent header with the sampling flag set, New Relic will take into account that sampling decision when deciding whether the current transaction will be sampled. Added support for sampling decisions based on whether the remote parent is sampled Added support for two new configuration options: distributed_tracing.sampler.remote_parent_sampled distributed_tracing.sampler.remote_parent_not_sampled default is the default behavior and behaves as it did before this change (it passes the sampling decision to the adaptive sampling algorithm to determine whether the transaction will be sampled). always_on means that the trace that has a remote parent sampled or remote parent not sampled will always be sampled. always_off means that the trace that has a remote parent sampled or remote parent not sampled will never be sampled. Bug fixes Add safeguard for deepest unique path in GraphQL Some users were experiencing issues with the deepest unique path in GraphQL  not being generated due to a field name returning None. This issue has been fixed. Add safeguard for web request parsing Some users experienced a parsing error when request_uri was malformed or contained invalid characters.  This can happen at this point if the request_uri in the request header is invalid and does not match the (valid) URL originally given.  While this safeguard has now been put in place in New Relic, urllib has resolved this issue for versions of Python released after Jan 31, 2025. Fix crash in ElasticSearch and GraphQL when trace.settings==None In cases where trace.settings is None, the instrumentation for ElasticSearch crashed the application.  A global_settings fallback has been put in place.  This also resolves the same issue found in GraphQL. Remove options method from async ElasticSearch client list The previous instrumentation of ElasticSearch caused a crash because options was in the list of async methods.  This method is no longer wrapped in a DatastoreTrace since it is not one that conducts any datastore operations/requests. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-101700","eolDate":"2026-09-04"},{"agent":"python","date":"2025-08-14","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.16.0","features":["Adds support for new Redis functions","Convert all internal paths from os.path to pathlib.Path"],"bugs":["Fix issue with JSON encoding PosixPaths"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for new Redis  functions, convert all internal paths from os.path to pathlib.Path, and fixes an issue with JSON encoding PosixPaths. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Adds support for new Redis functions Add instrumentation for new Redis  functions. Convert all internal paths from os.path to pathlib.Path Convert all internal usage of string based paths and os.path to pathlib.Path in preparation to support Windows paths. Bug fixes Fix issue with JSON encoding PosixPath Some users were experiencing issues with JSON encoding PosixPath configuration settings. This issue has been fixed. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-101600","eolDate":"2026-08-14"},{"agent":"python","date":"2025-07-24","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.15.0","features":["Adds support for oracledb"],"bugs":["Fixes MessageTransaction object has no attribute destination_name bug","Fixes an authentication issue when recording AWS metadata"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for oracledb , fixes a bug in Kombu and Kafka where MessageTransaction object has no attribute destination_name, and fixes the disappearance of utilization metadata with AWS. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Adds support for oracledb Add instrumentation for oracledb . Bug fixes Fix \"MessageTransaction object has no attribute destination_name\" bug Fix a bug in MessageBroker instrumentations where the serialize methods were looking for the destination_name attribute on the MessageTransaction and it did not exist. Fix AWS utilization metadata issue when running AWS and K8s together Due to permissions settings in K8s pods running on AWS EC2 instances, the utilization metadata is able to be retrieved the first time. However, if the application is left running continuously, the agent will reconnect and the utilization metadata fails to load. In cases like these, the utilization metadata is cached per agent instance and is able to be retrieved. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-101500","eolDate":"2026-07-24"},{"agent":"python","date":"2025-06-18","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.14.0","features":["Add support for Azure Function Apps"],"bugs":["Create pb2 files for protobuf v6"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Azure Function Apps  and protobuf  v6. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Adds support for Azure Function Apps Adds support for Azure Function Apps  for HTTPTrigger types. Bug fixes Adds pb2 files to enable protobuf v6 support Previously, several google packages were not compatible with New Relic due to the lack of protobuf  v6 support.  This has now been resolved. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-101400","eolDate":"2026-06-18"},{"agent":"python","date":"2025-06-09","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.13.0","features":["Add support for Model Context Protocol (MCP)"],"bugs":["Fix import logic for importlib.metadata and pkg_resources"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for the Model Context Protocol (MCP) and fixes import logic for importlib.metadata and pkg_resources. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for Model Context Protocol (MCP) Adds support for MCP calls in mcp  and fastmcp . The agent will now automatically instrument the following core MCP primitives: Tools (via call_tool) Resources (via read_resource) Prompts (via get_prompt) Bug fixes Fix import logic for importlib.metadata and pkg_resources Updates logic around import of importlib.metadata to also attempt to use the importlib_metadata backport before falling back to pkg_resources.*. This also removes use of sys.version conditionals and fixes issues where Python 3.9 could only use pkg_resources despite having importlib.metadata available. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-101300","eolDate":"2026-06-09"},{"agent":"python","date":"2025-05-12","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.12.0","features":["Add support for new methods in Redis v6.0.0"],"bugs":["Fix conflicts with opentelemetry-proto package"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Redis  v6.0.0 and fixes conflicts with the opentelemetry-proto  package. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for Redis v6.0.0 Adds support for all client methods introduced in Redis  v6.0.0. Bug fixes Fix conflicts with opentelemetry-proto package Fixes an issue where the agent's internal copy of opentelemetry-proto  would conflict with any other packages relying on opentelemetry-proto (such as ChromaDB). This should now be treated as a separate package by OpenTelemetry and prevent any conflicts. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-101200","eolDate":"2026-05-12"},{"agent":"python","date":"2025-05-01","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.11.0","features":["Add support for Google Gemini via Google Generative AI SDK","Instrument new Kinesis methods"],"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Google Gemini via the Google Generative AI SDK and instruments new Kinesis methods. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for Google Gemini via Google Generative AI SDK Adds support for google-genai . The agent will automatically instrument embed_content calls for synchronous and asynchronous embeddings . The agent also now supports synchronous and asynchronous text generations  for text inputs in non-streaming cases. This includes calls made to generate_content for single text-only inputs and calls to send_message for multi-turn conversations. Instrument new AWS Kinesis methods Adds botocore  instrumentation to support new AWS Kinesis  methods including tag_resource, untag_resource, and list_tags_for_resource. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-101100","eolDate":"2026-05-01"},{"agent":"python","date":"2025-04-24","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.10.0","features":["Add async support for elasticsearch"],"bugs":["Add parsing of graphql config setting","Fix crash in Kombu when running with Sentry"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for async elasticsearch , fixes a graphql configuration parsing issue, fixes a bug in the Kombu  instrumentation and re-enables the Kombu instrumentation. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add async support for elasticsearch Adds support for async elasticsearch . Thanks fagnerzulin  for the contribution! Bug fixes Add parsing of graphql config setting Previously, when the setting instrumentation.graphql.capture_introspection_queries was set in the config file, this setting did not take effect. This has been fixed. Fix crash in Kombu when running with Sentry Fixes a crash in Kombu  instrumentation where a TypeError was raised from the inspect module. This bug was due to a conflict in wrapping between New Relic and Sentry. The Kombu instrumentation has also been re-enabled. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-101000","eolDate":"2026-04-24"},{"agent":"python","date":"2025-04-11","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.9.0","features":["Add OpenTelemetry compatible datastore span attributes"],"bugs":["Fix LangChain instrumentation for string response types","Disable Kombu instrumentation"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds OpenTelemetry  compatible datastore span attribute names, fixes a bug in LangChain  instrumentation, and temporarily disables Kombu  instrumentation. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add OpenTelemetry compatible datastore span attributes The datastore span attributes are now more consistent with OpenTelemetry  naming conventions Bug fixes Fix LangChain instrumentation for string response types Previously, when LangChain  returned string-type responses, the agent only captured the first character of the string. This has been corrected. Disable Kombu instrumentation Existing Kombu  instrumentation in the agent is crashing with a TypeError being raised from the inspect module. This instrumentation has been temporarily disabled and will be re-enabled in a future release once the root cause of the crash is identified and patched. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-100900","eolDate":"2026-04-11"},{"agent":"python","date":"2025-03-31","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.8.1","features":[],"bugs":["Fix import error in Kombu instrumentation"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes a bug with the latest Kombu  instrumentation. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Bug fixes Fix import error in Kombu instrumentation A missing import in Kombu 's instrumentation resulted in a crash for those using the instrumentation.  This has now been fixed. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-100801","eolDate":"2026-03-31"},{"agent":"python","date":"2025-03-27","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.8.0","features":["Add support for Kombu","Add support for mysqlclient","Update instrumentation for PyMySQL for versions 1.0.3 and above"],"bugs":["Safeguard startup of agent healthchecks against exceptions","Fix warning message around garbage collection runtime metrics sampler"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Kombu, mysqlclient, PyMySQL, and adds a few safeguards to prevent exceptions. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for Kombu Add support for producer and consumer message tracing in Kombu . In the case where Celery and Kombu are used together, a transaction is produced for both Celery and Kombu message consumption and Kombu consumer tracing is turned off by default. It can be enabled via the instrumentation.kombu.consumer.enabled setting. A new setting instrumentation.kombu.ignored_exchanges to ignore certain exchanges was also added and by default it ignores the celeryev queue which is a monitoring queue. Add support for mysqlclient (a MySQLdb fork for Python 3) Instrumentation for the Python 2 library MySQLdb  has been adapted to support the Python 3 fork mysqlclient . Update instrumentation for PyMySQL for versions 1.0.3 and above Instrumentation for PyMySQL  has been updated for newer versions of the library, and versions below 1.0.3 are no longer supported. Bug fixes Safeguard startup of agent healthchecks against exceptions Previously, the agent healthchecks could raise exceptions during startup, potentially resulting in agent crashes. This has been fixed. Fix warning message around garbage collection runtime metrics sampler Previously, a warning message was sometimes emitted which was related to the garbage collection runtime metrics sampler. This has been fixed. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-100800","eolDate":"2026-03-27"},{"agent":"python","date":"2025-03-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.7.0","features":["Add support for asynchronous AWS Bedrock LLM calls"],"bugs":["Fix crash in aiomysql instrumentation","Fix segfaults with greenlets"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for asynchronous AWS Bedrock LLM calls in aioboto3 , a fix for a segfault with greenlet s, a fixed a crash in aiomysql  instrumentation, and reformatted the codebase with Ruff . Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for asynchronous AWS Bedrock LLM calls Adds instrumentation to support calls to invoke_model and invoke_model_with_response_stream made on aioboto3  clients Bug fixes Fix crash in aiomysql instrumentation Previously, using aiomysql.sa (the included sqlalchemy engine) with the agent would result in a crash due to a missing __await__ method in the instrumentation. This has been corrected. Fix segfaults with greenlets Previously, a segfault occured when the maximum number of worker processes were called.  This was due to a combination of using a weak reference for the agent's trace ID caching and greenlet's greenlet.getcurrent() retrieval function being called after the last greenlet has already been garbage collected.  This fix allows the worker process to restart without the segfault occurring. Changes Reformatted entire codebase with Ruff Switched to Ruff  linter and reformatted the entire codebase. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-100700","eolDate":"2026-03-06"},{"agent":"python","date":"2025-02-06","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.6.0","features":["Add entity linking attributes for AWS Kinesis and AWS Firehose when using boto3 and botocore"],"bugs":[],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds entity linking for AWS Kinesis and AWS Firehose in boto3  and botocore . Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add entity linking attributes for AWS Kinesis and AWS Firehose when using boto3  and botocore . Adds attributes linking distributed traces with AWS Kinesis and AWS Firehose entities in the New Relic UI. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-100600","eolDate":"2026-02-06"},{"agent":"python","date":"2025-01-29","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.5.0","features":["Add Agent Control health reporting","Add support for cassandra-driver","Add support for new langchain vectorstore","Enhance stack traces logged by NewRelicContextFormatter"],"bugs":["Fix compatibility issues with structlog ProcessorFormatter","Check for ExceptionMiddleware removal in starlette.exceptions"],"security":null,"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds Agent Control health reporting, instrumentation for cassandra-driver , support for new a langchain  vectorstore, improves NewRelicContextFormatter stack traces logging, fixes compatibility issues with the structlog  ProcessorFormatter, and checks for ExceptionMiddleware removal in starlette.exceptions. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add Agent Control health reporting Adds agent health reporting capability to support the upcoming release of New Relic Fleet Control. Add support for cassandra-driver Instrumentation support was added for cassandra-driver . Add support for new langchain vectorstore Adds instrumentation for TablestoreVectorStore in langchain . Enhance stack traces logged by NewRelicContextFormatter The NewRelicContextFormatter now reports exception causes when logging stack traces. Thanks @sweco  for your contribution! Bug fixes Fix compatibility issues with structlog's ProcessorFormatter Fix was added for the case where the structlog  ProcessorFormatter is used as a logging.Formatter for both logging and structlog log entries. Check for ExceptionMiddleware removal in starlette.exceptions After starlette  v0.45.0 the import proxy for ExceptionMiddleware was removed from starlette.exceptions (and now only resides in starlette.middleware.exceptions). Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-100500","eolDate":"2026-01-29"},{"agent":"python","date":"2024-12-12","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.4.0","features":["Add support for async PyMongo","Add support for Motor","Add support for aiomysql","Add AWS account ID configuration setting","Link AWS entity for DynamoDB","Link AWS entity for Lambda"],"bugs":["Fix path typing issue in newrelic.initialize"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for async PyMongo , Motor , aiomysql , a new AWS account ID configuration setting, linking AWS entities for DynamoDB and Lambda, and fixes a path typing issue in newrelic.initialize(). Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for async PyMongo Instrumentation support was added for asynchronous PyMongo . Note that this API is currently in beta and may be subject to future breaking changes, which may affect instrumentation. Add support for Motor Instrumentation support was added for motor . Add support for aiomysql Add support for aiomysql . Add new AWS account ID configuration setting Some AWS instrumentations are not able to automatically determine the AWS account ID which is used to link the AWS entity in the service map. When cloud.aws.account_id is set, it will be used in certain AWS instrumentations such as DynamoDB to link the DynamoDB AWS entity in the service map. Link AWS entity for DynamoDB Add linking to the AWS entity in the service map for DynamoDB. This linking is done by utilizing the cloud.aws.account_id configuration setting. Link AWS entity for Lambda Add linking to the AWS entity in the service map for Lambda. This linking is done by attaching the ARN to the lambda call's span. Bug fixes Fix path typing issue in newrelic.initialize() Fixes a bug in newrelic.initialize() where pathlike objects were not accepted. This has been corrected to support strings, bytes, or PathLike  objects. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-100400","eolDate":"2025-12-12"},{"agent":"python","date":"2024-11-25","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.3.1","features":[],"bugs":["Fix agent crash when uploading package version info"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent fixes a bug in the package version collector that disabled telemetry from being sent to New Relic in certain cases. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Bug fixes Fix agent crash when uploading package version info Previously, if package versioning was a class property then the function itself was sent with the payload. This would then display the __repr__() of the versioning class in the environment stats. In v10.3.0, this task was tweaked and moved to the harvest cycle that caused a failure during the payload conversion to JSON and disabled the telemetry transmission. This release introduces logic to exclude invalid data types from the module payload. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-100301","eolDate":"2025-11-25"},{"agent":"python","date":"2024-11-18","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.3.0","features":["Add Valkey support","Add TOML configuration file support","Add protobuf v5 support for infinite tracing","Add support for attaching custom attributes to logs","Add support for attaching labels to logs","Minor cleanup of HTTPX instrumentation"],"bugs":["Collect module information periodically"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Valkey, configuration via TOML file, protobuf v5 for infinite tracing, attaching custom attributes and labels to log events, and some minor cleanup of HTTPX instrumentation. HTTP/2 support was validated for Daphne , Hypercorn , and HTTPX . Module information is now collected periodically which fixes a bug where the CPU usage would spike on application startup. The Python agent now allows you to opt-in to adding your custom tags (labels) to agent-forwarded logs. With custom tags on logs, platform engineers can easily filter, search, and correlate log data for faster and more efficient troubleshooting, improved performance, and optimized resource utilization. To learn more about this feature see the documentation . Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for Valkey Add instrumentation for Valkey . Thanks @jairhenrique  for the contribution! Add TOML configuration file support Support to read TOML configuration is now available. Thanks @Tatsh  for the contribution! Add infinite tracing pb2 file for protobuf v5 This adds an additional pb2 file used for infinite tracing that is compatible with protobuf  v5. Add support for attaching custom attributes to logs A new configuration option has been added called application_logging.forwarding.custom_attributes that will add custom attributes to all log events when set. Add support for attaching labels to log events Labels as attributes can now be added to log events. When application_logging.forwarding.labels.enabled is set the values in labels will be added to all log events. Labels can be excluded by setting application_logging.forwarding.labels.exclude. Enhancements Minor cleanup of HTTPX instrumentation Some minor cleanup was done in the HTTPX instrumentation. Validate HTTP/2 support Added tests to ensure HTTP/2 support for the following frameworks: Daphne Hypercorn HTTPX Bug fixes Collect module information from application periodically instead of at startup Previously, the New Relic Python agent collected the application's module information all at once during startup. In some extreme cases this would cause a large spike in CPU usage. This enhancement allows the agent to do this incrementally throughout the application's operation, preventing potential memory spikes during agent startup. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-100300","eolDate":"2025-11-18"},{"agent":"python","date":"2024-10-15","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.2.0","features":["Add Azure Operator Flag"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds a flag for the Azure init container operator. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add Azure Init Container Operator Flag New Relic can be integrated into applications hosted on Microsoft Azure, either directly , through an init container  for Azure Container Apps , or a pre-build startup script  for Microsoft Azure App Service . You can flag that this is the installation method used by setting the NEW_RELIC_AZURE_OPERATOR_ENABLED environment variable. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-100200","eolDate":"2025-10-15"},{"agent":"python","date":"2024-10-10","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.1.0","features":["Add support for Python 3.13","Add new LLM custom attribute context manager API","Add support for reporting of Amazon ECS Fargate Docker IDs","Add instrumentation for `SQLiteVec` vectorstore in Langchain"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent adds support for Python 3.13, adds a new Large Language Model (LLM) API, supports Docker ID parsing in Amazon ECS Fargate environments, and instruments a new Langchain vectorstore. Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . New features Add support for Python 3.13 The agent now supports applications running in Python 3.13. Add new LLM custom attribute context manager API The agent now includes a new context manager API that adds custom attributes to LLM events generated from calls to LLMs in application code. For more information on usage, please see our API documentation . Add support for reporting of Amazon ECS Fargate  Docker IDs The agent now reports Docker IDs for containers running in ECS Fargate environments. Add instrumentation for SQLiteVec vectorstore in Langchain The agent now instruments similarity_search for the SQLiteVec vectorstore. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-100100","eolDate":"2025-10-10"},{"agent":"python","date":"2024-09-26","downloadLink":"https://pypi.python.org/pypi/newrelic","version":"10.0.0","features":["Remove Python 2.7 support","Add Kafka server metric","Add capturing of memcache host and port","Add support for kafka-python-ng","Add support for uvicorn_workers","Automatically detect function signature in LangChain similarity search","Add environment variable for garbage collector runtime metrics"],"bugs":["Fix bug in gRPC entity name detection","Fix issue in LangChain where a thread is started and the transaction context is lost","Fix parsing of request and response when running OpenAI via LangChain","Instrument new path to OpenAI chat class","Fix pyscopg v3 API incompatibilities","Remove versioned logic in loguru instrumentation"],"security":[],"supportedOperatingSystems":null,"description":"Notes This release of the Python agent drops support for Python 2.7 and adds the following: a Kafka server metric host and port attributes for memcache support for kafka-python-ng support for uvicorn_worker an environment variable for garbage collector (GC) runtime metrics automatic detection for the function signature in LangChain 's similarity_search updated support for OpenAI 's chat class a fix for a bug in gRPC's entity name detection a fix for transaction context propagation loss in LangChain  in the case of a new thread parsing of the request and response when running OpenAI  via LangChain a fix for pyscopg  v3 API incompatibilities a fix that removes versioned logic in loguru  instrumentation Install the agent using easy_install/pip/distribute via the Python Package Index  or download it directly from the New Relic download site . Deprecations Remove Python 2.7 Support Removes compatibility with Python 2.7. Also removes support for the following libraries that were only supported on Python 2.7: umemcache oursql pywapi Pylons web2py weberror New features Add Kafka server metric Adds a metric to capture the host and port information for Kafka entities on both consumers and producers. This metric allows the UI to link AWS information with AWS MSK entities in the service map. Add capturing of memcache host and port Adds capturing of host and port info on the following memcache libraries: bmemcached , aiomcache , and pymemcache . This allows the UI to link AWS information with AWS memcache entities in the service map. Add support for kafka-python-ng kafka-python  has been released under a new name: kafka-python-ng . This continues to support kafka-python under the new package name. Add support for uvicorn_worker uvicorn.workers has been moved to a separate package called uvicorn_worker. This checks for both names of the module when reporting dispatcher information. Automatically detect function signature in LangChain  similarity_search Automatically detect the function signature when wrapping similarity_search. Add environment variable for garbage collector runtime metrics Garbage collector runtime metrics can now be enabled/disabled via the following environment variable: NEW_RELIC_GC_RUNTIME_METRICS_ENABLED. Bug fixes Fix bug in gRPC entity name detection Previously, the gRPC channel entity name was missing the first character(s) in specific cases. This bug has been fixed. Fix issue in LangChain  where a thread is started and the transaction context is lost Previously, when LangChain called certain chains, such as retrieval chains, LangChain started a thread that caused the transaction to be lost, resulting in broken instrumentation. This has been fixed so the transaction context is passed across threads and instrumentation still works for retrieval chains. Fix parsing of request and response when running OpenAI  via LangChain Previously, when running OpenAI  via LangChain  the request and response were a different format and were not being recorded. This issue has been fixed. Instrument new path to OpenAI  chat completions class OpenAI  moved the ChatCompletions class to a different path which prevented the instrumentation from being applied. This has been fixed. Fix pyscopg  v3 API incompatibilities Expand DBAPI2 wrappers to allow arbitrary kwargs on executemany(). Upgrade psycopg  v3 instrumentation to allow arbitrary kwargs on executemany(). Rename existing psycopg v3 wrapper arguments to match the upstream library's names for compatibility. Remove versioned logic in loguru instrumentation Removed versioned logic in loguru  instrumentation to fix a bug that occurred when the version was undeterminable. Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more  about keeping agents up to date. See the New Relic Python agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/python-release-notes/python-agent-100000","eolDate":"2025-09-26"},{"agent":"dotnet","date":"2022-06-08","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.9.0.0","features":["Add log instrumentation for NLog","Add support for code level metrics CodeStream integration","Installers now clean up deprecated instrumentation"],"bugs":["Properly report application logging configuration during agent connect"],"security":["Upgrade Newtonsoft.Json to v13.0.1"],"supportedOperatingSystems":null,"description":"If you are currently running .NET Framework version 4.6.2 or higher, please update your .NET agent to the latest version . Notice:  If using Microsoft.Extensions.Logging as your logging framework of choice, please use .NET agent version 10.1.0 or newer.  We encourage you to adopt the newer version due to bug #1230 , which we fixed in #1237 , that was resolved in .NET agent version 10.1.0. New Features Adds support for logging metrics, forwarding application logs, and enriching application logs written to disk or standard out for NLog versions v5 and v4. #1087 Adds integration with CodeStream, introducing code-level metrics! Golden signals visible in your IDE through New Relic CodeStream. Learn more here . For any issues or direct feedback, please reach out to support@codestream.com Updates the following installation methods to check for and remove deprecated files. (#1104 ) MSI Installer Azure Site Extension RPM package DEB package Fixes Upgrades Newtonsoft.Json to version 13.0.1 to address potential security vulnerabilities identified by Snyk (#1107 ) The agent will now send the values of application logging config options (e.g. application_logging.forwarding.enabled) to the agent initialization settings page. (#1135 ) Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.9.0.0-scriptable-installer.zip           | 3D5DBC46B92E8B00D61366F53964623453D918350A6AFC7C8A98E1863379F05F |\n| newrelic-agent-win-x64-9.9.0.0.msi                            | 867D6059E0D49C2CD4531EAAB04895AC270ACB19F814CE3BDE562F0F89400AA3 |\n| newrelic-agent-win-x64-9.9.0.0.zip                            | 0F461830FE3610C2D5BB23E86D8DEC701F3300F25C2EA974A306011F40A33A0E |\n| newrelic-agent-win-x86-9.9.0.0.msi                            | E87AF61CD50D0CFFE15C1A640127CC67DB67347DC952E3D97677EAACFD5A1A4D |\n| newrelic-agent-win-x86-9.9.0.0.zip                            | 20DBE5A6A0E6B4D4B1D1FA8F5941974D8D1E87AECDF9EDF0B50A771B3EB02F5E |\n| newrelic-netcore20-agent-9.9.0.0-1.x86_64.rpm                 | 9BA2012C3737F2200EF1523088BF1D5573B7B8571744E41880FCCF7F715035C5 |\n| newrelic-netcore20-agent-win-9.9.0.0-scriptable-installer.zip | 4C7E2770EF8C0044952FE9FDC340B7A5FB10314F5CA0F6934E74E45D9692E974 |\n| newrelic-netcore20-agent-win-x64-9.9.0.0.zip                  | 9EA9F21496C6F07AA08B9493746959A3CEC8BDD3F2D9E818BE030BD2D6EA5BC0 |\n| newrelic-netcore20-agent-win-x86-9.9.0.0.zip                  | A536692FB98ED97027D3CA63AC93B50C96EB7BBD13368542B04111B63BD50C96 |\n| newrelic-netcore20-agent_9.9.0.0_amd64.deb                    | 5D15D22C645AA552BCBA2CBC215E411CB220D1A730B1D801E383E29D085A173A |\n| newrelic-netcore20-agent_9.9.0.0_amd64.tar.gz                 | B46F3B2CAF0722A43F9E726F775A921A290E557899AE57F2A38C176E120F8E8B |\n| newrelic-netcore20-agent_9.9.0.0_arm64.deb                    | 6DC6ED28E4F8EE84A0E9E7EDB0F59AD1400EBC6558CAA536E136E47D59BAB270 |\n| newrelic-netcore20-agent_9.9.0.0_arm64.tar.gz                 | 6DE05E0B34ABDA54730EE70CE2E411A06AA4D05F45102F5EF1A6F161D9A11702 | Support statement New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.29.0 . Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9900","eolDate":"2024-06-08"},{"agent":"dotnet","date":"2022-05-19","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.8.1.0","features":[],"bugs":["Agent no longer intermittently forwards logs when the log forwarding is disabled at the account level","Ignore deprecated instrumentation to avoid duplicate data"],"security":[],"supportedOperatingSystems":null,"description":"Notice:  If using Microsoft.Extensions.Logging as your logging framework of choice, please use .NET agent version 10.1.0 or newer.  We encourage you to adopt the newer version due to bug #1230 , which we fixed in #1237 , that was resolved in .NET agent version 10.1.0. Fixes Fixes an issue with log forwarding  where an agent could momentarily forward logs even if the feature had been disabled at an account level. (#1051 ) Adds an internal list of deprecated instrumentation xml files which will cause the profiler to ignore deprecated instrumentation. This feature avoids an issue where orphaned deprecated log forwarding instrumentation could conflict with newer instrumentation. (#1051 ) Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.8.1.0-scriptable-installer.zip           | 409AF36381E1226E6C96BC01E105FA4A1C788C7531BB3D45F8498D909F3F9583 |\n| newrelic-agent-win-x64-9.8.1.0.msi                            | 6795B97B5C0E520B155F1F2400C69B23519404DE93619C64D1D44BB7CF2BD7C0 |\n| newrelic-agent-win-x64-9.8.1.0.zip                            | 4C488AA142B3CF96DC47B48736F5C33A05920F5C7F0D750AA769897133F4913B |\n| newrelic-agent-win-x86-9.8.1.0.msi                            | 31FB12E2F4D750E2A2AE8859729DE041E064111B0BB5DFA1BCD5F6524F3A4FAC |\n| newrelic-agent-win-x86-9.8.1.0.zip                            | 780E044D65A05B664149AD6080F3910A0A455CBD6C14EE51351A73D35A217178 |\n| newrelic-netcore20-agent-9.8.1.0-1.x86_64.rpm                 | 8D2E6AC573B88C95BEBDC58522D068A15159BDD5DAB1912BCFABAB4160250FF9 |\n| newrelic-netcore20-agent-win-9.8.1.0-scriptable-installer.zip | A98560CCD5F0DA7521A6AE1859D07B91C71B01D820D6904B5C4951324C413D64 |\n| newrelic-netcore20-agent-win-x64-9.8.1.0.zip                  | D0B1D7593A982EEA60F1C7F570B276DFCE26C754100DDB8132DF8BDC301EF12D |\n| newrelic-netcore20-agent-win-x86-9.8.1.0.zip                  | 34C2FF00089FDE7E5A3FC7623C18B9DC2EE5798C50318B53A0F3C29F10E30D0E |\n| newrelic-netcore20-agent_9.8.1.0_amd64.deb                    | 1A457E0802D543A6BA617E9001A9C6FA2936B38693ADE99E4CCF1291609EF0A8 |\n| newrelic-netcore20-agent_9.8.1.0_amd64.tar.gz                 | 63691200311EA17CE73767E40471EE5DA32884EA4C100D188E2ABC1E4C3EB132 |\n| newrelic-netcore20-agent_9.8.1.0_arm64.deb                    | EE380761155A398143BB4162BF43C41C41D1E780DC32E5A4CF4DF4C3DA1C4882 |\n| newrelic-netcore20-agent_9.8.1.0_arm64.tar.gz                 | F253BACE2E517163818F9EEFD909EBFD476453D12E8518E27DE125F692126C28 | Support statement New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.28.0 . Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9810","eolDate":"2024-05-19"},{"agent":"dotnet","date":"2022-05-05","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.8.0.0","features":["Increase maximum length of error messages to 1023 characters","Add environment variables for attribute filtering","Add environment variables to disable cloud provider detection","Add environment variables to configure agent proxy","Add configuration option to force new transactions in async scenarios"],"bugs":["Fix capture of explain plans for parameterized stored procedures","Fix duplicate log instrumentation for Serilog"],"security":[],"supportedOperatingSystems":null,"description":"Notice:  If using Microsoft.Extensions.Logging as your logging framework of choice, please use .NET agent version 10.1.0 or newer.  We encourage you to adopt the newer version due to bug #1230 , which we fixed in #1237 , that was resolved in .NET agent version 10.1.0. APM logs in context Automatic application log forwarding is now enabled by default. This version of the agent will automatically send enriched application logs to New Relic. To learn more about about this feature, see the APM logs in context documentation . For additional configuration options, see the .NET logs in context documentation . To learn about how to toggle log ingestion on or off by account, see our documentation to disable automatic logging  via the UI or API. New features Error messages in error traces and error events now retain up to 1023 characters instead of 255 characters. #1058 New environment variables have been added for AllowAllHeaders and Attributes configuration settings. See our configuration documentation  for more details. #1059 Introduces environment variables to enable/disable cloud detection  to facilitate customer use cases and reduce errors in logs. (#1061 ) New environment variables have been added for all Proxy configuration settings.  See our configuration documentation  for more details. #1063 Introduces a new configuration option to force custom instrumentation to create new transactions  in async scenarios versus re-using an existing transaction. #1071 Fixes Fixes Agent fails to execute explain plan for parameterized stored procedure. (#1066 ) Fixes getting duplicate logs using log forwarding and Serilog. #1076 Deprecations Microsoft has officially EOLed: .NET Framework versions 4.5.1, 4.5.2, and 4.6.1  on  Apr 26, 2022. .NET Core version 2.0  on October 1, 2018. .NET Core version 2.1  on August 21, 2021. .NET Core version 2.2  on December 23, 2019. .NET Core version 3.0  on March 3, 2020. The official product lifecycle start and end dates can be found on the Microsoft documentation for .NET Framework  and for .NET Core onward . Our .NET agent support of these framework versions will continue as is with the released versions. In a future major release, we will target .NET Framework 4.6.2 and .NET Core 3.1 onwards. Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.8.0.0-scriptable-installer.zip           | C8B38337C08B4D4D9AF3385FD731E685A27F9813174D8F021B942FFDD08BB010 |\n| newrelic-agent-win-x64-9.8.0.0.msi                            | 5B247617A1B20D52F7FF9B1A3DA2D31A5DDAC321CA0453115007FE665F8FD231 |\n| newrelic-agent-win-x64-9.8.0.0.zip                            | A5C0731D694EF4DC182D057073351706F642DFF28415341B38219D07F4039B0F |\n| newrelic-agent-win-x86-9.8.0.0.msi                            | FFB556903F65380B21686E229A3E8570C2A673EBCC3A514CC416C868FD9E9CBD |\n| newrelic-agent-win-x86-9.8.0.0.zip                            | CB95C49071E808DC78523D5FF366A2FA0CF2B95B2361F201E4E5A6FAE4470295 |\n| newrelic-netcore20-agent-9.8.0.0-1.x86_64.rpm                 | 537F369DB1F97384C46F11AEF88A6862A0CDFE92327325133AC1FBC0E8D05DA5 |\n| newrelic-netcore20-agent-win-9.8.0.0-scriptable-installer.zip | 15C04CFDB251AE0C6CB458EFEAFA8151ED66B361846F87E8DC28EB88AD6E03D8 |\n| newrelic-netcore20-agent-win-x64-9.8.0.0.zip                  | 988A41FA46F9088F51FCC5F33FE97A39128BB9FFEC9F827F8DB13D02905CCE10 |\n| newrelic-netcore20-agent-win-x86-9.8.0.0.zip                  | ABBEE303EAD4C1738E2B724542900321584B9298E552D1626F3BA46FBCA0531E |\n| newrelic-netcore20-agent_9.8.0.0_amd64.deb                    | 3BC8F31BE6F4099C4E5AC82BBF27A701E4E801C02A585E661544278662EDC136 |\n| newrelic-netcore20-agent_9.8.0.0_amd64.tar.gz                 | 214ED65181B717AC556860F77C9987ED07FA21CF53C1865DD74DB41AFD75FAE1 |\n| newrelic-netcore20-agent_9.8.0.0_arm64.deb                    | C32185FF50417C25A4E4C2D4AB50D4C16C8D0CF1607494255E4A88E91FBBA47F |\n| newrelic-netcore20-agent_9.8.0.0_arm64.tar.gz                 | B12C81C412892A002DEB40B17949212AA6EA7FC109225380EE0FF5AA12520EEF | Support statement New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.28.0 . Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9800","eolDate":"2024-05-05"},{"agent":"dotnet","date":"2022-04-13","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.7.1.0","features":[],"bugs":["Add missing application log forwarding components to MSI installer","Create intermediate log directories on Linux"],"security":[],"supportedOperatingSystems":null,"description":"Notice:  If using Microsoft.Extensions.Logging as your logging framework of choice, please use .NET agent version 10.1.0 or newer.  We encourage you to adopt the newer version due to bug #1230 , which we fixed in #1237 , that was resolved in .NET agent version 10.1.0. Fixes Adds missing instrumentation for application logging feature when using the MSI installer (#1055 ) Fixes issue on Linux  when specifying a non-default profiler log directory with non-existent intermediate directories. (#1051 ) Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.7.1.0-scriptable-installer.zip           | 58C4A3BD47EABF9908F8D0940C634E9AAB291DB63B40A116B4E3D6F4796D8C2D |\n| newrelic-agent-win-x64-9.7.1.0.msi                            | 9DB3F1990F8BAE604DB8E51E6CDD2F7E3558EAA86680418541276E5DDEA5F597 |\n| newrelic-agent-win-x64-9.7.1.0.zip                            | 52C7D0321882D2564A3CF2638705B93C337185D50D8CC1D2AAE19653AA70CA73 |\n| newrelic-agent-win-x86-9.7.1.0.msi                            | 17CA9FC7BE010A193EA229E0A3479EEF357C4AC7C0994877E9D04A95D8B1FBEC |\n| newrelic-agent-win-x86-9.7.1.0.zip                            | 57277A14609D1540DF3F5CBD44D0E8CA848A8DD3F149FC661B1EED548FF9F171 |\n| newrelic-netcore20-agent-9.7.1.0-1.x86_64.rpm                 | E98AF466FFA088B2FDF0E649BA882B81BAC4489C6DDC80CDF708481F3AB68441 |\n| newrelic-netcore20-agent-win-9.7.1.0-scriptable-installer.zip | 8EAAF6F13536B233344DEDED46EC5BA19A4F4EB925D605B2CDE071DB7391EB73 |\n| newrelic-netcore20-agent-win-x64-9.7.1.0.zip                  | A036A53815A3EC69178B2A2FEAB49715AF4FC4390D0541D6541A1AF09110F665 |\n| newrelic-netcore20-agent-win-x86-9.7.1.0.zip                  | 65208DA30735F797439CACCFCF32984CC37B4DBDA15D865E343AF79A47CDE50D |\n| newrelic-netcore20-agent_9.7.1.0_amd64.deb                    | 552FF7CC2023B8E905D744B3A817BBCCE691F36C802425E1665F40EB5F89F171 |\n| newrelic-netcore20-agent_9.7.1.0_amd64.tar.gz                 | 23642C42C5890F8019FDBEA958DE0CAFDA51255B4C5176DD509921CDCD63230A |\n| newrelic-netcore20-agent_9.7.1.0_arm64.deb                    | 792D5BD7F7F8D05E6B954FF0A5B94A8BA7B4E656259D8721B256E3391518D5A0 |\n| newrelic-netcore20-agent_9.7.1.0_arm64.tar.gz                 | 601BB88E1E373C9E28FF24B57A44E5C1DFDE2026A94984176669B772D542D344 | Support statement New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.26.630.0 . Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9710","eolDate":"2024-04-13"},{"agent":"dotnet","date":"2022-04-04","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.7.0.0","features":["Add in agent log forwarding","Add application log metrics","Add in agent log decoration","Add flexibility to accepted values for boolean environment variables"],"bugs":["Add environment variable to disable the use of AppDomain for method caching"],"security":[],"supportedOperatingSystems":null,"description":"Notice:  For the new application logging features, if you install using the MSI, please update to version 9.7.1 or later. Notice:  If using Microsoft.Extensions.Logging as your logging framework of choice, please use .NET agent version 10.1.0 or newer.  We encourage you to adopt the newer version due to bug #1230 , which we fixed in #1237 , that was resolved in .NET agent version 10.1.0. New Features Adds support for logging metrics which shows the rate of log message by severity in the Logs chart in the APM Summary  view for Log4net, Serilog, and Microsoft.Extensions.Logging. This is enabled by default in this release. (#1034 ) Adds support for forwarding application logs to New Relic. This automatically sends enriched application logs for Log4net, Serilog, and Microsoft.Extensions.Logging. This is disabled by default in this release. (#1034 ) Adds support for enriching application logs written to disk or standard out for Log4net, Serilog, Microsoft.Extensions.Logging. This can be used with another log forwarder if in-agent log forwarding is not desired. We recommend enabling either log forwarding or local log decorating, but not both features. This is disabled by default in this release. To learn more about APM logs in context and the configuration options, please see the documentation here . (#1034 ) Adds flexibility to what is accepted to enable/disable boolean environment variables per FR #1008 . \"0\"/\"1\", and case insensitive \"true\"/\"false\" are now accepted. (#1033 ) Fixes Adds a new environment variable NEW_RELIC_DISABLE_APPDOMAIN_CACHING for customers to try when experiencing #533 high lock contention related to AppDomain.GetData()  usage by the agent when profiling .NET Framework applications. (#1033 ) Deprecations The scriptable installers are now deprecated and will be removed from the download site in a future major release. (Issue: #571 ) The established release installers are now deprecated and will be removed from the download site in a future major release. (Issue: #578 ) Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.7.0.0-scriptable-installer.zip           | FE528292625D80547D698FC482D1EC373CC407314449B7F89F732ED301103885 |\n| newrelic-agent-win-x64-9.7.0.0.msi                            | B27BDD508CCB360D652FB23EDB5F8DFB755D96EEB74B7F4EE45D748F13A6B9A8 |\n| newrelic-agent-win-x64-9.7.0.0.zip                            | 7FC6D2BD6DEC16E34CEDE92E4B54759BDC28EBFBF5AFCBB257F09F88D172CFAE |\n| newrelic-agent-win-x86-9.7.0.0.msi                            | 7567558EC799B2F573B042D45AB7490DA59680686FF8CECA67CF7DB20FD8B4AC |\n| newrelic-agent-win-x86-9.7.0.0.zip                            | B1DDB86396D21C050103DA8B3FE977245C2081A26702B5AD91FFCAFA50ECF17E |\n| newrelic-netcore20-agent-9.7.0.0-1.x86_64.rpm                 | BA401AF53ACA7D9C2C88338D6B54BC1B6DF025C1A07D3F9FE88CF33D4922A031 |\n| newrelic-netcore20-agent-win-9.7.0.0-scriptable-installer.zip | 97389E969F8DB68F5F5CFE9B8E299C8AC828530E2C3D2DDA4A0736D06C26F79A |\n| newrelic-netcore20-agent-win-x64-9.7.0.0.zip                  | B33A80F392FB80FB3D02CFF70F1995A2BBC61956575235AADDF5F9B7A0BBF585 |\n| newrelic-netcore20-agent-win-x86-9.7.0.0.zip                  | D04A2EE1DCB95248E07E54C12F8D5E7434EE871BAC63E68729FE7651670E5C3C |\n| newrelic-netcore20-agent_9.7.0.0_amd64.deb                    | 36C85CA42B73BC634E54A63D4DCF422E158B5475E316953D15AB4EA579A20152 |\n| newrelic-netcore20-agent_9.7.0.0_amd64.tar.gz                 | 3AF28D0C6650AD9C76567A28B766E5357AA097B2147C84EE248D98A53FBA2756 |\n| newrelic-netcore20-agent_9.7.0.0_arm64.deb                    | CD592E0975874AE9E9BEC6EEF686045E47313B0021AD1BDA391F5D9B0F8E704F |\n| newrelic-netcore20-agent_9.7.0.0_arm64.tar.gz                 | A6CAC159D5E6DFEA058BAD3369FA48B9F97789EE0BCE0BF7C90D875ABE01EB8E | Support statement New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.26.630.0 . Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9700","eolDate":"2024-04-04"},{"agent":"dotnet","date":"2022-03-15","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.6.1.0","features":[],"bugs":["Fix application pool allow/deny list issue"],"security":[],"supportedOperatingSystems":null,"description":"Fixes Fixes application pool allow/deny listing bug  introduced in 9.5.0 (#1015 ) Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.6.1.0-scriptable-installer.zip           | 5C06B19B9D29D0F8E47170083EE5A9A1D7C576BC049E6C207AD69D069E09E6F6 |\n| newrelic-agent-win-x64-9.6.1.0.msi                            | 2AE3A0E647BD9A490B9D4F3B23817784B5FA70B5F949136E1637206118A978C9 |\n| newrelic-agent-win-x64-9.6.1.0.zip                            | 4D1053241C2F4849199750D598A473DB81687F0C6357582A4DA76C2E5DED82F5 |\n| newrelic-agent-win-x86-9.6.1.0.msi                            | 835A95F61A9097A05A9EDECADA4BD9E665FF0BFF71786B238EAC0263B8E039EE |\n| newrelic-agent-win-x86-9.6.1.0.zip                            | D84DE006542F1EDEAD1C07F6FD7BF9E82405A777A9BFC5A72FE679310EA5007B |\n| newrelic-netcore20-agent-9.6.1.0-1.x86_64.rpm                 | 50317ABECA590387AEC7A97D7C40AB42981E074C888647174C01B2B326BF30E3 |\n| newrelic-netcore20-agent-win-9.6.1.0-scriptable-installer.zip | 759ADF56231178A5285087277D4968018DB6889F13BE7C8473FE87CCD1ABCA62 |\n| newrelic-netcore20-agent-win-x64-9.6.1.0.zip                  | CC080FBF6C4B46171F994C40DC36937E85E78A3665927E5CC0DD768BD6F4F555 |\n| newrelic-netcore20-agent-win-x86-9.6.1.0.zip                  | 01FC9A6DA642257ABDD9666831D3F68B2EB8D50C74279878B73D6E8E221AFF51 |\n| newrelic-netcore20-agent_9.6.1.0_amd64.deb                    | 99D46257FBE232806C8D79AFD95FE9A95F6194C9A78B023C9743C84D3BCB5A16 |\n| newrelic-netcore20-agent_9.6.1.0_amd64.tar.gz                 | 2ABDB8AE794660CE360A0AE13C6D32A224E67E2F8BDED8283E9B41F2F808BE77 |\n| newrelic-netcore20-agent_9.6.1.0_arm64.deb                    | 9E422642220A1E164ADBA6C48269207B00CBDD5FBA3491BE26AF4B91EBC94137 |\n| newrelic-netcore20-agent_9.6.1.0_arm64.tar.gz                 | A5102EDAEFC11C90368809C929ED80AA609D448FF67FA544CD7E75E27FE34BB1 | Support statement New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.26.630.0 . Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9610","eolDate":"2024-03-15"},{"agent":"dotnet","date":"2022-02-24","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.6.0.0","features":["Add supportability metrics for agent data"],"bugs":[],"security":["Use IMDSv2 to gather AWS utilization details"],"supportedOperatingSystems":null,"description":"New Features Adds new supportability metrics to track agent endpoint data usage. New metrics will be reported under the Supportability/DotNET/Collector namespace. (#899 ) Uses IMDSv2 instead of IMDSv1 to gather utilization details for AWS hosted instances. 965 Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.6.0.0-scriptable-installer.zip           | 3D65ED0B10977CD13EFD8A4CC24B7F06B0B6B60E784830A09B4384EE6F5AD9BD |\n| newrelic-agent-win-x64-9.6.0.0.msi                            | 3C514C6C2C27DD33EBBFE84469333CC812045B42626619AA5BE3519FCEC17EAB |\n| newrelic-agent-win-x64-9.6.0.0.zip                            | 7CCC53713245555D52F910F368621DDC83F133A1A21F29FD917E2C515283B521 |\n| newrelic-agent-win-x86-9.6.0.0.msi                            | A2E015DB73832DB818CB1E184890ED62B97FAF39EB75A45458881CB36AD1DEE3 |\n| newrelic-agent-win-x86-9.6.0.0.zip                            | B962DC612C98F41F3AE63855119967246C7104CC65865F183F35E63CFF6AC36E |\n| newrelic-netcore20-agent-9.6.0.0-1.x86_64.rpm                 | 1578AA7CEC1B4AB798F0359F404F1AED2720BEA4EA20A491F54A5E6FE14D0AAA |\n| newrelic-netcore20-agent-win-9.6.0.0-scriptable-installer.zip | E61D552478F5808677DAAD10460B4C77C822157097BD4625E6CDBB9A20E65B53 |\n| newrelic-netcore20-agent-win-x64-9.6.0.0.zip                  | 25A5854FA85C7BCC33C9D6613B4FF2271ABAAE303C3361AA18AD37B41E59E193 |\n| newrelic-netcore20-agent-win-x86-9.6.0.0.zip                  | 2D839B98BDB0DE52D5F4BBAD2FF3DCE066492A4A21E81B49FE23397E9C22CCB9 |\n| newrelic-netcore20-agent_9.6.0.0_amd64.deb                    | 53B716293BBE577940514ED088A456FD41498A1351464C00E4697B94EA867AE6 |\n| newrelic-netcore20-agent_9.6.0.0_amd64.tar.gz                 | 18C66A4EF8023D83375A4F450A064892B5189A1BEEDBF393D2EB7E874F92CA96 |\n| newrelic-netcore20-agent_9.6.0.0_arm64.deb                    | C8826C78CEE2BF0B0C2F73AB65FC06BE74DE931EFDDD0A162A5BF907589852E5 |\n| newrelic-netcore20-agent_9.6.0.0_arm64.tar.gz                 | C8DDFD3DA29496DC760028C915E43FE54E46ACD10B213BB2F55F83DA82309431 | Support statement New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.24.244.0 . Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9600","eolDate":"2024-02-24"},{"agent":"dotnet","date":"2022-02-03","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.5.1.0","features":[],"bugs":["Fix application crash on Alpine Linux"],"security":[],"supportedOperatingSystems":null,"description":"Fixes Fixes application crashes on Alpine Linux  introduced in 9.5.0. (#929 ) Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.5.1.0-scriptable-installer.zip           | E4E522D118C900E5BEF28249DEFE53DEAF1CC95B88C75B39F3539B5650E213F7 |\n| newrelic-agent-win-x64-9.5.1.0.msi                            | 7693E43022923020CD3799D8B7504CDF98564FCB4455E505C592E82C75A305E2 |\n| newrelic-agent-win-x64-9.5.1.0.zip                            | B0A9160EAF659D96EF3D34F561251B80FA031B1066B0BCC9908073DE69D38FFC |\n| newrelic-agent-win-x86-9.5.1.0.msi                            | 3ED42E06993F514E5D6C086CD5D40C7BC1E5DF674B146D2C9E2C1C9A4F89E7D2 |\n| newrelic-agent-win-x86-9.5.1.0.zip                            | B9785E8245F60ACE2C1296EF03BFD882626E1830996C87E14721F307FD0A89D3 |\n| newrelic-netcore20-agent-9.5.1.0-1.x86_64.rpm                 | 8E5F0FDA4D7598F3F20448DD6E9C8481C560C566A1728B26C9F475B85A927FF9 |\n| newrelic-netcore20-agent-win-9.5.1.0-scriptable-installer.zip | F730610AA3855B95E6D9D95D9787E8578BB7203B4A6C67821C5E72065EA33367 |\n| newrelic-netcore20-agent-win-x64-9.5.1.0.zip                  | B4C2029110CC419E3B7C87441E154029C2A7EB75FA96A172BE72591CF166B75A |\n| newrelic-netcore20-agent-win-x86-9.5.1.0.zip                  | 4E01F117016CB30E5EC996B2B7A96A2D6E2912CF804BD121821B0EE5CFB1967E |\n| newrelic-netcore20-agent_9.5.1.0_amd64.deb                    | D38B442F8BF8F7C9C11C9A65F3FBBCA1138332592B73CC03E4152781258A83A2 |\n| newrelic-netcore20-agent_9.5.1.0_amd64.tar.gz                 | CA86928B964D525D8BC25C89D559DB74411B5376BFFCD6ECECC4C3932783FB0A |\n| newrelic-netcore20-agent_9.5.1.0_arm64.deb                    | 76BC71ACC63E9A1A8957DA01863061062FABB7700A44C72A183FD50D4BE4C1C4 |\n| newrelic-netcore20-agent_9.5.1.0_arm64.tar.gz                 | 9CB898CC055A4D9B2D923732E8726C3295A90441F6E74941ECFC95084828969A | Support statement New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.24.244.0 . Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9510","eolDate":"2024-02-03"},{"agent":"dotnet","date":"2022-02-01","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.5.0.0","features":["Use same Profiler for .NET Framework and .NET Core"],"bugs":["Fix inaccurate NuGet package metadata"],"security":[],"supportedOperatingSystems":null,"description":"Do not install this version if you are using the agent on Alpine Linux; it will crash your applications.  See this issue  for more details. New Features Internal improvements to runtime detection logic in the profiler component of the agent. (#891 ) Fixes Fixed an issue with NuGet package metadata . (#901 ) Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.5.0.0-scriptable-installer.zip           | FB2C1DD6766A17AB202DC84013125DB68BEC70AB6F9C4BD85E2909BCD57BAC58 |\n| newrelic-agent-win-x64-9.5.0.0.msi                            | 5876943564BBF549DC5727E62F33EB4A99C5126186C649B97B6FF3561D221AD3 |\n| newrelic-agent-win-x64-9.5.0.0.zip                            | 4B7733F5891910DA2702453C794045521259C6D54567768AC8CF2D9136638971 |\n| newrelic-agent-win-x86-9.5.0.0.msi                            | B926ADDE8CEF4DD17C386A4C7F021A3F1A50C65A5D305ADD3A9A596CE7861D49 |\n| newrelic-agent-win-x86-9.5.0.0.zip                            | 77AD919BBE4CB3FA7CB473DAFC158758C02451A29950FFAAE67C06CE39E09B01 |\n| newrelic-netcore20-agent-9.5.0.0-1.x86_64.rpm                 | ED012BBD19031FF29798A0A920F77B492F609528C7491D2FA5A0199E51C70981 |\n| newrelic-netcore20-agent-win-9.5.0.0-scriptable-installer.zip | 7295C13DA7E11527386F9BE284BDA26D1467089602146E20C3833DD59B418E15 |\n| newrelic-netcore20-agent-win-x64-9.5.0.0.zip                  | 86050C0B7A122AD96A1318FD17F0BB0389668956DAE806706DAC8792752527F4 |\n| newrelic-netcore20-agent-win-x86-9.5.0.0.zip                  | 6ADC5B1AF32190ED62AD4132E8F00A06811EA629EC38CAE3160D77479454C17B |\n| newrelic-netcore20-agent_9.5.0.0_amd64.deb                    | 5A85628FD87F0EA5AA846AA4534400CB1B871752BD3B553D991CB5D67DB1DD93 |\n| newrelic-netcore20-agent_9.5.0.0_amd64.tar.gz                 | 525B218F26859FABA57E19DFA724E7D9177C2D7E517A894779B2BD0961E83DC2 |\n| newrelic-netcore20-agent_9.5.0.0_arm64.deb                    | 6082EAB15EEBE6DCC36D5D8FBF35CFD6C523F7E05E5A65038CE6FBC8A1119C5A |\n| newrelic-netcore20-agent_9.5.0.0_arm64.tar.gz                 | 458BD2E3E183986D45F36E1920E860054737902ACD3E0EA65173A9552A607574 | Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.24.244.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9500","eolDate":"2024-02-01"},{"agent":"dotnet","date":"2022-01-18","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.4.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Allows NewRelicQueryName to be specified for SQL, to implement this suggestion . Thanks to community contributor @kevinpohlmeier for the implementation. (#799 ) Fixes Resolves an issue where GC metrics were not being properly captured for .NET 6 applications (#874 ) Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.4.0.0-scriptable-installer.zip           | 6CC4989FBB8DD0D68036D8FEFC1349840D7909AB60700B45A24EC7CDCF6C3158 |\n| newrelic-agent-win-x64-9.4.0.0.msi                            | BFC0E3043EF6CD2667C526BB6C18B037CB9FC835EE0C8CE69EE3B60624149180 |\n| newrelic-agent-win-x64-9.4.0.0.zip                            | AD0AB9CC4E62046C0077A6C1A9B79F3395DBA9F4D88D3C1189673DCFFB3CBE45 |\n| newrelic-agent-win-x86-9.4.0.0.msi                            | C6F2C0568B35E63CCDC19E85271D1E71E1C1147CC5763498EB8C61411DA52619 |\n| newrelic-agent-win-x86-9.4.0.0.zip                            | EBA4F1EE56F68BB3F20CC2488CC494FFA838BC0209A1F0D9724F920E93D1A4FC |\n| newrelic-netcore20-agent-9.4.0.0-1.x86_64.rpm                 | EA0753FAF753FA93E3DCB4C4F8981B220B3C26CE69F8C5C5D06D7597325707FC |\n| newrelic-netcore20-agent-win-9.4.0.0-scriptable-installer.zip | F8B716342C03B6A99431B91940E1B5D54C3C097F3C96F31FC01E37FBC60AE019 |\n| newrelic-netcore20-agent-win-x64-9.4.0.0.zip                  | 809D6C55C3D016C91AE7A5D1F0E4EBA8D2B253E4C0693C7A6C5763A4FF18BE61 |\n| newrelic-netcore20-agent-win-x86-9.4.0.0.zip                  | BCFD52C6425B62AD7442B9CF60BF458BF96641025E4F7CAF006463E4CCF5704E |\n| newrelic-netcore20-agent_9.4.0.0_amd64.deb                    | 46F39D06CC349889E94A72FDE094CA2BE6D27BF16961FEE88531076ECC58593F |\n| newrelic-netcore20-agent_9.4.0.0_amd64.tar.gz                 | A6452B05599EC84C4B2DC08A52DFB16AF652AE6C89C88C35306D7EAF05FB31B3 |\n| newrelic-netcore20-agent_9.4.0.0_arm64.deb                    | 1C73FBC95935F5B11FFE260E8D567C2438893A3BB2F8A26F50BF567CD5321EE1 |\n| newrelic-netcore20-agent_9.4.0.0_arm64.tar.gz                 | 3E738DBB50A6C460386250FDE4DA4EAC9D5046999562C8A72A8D9D7DC15DADF0 | Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.24.244.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9400","eolDate":"2024-01-18"},{"agent":"dotnet","date":"2022-01-04","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.3.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features NServiceBus versions 6 and 7 are now supported in .NET Framework and .NET Core. (#857 ) Add ability to disable agent support for Server-Configuration with NEW_RELIC_IGNORE_SERVER_SIDE_CONFIG environment variable. The available value options are true and false. (#814 ) Fixes Fixes issue #36 : Total system memory will now be correctly reported on Linux. (#855 ) Fixes an issue in newrelic.config file schema validation that could block agent startup. (#835 ) Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.3.0.0-scriptable-installer.zip           | 1D00014EA12F91BB9069C2331D11BE6310D3F656CA0BB95B305622C84B954C7F |\n| newrelic-agent-win-x64-9.3.0.0.msi                            | B72E991B1ABCE9C4AF989A8BA7690D00A2B268CA33B0FB23520736B1AC5E02DC |\n| newrelic-agent-win-x64-9.3.0.0.zip                            | 3AC8557107BF7EBB8A5ADCA52E49BFB9CD67A6423D56926F5160D69D406CB1C0 |\n| newrelic-agent-win-x86-9.3.0.0.msi                            | 09E34A61205C4728D4A706CD2665FDA1AA113D15E68DF26C561B31BBEB9ADB51 |\n| newrelic-agent-win-x86-9.3.0.0.zip                            | 362AA522E498306695A5BB261DA82EDB289F49FC89CD0AAEF1BFB40E085ACC98 |\n| newrelic-netcore20-agent-9.3.0.0-1.x86_64.rpm                 | 53CEE9BDDC179B74CD29D026EAFF00E2C39D175CC5D761C67A9EDB8B931A51C0 |\n| newrelic-netcore20-agent-win-9.3.0.0-scriptable-installer.zip | 82560B0E07993E84F61DB7928D417C64482C1398400FD08324F54B815A8718B0 |\n| newrelic-netcore20-agent-win-x64-9.3.0.0.zip                  | 4ED3A63EA81E54AE9BAF3923B97409108A2F1D565FE481AFC0A65829E79C0515 |\n| newrelic-netcore20-agent-win-x86-9.3.0.0.zip                  | 88B55CE150A285A8DAC298A0455719C8178DDC7DAEFE627B9E7B75FDBB486EB9 |\n| newrelic-netcore20-agent_9.3.0.0_amd64.deb                    | 12FBC326D6E51C9855C29AA09EC350AAED9C65D72A78AF4DAFEAB89335768B75 |\n| newrelic-netcore20-agent_9.3.0.0_amd64.tar.gz                 | 62F5CA4DEC4CD37EE3C0F3B1262C060087F26FB9680915EBF78AAEC9764CA79D |\n| newrelic-netcore20-agent_9.3.0.0_arm64.deb                    | 125F596FBC125D6B72F0187E64E00906C272215C186DCE257ACFE7F4258A40DE |\n| newrelic-netcore20-agent_9.3.0.0_arm64.tar.gz                 | 6B0E13172255549536D1BA0694E0400EDBE4BF9336E43FA99CDEF008CFEB0306 | Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.22.181.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9300","eolDate":"2024-01-04"},{"agent":"dotnet","date":"2021-11-18","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.2.0.0","features":["Add support for .NET 6","Add instrumentation for Microsoft.Azure.Cosmos","Add additional Garbage Collection metrics"],"bugs":["Fix thread safety issue with HttpClient","Accurately report .NET Framework version in Environment data"],"security":[],"supportedOperatingSystems":null,"description":".NET 6 Compatibility As of version 9.2.0, the New Relic .NET Core agent supports .NET 6. New Features Adds automatic instrumentation for the Microsoft.Azure.Cosmos client library. (#811 ) Adds additional logging to the Garbage Collection performance metrics to aid in troubleshooting performance counter issues. (#792 ) Feature #800 : for .NET Framework apps instrumented with the .NET Framework agent, the value of the \".NET Version\" property in the Environment data page will more accurately reflect the version of .NET Framework in use. (#801 ) Fixes Fixes issue #803 : Thread safety issue in access to HTTP headers collection in HttpClient on .NET 6. (#804 ) Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.2.0.0-scriptable-installer.zip           | 672DBD066BAFF31C837B8FA3070FCD36DB3E9F68A3F830BBD93079CEE7DFA63F |\n| newrelic-agent-win-x64-9.2.0.0.msi                            | 30441A7FF8531F224FCC6C8377989873A8AA08854F28873F7B576AA6A51D92BD |\n| newrelic-agent-win-x64-9.2.0.0.zip                            | 739A0685B253F900868D81E11B15405D2FC030E850CD0B249AE0BED30CC0FC5E |\n| newrelic-agent-win-x86-9.2.0.0.msi                            | 053D569CF51C99554DEAE7DB8B01E731F9AB775A96EEB6A414D8A7A10B32FAE3 |\n| newrelic-agent-win-x86-9.2.0.0.zip                            | 7B06E2DFDF31654D387E51AC3EF974C0253F429914DB76550F1A33C388A08886 |\n| newrelic-netcore20-agent-9.2.0.0-1.x86_64.rpm                 | 684AA635EBFD7303FB9C205AC7B618D98CED3B04D35E95C34E4E40B87A55C9BA |\n| newrelic-netcore20-agent-win-9.2.0.0-scriptable-installer.zip | BE36D5DE8BABE92463CEA95FC446B4961FDFA4CC045885551841EFB662E46E04 |\n| newrelic-netcore20-agent-win-x64-9.2.0.0.zip                  | E44A7EE3C3FCEDF0F08F29FCE4C8D37B036E762896EC33FE4DF8B10C8FD4805A |\n| newrelic-netcore20-agent-win-x86-9.2.0.0.zip                  | 3ADD8938392613C35916923EBE1BB851CC25678F942B53CD0ECD1B59CFF585C6 |\n| newrelic-netcore20-agent_9.2.0.0_amd64.deb                    | 06051CDF373A0877A9545D9E499B44A2F024B3FF7192D205157030812D79701E |\n| newrelic-netcore20-agent_9.2.0.0_amd64.tar.gz                 | 2B1D66A71062CB78D1D710BFA9B6ED1E1B156123F2EDB080ED6E1A9BAA1680C6 |\n| newrelic-netcore20-agent_9.2.0.0_arm64.deb                    | EF173ECA83233F4FDFE2F91B996F5BE0E8C84AFCC3AC79BF1B3B786ADDE428AE |\n| newrelic-netcore20-agent_9.2.0.0_arm64.tar.gz                 | CDF5F89F827E1C6C5333369D930D8D5B7826698845E46671C8E6977B6D7DC2C8 | Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.22.181.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9200","eolDate":"2023-11-18"},{"agent":"dotnet","date":"2021-11-02","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.1.1.0","features":[],"bugs":["Reduce gRPC traffic on connection failure","Install correct gRPC binaries with MSI installer"],"security":[],"supportedOperatingSystems":null,"description":"Fixes Fixes issue #780 : Improves management of gRPC channels during connection failure scenarios. (#782 ) Fixes issue #781 : Windows MSI installer was not deploying gRPC libraries for netcore applications. (#788 ) Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.1.1.0-scriptable-installer.zip           | 4C63DCE0649253733D1F1AB9E820807DB834C1536A4182A7A74DDDD9AEB79B97 |\n| newrelic-agent-win-x64-9.1.1.0.msi                            | C4909EE7C46222AF74D1C427138C8F2C9A0EDA155519F68BDE4212D40B409CF2 |\n| newrelic-agent-win-x64-9.1.1.0.zip                            | E61DCB55F932236EFC64B7275409F14ECBDC0A02FE9F73FF650AA97C9602056F |\n| newrelic-agent-win-x86-9.1.1.0.msi                            | 62DFF5421A957C52F40F14A808CEAEA5166190740738A2874DEC34B241932817 |\n| newrelic-agent-win-x86-9.1.1.0.zip                            | B8F3ABD931DE37F73E04431098177665B8F6E3405F283006389C315120A4E3AE |\n| newrelic-netcore20-agent-9.1.1.0-1.x86_64.rpm                 | E4FD4A7A6F6CD2091087215A7F814154662985AB486E0D9C972E297811449BA4 |\n| newrelic-netcore20-agent-win-9.1.1.0-scriptable-installer.zip | EC44387D95EC1A7C8D568787381A96F91F6211861F47CDE1A5DF41EFE0128779 |\n| newrelic-netcore20-agent-win-x64-9.1.1.0.zip                  | C820A426B3652B76E898C3C0C489247DDD608BC4AE4A87F6CCCEE79C0CDEF350 |\n| newrelic-netcore20-agent-win-x86-9.1.1.0.zip                  | D138D2228ADB40C9DABE741B9A3E0B07BE58F9D8F8EC5FCB3B0FDCF5C9B75960 |\n| newrelic-netcore20-agent_9.1.1.0_amd64.deb                    | DAF7BC759950961AFE159BE9ADB81B793BFDB0D72B8DF6E506D0854EE701175A |\n| newrelic-netcore20-agent_9.1.1.0_amd64.tar.gz                 | 9D65FB744A9A30917D37BC0CECE508D805F0052153752C7D653E4B7D9D1EFB3C |\n| newrelic-netcore20-agent_9.1.1.0_arm64.deb                    | D7FC95719EA2C4E75EE369F7A4EC86230D05D79E2618A1D49286730C43577210 |\n| newrelic-netcore20-agent_9.1.1.0_arm64.tar.gz                 | 85C0DFFEB41BE78A9759B34B50891BED9CCE27747E04DD423527955EE7B5EB04 | Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.13.798.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9110","eolDate":"2023-11-02"},{"agent":"dotnet","date":"2021-10-26","downloadLink":"https://download.newrelic.com/dot_net_agent/previous_releases","version":"9.1.0.0","features":["Add support for Linux ARM64/AWS Graviton2"],"bugs":["Fix potential startup hang when using Microsoft.Configuration.ConfigurationBuilders"],"security":[],"supportedOperatingSystems":null,"description":"New Features Feature #365 : This version adds support for the Linux ARM64/AWS Graviton2 platform using .NET 5.0. (#768 ) Includes a new Processor Architecture property reported by the Agent with the Environment. Fixes Fixes issue #754 : Agent could cause applications that use configuration builders from Microsoft.Configuration.ConfigurationBuilders to hang on startup. (#753 ) Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.1.0.0-scriptable-installer.zip           | 5ECE58EBC15C4A4A8F9CA8094B557508EEE479FB68FB1D05F42805E511719711 |\n| newrelic-agent-win-x64-9.1.0.0.msi                            | 43AC720317253A7A2FEF1C42C4AAE174DEEB93F103E89AE344D85084F2F97127 |\n| newrelic-agent-win-x64-9.1.0.0.zip                            | 9BA011BFEBB72657BEA87187A9AEE23B7203A45DE4E5B367403AF14CFA627F58 |\n| newrelic-agent-win-x86-9.1.0.0.msi                            | 1E3B83503216113E5CBC1F97E382297331F3D0E13C7F65B44FDBD13C444B0F5D |\n| newrelic-agent-win-x86-9.1.0.0.zip                            | 44D250510A3C96CC252F30551061B0BF91657807B472A9E7C6C7FAD84B880163 |\n| newrelic-netcore20-agent-9.1.0.0-1.x86_64.rpm                 | 7B1F73EFBCE149FF6895BB8BB9A7192EEA0EF7E2D6FFF287EAFA41F08E35045B |\n| newrelic-netcore20-agent-win-9.1.0.0-scriptable-installer.zip | FBFB3253A844B9D8A0EA76F83C91D7319F4E6021624140935A5FA1B56163CDD0 |\n| newrelic-netcore20-agent-win-x64-9.1.0.0.zip                  | AEDCE4CB315D8ED9B93A8665776B696F823028770D34C2DCF96B63F8CEB97793 |\n| newrelic-netcore20-agent-win-x86-9.1.0.0.zip                  | 2E1913C6B00A16EDF2DC6D8E45522D9258D10DEBDBEC61C52931593A199DFE06 |\n| newrelic-netcore20-agent_9.1.0.0_amd64.deb                    | 3A27EBAD2F1FDEDCDB054395A061B3AEF1473EECB9BCECDAF18E404BAACEE502 |\n| newrelic-netcore20-agent_9.1.0.0_amd64.tar.gz                 | 4F9C7E379DBB466788B442F8FA23BB303F6E5213C2F5BD66A86FBCFB9AC88889 |\n| newrelic-netcore20-agent_9.1.0.0_arm64.deb                    | C428D7FCEB252CD5DA801FBB64E4CC831A69DA1DE84DE9C5ED8D667D1B55BBE2 |\n| newrelic-netcore20-agent_9.1.0.0_arm64.tar.gz                 | 86F1FC2AC5EE3FE045B8956A246D9C7D3A1B953D444C961C23BB454DD672E55D | Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.13.798.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9100","eolDate":"2023-10-26"},{"agent":"dotnet","date":"2021-09-16","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"9.0.0.0","features":["Enable Distributed Tracing by default","Allow configuration of number of span event samples","Allow setting log level and directory by environment variable","Deprecate Cross Application Tracing, support for Castle.Monorail, and some Agent APIs"],"bugs":["Fix missing SQL Explain Plans","Fix serialization error with some custom attributes","Reduce install size"],"security":[],"supportedOperatingSystems":null,"description":"New Features Feature #672 : This release of the .NET agent enables distributed tracing by default, and deprecates cross application tracing. (#700 ) Feature #671 : The maximum number of samples stored for span events can be configured via the spanEvents.maximumSamplesStored configuration in the newrelic.config or the NEW_RELIC_SPAN_EVENTS_MAX_SAMPLES_STORED environment variable.(#701 ) Feature #703 : Increases the default maximum number of samples stored for span events from 1000 to 2000.(#705 ) Feature #532 : Adds environment variables for log level NEWRELIC_LOG_LEVEL and directory NEWRELIC_LOG_DIRECTORY to allow better control of logs for the agent and the profiler. (#717 ) Fixes Fixes issue #707 : In 8.40.1 SQL explain plans are not being captured for parameterized SQL statements. (#708 ) Fixes issue #502 : Agent encountering serialization error (#715 ) Fixes issue #679 : Update gRPC libraries from 2.35.0 to 2.40.0 to reduce installation size (#721 ) Deprecations/Removed Features Cross application tracing is now deprecated, and disabled by default. To continue using it, enable it with crossApplicationTracer.enabled = true and distributedTracing.enabled = false. Issue #667 , 668 , #669 : previously deprecated agent configuration options are now disabled.  See the migration guide  for details. Issue #666 : previously deprecated agent APIs have been removed, and disabled in the Agent. Disabled APIs will log a warning when invoked by old versions of the .NET agent API. See the migration guide  for details. (#687 ) Issue #702  Deprecate instrumentation for Castle.Monorail (#710 ) Checksums | File                                                          | SHA - 256  Hash                                                  |\n| ------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-9.0.0.0-scriptable-installer.zip           | 44D43682A42ABE2736CCACFC1F762155898DFC3E692091D351F12389A88B8A46 |\n| newrelic-agent-win-x64-9.0.0.0.msi                            | 161EC6128E104F87D4800ED6D311B3D918BDE678AEC9B599ED7A247327ED971B |\n| newrelic-agent-win-x64-9.0.0.0.zip                            | 810FEAA211079B40D4E3313BFEE347EA3F947BF278CFA4AC8C55CA0685830CF8 |\n| newrelic-agent-win-x86-9.0.0.0.msi                            | F2C1F758F47734B4959F7109C8FECD2FB2D18CC2A94661D4BDE75F092EDDBF77 |\n| newrelic-agent-win-x86-9.0.0.0.zip                            | 017C05C9C86CB5DA1A072C546B44619665A90130813E37C5E9EFF256ED10193D |\n| newrelic-netcore20-agent-9.0.0.0-1.x86_64.rpm                 | 678D19758034E93BD4F9DA3CB3407BDC9405F9CD91C69C62DE20C6D38B59B81C |\n| newrelic-netcore20-agent-win-9.0.0.0-scriptable-installer.zip | C8536759FFA847805484790D87A34A1506042B037F691A2619F67EAFB219D398 |\n| newrelic-netcore20-agent-win-x64-9.0.0.0.zip                  | 5A0609465319C57AEE37C0C5F7686062E0B0A694488A2DEAB0563651C6E6011C |\n| newrelic-netcore20-agent-win-x86-9.0.0.0.zip                  | 21CA7F79E83562430CBFDC8653D8527915E5CA2B8F804D53154299A9ACAD5803 |\n| newrelic-netcore20-agent_9.0.0.0_amd64.deb                    | 1A8F05C857223F075F6442B8332FB35BEA7892C3B50B01C4B8A9472E05E4FC08 |\n| newrelic-netcore20-agent_9.0.0.0_amd64.tar.gz                 | C5C6E12199F029B7D0DEB23F27D1D4FAC413284D446CEA29200FE1F1500AEFD3 | Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.13.798.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-9000","eolDate":"2023-09-16"},{"agent":"dotnet","date":"2018-11-15","downloadLink":null,"version":"8.9.130.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Added auto instrumentation to prevent associating Serilog PeriodicBatchingSink activity with an application’s transactions. New Features Added API support  for manually creating and accepting distributed tracing payloads. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-891300","eolDate":"2021-11-15"},{"agent":"dotnet","date":"2018-10-18","downloadLink":null,"version":"8.8.83.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes potential memory leak when Distributed Tracing is enabled. Fixes an issue where a NullReferenceException is logged for certain data stores (MongoDB and Couchbase) when distributed tracing is enabled. Fixes an issue where a transaction start time is incorrect when an error has been reported. Other Information After November 7th, 2018 the Core_20 directory will be removed from the download site. This folder currently contains an outdated version of the .Net Core agent. The most up-to-date version of the .NET Core agent can be found in inlatest_release directory. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-88830","eolDate":"2021-10-18"},{"agent":"dotnet","date":"2018-10-03","downloadLink":null,"version":"8.7.75.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Users can now set a customized host name to be displayed in the APM UI via the newrelic.config file or an environment variable. For more information, visit https://docs.newrelic.com/docs/agents/net-agent/configuration/net-agent-... [.NET Framework]  Added the ability to enable the agent from the local newrelic.config file for all non-IIS hosted .NET Framework applications. Additional information can be found at: https://docs.newrelic.com/docs/agents/net-agent/additional-installation/... Fixes The profiler now honors the log level configuration setting that is set in the app-local newrelic.config file. Other Information After November 7th, 2018 the Core_20 directory will be removed from the download site. This folder currently contains an outdated version of the .Net Core agent. The most up-to-date version of the .NET Core agent can be found in inlatest_release directory. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8775","eolDate":"2021-10-03"},{"agent":"dotnet","date":"2018-08-28","downloadLink":null,"version":"8.6.45.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Download URLs Download the appropriate release for your New Relic .NET agent: https://download.newrelic.com/dot_net_agent/latest_release New Features Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before. Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide  before you enable this feature. To enable distributed tracing, see .NET Agent configuration . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-86450","eolDate":"2021-08-28"},{"agent":"dotnet","date":"2018-08-16","downloadLink":null,"version":"8.5.186.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Adds support for capturing request.uri attribute for WCF services when available. [.NET Core]  SQL query parameter values can now be captured on Slow SQL Traces on Linux. Fixes Fixes an issue where errors set to be ignored through configuration were not being ignored. Fixes an issue where running the thread profiler can cause an application to terminate. Fixes an issue where transaction events could be dropped. [.NET Core]  Fixes an issue for .NET Core applications running on Linux when serializing slow SQL trace and explain plan data for transmission to New Relic. Previously, the following exception would be seen in the agent logs: NewRelic ERROR: System.PlatformNotSupportedException: Operation is not supported on this platform. Notes We will be removing the core_20 directory from the download site the week of September 3rd, 2018 as it contains a deprecated version of the .Net Core agent. Please be sure to update any of your scripts that reference this location accordingly. All downloads for the current version of the agent can be found in the latest_release directory on the download site. Historical versions can be found in the previous_releases directory. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-851860","eolDate":"2021-08-16"},{"agent":"dotnet","date":"2018-07-30","downloadLink":null,"version":"8.4.880.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Download URLs Download the appropriate release for your New Relic .NET agent: https://download.newrelic.com/dot_net_agent/previous_releases New Features SQL query parameter values can now be captured on Slow SQL Traces. This feature can be enabled with the new configuration option datastoreTracer.queryParameters. The transactionTracer.record_sql configuration option must also be set to raw. See documentation here . This feature should be used with caution as it can lead to the capture of sensitive data. High-security mode prevents the use of this feature. Windows support only. Linux support coming soon. [.NET Framework]  Adds support for tracking async transactions when .ConfigureAwait(false) is used from async controller actions in ASP.NET MVC applications. [.NET Core]  Adds support for .NET Core 2.1. Support for .NET Core 2.1 requires at least CLR version 2.1.3 and tiered compilation must not be enabled. Fixes [.NET Core]  Fixes issue where status code based errors would be reported instead of the actual noticed Exception. This most commonly occurred with errors noticed in the ExceptionHandlerMiddleware (app.UseExceptionHandler(...)). Fixes an issue where only the first request parameter is captured when request.parameters.* attributes are added to an include list. Notes We will be removing the core_20 directory from the download site the week of September 3rd, 2018 as it contains a deprecated version of the .Net Core agent. Please be sure to update any of your scripts that reference this location accordingly. All downloads for the current version of the agent can be found in the latest_release directory on the download site. Historical versions can be found in the previous_releases directory. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-848800","eolDate":"2021-07-30"},{"agent":"dotnet","date":"2021-08-25","downloadLink":null,"version":"8.41.1.0","features":[],"bugs":["Fix gRPC error on disconnect","Allow setting stack trace depth to 0 to disable"],"security":[],"supportedOperatingSystems":null,"description":"Fixes Fixes issue #627 : Grpc channel shutdown can cause license_key is required error message. (#663 ) Fixes issue #683 : Requested stack trace depth is not always honored. (#684 ) Checksums | File                                                           | SHA - 256  Hash                                                  |\n| -------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-8.41.1.0-scriptable-installer.zip           | F00B39B7FACDFDFF1733A981C5C67BD8F4D4E31F2D6F0B4AC0B9C227153CE758 |\n| newrelic-agent-win-x64-8.41.1.0.msi                            | 3E84FD91E82DFC31D473F8E300E4F0C2EF2D9DEB7CC0D719E9026F0879E8E53E |\n| newrelic-agent-win-x64-8.41.1.0.zip                            | 12DACF0FD6B393D15575CAA7D141C1D1CBC7B779BAF4ED46AA8B68679A16E491 |\n| newrelic-agent-win-x86-8.41.1.0.msi                            | A6C6BFAB2EA66C12811C3F7071B9836C1BDC52852FB7ACA7905D389285765533 |\n| newrelic-agent-win-x86-8.41.1.0.zip                            | 97DB8475E6009E90BD607441541E2C8CDF129CC8B4266E351DE5B4E47BC39B7C |\n| newrelic-netcore20-agent-8.41.1.0-1.x86_64.rpm                 | 02FDF5CDA21BD336E1282DD49D68CA271F0BF0348AE529E8AD298C188ABA5430 |\n| newrelic-netcore20-agent-win-8.41.1.0-scriptable-installer.zip | 4952EA5639BCB0ECA697FFE815368C09FB9CA4ACAA61605D62E53D2EF3FBC477 |\n| newrelic-netcore20-agent-win-x64-8.41.1.0.zip                  | 89060852EC52AB6208F899FEA35C633E6A79DF63CA86A34500AD4F2FD3167E62 |\n| newrelic-netcore20-agent-win-x86-8.41.1.0.zip                  | 9CAE189730FBA5B0B7F44E6EA8F760711F3AAB4742E8BB72D8764CDE8F0C9153 |\n| newrelic-netcore20-agent_8.41.1.0_amd64.deb                    | 470DF5E9E5A3BC2B286F05B126DD31DDAB886E661C0621D1E3F2F74C2ABEE01B |\n| newrelic-netcore20-agent_8.41.1.0_amd64.tar.gz                 | 6021E09E17A6A28F52769C0F4803AA6A35A8DE5825B85FF4876B1748EF14EBCA | Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET Agent 8.13.798.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-84110","eolDate":"2023-08-25"},{"agent":"dotnet","date":"2021-07-21","downloadLink":null,"version":"8.41.0.0","features":["Capture HTTP request method on transactions","Capture stack traces in Transaction Traces","Report name configuration in Environment data"],"bugs":["No longer delete user headers from RabbitMQ messages"],"security":[],"supportedOperatingSystems":null,"description":"New Features Feature #611 : Capture HTTP request method on transactions in the AspNetCore, Asp35, Wcf3, and Owin wrappers. Feature #580 : Send initial app name and source in environment data. (#653 ) Adds support for capturing stack traces for each instrumented method in a Transaction Trace. This feature is disabled by default. You can enable the capture of stack traces by setting either maxStackTrace to any value greater than 1.  This value will only be used to determine if stack traces are captured or not despite the name. The following are the default settings for stack traces. These can be changed using the newrelic.config: A maximum 80 stack frames are reported per stack trace. Fixes Fixes issue #639 : RabbitMQ instrumentation can delete user headers from messages. Thank you @witoldsz for finding and reporting this bug. (#648 ) Checksums | File                                                           | SHA - 256  Hash                                                  |\n| -------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-8.41.0.0-scriptable-installer.zip           | 1D52B36A3975C5CA2A203AD68D5817ECB3A83CF0600B1ECD7869659964532600 |\n| newrelic-agent-win-x64-8.41.0.0.msi                            | 2E21966D5E10C5B788B2F2C5B518D2199E5B0D66EEBDF4D0E7B2191726A310BB |\n| newrelic-agent-win-x64-8.41.0.0.zip                            | 2A7B5D96BF5F501640497769BA2ACCD1CB43F85AEFBBEA20B2932E3D58377CF5 |\n| newrelic-agent-win-x86-8.41.0.0.msi                            | 954A364C0C47B2935CA3AF6E3F9441A4F6333D480AC2D97444EBF16ECBC60C13 |\n| newrelic-agent-win-x86-8.41.0.0.zip                            | 55ECB00F775056C814FA9B6F57F2CA0F2C42522AC09E5E58D87172F0D6B9D633 |\n| newrelic-netcore20-agent-8.41.0.0-1.x86_64.rpm                 | DE5C792C8412153F6B5594ED1601BFB078190750B28772D11A646D09AF28C42B |\n| newrelic-netcore20-agent-win-8.41.0.0-scriptable-installer.zip | 6EEF6BDA67C6E9AE173C8E8D58DF78F18E459966C5AB6C213024371D0F18BDC4 |\n| newrelic-netcore20-agent-win-x64-8.41.0.0.zip                  | F75913CC26973EF81742D65D6AB489DF1E7D2019B009D2E82754DBC3B1BA0A9E |\n| newrelic-netcore20-agent-win-x86-8.41.0.0.zip                  | 29742D9528FF1D2C718C741B4A6C15D6EAD56618C488F5685A1FE64CA22CEFA3 |\n| newrelic-netcore20-agent_8.41.0.0_amd64.deb                    | B7A5B1F98C58B468770FE2EDFC0F51C9081851B9EA0C5CA0B56B02E1120F38C3 |\n| newrelic-netcore20-agent_8.41.0.0_amd64.tar.gz                 | 2958DEF3988093F81866F29F8B5584D2A29CD5F6B385901534541EF023AD2992 | Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET Agent 8.13.798.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-84100","eolDate":"2023-07-21"},{"agent":"dotnet","date":"2021-07-08","downloadLink":null,"version":"8.40.1.0","features":[],"bugs":["Fix missing data when using Infinite Tracing and SendDataOnExit","No longer record a transaction for invalid MVC actions","Correct transaction name around attribute-based routing","Correctly handle OPTIONS requests","Report missing external calls in WCF services","Ignore Kudu on Linux Azure","Fix startup failure due to invalid config file","Always report thread ID in Agent log","Fix failures in creating SQL Explain Plans"],"security":[],"supportedOperatingSystems":null,"description":"Fixes Fixes issue #485 : SendDataOnExit configuration setting will prevent Infinite Traces data sending interuption on application exit. (#550 ) Fixes issue #155 : MVC invalid Action for valid Controller can cause MGI. (#608 ) Fixes issue #186 : Attribute based Routing (ex WebAPI) can cause transaction naming issues. (#612 ) Fixes issue #463 : Handle OPTIONS requests for asp.net applications. (#612 ) Fixes issue #551 : Missing external calls in WCF Service. (#610 ) Fixes issue #616 : Linux Kudu not accessible when .NET agent presents. (#618 ) Fixes issue #266 : Agent fails to initialize and provides no logs when configured with capitalized booleans. (#617 ) Explain plans will be created if transactionTracer.explainEnabled  is true and one or both transactionTracer.enabled  or slowSql.enabled  are true.  If transactionTracer.explainEnabled is false or both transactionTracer.enabled and slowSql.enabled are false, no Explain Plans will be created. Fixes issue #600 : Thread id will now be used in agent logging, even if a thread name has been set. (#626 ) Fixes issue #476 : When generating and explain plan MS SQL parsing is matching parts of words instead of whole words Fixes issue #477 : SQL Explain plans MS SQL parser needs to be able to ToString an object to work with parameterized queries Improves handling serializable types like DateTimeOffset The presence DbTypes Binary and Object will prevent an Explain Plan from being executed.  In order to execute an explain plan, the agent must replace any parameters in a query with the real values.  Binary and Object are too complex to properly serialize without introducing errors. Checksums | File                                                           | SHA - 256  Hash                                                  |\n| -------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-8.40.1.0-scriptable-installer.zip           | DA01B071EE654006A811BEF4A63780C0C1A5AE94D6B7315C26D8CBC1BA6C81EB |\n| newrelic-agent-win-x64-8.40.1.0.msi                            | DBB3E7DD895BC6B9412FD748E0DC8A4C42C54FEDDAE46759F0A813911562EE15 |\n| newrelic-agent-win-x64-8.40.1.0.zip                            | 55E29C0291E0BCE8EEF0F04252972EDA9614D9C199D4ECDF04D8D8D235C1C441 |\n| newrelic-agent-win-x86-8.40.1.0.msi                            | 08F3C3EEFE6AFEFAB82C2C030E3DDC62E6A7AA5CAB8D99F25F399D6894BED653 |\n| newrelic-agent-win-x86-8.40.1.0.zip                            | 66EB3609CE1AC145F1AC9DB7B7EF0B4F83F1A975D86AD7067A3E51A30FD7FF51 |\n| newrelic-netcore20-agent-8.40.1.0-1.x86_64.rpm                 | E165609FE8F1063221786AB0D19D76122CC735DB4162D9C9CB1FAB779FD38806 |\n| newrelic-netcore20-agent-win-8.40.1.0-scriptable-installer.zip | 75DDDEAD573336DB586668C892AC7B9E5FBF56ED6595C9FF4090DB9FF129AA23 |\n| newrelic-netcore20-agent-win-x64-8.40.1.0.zip                  | 0252C16007C18219A1EFDB7E2F8C2DE178D0A94A58F58EABEC4F376762829B4A |\n| newrelic-netcore20-agent-win-x86-8.40.1.0.zip                  | 31CBE34CBB8E62AE3E87319E026E1B14AFCBB234CF7FD48971F1C7A5B8050FC3 |\n| newrelic-netcore20-agent_8.40.1.0_amd64.deb                    | F84646E7A606918FF2C6189EFA9269922F0F1297F3B5581BC795F905D79B7400 |\n| newrelic-netcore20-agent_8.40.1.0_amd64.tar.gz                 | 9C4B853A748F508DF6FECDB3BE3E963C6ECA89C6D3ACFACD90C1D4D1A89BAFFB | Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET Agent 8.13.798.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-84010","eolDate":"2023-07-08"},{"agent":"dotnet","date":"2021-06-08","downloadLink":null,"version":"8.40.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Adds Agent support for capturing HTTP Request Headers. Support included for ASP.NET 4.x, ASP.NET Core, Owin, and WCF instrumentation. (#558 , #559 , #560 , #561 ) To enable this feature, the new allowAllHeaders configuration setting must be set to true. For more information about this new configuration, visit the agent configuration page . Fixes Fixes issue #264 : Negative GC count metrics will now be clamped to 0, and a log message will be written to note the correction. This should resolve an issue where the GCSampler was encountering negative values and crashing. (#550 ) Fixes issue #584 : When the agent is configured to log to the console, the configured logging level from newrelic.config will be respected. (#587 ) Checksums File SHA - 256 Hash newrelic-agent-win-8.40.0.0-scriptable-installer.zip 1C752F5BAF8B1A13F0276BDE70522E08B92D34215A556C45AC8AF4AABBE0B87A newrelic-agent-win-x64-8.40.0.0.msi 68A5C3C9CA6B8F35DD3F4FA4B97B7560CFADAE3D25790C33245CA69AF92F0BD0 newrelic-agent-win-x64-8.40.0.0.zip 93F1FE590F8D74483110250BBD94B7967BFADDB4C79241E9725B4FDEE8A85F6B newrelic-agent-win-x86-8.40.0.0.msi 50E1C40F68CA7058D4491D994D3BCC31FF5EFB32C2EBB2F4E3EE9B391900CEEF newrelic-agent-win-x86-8.40.0.0.zip 543C1473C7FE73B470B99A749A0E48B887116B82AAE784C0A195B5A88175AB1D newrelic-netcore20-agent-8.40.0.0-1.x86_64.rpm FCE857338C2ED7E740AEA6A57B506567AF8255C804CFDCD78BF4F6392B228893 newrelic-netcore20-agent-win-8.40.0.0-scriptable-installer.zip 3E12577B34CF8DE4E118D191B2C0EAA948AFC9AF15CEA4983A9C4AE5DBC74DA7 newrelic-netcore20-agent-win-x64-8.40.0.0.zip 34038A364C6B213F5CFD13D7785F925F244460DE995F02309CEA370F1A5E3BC4 newrelic-netcore20-agent-win-x86-8.40.0.0.zip B52A6AAB8F24F2ECEAAD0589AE7A2B1CD71E28790627908B3DF9DE671C0D5E70 newrelic-netcore20-agent_8.40.0.0_amd64.deb 59188974CFECB5C7F8CB291D4669C48B7AA3FB936C3AF456EB1387D3CE99A4FA newrelic-netcore20-agent_8.40.0.0_amd64.tar.gz CF99691E1E6DF2B0ABDFB6C8740FBDC5FBA557BC248447E33D87214D167D217B Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET Agent 8.13.798.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-84000","eolDate":"2023-06-08"},{"agent":"dotnet","date":"2021-04-14","downloadLink":null,"version":"8.39.2.0","features":[],"bugs":["Always include Error attribute even if no errors","Fix setting to disable stack traces"],"security":[],"supportedOperatingSystems":null,"description":"Fixes Fixes issue #500 : For transactions without errors, the agent should still create the error intrinsics attribute with its value set to false. (#501 ) Fixes issue #522 : When the maxStackTraceLines config value is set to 0, the agent should not send any stack trace data in the error_data payload. (#523 ) Checksums | File                                                           | SHA - 256  Hash                                                  |\n| -------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-8.39.2.0-scriptable-installer.zip           | 3A40D307EFC6B7E311EAC01E143AC04CAAD122E3B37A2FF9A34FF5FE7E104176 |\n| newrelic-agent-win-x64-8.39.2.0.msi                            | 061AD90F758C85B85F734A20F73C0A17388C3B5529428A132B545759DE214D25 |\n| newrelic-agent-win-x64-8.39.2.0.zip                            | 18F8EB0A5F0068F3FD972C406562173061FB4939C6F6CC46887804BF1CDF6331 |\n| newrelic-agent-win-x86-8.39.2.0.msi                            | 0438DFBBB2882B0CFA9DF77B11F2065C98C03903D460786A439CCC5CFD087660 |\n| newrelic-agent-win-x86-8.39.2.0.zip                            | C20B69EAFBAC4FFDD4D2C3CFCB4C48490E4E2A933D477E470705698763FCADEF |\n| newrelic-netcore20-agent-8.39.2.0-1.x86_64.rpm                 | E5E3A558978595A1CAE7FF0561F058C6EDA4C2DE50AEDFBF60AF2643EC251B82 |\n| newrelic-netcore20-agent-win-8.39.2.0-scriptable-installer.zip | 19BE94827F4F03C3E5FF8E31F47E1E0EE754F1C43E51AFD22536BB3D848934F0 |\n| newrelic-netcore20-agent-win-x64-8.39.2.0.zip                  | D733D30C71A31AB779B809C52BB86289752E7A264B57D1BC1975DAFA95311803 |\n| newrelic-netcore20-agent-win-x86-8.39.2.0.zip                  | 6539290914C3F345C7472C46C3AF0D39741D0616D3E200E51C335C05EF6FE538 |\n| newrelic-netcore20-agent_8.39.2.0_amd64.deb                    | 4631FBB64A88F04653AC1BEAEDE32BA22666F6CA3866FA1291292B2C6342C1AE |\n| newrelic-netcore20-agent_8.39.2.0_amd64.tar.gz                 | 1AD2B907420484064FB49D4F540423287B43A3B90E97C9DD0FFE51FDB142D233 | Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET Agent 8.14.222.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-83902","eolDate":"2023-04-14"},{"agent":"dotnet","date":"2021-03-17","downloadLink":null,"version":"8.39.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes issue #22 : Agent causes exception when distributed tracing is enabled in ASP.NET Core applications that use the RequestLocalization middleware in a Linux environment. (#493 ) Fixes issue #267 : On Linux, the profiler fails to parse config files that start with a UTF-8 byte-order-mark (BOM). (#492 ) Fixes issue #464 : Distributed tracing over RabbitMQ does not work with RabbitMQ.Client versions 6.x+ (#466 ) Fixes issue #169 : Profiler should be able to match method parameters from XML that contain a space. (#461 ) Checksums | File                                                           | SHA - 256  Hash                                                  |\n| -------------------------------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-agent-win-8.39.1.0-scriptable-installer.zip           | 0F027A061D2C1B26D3883EEB8C02BA35D202EA3FA4DDE302CC4D3B4357669183 |\n| newrelic-agent-win-x64-8.39.1.0.msi                            | 9C1015503869C46CE98086AE4065C356E1457FB4F37FE89A8A17B2B2D2543949 |\n| newrelic-agent-win-x64-8.39.1.0.zip                            | 483A43F2520431F88EC9A3DA7DB4B355B59CE662B45943E5E88B00814641ED2E |\n| newrelic-agent-win-x86-8.39.1.0.msi                            | 76E65F8FB8F9F104CA70B869D3D483824DAE6098AB44D8408B863838000DB538 |\n| newrelic-agent-win-x86-8.39.1.0.zip                            | 7B3A2E853484EACECE81C2CB0E47CBA3F6CDE0E77D4A706DC89DAE4112456E93 |\n| newrelic-netcore20-agent-8.39.1.0-1.x86_64.rpm                 | 82CDA137B03578A944E2D6FB2372380EF3E89615EAB7752A68ABB5D6529CB19C |\n| newrelic-netcore20-agent-win-8.39.1.0-scriptable-installer.zip | E1DED942CAC48E2AA50A979410CB386696B4A0B1A0FCB1001E35D6EA4F444F05 |\n| newrelic-netcore20-agent-win-x64-8.39.1.0.zip                  | FC5C031BCBC2AE4167F15DDF34467F510CEB990CAF1841E3FA13A1082FE67769 |\n| newrelic-netcore20-agent-win-x86-8.39.1.0.zip                  | 73079032BFFADCAD0F7678516E5AF03F75DDB37E5E9F08AD51CC306EECD28F42 |\n| newrelic-netcore20-agent_8.39.1.0_amd64.deb                    | B18497FE20DC9ED1BC8F81715FD3BD3AEFB70459B5654BF23A5FA359A131A8D7 |\n| newrelic-netcore20-agent_8.39.1.0_amd64.tar.gz                 | 78154716CAD11D0D4D380C59746E24B2D0F3A120E885E382A9C0CBCDD4533A3D | Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET Agent 8.14.222.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-83901","eolDate":"2023-03-17"},{"agent":"dotnet","date":"2021-02-10","downloadLink":null,"version":"8.39.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Add GetBrowserTimingHeader(string nonce) overload. This allows sites with a Content-Security-Policy that disables 'unsafe-inline' to emit the inline script with a nonce. Fixes Fixes Issue #394 : agent fails to enable infinite tracing in net5.0 docker images. Checksums File SHA - 256 Hash newrelic-agent-win-8.39.0.0-scriptable-installer.zip 80B8139E8E6D98CF5853480FEC43AAA488C128F80ACBF8C3EBC6A7A88642E423 newrelic-agent-win-x64-8.39.0.0.msi C6E4EF3E1071FD7EFBAA987CB16027AD348FCE6B4318BC8E95285F9A8FA304F0 newrelic-agent-win-x64-8.39.0.0.zip B12D7C2A08D7456F063283BE4FC696038404EE31AAF1012B8174568352B5CFE3 newrelic-agent-win-x86-8.39.0.0.msi 2465B0B2C3A7A1CA39CED12FA09D8CFE6283C90763FC2DF872B93BFB8C65E050 newrelic-agent-win-x86-8.39.0.0.zip AE27ADCA535353AF6DDD0E00BF826C4B8859A1DA69AD66512043AB6518929C28 newrelic-netcore20-agent-8.39.0.0-1.x86_64.rpm DA037A3E80E60B420F4D9093B34DE7B5F08C10C5711890B1462B73ABE39CE9B8 newrelic-netcore20-agent-win-8.39.0.0-scriptable-installer.zip DCDF1644F5FEF68CE0D809F32A2170C1D52948DE8F7AC631BA10AD59A775EB83 newrelic-netcore20-agent-win-x64-8.39.0.0.zip CAC8011D7F2887437D080D491CF5462BBE8F1786208A81CE9CDF09E551B7A5B8 newrelic-netcore20-agent-win-x86-8.39.0.0.zip 508A88E804692565301BBBD01BB12E502D1DDEF110655C4CA0FCE077C6F75074 newrelic-netcore20-agent_8.39.0.0_amd64.deb 12044EAB563822EB47B06F157F22DE9E593CD167201DF70A1159903C457BC019 newrelic-netcore20-agent_8.39.0.0_amd64.tar.gz 1FDEBB0262981C7088E8A46AEE467A254ED175F4FB6620611D9DA78B2E1E7AF8 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET Agent 8.13.798.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-83900","eolDate":"2023-02-10"},{"agent":"dotnet","date":"2021-01-26","downloadLink":null,"version":"8.38.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Improvements to New Relic Edge (Infinite Tracing) The agent will now handle having its infinite tracing traffic moved from one backend host to another without losing data or requiring an agent restart. Improved logging of infinite tracing connections. Checksums File SHA-256 Hash newrelic-agent-win-8.38.0.0-scriptable-installer.zip 978339DA2D43E2412BD832F5EB8F69DFF2FE226E70D1106F76AB41DE3B5B7C60 newrelic-agent-win-x64-8.38.0.0.msi 7D4BF6A5D4BAB5D58051810FD7701449A57F72CE9331477900BB82FFDB97FECD newrelic-agent-win-x64-8.38.0.0.zip E3E6854495D306537F557D7B62E238E6143754FF36C0B564CA436E8294C210A6 newrelic-agent-win-x86-8.38.0.0.msi 87A77E5ACDB21B6ACA8E5A924DF01FC1FD49A6F8773565BB96983AA98F123DF3 newrelic-agent-win-x86-8.38.0.0.zip BEC5713B7E71DE09384CEE7C48C44C8570FB008E2F4707EAE7E6CC1610322A87 newrelic-netcore20-agent-8.38.0.0-1.x86_64.rpm 93A05ACED53F2F3C140B1C5212A699CD41DEAC65BB3D01BC5B47685A814A18EF newrelic-netcore20-agent-win-8.38.0.0-scriptable-installer.zip 6614C3A1474114851FBC81484693C3252EA575EA4839F511CE82D92CE8126043 newrelic-netcore20-agent-win-x64-8.38.0.0.zip 5206FB7E63746F821C3ED1600943B600C15B6DCDAD68ECFB9A3AF337E2E51AE7 newrelic-netcore20-agent-win-x86-8.38.0.0.zip 186EF11710CB01A366B02CCB5BE1809AAEDB5FD1B990FFD84A1E1083E422613A newrelic-netcore20-agent_8.38.0.0_amd64.deb F817E4BD28EEDE0F3DD887E717582E50D7B879B4DE7919037E62DBF966DD6284 newrelic-netcore20-agent_8.38.0.0_amd64.tar.gz 4A329C7E8DF1D144BD8812314B065D294EA02ADC1E2B2326528B121D59D00E21 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET Agent 8.13.798.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-83800","eolDate":"2023-01-26"},{"agent":"dotnet","date":"2021-01-04","downloadLink":null,"version":"8.37.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Updated support for RabbitMQ Adds support for .NET Core applications using RabbitMQ.Client. Adds support for RabbitMQ.Client version 6.2.1. Not supported: Distributed Tracing is not supported with the RabbitMQ AMQP 1.0 plugin. Adds configuration  Environment Variables Adds MAX_TRANSACTION_SAMPLES_STORE - the maximum number of samples stored for Transaction Events. Adds MAX_EVENT_SAMPLES_STORED - the maximum number of samples stored for Custom Events. Adds NEW_RELIC_LOG - the unqualifed name for the Agent's log file. Checksums File SHA-256 Hash newrelic-agent-win-8.37.0.0-scriptable-installer.zip 27FA806F7DC9EF4067F58CE721AE3D4F2DA9203413B383717293C1028E1BE6D0 newrelic-agent-win-x64-8.37.0.0.msi 0AEC1EF00E2D607310A1A9266B237F7D892EE738624C6E1C6BB0E18B3AE54657 newrelic-agent-win-x64-8.37.0.0.zip 0F86B501344B444EE3E79548C58A4DD03ACB7A93605BC2B6EE6C61C9A581E4B6 newrelic-agent-win-x86-8.37.0.0.msi 8AE3F89D122FB92838763205E07EA2A672A583599D892721439985126DACDE0B newrelic-agent-win-x86-8.37.0.0.zip 618B4220FFDA15B39D1B666EE06E91D86875D3572A5C8541C71F7975AAE931C2 newrelic-netcore20-agent-8.37.0.0-1.x86_64.rpm 3DA7EAA99CB44A57486D3058F5CAD6DC17D9CBD0BEC31C839C0A4EDC12D5408E newrelic-netcore20-agent-win-8.37.0.0-scriptable-installer.zip 26ED55C8E848F762CEF743C059E704C7147052A9E6DB173CBD7427A1654A45C5 newrelic-netcore20-agent-win-x64-8.37.0.0.zip E5D80B8B0A90017A0A0B5C9556120BB728450BE11793F9209B6BEF082B1C1F2D newrelic-netcore20-agent-win-x86-8.37.0.0.zip DABD3E9712EBD8D3AAF8ACF6A723AE7ED65B8ECFA74B25DB0FA31799227130FE newrelic-netcore20-agent_8.37.0.0_amd64.deb 41C4725E82D0E317EC3B0F43870D219EDECF33A7DD94CF7F5C1EA5769C5E09F4 newrelic-netcore20-agent_8.37.0.0_amd64.tar.gz 0ED5C95EB19996BF329E14D8547C3447C8CE8692DBD2C119B2C518BAF24382D3 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET Agent 8.12.216.0 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-83700","eolDate":"2023-01-04"},{"agent":"dotnet","date":"2020-12-08","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"8.36.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Download URLs Download the appropriate release for your New Relic .NET agent: https://download.newrelic.com/dot_net_agent/latest_release Fixes Fixes Issue #224  where leading \"SET\" commands will be ignored when parsing compound SQL statements. (#370 ) Fixes Issue #226  where the profiler ignores drive letter in HOME_EXPANDED when detecting running in Azure Web Apps. (#373 ) Fixes Issue #93 : when the parent methods are blocked by their asynchronous child methods, the agent deducts the child methods' duration from the parent methods' exclusive duration.(#374 ) Fixes Issue #9  where the agent failed to read settings from appsettings.{environment}.json files. (#372 ) Fixes Issue #116  where the agent failed to read settings from appsettings.json in certain hosting scenarios. (#375 ) Fixes Issue #234  by reducing the likelihood of a Fatal CLR Error. (#376 ) Fixes Issue #377  when using the AddCustomAttribute API with Microsoft.Extensions.Primitives.StringValues type causes unsupported type exception. (378 ) Checksums File SHA-256 Hash newrelic-agent-win-8.36.0.0-scriptable-installer.zip 840CEC0E80922D747974E514729CA88CC6FF8070B510A8DFC2A70C9CFAD4EF9D newrelic-agent-win-x64-8.36.0.0.msi 047214F5937754DB77EDBBA6E7460C4ADCE11A6AF54C812CD596EDFC7084F754 newrelic-agent-win-x64-8.36.0.0.zip 35182DEC9D68C402AF8489515E0EDD41CEC7B5CB639E0B3296059D2C6090F3D2 newrelic-agent-win-x86-8.36.0.0.ms 7B43749D0EE4E8A887EC4C71BA079C00EB3FD33CF9CB5B9F20F7BEE6AF1887DC newrelic-agent-win-x86-8.36.0.0.zip C3E03647EA1C4519ADD90A76999B35D582E1A241265FF5CD4DEDCD349D8EC6A6 newrelic-netcore20-agent_8.36.0.0_amd64.deb 6E74F4D1937F7C99679438D3DD918FBCCD9B733EF4A5CE0D7DF7CB21F5B2812A newrelic-netcore20-agent_8.36.0.0_amd64.tar.gz FD915C68D7B5A4A8ACAFA06E689E7A5B3210AAA42D0200C6D7C685DB36D2771D newrelic-netcore20-agent-8.36.0.0-1.x86_64.rpm 158BBE145ACC1662FC88547A37D6EFB725EC997985A40903A604E0B8CC0B94D2 newrelic-netcore20-agent-win-8.36.0.0-scriptable-installer.zip 6CC926F38996FF0DC502141C2DC59078B5811885E14D1435C23811AA88DFE462 newrelic-netcore20-agent-win-x64-8.36.0.0.zip 83CA1F3F010F8727572ABEE5560454FEF5414068F572E87031C8064FAC0153A8 newrelic-netcore20-agent-win-x86-8.36.0.0.zip 94B4100F4CF2B7862436BD12D627CF30EA03B14AB117A6EBF1CA5E0A8AEBC9D7 Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-83600","eolDate":"2022-12-08"},{"agent":"dotnet","date":"2020-11-09","downloadLink":null,"version":"8.35.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features .NET 5 GA Support We have validated that this version of the agent is compatible with .NET 5 GA. See the compatibility and requirements for .NET Core  page for more details. Fixes Fixes Issue #337  by removing obsolete code which was causing memory growth associated with a large number of transaction names. PR #348 : guards against potential exceptions being thrown from the agent API when the agent is not attached. Checksums File SHA-256 Hash newrelic-agent-win-8.35.0.0-scriptable-installer.zip F77B7BE0AA8C1892F085EA2B30B01E7A192FFAD296F35298267910DA14ABB529 newrelic-agent-win-x64-8.35.0.0.msi EAA8B9D6C17B31B81003107C07E5B2B3872667F10603F119A782220C43D27713 newrelic-agent-win-x64-8.35.0.0.zip 94DC8BD9F9C5D8BFE849C4E2A284AAF7D22A46F85CFA50936573C22AEF90A507 newrelic-agent-win-x86-8.35.0.0.ms CEA4474FB19E8EEDB7C955C36B8EC884232989C4B1A92F0ABF9804F1BC08396C newrelic-agent-win-x86-8.35.0.0.zip 61192FF4A219B63ECE2F9526EA599626D942B749F935CA405871BDC7AF252810 newrelic-netcore20-agent_8.35.0.0_amd64.deb 9638E1F68E7A05A4D11314D0DEF40445EC4E8E9A4B322342DD7935CC56AAE4F3 newrelic-netcore20-agent_8.35.0.0_amd64.tar.gz 305B2CA7C35BDD86BDAAB3CA9708A02DA3E87A9D9A49216E56DFC316E07F6C4A newrelic-netcore20-agent-8.35.0.0-1.x86_64.rpm 0CE69F23914820740FEDEA61D72E674F80E1C4CDB8A7386082DD47EB11F129D8 newrelic-netcore20-agent-win-8.35.0.0-scriptable-installer.zip 4A0FD8FC0DD2D0EC06CA92D6CE7342FCE12D103F7595110625488F77678C187F newrelic-netcore20-agent-win-x64-8.35.0.0.zip A7D05A3EB5DB12A10DDFF65B9E95272B8BBB88B78B6075CB7BC517D5F96715E2 newrelic-netcore20-agent-win-x86-8.35.0.0.zip 2D6000577D591F637E0F5C8B63E2CCCF44B5920854CC5E06D93EA0E13046801B Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-83500","eolDate":"2022-11-09"},{"agent":"dotnet","date":"2020-10-26","downloadLink":null,"version":"8.34.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features .NET 5 RC2 Support We have validated that this version of the agent is compatible with .NET 5 Release Candidate 2. Fixes Fixes #301  where the agent incorrectly parses server-side configuration causing agent to shutdown.#310 Modifies WCF Instrumentation to address #314  by minimizing the reliance upon handled exceptions during the attempt to capture CAT and DT payloads. Checksums File SHA-256 Hash newrelic-agent-win-8.34.0.0-scriptable-installer.zip 463A0DA90BF60E59691005DBC3698A52DA11C819F4F476012C2E871133CA59A4 newrelic-agent-win-x64-8.34.0.0.msi 3642580229F7EFF9AA37880DA46C4B2BCAA54D1C169D1C7EC8A20327E6241BAF newrelic-agent-win-x64-8.34.0.0.zip B6BAA1843376E9C47EE64BDCC19CAE7CDA089BFEEECB3C867C6498404F24C3BE newrelic-agent-win-x86-8.34.0.0.msi 80D9370362B43863EAF6C87871DC8D0EF5CC5FEA47A1DA1BEFA8D5C5B5EE81AC newrelic-agent-win-x86-8.34.0.0.zip 662F3F7FBF7416E64C68F4E530FAB3804419E09C2CACADD7A8FF5031FA49CD38 newrelic-netcore20-agent-8.34.0.0-1.x86_64.rpm 60ED7D61DE282881E49E2C6598505C88418F7CD3F5EFB3E5BE76DD260C410388 newrelic-netcore20-agent-win-8.34.0.0-scriptable-installer.zip 381D723C36620D2BF9D36521EFC8E12EA961A31D741704080571BEB1C6A443AF newrelic-netcore20-agent-win-x64-8.34.0.0.zip C6C9C62469D09413456436E865E0DCB84A06051A51EC82B97D8E81CB7012FBA9 newrelic-netcore20-agent-win-x86-8.34.0.0.zip EFF2C7F340A4B767B9ED4DD7225005AE2D219BDAC8815B1224A53518FD394027 newrelic-netcore20-agent_8.34.0.0_amd64.deb 12E3ED96888B236CA7845382441C45698A0AB5DF99BBF3DF05B379E0D68728A3 newrelic-netcore20-agent_8.34.0.0_amd64.tar.gz 2987B39AC2CDFE19CC1E8EB4D9A2DB4A91817A37ED442CC51AF441128D90D216 Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-83400","eolDate":"2022-10-26"},{"agent":"dotnet","date":"2018-06-19","downloadLink":null,"version":"8.3.360.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Download URLs Download the appropriate release for your New Relic .NET agent: https://download.newrelic.com/dot_net_agent/previous_releases New Features Adds automatic capture of datastore information for MongoDB driver versions 2.6.x, 2.5.x, 2.4.x, and 2.3.x. [.NET Core 2.0]  Adds thread profiler support for .NET Core applications running on Windows. Fixes Improved the agent's ability to recover from certain connection related issues without requiring an agent or application restart. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-833600","eolDate":"2021-06-19"},{"agent":"dotnet","date":"2020-10-12","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"8.33.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes #223  so the agent can be compatible with ASP.NET Core 5 RC1. Fixes issue in .NET 5 applications where external calls made with HttpClient may not get instrumented. For example, calls made with HttpClient.GetStringAsync would be missed. (#235 ) Fixes issue #257  where .NET Standard Libraries that do not reference mscorlib fail to be instrumented in .NET Framework applications. Reduces the performance impact of large amounts of instrumentation. See issue #269  for more information. Checksums File SHA-256 Hash newrelic-agent-win-8.33.0.0-scriptable-installer.zip B9685CE346FBCC1D403E3AFCB032C3050ABEE0EED7CB468387FE6793B78139F4 newrelic-agent-win-x64-8.33.0.0.msi 2C641DE0A6EB1CC81812341219CB8B2D1A7B17D37BC0E10435670DC91F5F03D0 newrelic-agent-win-x64-8.33.0.0.zip 8BA85B43037222C642DCAC1647922267C232BD5ABD67315BD31C27A9ECE49A65 newrelic-agent-win-x86-8.33.0.0.msi 5D6CB7F0BE00969356AB62DFA2DEB028AA8CABD13CD177760E960E29532E33A2 newrelic-agent-win-x86-8.33.0.0.zip E532F3ADFCE4D5D835C1865410F07A74E11C364C9486C89BE19326FC842D7C1F newrelic-netcore20-agent-8.33.0.0-1.x86_64.rpm EE37954141958D9F5E76ED129CAD5836C0D6F5AD20F8D2C9CD6D7521FEF9AC7A newrelic-netcore20-agent-win-8.33.0.0-scriptable-installer.zip C7AFFA93D569DB20E0D8D1F6136F002284F7E7FDCF6AB97A33F9A3C1464A605E newrelic-netcore20-agent-win-x64-8.33.0.0.zip 4CDF06211CAE67ED5393F18424FBD91F884A4EF82B3F5CB639643BE16A8430DF newrelic-netcore20-agent-win-x86-8.33.0.0.zip EA4B519DFA40615F7877389808DCDD65DC5F9E9F84A5CBD701B6D28814C037DD newrelic-netcore20-agent_8.33.0.0_amd64.deb CBE01E82D68718254F29A491243766FF759E0295C1559487A466178BE01CBD71 newrelic-netcore20-agent_8.33.0.0_amd64.tar.gz 150FB5A6D122B78457FAD596C842F2B49682680085BF666767B492F37E694EF0 Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-83300","eolDate":"2022-10-12"},{"agent":"dotnet","date":"2020-09-16","downloadLink":null,"version":"8.32.0.0","features":["Allow obfuscating proxy password","Add instrumentation for MySqlConnector ADO.NET driver","Allow nullable reference types in the Agent API","Improve support for NetTCP Binding in WCF"],"bugs":["Fix potential exception with MVC 3","Fix timing of some async methods"],"security":[],"supportedOperatingSystems":null,"description":"New Features Proxy Password Obfuscation Support Agent configuration supports the obfuscation of the proxy password. The New Relic Command Line Interface (CLI)  may be used to obscure the proxy password. The following documentation  describes how to use an obscured proxy password in the .NET Agent configuration. MySqlConnector Support The MySqlConnector ADO.NET driver is instrumented by default. Fixes #85  and implements this suggestion . Nullable Reference Type support in the API Enables nullable reference types that are part of the C# 8.0 language specification and updates the signatures of API methods accordingly. There should be no required changes in API usage. Improved Support for NetTCP Binding in WCF Instrumentation When the NetTCP Binding type is used in Windows Communication Foundation (WCF), the Agent will now send and receive trace context information in support of Distributed Tracing (DT) or Cross Application Tracing (CAT). Implements #209 . Fixes Fixes an issue that may cause InvalidCastException due to an assembly version mismatch in Mvc3 instrumentation. Fixes an async timing issue that can cause the end time of Task-returning methods to be determined incorrectly. Checksums File SHA-256 Hash newrelic-agent-win-8.32.0.0-scriptable-installer.zip 992B077AF9F8966F3F4B7925B6ACB5CE18390EF16115DBE136723EFC3965F3AB newrelic-agent-win-x64-8.32.0.0.msi A675DA40B522551B3DBBCA49941143940A5253E88DD59F26E5B2C862EF6A48FE newrelic-agent-win-x64-8.32.0.0.zip 9ABAE87713705DA3C7C3C65BA89DA4A0FE9E05739E00A90152882BF37E3F1679 newrelic-agent-win-x86-8.32.0.0.msi 98D21C44C55663BB5DA762C1FAFA576EAAE24D7A62B6BAAC8337813DF1F0A9BC newrelic-agent-win-x86-8.32.0.0.zip 846F9B0E36B6F374AE547FD9AD9AB508A47D4D8567E9EAE20F18136F762F5E86 newrelic-netcore20-agent-8.32.0.0-1.x86_64.rpm 6E6148B069E4B55F7E001AA2524EC5B75306E1901005977FA76F8AD3834E5541 newrelic-netcore20-agent-win-8.32.0.0-scriptable-installer.zip 842D04237B478A35E3634A92B1E21C734227B6173CE587F790F66E7209163550 newrelic-netcore20-agent-win-x64-8.32.0.0.zip 81D9ABE4DC782CBDAA0B3F8EF2D3AE9E545DE9DB9A9B3BF2F3FD4AF4AFCA9FA2 newrelic-netcore20-agent-win-x86-8.32.0.0.zip 6A78FD50FF666EFAA65AA97EA0FDE8F97BBEA7223DAEFAB2AC929F43F4A696E9 newrelic-netcore20-agent_8.32.0.0_amd64.deb CE44BF8463B0BFD7AE711ACDB4EB07553CBB8F68066CCFA09FAEFB830D53277C newrelic-netcore20-agent_8.32.0.0_amd64.tar.gz 695A77EC5693349E8122B59AD1655DE4AA41CB484C7580A2BFAE5726129CE371 Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-83200","eolDate":"2023-09-16"},{"agent":"dotnet","date":"2020-08-17","downloadLink":null,"version":"8.31.0.0","features":["Add support for Expected Errors","Add more configuration options for Ignored Errors"],"bugs":["Correctly report garbage collection metrics on Windows","Prevent overwriting config file on Linux upgrade"],"security":[],"supportedOperatingSystems":null,"description":"New Features Expected Errors Support Certain errors that are expected within the application may be identified so that they will not be counted towards the application's error rate and Apdex Score. Only errors that truly affect the health of the application will be alerted on. Please review the following documentation  for details on how to configure Expected Errors. Ignored Errors Enhancements Certain errors may be identified in configuration so that they will be ignored. These errors will not be counted towards the application's error rate, Apdex score, and will not be reported by the agent. Please review the following documentation  for details on how to configure Ignored Errors. New configuration element <ignoreMessages> supports filtering based on the error message. Please note that the <ignoreErrors>  configuration element has been deprecated and replaced by <ignoreClasses> . The .NET Agent continues to support this configuration element, but its support may be removed in the future. Fixes Garbage Collection Performance Metrics for Windows Fixes an issue where Garbage Collection Performance Metrics may not be reported for Windows Applications. Maintaining newrelic.config on Linux package upgrades Fixes an issue where newrelic.config was being overwritten when upgrading the agent via either rpm/yum (RedHat/Centos) or dpkg/apt (Debian/Ubuntu). Checksums File SHA-256 Hash newrelic-agent-win-8.31.0.0-scriptable-installer.zip 1A7D11F91E36259BED3C5A99ACB7FDD967BEACE36AC744401CB3D8D1A2FF1D48 newrelic-agent-win-x64-8.31.0.0.msi 4F9AB318FCD3956703E659A3B2C8F4C4F1C51F479F479659B384DEA64A701813 newrelic-agent-win-x64-8.31.0.0.zip D0F4BE582B090B7B6F6EF76B837904A8DA18713E2715E6573145B9AB11603560 newrelic-agent-win-x86-8.31.0.0.msi C28C875482B22A4D929FFDB1E9EC46EF2CA1EDEDAE46360DC5E257CF5BF86E3F newrelic-agent-win-x86-8.31.0.0.zip B689142C9B5373EB0272D6C3C3759E1A9DD2717A4FE79140BC9B766E8FABF71D newrelic-netcore20-agent-8.31.0.0-1.x86_64.rpm 4B56330CDD2F8BA7D661A5ECC47E9C53AA52D1295D9F67748BF1F342BA6852EE newrelic-netcore20-agent-win-8.31.0.0-scriptable-installer.zip 27DB97C3B407115033EAC92DC608567E7C605E5D91297EFD298EA84E78F3BB71 newrelic-netcore20-agent-win-x64-8.31.0.0.zip 3DAFB26542734531311C7963870EA21F43E028BB00EA4044D70DF18A58993484 newrelic-netcore20-agent-win-x86-8.31.0.0.zip 55B3EBEA7298D5DC47A5FC72C81327C6B62EE560445E3595FDA88BE464532898 newrelic-netcore20-agent_8.31.0.0_amd64.deb 14EB3E46E1A540A020433CA83EDAC75076C1DF9D8894C205582A1FE0330B1981 newrelic-netcore20-agent_8.31.0.0_amd64.tar.gz 5EA9620DE0D3EA72859EEC058E3CD811F8BAFCAB6957F005B9D1EFC73A9CB400 Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-83100","eolDate":"2023-08-17"},{"agent":"dotnet","date":"2020-07-16","downloadLink":null,"version":"8.30.0.0","features":["Convert the .NET Agent to an open source project"],"bugs":["Correctly report memory usage on Linux","Improve Infinite Tracing performance","Allow configuration changes at runtime on .NET 5"],"security":[],"supportedOperatingSystems":null,"description":"New Features The .NET agent is now open source! The New Relic .NET agent is now open source! Now you can view the source code to help with troubleshooting, observe the project roadmap, and file issues directly in this repository. We are now using the Apache 2 license . See our Contributing guide  and Code of Conduct  for details on contributing! Fixes Memory usage reporting for Linux Fixes issue where applications running on Linux were either reporting no physical memory usage or using VmData to report the physical memory usage of the application. The agent now uses VmRSS through a call to Process.WorkingSet64  to report physical memory usage. See the dotnet runtime discussion  and the proc man pages  for more details about this change. Infinite Tracing performance Fixes issue where the agent may consume too much memory when using Infinite Tracing. .NET 5 support Fixes issue with applications running on .NET 5 that prevented instrumentation changes at runtime (either though editing instrumentation XML files or through the Live Instrumentation editor Beta). Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-83000","eolDate":"2023-07-16"},{"agent":"dotnet","date":"2020-06-25","downloadLink":null,"version":"8.29.0.0","features":["Add Request Parameters and other attributes to Span Events"],"bugs":["Fix potential crash when updating custom instrumentation at runtime"],"security":[],"supportedOperatingSystems":null,"description":"New Features Additional Transaction Information applied to Span Events When Distributed Tracing and/or Infinite Tracing are enabled, the Agent will now incorporate additional information from the Transaction Event on to the root Span Event of the transaction. The following items are affected: Request Parameters request.parameter.* Custom Attribute Values applied to the Transaction via API Calls AddCustomParameter and ITransaction.AddCustomAttribute. request.uri response.status host.displayName Security Recommendation Review your Transaction Attributes  configuration. Any attribute include or exclude settings specific to Transaction Events, should be applied to your Span Attributes  configuration or your Global Attributes  configuration. Fixes Fixes issue where updating custom instrumentation while application is running could cause application to crash. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-82900","eolDate":"2023-06-25"},{"agent":"dotnet","date":"2020-06-04","downloadLink":null,"version":"8.28.0.0","features":[],"bugs":["Improve performance of Infinite Tracing","Fix issue tracking transactions across threads","Fix exception with some MVC controller actions","Always report Error Events with Error Traces"],"security":[],"supportedOperatingSystems":null,"description":"New Features Fixes Infinite Tracing Fixes issue with Infinite Tracing where a communication error can result in consuming too much CPU. Fixes issue with Infinite Tracing where a communication error did not clean up its corresponding communication threads. Agent version 8.30 introduces significant performance enhancements to Infinite Tracing. To use Infinite Tracing, please upgrade to version 8.30 or later. Fixes issue in .NET Framework ASP.NET MVC applications where transactions started on one thread would flow to background threads (e.g., started with Task.Run) in some scenarios but not others. Transaction state used to only flow to a background thread if the transaction originated from an async controller action. Transaction state now flows to background threads regardless of whether the controller action is async or not. Fixes issue in .NET Framework ASP.NET MVC applications where agent instrumentation of an MVC controller action could cause an InvalidProgramException. Fixes a problem with the reporting of Errors where Error Events may not appear even though Error Traces are being sent. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8280","eolDate":"2023-06-04"},{"agent":"dotnet","date":"2020-04-30","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"8.27.139.0","features":["Add support for W3C Trace Context"],"bugs":["Fix incompatibility between Synthetics and Distributed Tracing","Remove unnecessary dependencices on RPM-based Linux distros","Correctly report TransportDuration metric"],"security":[],"supportedOperatingSystems":null,"description":"New Features Support for W3C Trace Context, with easy upgrade from New Relic trace context Distributed Tracing now supports W3C Trace Context headers  for HTTP when distributed tracing is enabled. Our implementation can accept and emit both W3C trace header format and New Relic trace header format. This simplifies agent upgrades, allowing trace context to be propagated between services with older and newer releases of New Relic agents. W3C trace header format will always be accepted and emitted. New Relic trace header format will be accepted, and you can optionally disable emission of the New Relic trace header format. When distributed tracing is enabled with <distributedTracing enabled=\"true\" />, the .NET agent will now accept W3C's traceparent and tracestate headers when calling Transaction.AcceptDistributedTraceHeaders . When calling Transaction.InsertDistributedTraceHeaders , the .NET agent will include the W3C headers along with the New Relic distributed tracing header, unless the New Relic trace header format is disabled using <distributedTracing enabled=\"true\" excludeNewrelicHeader=\"true\" />. The existing Transaction.AcceptDistributedTracePayload and Transaction.CreateDistributedTracePayload APIs are deprecated  in favor of Transaction.AcceptDistributedTraceHeaders  and Transaction.InsertDistributedTraceHeaders . Fixes Fixes issue which prevented synthetic monitors from working when distributed tracing is enabled. Fixes issue where our RPM package for installing the agent on RPM-based Linux distributions included a 32-bit shared library, which created unnecessary dependencies on 32-bit system libraries. Fixes issue where the TransportDuration metric for distributed traces was always reporting 0. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8271390","eolDate":"2023-04-30"},{"agent":"dotnet","date":"2020-04-20","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"8.26.630.0","features":["Add Infinite Tracing feature","Add Error Attributes to Span Events"],"bugs":["Fix InstrumentAllNETFramework option on MSI installs","Fix incompatibility with Azure App Service and Kudu on Linux","Better handle Ignored Errors","Fix possible exception when instrumenting StackExchange.Redis"],"security":[],"supportedOperatingSystems":null,"description":"New Features Infinite Tracing on New Relic Edge This release adds support for Infinite Tracing on New Relic Edge . Infinite Tracing observes 100% of your distributed traces and provides visualizations for the most actionable data so you have the examples of errors and long-running traces so you can better diagnose and troubleshoot your systems. You configure your agent to send traces to a trace observer in New Relic Edge. You view your distributed traces through the New Relic’s UI. There is no need to install a collector on your network. Infinite Tracing is currently available on a sign-up basis. If you would like to participate, please contact your sales representative. Agent version 8.30 introduces significant performance enhancements to Infinite Tracing. To use Infinite Tracing, please upgrade to version 8.30 or later. Error attributes now added to each span that exits with an error or exception Error attributes error.class and error.message are now included on the span event in which an error or exception was noticed, and, in the case of unhandled exceptions, on any ancestor spans that also exit with an error. The public API method NoticeError now attaches these error attributes to the currently executing span. Spans with error details are now highlighted red in the Distributed Tracing UI , and error details will expose the associated error.class and error.message. It is also now possible to see when an exception leaves the boundary of the span, and if it is caught in an ancestor span without reaching the entry span. NOTE: This “bubbling up” of exceptions will impact the error count when compared to prior behavior for the same trace. It is possible to have a trace that now has span errors without the trace level showing an error. If multiple errors occur on the same span, only the most recent error information is added to the attributes. Prior errors on the same span are overwritten. These span event attributes conform to ignored errors  configuration. Fixes Fixes issue in the MSI installer which prevented the InstrumentAllNETFramework feature selection from working as expected on the command line. Fixes issue for Azure App Service environments running on Linux that caused both the application and its Kudu process to be instrumented by the agent. The Kudu process is no longer instrumented. Fixes issue when using the ignoreErrors configuration . Previously, when an exception contained a inner exception(s), the ignoreErrors config was only applied to the outer-most exception. Now, both the outer-most and inner-most exception type are considered when evaluating the ignoreErrors configuration. Fixes an issue that could cause an exception to occur in the instrumentation for StackExchange Redis. This exception caused the instrumentation to shut down leaving StackExchange Redis uninstrumented. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8266300","eolDate":"2023-04-20"},{"agent":"dotnet","date":"2020-03-11","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"8.25.214.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Thread profiling support for Linux Thread profiling on Linux will be supported on .NET Core 3.0 or later applications when running .NET agent version 8.23 or later. Triggering a thread profile is done from the Thread profiler page in APM. Accessing Span-Specific information using the .NET Agent API New property, CurrentSpan has been added to IAgent and ITransaction. It returns an object implementing ISpan which provides access to span-specific functions within the API. Adding Custom Span Attributes using the .NET Agent API New method, AddCustomAttribute(string, object) has been added to ISpan. This new method accepts and supports all data-types. Further information may be found within .NET Agent API documentation . Adding custom attributes to spans requires distributed tracing and span events to be enabled. See .NET agent configuration Fixes Fixes issue where adding multiple custom attributes on a Transaction using ITransaction.AddCustomAttribute  causes the agent to ignore additional attempts to add custom attributes to any transaction. Fixes issue that prevented Custom Events from being sent to New Relic until the agent shuts down. Fixes issue that can cause asynchronous Redis calls in an ASP.NET MVC application to report an inflated duration. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8252140","eolDate":"2023-03-11"},{"agent":"dotnet","date":"2020-02-19","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"8.24.244.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Adding custom transaction attributes using the .NET Agent API New method, AddCustomAttribute(string, object) has been added to ITransaction. This new method accepts and supports all data types. Method AddCustomParameter(string, IConvertable) is still available with limited data-type support; however, this method should be considered obsolete and will be removed in a future release of the agent API. Further information may be found within .NET Agent API documentation . Enhanced type support for RecordCustomEvent and NoticeError API methods. APIs for recording exceptions and custom events now support values of all types. The NoticeError API method has new overloads that accept an IDictionary<string, object>. The RecordCustomEvent methods have been modified to handle all types of data. In that past, they only handled string and float types. Further information may be found within .NET agent API documentation . New attributes on span events Spans created for external HTTP calls now include the http.statusCode attribute representing the status code of the call. Spans created for calls to a datastore now include the db.collection attribute. For instance, this will be the table name for a call to MS SQL Server. Ability to exclude attributes from span events Attributes on span events (e.g., http.url) can now be excluded via configuration. See .NET agent configuration  for further information. Fixes New Relic distributed tracing relies on propagating trace and span identifiers in the headers of external calls (e.g., an HTTP call). These identifiers now only contain lowercase alphanumeric characters. Previous versions of the .NET agent used uppercase alphanumeric characters. The usage of uppercase alphanumeric characters can break traces when calling downstream services also monitored by a New Relic agent that supports W3C trace context (New Relic's .NET agent does not currently support W3C trace context. Support for W3C trace context for .NET will be in an upcoming release). This is only a problem if a .NET application is the originator of the trace. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8242440","eolDate":"2023-02-19"},{"agent":"dotnet","date":"2020-01-15","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"8.23.107.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Support for Real Time Streaming Event data is now sent to New Relic every five seconds, instead of every minute. As a result, transaction, error, and custom events will now be available in New Relic and Insights dashboards in near real time. For more information on how to view your events with a five-second refresh, see the real time streaming documentation . Note that the overall limits on how many events can be sent per minute have not changed. Also, span events, metrics, and trace data is unaffected, and will still be sent every minute. Fixes Fixes security vulnerability NR20-01  which may cause SQL parameter values to appear in the agent log file when the logging level is set to Debug or Finest and the calling application supplies SQL parameters without a @ prefix. Fixes an issue where Explain Plans are not generated for database commands with parameters that do not have the @ prefix on the name. Fixes an issue with the timing of some async MongoDB driver methods. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8231070","eolDate":"2023-01-15"},{"agent":"dotnet","date":"2019-12-19","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"8.22.181.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Enables ability to migrate to Configurable Security Policies (CSP) on a per agent basis for accounts already using High-security mode (HSM). When both HSM and CSP are enabled for an account, an agent (this version or later) can successfully connect with either high_security: true or the appropriate security_policies_token configured. Fixes Fixes a number of issues caused when Application Initialization has been enabled in Internet Information Services (IIS) (a.k.a. AlwaysOn  in Azure App Services). The issues include the inability for the agent to name an app or possibly not instrument an app at all when app pool allow/deny listing has been applied via newrelic.config. In an Azure App Services scenario inadvertent instrumentation of the Kudu process could also occur. This was caused by the agent relying on the IIS environment variable APP_POOL_ID. When Application Initialization or AlwaysOn are enabled, the APP_POOL_ID environment variable is unavailable to the agent. The agent now also attempts to parse the command line of the w3wp.exe process to identify the application pool the app is running under. Improves the handling of OperationCanceledException errors when trying to connect or send data to New Relic. Fixes a problem with instrumenting ASP.NET Core applications that can occur when the Microsoft.AspNetCore.Diagnostics.Abstraction assembly is not available. Fixes a problem where WCF Instrumentation may shut-down due to an unexpected error. Fixes a problem that can cause the agent to fail to shutdown completely when a shutdown is triggered while the agent is still in its startup process. Fixes a problem with the GetLinkingMetadata  API method that could cause an expected KeyValuePair to not be included in the Dictionary. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8221810","eolDate":"2022-12-19"},{"agent":"dotnet","date":"2018-05-16","downloadLink":null,"version":"8.2.216.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Download URLs Download the appropriate release for your New Relic .NET agent: https://download.newrelic.com/dot_net_agent/previous_releases New Features Replaces the request_uri attribute with request.uri. Adds the request.uri attribute to transaction traces and error traces. If you wish to control the presence of this attribute please follow the instructions at https://docs.newrelic.com/docs/agents/net-agent/configuration/net-agent-... Fixes [.NET Framework]  Fixes issue of recursive directory creation when recovering from a failed upgrade install in the scriptable installer. [.NET Framework]  Fixes issue where Thread Profiler fails to resolve types and method names. These would appear as UnknownClass.UnknownMethod(<#>) in a profile. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-822160","eolDate":"2021-05-16"},{"agent":"dotnet","date":"2019-11-14","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"8.21.34.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes [.NET Core]  Fixes a problem that could cause some .NET Core 3.0 applications to hang if they were configured with an invalid license key. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-821340","eolDate":"2022-11-14"},{"agent":"dotnet","date":"2019-10-01","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"8.19.353.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features .NET agent installation procedures have been simplified for Windows environments enabling you to more easily monitor .NET Core applications. Our standard installation procedures  use a single MSI installer to install support for both .NET Framework and .NET Core applications. If you previously only monitored .NET Framework applications then nothing changes for you. If you were previously installing our .NET Core support using one of our manual install procedures you may need to port any custom modifications you have made to your newrelic.config  and any XML custom instrumentation  you have applied to the new install location. Trace Accessors APIs: two new API calls to obtain information used to support tracing. TraceMetadata  - returns a property with access to the following: TraceId - the currently executing trace's identifier. SpanId - the currently executing span's identifier. IsSampled - returns whether or not the current transaction is part of a sampled distributed trace. GetLinkingMetadata  - returns key/value pairs which can be used to correlate this application in the New Relic backend. Fixes [.NET Framework]  Fix an issue in WCF instrumentation where multiple transactions were created for a call to a WCF service endpoint that used the begin/end async pattern. [.NET Core]  Fix an application crash bug on Alpine Linux. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8193530","eolDate":"2022-10-01"},{"agent":"dotnet","date":"2019-08-26","downloadLink":null,"version":"8.18.241.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Adds instrumentation for StackExchange.Redis asynchronous methods. Generally, these methods end with the Async suffix (e.g., StringSetAsync). [.NET Core]  Adds support in the .NET Core Agent for StackExchange.Redis . Fixes Resolves security issue where a manually constructed SQL stored procedure invocation may cause sensitive data to be captured in metric names. See Security Bulletin NR19-05 Fix a memory leak introduced in agent version 8.17.438.0. Fixes an issue where NullReferenceExceptions may be logged in scenarios where a large number of segments are created for a single transaction. Fix an issue where the request.uri attribute on transaction traces and event data would be set to the full URI of the request instead of the request path (e.g., http://www.domain.com/request/path instead of /request/path) in automatic instrumentation of ASP.NET and WCF applications, as well as in the agent API method SetTransactionUri(). [.NET Core]  Fix an issue where memory and CPU metrics may be overstated in APM. [.NET Framework]  Fix an issue with the 8.17.438.0 release which can cause a delay in starting up an application. [.NET Framework]  Fix an issue where the agent may fail to start for 32-bit ASP.NET MVC applications when the NewRelic.Agent NuGet package was used to install the agent. [.NET Framework]  Fix an issue on agent shutdown where an error log message may appear in the agent log indicating an HTTP 409 error response from New Relic. This error did not have any other impact other than appearing in the log. [.NET Framework]  Fix an issue where a large number of error messages may be reported on agent startup due to insufficient permissions of the app-pool user to create performance counters. In this release, a specific warning message regarding permissions will be reported. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8182410","eolDate":"2022-08-26"},{"agent":"dotnet","date":"2019-07-22","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"8.17.438.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features This release adds Transaction event attributes that provide context between your Kubernetes cluster and services. For details on the benefits see this blog post . The NewRelic.Agent NuGet package  now includes the x86 (32-bit) profiler for Windows. To monitor 32-bit Windows applications using this NuGet package the COR_PROFILER_PATH (.NET Framework ) or the CORECLR_PROFILER_PATH (.NET Core ) environment variable needs to be set to the path the of the 32-bit profiler DLL (NewRelic.Profiler.x86.dll). For .NET Core applications hosted in Azure App Services, the New Relic Azure Site Extension  can now be used to install the agent. This was previously only available for .NET Framework applications. Follow these procedures  to install. Fixes Fixed an issue where the NRQL Extrapolate clause  in Insights did not work properly for Transaction Events. Fixed an issue where cross application tracing could cause a metric grouping issue (MGI) for web requests that result in a 300 or higher response status code. Transaction names may now be rolled up by status code. Fixed an issue where browser script injection in ASP.NET applications could cause a metric grouping issue (MGI) for web requests that result in a 30x redirect status code. Transaction names may now be rolled up by status code. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8174380","eolDate":"2022-07-22"},{"agent":"dotnet","date":"2018-05-01","downloadLink":null,"version":"8.1.712.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features [.NET Framework]  The .NET Framework agent now supports instrumenting ASP.NET Core applications that are running on .NET Framework. The .NET Core specific agent is still required for instrumenting applications running on .NET Core. Fixes Fixed issue where deadlocks could occur in some situations when a ThreadAbortException was thrown within a client application. Fixed issue where only the first transaction name set via API call to SetTransactionName() would be honored. Now, the last call to SetTransactionName() will be the name applied to the transaction. [.NET Core 2.0]  Fixed issue with the .NET Core agent on Windows where the CORECLR_PROFILER_PATH environment variable was not being expanded properly in certain deployment scenarios. [.NET Framework]  Fixed issue introduced in agent version 8.1.709.0 that caused some .NET Framework applications to throw the following exception: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-817120","eolDate":"2021-05-01"},{"agent":"dotnet","date":"2018-04-19","downloadLink":null,"version":"8.1.709.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"This release has been unpublished. Use version 8.1.712.0  or higher. This version introduced a bug that could cause crashes for .NET Framework applications manually loading types from assemblies in the application domain. This includes enumerating custom attributes. The encountered error will appear like the following: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified New Features [.NET Framework]  The .NET Framework agent now supports instrumenting ASP.NET Core applications that are running on .NET Framework. The .NET Core specific agent is still required for instrumenting applications running on .NET Core. Fixes Fixed issue where deadlocks could occur in some situations when a ThreadAbortException was thrown within a client application. Fixed issue where only the first transaction name set via API call to SetTransactionName() would be honored. Now, the last call to SetTransactionName() will be the name applied to the transaction. [.NET Core 2.0]  Fixed issue with the .NET Core agent on Windows where the CORECLR_PROFILER_PATH environment variable was not being expanded properly in certain deployment scenarios. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-817090","eolDate":"2021-04-19"},{"agent":"dotnet","date":"2019-06-11","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"8.16.567.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes CORS (Cross-Origin Resource Sharing) “pre-flight” requests with the HTTP OPTIONS method were causing extraneous metrics to be generated for ASP.NET Core applications using the CORS middleware. These requests will now be ignored by the agent. Fixes a problem where WCF instrumentation shuts down when WebHttpBinding is used and CAT is enabled. Fixes a problem where an async WCF client call may prevent further data from being captured in a transaction. New Features Adds database instrumentation for Microsoft.Data.SqlClient. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8165670","eolDate":"2022-06-11"},{"agent":"dotnet","date":"2019-04-22","downloadLink":null,"version":"8.15.455.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes a problem with parsing method signatures that do not align with ECMA-335 that could cause an application to crash. Fixes a problem where third-party libraries that perform assembly-scanning using reflection may encounter TypeLoadExceptions. Fixes a problem where the agent may incorrectly report Response Time when custom instrumentation is applied to methods that are called from within an instrumented framework (such as ASP.Net). Resolves security issue with how SQL Server handles escaping which could lead to a failure to correctly obfuscate SQL statements. See Security Bulletin NR19-03 . Resolves issue with not rolling up 30x HTTP response codes which resulted in MGI issues. New Features Adds improved WCF support WCF client task asynchronous programming model (following the task asynchronous pattern) calls are tracked as external calls. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8154550","eolDate":"2022-04-22"},{"agent":"dotnet","date":"2019-03-18","downloadLink":null,"version":"8.14.222.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed issue where transactions may not get reported when custom instrumentation is applied to async methods with a void return type. Instrumenting async void methods is generally not recommended and may result in unexpected segment timing as well as the disruption of downstream instrumentation. Please review async limitations online help for alternative approaches. New Features [.NET Core]  Adds support for .NET Core 3.0 [.NET Core]  Adds support for ASP.NET Core 3.0 [.NET Framework]  Adds support for .NET Framework 4.8 Early Access build 3694 Adds official support for Postgres/Npgsql versions 4.0. Supports Sync and Async methods, on .Net Framework and .Net Core running in Windows and Linux. Eliminates duplicate and extraneous datastore metrics and trace segments associated with opening connections to databases (as seen in prior agent versions). Npgsql versions older than 4.0 may also be instrumented, but duplicate and/or missing metrics are possible. Adds improved WCF support WCF client calls are tracked as external calls WCF client synchronous and asynchronous programming model (following the begin/end asynchronous pattern) calls are tracked. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8142220","eolDate":"2022-03-18"},{"agent":"dotnet","date":"2019-02-12","downloadLink":null,"version":"8.13.798.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes [Framework]  Improved support for async workloads in self-hosted OWIN applications. [Framework]  Status code only errors are now noticed in self-hosted OWIN applications. New Features [Framework]  Adds support for the following in .Net Framework self-hosted OWIN apps: Microsoft OWIN version 4 Distributed tracing Cross application tracing Request parameters capture Request URI capture Introduces single metric creation for HTTP status codes 400 and greater Exception capture from OWIN middleware components Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8137980","eolDate":"2022-02-12"},{"agent":"dotnet","date":"2019-01-09","downloadLink":null,"version":"8.12.216.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed an issue where the response time of a web transaction could be misreported when making asynchronous external calls whose duration extended beyond the time the web transaction response ended. Fixed an issue when using OpenRasta instrumentation where the full URL could be captured on instrumented requests. This may have resulted in query strings being collected which can contain sensitive information. See security bulletin NR19-01 . Fixes an issue with auto-instrumenting RestSharp and Couchbase driver calls involving non-public collection types. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8122160","eolDate":"2022-01-09"},{"agent":"dotnet","date":"2018-12-17","downloadLink":null,"version":"8.11.157.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes an issue where stack traces for custom errors outside a transaction were not visible in the Error Analytics UI page. Fixes an issue with auto-instrumenting MongoDB driver calls involving non-public collection types. Fixes an issue with reporting the same transaction multiple times. New Features Improved performance when serializing metrics prior to sending to New Relic. Improved SQL-related database instrumentation performance. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8111570","eolDate":"2021-12-17"},{"agent":"dotnet","date":"2018-11-29","downloadLink":null,"version":"8.10.51.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes a bug in SQL-related database instrumentation that potentially causes a CPU spike. This bug appeared in the agent version 8.9.130. New Features [.NET Core]  Adds support for .NET Core 2.2. Adds support for ASP.NET Core 2.2. Improves the performance of cross application tracing. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-810510","eolDate":"2021-11-29"},{"agent":"dotnet","date":"2018-03-07","downloadLink":null,"version":"8.0.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Adds stripExceptionMessages configuration option to the newrelic.config file. When enabled, this will remove error messages from errors that are reported to New Relic. This is the same behavior as having High-security mode enabled but can be used without High-security mode. The default value for this setting is false. Fixes Security Bulletin NR18-07 : The agent will no longer run explain plans on MySQL queries that have multiple statements. Other Changes In order to increase security, disabling agent HTTPS communication via the service SSL configuration is no longer allowed. WCF service parameters are now captured as request.parameters.* attributes and are no longer sent as service.request.* attributes. Minimum version required for use in EU Datacenter. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-8000","eolDate":"2021-03-07"},{"agent":"dotnet","date":"2018-02-20","downloadLink":null,"version":"7.1.229.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Improved metadata collection for cloud providers. The agent now collects additional metadata when running in AWS, GCP, and Azure. This information is used to provide an enhanced experience when the agent is deployed on those platforms. Fixes Fixed an issue where transactions could be dropped when they included datastore segments and the following exception was logged: NewRelic ERROR: An exception occurred while doing some background work: System.NullReferenceException: Object reference not set to an instance of an object. Fixed an issue where SOAP instrumentation would report System.Reflection.TargetInvocationException errors when a more specific error existed. Inner exceptions will now be reported when they exist. Deprecation Warnings The follow items are considered deprecated and will be removed with the upcoming 8.x major release: Disabling agent HTTPS communication via the service SSL configuration will no longer be allowed starting in 8.x versions of the agent. WCF service parameters will no longer be sent as service.request.* attributes starting in 8.x versions of the agent. These parameters will be sent in the form request.parameters.*. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-712290","eolDate":"2021-02-20"},{"agent":"dotnet","date":"2018-01-22","downloadLink":null,"version":"7.0.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Modifying custom instrumentation XML files can now be performed without having to restart the monitored application. Instrumentation updates will be applied ‘dynamically’ at runtime. This feature required functionality provided by new APIs introduced in .NET Framework 4.5 and newer, which this release also addresses (see ‘Framework Support’ section below). Fixes Security Bulletin NR18-04 : Fixes issue where error messages were not fully being filtered out of error traces and error events when High-security mode was enabled. Fixed an issue with automatic browser monitoring which could cause a stack overflow exception. For custom instrumentation, the metricName parameter will be honored without needing to set transactionNamingPriority. The scriptable installer will now successfully install and uninstall in scenarios where there is a space in the path to the installation files. Framework Support This release of the agent removes support for .NET Framework versions earlier than 4.5. See our community post  about this from November of last year, for more details. This is not an end of life for the 6.x agents (that support older .NET Frameworks), which will continue to work and report into New Relic. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-7020","eolDate":"2021-01-22"},{"agent":"dotnet","date":"2017-03-16","downloadLink":null,"version":"6.9.62.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes a bug where a SerializationException message is generated in New Relic log during monitoring of asychronous calls. Resolved issue where newrelic.config changes were not being picked up by the agent. Upgrading For upgrade instructions, see Upgrade the .NET agent. If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-69620","eolDate":"2020-03-16"},{"agent":"dotnet","date":"2017-03-02","downloadLink":null,"version":"6.8.172.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features With this release, the agent reports error analytic events. The event type is called TransactionError, and it powers the Error Analytics in APM  feature. The error events are also available through New Relic Insights . For applications with high volume, low latency characteristics, performance has been improved resulting in lower agent overhead and greater application throughput. Performance improvements, related to the capturing of slow transaction traces, have been made to the agent which should result in less CPU overhead. Fixes A bug was fixed which could cause the agent to shut down immediately at startup if a specific network error was encountered. The agent would then not restart until the application was restarted. The agent now retries network connection attempts indefinitely at startup until success is achieved, in all cases. Upgrading For upgrade instructions, see Upgrade the .NET agent. If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-681720","eolDate":"2020-03-02"},{"agent":"dotnet","date":"2017-01-25","downloadLink":null,"version":"6.7.67.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added instrumentation for RabbitMQ client versions 3.5 and above. For more information on which RabbitMQ operations are instrumented, see: Compatibility and requirements for the .NET agent . Added instrumentation for Couchbase client versions 2.x. For more information on which Couchbase operations are instrumented, see: Compatibility and requirements for the .NET agent . Fixes Fixed a bug where MS SQL Server instrumentation would generate exceptions and disable itself when a connection string contained a port number. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-67670","eolDate":"2020-01-25"},{"agent":"dotnet","date":"2017-01-12","downloadLink":null,"version":"6.6.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes an issue where query string parameters of a request's referrer URL get sent to APM when they should not be. For more information see the security bulletin https://docs.newrelic.com/docs/accounts-partnerships/accounts/security-b... The Status Monitor now verifies that the application link points to the New Relic domain before loading the URI in the browser, when the user selects the 'View application in New Relic' button in the Status Monitor. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-6650","eolDate":"2020-01-12"},{"agent":"dotnet","date":"2017-01-05","downloadLink":null,"version":"6.5.29.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features The agent now collects datastore instance information for Microsoft SQL Server, MySQL, PostGreSQL, Oracle, DB2, and Redis. This information is displayed in transaction traces and slow query traces. Datastore instance details are captured by default. For more information, visit https://docs.newrelic.com/docs/apm/applications-menu/features/analyze-da... SQL trace identifiers now use an 8-byte value instead of a 4-byte value so that Data Loss Prevention monitors do not interpret the value as a 9-digit Social Security Number. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-65290","eolDate":"2020-01-05"},{"agent":"dotnet","date":"2016-12-19","downloadLink":null,"version":"6.4.21.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Transaction events and PageView events now include a common attribute, nr.tripId, which can be used to correlate between them in data returned by Insights. This allows, for example, the browser page load time information and the server page serve time for a web application to be considered together rather than separately. A new, scriptable, installer is now available for the .NET Agent. This new installer makes it easier to perform unattended installations of the agent. This installer does not require .NET 3.5. If it is used to install the agent on a 64-bit machine, then both the 32-bit and 64-bit applications will be instrumented. The existing MSI installer is still recommended if you prefer an interactive installation process. For details, see: https://docs.newrelic.com/docs/agents/net-agent/installation-configurati... . Fixes Fix an issue where the agent imposes a limitation on throughput for applications using datastores for which instance information is not currently supported. Fixed a bug where the database name was not being captured from Microsoft SQL Server connections for the purposes of datastore instance reporting. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-64210","eolDate":"2019-12-19"},{"agent":"dotnet","date":"2016-11-09","downloadLink":null,"version":"6.3.123.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed an issue where the agent was not sending data to New Relic upon exit from a very short running application. Fixed a bug where parameterized SQL queries might cause an incorrect explain plan to be generated. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-631230","eolDate":"2019-11-09"},{"agent":"dotnet","date":"2021-01-28","downloadLink":"https://download.newrelic.com/dot_net_agent/6.x_release/","version":"6.27.0.0","features":["Continue to support .NET Framework 4.5 and below"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes The 6.x agent supports legacy frameworks (.NET version 4.5 and lower). If you are on .NET version 4.5 or higher, or if you are on .NET Core, use the 8.x or higher agent versions. Download URLs Download the appropriate release for your New Relic .NET agent: .NET Framework New Features CI/Deployment moved to GitHub Actions This release is functionally identical to version 6.26.0. We have migrated our CI and deployment process for the 6.x agent to GitHub Actions, and this release validates that this process is working correctly. There is no need to upgrade from 6.26.0 to 6.27.0. Support statement New Relic recommends staying current with the latest 6.x version. The .NET Agent 6.x updates include only security-related fixes. Active development of features and other bug fixes is no longer supported. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-62700","eolDate":"2029-01-09"},{"agent":"dotnet","date":"2020-09-15","downloadLink":"https://download.newrelic.com/dot_net_agent/6.x_release/","version":"6.26.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The 6.x agent supports legacy frameworks (.NET version 4.5 and lower). If you are on .NET version 4.5 or higher, or if you are on .NET Core, use the 8.x agent versions. Download URLs Download the appropriate release for your New Relic .NET agent: .NET Framework New Features The .NET Agent is now open source! The New Relic .NET agent is now open source! Now you can view the source code to help with troubleshooting, observe the project roadmap, and file issues directly in this repository. We are now using the Apache 2 license . See our Contributing guide  and Code of Conduct  for details on contributing! SSL Required In order to increase security, disabling agent HTTPS communication via the service SSL configuration is no longer supported. All communication with New Relic services will occur via SSL. EU Data Center Support Adds support for communicating with New Relic's EU Data Center. Please review our docs site  for further information. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-62600","eolDate":"2029-01-09"},{"agent":"dotnet","date":"2020-01-15","downloadLink":null,"version":"6.25.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"This is a security-only release for the 6.x agents that support legacy frameworks (.NET version 4.5 and lower). If you are on .NET version 4.5 or higher, or if you are on .NET Core, use the 8.x or later agent versions. Fixes Fixes security vulnerability NR20-01  which may cause SQL parameter values to appear in the agent log file when the logging level is set to Debug or Finest and the calling application supplies SQL parameters without a @ prefix. Fixes an issue where Explain Plans are not generated for database commands with parameters that do not have the @ prefix on the name. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-62500","eolDate":"2023-01-15"},{"agent":"dotnet","date":"2019-08-26","downloadLink":"https://download.newrelic.com/dot_net_agent/6.x_release/","version":"6.24.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This is a security-only release for the 6.x agents that support legacy frameworks (.NET version 4.5 and lower). If you are on .NET version 4.5 or higher, or if you are on .NET Core, use the 7.x or later agent versions. Fixes Resolves security issue where a manually constructed SQL stored procedure invocation may cause sensitive data to be captured in metric names. See Security Bulletin NR19-05 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-62400","eolDate":"2022-08-26"},{"agent":"dotnet","date":"2019-04-22","downloadLink":"https://download.newrelic.com/dot_net_agent/6.x_release/","version":"6.22.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This is a security-only release for the 6.x agents that support legacy frameworks (.NET version 4.5 and lower). If you are on .NET version 4.5 and higher or .NET Core, the 7.x or later versions of the agent should be used. Fixes Resolved security issue with how SQL Server handles escaping which could lead to a failure to correctly obfuscate SQL statements. See Security Bulletin NR19-03 . Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-62300","eolDate":"2022-04-22"},{"agent":"dotnet","date":"2016-10-13","downloadLink":null,"version":"6.2.26.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added support for IBM DB2 including slow query support. You'll see relevant breakdowns in the overview chart, entries in the Databases tab, and segments in transaction traces. Fixes The enabled attribute of the transactionTracer, when set to false, should disable all transaction trace output. This has been fixed in the .NET agent version 6.2.26.0 Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-62260","eolDate":"2019-10-13"},{"agent":"dotnet","date":"2018-03-07","downloadLink":null,"version":"6.22.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Security Bulletin NR18-07 : The agent will no longer run explain plans on MySQL queries which have multiple statements. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-62200","eolDate":"2021-03-07"},{"agent":"dotnet","date":"2018-02-08","downloadLink":null,"version":"6.21.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Security Bulletin NR18-04 : Fixes issue where error messages were not fully being filtered out of error traces and error events when High-security mode was enabled. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-62100","eolDate":"2021-02-08"},{"agent":"dotnet","date":"2017-12-18","downloadLink":null,"version":"6.20.166.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features The request URI for a web transaction will now be included as an attribute of transaction events and error events. The New Relic .NET Status Monitor has been retired and is no longer included in the install. The replacement tool is New Relic Diagnostics . To download the most recent version, select the link in the New Relic Diagnostics documentation . Fixes Security Bulletin NR17-06 : Fixes issue where query parameters were being included in the URL property of transaction trace segments for external calls (uses of System.Net.HttpClient, System.Net.WebRequest, or third-party libraries which are built on top of those). Query parameters will no longer be included in transaction trace segments. Transaction names will be rolled up for web transactions resulting in a 400 or 500 level HTTP status code and a higher priority name has not been set. This helps prevent metric grouping issues . Fixed error that could result in the one time loss of a metric and/or transaction for an instrumentation point at the start of monitoring an application. \"...NewRelic ERROR: Tracer invocation error: System.ArgumentException: An item with the same key has already been added. Key: ...\" Minor log level adjustments in the profiler logging. Suppresses benign error Failed to tokenize method signature: class System.Reflection.Assembly System.CannotUnloadAppDomainException::LoadAssemblyOrThrow(string) [.NET Core 2.0]  For .NET Core agent users on Linux, this release fixes a problem with the run.sh convenience script in combination with a custom installation path. [.NET Framework]  Fixes issue resulting in SerializationExceptions when using .Net Remoting. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-6201660","eolDate":"2020-12-18"},{"agent":"dotnet","date":"2017-11-30","downloadLink":null,"version":"6.19.330.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Relic Agent for .NET Core 2.0 GA Highlights Windows and Linux support, including Azure App Services and Docker Automatic instrumentation for ASP.NET Core applications running on Kestrel External calls via HttpClient Database instrumentation for System.Data.SqlClient, Npgsql, and MySql.Data Custom instrumentation via XML and transaction/trace attributes NewRelic.Agent.Api support For a more detailed list, see the compatibility documentation . The .NET Core 2.0 agent is a separate install and can live side-by-side on the same server as the .NET Framework agent. For installation information, follow the procedures for your operating system as applicable: Windows Linux Docker Azure App Services New Shared Features Database instrumentation performance has been improved. Explain plans are no longer captured by default for supported database systems: Microsoft SQL Server and MySQL. Explain plans can be enabled via configuration . Updating the Agent Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-6193300","eolDate":"2020-11-30"},{"agent":"dotnet","date":"2017-11-02","downloadLink":null,"version":"6.18.139.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features The agent now supports running in FIPS compliance mode. Fixes Fixed an issue that caused some transactions to report start time in the server's local time zone instead of UTC. Additional bug fixes to remedy a SerializationException caused by the agent. Upgrading Follow standard procedures to upgrade the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-6181390","eolDate":"2020-11-02"},{"agent":"dotnet","date":"2017-10-03","downloadLink":null,"version":"6.17.387.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Adds support for RestSharp library. The Agent can now instrument async and non-async methods from a RestSharp client. For supported methods, please visit here . The application name reported to New Relic APM can now be set by defining the NEW_RELIC_APP_NAME environment variable. Fixes Fixed some situations where SerializationException occurs in the agent log file. The injection of Browser Monitor JavaScript directly above the body tag on a page should occur less often. Fixes issue where datastore instance information would not be reported for some NpgsqlCommand async calls. Fixed remaining cases where 9-digit SQL trace identifiers were generated, failing Data Loss Prevention monitors which interpret the value as a Social Security Number. Upgrading Follow standard procedures to upgrade the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-6173870","eolDate":"2020-10-03"},{"agent":"dotnet","date":"2017-08-28","downloadLink":null,"version":"6.16.178.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Custom instrumentation can now be declared by applying the agent API's new Transaction and Trace attributes to methods. Using the Transaction attribute, transactions can be marked as Web vs. Non-Web. For more information, see Custom instrumentation via attributes . Fixes Fixes bug preventing instrumented apps from shutting down due to Profiler failure to detach. Upgrading Follow standard procedures to upgrade the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-6161780","eolDate":"2020-08-28"},{"agent":"dotnet","date":"2017-08-03","downloadLink":null,"version":"6.15.202.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Adds instrumentation for OWIN hosted Web API applications on .NET framework using Microsoft.Owin.Host.HttpListener versions 3.* Instrumentation includes async-await support. Adds async-await support for OWIN hosted Web API applications on .NET framework using Microsoft.Owin.Host.HttpListener versions 2.*. Fixes Fixed an issue where SQL instrumentation could raise exceptions and cause it to shutdown. Error traces now include the full stack trace, including any inner exceptions. Upgrading Follow standard procedures to upgrade the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-6152020","eolDate":"2020-08-03"},{"agent":"dotnet","date":"2016-09-29","downloadLink":null,"version":"6.1.48.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added ability to configure the use of Gzip compression instead of Deflate (the default) when sending data to New Relic. This can be useful in cases where DLP software requires Gzip compression for verification. Added ability to configure the use of PUT instead of POST (the default) for sending data to New Relic. This can be useful in cases where DLP software requires PUT for verification. Fixes Fixed issue where the Database Queries tab  would not appear for relevant transaction traces in APM. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-61480","eolDate":"2019-09-29"},{"agent":"dotnet","date":"2017-07-12","downloadLink":null,"version":"6.14.209.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Performance improvements when slowSQL is enabled, particularly for apps with lots of slow SQL queries. Fixes Fixed an issue that was preventing the proper setting of Key Transaction Apdex scores based on their configured ApdexT values. Fixed an issue preventing the collection of transaction traces for Key Transactions based on their configured ApdexT values. Upgrading Follow standard procedures to upgrade the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-6142090","eolDate":"2020-07-12"},{"agent":"dotnet","date":"2017-06-15","downloadLink":null,"version":"6.13.366.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Agent overhead is reduced for transactions composed of an unusually large number of small activities. Fixes Enhanced low-level logging to improve supportability. Fixed a problem with new installs using the Thin Installer where false permission errors could be reported. Upgrading Follow standard procedures to upgrade the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-6133660","eolDate":"2020-06-15"},{"agent":"dotnet","date":"2017-05-24","downloadLink":null,"version":"6.12.71.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes In some cases, the trace breakdown table overreported segment times. This happened when these three conditions were met, 1. instrumentation occurred through custom XML files, 2. the segment name was overridden, and 3. the segment contained child segments. Upgrading Follow standard procedures to upgrade the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-612710","eolDate":"2020-05-24"},{"agent":"dotnet","date":"2017-05-17","downloadLink":null,"version":"6.12.64.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed an issue preventing injection of a mscorlib reference into every module. Upgrading Follow standard procedures to upgrade the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-612640","eolDate":"2020-05-17"},{"agent":"dotnet","date":"2017-05-11","downloadLink":null,"version":"6.12.61.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features The .NET agent no longer supports Windows Server 2003. Applications running on Windows Server 2003 will be required to use .NET agent version 6.11 or lower. For more information, get support at support.newrelic.com  or download the agent at https://download.newrelic.com/ Reduced overhead of the agent for transactions that contain many segments. Reduced performance overhead for instrumented methods. Low latency, high-throughput applications may also see a reduction in CPU overhead. Reduced the overhead associated with method JITs. This will reduce the overall startup time and memory footprint of instrumented applications. Fixes Methods associated with wrappers that have been disabled due to too many exceptions are no longer instrumented by the default wrapper. The previous behavior could result in orphaned metrics and a potential degradation in performance. Upgrading Follow standard procedures to upgrade the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-612610","eolDate":"2020-05-11"},{"agent":"dotnet","date":"2017-05-04","downloadLink":"https://download.newrelic.com/dot_net_agent/server2003_final/","version":" 6.11.613.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features A new configuration option to supply a proxy URI path has been added to the newrelic.config file. See proxy-uripath . Fixes Resolved issue where service.request parameters, if present, were being transmitted to New Relic as part of an error analytics event. Fixed issue that could cause a SerializationException and cause metrics to be dropped. Fixed bug that would cause performance degradation for deeply nested segments. Fixes issue where scoped metrics would be dropped from an initial custom transaction when a second custom transaction was created. Impacts transaction created using the BackgroundThreadTracerFactory or the OtherTransactionWrapper via XML. Setting slowSql in newrelic.config to 'false' will now turn off slow SQL traces in the agent. This setting defaults to true. Server configuration values for this setting will override the value in the newrelic.config file. Removed the generation of unscoped metrics in cases where a transaction was not available. The generation of these metrics has been found to have a noticeable negative performance impact, particularly to low-latency/high-throughput applications. This impact typically shows up as a drop in throughput and higher CPU overhead. The vast majority of these metrics are not visible unless added to a custom dashboard. Datastore and External metrics, however, were visible on their respective pages and will no longer be displayed unless associated with a transaction. Fixed an issue when end-user monitoring is enabled that could cause some UTF-8 characters to get corrupted. The .NET agent now sends up the databaseDuration and externalDuration attributes when the value is 0. Upgrading Follow standard procedures to upgrade the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-6116130","eolDate":"2020-05-04"},{"agent":"dotnet","date":"2017-04-05","downloadLink":null,"version":" 6.10.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed issue where \"Query plan threshold\" from server settings was being incorrectly interpreted. This caused a spike in SQL traces as well as explain plan executions for clients using server configuration. Fixed a potential memory leak when an update to agent configuration is performed. Upgrading Follow standard procedures to upgrade the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-61010","eolDate":"2020-04-05"},{"agent":"dotnet","date":"2016-09-14","downloadLink":null,"version":"6.0.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Async support in .NET. The .NET agent now provides out-of-the-box asynchronous framework instrumentation. With the standard async-await pattern, as introduced in .NET 4.5, calls to async methods can return while work being done in the called method is still in progress. For supported libraries  and methods monitored with async custom instrumentation , the .NET agent observes this in-progress asynchronous work and waits for it to complete before recording timings. To take full advantage of features in this release please see this document . Fixes Fixed method segment naming for transaction traces to ensure consistency. For previous versions of the agent with async mode enabled, some method segments in transaction traces had inconsistent categories and different method formatting. Fixed these to make them consistent in async supported agent. Category: DotNet, Slowest components: Type.Method(). Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-6000","eolDate":"2019-09-14"},{"agent":"dotnet","date":"2015-11-05","downloadLink":null,"version":"5.9.74.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes an issue where if a customer was using the default proxy and not specifying one in the New Relic configuration for the Agent the default would not be used potentially causing HTTP status code 504 to be thrown when communicating with the New Relic collectors. Fixes an issue where cross application tracing would slow down in environments using WFC with extremely high throughput. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-59740","eolDate":"2018-11-05"},{"agent":"dotnet","date":"2015-10-14","downloadLink":null,"version":"5.8.28.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes a bug where the .NET Agent was not handling exceptions coming from HttpRequest.Path and HttpRequest.Url properties. Because the exception was unhandled users would see a System.Web.HttprequestValidationException in their log files and in some cases could miss transactions being reported. Fixes a bug where the .NET Agent was throwing null reference exceptions when tracing some SQL commands where there was no transaction available. Fixes a bug where the .NET Agent was reporting StackExchange.Redis call times incorrectly. Now, the agent reports the correct call times for apps that use StackExchange.Redis synchronously. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-58280","eolDate":"2018-10-14"},{"agent":"dotnet","date":"2015-10-05","downloadLink":null,"version":"5.7.17.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed a bug that caused certain frameworks (such as EpiServer CMS) to throw exceptions when trying to resolve a reference to JetBrains. Fixed a bug that caused ASMX web service exceptions to not be noticed. This would result in missing some error details, such as stack traces. Fixed a bug where sometimes transactions will not be reported if the HttpClient class is used during that transaction. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-57170","eolDate":"2018-10-05"},{"agent":"dotnet","date":"2015-09-24","downloadLink":null,"version":"5.6.53.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed a bug that prevented self-hosted WCF applications from automatically creating Traced Errors. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-56530","eolDate":"2018-09-24"},{"agent":"dotnet","date":"2015-09-14","downloadLink":null,"version":"5.5.52.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added StackExchange.Redis framework support. The .Net agent now records time spent making StackExchange.Redis API calls, which will appear as Datastore metrics and Transaction Trace segments in New Relic APM. Fixes Fixed a bug that cause Automatic Browser Monitoring to cause problems on web pages that have no HEAD tag and also contain the text \"<BODY\" inside of an inline script. Improved agent error reporting for applications using WebAPI v1 in unsupported configurations. A warning will be displayed in the agent log (during agent startup) if an application is using an unsupported configuration. Azure KUDU (scm) sites were being instrumented by the .NET Agent due to a change in the way Azure is naming application pools. We have updated our logic to match the new application pool naming so these sites will be ignored by the agent. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-55520","eolDate":"2018-09-14"},{"agent":"dotnet","date":"2015-08-27","downloadLink":null,"version":"5.4.16.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added ServiceStack.Redis v3.x and v4.x framework support. The .Net agent now wraps time spent making ServiceStack.Redis API calls, which will appear as Datastore metrics and Transaction Trace segments in New Relic APM. Fixes Fixed a bug that caused web transaction data to be lost if the request contained an invalid \"Referer\" HTTP header. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-54160","eolDate":"2018-08-27"},{"agent":"dotnet","date":"2015-08-20","downloadLink":null,"version":"5.3.90.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes a bug which caused the .NET Agent to stop reporting intermittently due to an exception raised within the .NET Framework and caught by the Agent. Fixes an unhandled System.ObjectDisposedException in the agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-53900","eolDate":"2018-08-20"},{"agent":"dotnet","date":"2015-07-22","downloadLink":null,"version":"5.2.87.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Web requests for static resources which are handled by System.Web.Optimization will be named with the requested URL instead of the unmapped route parameters (some previously were named {controller}/{action}/{id}).","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-52870","eolDate":"2018-07-22"},{"agent":"dotnet","date":"2016-08-31","downloadLink":null,"version":"5.22.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Minor performance improvement with cross application tracing . Fixes Fixed a spelling error in NewRelic.Providers.Wrapper.WebServices.Instrumentation.xml. Removed duplicate instrumentation out of CoreInstrumentation.xml. Improved transaction handling for rare cases where a segment cannot be associated with its parent. This scenario can occur in applications with complex threading architectures and would previously cause the entire transaction to be dropped. The transaction will now be retained but the orphaned segment and children will be excluded. A warning log message including specifics will be generated for further troubleshooting. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-52260","eolDate":"2019-08-31"},{"agent":"dotnet","date":"2016-08-23","downloadLink":null,"version":"5.21.74.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Async mode  - New Requirement: Await-friendly asynchronous pipeline introduced in ASP.NET 4.5 must be turned on in your web config for the instrumentation of async methods. Without this configuration, async / await is undefined in ASP.NET and could result in intermittent drops of metrics or potential deadlocks. You may stop seeing some async metrics for your application unless you update its web.config file, as documented here: https://docs.newrelic.com/docs/agents/net-agent/troubleshooting/missing-... . For a brief description of this configuration, see the section here: https://blogs.msdn.microsoft.com/webdev/2012/11/19/all-about-httpruntime... Async mode : Fixed issue where High-security mode was filtering some attributes that are not sensitive. Async mode : Fixed an issue that could lead to missing external segments in some async transactions. Async mode : Fixed an issue in .NET 4.0 and older where in certain instances call stacks may not accurately get tracked due to ASP.NET thread agility. Async mode : Fixed issue where calling AgentApi.GetBrowserTimingHeader() did not prevent subsequent calls in the same transaction or auto browser injection from injecting duplicate JavaScript. Async mode : Fixed issue where setting browser monitoring auto instrument to false would prevent NewRelic.Api.Agent.NewRelic.GetBrowserTimingHeader() from returning the header for manual injection. Enhanced the instrumentation for NServiceBus (receive side) so that when a service hosted by NServiceBus throws an unhandled exception while processing a service bus request, the New Relic Agent captures information about the error and generates an error trace. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-521740","eolDate":"2019-08-23"},{"agent":"dotnet","date":"2016-06-15","downloadLink":null,"version":"5.20.61.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Async mode : Added System.Web.Script.Services.WebServiceMethodData support to .NET Async mode. All transactions named from this instrumentation will now use the more appropriate naming format of: WebService/{ServiceClassName}/{MethodName}. Async mode : Added OpenRasta support to .NET Async mode. This instrumentation now appropriately names transactions using the {Controller}/{Action} format. Moved System.Web.UI.Page.PerformPreInit, System.Web.Compilation.AssemblyBuilder.Compile and System.Web.Compilation.BuildManager.CompileWebFile instrumentation configuration elements from the CoreInstrumentation.xml file to the Asp35.Instrumentation.xml file. Fixes Async mode : Resolved an issue where the agent incorrectly handled HttpClient async requests that timed-out or were manually cancelled. These would show up as wrapper errors. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-520610","eolDate":"2019-06-15"},{"agent":"dotnet","date":"2016-04-26","downloadLink":null,"version":"5.19.47.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Async mode : Added support for the metricName and transactionNamingPriority custom instrumentation options when async mode is enabled. Async mode: Added support for Castle MonoRail 2.x when async mode is enabled. Note that MonoRail transactions previously named WebTransaction/DotNetController/{controller}/{action} will be renamed to WebTransaction/MonoRail/{controller}/{action} when async mode is enabled. Async mode: Added support for legacy ScriptHandlerFactory instrumentation when async mode is enabled. Removes instrumentation for deprecated methods in Umbraco. The default instrumentation for ASP .NET MVC or ASP .NET Web API will now be used by the agent in its place. Fixes Async mode: Fixed an issue where the agent would not clean up SQL connections after explain plan execution when async mode is enabled. Async mode: Fixed a bug which would cause a SerializationException to occur when async mode is enabled which could result in an app crash. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-519470","eolDate":"2019-04-26"},{"agent":"dotnet","date":"2016-04-13","downloadLink":null,"version":"5.18.36.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Async mode : Instrumentation of NServiceBus is now enabled when the AsyncMode flag is true. Async mode: Added support for Microsoft Message Queue (MSMQ) instrumentation when Async mode is enabled. Async mode: Microsoft Enterprise Library officially supported when Async mode is enabled. Fixes Fixed a bug where ASP.NET 4.5+ applications would not get transactions for requests that had invalid query stings (such as \"myPage.aspx?test=\"). Fixed an issue where metrics from database calls using Enterprise Library would display as from vendor \"Other.\" The metrics should now show the appropriate supported vendor (Oracle, MsSql, etc.). Fixed a bug that prevented SqlCommand.ExecuteNonQuery commands from being instrumented with the default instrumentation xml files. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-518360","eolDate":"2019-04-13"},{"agent":"dotnet","date":"2016-04-04","downloadLink":null,"version":"5.17.59.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features New Features Added support for Stack Exchange Redis strongly named assembly: StackExchange.Redis.StrongName. Added support for the \"CustomSegmentTracerFactory\" custom instrumentation option. See docs  for example usage. Async mode : Added support for NpgsqlCommand asynchronous methods (such as ExecuteReaderAsync) when the agent is in Async mode. Async mode: Explain plans for MS SQL and MySQL commands are now available when the agent is in Async mode. Fixes Async mode: Fixed a bug that prevented SQL activity from being recorded in transactions. Fixed a bug where the incorrect namespace of the default asynchronous wrapper was used. The incorrect name was \"NewRelic.Agent.Core.Wrapper.DefaultWrapperAsync\" and is now \"NewRelic.Providers.Wrapper.CustomInstrumentationAsync.DefaultWrapperAsync\". Any customers that had created a custom instrumentation file and put the incorrect name in it as a workaround should change it to the correct name. Duplicate custom parameters will now be logged as Debug level, providing a minor performance improvement. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-517590","eolDate":"2019-04-04"},{"agent":"dotnet","date":"2015-07-06","downloadLink":null,"version":"5.1.72.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Transactions using MVC attribute routing will show the correct action name instead of \"Unknown Action\".","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-51720","eolDate":"2018-07-06"},{"agent":"dotnet","date":"2016-03-11","downloadLink":null,"version":"5.16.71.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Async mode : Custom instrumentation is now supported for both synchronous and asynchronous methods when async mode is enabled, however; the metricName and transactionNamePriority elements will not be respected. This is coming in a future release. Please see our custom instrumentation documentation  for details. Fixes Changes the log messages for when a wrapper / method combination needs to be shut down. The new message provides more information and clarity around the shutdown event. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-516710","eolDate":"2019-03-11"},{"agent":"dotnet","date":"2016-02-24","downloadLink":null,"version":"5.15.64.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Async mode: Added support for SqlCommand method ExecuteReaderAsync, ExecuteScalarAsync, ExecuteNonQueryAsync, and ExecuteXmlReaderAsync. Async Mode: Added support for SQL Traces on slow SQL commands when the agent is in async mode. Async mode: Adds support for synthetic transaction tracing when the agent is in async mode. Async Mode: Added instrumentation for System.Data.SqlClient.SqlDataReader ReadAsync and NextResultAsync methods. Note that, for performance reasons, this instrumentation is disabled by default in the SqlAsync instrumentation xml file. Fixes Fixed a bug where the agent erroneously treated HTTP headers as being case-sensitive, causing CAT to not work under certain conditions. Fixed a bug where the agent rejected custom events if any attribute had a null value. Async mode: Fixed a bug that caused some datastore activity to be missed. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-515640","eolDate":"2019-02-24"},{"agent":"dotnet","date":"2016-02-09","downloadLink":null,"version":"5.14.43.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Async Mode: Added Agent API support. Async mode: Instrumentation for synchronous SQL commands is available when the agent is in async mode. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-514430","eolDate":"2019-02-09"},{"agent":"dotnet","date":"2016-01-21","downloadLink":null,"version":"5.13.30.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Async mode: The .NET agent now reports CPU and Memory usage metrics which will show up on the APM Application Overview page. Async mode: Basic support for Redis and MongoDB are available when the agent is in async mode. Fixes Fixed a bug that prevented Cross Application Tracing from working between Java and .NET applications. Fixed a bug where turning on High-security mode did not prevent custom events from being created via the agent API. For additional information regarding High-security mode, please refer to our public documentation: https://docs.newrelic.com/docs/accounts-partnerships/accounts/security/h... Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-513300","eolDate":"2019-01-21"},{"agent":"dotnet","date":"2016-01-07","downloadLink":null,"version":"5.12.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Async Mode: Added automatic Browser Monitoring support. Fixes Async mode: Fixed a bug where using HttpClient with a BaseAddress would result in transactions being lost or corrupted. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-512130","eolDate":"2019-01-07"},{"agent":"dotnet","date":"2015-12-16","downloadLink":null,"version":"5.11.53.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Async mode: The .NET agent now has an optional async mode which provides a look at the agent's asynchronous framework instrumentation as it becomes available. As of this release, asynchronous instrumentation for System.Net.Http.HttpClient and System.Net.HttpWebRequest are available when the agent is in async mode. Please note that activating async mode disables some functionality within the .NET agent. More details and instructions are available here: https://docs.newrelic.com/docs/agents/net-agent/features/async-mode-net Improvements Added new log for cases where the .NET Agent cannot inject Browser Agent Fixes Fixes an issue where intermittent connection issues would cause the Agent to shut down until the process was restarted. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-511530","eolDate":"2018-12-16"},{"agent":"dotnet","date":"2015-12-01","downloadLink":null,"version":"5.10.59.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed a bug where IIS applications using a classic pipeline app pool would sometimes not report transactions. Fixed a bug where clicking on the transaction name from an error trace would not take you to the correct transaction page. Fixed an Agent API bug that caused the IgnoreApdex to not actually ignore a transaction for apdex calculations. Fixed a bug that would sometimes cause transaction data to be lost if the Cross Application Tracing feature was enabled. Fixed a bug that sometimes caused agent environment info to be incomplete. Fixed a bug where configuring the agent to ignore HTTP sub-status codes (such as 403.1) would result in an exception. Upgrading For upgrade instructions, see Upgrade the .NET agent . If you are upgrading from a particularly old agent, see Upgrading legacy .NET agents  for a list of major changes to the .NET agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-510590","eolDate":"2018-12-01"},{"agent":"dotnet","date":"2015-06-24","downloadLink":null,"version":"5.0.136.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Adds an API method for setting the name of the application reported to in New Relic at runtime. Adds a configuration option for stopping the agent from reporting automatically when the agent starts up. Adds an API method for telling the agent to start reporting at runtime. Fixes Fixes a bug where self-hosted WCF applications would not correctly report on the overview page. Fixes a bug where database calls and external calls in a background/async thread would result in a transaction named * showing up in the Other bucket. Fixes a bug where apdex was not reported for self-hosted WCF applications. Fixes a bug where API calls from an application that didn't have any instrumentation would not report any data. SQL object names are more accurately parsed. In particular, table names will be recognized with an expanded set of characters. The agent is able to parse table names with a variety of separator characters and formatting whitespace. For example, {Table1}, [ Table2 ], \"Table3\" and Table4. Known Issues If you are using WebAPI and targeting .NET Framework 4.0 then you may need to opt-in to a .NET Framework 4.5 bug fix in order to continue seeing web transactions! For more information, see WebAPI transactions are missing .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-501360","eolDate":"2018-06-24"},{"agent":"dotnet","date":"2015-05-20","downloadLink":null,"version":"4.6.29.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Improvements The .NET agent now provides an API for sending custom events  to New Relic Insights.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-46290","eolDate":"2018-05-20"},{"agent":"dotnet","date":"2015-05-14","downloadLink":null,"version":"4.5.90.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Fixed a bug that sometimes caused thread profiles to be empty.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-45900","eolDate":"2018-05-14"},{"agent":"dotnet","date":"2015-04-29","downloadLink":null,"version":"4.4.60.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Web transaction types (seen in tooltips) should now be more meaningful. When you mouse over a transaction, instead of showing Action  it will show ASP, MVC, WebAPI, WebService, WCF, etc. Upgrade Notes This improvement to transaction naming may impact the transaction names of existing metrics including Key Transactions, Alert on Anything metrics and Insights queries based on transaction names. These would need to be recreated with the new transaction name after the upgrade. Fixes The agent will now fallback to using the proxy configured for the executing user when talking to New Relic.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-44600","eolDate":"2018-04-29"},{"agent":"dotnet","date":"2015-04-16","downloadLink":null,"version":"4.3.123.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Non-web transactions can now report Apdex scores. This can be done by marking a non-web transaction as Key Transaction and setting its Apdex threshold to the desired time (in seconds). This allows monitoring and alerting based on this score as well as configuration of thresholds that make sense for long-running or faster background transactions. Fixes Fixed a bug that caused WebApi applications to intermittently throw exceptions under certain conditions. Fixed a bug that caused Browser Monitoring autoinjection to increase application memory usage. Fixed a bug where attempting to load newrelic.config  from web root on a network share would fail. Fixed RUM auto-injection for default pages in WebForms applications running on .NET 3.5 or lower in integrated pipeline mode. Fixed a bug where sometimes transaction events wouldn't be sent to Insights. Fixed a bug where sometimes error traces wouldn't be sent to APM. Thread profiles of .NET agent instrumented applications now only contain data in the Other  bucket.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-431230","eolDate":"2018-04-16"},{"agent":"dotnet","date":"2015-03-31","downloadLink":null,"version":"4.2.185.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Customers who use the MongoDB.Driver for .NET in their applications will start to see MongoDB-based transaction segments. Operations will include data querying, aggregation, index creation/retrieval, data insertion/update/removal and bulk write operations. MongoDB datastore transactions will appear in the Monitoring > Databases  APM page. The .NET agent uses the 1.10.0 version of the MongoDB Driver for .NET but will report instrumentation for applications using older versions of the driver. Provides support for NServiceBus instrumentation, which will appear as transaction segments containing Message Broker , the queue name and the action (such as Produce  or Consume ). Since NServiceBus can be used for inter-application communication, nodes will also appear within the Cross-Application Tracing map  in APM. This release supports NServiceBus 5.0 and later. Fixes Fixes a bug where WCF applications hosted in IIS with compatibility mode disabled would not receive any useful transaction traces. Fixes a bug where WCF applications hosted in IIS with compatibility mode disabled would see twice as much throughput and *.svc transactions. Fixes a bug where some frameworks (WCF, Umbraco, DotNetNuke, etc.) were not having their transactions named as they were in agent 3.x and instead were getting named by the route. Fixed a bug where server-side redirects would cause transactions to be dropped. Fixes a bug where default page redirection in IIS classic pipeline mode would cause the redirection to fail and a 404 to occur instead. Fixes a bug where an exception could be thrown if the Content Type of an outgoing payload could not be parsed. Fixes an issue where the Azure Cloud Services NuGet package will not install on roles that are added as part of a second Cloud Service project. Fixes a bug where transactions would sometimes not show up in the UI. Notes There is a known issue in version 4.2.185.0 of the .NET agent which prevents auto-injection in certain specific cases. This issue only affects WebForms websites running in integrated pipeline mode, and only manifests when navigating to the website's root URL.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-421850","eolDate":"2018-03-31"},{"agent":"dotnet","date":"2015-03-18","downloadLink":null,"version":"4.1.136.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Fixes a bug that would break WebResources if a response filter was hooked up. This was caused by a bug in AssemblyResourceLoader (part of ASP.NET/WebForms ).","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-411360","eolDate":"2018-03-18"},{"agent":"dotnet","date":"2015-03-17","downloadLink":null,"version":"4.1.134.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Unified view for SQL database and NoSQL datastore products. For more information, see https://docs.newrelic.com/docs/apm/applications-menu/monitoring/databases-slow-queries-dashboard Fixes Non-IIS applications no longer use the process name as an application name unless no other name is provided. This brings non-IIS application naming in-line with IIS application naming and all of the same naming rules should apply. Fixes a bug where simple transactions wouldn't be available to insights for queries. This was most likely to occur with custom applications or WCF applications. Fixes a security issue where proxy credentials could be written to the agent log file if you supplied them in the hostname (e.g., user:password@proxy.com :1234). Fixed a bug that caused the .NET agent to corrupt some non-HTML resources if browser monitoring was enabled.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-411340","eolDate":"2018-03-17"},{"agent":"dotnet","date":"2015-03-12","downloadLink":null,"version":"4.0.146.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features ASP.NET, MVC, and Web API instrumentation has been greatly improved. We now time each of the lifecycle events to help diagnose problematic areas of the .NET lifecycle such as session state lock contention. MVC and WebAPI should now properly wrap the time spent in controller actions inside the proper segment. We should now see far more exceptions that occur in your application, with full stack traces. The caveat here is that your error rate may appear to spike after upgrading and you may need to add some additional configuration to ignore more errors (or adjust error rate thresholds). Fixes Fixed a bug where WebAPI exceptions didn't contain stack traces. Increases the number of places during the ASP.NET Lifecycle that New Relic API methods that modify the transaction (like SetTransactionName) can be used. Provides support for instrumentation of methods on generic class types. Fixed a bug that would sometimes cause IIS to get into a bad state under certain load conditions where it would stop serving requests. This could be identified by an exception from IIS around System.Web.HttpApplication.PipelineStepManager.ResumeSteps. Other MVC2 applications will no longer generate MVC-specific segments or have MVC route-based transaction names. Thread profiles will no longer put threads into the Web Requests thread bucket (the Other bucket will be used instead)","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-401460","eolDate":"2018-03-12"},{"agent":"dotnet","date":"2014-10-29","downloadLink":null,"version":"3.9.146.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Added support for agent-side creation of application labels and categories via newrelic.config  or the NEW_RELIC_LABELS environment variable. Labeling enables organization of applications with labels and categories. The APM UI will use these labels and categories to group, filter and organize all your applications in a meaningful way; this is particularly useful if you have many applications. For more information, see Labels and categories . Fixes Fixes a race condition that could lead to a small amount of missing data and in some rare cases, excessive CPU utilization. Most likely to occur with WCF applications under heavy load. Fixes a bug where turning on high-security mode and turning off SQL would result in receiving obfuscated SQL.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-391460","eolDate":"2017-10-29"},{"agent":"dotnet","date":"2014-10-01","downloadLink":null,"version":"3.8.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Disables automatic instrumentation of Microsoft Azure Websites SCM service site.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-3810","eolDate":"2017-10-01"},{"agent":"dotnet","date":"2014-09-25","downloadLink":null,"version":"3.7.135.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Improvements Adds functionality to the system tray application that will collate information commonly asked for by New Relic support and upload it to S3 when instructed to by the user. Response.status is now reported by default in the latest version of the .NET agent on all Insights Transaction events. Previously, this required a configuration change, but now the user simply has to update their agent to the latest version. Fixes Fixes a bug that would cause a failure to connect to New Relic when local high security was enabled and ssl was disabled. Now you will successfully connect with SSL in this scenario. Fixes a bug where ignoring a status code for error reporting would sometimes not work correctly and the error would still be reported. Fixes a bug where CPU usage sometimes increased with agent version 3.6.177. Fixed a bug where applications running older agents making requests of applications running newer agents would sometimes cause the application running the newer agent to drop the transaction.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-371350","eolDate":"2017-09-25"},{"agent":"dotnet","date":"2014-08-27","downloadLink":null,"version":"3.6.177.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features Flexible capturing of attributes You can now fine tune the attributes the .NET agent sends to New Relic. For more information, see .NET agent attributes Fixes Fixes a bug where external requests that occurred outside of a transaction were generating error traces when the response code from the external request was an error. Fixes a bug where environment wasn't showing up correctly in the New Relic UI.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-361770","eolDate":"2017-08-27"},{"agent":"dotnet","date":"2014-08-19","downloadLink":null,"version":"3.5.107.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features This release enhances cross application tracing with a visualization of the cross application calls that a specific Transaction Trace is involved in. The new visualization helps you spot bottlenecks in external services within Transaction Traces and gives you an end-to-end understanding of how the transaction trace is used by other applications and services. This leads to faster problem diagnosis and better collaboration across teams. All agents involved in the cross application communication must be upgraded to see the complete graph. You can view cross application traces from in the Transaction Trace drill-down. Fixes Fixes a problem where a transaction may not be correctly recorded if the application is using WCF services. In this case, one of two exception types may appear in the agent log file: a Null Reference Exception or an Object Disposed Exception.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-351070","eolDate":"2017-08-19"},{"agent":"dotnet","date":"2014-07-24","downloadLink":null,"version":"3.4.24.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features Provides visibility into Microsoft Message Queue (MSMQ) activity. Within a web transaction, e.g., you can now see whether a message has been sent to a queue, pulled off a queue, peeked at, or if a queue has been purged. Fixes Fixes a crash in the New Relic system tray application that would occur for some users on launch.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-34240","eolDate":"2017-07-24"},{"agent":"dotnet","date":"2014-07-11","downloadLink":null,"version":"3.3.38.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Improvements Agent-Side High Security Configuration See https://docs.newrelic.com/docs/subscriptions/high-security Added new local setting to enable high-security mode. If your account is set to high security in the New Relic UI, you must add the following to your local newrelic.config file under the configuration element: ... This setting is false by default. Without this property, the agent will stop collecting data when high security is enabled in the New Relic UI. When set to true, this setting has the following effects: Data will not be sent to New Relic unless the agent is using SSL. Raw SQL strings will never be gathered, regardless of the value of newrelic.transaction_tracer.record_sql. Request parameters will never be captured, regardless of the value of newrelic.capture_params. The following API functions will have no effect: AddCustomParameter, SetUserParameters. Fixes Fixes an issue where sometimes applications on the same host reporting to New Relic were not reporting as unique and distinct applications. Due to a rare DLL versioning issue, we did not release the NuGet package for Windows Azure Web Sites with our 3.2.113.0 version of the agent. We have fixed the issue and are once again releasing the NuGet package.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-33380","eolDate":"2017-07-11"},{"agent":"dotnet","date":"2014-06-30","downloadLink":null,"version":"3.2.113.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features Support for Windows Communication Foundation (WCF) now includes: self-hosted (i.e., hosted outside of IIS) services services hosted by IIS whether or not ASP.NET Compatibility Mode is used. service request parameters can be viewed in a transaction trace summary or in an error summary. By default, these parameters are not captured, but can be enabled and filtered in the newrelic.config file using a new parameter group named 'serverRequestParameters'. See the online documentation for more details. Note: This release is not currently supported for installation via the Azure Web Sites NuGet package. We will be updating that NuGet package at a later time.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-321130","eolDate":"2017-06-30"},{"agent":"dotnet","date":"2014-06-20","downloadLink":null,"version":"3.1.65.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Improvements The New Relic .NET Agent Status Monitor should now report more useful error messages for debugging problems. This will allow us to more rapidly act on bug/crash reports in the Status Monitor. Messages in the status monitor when checking installation or repairing installation have been improved to be less confusing. Fixes Improves exception reporting in MVC by reporting filtered exceptions. This resolves an issue where turning on custom error pages in an MVC application would cause you to only receive status code errors rather than exception errors. Please remember that you can ignore errors in New Relic either via API call or configuration! Fixes a bug where error reporting for transactions was not behaving correctly. You should once again see correct error counts for key transactions. Addresses a bug that impacted users who enabled request parameters in the configuration file AND had configured specific parameters to be ignored. For these customers, the ignored parameters were filtered when sent as requested attributes but were still included in the captured URL. Customers with request parameters disabled (the default configuration) or who did not specify any ignored parameters were not impacted by this bug. Fixes a bug where sometimes custom instrumentation wouldn't render correctly in the UI. This happened when the metricName in the custom instrumentation file wasn't prefixed with \"Custom/\". Now the \"Custom/\" prefix is added automatically if not provided in the file.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-31650","eolDate":"2017-06-20"},{"agent":"dotnet","date":"2015-02-19","downloadLink":null,"version":"3.12.140.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features The .Net Agent now reports Insights Transaction Events for transactions that are errors. New queryable attributes: errorType and errorMessage are reported on these events, providing a reliable way to filter out error transactions in your Insights queries. Fixes Fixes a bug where breakdown tables wouldn't include external calls.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-3121400","eolDate":"2018-02-19"},{"agent":"dotnet","date":"2015-01-26","downloadLink":null,"version":"3.11.296.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Fixes a bug where setting transaction trace threshold from the New Relic UI would cause it to revert to default. Fixes a bug where the cross application map would sometimes show the wrong color (apdex) line between nodes. Fixes a bug where the New Relic tray application would report IIS 7+ as not running if one of the application pools was stopped.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-3112960","eolDate":"2018-01-26"},{"agent":"dotnet","date":"2014-11-20","downloadLink":null,"version":"3.10.43.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features The .NET agent now gives you additional information for requests from synthetic monitors. More transaction traces and events give you a clearer look into how your application is performing around the world.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-310430","eolDate":"2017-11-20"},{"agent":"dotnet","date":"2014-05-29","downloadLink":null,"version":"3.0.79.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Improvements Adds instrumentation support for Oracle's ManagedDataAccess APIs. Now any applications using Oracle.ManagedDataAccess.Client methods will get database instrumentation for those method calls. Adds better support for Windows Communication Foundation applications that are hosted by IIS. Changed agent logs to use UTC timestamps instead of local server timestamps. This should allow us to resolve customer issues more quickly. Changes the agent to depend on .NET 3.5. Your application can still target .NET 2.0, but you must have .NET 3.5 installed on the computer the agent is executing on. Fixes Fixes an issue where the Agent was not respecting the server side enable error collection setting.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-30790","eolDate":"2017-05-29"},{"agent":"dotnet","date":"2013-07-24","downloadLink":null,"version":"2.9.135.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Fixed a bug where external request timing was showing up on the call to WriteHeaders instead of on the Stream Read. The Stream Read has been removed and WriteHeaders should correctly report as being fast. In their place you will now see all the time occurring inside a call to Stream GetResponse. Fixed a bug in external request counting that would result in the counts being too high. The Original Url custom parameter will now contain the correct value if the application had re-written the Url in the BeginRequest event handler of an HttpModule. Fixes an issue on Windows 2003/IIS 6 server where the New Relic Status Monitor was showing no reporting applications and an incorrect error message about IIS being in a stopped state in some cases where apps hosted on the machine were in fact reporting to New Relic. Fixed an issue where sometimes our usage of Log4Net would conflict with the user's usage of Log4Net. Fixed a bug that would cause some stack traces thrown in the user's application to be truncated. Moved some spammy log messages to debug level logging. New Features Improved cold startup time for user applications instrumented by New Relic. Added the ability to selectively include or exclude certain application pools from being monitored by New Relic. Improvements Improved error logging of API method calls. If you call an API method at an invalid time or you supply invalid parameters a warning will be logged to the New Relic .NET Agent log file. Changed startup logging location from the event log to log file on disk. Changed the agent configuration file from newrelic.xml to newrelic.config.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-291350","eolDate":"2016-07-24"},{"agent":"dotnet","date":"2013-06-21","downloadLink":null,"version":"2.8.134.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Fixed a very rare race condition that could cause a monitored application to get into a bad state and start consuming as much CPU as possible (across multiple threads). Fixed a bug that would sometimes cause a TypeLoadException when using the New Relic API. Fixed a crash that would occur if the agent failed to connect to our servers due to SSL issues when running under IIS7 integrated mode. New Features Adds a new utility (New Relic Status Monitor) that provides a quick way to give feedback on what the .net agent has instrumented just after installation. The tool also provides a quick way to diagnose and troubleshoot issues with instrumentation or with the agent that are normally obscured form the users view. Improvements Fixes an issue in the coreinstrumentation.xml file where an overload for Oracle.DataAccess.Client.OracleCommand.ExecuteReader was not getting instrumented.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-281340","eolDate":"2016-06-21"},{"agent":"dotnet","date":"2013-06-22","downloadLink":null,"version":"2.8.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This is an interim release which addresses performance issues by temporarily disabling some features. Known issues At times, the agent may not release database connections quickly when the code being instrumented does not properly dispose of connections. Connections may not be returned to the pool until the one minute harvest cycle is reached. The Status Monitor diagnostics tool has the following known issues: Does not function correctly for IIS6 installations and applications running under sites other than DefaultWebSite. Shows incorrect information for some sites. Shows no reporting applications and an incorrect error message about IIS being in a stopped state in some cases where apps hosted on the machine are in fact reporting to New Relic. The agent writes too many messages to the log at INFO level. This can result in log files growing too large and a possible CPU impact. Work-around: set logging level to warning or above. In some cases, the agent may display incorrect counts for external calls. The Original URL displayed in the UI is not correct if the application uses an HttpModule to rewrite the url. In some cases, the agent may inject browser monitoring code in the wrong section of the page. This can cause pages to render incorrectly. Work-around: disable browser monitoring via the API for pages experiencing this issue. The agent reads its config file more frequently than necessary causing a potential performance problem for apps with very high frequency, very fast transactions. Auto RUM may not inject appropriately on pages where the content-type has optional parameters. This can result in no browser monitoring functionality for these pages. Generic exceptions cannot be ignored in the UI. Future upgrades from 2.8 to newer releases may not remove the newrelic.xml file. This may require manual cleanup.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-2810","eolDate":"2016-06-22"},{"agent":"dotnet","date":"2013-05-16","downloadLink":null,"version":"2.7.60.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Fixes cleanup of Component Object Model (COM) registration. Fixes ability of agent to monitor partially-trusted .NET applications. Improvements Removes comments from the newrelic.xml file and provides a link to the living docs to provide more information on configuring the agent","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-27600","eolDate":"2016-05-16"},{"agent":"dotnet","date":"2013-05-10","downloadLink":null,"version":"2.6.54.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features Added ability to enable/disable various parameter information via agent configuration. This includes the default setting to not capture a username from the security principal associated with a web application. Fixes Fixes instances where the AgentEnabled setting was set to false and the NewRelic.Agent.IL.dll was not getting unloaded from the process. No code was ever executed from the module when the agent was disabled but the module needed to be unloaded so that the process would correctly reflect the actual modules that were being used. Fixes an issue where the user could not override the default naming of a transaction using the agent API.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-26540","eolDate":"2016-05-10"},{"agent":"dotnet","date":"2013-03-15","downloadLink":null,"version":"2.5.112.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features Adds a new API method that can be used to disable Auto or Manual Real User Monitoring (RUM) script injection on a per page basis. Simply call NewRelic.Api.Agent.NewRelic.DisableBrowserMonitoring(); in your view to disable RUM scripts for that page.See: https://newrelic.com/docs/dotnet/AgentApi  for more information. Improvements Adds Cross Application Tracing for web request calls that use System.Net.WebClient Adds Cross Application Tracing for all Traced Errors that happen on the external applications Fixes Addresses an issue where enabling query explain plans on applications using MySql sometimes caused connection leaking. Correctly strip forward slash from the category name in AgentAPI's SetTransactionName method.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-251120","eolDate":"2016-03-15"},{"agent":"dotnet","date":"2013-02-28","downloadLink":null,"version":"2.4.57.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features Adds Cross Application Transaction Trace linking so that in SOA (service-oriented architectures), all applications that are instrumented by a New Relic agent and that communicate with each other via http will now \"link\" transaction traces with the applications that they call and the applications they are called by. This change helps improve the correlation of performance between services and applications. Fixes The installer should now do a better job of cleaning up bad install states. We are uncertain how users get into such a state, but now it is less problematic when it does occur.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-24570","eolDate":"2016-02-28"},{"agent":"dotnet","date":"2013-02-08","downloadLink":null,"version":"2.3.126.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features New (not update) installations of the .NET Agent will default to using secure communications (HTTPS) between the agent and the New Relic server. Agent logging improvements. We have improved the clarity of logging messages, adjusted logging levels to be more appropriate, and increased logging performance. Adds a 'X-NewRelic-ID' header to all outbound http requests. This change helps improve the correlation of performance between services in a service-oriented architecture for a forthcoming feature. In the meantime, if you wish to disable the header, set 'crossApplicationTracingEnabled=false' in the configuration element of the newrelic.xml file. Fixes Fix crash in NewRelic.Agent.IL.dll caused by uninitialized data. Fix potential metric grouping issues associated with HTTP redirects. Fix confusing error message in the Diagnostic tool when the Application Event Log is at least 90% full. Fix potential null de-reference in unmanaged dll.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-231260","eolDate":"2016-02-08"},{"agent":"dotnet","date":"2013-01-16","downloadLink":null,"version":"2.2.83.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features Extends the uri reported in the external call labels in transaction traces so that users can see both the host and the resource being called. Improvements Rewrote the installer. You no longer need to uninstall before re-installing the agent. You can simply run the new installer and it will upgrade your old install. The installer no longer requires administrative rights at start to complete successfully. It will ask for elevation (on newer OSs) when needed and give reasonable error messages when it doesn't have enough permission (on older OSs). If you instrument non-IIS applications you should no longer manually set environment variables manually. Instead, during install choose the \"Instrument All .NET Applications\" feature. If you have already installed run the installer again and choose \"Change\". Configuration and log files are now stored in %ALLUSERSPROFILE%\\New Relic.NET Agent\\ instead of Program Files. The API is now optionally installed and should only be needed on development machines and build servers. Fixes Restores request queuing metrics being reported by the agent - they will now appropriately appear in the overview graphs","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-22830","eolDate":"2016-01-16"},{"agent":"dotnet","date":"2014-04-23","downloadLink":null,"version":"2.25.208.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Improvements Removed unnecessary instrumentation of an ASP.NET pipeline execution method. When automatically inserting the browser monitoring javascript, the agent now assures that a charset meta-tag continues to fall within the first 512 bytes of the document. Prior to this fix, insertion of the javascript may have pushed the charset meta-tag past the first 512 bytes, which would cause the character set not to be set, resulting in the browser setting the default to something that may not be what the developer intended. Fixes Fixes an issue where the Real User Monitoring Javascript was being injected into the page more than once because the response stream was being chunked. Fixes a problem where Unicode characters were not being correctly written to the page in some cases when Browser Monitoring was enabled in the agent. Fixes an issue where log files from the .NET Agent for Azure Websites were not being put in the correct location. Calling SetTransactionName via the NewRelic API will now behave correctly in background transactions. Fixes a bug where browser monitoring data was not captured when using Server-Side Configuration and Enterprise Security. Fixes an issue where when disabling Real User Monitoring in the New Relic UI the value set was not properly overriding the local configuration on the server. Fixes an issue where disabling the error collector in server-side configuration did not actually disable error collection by the agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-2252080","eolDate":"2017-04-23"},{"agent":"dotnet","date":"2014-03-05","downloadLink":null,"version":"2.24.218.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Improvements Improves transaction breakdown and transaction trace views by filtering certain .NET Framework methods. Due to the performance impact, adding \"NewRelic_BrowserTimingHeader\" and \"NewRelic_BrowserTimingFooter\" to manually-instrument browser monitoring (RUM) has been deprecated. The recommended method for manual instrumentation is to use the New Relic .NET Agent API. See the documentation page: https://docs.newrelic.com/docs/dotnet/real-user-monitoring-in-net  for details. Reduced the overhead of the agent through improved targeting of instrumented methods. Removes an erroneous error log message related to attempting to instrument RefEmit_InMemoryManifestModule. Fixes Fixes a bug where sometimes thread profiles would not display properly after being collected successfully. Fixes an issue where System.Data.SqlClient.SqlConnection.Open() metric was being removed from traces making it more difficult for users to gain visibility into how many database connections each transaction in their app was opening. Fixes a bug where the agent wouldn't increment the total errors count for errors reported via the API that occurred outside of a transaction. NuGet Fixes an issue where after deploying Windows Server monitor using the nuget package to Windows Azure the service will be in a stopped state. The Windows Server monitor will now start after deployment. Thanks Steven Kuhn  for the contribution!","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-2242180","eolDate":"2017-03-05"},{"agent":"dotnet","date":"2014-02-05","downloadLink":null,"version":"2.23.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Fixes a problem where running a thread profile against a 32-bit application fails to complete.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-22320","eolDate":"2017-02-05"},{"agent":"dotnet","date":"2014-02-04","downloadLink":null,"version":"2.22.79.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Improvements Reduces overhead cost (CPU and response time) of the agent in some cases. Fixes Fixes an issue where the Agent was not quickly releasing DBCommand when the explain plan threshold had been reached. Fixes an instance where a NullReferenceException might happen when the agent would try to record transaction statistics. A bug was fixed where the Capture Parameters setting (for Request Parameters) in Server-Side Configuration was not being respected by the agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-222790","eolDate":"2017-02-04"},{"agent":"dotnet","date":"2014-01-23","downloadLink":null,"version":"2.21.84.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Improvements We now add custom parameters to project Codename \"Rubicon.\"","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-221840","eolDate":"2017-01-23"},{"agent":"dotnet","date":"2014-01-18","downloadLink":null,"version":"2.20.25.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Fixes an issue where browser traces were not showing up in New Relic.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-220250","eolDate":"2017-01-18"},{"agent":"dotnet","date":"2014-01-09","downloadLink":null,"version":"2.20.24.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Improvements Adds Windows Server Monitoring to the New Relic Azure Cloud Services nuget package. Now when users add or update the nuget package on their cloud service projects and deploy they will begin getting all of the data and benefits of Windows Server monitoring. Thanks Steven Kuhn  for the contribution! Browser monitoring has been enhanced to allow for easier inclusion of features in client-side profiling. The agent now only injects javascript in the page header or, in the event that no head section exists, immediately before the opening body tag. In addition, the algorithm for identifying the insertion point has been improved. Fixes Fixes a bug during metrics harvest where a race condition might throw an exception.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-220240","eolDate":"2017-01-09"},{"agent":"dotnet","date":"2014-01-01","downloadLink":null,"version":"2.19.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Additional fixes for cases where status codes were not correctly being ignored when they should have been.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-21930","eolDate":"2017-01-01"},{"agent":"dotnet","date":"2013-12-27","downloadLink":null,"version":"2.18.35.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Fixed a bug where transactions were sometimes not being named. Fixed a bug where status codes were not correctly being ignored when they should have been.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-218350","eolDate":"2016-12-27"},{"agent":"dotnet","date":"2013-12-20","downloadLink":null,"version":"2.17.268.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This is a patch release to address an issue introduced in 2.17.266.0 where resources were not properly disposed, potentially causing a degradation in throughput over time.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-2172680","eolDate":"2016-12-20"},{"agent":"dotnet","date":"2013-12-19","downloadLink":null,"version":"2.17.266.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Fixes a bug where sometimes the first transaction after a cold start would be recorded resulting in a notable spike in response time graphs. Improvements Improves running performance and memory consumption of the agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-2172660","eolDate":"2016-12-19"},{"agent":"dotnet","date":"2013-11-19","downloadLink":null,"version":"2.16.164.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Fixes an issue where the agent was making calls to retrieve the SQL connection's database version unnecessarily. This issue may have caused some customer applications to unnecessarily hold onto database connections. Fixes an issue with the harvesting of AnalyticsEvents where a race condition would cause the collection of events to become invalid. Fixes a bug where generic exceptions were being reported with generic arguments which made it so they couldn't be ignored. Fixed a bug where attempting to add custom instrumentation for a parameterless overload of a method with parameterized overloads would result in all overloads of the method being instrumented. Added back support for custom instrumenting methods via parameters='void' in the exactMethodMatcher. It is recommended you use the new way which is to simply leave the parameters attribute off of your exactMethodMatcher, but for those with existing instrumentation files using 'void' parameters that will once again work.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-2161640","eolDate":"2016-11-19"},{"agent":"dotnet","date":"2013-10-22","downloadLink":null,"version":"2.15.186.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Fixes a bug where applications were sometimes named incorrectly.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-2151861","eolDate":"2016-10-22"},{"agent":"dotnet","date":"2013-10-21","downloadLink":null,"version":"2.15.180.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features Adds Percentiles and Histograms Adds the ability to instrument processes from IIS Express which include Azure Compute Emulator, Web Matrix and Visual Studio. By checking the \"Instrument all .NET Applications\" checkbox during the installation developers will now be able to get instrumentation on all web applications running as a hosted IISExpress process. Fixes Fixes logging during the installation of the .NET Agent for when the installer looks for an existing license key and on cleanup methods. Now when running installer using msiexec with options /i and /l*v it will now properly report the status of all installer actions in the log output. Fixed a bug that would cause a stack overflow if you tried to instrument a generic method with multiple instantiations.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-2151800","eolDate":"2016-10-21"},{"agent":"dotnet","date":"2013-10-11","downloadLink":null,"version":"2.14.53.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Resolved an issue where an application with limited permissions could throw an expensive/slow exception repeatedly per transaction causing increased CPU usage and decreased response time Resolved a performance issue associated with reading configuration off disk too frequently. Resolved several minor performance issues.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-214530","eolDate":"2016-10-11"},{"agent":"dotnet","date":"2012-12-04","downloadLink":null,"version":"2.1.3.494","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features Adds Real User Monitoring (RUM) auto instrumentation for all .net MVC versions Fixes Fixed an issue that would cause certain methods to not to be instrumented correctly including but not limited to Oracle.DataAccess.Client.OracleCommand.ExecuteReader.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-213494","eolDate":"2015-12-04"},{"agent":"dotnet","date":"2013-10-02","downloadLink":null,"version":"2.13.38.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes An unhandled null reference exception has been fixed. Fixed a bug that would cause a stack overflow if you tried to instrument a generic method with multiple instantiations.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-213380","eolDate":"2016-10-02"},{"agent":"dotnet","date":"2012-11-28","downloadLink":null,"version":"2.1.2.472","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Addresses an issue where the Real User Monitoring (RUM) footer was being injected outside of the body close tag in Web Forms applications, creating invalid markup. Also improves the performance of the auto instrumentation of RUM in Web Forms applications. The Apdex score (Satisfied, Tolerating, Frustrating) was being incorrectly reported for Key Transactions, and was also skewing the overall Apdex score.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-212472","eolDate":"2015-11-28"},{"agent":"dotnet","date":"2013-09-13","downloadLink":null,"version":"2.12.146.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Fixes an issue where content-type was being explicitly checked for \"text/HTML.\" In some frameworks, such as NancyFX , the charset was being added to the content-type before the New Relic HTTP module was loaded which caused the explicit check to fail and the RUM header and footer to not be added to the pages. Fixes an issue when the application results in a status code 404 or greater the metrics would be reported for the page not found instead of recording metrics for the 404 itself. This change also addresses an issue where assets such as png, css, js and so on would have metrics recorded for each individual asset instead of rolling them up into the appropriate asset group, such as *.png or *.css. Finally there were other metric grouping issues fixed where metrics were being named the custom route (such as /products/1) on some applications instead of using the name of the code asset that was doing the work to create the page (such as /products/productstemplate.aspx). Corrects functionality of the Status Monitor for IIS6 installations and applications running under sites other than DefaultWebSite. New Features A thread profiler  has been added to the .NET agent. The thread profiler is a low-impact profiling tool that can be used in production to identify bottlenecks in an application. Improvements Improves the logic around the RUM response filters which reduces the overall overhead of the .NET agent. Log files now have windows style line endings so they display correctly in notepad.exe. The status monitor tray application will now prompt for elevation on launch rather than error at runtime when it doesn't have correct permissions. Azure Cloud Services nuget package : Modified the package so that when installing a new version it will attempt an upgrade if an existing agent is installed. (This feature requires Nuget v.2.6 which prompts the user to overwrite existing / modified files - the newrelic.cmd must be overwritten to apply the new commands on the cloud service) Azure Cloud Services nuget package : The package now properly cleans up the environment variables out of the csdef when an uninstall or update occurs. Azure Cloud Services nuget package : For Worker Roles, the msiexec command in the newrelic.cmd file as been changed so that when the agent is installed it will install it for all CLR based applications.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-2121460","eolDate":"2016-09-13"},{"agent":"dotnet","date":"2012-11-16","downloadLink":null,"version":"2.1.1.13","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Fixed an issue where if an application was not using real user monitoring (RUM) the field that is used for that data was not being properly cleared. Fixed an issue where an implementation of ExtensionAttribute was overriding the .net 4.0 framework's CompilerServices.ExtensionAttribute. The agent will now use the appropriate implementation of ExtensionAttribute based on the given framework.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-21113","eolDate":"2015-11-16"},{"agent":"dotnet","date":"2012-10-11","downloadLink":null,"version":"2.1.0.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features Key Transactions alerting support for .NET Real User Monitoring (RUM) browser traces are now linked to app server transaction traces. Users can optionally turn on an Audit Log which will be a separate log file containing just the bits sent between the agent and the New Relic server. It can be enabled by adding the auditLog attribute to the log node of newrelic.xml, and assigning it a value of true. Fixes Fixed a bug revolving around a race condition that could cause an application to crash. Clarified some of the error output from the NewRelic .NET agent's diagnostic tool.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-2105","eolDate":"2015-10-11"},{"agent":"dotnet","date":"2013-08-20","downloadLink":null,"version":"2.10.40.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes Fixed a bug whereby IIS applications with underscore characters in their names were not displayed correctly in the Status Monitor. Fixed a bug whereby users could not view the log file for some IIS applications in the Status Monitor. Improvements Improved the naming of MVC transactions. Naming to controller/action should be much more reliable now. Improved WebAPI support. You should now see Web Transactions grouped by [controller].[action] rather than all WebAPI transactions reporting as System.Web.Http.WebHost.HttpControllerHandler.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-210400","eolDate":"2016-08-20"},{"agent":"dotnet","date":"2012-06-07","downloadLink":null,"version":"2.0.9.15","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes After deployment of a site, the site would throw a TypeLoadException \"Could not load 'NewRelic.Agent.Core.AgentShim' from assembly mscorlib\", because of a stale assembly token cache used within the agent. Segments in transactions for .NET MVC applications were being mis-labeled with System.Web.Mvc.ProcessRequest(async). This has been renamed to System.Web.Mvc.ProcessBeginRequest()[async] to reflect the actual name of the framework method being instrumented. This is because System.Web.Mvc.MvcHandler now implements IHttpAsyncHandler. Features changed The agent installer will no longer allow users who are not administrators to complete the installation. This prevents the agent from being improperly installed. Turned off the metrics for the execution pipeline steps. The agent still generates transaction trace segments for the calls, so the user will still be able to diagnose the pipeline without the execution pipeline steps.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-20915","eolDate":"2015-06-07"},{"agent":"dotnet","date":"2012-04-27","downloadLink":null,"version":"2.0.8.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Do a better job of exercising some diagnostic print statements. Strip off the generic qualifier (backtick and beyond) in Exception names when comparing names with a list of exception names to ignore. Make the diagnostic tool more robust, and release in an architecture-neutral format. The diagnostic tool now only writes to stdout. Change SQL obfuscator to correctly handle escaped quotes in strings, and to obfuscate more literal constants. Log (at finest level) obfuscated SQL and the generated metric name for SQL queries. Change the diagnostic tool to ternary logic, reporting PASS, WARN and FAIL; some errors reading registry now marked as WARN. Disable tracers for HttpWebRequest.SerializeHeaders and HttpWebResponse.Close, as the data collected by those is not yet used. Copy comments from newrelic.xml into newrelic.xsd to help xml aware editors. Log timestamps now contain millisecond accurate data. Stability enhancements in profiler core. Fix fusion log binding errors from the New Relic Agent.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-2084","eolDate":"2015-04-27"},{"agent":"dotnet","date":"2012-02-20","downloadLink":null,"version":"2.0.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Extend the command-line tool NewRelic.DiagnosticTool.exe to try to write to logs, %TMP% and to the registry. Add DiagnosticToolDocumentation.html that describes the DiagnosticTool. Improve error messages and error recovery when web.config file or any of the xml configuration files are lexically, syntactically or semantically incorrect. Fix a bug in the way some text is rendered in the event viewer.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-207","eolDate":"2015-02-20"},{"agent":"dotnet","date":"2012-01-26","downloadLink":null,"version":"2.0.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fix a bug when profiling functions with non-builtin value types as arguments. such as \"KeyValuePair\", \"Decimal\", etc. Make the profiler's interaction with the CLR memory more robust. Improve documentation on how to write custom instrumentation specifications. Extend the command-line tool NewRelic.DiagnosticTool.exe to check for more conditions, up to and including successful profiling. Page names collected from ASP are now downcased before being collected by the RPM, to match implicit case-insensitive behavior on windows. Allow Azure wawebhost.exe and waworkerhost.exe to be profiled executables. Copyrights to 2012.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-206","eolDate":"2015-01-26"},{"agent":"dotnet","date":"2011-12-07","downloadLink":null,"version":"2.0.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Bug fixes, debugging support and stability improvements Do not profile functions ending with .Dispose or .Finalize Do not reprofile functions that have already been profiled Load files in extensions directory in alphabetical order Support profiling functions that contain switch statements Fix bugs involving exception clauses for corner cases Fix bugs involving rewrites of short branch statements Fix some memory leaks for error paths in the profiler SQL declare, waitfor and execute keywords now supported Minor changes and bug fixes in documentation Rethrow ThreadAbortExceptions in profiled code","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-205","eolDate":"2014-12-07"},{"agent":"dotnet","date":"2012-09-20","downloadLink":null,"version":"2.0.12.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Features Updated the logo used in the installer. Fixes Allow medium-trust .NET applications to be monitored. We accomplished this by adding the AllowPartiallyTrustedCallers assembly attribute to all of our .NET assemblies. This also reduces assembly load overhead in some environments. Minor improvements to debug logging. Fix parsing of sql commands so that the metric name is based on a SELECT/INSERT/UPDATE/DELETE-style command instead of supporting commands such as SET (as in SET NOCOUNT). Improvement error handling in agent to avoid null reference exceptions. Added comments to the NewRelic.AgentApi programmer interface for intellisense support. Diagnostic tool now warns instead of reporting an error if COR_ENABLE_PROFILING is not set to 1.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-20124","eolDate":"2015-09-20"},{"agent":"dotnet","date":"2012-08-22","downloadLink":null,"version":"2.0.11.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . New Features The agent diagnostic utility, NewRelic.DiagnosticTool.exe, now supports a \"verbose\" mode as a command-line option (-v or -verbose). If you do not use the option, you will just get the failures and warnings. If you use the -v option, the output will include failures, warnings and passed test results. In previous versions of the agent, the diagnostic utility always output all results, making it more difficult to easily see where the failures were. Fixes Removed all of the static docs from the installer. All documents for the .net Agent are now available at: https://newrelic.com/docs/dotnet/ Changed the way the agent gets the urls for each web-based transaction from the built-in .NET RawUrl property to using the url off of the request. This will help keep urls reported by the agent consistent and prevent exceptions when raw representations of the url do not exist Significant improvements around the way the agent loads assemblies for instrumentation. This should help individual application load times as well as load times when instrumenting multiple applications on a single server","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-20111","eolDate":"2015-08-22"},{"agent":"dotnet","date":"2012-07-19","downloadLink":null,"version":"2.0.10.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fixes When enabling enterprise security (or High Security) in rpm applications either stop responding completely or the profiler will shut down due to security violation regardless of the ssl setting in newrelic.xml config.High security requires that the newrelic.xml config have the attribute ssl in the service node set to \"true,\" the enabled attribute in the requestParameters node set to \"false\" and the recordSQL attribute in the transactionTracer node to be set to \"obfuscated.\" The .net Agent log now appropriately reflects the configuration needs and will gracefully stop the profiler if the configuration does not meet the requirements of High Security. If there are invalid characters in the newrelic.xml file, when the .NET Agent's DiagnosticTool is run, it throws an exception associated with the \"DiagnosticCollectorAttachment\". This is the name of a private function in the tool, and the tool just logs the message associated with the exception. The fix now allows the evaluation for an inner exception, where the more meaningful message can usually be found and recorded. Fix for a Null Reference Exception happening on rare occasions when recording metrics.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-20103","eolDate":"2015-07-19"},{"agent":"dotnet","date":"2023-04-11","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.9.1","features":[],"bugs":["Allow StackExchange.Redis v2+ profiling to start outside of a transaction.","Fix a memory leak when using StackExchange.Redis v2+.","Allow the agent to accept multiple versions of legacy NR distributed tracing headers.","Retry connection on HttpRequestException error."],"security":[],"supportedOperatingSystems":null,"description":"New Relic recommends that you update the agent regularly and at a minimum every 3 months. Read more about keeping your agent up to date . This release is supported for one year after its release date. For a full list of supported versions and their support periods, please see our EOL policy doc . As of this release, the oldest supported version is .NET agent 8.26.630.0 . Fixes Allow StackExchange.Redis v2+ profiling to start outside of a transaction. (#1501 ) (#1504 ) (925d016 ) Allow the agent to accept multiple versions of legacy NR distributed tracing headers. (#1489 ) (23ee241 ) Fix a memory leak when using StackExchange.Redis v2+. (#1473 ) (#1504 ) (925d016 ) Retry connection on HttpRequestException error. (#1514 ) (#1484 ) (99b520e ) Once published, you can find the release artifacts for this release here  or on NuGet.org . Checksums | File                                      | SHA - 256  Hash                                                  |\n| ----------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.9.1-1.x86_64.rpm | 967F25DFD75AC1091AFA0CC6BC464D0511B23B6E92545179CB2807D91820F44B |\n| newrelic-dotnet-agent_10.9.1_amd64.deb    | 349AAC4179A1D597349190058DDBA5A6190947336B9FF1C16988C998C88B3ACA |\n| newrelic-dotnet-agent_10.9.1_amd64.tar.gz | 0D527ED576FAE29B2BA5F57E638EC3D2ED6B74352CC154B59BEEDD76CBEAA883 |\n| newrelic-dotnet-agent_10.9.1_arm64.deb    | 7F629B6329AEB0A357D4C04EF5152407AD937D1244F346A8F0888D465E9F19B8 |\n| newrelic-dotnet-agent_10.9.1_arm64.tar.gz | B65F63A3DEDB7018E07E1577CD5451D77678704D1D84DBA124EDB404615AD417 |\n| NewRelicDotNetAgent_10.9.1_x64.msi        | 67EE946BEE4175EABDFEB9AA8E23CDF8BC4F1A06264884C97984FAF957873120 |\n| NewRelicDotNetAgent_10.9.1_x64.zip        | 0852CBE4EED73491CE1D8A541C36D60F898CB9A068F5CF6092060EEB3A04CA5C |\n| NewRelicDotNetAgent_10.9.1_x86.msi        | 7411E1CC97E16BD57DCCCAB66A5FD9A355357531CCB87CA4B61C32FD3A166DEF |\n| NewRelicDotNetAgent_10.9.1_x86.zip        | 8337AC858B4ABB5486917B3069E4E8C4013A7377FF8E109AD2FDFB4EA2480889 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-9-1","eolDate":"2024-04-11"},{"agent":"dotnet","date":"2023-03-28","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.9.0","features":["Rename NewRelic.Providers.Wrapper.Asp35 to NewRelic.Providers.Wrapper.AspNet","Agent API supports associating a User Id with the current transaction","Agent API supports providing a callback to determine what error group an exception should be grouped under","Adds the Supportability/Logging/Forwarding/Dropped metric to track the number of log messages that were dropped due to capacity constraints"],"bugs":["Reduce redundant collector request data payload logging in the agent log at DEBUG level","Fix a regression in NLog local decoration when logging messages with object parameters"],"security":[],"supportedOperatingSystems":null,"description":"New Relic recommends that you update the agent regularly and at a minimum every 3 months. Read more about keeping your agent up to date . This release is supported for one year after its release date. For a full list of supported versions and their support periods, please see our EOL policy doc . As of this release, the oldest supported version is .NET agent 8.26.630.0 . New Errors inbox features User tracking : You can now see the number of users impacted by an error group. Identify the end user with the setUserId method. Error fingerprint : Are your error occurrences grouped poorly? Set your own error fingerprint via a callback function. New Features Agent API now supports associating a User Id with the current transaction. See our ITransaction API documentation  for more details.  #1420 Agent API now supports providing a callback to determine what error group an exception should be grouped under. See our SetErrorGroupCallback API documentation  for more details. #1434 Adds the Supportability/Logging/Forwarding/Dropped metric to track the number of log messages that were dropped due to capacity constraints. #1470 Fixes Reduce redundant collector request data payload logging in the agent log at DEBUG level. #1449 Fixes #1459 , a regression in NLog local decoration when logging messages with object parameters. #1480 Other Renamed NewRelic.Providers.Wrapper.Asp35 to NewRelic.Providers.Wrapper.AspNet since this wrapper instruments multiple versions of ASP.NET. Updated installers to remove old Asp35 artifacts. #1448 Once published, you can find the release artifacts for this release here  or on NuGet.org . Checksums | File                                      | SHA - 256  Hash                                                  |\n| ----------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.9.0-1.x86_64.rpm | 26AA1CE84A2724E65991E3035FB9F2899DF47447DC96618DC1969C424D18DFEB |\n| newrelic-dotnet-agent_10.9.0_amd64.deb    | F03AF60E81DFCAF706551BC8DB8DEB7B6FE7ADDCD961DDA72AA3B7F7D866B319 |\n| newrelic-dotnet-agent_10.9.0_amd64.tar.gz | 04F0A8699A35FF4E22D0FF704227B7E2DBA900064B17490D86270D4ADC01DB23 |\n| newrelic-dotnet-agent_10.9.0_arm64.deb    | 2C16448899297496B2659C31B6B72BDF08EE0B3A23218374FC9FE515BB714361 |\n| newrelic-dotnet-agent_10.9.0_arm64.tar.gz | C1795D4A94268DAEB57290DD2012822D9E9A76C7F38C52E84F93729BC89862D4 |\n| NewRelicDotNetAgent_10.9.0_x64.msi        | CFC4F5A33888B532808FEE8D256EF552804D59672726E43A34AADA20B31C972A |\n| NewRelicDotNetAgent_10.9.0_x64.zip        | 8D4682B2C3540527AB96EA08CB01F9B050917B66A67D651EECBD1A69DFC6FB59 |\n| NewRelicDotNetAgent_10.9.0_x86.msi        | A3C8FCC210F984BD89B91AD1237F212F17AA9DC77E7B977AA67D52FA4E4030AE |\n| NewRelicDotNetAgent_10.9.0_x86.zip        | 87775474DF6AF523380A9F434C316EC53694FF55784435BD53CFF272D1B4E085 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-9-0","eolDate":"2024-03-28"},{"agent":"dotnet","date":"2023-03-14","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.8.0","features":["Report Linux distro and version during agent connect"],"bugs":["Fix identification of .NET Core applications running in IIS when hosted out of process"],"security":[],"supportedOperatingSystems":null,"description":"New Relic recommends that you update the agent regularly and at a minimum every 3 months. Read more about keeping your agent up to date . This release is supported for one year after its release date. For a full list of supported versions and their support periods, please see our EOL policy doc . As of this release, the oldest supported version is .NET agent 8.26.630.0 . New Features When running on Linux, distro name and version will be reported as environment settings #1439 Fixes Fixes #1353  so that out-of-process .Net Core web applications are instrumented according to the <applicationPools> setting in the newrelic.config file. 1392 Update NLog to improve local log decoration coverage. #1393 Once published, you can find the release artifacts for this release here  or on NuGet.org . Checksums | File                                      | SHA - 256  Hash                                                  |\n| ----------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.8.0-1.x86_64.rpm | B6EDAF8B198C81FAB0FA190F28F5D49A8A255F5670CA8D76DBEDBF9E23B7DA10 |\n| newrelic-dotnet-agent_10.8.0_amd64.deb    | 8FFA4364420264E8E541DCF8F4F04F46EFAC8D30053C66686E922F7CDD45D511 |\n| newrelic-dotnet-agent_10.8.0_amd64.tar.gz | 04558B3B12DAE989874BF873041EB661995EC76DCE1594B936ADC671906385D3 |\n| newrelic-dotnet-agent_10.8.0_arm64.deb    | 50A88D55B0D82B63D7BDF68D2C83A030898BDA215F55992B20AE678AA1415BE7 |\n| newrelic-dotnet-agent_10.8.0_arm64.tar.gz | 015EEDF62DEC64CF4B95BFFBCDAC8FCE7DB0ECDEF833647ADD4DA69FFC65020C |\n| NewRelicDotNetAgent_10.8.0_x64.msi        | 7CF5BD50484C0CACE334F5CECF449602E9A596FF6D27F2E43EF15A0B44BE0479 |\n| NewRelicDotNetAgent_10.8.0_x64.zip        | 8112FF27EBFB77A1E3F80EC13B8A9194814D0E4E48A79CC22F3EDB2351F15F4A |\n| NewRelicDotNetAgent_10.8.0_x86.msi        | BF8669052C08A3B449A5278EC9FD23CAFA684CE322F19E30D172E3CB1EE4A12D |\n| NewRelicDotNetAgent_10.8.0_x86.zip        | 7A1658A7F8C6D39EED8AEFD30DCC5814D4A458E3A3F2EC45902AF001C0770F98 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-8-0","eolDate":"2024-03-14"},{"agent":"dotnet","date":"2023-02-14","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.7.0","features":["Add instrumentation for new versions of Postgres","Enable gzip compression by default for Infinite Tracing"],"bugs":["Fix race condition when using SetApplicationName API","Fix issue where enabling log context data could cause log forwarding to break","Add missing supportability metrics for Infinite Tracing"],"security":["Upgrade from soon to be deprecated gRPC libary to one with long term future support"],"supportedOperatingSystems":null,"description":"New Relic recommends that you update the agent regularly and at a minimum every 3 months. Read more about keeping your agent up to date . This release is supported for one year after its release date. For a full list of supported versions and their support periods, please see our EOL policy doc . As of this release, the oldest supported version is .NET agent 8.24.244.0 . New Features Postgres client instrumentation support has been extended to include the following versions: 4.0.x, 4.1.x, 5.0.x, 6.0.x and 7.0.x. #1363 Enables gzip compression by default for Infinite Tracing. #1383 Fixes Fix a race condition when using SetApplicationName. #1361 Resolves #1374  related to enabling Context Data for some loggers. #1381 Add missing supportability metrics to gRPC response streams and improve Infinite Tracing integration test reliability #1379 Deprecations Infinite Tracing for .NET Framework applications will be deprecated in May 2023. The Infinite Tracing feature depends on the gRPC framework to send streaming data to New Relic. The gRPC library currently in use, gRPC Core , has been in the maintenance-only phase since May 2021, and will be deprecated as of May 2023. The .NET Agent on .NET Core has been migrated to gRPC for .NET  per the guidance from grpc.io. However, this library doesn't have the full functionality that is required for Infinite Tracing on .NET Framework applications. Those applications will continue to use gRPC Core  until May 2023, at which time we'll end support for Infinite Tracing for .NET Framework. We may revisit this decision in the future if the situation changes. #1367 Other Resolved several static code analysis warnings relating to unused variables and outdated api usage. #1369 Update gRPC log message when a response stream is automatically cancelled due to no messages in a time period. #1378 Proxy configuration for Infinite Tracing should be specified using only the https_proxy environment variable. grpc_proxy is no longer supported for all application types. Once published, the release artifacts for this release can be found here  or on NuGet.org. Checksums | File                                      | SHA - 256  Hash                                                  |\n| ----------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.7.0-1.x86_64.rpm | B40A11004136EECD12F56BE28BDDE832E8D8494FC969A4A18EB058DC46E212EC |\n| newrelic-dotnet-agent_10.7.0_amd64.deb    | 2444258E09B0029FD18BEC9C21379E5A3F7DE2F67726C3C0D4944CEB271539FC |\n| newrelic-dotnet-agent_10.7.0_amd64.tar.gz | 4AA2CA405CBCBA7A9045E13E888883027681314061FEF88B12605DBF2B1E0350 |\n| newrelic-dotnet-agent_10.7.0_arm64.deb    | 060B9ABD3788833F1EF3F9476EF83A8D4FBB46E5897E992C55830214F6C6F27D |\n| newrelic-dotnet-agent_10.7.0_arm64.tar.gz | AAA980762F908C6AD69D085D4C40D55CBD38D8E1A0197DDE79CB3E9B7E55B593 |\n| NewRelicDotNetAgent_10.7.0_x64.msi        | 43238C88046CBB39896E749A9A5ED24190A450E3278D52C144777CF5B4FFDF1E |\n| NewRelicDotNetAgent_10.7.0_x64.zip        | 622304DD180C2B630A2DFDC00BB71172CF28BFF2CE4414C7AF5C15B64872E3DD |\n| NewRelicDotNetAgent_10.7.0_x86.msi        | 3CBCBE7DE060255FDA98A8B4BB7259DD9D0B4752678BA79936653D47031ADDF1 |\n| NewRelicDotNetAgent_10.7.0_x86.zip        | 2FD5DE0EFA6AA8B45568C70ACC0120D6264A1F3C2B5C5B7DCF8F2FB9CD3FCF6F | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-7-0","eolDate":"2024-02-14"},{"agent":"dotnet","date":"2023-01-24","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.6.0","features":["Add ability to target assembly versions in instrumentation","Add missing instrumentation for some versions of RestSharp","Log current TLS options during startup"],"bugs":["Improve performance when instrumenting Redis"],"security":[],"supportedOperatingSystems":null,"description":"New Relic recommends that you update the agent regularly and at a minimum every 3 months. Read more about keeping your agent up to date . This release will be supported for one year after its release date. For a full list of supported versions and their support periods, please see our EOL policy doc . As of this release, the oldest supported version is .NET agent 8.24.244.0 . Fixes StackExchange.Redis versions 2 and above use a new wrapper with improved performance and reduced network overhead. #1351 New Features Custom instrumentation now supports targeting specific assembly versions. See the documentation   for more details. #1342 RestSharp client instrumentation support has been extended to include the following versions: 106.11.x, 106.12.0, 106.13.0, and 106.15.0. #1352 RestSharp client instrumentation has been verified for versions 107.x and 108.x. For newer versions of RestSharp, external segments/spans are actually generated via our instrumentation of HttpClient. #1356 .NET TLS options are now logged during startup. #1357 Once published, the release artifacts for this release can be found here  or on NuGet.org. Checksums | File                                      | SHA - 256  Hash                                                  |\n| ----------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.6.0-1.x86_64.rpm | AAC3DD1231440E8D763BD1DF321AEAD8F4839F64CB1F9571270B9FFCC5C44AE2 |\n| newrelic-dotnet-agent_10.6.0_amd64.deb    | D50AD9EC45E40C82B410B8D46742375CCEB406018A5D1BC2B0F742F2AAD61836 |\n| newrelic-dotnet-agent_10.6.0_amd64.tar.gz | 9E3364B6AB5E9E28096AE58D8B25B0FCB7D71FFAAE18F2F119D5173212184A4B |\n| newrelic-dotnet-agent_10.6.0_arm64.deb    | 48165573EAE02D95A0B32EA044D7F9CF01A8BDBAD71F3B1A957D15D8D479BFE2 |\n| newrelic-dotnet-agent_10.6.0_arm64.tar.gz | CBD1FFF6117C122C48502A5CCB7C15D8175FF533213C56F193FCC57BC32AEE9A |\n| NewRelicDotNetAgent_10.6.0_x64.msi        | 904082AD371266353719FE331AB8013008DE71AD15A587974C09CAFD62591DA9 |\n| NewRelicDotNetAgent_10.6.0_x64.zip        | 87572DF1F0B41F38999F630C812B51F054A6DB6B31194829647FDF44C9A3C395 |\n| NewRelicDotNetAgent_10.6.0_x86.msi        | BDE47257B5AEF653671269724D8F781D9242538DB5A0CEEC540C603021892B06 |\n| NewRelicDotNetAgent_10.6.0_x86.zip        | 47006C36D9D2483D5A9497DC500078B077076B61EAFCC9219D6EFE4C8179D518 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-6-0","eolDate":"2024-01-24"},{"agent":"dotnet","date":"2026-09-16","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.55.0","features":["Add Kafka cluster metrics.","Allow setting the application name per IIS application pool in `newrelic.config`.","Instrument runtime-async methods."],"bugs":["Correct cloud.region and ARN partition determination for AWS SDK segments."],"security":[],"supportedOperatingSystems":null,"description":"New features Add Kafka cluster metrics (#3803 ) (803dc9a ) Allow setting the application name per IIS application pool in newrelic.config (#3794 ) (f1e2dcf ) Instrument runtime-async methods (#3804 ) (420485a ) Fixes Correct cloud.region and ARN partition determination for AWS SDK segments (#3787 ) (fc279c5 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.55.0-1.x86_64.rpm | BCDEE49221043F2CF34E1E6438C5F4610587553A0ECD6263347505DCC9775750 |\r\n| newrelic-dotnet-agent_10.55.0_amd64.deb | 7D2A3C5840B02D1EAEA543801C4D9E225E219C43D547245C8175D50BA7A7421E |\r\n| newrelic-dotnet-agent_10.55.0_amd64.tar.gz | 0291C440A8D0B8D675678500575A62503914EDDD7E7EC1FAE7729CF268215783 |\r\n| newrelic-dotnet-agent_10.55.0_arm64.deb | 91097FB797C6916C2EB1B3CAF6B70A302E5D38012715D96C2056B9F503584BC4 |\r\n| newrelic-dotnet-agent_10.55.0_arm64.tar.gz | CCE52F3D64C80617A9B3AC0AC7B0D377E6266280C47F7DE5A69F0BFEE7E0C85D |\r\n| NewRelicDotNetAgent_10.55.0_x64.msi | 8606356BD701B01AD56EE1A04242BBC3116576F96879E3402EA98B7280E29DC3 |\r\n| NewRelicDotNetAgent_10.55.0_x64.zip | 5689E231447803626D7EA6AA1F0CE21AC0845F561B421A27C7298642B7DE7E4B |\r\n| NewRelicDotNetAgent_10.55.0_x86.msi | C6E9F790781AA3331C6241C7A238CD92BD777D7E6895C2FA708B45DA2E40BA0D |\r\n| NewRelicDotNetAgent_10.55.0_x86.zip | 58C1DDC7BB9047A0FD5AA9AA998BD0B79A0B17426D2155ABF3BCD55B2210267A | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-55-0","eolDate":"2027-09-16"},{"agent":"dotnet","date":"2026-08-25","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.54.0","features":["The code that the profiler injects into your application now caches its lookups into the agent with a lock-free cache, instead of resolving each call by reflection, resulting in lower agent overhead for .NET applications."],"bugs":["Prevent transaction cross-contamination in HybridHttpContextStorage.","Release held WCF client transaction when async result completes before callback swap.","Skip SQL metadata comment injection for CommandType.StoredProcedure."],"security":[],"supportedOperatingSystems":null,"description":"New features The code that the profiler injects into your application now caches its lookups into the agent with a lock-free cache, instead of resolving each call by reflection, resulting in lower agent overhead for .NET applications. (#3709 ) (4c7797c ) Fixes Prevent transaction cross-contamination in HybridHttpContextStorage (#3754 ) (2d04565 ) Release held WCF client transaction when async result completes before callback swap (#3772 ) (3ef02f3 ) Skip SQL metadata comment injection for CommandType.StoredProcedure (#3756 ) (59b92ea ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.54.0-1.x86_64.rpm | 5827DDBD2DF30D8FD95716D39174C2B5F1D070FAA3935661390B08E525AC7269 |\r\n| newrelic-dotnet-agent_10.54.0_amd64.deb | 4A030327EEC8984DC710D954A2CFC0FD9083DA7EE4C901C131733CD4701B52C3 |\r\n| newrelic-dotnet-agent_10.54.0_amd64.tar.gz | F0DB7C0EE61D1541B53E4F2C386FFC2A1E9EAF8A2747851ADDB609413C7C9716 |\r\n| newrelic-dotnet-agent_10.54.0_arm64.deb | 1ADDF14BF92712CB7D4B94B48FF522D90AE4962117BA0FF8A753622364BB97AA |\r\n| newrelic-dotnet-agent_10.54.0_arm64.tar.gz | 5669562FD4C385E1E77467A83020B428F71285AFDF520D1849132BA67AF0D1EC |\r\n| NewRelicDotNetAgent_10.54.0_x64.msi | 30ECD5C1569FE9DC7C4BE42E01CDE9AE39B3374DE0B02E03EEAF864972F1624F |\r\n| NewRelicDotNetAgent_10.54.0_x64.zip | E6AAA98E88A53D8DBDF6554A718255251E61F927550A3C635B5BC10EF2BEB390 |\r\n| NewRelicDotNetAgent_10.54.0_x86.msi | 2E45E5C90F7E966879B62B67009CD21944DF0D0559FFF4C732B357BC9EAD8823 |\r\n| NewRelicDotNetAgent_10.54.0_x86.zip | 0844A835F179A420797F491433CFFDEBAA376DBDA8C89BCB18DABC69D1A76E8A | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-54-0","eolDate":"2027-08-25"},{"agent":"dotnet","date":"2026-08-12","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.53.1","features":[],"bugs":["Add on-insert check to SimpleCache to prevent runaway growth.","Aggregate metrics post rename instead of using old names.","Guard null OperationContext in WCF MethodInvokerWrapper.","Instrument new method for local log decoration in Serilog 4.4.0+.","Prevent double RUM script injection in ASP.NET Core 6+ responses.","Report the database a SQL command actually ran against."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Add on-insert check to SimpleCache to prevent runaway growth. (#3727 ) (88e667f ) Aggregate metrics post rename instead of using old names. (#3729 ) (67f7fcd ) Guard null OperationContext in WCF MethodInvokerWrapper (#3730 ) (4ab79f3 ) Instrument new method for local log decoration in Serilog 4.4.0+ (#3705 ) (426f711 ) Prevent double RUM script injection in ASP.NET Core 6+ responses (#3726 ) (498da98 ) Report the database a SQL command actually ran against (#3752 ) (b24ff10 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.53.1-1.x86_64.rpm | E3F829205343507625889375ADADD32EFD58A1F5E96FB48E4E31EEEB5704B503 |\r\n| newrelic-dotnet-agent_10.53.1_amd64.deb | 4EA560A11937A97A4762EFB6663C4A7C0F538B8F5A8B9BF799B0740EB2BA60DA |\r\n| newrelic-dotnet-agent_10.53.1_amd64.tar.gz | 80EB9F1884F8266FA807BA29BD2181F7B4E0F7738C6123718234A47280B09608 |\r\n| newrelic-dotnet-agent_10.53.1_arm64.deb | EDB1BBDF0274F768E77FDF49A9EB5EADCD1DCE9625BE2CAFD0B3F3ABE6D0A3A8 |\r\n| newrelic-dotnet-agent_10.53.1_arm64.tar.gz | 90E7AC73EDB9987E1EB018753BE145A73558B68C7E6C5B526E1CF952203F8733 |\r\n| NewRelicDotNetAgent_10.53.1_x64.msi | 2CADDEDC0D01D3BC9254709094306616F1866CA69B540A49A965E7AA1CC8079F |\r\n| NewRelicDotNetAgent_10.53.1_x64.zip | C257BB683F68804D852D28D7666B59603A687085B68DB38576C7AC0EB991712D |\r\n| NewRelicDotNetAgent_10.53.1_x86.msi | 138D8DC0EE9EDCB8036B6CBA040C19158102F1BCD2CD46DAFB684EC90B0D1825 |\r\n| NewRelicDotNetAgent_10.53.1_x86.zip | ED8469671E92226AECF76A567A4D55767112B4341918196374D7836BBE880197 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-53-1","eolDate":"2027-08-12"},{"agent":"dotnet","date":"2026-07-14","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.53.0","features":["Report request queue time from X-Request-Start/X-Queue-Start headers across all web hosts.","Support server-side configuration for AI Monitoring settings."],"bugs":["Update Npgsql instrumentation to support v8.x and newer."],"security":[],"supportedOperatingSystems":null,"description":"New features Added support for reporting request queue times using X-Request-Start and X-Queue-Start headers across all web hosts.(#3659 ) Added support for server-side configuration of AI Monitoring settings. (#3664 ) Fixes Updated Npgsql instrumentation to support version 8.x and newer. (#3667 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.53.0-1.x86_64.rpm | 47FEB3006A4BB71873B69B55AB8328444177F940B74F3C7EADD86A8DA28CB7ED |\r\n| newrelic-dotnet-agent_10.53.0_amd64.deb | 97A9BD3B5E4500512F6E1440F120FCDCCE23AC6721E23D8BFCA619725440DC5A |\r\n| newrelic-dotnet-agent_10.53.0_amd64.tar.gz | 9290ABC4F1F134458E9CDDF9A416B1BEC4B20ACFCB89121704A22B1C3C7E0249 |\r\n| newrelic-dotnet-agent_10.53.0_arm64.deb | 2D2C57E1DFAF9532FC02D650D4B6CB9FDAC61A6B2EE83D8E139ECF087C38CA55 |\r\n| newrelic-dotnet-agent_10.53.0_arm64.tar.gz | AC45E599A837055AF3666771570E979A185DA0764EBA9860874FACDB3D3A98D5 |\r\n| NewRelicDotNetAgent_10.53.0_x64.msi | 346A5B6942046BB0B86BBDF2FBA6AF5F9469FEE33BBD322219D0C80A42F345A8 |\r\n| NewRelicDotNetAgent_10.53.0_x64.zip | 082B15DF24C91EC9FE52DF2A2785786D685A93AC0196E0630CDF2950CE8A01E9 |\r\n| NewRelicDotNetAgent_10.53.0_x86.msi | FCC9965DCC4A95BF97BCA104603499FFAD3D6FEE5A9F59096F2BC63AC48809A7 |\r\n| NewRelicDotNetAgent_10.53.0_x86.zip | 3C8BA4B69609E1A9C9978CB30476CC1781F69BC2F9B9D43306AD867B03281EE9 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\r\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-53-0","eolDate":"2027-07-14"},{"agent":"dotnet","date":"2026-06-24","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.52.0","features":["Add alternative environment variables for expected and ignored error codes.","Add Kafka internal metrics.","Add SQL metadata comments to enable APM to DB Query Performance Monitoring correlation."],"bugs":["Bedrock Converse no longer drops events when first content block is non-text.","Distributed tracing for HttpWebRequest body and async requests.","Prevent malformed log_event_data JSON for non-serializable context values."],"security":[],"supportedOperatingSystems":null,"description":"New features Add alternative environment variables for expected and ignored error codes. (#3626 ) (c29f037 ) Add Kafka internal metrics (#3555 ) (1102c0b ) Add SQL metadata comments to enable APM to DB Query Performance Monitoring correlation (#3582 ) (04599b5 ) Fixes Bedrock Converse no longer drops events when first content block is non-text (#3649 ) (8813077 ) Distributed tracing for HttpWebRequest body and async requests (#3652 ) (8f8928d ) Prevent malformed log_event_data JSON for non-serializable context values (#3642 ) (a7108cb ) Checksums | File | SHA - 256  Hash |\n| ---| ---|\n| newrelic-dotnet-agent-10.52.0-1.x86_64.rpm | 8EEF3B79E350C9AC8847F98BD7B65F36EBB68DEA07584B25DEAED26F3BDD82C7 |\n| newrelic-dotnet-agent_10.52.0_amd64.deb | 39B04D8A1E0A959BCD991F74B8976233B3EFBB554888392C1F2604047B93F050 |\n| newrelic-dotnet-agent_10.52.0_amd64.tar.gz | EC89A207AF06250B95D18B37D0AB48E0084F200AE490E2742E46B67EDE15D140 |\n| newrelic-dotnet-agent_10.52.0_arm64.deb | 3835EC1A3E09FDB2E89D84BF208C4B4A672ABA7D871B4085FA1CE4F4940B63C3 |\n| newrelic-dotnet-agent_10.52.0_arm64.tar.gz | 368B0A07CD8D364118C03DD88BCCA0F1949F41E0AFA46F0B5F570206189EC3BB |\n| NewRelicDotNetAgent_10.52.0_x64.msi | FDEC80AF34274E8977B7FA8D3988DBD97C886076EF2FBF79DC183D0B67CCFD79 |\n| NewRelicDotNetAgent_10.52.0_x64.zip | D4B881550DDF0DCA896F2562609E9A4913B374D5D700C8BBBB19829525E32BE9 |\n| NewRelicDotNetAgent_10.52.0_x86.msi | 926EBD52E48FBF5FA950204502939AC9487D87DB9B99960E04EC772C94DC0E6A |\n| NewRelicDotNetAgent_10.52.0_x86.zip | 31DFFFCCC20C3B9735EE9D4D060D8C4DC1476F9B87088CE4A78477894E8431DA | Update your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-52-0","eolDate":"2027-06-24"},{"agent":"dotnet","date":"2026-06-03","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.51.1","features":[],"bugs":["`RecordDatastoreSegment()` API will correctly use the caller-supplied vendor name instead of ignoring it.","Ensure all StackExchange.Redis segments are created and added to transaction before it is harvested.","Update MySql.Data instrumentation to support 9.7.0 signature changes."],"security":[],"supportedOperatingSystems":null,"description":"Notice Customers using RecordDatastoreSegment() with a custom vendor name will see metric names change from Datastore/*/Other/* to Datastore/*/<VendorName>/*. Update any dashboards, alerts, or queries that reference the old Other-based metric names. (f6c0e48 ) Fixes RecordDatastoreSegment() API will correctly use the caller-supplied vendor name instead of ignoring it. (f6c0e48 ) Ensure all StackExchange.Redis segments are created and added to transaction before it is harvested (#3574 ) (4152ea2 ) Update MySql.Data instrumentation to support 9.7.0 signature changes (#3562 ) (1e40e44 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.51.1-1.x86_64.rpm | 3B9EF23D18D2E02203460709B26B28161CC31DEFBBCBFAF3D48834560DD0DF4B |\r\n| newrelic-dotnet-agent_10.51.1_amd64.deb | FE96D636FDC7EACEF3ABBA8CB21017CBB26997B3FDFC1C5210DC22D0B0A2CC4C |\r\n| newrelic-dotnet-agent_10.51.1_amd64.tar.gz | A68BC5A3D4CEC75EC5CA74099A8AD26304C95703C7C4D97446AC3ECEF7F8D5D1 |\r\n| newrelic-dotnet-agent_10.51.1_arm64.deb | F9AC7CCB60BBBBD4F6E1836C26E90E120CDF0AF19A260D163679AF4E47FA727F |\r\n| newrelic-dotnet-agent_10.51.1_arm64.tar.gz | 3976004C0172EB55F7E5870B30C346EDA9E36D142B4D8DB2022F75698AED96AC |\r\n| NewRelicDotNetAgent_10.51.1_x64.msi | 218633CA0DC399FCFB97BE0CCFABEE09AE7B61CC3122E978C62F72D706068E71 |\r\n| NewRelicDotNetAgent_10.51.1_x64.zip | 71CB4D69F20D4111C6C7A9E72D8B3F8110099EA5DC574FEC12C5B0DAC4B89B9B |\r\n| NewRelicDotNetAgent_10.51.1_x86.msi | 7B45106117DA4195D759BF045A2CB67E7146C95018062574E6EB3F0FA4DAE155 |\r\n| NewRelicDotNetAgent_10.51.1_x86.zip | AA228DAC74A2223285F69E68DD92D85AE1D110E8DE755E483842B5CE667A2BFC | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-51-1","eolDate":"2027-06-03"},{"agent":"dotnet","date":"2026-04-22","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.51.0","features":["Add support for instrumenting Hangfire background jobs.","Include structured log message arguments as context data for MEL."],"bugs":["Complete array attribute serialization for all payload types.","Resolve Lambda auto-instrumentation race condition.","Restore dotnet-counters tool compatibility.","Send loaded modules on agent reconnect.","Support multi-transport queue name parsing for MassTransit."],"security":[],"supportedOperatingSystems":null,"description":"New features Add support for instrumenting Hangfire background jobs. (#3520 ) (2e82366 ) Include structured log message arguments as context data for MEL (#3479 ) (24819c4 ) Fixes Complete array attribute serialization for all payload types (#3531 ) (62bdb44 ) Resolve Lambda auto-instrumentation race condition (#3508 ) (25c59e7 ) Restore dotnet-counters tool compatibility (#3526 ) (407eae5 ) Send loaded modules on agent reconnect (#3534 ) (ecaa550 ) Support multi-transport queue name parsing for MassTransit (#3523 ) (db48d08 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.51.0-1.x86_64.rpm | 795AEBF7AA3C09ACB59F2A39668196B8A6CD1BC7C7EF7D5896BD6BD7FB684926 |\r\n| newrelic-dotnet-agent_10.51.0_amd64.deb | 69BCA5C0275B88E58C4081D5BA1A2D9C0B39BD5652A4501D5648E92DB1972847 |\r\n| newrelic-dotnet-agent_10.51.0_amd64.tar.gz | 48BC2FC7314D687F88AAE4C80DCABBFC1E71C6C03C0D003A8C37B5F4857D8D21 |\r\n| newrelic-dotnet-agent_10.51.0_arm64.deb | 625D40CD6859F69BE4BDB2E00F723CF6502C36AD75BDEBDF4540038FE1352A14 |\r\n| newrelic-dotnet-agent_10.51.0_arm64.tar.gz | 70AA68C9DED666E7FF5CECE0C3C136AAABF2ACBB13001454FEDF755EFDCCE844 |\r\n| NewRelicDotNetAgent_10.51.0_x64.msi | 0C63470CB0BE1110666156BB78972CB60931C0896D9F92B3B75ABD2426234CFA |\r\n| NewRelicDotNetAgent_10.51.0_x64.zip | 7A8130286581CD1ABA6AEC10796FD52F3003D249C9689B62B8CB76548D94315F |\r\n| NewRelicDotNetAgent_10.51.0_x86.msi | 86F4F84703410CEB856D69D12E4057ACB412EB543236766DF5F55DDD37609F42 |\r\n| NewRelicDotNetAgent_10.51.0_x86.zip | 0B12AA812E197964F531DEAFE30B38BF764A66BF97D76BA128C81CE09245BCED | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-51-0","eolDate":"2027-04-22"},{"agent":"dotnet","date":"2026-03-19","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.50.0","features":["Add array support for custom attributes in .NET Agent API.","Add hybrid agent support for grpc-dotnet.","Add LLM monitoring for `Microsoft.Extensions.AI` via OpenTelemetry bridge."],"bugs":["Don't instrument Blazor / SignalR websocket connections."],"security":[],"supportedOperatingSystems":null,"description":"New features Add array support for custom attributes in .NET Agent API (#3456 ) (4fb9405 ) Add hybrid agent support for grpc-dotnet. (#3475 ) (6b48c06 ) Add LLM monitoring for Microsoft.Extensions.AI via OpenTelemetry bridge (#3472 ) (2e03c0c ) Fixes Don't instrument Blazor / SignalR websocket connections (#3468 ) (7f2a5e9 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.50.0-1.x86_64.rpm | 0BEA299FD737B07D979647FD1DCFB6CFB55E9DE14515ACFB1A5792F919505234 |\r\n| newrelic-dotnet-agent_10.50.0_amd64.deb | 372865C6C6E008A9D29E133D77DC0F071316C4C642C01FBCC18DEF911966A03D |\r\n| newrelic-dotnet-agent_10.50.0_amd64.tar.gz | B65E508595A9803C2511B4466ADB010CEDE2526EB3F2647F30F0CC0AE1B59E0A |\r\n| newrelic-dotnet-agent_10.50.0_arm64.deb | 3D775B140EE8C2335D6E4384F032DF98FB1293C48725BE11F387B82DEA6F5A0F |\r\n| newrelic-dotnet-agent_10.50.0_arm64.tar.gz | EA7A14F1538518219D7FA1A7BCEC24271B4FDB7476F10ADA53D35DF242A17ACE |\r\n| NewRelicDotNetAgent_10.50.0_x64.msi | C8A8F68F5ED917E90D9CCCB4C3FDCDD386B61B165E1BF1F1EF10905905984A62 |\r\n| NewRelicDotNetAgent_10.50.0_x64.zip | CBF97772F7AE907DDBED719461149B31B96443C959B091D0AD337D749BBCDF3A |\r\n| NewRelicDotNetAgent_10.50.0_x86.msi | B155B6093D0F757D1B254F3AE44CB12A798C433AF14E1A4969810BCB170C41E6 |\r\n| NewRelicDotNetAgent_10.50.0_x86.zip | 700693677A6C44895533D7806F39AC983EB9DE58D2E78215FDC00FE7D2855A6B | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-50-0","eolDate":"2027-03-19"},{"agent":"dotnet","date":"2023-01-17","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.5.1","features":[],"bugs":["Add missing content to NuGet packages"],"security":[],"supportedOperatingSystems":null,"description":"New Relic recommends that you update the agent regularly and at a minimum every 3 months. Read more about keeping your agent up to date . This release will be supported for one year after its release date. For a full list of supported versions and their support periods, please see our EOL policy doc . As of this release, the oldest supported version is .NET agent 8.24.244.0 . Fixes Resolves #1346  where some NuGet packages were incomplete for the 10.5.0 release. Impacted packages have been delisted from NuGet. (#1347 ) Once published, the release artifacts for this release can be found at https://download.newrelic.com/dot_net_agent/latest_release/  or on NuGet.org. Checksums | File                                      | SHA - 256  Hash                                                  |\n| ----------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.5.1-1.x86_64.rpm | 7F1407B5CF51F1D6F32FE7EC63FF06DB401554BD9C4C2337EDA2AE43FCB46EBF |\n| newrelic-dotnet-agent_10.5.1_amd64.deb    | 0B80A6F79457A2CDE1DB2B9C49002B31FE8CB6EB529161752FB9A389B7CDDE09 |\n| newrelic-dotnet-agent_10.5.1_amd64.tar.gz | EAC8E7B3104E8E385AED5D5038A0AB250E6AAE174EC7CD2432D35CDFAA931EF3 |\n| newrelic-dotnet-agent_10.5.1_arm64.deb    | 0F1B7E673A2CFA78DF87DC677E9E35CC7DF88CC4D510284E7EC777494F4A872B |\n| newrelic-dotnet-agent_10.5.1_arm64.tar.gz | 403C51C04133A3BB62203988B404B6C1509456AE83646FDB034F5DD3B4E2B9CA |\n| NewRelicDotNetAgent_10.5.1_x64.msi        | 7753F1912849BF11ADDA71D5BD00539D6E49A46ABFD80CF357C65CC244DAC1C6 |\n| NewRelicDotNetAgent_10.5.1_x64.zip        | 78245732D094919DEA264C0B793601E630220984A66E54567CEABB2220C4E00D |\n| NewRelicDotNetAgent_10.5.1_x86.msi        | DEDC6A206868A460496435676EEF37D9A1FC319B96282F0FB9F7CC6D0E6119D4 |\n| NewRelicDotNetAgent_10.5.1_x86.zip        | A29FBC03013D8B5A1EB81B3AB7838AF19309BC96314C733E7882061BEFFE1272 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-5-1","eolDate":"2024-01-17"},{"agent":"dotnet","date":"2023-01-12","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.5.0","features":[],"bugs":["Improve attribute collection limit and update logic","Resolve issue where Agent could cause socket errors in applications using HttpClient"],"security":[],"supportedOperatingSystems":null,"description":"New Relic recommends that you update the agent regularly and at a minimum every 3 months. Read more about keeping your agent up to date . This release will be supported for one year after its release date. For a full list of supported versions and their support periods, please see our EOL policy doc . As of this release, the oldest supported version is .NET agent 8.23.107.0 . Some of the NuGet packages from this release were incomplete and have been unpublished from nuget.org.  Please use 10.5.1 instead. Fixes Attribute collections in the agent will now more reliably track the number of attributes contained, and allow updates to attributes that already exist in the collection when collection limits have been reached\n(255 global attributes, 65 custom attributes). (#1335 ) The agent has been updated to use System.Net.Http.HTTPClient to send data to New Relic instead of System.Net.WebRequest, in order to fix issue #897 , as well as remove use of a deprecated library. (#1325 ) Once published, the release artifacts for this release can be found at https://download.newrelic.com/dot_net_agent/latest_release/  or on NuGet.org. Checksums | File                                      | SHA - 256  Hash                                                  |\n| ----------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.5.0-1.x86_64.rpm | 939A1A8DFD179B4436F2DFDC1950D7AD4DEC5ED4F26C3E750A9880F147E47092 |\n| newrelic-dotnet-agent_10.5.0_amd64.deb    | 39B1E63CAD364765527B254EF363615F3209213D9CCF9EC2DA2920D4104788B2 |\n| newrelic-dotnet-agent_10.5.0_amd64.tar.gz | A3937CF850A2FDAC5978112626063C07AEA96244FF82749E85470FA02523B44B |\n| newrelic-dotnet-agent_10.5.0_arm64.deb    | D2BE115DFF5E98A637451C7851BC6BA03B703543931CF1DF2609637AC61F6AFF |\n| newrelic-dotnet-agent_10.5.0_arm64.tar.gz | 340063F58538E2DF33FBE8DDA04D41A548DE4F2D139EE9A7D2E5EA79F0FB4279 |\n| NewRelicDotNetAgent_10.5.0_x64.msi        | E2C6F6FDFA4789D2A72EE985FEF4B86E8B53E57ADC26EF3CD1D4E44DAE4D09A3 |\n| NewRelicDotNetAgent_10.5.0_x64.zip        | 7141AB68BA848B5861943DD50849E5609B767B75A3BF43E540959EAA1874326A |\n| NewRelicDotNetAgent_10.5.0_x86.msi        | E87DEF5028F1AF01A8EF8A0503A112F80D1B519EA11464FFC41AFE63F231D54A |\n| NewRelicDotNetAgent_10.5.0_x86.zip        | 4C660F4267F42A73EA66166AC536CC0596F8A7840D62FCA8FC76EB4771942439 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-5-0","eolDate":"2024-01-12"},{"agent":"dotnet","date":"2026-02-11","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.49.0","features":["The .NET Hybrid Agent provides a future-proof observability solution with integrated support for OpenTelemetry Tracing and Metrics APIs."],"bugs":["Agent correctly overwrites files when necessary."],"security":[],"supportedOperatingSystems":null,"description":"New features The .NET Hybrid Agent provides a future-proof observability solution with integrated support for OpenTelemetry Tracing and Metrics APIs. OpenTelemetry Logs will continue to be supported through the existing Microsoft.Extensions.Logging integration. This release delivers critical OpenTelemetry features including Span Links, Events on Spans, and unified sampling algorithms. It is designed to bridge the gap for .NET teams looking to adopt OpenTelemetry standards while maintaining backwards compatibility with their existing New Relic dashboards. (72a0414 ) Fixes Agent correctly overwrites files when necessary. (#3425 ) (9cafa88 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.49.0-1.x86_64.rpm | B7DEA32E1E0775A869D7700A1EFACDB2361D8EF1200B80B62D3499E0DA37F14C |\r\n| newrelic-dotnet-agent_10.49.0_amd64.deb | CB99FD48A78EAF3AD79AACAAAB6CE084BD9544893D170AF1F525B28EA6B5E0A6 |\r\n| newrelic-dotnet-agent_10.49.0_amd64.tar.gz | FB189DC2416B93909A03A46439E74F6E18BAAE9C1C1D470EB5110A5137F5B511 |\r\n| newrelic-dotnet-agent_10.49.0_arm64.deb | 98F9A16A0C57B21B12D43BAB14EA5D981C9288023F1D1E632D6DE361FC3BE21A |\r\n| newrelic-dotnet-agent_10.49.0_arm64.tar.gz | 413C5463576D705216CA4AD8EF6EECBF191F703C4B99B18C1E9BDB0521CD0315 |\r\n| NewRelicDotNetAgent_10.49.0_x64.msi | FCF035722DCF482E2735C77272305F6B731E9829C16D31222E76DC9527988000 |\r\n| NewRelicDotNetAgent_10.49.0_x64.zip | F3F5E3290EBF60769C936B6E3C114621E2D7AC901D752E165B18807444B0D1EE |\r\n| NewRelicDotNetAgent_10.49.0_x86.msi | C3BDD82B1A067349C9792319B73290E02DF4A4FD483ED280CA734E1F45CE58AA |\r\n| NewRelicDotNetAgent_10.49.0_x86.zip | 26C00F9CD5B33D73B00C8E958D10BF9126CC13B81984AC58B3D3944388792649 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-49-0","eolDate":"2027-02-11"},{"agent":"dotnet","date":"2026-01-28","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.48.1","features":[],"bugs":["Properly handle unsupported DynamoDB SDK requests."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Properly handle unsupported DynamoDB SDK requests (#3403 ) (#3407 ) (d0155ea ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.48.1-1.x86_64.rpm | EDC902F3A97DC34BE75DEE5CE3E4C9B9AF86195EBF596D61BB4E200CC7EF108A |\r\n| newrelic-dotnet-agent_10.48.1_amd64.deb | 6B4F94753712C4383C5EA024B13ABF0591082DFE5A02B24E10E5DBA04CBD2666 |\r\n| newrelic-dotnet-agent_10.48.1_amd64.tar.gz | CB7DE88D494DFA1BF301404BBA05C673394D7CA4BCCD7580E50EFBD762C808AC |\r\n| newrelic-dotnet-agent_10.48.1_arm64.deb | CCCB4B9942F8A73135D9EFB8CBEF12AD52E3D288B10E04FE833F5CCD056BC026 |\r\n| newrelic-dotnet-agent_10.48.1_arm64.tar.gz | B869C64D9176359DA5FDA5ECFC05DB30ECA6AF5D4BA30AD215D916EF0E09E39D |\r\n| NewRelicDotNetAgent_10.48.1_x64.msi | A5D01759C0449AD7533E0B50690DB66C1B3E5F330B74729CB4895C7F49AB3230 |\r\n| NewRelicDotNetAgent_10.48.1_x64.zip | 0D3CE0A5B6036E60C9692116AC9C5BEB63E4A9C73139AE9A794E341CEE509261 |\r\n| NewRelicDotNetAgent_10.48.1_x86.msi | D5E523AC071970460858E1A03B486F103441A0CA1E7AB53F5C5BA5380F126448 |\r\n| NewRelicDotNetAgent_10.48.1_x86.zip | 20C17D00441366F65FA309D4DF54F0DA363856F916C6A0D833145CBEB0843F20 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-48-1","eolDate":"2027-01-28"},{"agent":"dotnet","date":"2026-01-14","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.48.0","features":["Allow users to configure process names that should not be instrumented.","Increase maximum length of `db.statement` span attribute to 4096 bytes."],"bugs":["Fix agent connection error when debug logging is enabled.","Restore min/max occurs properties on `distributedTracing` config element."],"security":[],"supportedOperatingSystems":null,"description":"Notice The GPG key used to sign .NET Agent RPM packages in our YUM repo has been rotated. Please update your systems to trust the new key by downloading our updated repository definition file  and placing it in /etc/yum.repos.d/, overwriting any existing version of that file. (ef5f329 ) New features Allow users to configure process names that should not be instrumented (#3387 ) (8dedf32 ) Increase maximum length of db.statement span attribute to 4096 bytes (#3364 ) (#3365 ) (bbac2f4 ) Fixes Fix agent connection error when debug logging is enabled. (#3395 ) (82fc1b6 ) Restore min/max occurs properties on distributedTracing config element. (#3381 ) (#3388 ) (2d0b89f ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.48.0-1.x86_64.rpm | 56F03A355A181BD379AF3B4FED304DB54717DAD5F9E206184BF9FACCB478F82E |\r\n| newrelic-dotnet-agent_10.48.0_amd64.deb | A88F00D777D7F55BBCEA767F30B76E7B26061CCF0EE15C9677E9D08B6DB1CC98 |\r\n| newrelic-dotnet-agent_10.48.0_amd64.tar.gz | E7A24777F5008041E92A43578408997A57DFCC1C560CC2E4D750C34DC6433565 |\r\n| newrelic-dotnet-agent_10.48.0_arm64.deb | 8F5B24807FB9BD6DF71C2B958FAA886031110D8CC9A4F1681D43534A7EDF0321 |\r\n| newrelic-dotnet-agent_10.48.0_arm64.tar.gz | 8A998489962E8521F9CBCB1B19CC49B7ABC0816C1BDED9303F978DC5575B5209 |\r\n| NewRelicDotNetAgent_10.48.0_x64.msi | 3534742D2029A1889CF1E3FFD86CDF60C216BAE69944D8CA753DEB8964441806 |\r\n| NewRelicDotNetAgent_10.48.0_x64.zip | 03DC5D4471DD6F9288676355EC1EBB2FDFAFA897895296C53A9D02ADF39E74C8 |\r\n| NewRelicDotNetAgent_10.48.0_x86.msi | AFCB8F179EC968ACF207E972A95E22039E116253BADB60A5CFE1083FD398EDF2 |\r\n| NewRelicDotNetAgent_10.48.0_x86.zip | E01343FDB5AD979878B6EA4D72AB5CA3EE57AE37C6653BE8C71F5FA81FDD3866 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-48-0","eolDate":"2027-01-14"},{"agent":"dotnet","date":"2025-12-03","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.47.1","features":[],"bugs":["Cache all environment variable access to reduce possible thread contention.","Ensure OpenAI LLM supportability metrics are recorded on all invocations."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Cache all environment variable access to reduce possible thread contention (#3322 ) (e2a8109 ) Ensure OpenAI LLM supportability metrics are recorded on all invocations. (#3320 ) (a4d7af8 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.47.1-1.x86_64.rpm | 2E01BB5F52ABB5F1A322D5888FE38D6F755E9C94E02252C9A65EDA598F6D9DD7 |\r\n| newrelic-dotnet-agent_10.47.1_amd64.deb | 0E4535C6F117F3BC8693110DD7FC54494032E087010CE38ED007B1F50D855843 |\r\n| newrelic-dotnet-agent_10.47.1_amd64.tar.gz | 3DB1E39F06ED3725EB0003A4608634E04B1901B06D510C690FC7BEC68AE2F784 |\r\n| newrelic-dotnet-agent_10.47.1_arm64.deb | BF6B15FC385905D53B4F81EF9E3EBA457D1A95298E75E8CC207F62626701B69A |\r\n| newrelic-dotnet-agent_10.47.1_arm64.tar.gz | 44033BE45CF837C5B560B3AE0D9086EF1B3A1F1C2985AD209D304893346F2503 |\r\n| NewRelicDotNetAgent_10.47.1_x64.msi | 2C2DA594CFC4A87AC618BCCED020C89695C4A95C48455AC748B5215E7E07D8C2 |\r\n| NewRelicDotNetAgent_10.47.1_x64.zip | F9997CCA1CE4C9DC7FBDF15A04CA8F7A25A3E1866A59CDFD21BDEDF1C9810DA4 |\r\n| NewRelicDotNetAgent_10.47.1_x86.msi | F7BBB2FD6E33D426060C7A78196AC575784743F7DB1EF75CDA2CA5EE38CCBBDE |\r\n| NewRelicDotNetAgent_10.47.1_x86.zip | 2E95DE873D98B60824641AD9D60A31CFE14ADE3709300AEE724477A89B622298 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-47-1","eolDate":"2026-12-03"},{"agent":"dotnet","date":"2025-11-19","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.47.0","features":["Add an optional transaction storage mechanism to allow transactions to flow with the ExecutionContext for ASP.NET web apps."],"bugs":["Azure Service Bus instrumentation fails due to null reference exception.","OpenAI instrumentation ignores chat completions when `CompleteChatAsync()` or `CompleteChat()` `messages` parameter is not an `Array`."],"security":[],"supportedOperatingSystems":null,"description":"New features Add an optional transaction storage mechanism to allow transactions to flow with the ExecutionContext for ASP.NET web apps (#3311 ) (d254ce9 ) Fixes Azure Service Bus instrumentation fails due to null reference exception (#3305 ) (b2bf4df ) OpenAI instrumentation ignores chat completions when CompleteChatAsync() or CompleteChat() messages parameter is not an Array (#3317 ) (3df9570 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.47.0-1.x86_64.rpm | 77315BA7E66433CE1978BAFF29526E8A5DE8C34892D75658D8DCBCEDF9FA0279 |\r\n| newrelic-dotnet-agent_10.47.0_amd64.deb | B88DDC601C571807A17D21F368C16E70E24607BC5CBD246B5FE4B6E314D990D7 |\r\n| newrelic-dotnet-agent_10.47.0_amd64.tar.gz | 2BDAF86B8CF98E777017C6F6B30616DA6560F6F277CFBEBA8B09CE20957E0DEF |\r\n| newrelic-dotnet-agent_10.47.0_arm64.deb | BEFAB3E74594B40D4E12B805B06B6F7E9F34C25094B4D5D658D40D3B587EC2F3 |\r\n| newrelic-dotnet-agent_10.47.0_arm64.tar.gz | F15BECC94421830FA5CA19E85DF58870C3306273AE1C83FE53BB1F955B8A43B8 |\r\n| NewRelicDotNetAgent_10.47.0_x64.msi | BFCE165BF19D370063A807781C03583818F60BC51BA82545E04CC3FEA2336416 |\r\n| NewRelicDotNetAgent_10.47.0_x64.zip | 6820E4EC4797DD6912A109539583898D2F1FB2BE8508D91097A7E0C0EA4D0A5B |\r\n| NewRelicDotNetAgent_10.47.0_x86.msi | 8ECE4596BA1FEABCEE84B48A64B857F1E8D40CEA6227AB2409988886A30BC0F9 |\r\n| NewRelicDotNetAgent_10.47.0_x86.zip | 3F0D0E6E27E1F63941205F8C3CC4CBF39C90CD44AE9713C953CE6E9B42401B72 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-47-0","eolDate":"2026-11-19"},{"agent":"dotnet","date":"2025-11-11","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.46.1","features":[],"bugs":["Remove \"consume\" span from Azure Service Bus transactions created in \"processor\" mode for more accurate transaction timing.","Update ReportedConfiguration to serialize certain enums as strings instead of integers for better clarity when viewing settings in the UI."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Remove \"consume\" span from Azure Service Bus transactions created in \"processor\" mode for more accurate transaction timing. (faa591f ) Update ReportedConfiguration to serialize certain enums as strings instead of integers for better clarity when viewing settings in the UI (#3296 ) (e972745 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.46.1-1.x86_64.rpm | C89903047345D3F1F031C526374A70987A9172E04ED4ACF2250B6CF0B64566AA |\r\n| newrelic-dotnet-agent_10.46.1_amd64.deb | 8F2AF9B296896A420FE05ED4CC35A4E7824E33FE9096F2A015C5DBBA532BDA65 |\r\n| newrelic-dotnet-agent_10.46.1_amd64.tar.gz | FA9274C1C323E104DBC8308F7F6FD5371801971D0A8B4E660311D98013E286BC |\r\n| newrelic-dotnet-agent_10.46.1_arm64.deb | 9205C1336AB2F65C62F63EE4CD086BBA44B66A53568122B8947F32523A40EFF6 |\r\n| newrelic-dotnet-agent_10.46.1_arm64.tar.gz | EB988111A2C38521996401A52A88B6720CF06499C442C297E0413C1C3CDCA5B6 |\r\n| NewRelicDotNetAgent_10.46.1_x64.msi | 381B941AF95879465E81364981E265940DCB25D9311060E1D4C13064A13E7C19 |\r\n| NewRelicDotNetAgent_10.46.1_x64.zip | C0D37F4FEAA97B28E0C78D74A2BEB0A0E38F4026F19476EBB7D8201E0D4293C6 |\r\n| NewRelicDotNetAgent_10.46.1_x86.msi | 2B512766FB68478515AC294FA9BBD1174766635E5BCC515562E72B9DB724472D |\r\n| NewRelicDotNetAgent_10.46.1_x86.zip | 575E9F6E8F18435A2FB75F0AC2C85D360A85618D5B37A587C6FDA37F66C7E855 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-46-1","eolDate":"2026-11-11"},{"agent":"dotnet","date":"2025-10-30","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.46.0","features":[".NET 10 Support.","Add environment variable support to enable/disable browser agent."],"bugs":["AgentHealthReporter runs when the agent is disabled via config.","Remove service bus distributed trace header manipulation from Azure Function instrumentation."],"security":[],"supportedOperatingSystems":null,"description":"New features .NET 10 Support (#3271 ) (3b03e65 ) Add environment variable support to enable/disable browser agent (#3279 ) (faec9a9 ) Fixes AgentHealthReporter runs when the agent is disabled via config (#3267 ) (76154c9 ) Remove service bus distributed trace header manipulation from Azure Function instrumentation. (#3274 ) (e21eca0 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.46.0-1.x86_64.rpm | C4BDDCA5B5EC3443B919F7FE463B6813C31BF67DAA628FE5788A43EFE31EBFCB |\r\n| newrelic-dotnet-agent_10.46.0_amd64.deb | 672554853A77E864C60D2D9AC270024192F953896865856B771A9598F4961034 |\r\n| newrelic-dotnet-agent_10.46.0_amd64.tar.gz | 94D732591BA75CE7B45827ABD866827589961E215A9B738D8F33960756AD4A9B |\r\n| newrelic-dotnet-agent_10.46.0_arm64.deb | 9DD5CEAE791F655636BCB32A2C96BF552939D2A00CBF4EA7266FBDCBC840BF9D |\r\n| newrelic-dotnet-agent_10.46.0_arm64.tar.gz | 0208041F67E343549CFC4C369203B78C57E45FBD05F1A2857FA8AA54A963BDF8 |\r\n| NewRelicDotNetAgent_10.46.0_x64.msi | B99264713D9D61218D460C31E1AFA4258195CB4B5DF0CB6C816E3C4AE3C7E683 |\r\n| NewRelicDotNetAgent_10.46.0_x64.zip | BFA3E6EB94D32A2BD56B29F6A6FEADDCB62758AD89E82656628BA9B3F0DA068B |\r\n| NewRelicDotNetAgent_10.46.0_x86.msi | D9F70E85E490C28683ABC18445605A16B3763639DE32326EC0250DCA3789D77B |\r\n| NewRelicDotNetAgent_10.46.0_x86.zip | 7504B983945D8BFA58145DBF237C7B818F5A23CA3FCE7C6F1BB5AD52550D8266 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-46-0","eolDate":"2026-10-30"},{"agent":"dotnet","date":"2025-10-01","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.45.0","features":["Add a new Distributed Tracing sampler, the TraceId Ratio-Based Sampler, which is based on the [OpenTelemetry implementation](https\":\"//github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry/Trace/Sampler/TraceIdRatioBasedSampler.cs)."],"bugs":["MSSQL connection string parsing can throw exceptions and disable Datastore instrumentation.","Resolve issues with Kafka \"Consume\" instrumentation to ensure that automatic instrumentation works in conjunction with custom instrumentation."],"security":[],"supportedOperatingSystems":null,"description":"New features Add a new Distributed Tracing sampler, the TraceId Ratio-Based Sampler, which is based on the OpenTelemetry implementation . This sampler makes its sampling decision using the TraceId (a random GUID) and a configured sampling ratio (a target percentage of traces to be sampled).  For more information, see the OpenTelemetry specification . (#3211 ) (63ca603 ) Fixes MSSQL connection string parsing can throw exceptions and disable Datastore instrumentation (#3263 ) (cdf000b ) Resolve issues with Kafka \"Consume\" instrumentation to ensure that automatic instrumentation works in conjunction with custom instrumentation. (#3257 ) (1dbd1c5 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.45.0-1.x86_64.rpm | DB84CEDFB00587787FF38EEAF6DFB61C83B85C6BACEB7337A766044906EC2CBC |\r\n| newrelic-dotnet-agent_10.45.0_amd64.deb | A02281A0F5A183D8F5617F495AA8F6D6670BCE8A6268550DFBBE83354A63747B |\r\n| newrelic-dotnet-agent_10.45.0_amd64.tar.gz | 435C3C71256C7A2E94FC70E130D205062B88ED345B5498207B52C8C2933AACDD |\r\n| newrelic-dotnet-agent_10.45.0_arm64.deb | BD78EB57B31D7F438D45E15EE802BF62A38D805782EFD421543DC41DEA8779B2 |\r\n| newrelic-dotnet-agent_10.45.0_arm64.tar.gz | 2D8B2B919818D5A256A691753DB5FBB73F395E1F8235471F9016967586CAAF9E |\r\n| NewRelicDotNetAgent_10.45.0_x64.msi | 4DB6BC55B292E09F0E9BC81231232E90C62CFFD005AE612F803701B9E34D908E |\r\n| NewRelicDotNetAgent_10.45.0_x64.zip | 18E2EA211703DF077E5D80B929920C2C2F8C95182D1300564E88A6136393E538 |\r\n| NewRelicDotNetAgent_10.45.0_x86.msi | DFC319D553813406AB8CBCF427B082468D648FD07F3F04F82AB4AA2D01C2176E |\r\n| NewRelicDotNetAgent_10.45.0_x86.zip | 7D9390473D9319BE311B2C8FF067106328FB1343B4C86110BB39B231E09E58D0 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-45-0","eolDate":"2026-10-01"},{"agent":"dotnet","date":"2025-08-20","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.44.1","features":[],"bugs":["Exception incorrectly handled in Service Bus instrumentation wrapper.","Exclude Azure Function webhost (Linux) process from instrumentation."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Exception incorrectly handled in Service Bus instrumentation wrapper. (825cd2b ) Exclude Azure Function webhost (Linux) process from instrumentation. (#3223 ) (e363aea ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.44.1-1.x86_64.rpm | FC0C7710DACFF73B4642644CDAEBC8D0B9D90055C27392572D65405BE3AD98BF |\r\n| newrelic-dotnet-agent_10.44.1_amd64.deb | 6FAD41A1058A5880CA00ABBBD82976AC44023703F4E53655633A61FD756C2BE9 |\r\n| newrelic-dotnet-agent_10.44.1_amd64.tar.gz | 81023010263C03071C063346B88776DC7CA783E2B5F1269C942EEBA98804005E |\r\n| newrelic-dotnet-agent_10.44.1_arm64.deb | 8E7C609B1E26784261AC0B60BA98B976C4588F48951D70052C92FDCD111D6545 |\r\n| newrelic-dotnet-agent_10.44.1_arm64.tar.gz | CFB7C711697EB155E27C59E7EAAE2FCA83007407E8F5242DAE9A859E7E167734 |\r\n| NewRelicDotNetAgent_10.44.1_x64.msi | DF4D8C74B4E0C8EE0CB68A326C8E5313E796B8BA98A895142B42977A0FF7E638 |\r\n| NewRelicDotNetAgent_10.44.1_x64.zip | 33EA0E4E4454AACC8430944E42A75AB42F3C289BBF0E62272D4A2D72E9E118D4 |\r\n| NewRelicDotNetAgent_10.44.1_x86.msi | CDFB7F3E436ADFE3399D3DDC50DB3AE2C7B1EDB67D5F3E2E865462E2B6B27EB9 |\r\n| NewRelicDotNetAgent_10.44.1_x86.zip | A951D4527249D48A23BF32A8A78A4D0C141F0A2196CCF7C4536F85C717A0DEF1 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-44-1","eolDate":"2026-08-20"},{"agent":"dotnet","date":"2025-08-13","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.44.0","features":["Enable performance metric samplers in Serverless mode."],"bugs":["Exclude Azure Function webhost (Linux) process from instrumentation."],"security":[],"supportedOperatingSystems":null,"description":"New features Enable performance metric samplers in Serverless mode (#3199 ) (3fc5ea7 ) Fixes Exclude Azure Function webhost (Linux) process from instrumentation. (#3194 ) (fc20645 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.44.0-1.x86_64.rpm | DE7F50B9146B85BF55F26AB204AD8CA153FB3B010793280755F37388D734D4DA |\r\n| newrelic-dotnet-agent_10.44.0_amd64.deb | E44479786005A2D5B10C02C966E1D04F8D8972788508533DE0508266E91A3546 |\r\n| newrelic-dotnet-agent_10.44.0_amd64.tar.gz | 11BA6A58DD04BECABF3BA2BBCB958EB74B5EC506E61B742DF39B633F59352AC1 |\r\n| newrelic-dotnet-agent_10.44.0_arm64.deb | 6E7B508059C7B6D59CAB552074CA86FFD63A2675B7C480A78C61D6F1EE9330B1 |\r\n| newrelic-dotnet-agent_10.44.0_arm64.tar.gz | 00C4FCB2F3AD5336F1EC974224A5454491AFC367A9CD8C9F11B0CFFA88F2EE52 |\r\n| NewRelicDotNetAgent_10.44.0_x64.msi | AB4711259E1D94CB9681B4E010360E66A7158932FC0DAE710E82F8792E3445EF |\r\n| NewRelicDotNetAgent_10.44.0_x64.zip | 9DA0509D694CF1E55666BC089E6122C3B123821B356FD8CDC5379222F4AB8EE0 |\r\n| NewRelicDotNetAgent_10.44.0_x86.msi | 51AAD05459F013ED63B220E03BD557659AB3B4E6A0E8F46F98ADE416CBD15AE8 |\r\n| NewRelicDotNetAgent_10.44.0_x86.zip | 270BC7FE1D4E36D26FDF44A2A83585A56280993998CA3FDC29EC3D649B7EA0E1 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-44-0","eolDate":"2026-08-13"},{"agent":"dotnet","date":"2025-07-09","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.43.0","features":["Add support for topics to Azure Service Bus.","Supportability metrics for custom instrumentation."],"bugs":["Profiler doesn't handle wide-character files correctly."],"security":[],"supportedOperatingSystems":null,"description":"New features Add support for topics to Azure Service Bus. (#3179 ) (d6610a1 ) Supportability metrics for custom instrumentation. Reports the first 25 custom instrumentation methods seen, and a count of the total number of custom instrumentation methods seen. (https://github.com/newrelic/newrelic-dotnet-agent/pull/2797) (99c6256 ) Fixes Profiler doesn't handle wide-character files correctly (#3172 ) (75ddd6b ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.43.0-1.x86_64.rpm | 87AB30791AE82E49F2DCB4E47983BB93A7933DAC6A3C18D0DEB62B3C5D0EB6ED |\r\n| newrelic-dotnet-agent_10.43.0_amd64.deb | 7CD058390C975BE0EC037669C0F46AD75EA821161FADE71D01CFBFCFE674FBDB |\r\n| newrelic-dotnet-agent_10.43.0_amd64.tar.gz | 477B1CF4F0B7951729CE38326B857562F7B50B1DC968D5DFD0F727A90B8374C1 |\r\n| newrelic-dotnet-agent_10.43.0_arm64.deb | F7FF0394F2F7F1295B65256C27F0725191D8B572B2A8BC716A394FE2B85BAA38 |\r\n| newrelic-dotnet-agent_10.43.0_arm64.tar.gz | CBB9F12B4CDACE8E1A77138DFCB7371E221C78212494761CC6915417388623B0 |\r\n| NewRelicDotNetAgent_10.43.0_x64.msi | AD00A5479FE435B2D9D1CC8B8851CD957025390AFC1F849F733D22E37E28E622 |\r\n| NewRelicDotNetAgent_10.43.0_x64.zip | A8F3DFE2ACF3BFC3454D131127018B43C9F61E6009C2D1E63F446B1B2AA7A171 |\r\n| NewRelicDotNetAgent_10.43.0_x86.msi | B761C8245DB2370602D737D2C6EB428BA37F3AFD65B1D47E41ACFDDEE513189A |\r\n| NewRelicDotNetAgent_10.43.0_x86.zip | A60E4AF3593296DD18FDFAE893F1DB04665A0D80E36C08A828986DF27FC7646A | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-43-0","eolDate":"2026-07-09"},{"agent":"dotnet","date":"2025-06-24","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.42.0","features":["Add support for Azure Service Bus."],"bugs":["Fix Profiler build errors with latest VS."],"security":[],"supportedOperatingSystems":null,"description":"Notice As of this release, there is a new public key available for apt.newrelic.com at https://download.newrelic.com/NEWRELIC_APT_2DAD550E.public. This key uses a more secure GPG algorithm than the current public key. If you use APT to install or upgrade the agent on APT-based Linux hosts, we recommend that you switch to using the new key, following the instructions found here: https://docs.newrelic.com/install/dotnet/?deployment=linux&docker=noDocker#apt (1001cf7 ) New features Add support for Azure Service Bus. (#3124 ) (6a075cc ) Fixes Fix Profiler build errors with latest VS (#3162 ) (0cfdedb ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.42.0-1.x86_64.rpm | 85D32AF90B0C968EEF33631F507197F69DAC510AF9E7BAA3E6F479D74A284907 |\r\n| newrelic-dotnet-agent_10.42.0_amd64.deb | 2696F55955D7E0300BCF70A1A2EDC8471A1DBACD2361344C4BD5E003FD582F4C |\r\n| newrelic-dotnet-agent_10.42.0_amd64.tar.gz | AD1B3F3F1D22DD1E539EFAC44B3422654608C26FA72E0BC1D2292D23BBFECC5D |\r\n| newrelic-dotnet-agent_10.42.0_arm64.deb | 126C8F772AD736D1C771C65FEBE25DC827E9734626220081BA3AE2C153E03935 |\r\n| newrelic-dotnet-agent_10.42.0_arm64.tar.gz | D087D4A65E1B441C83B5B7D6C6AFC01E88DD87A7358A180DD0B7E3977D52DF64 |\r\n| NewRelicDotNetAgent_10.42.0_x64.msi | 19C7BC3370F7864257E5870834F3ADFBBD190DE410625B7495631E901508CDFB |\r\n| NewRelicDotNetAgent_10.42.0_x64.zip | 2102CC1D97014142BB42A69224BA84660018F0510B6E09E19E0E509934742E36 |\r\n| NewRelicDotNetAgent_10.42.0_x86.msi | FA98CE97BD02246A5D0413ED64C693F5A045827F32A4B9CA62F14B5534638F46 |\r\n| NewRelicDotNetAgent_10.42.0_x86.zip | 594B7F38FB189EBE24D77A7D5400EB2A80A49E55107B6F00BB006FE96A5CB391 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-42-0","eolDate":"2026-06-24"},{"agent":"dotnet","date":"2025-04-30","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.41.0","features":["Allow incoming W3C traceparent `sampled` flag to influence .NET agent sampling decision."],"bugs":["Null reference exception in Asp.NET Core 6+ browser monitoring injection."],"security":[],"supportedOperatingSystems":null,"description":"New features Allow incoming W3C traceparent sampled flag to influence .NET agent sampling decision. (#3100 ) (6047bda ) Fixes Null reference exception in Asp.NET Core 6+ browser monitoring injection.  (#3102 ) (49df7bf ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.41.0-1.x86_64.rpm | 20E87B1AE872DA5418FF20C6F63C516CEBC4CB3789335092E457333E7DB6034B |\r\n| newrelic-dotnet-agent_10.41.0_amd64.deb | 5CD7CB04237E14615DEDADCAA233E10E7668365D7857576C53815D2D77CA782B |\r\n| newrelic-dotnet-agent_10.41.0_amd64.tar.gz | D358C68D89BB2E9C453311CF2ACA91947B8152459F7CB5BB735D76D9039A896A |\r\n| newrelic-dotnet-agent_10.41.0_arm64.deb | 4100920FFB7B363029EF26F8F5317A333FAC80B57BB6CB41E8032C532184A360 |\r\n| newrelic-dotnet-agent_10.41.0_arm64.tar.gz | 517B415B98B6E4E3370AAB4EB3D225169FCD8E1B51159E259DEDDA010328D374 |\r\n| NewRelicDotNetAgent_10.41.0_x64.msi | E642F1C3BCCED20270E7B550B4EE720B6EC3D599BA93A979BB30BDA5C49E801D |\r\n| NewRelicDotNetAgent_10.41.0_x64.zip | A650D8AB6482A4549EA4FE205CB87610B8225A8AA093A75180CEA403DEC2B858 |\r\n| NewRelicDotNetAgent_10.41.0_x86.msi | 0E736DA3B0B0376581E40ED88C958B4597E1B3A22F64ACFB0CAB5E4BA3DF5143 |\r\n| NewRelicDotNetAgent_10.41.0_x86.zip | CF6DC625533B4D9C55DCADF66DDAA7A7C098F7B50C17CA785A57D77CE69CEBDF | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-41-0","eolDate":"2026-04-30"},{"agent":"dotnet","date":"2025-04-16","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.40.1","features":[],"bugs":["Specify a non-infinite timeout when creating `HttpClient` and `SocketsHttpHandler` instances.","When sql explain plan generation fails, don't attempt to generate an explain plan on future invocations of the same query."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Specify a non-infinite timeout when creating HttpClient and SocketsHttpHandler instances. (#3084 ) (6f72158 ) When sql explain plan generation fails, don't attempt to generate an explain plan on future invocations of the same query. (#3075 ) (12e1743 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.40.1-1.x86_64.rpm | E2AA62CC58F96DB3593EAA1F9182590D70B35B11FD25F68E113EBCEE1DA56985 |\r\n| newrelic-dotnet-agent_10.40.1_amd64.deb | DAA85EF654DCC68E34A92E2F83C72021101F7C281F78A6F3EFE9AB22217C7969 |\r\n| newrelic-dotnet-agent_10.40.1_amd64.tar.gz | 2E62E483FF09D42BB7AB9AFFBB603CA13C68F504052CA17E192CFFA024EFBF72 |\r\n| newrelic-dotnet-agent_10.40.1_arm64.deb | E3CB0218C4DDF66F06523AA1DD81A8972A98D9E21A877C56DC758652B2DD7B3B |\r\n| newrelic-dotnet-agent_10.40.1_arm64.tar.gz | F6712C3555CA541676FF07A0F24BCAD5FAAC076D5B1CB2A1753E28ADE3E5BC11 |\r\n| NewRelicDotNetAgent_10.40.1_x64.msi | 76CF8DBE54BE8BF868B953938EC1B6B7B477D25CF8C741119C289296DF49A001 |\r\n| NewRelicDotNetAgent_10.40.1_x64.zip | 5886F5668503498A6080C16569394496E01349A1E7BF5BA37691384082F6D7D0 |\r\n| NewRelicDotNetAgent_10.40.1_x86.msi | DDD5E8F4B8A23A57D90F3BC89D91B9788848D2D43E1DE0DF400396FAD1286374 |\r\n| NewRelicDotNetAgent_10.40.1_x86.zip | 3CC2A11BB0C2C256DD005FF0D6AF4EC24F4BD4C496E0B1860FAE261349CFFA5B | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-40-1","eolDate":"2026-04-16"},{"agent":"dotnet","date":"2025-04-02","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.40.0","features":["Add Couchbase 3.x instrumentation.","Add instrumentation for AWS Kinesis Data Streams and Kinesis Delivery Streams (Firehose).","Add support for MongoDB.Driver 3.x and above."],"bugs":["Add more null checks to Asp.NET Core 6+ browser instrumentation logic.","In-process Azure Function publishes Nuget agent DLLs to the wrong folder.","Profiler should not log \"with parent process\" unless parent process is non-empty."],"security":[],"supportedOperatingSystems":null,"description":"New features Add Couchbase 3.x instrumentation (#3048 ) (7ef0c82 ) Add instrumentation for AWS Kinesis Data Streams and Kinesis Delivery Streams (Firehose) (7b52a67 ) Add support for MongoDB.Driver 3.x and above. (#3065 ) (c8acbc5 ) Fixes Add more null checks to Asp.NET Core 6+ browser instrumentation logic (#3070 ) (5f5cf12 ) In-process Azure Function publishes Nuget agent DLLs to the wrong folder (#3068 ) (ee04d25 ) Profiler should not log \"with parent process\" unless parent process is non-empty (#3066 ) (a6c6d7d ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.40.0-1.x86_64.rpm | 2A407D56559A9A435C403ADBC4D2460B2F069D0BF31BED5939FEA4610AC39DCD |\r\n| newrelic-dotnet-agent_10.40.0_amd64.deb | 82BD0FD01827F71552C7B6B8DB27AF1E39FF9EE32D8A5A8B505C82FF9E099569 |\r\n| newrelic-dotnet-agent_10.40.0_amd64.tar.gz | 6B11DDD981972BD5CAEB1862389B82830741DEE46249CF33EF5DA0C8E9846F59 |\r\n| newrelic-dotnet-agent_10.40.0_arm64.deb | 09DDD05630AC17ABCCB8B7712E22E45C91BD83B0BC6921BB439AE4EFF98A9E90 |\r\n| newrelic-dotnet-agent_10.40.0_arm64.tar.gz | A84E7B9295AD3F27D7F5CBD81B49BC37A8C68E3B388C03D53E67EED3B8E2C7E6 |\r\n| NewRelicDotNetAgent_10.40.0_x64.msi | 3594F40FF0AFD167C069075AC682F2B937D1CE2E2E119C4519A187ACD05C59C7 |\r\n| NewRelicDotNetAgent_10.40.0_x64.zip | B65E62C60FCC3365E158ACEB54AD1079146CF1E081AB54EAD57D51798DF268B4 |\r\n| NewRelicDotNetAgent_10.40.0_x86.msi | 4447396404182E602C33C6D803CC054E8C97BEB5954D8EC56965463BFB4B2215 |\r\n| NewRelicDotNetAgent_10.40.0_x86.zip | DE9147661B2826E2AF6B5FE64C4F4385BDCBA357F16DD5DD17FC6BE4E190B2DB | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-40-0","eolDate":"2026-04-02"},{"agent":"dotnet","date":"2022-12-06","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.4.0","features":["Verified support for .NET 7 applications","Add option to capture and forward log context data","Include Arm64 profiler in Agent NuGet package","Improve logging when attribute limits are reached"],"bugs":["Fix potential crash when using Infinite Tracing"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date . As of this release, the oldest supported version is .NET agent 8.22.181.0 . New Features Support for .NET 7 has been verified with the GA version of the .NET 7 SDK. Please note that if you use dynamically-created assemblies , there is a bug in .NET 7  that prevents them from being instrumented at this time. Application log fowarding can now be configured to capture and forward context data to New Relic.  Details (including how to enable and configure this new feature) can be found here . The NewRelic.Agent NuGet package  now includes the Linux Arm64 profiler. This can be found in the newrelic/linux-arm64 directory. Configure your CORECLR_PROFILER_PATH environment variable to use this version of the profiler when deploying to linux ARM64 targets. When finest logs are enabled, the transaction guid will be applied to attribute limit log messages, if present. Fixes Resolves potential crash when using Infinite Tracing. #1319 Once published, the release artifacts for this release can be found at https://download.newrelic.com/dot_net_agent/latest_release/  or on NuGet.org. Checksums | File                                      | SHA - 256  Hash                                                  |\n| ----------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.4.0-1.x86_64.rpm | 7A1E1F2A669D7043C7BCAEE0DF13993928CAC392981253F3AB443ADC5E280EB2 |\n| newrelic-dotnet-agent_10.4.0_amd64.deb    | 21B067F89092F95CD8420BFE285A8B034F7BF25E8FDF04353934F59FE862D761 |\n| newrelic-dotnet-agent_10.4.0_amd64.tar.gz | 375B4EE5F5E3471E1C2CC8029F07EEA1613D113EB9490B3F852043076E5B4038 |\n| newrelic-dotnet-agent_10.4.0_arm64.deb    | 5EDED9749F2877074ABEB10480F4DF351C6EB25B2CB971A25284CADBABFF0EE7 |\n| newrelic-dotnet-agent_10.4.0_arm64.tar.gz | D60ED7376AD3C82F6C0ED0A57386D3CBF98D5FB003343278C74E5B894ABD57E9 |\n| NewRelicDotNetAgent_10.4.0_x64.msi        | 0F7FA6A0EC37362A4575DD4C300F74D2B616AE5817EB9A36E7100C9AE185D970 |\n| NewRelicDotNetAgent_10.4.0_x64.zip        | ECA525FC60AAFA1B7B671C7F380D7AB4C35DA2B123A87E2C34C57C5EB118ECD8 |\n| NewRelicDotNetAgent_10.4.0_x86.msi        | A216AD012037C418BAF09D0C3795D0CDE5B458070504985E2C1E567DCF7E4D03 |\n| NewRelicDotNetAgent_10.4.0_x86.zip        | B8B849A860A7AFBD18931179EEB5C18722D3AD5F2EEF8ABF26BDC811BD791B59 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-4-0","eolDate":"2023-12-06"},{"agent":"dotnet","date":"2025-03-19","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.39.0","features":["Enable ASP.NET Core browser auto-injection by default.","Instrument In-Process Azure Function invocations, with distributed tracing support for Http and Service Bus triggers."],"bugs":["Look for `ASPNETCORE_IIS_APP_POOL_ID` if `APP_POOL_ID` isn't found.","Remove diagnostics tracing output from agent API calls.","Remove unnecessary dependency on `System.Runtime.InteropServices.RuntimeInformation` in .NET 4.6.2  builds.","Set Profiler logger to initialized when configuration load fails."],"security":[],"supportedOperatingSystems":null,"description":"Notice Automatic browser agent injection for ASP.NET Core v6+ web applications has been enabled by default. If you experience any issues with this feature, please see item 2 on this page  for a setting that can be set to false to disable the feature and contact us for support . (051ceab ) New features Enable ASP.NET Core browser auto-injection by default. (051ceab ) Instrument In-Process Azure Function invocations, with distributed tracing support for Http and Service Bus triggers. (#3003 ) (47d22a1 ) Fixes Look for ASPNETCORE_IIS_APP_POOL_ID if APP_POOL_ID isn't found. (#3036 ) (620064c ) Remove diagnostics tracing output from agent API calls (#3029 ) (be7b7f4 ) Remove unnecessary dependency on System.Runtime.InteropServices.RuntimeInformation in .NET 4.6.2  builds. (#3033 ) (ab81d1c ) Set Profiler logger to initialized when configuration load fails. (#3015 ) (7ab30d7 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.39.0-1.x86_64.rpm | F6156B36FB3772774853D52E9EF8B0566954F0167B92CB55CCBA1ABAA64D1AC5 |\r\n| newrelic-dotnet-agent_10.39.0_amd64.deb | 263E95CAFF0FAB2DB7BB9605E2FCA6E6F5618F10F11DFF2DCE81A14884AC9515 |\r\n| newrelic-dotnet-agent_10.39.0_amd64.tar.gz | C2A68808DD66261E753336711AD1F172019B5FF27ADED70CDBAB93EA09D24842 |\r\n| newrelic-dotnet-agent_10.39.0_arm64.deb | C61BDD208605464F1CDA4888D30BA3C2E05981C0E9CFD5D4B820BFF7D40AF5EC |\r\n| newrelic-dotnet-agent_10.39.0_arm64.tar.gz | FB199C303167FEA0E288D4F34774BC00E95563D15B5E820A335C5A4E35F392EE |\r\n| NewRelicDotNetAgent_10.39.0_x64.msi | DE865CB9BEF672AA3DB0EB81182C95DC8BF4AC822ADB08E4FE31835ED8017091 |\r\n| NewRelicDotNetAgent_10.39.0_x64.zip | 4C1044998AE5E4834E857D3B08D6610CD92E063F6CC72DBF5CCE69727F3E8E21 |\r\n| NewRelicDotNetAgent_10.39.0_x86.msi | 34AB182949FF42D83B9CE8C4FB937257DEEBAB3C21D76CA387886B27EEEFF6FF |\r\n| NewRelicDotNetAgent_10.39.0_x86.zip | BCFA9B2EC1450DDB2B935B393C9B2B499C83603817384BA638F610C35F848444 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-39-0","eolDate":"2026-03-19"},{"agent":"dotnet","date":"2025-03-05","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.38.0","features":["Add support for PackageReference with NewRelic.Azure.WebSites packages.","Azure Function instrumentation is enabled by default."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New features Add support for PackageReference with NewRelic.Azure.WebSites packages. (#3001 ) (8fb397f ) Azure Function instrumentation is enabled by default (#3007 ) (8eba1bf ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.38.0-1.x86_64.rpm | 5C94851B96A38D4B7D152BB97710A79D37019E6D5710C8A530C0AAF432E343A3 |\r\n| newrelic-dotnet-agent_10.38.0_amd64.deb | C754278CFA8CCBD23A831E0B70E63F77718ED89EB3C6EC2C84F47075A32F9BBA |\r\n| newrelic-dotnet-agent_10.38.0_amd64.tar.gz | EF2E9F9C76B31BE3B05CCFC96976A6677A1D91532B35CE51B7C946E6649C421F |\r\n| newrelic-dotnet-agent_10.38.0_arm64.deb | 05B6E12577B78A35255236FD0F2C0852884F0992F3F3620ABF5B3D0A81BD7C0B |\r\n| newrelic-dotnet-agent_10.38.0_arm64.tar.gz | 1C442C187D35FE8532806FEB159F519031FFF94BA03FA5304DF51DD7F005F8A9 |\r\n| NewRelicDotNetAgent_10.38.0_x64.msi | 6910F6610965C0D7687FED378F2626116334177A936B6DB74A24D53A488EC393 |\r\n| NewRelicDotNetAgent_10.38.0_x64.zip | 54440E5F01F2C0EC1EF58EC7C915A92356D73A078BAED1E2C83D99F00AC1592C |\r\n| NewRelicDotNetAgent_10.38.0_x86.msi | 5C253FDEF7EA54550A5D7F532A46D095A34722D02D3430F2A04A9C8E8B410495 |\r\n| NewRelicDotNetAgent_10.38.0_x86.zip | ECCBE88B4C6E6913D1183E94AE760F1EA548970960F06A8B458678F6E2A9C8A6 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-38-0","eolDate":"2026-03-05"},{"agent":"dotnet","date":"2025-02-19","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.37.0","features":["Add AI Monitoring instrumentation for `AmazonBedrockRuntimeClient.ConverseAsync()`.","Add AI Monitoring instrumentation for OpenAI and Azure.AI.OpenAI.","Add support for .NET Framework Azure Function Apps.","Improve logging and validation for license keys."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New features Add AI Monitoring instrumentation for AmazonBedrockRuntimeClient.ConverseAsync() (#2997 ) (cdc2f6c ) Add AI Monitoring instrumentation for OpenAI and Azure.AI.OpenAI (#2987 ) (aa06d9d ) Add support for .NET Framework Azure Function Apps (#2992 ) (5b077f3 ) Improve logging and validation for license keys. (#2982 ) (19e8387 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.37.0-1.x86_64.rpm | 3852B2A27A75FB1983C34D9403091BA3311F7FCC43EA48A1321A8733739AC505 |\r\n| newrelic-dotnet-agent_10.37.0_amd64.deb | 20A384451D5C3949B5442E0C742ECD9573A2CEE8776789893B8D8F56F81DA2B5 |\r\n| newrelic-dotnet-agent_10.37.0_amd64.tar.gz | FC0263475AF6C49BBD925C060F2A8BD97CA01731040B685A307E01F6040CD433 |\r\n| newrelic-dotnet-agent_10.37.0_arm64.deb | 7B0BA1986BE52D7254C5A7455A93862634C3BC89C0AC22D3D4859AB665864C2B |\r\n| newrelic-dotnet-agent_10.37.0_arm64.tar.gz | FD60250AF6AD1437CA114ABD660B22E7407C153CC55EC9EC870641AEF6BB4F47 |\r\n| NewRelicDotNetAgent_10.37.0_x64.msi | 7945D0F524C43278F69761F84D4CA11A915A90974E87A0D0FF22C124F1557C3A |\r\n| NewRelicDotNetAgent_10.37.0_x64.zip | 1C31D39F5F315F2C131E9190E2061F496D0C27F54CD3A8EC14FB2E9BE959965A |\r\n| NewRelicDotNetAgent_10.37.0_x86.msi | AEB95BA464DD51D72AF7899DD4F6351E2D183A7D84AF0A0F9C2838BBF2DC19D5 |\r\n| NewRelicDotNetAgent_10.37.0_x86.zip | E8BDF4C2F98124DF0428BA541028B3FF8F8C6BD7FC654B5533D8709036E7E24A | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-37-0","eolDate":"2026-02-19"},{"agent":"dotnet","date":"2025-02-05","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.36.0","features":["Add .NET 8+ support for System.Data.Odbc.","Add support for instrumenting OpenSearchClient requests."],"bugs":["Add Azure Function app name prefix to `faas.name` attribute in Azure Function transactions.","Custom attribute values of type float and decimal were not serialized correctly.","Improve error handling in AWS account ID parsing logic."],"security":[],"supportedOperatingSystems":null,"description":"New features Add .NET 8+ support for System.Data.Odbc (#2948 ) (7ee9825 ) Add support for instrumenting OpenSearchClient requests. (#2956 ) (4309938 ) Fixes Add Azure Function app name prefix to faas.name attribute in Azure Function transactions. (#2973 ) (80d4c76 ) Custom attribute values of type float and decimal were not serialized correctly. (#2975 ) (8812fe1 ) Improve error handling in AWS account ID parsing logic (#2984 ) (9b66750 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.36.0-1.x86_64.rpm | 91BA7176F99AEE0BC3817F00371A13481356F63E000E57141FBEE2A7BAAFB68B |\r\n| newrelic-dotnet-agent_10.36.0_amd64.deb | 807C95FE01ECAD96C7120D2264DBADFF9FBD4BA761B574BEE08D8CC0268A69E4 |\r\n| newrelic-dotnet-agent_10.36.0_amd64.tar.gz | 9CA4753487DF4B87C99C5A64D9CF772BFF100EABD90F964682FDD4ECB4D87CD8 |\r\n| newrelic-dotnet-agent_10.36.0_arm64.deb | E6DC9B2395CEEF228A53960321A9B41E056CA967805610E414973A4B6E3A30C9 |\r\n| newrelic-dotnet-agent_10.36.0_arm64.tar.gz | F8AE80A25CE634BB4307D0035ABDC3DB8D5B11835C4BE3E353AF62F694409884 |\r\n| NewRelicDotNetAgent_10.36.0_x64.msi | 52D24B0B05449CB09BF01DD659FCD4A50F5C10BF243BD248B16935A9660B8BB7 |\r\n| NewRelicDotNetAgent_10.36.0_x64.zip | 22CF5D61002EFB0E7DD04B1E03F09ED0B2143CAF8D01C95D9C02EF21025EA5AF |\r\n| NewRelicDotNetAgent_10.36.0_x86.msi | F66B1708D384D48603205768CA7AECACD700673CA86F361D9C7D0370944FDFEA |\r\n| NewRelicDotNetAgent_10.36.0_x86.zip | 15588F3BC4D33756E117BC8680B3B8AAE02757751443ADBDA88EF0E75ABD09A1 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-36-0","eolDate":"2026-02-05"},{"agent":"dotnet","date":"2025-01-22","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.35.0","features":["Enable DynamoDB entity relationships.","Instrument Lambda invocations in AWS SDK.","Use `SocketsHttpHandler` to configure `HttpClient` in .NET 6+."],"bugs":["Console logging is inconsistent between Agent and Profiler.","Incorrect string comparison in the profiler caused constructor instrumentation to fail on Linux.","Refactoring to reduce the likelihood of a deadlock in `HttpClient.SendAsync()`."],"security":[],"supportedOperatingSystems":null,"description":"New features Enable DynamoDB entity relationships (#2923 ) (f70b64a ) Instrument Lambda invocations in AWS SDK (#2901 ) (3b655e4 ) Use SocketsHttpHandler to configure HttpClient in .NET 6+. (#2931 ) (eb3afda ) Fixes Console logging is inconsistent between Agent and Profiler (#2955 ) (7c42b33 ) Incorrect string comparison in the profiler caused constructor instrumentation to fail on Linux (#2912 ) (49a71c5 ) Refactoring to reduce the likelihood of a deadlock in HttpClient.SendAsync(). (#2931 ) (eb3afda ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.35.0-1.x86_64.rpm | 6F9D54B1643381BF2A84728615509608B4A6E270F6F6B0FD58179DBBF2516192 |\r\n| newrelic-dotnet-agent_10.35.0_amd64.deb | B920D3C3B9B71DB3E05927B13AE996C6A6295B61AB9A54C0959D40FFB28B167B |\r\n| newrelic-dotnet-agent_10.35.0_amd64.tar.gz | CEC51A855F30AB1270661D37B5C74FD506D8C81B9202A387C3F26FCE835D4143 |\r\n| newrelic-dotnet-agent_10.35.0_arm64.deb | 9A171F16C37BB543997CB23F209B1212F1DF82B157FFA85CDC90DD20CC3DD148 |\r\n| newrelic-dotnet-agent_10.35.0_arm64.tar.gz | 27848A1A403C2AC67B4F3B0BFFE55E1520DBE19C384568A613E57C0A2A9B7267 |\r\n| NewRelicDotNetAgent_10.35.0_x64.msi | 9E1E949B762BB0F3B93F94C2FEFC31E2990C71E3E772FE072FA620FE6507F15B |\r\n| NewRelicDotNetAgent_10.35.0_x64.zip | F7680D5C2B03374B80F874AB25AFDB8E1E6767D6E22DFA95B8A5FFE68AA79116 |\r\n| NewRelicDotNetAgent_10.35.0_x86.msi | DB82A5316EB90DEAB94CD8F219E4F1F704FBA038546883996AA27CFD211B248A |\r\n| NewRelicDotNetAgent_10.35.0_x86.zip | 6464A271E9227CC44D5D127BCE6CBAFB073DEC1862887676568C43D37E3F9D1C | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-35-0","eolDate":"2026-01-22"},{"agent":"dotnet","date":"2024-12-04","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.34.1","features":[],"bugs":["Remove .NET Standard libraries from .NET Framework target."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Remove .NET Standard libraries from .NET Framework target (#2896 ) (0873941 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.34.1-1.x86_64.rpm | 66F1700E3FD8F97B2F80EB1FB6D9A79CE47F67D8ADBC1FE78CDBB5D4E9C96E92 |\r\n| newrelic-dotnet-agent_10.34.1_amd64.deb | DD6A87581F2D06E5C4CC3B3086B1AE8D8600ADEC8603DED71E9E1D59E8494F97 |\r\n| newrelic-dotnet-agent_10.34.1_amd64.tar.gz | 86C126A09C232931A7523CEDD125E20C11D105547C5ED5C4CB246F7A4937F210 |\r\n| newrelic-dotnet-agent_10.34.1_arm64.deb | 08C186573EF6FC1096E7445FECCA04E1DB0B4B0A8145933574A40B4483BBE402 |\r\n| newrelic-dotnet-agent_10.34.1_arm64.tar.gz | E25DB5F632776042EA57DCE4DF0F9A9E2A13933ED8B0422B86ECD5987E27C775 |\r\n| NewRelicDotNetAgent_10.34.1_x64.msi | 7640AA107DDF0C26E586C0C5594AE843CB4F71625224050B6A9977DA59D7706E |\r\n| NewRelicDotNetAgent_10.34.1_x64.zip | ACA4B6AF67D83F353BC2D9FE1B946522BCF7C16D2980EDAEE757F9FAF4651545 |\r\n| NewRelicDotNetAgent_10.34.1_x86.msi | 93EACCB74BE6FE92A7513EF666698AECD1C132E24536406632397504BAAEDF40 |\r\n| NewRelicDotNetAgent_10.34.1_x86.zip | 0EAED401B591C7788040741495F745A9BC06B991BB5E0280D37D509515336400 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-34-1","eolDate":"2025-12-04"},{"agent":"dotnet","date":"2024-11-19","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.34.0","features":["Add Distributed Tracing support for Azure Functions HTTPTrigger.","The .NET agent now allows you to opt-in to adding your custom tags (labels) to agent-forwarded logs."],"bugs":["Don't instrument certain processes in Azure Linux App Service deployments.","Fix a bug in `run.sh`."],"security":[],"supportedOperatingSystems":null,"description":"Notice The .NET agent now allows you to opt-in to adding your custom tags (labels) to agent-forwarded logs. With custom tags on logs, platform engineers can easily filter, search, and correlate log data for faster and more efficient troubleshooting, improved performance, and optimized resource utilization. To learn more about this feature see the documentation .(https://github.com/newrelic/newrelic-dotnet-agent/pull/2831) (d1e29ea ) New features Add Distributed Tracing support for Azure Functions HTTPTrigger. (#2868 ) (0278836 ) The .NET agent now allows you to opt-in to adding your custom tags (labels) to agent-forwarded logs. With custom tags on logs, platform engineers can easily filter, search, and correlate log data for faster and more efficient troubleshooting, improved performance, and optimized resource utilization. To learn more about this feature see the documentation .(https://github.com/newrelic/newrelic-dotnet-agent/pull/2831) (d1e29ea ) Fixes Don't instrument certain processes in Azure Linux App Service deployments. Resolves #2871 . (7ed945b ) Fix a bug in run.sh. Resolves #2887  (#2888 ) (df17cfd ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.34.0-1.x86_64.rpm | 6D79C44A4C2E96286CF3F1C12E07838DC65CE9A474CC86407F6B4DF6D346656C |\r\n| newrelic-dotnet-agent_10.34.0_amd64.deb | 444BF2BA93B0E95FCE916CE7BFCA26A9A221830B368D86F1B738B47B50F38D1F |\r\n| newrelic-dotnet-agent_10.34.0_amd64.tar.gz | 338120A20039D49F27CB48D1CB940540660F0F9FB4BBEC98CAF097810ED8C88B |\r\n| newrelic-dotnet-agent_10.34.0_arm64.deb | 371269E295ECB425FAE120DF2E7AB0A1AFA2520A451B8A83BE16BCBE0ABD3957 |\r\n| newrelic-dotnet-agent_10.34.0_arm64.tar.gz | A008918C7A97D988023DBE43E46C4A118EDB2073E25DF9D95B3794F71E7674B5 |\r\n| NewRelicDotNetAgent_10.34.0_x64.msi | 8B889669F8CB6DBD437D626B3C4252B5C95C223FACEB3CFB02544C62FCAFDE5B |\r\n| NewRelicDotNetAgent_10.34.0_x64.zip | 629A6FD8A3F856AE40F6F77C60DF17321E92003B44F88960CA1A32734B269455 |\r\n| NewRelicDotNetAgent_10.34.0_x86.msi | E1BE19B96B41C3640067FDD20DCCF5DDB43ED38DA0786C34A2B8D0DE8F4459A6 |\r\n| NewRelicDotNetAgent_10.34.0_x86.zip | 5292B803BCB1D01F0F50F74383D2D37EB9F5874CDD5FD7C3822B8F695789F7AE | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-34-0","eolDate":"2025-11-19"},{"agent":"dotnet","date":"2024-10-31","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.33.1","features":[],"bugs":["Fix syntax error in `setenv.sh`."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Fix syntax error in setenv.sh (#2864 ) (a629138 ), closes #2863 Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.33.1-1.x86_64.rpm | 6DFF96A2017167A96E9E4F95B963931C11092B97B8A029575E5408B6ED0A4B6B |\r\n| newrelic-dotnet-agent_10.33.1_amd64.deb | 337B8A545EFE0F67A9323258F5483815B99E8644236F4D7ADE1134E59417B6A8 |\r\n| newrelic-dotnet-agent_10.33.1_amd64.tar.gz | 72A981FD44B9CBC0FDEAFD7EF23AB0B2952D46946C8CBBE867CCAFB2FDDCA9C5 |\r\n| newrelic-dotnet-agent_10.33.1_arm64.deb | 9FDA286CEEBDC73A7A3A03B3FA5E18B6857C7EDB12754BACFB3F30C9815FF193 |\r\n| newrelic-dotnet-agent_10.33.1_arm64.tar.gz | B75D3093CC46F3931C5076B24C1E6DA184D49D40421706CA228ED2EB27721FB1 |\r\n| NewRelicDotNetAgent_10.33.1_x64.msi | F96A7D40F2CAF2CDBF1C8EF0D3BFF44E68BEFE2DD6BB9F2274B226F9B83C29E3 |\r\n| NewRelicDotNetAgent_10.33.1_x64.zip | 156E5935B805F8936E978D1C9F4ED43E952C856D2C9EA5A143765885C8D336A2 |\r\n| NewRelicDotNetAgent_10.33.1_x86.msi | 34F3582C206B5E1C4CD2B0698E5BA3BCC347BBCA74543A3CBBD6688B7232B0C5 |\r\n| NewRelicDotNetAgent_10.33.1_x86.zip | B5FC14F24B9FAA066BE93233FF6B74C7FE655DE549B6E6062D108AF3697B2BD5 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-33-1","eolDate":"2025-10-31"},{"agent":"dotnet","date":"2024-10-30","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.33.0","features":["Add AWSSDK.DynamoDBv2 instrumentation.","Add config option for providing AWS account ID for linking.","New Garbage Collection Metrics Sampler for .NET 6+."],"bugs":["Fix potential race condition in AWS SDK, AWS Bedrock, and Elastisearch that could lead to an orphaned Transaction.","Remove usage of non-thread safe HashSet in AwsSdk pipeline wrappers.","Revert environment variable name change in installers and scripts."],"security":[],"supportedOperatingSystems":null,"description":"New features Add AWSSDK.DynamoDBv2 instrumentation.  Versions 3.5 through 4.0.0-preview.4 are supported.  Note: previous agent versions would instrument DynamoDB calls as Externals; now DynamoDB calls will show up as Database operations in the New Relic UI. (2460527 ) Add config option for providing AWS account ID for linking (#2851 ) (936b6f6 ) New Garbage Collection Metrics Sampler for .NET 6+ (#2838 ) (f24a5da ) Fixes Fix potential race condition in AWS SDK, AWS Bedrock, and Elastisearch that could lead to an orphaned Transaction. (#2842 ) (3afa15f ) Remove usage of non-thread safe HashSet in AwsSdk pipeline wrappers. Thanks, @gjunge ! (#2855 ) (#2857 ) (ae1d422 ) Revert environment variable name change in installers and scripts (#2852 ) (e77683b ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.33.0-1.x86_64.rpm | F5CBE9937294163ECC8D3F8C0FEB72DBA8F89F1E79E5F3B9AD0F244F14E86328 |\r\n| newrelic-dotnet-agent_10.33.0_amd64.deb | 6B0DADD9D4D1DCBA3915E050878DDB0110DDF06D4EEC30A647E1996F74EDFC5B |\r\n| newrelic-dotnet-agent_10.33.0_amd64.tar.gz | 50BFCF1EF7FB3D660C92706676C9F55309461D596E2391CCBCD2ADE1F53B9971 |\r\n| newrelic-dotnet-agent_10.33.0_arm64.deb | 42CE2986A6B948C425EE5BBCF0FCC52E6556B318A8470A0BD9AE5E9685FDDC23 |\r\n| newrelic-dotnet-agent_10.33.0_arm64.tar.gz | B82C358F40F81CA5A53191C16DC1258DE59FD264C7FDD4180CF4E72AD64BAB06 |\r\n| NewRelicDotNetAgent_10.33.0_x64.msi | 11A89BA94BC535344AF75DFEE9C5C317CA2C3E2F27AF3AECAA61F9DB01408DB9 |\r\n| NewRelicDotNetAgent_10.33.0_x64.zip | 8AE550001EC5CDEFA51E234F84D4F135E8103A0E51ECE8B5251AD988F283F1E7 |\r\n| NewRelicDotNetAgent_10.33.0_x86.msi | 1599C0DA0BB8D54D7EDF4885FAE2073644E6B450DEDB9DA4A43614E117620089 |\r\n| NewRelicDotNetAgent_10.33.0_x86.zip | F65185B5558DBCEEA1C093671D413D7AC679312EF1EF70C69A194C759C1CFC7F | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-33-0","eolDate":"2025-10-30"},{"agent":"dotnet","date":"2024-10-16","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.32.0","features":["Implement consistent naming scheme for all environment variables.","Update CosmosDB instrumentation to support latest version."],"bugs":["Handle null or empty SQS messages and/or message attributes.","Update Profiler to check whether Azure function mode support is enabled."],"security":[],"supportedOperatingSystems":null,"description":"Notice Environment variables that start with or contain NEWRELIC_ are deprecated and may be removed in a future major release. Users are encouraged to update their installation to use NEW_RELIC_ names as soon as possible. (b00edda ) New features Implement consistent naming scheme for all environment variables. All environment variables starting with (or containing) NEWRELIC_ are now named NEW_RELIC_. Support for previous environment variables is retained, so this is not a breaking change. (#718 ) (#2812 ) (b00edda ) Update CosmosDB instrumentation to support latest version (#2832 ) (27a78cb ) Fixes Handle null or empty SQS messages and/or message attributes (#2833 ) (758b770 ) Update Profiler to check whether Azure function mode support is enabled (#2822 ) (9669641 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.32.0-1.x86_64.rpm | 2FFDA6284FAAFD1D803AEA0D101E68CE2BC3DE216843BB447B8942A085B72610 |\r\n| newrelic-dotnet-agent_10.32.0_amd64.deb | 425FF9AE08D2FF21B0CC261BB817B0E99376804B854AEB243D82A62242B4D440 |\r\n| newrelic-dotnet-agent_10.32.0_amd64.tar.gz | 73AF5E32B8CC62EE4715A58389482C88049F8A0CB2BB7A3653136BC75E332A52 |\r\n| newrelic-dotnet-agent_10.32.0_arm64.deb | FC30F4F24F6FBF74C3BF583461A1DE2122E4BB869F6E246BBAC4CB722FE05FB3 |\r\n| newrelic-dotnet-agent_10.32.0_arm64.tar.gz | CD096D73FABF2FF83FFAB86ED64DA49C81EEB73DFB5FBCBDDFBF040C37D71EE3 |\r\n| NewRelicDotNetAgent_10.32.0_x64.msi | 451BE41904B4A6DDAE0278ECA9DAF774A5C6D07BAF3CEFC8C6F676C0C48B07D4 |\r\n| NewRelicDotNetAgent_10.32.0_x64.zip | 7A4F5C455B2CAF56F814F17D08469D4B7ED319F87345B7F5CB785DBF96D6A07A |\r\n| NewRelicDotNetAgent_10.32.0_x86.msi | DE111B96233805F1E113D3321583F8CBE6CD90549869F2A1070C5F77982E0D36 |\r\n| NewRelicDotNetAgent_10.32.0_x86.zip | 158811ECD68577B70A94C8119F8FFDEDC1BE450D2D4F11BF084F0CF9D0ABD20E | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-32-0","eolDate":"2025-10-16"},{"agent":"dotnet","date":"2024-09-25","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.31.0","features":["Add support for the EnyimMemcachedCore client.","Allow container linking for AWS ECS applications.","Parse Azure Function HttpTrigger parameters."],"bugs":["Prevent FileNotFoundException when handling connection issues while instrumenting .NET Framework apps."],"security":[],"supportedOperatingSystems":null,"description":"New features Add support for the EnyimMemcachedCore client. (#2781 ) (52bdc11 ) Allow container linking for AWS ECS applications. (#2683 ) (d55567f ) Parse Azure Function HttpTrigger parameters (#2776 ) (7e8c28b ) Fixes Prevent FileNotFoundException when handling connection issues while instrumenting .NET Framework apps. (#2750 ) (#2751 ) (cebd287 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.31.0-1.x86_64.rpm | D873D277B24335A7D85CEDC0F91F0B9F336D1D68E228201523E5D02150818CDF |\r\n| newrelic-dotnet-agent_10.31.0_amd64.deb | B3CB137FF82A8C4FE1CA1DDA02055358261C5038E60A6BCCA7420398CDBE8C28 |\r\n| newrelic-dotnet-agent_10.31.0_amd64.tar.gz | 1AAB60372C428EA2B7BFD6886ADDF8A86F30FEC8043B50E15446B56B967D3081 |\r\n| newrelic-dotnet-agent_10.31.0_arm64.deb | BC5ACC6DAF08C29529DE8406EF0A2CE4F808EC108C8B217AA7DC41D5C825401D |\r\n| newrelic-dotnet-agent_10.31.0_arm64.tar.gz | 56896886BE4FEE9A72EC92593603DECCB18AF4AEC3102FFAB522ED482B34C5E3 |\r\n| NewRelicDotNetAgent_10.31.0_x64.msi | 530626D7CC66A772A5FEE3C6EC04FEC48B07264F15854B66EAC557097B6E4723 |\r\n| NewRelicDotNetAgent_10.31.0_x64.zip | 70B075004FC8CE503FD43C8056694C5747F2B8B914E21CADB031C5F2F98B0FD5 |\r\n| NewRelicDotNetAgent_10.31.0_x86.msi | 4957674057693770433D32D8765209434640F23A797EFB6FE251B2A2013FD391 |\r\n| NewRelicDotNetAgent_10.31.0_x86.zip | 2A109C02E7331E34EA3BFAD66B17EF607FF458F3DF3C287B66DE619F57C9AC0F | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-31-0","eolDate":"2025-09-25"},{"agent":"dotnet","date":"2024-09-12","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.30.0","features":["Oracle instrumentation now supports latest version.","Preview support for instrumentation of \"isolated\" model Azure Functions."],"bugs":["Preserve custom query name even if statement can't be parsed."],"security":[],"supportedOperatingSystems":null,"description":"New features Oracle instrumentation now supports latest version. (#2721 ) (50cb663 ) Initial support for instrumentation of \"isolated\" model Azure Functions. Instrumentation is disabled by default. (d8a79e5 ) Fixes Preserve custom query name even if statement can't be parsed. (#2708 ) (#2709 ) (3ab0cb4 ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.30.0-1.x86_64.rpm | 7FE531AB9D48EF336A01953C865E40726515A20DB3A1D48BE066D9ADCEF52FB1 |\r\n| newrelic-dotnet-agent_10.30.0_amd64.deb | E2D7E13449DEF79A652B21747E0CAB40915CDA7C127B6D438C27BE531EB21895 |\r\n| newrelic-dotnet-agent_10.30.0_amd64.tar.gz | 5A93A52EC717363A2CA82D3D98F12CE947218392BE4D41EB829427E6268C126E |\r\n| newrelic-dotnet-agent_10.30.0_arm64.deb | BD9A82DEA2CE53484C1D1C45BCCBD9352EB3AC078A3B5499F8F230F7442B1D99 |\r\n| newrelic-dotnet-agent_10.30.0_arm64.tar.gz | 296DD8FEA47D2DE5C2CA342D9424FE6805910FAA24DA41002987FAB4C121B05F |\r\n| NewRelicDotNetAgent_10.30.0_x64.msi | 651CB0B3966B4E2DC0DED189563EF8B5DDF3851EE7C98A7754B693FD36B32FC8 |\r\n| NewRelicDotNetAgent_10.30.0_x64.zip | 9F2C92A8DC1376BAFDE375F853E6EBF09DFD8CE48533705001EC9BE59281300E |\r\n| NewRelicDotNetAgent_10.30.0_x86.msi | 0CBA2A01AB769C20160689E39BDAF7F847AE6B309B2A50362798A85D79880382 |\r\n| NewRelicDotNetAgent_10.30.0_x86.zip | DDF0CDBC97BBEB5C9C8781E03318EFCD77B0EC27ACB2FD738C4B60D9EB540E19 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\r\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-30-0","eolDate":"2025-09-12"},{"agent":"dotnet","date":"2022-10-26","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.3.0","features":["Increase default limit of Custom Events per second from 10,000 to 30,000"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date . As of this release, the oldest supported version is .NET agent 8.20.262.0 . New features Custom event limit increase This version increases the default limit of custom events from 10,000 events per minute to 30,000 events per minute. In the scenario that custom events were being limited, this change will allow more custom events to be sent to New Relic. There is also a new configurable maximum limit of 100,000 events per minute. To change the limits, see the docs for max_samples_stored . To learn more about the change and how to determine if custom events are being dropped, see our Explorers Hub post . #1284 Checksums | File                                      | SHA - 256  Hash                                                  |\n| ----------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.3.0-1.x86_64.rpm | F115BC82F8CACD4AA5603282C3D21ADEAF32B344E2A0C4CF93108AD70250A4BA |\n| newrelic-dotnet-agent_10.3.0_amd64.deb    | 04521A96DF7A40140BA68761B2E5DE55AA2C561CE495AA284C45E7CFBAE294AF |\n| newrelic-dotnet-agent_10.3.0_amd64.tar.gz | 164BCF990059A4FA41FD02CA878D9ABAF019EEF3D0FA7D5C0F8694122C0C0B79 |\n| newrelic-dotnet-agent_10.3.0_arm64.deb    | 056F13CB19738BD8E4085F39119E4890B429ADAF1BCE9B2A43E8ACB8C1CD4D9B |\n| newrelic-dotnet-agent_10.3.0_arm64.tar.gz | 05E46D4BA843ADAADEBEFA9AEC3ECE02A90E36C8CF5A9D3D7D35FC190E80B110 |\n| NewRelicDotNetAgent_10.3.0_x64.msi        | CE393D38481F013D083F1473D518A7BC74663FD988C260570A79B8B087C919B1 |\n| NewRelicDotNetAgent_10.3.0_x64.zip        | 1588BBDFAE862439364D8E446E43A03947429247DA1ED611982CDD6AA598A206 |\n| NewRelicDotNetAgent_10.3.0_x86.msi        | C27161AD0B8FFCDBA1D18697EC7395ECFDB433060996811BB829BA6EF309C4A8 |\n| NewRelicDotNetAgent_10.3.0_x86.zip        | D952DC4CEA0400AFBA02E9EB2ECAD3932790942D7EFA2960E94CB3CE9FAA487C | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-3-0","eolDate":"2023-10-26"},{"agent":"dotnet","date":"2024-08-20","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.29.0","features":["Additional metrics and attributes for some instrumented libraries.","Auto-instrument ASP.NET Core Lambda functions.","Use Lambda function name if application name is not set."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New features Additional metrics and attributes for some instrumented libraries (#2675 ) (a033b81 ) Auto-instrument ASP.NET Core Lambda functions (#2662 ) (#2674 ) (ceaefc5 ) Use Lambda function name if application name is not set (#2695 ) (3dcf3af ) Checksums | File | SHA - 256  Hash |\r\n| ---| ---|\r\n| newrelic-dotnet-agent-10.29.0-1.x86_64.rpm | 2038CC43442723F8A315290E85A6199F4636E7616026349E7300ADD6BEE8E80F |\r\n| newrelic-dotnet-agent_10.29.0_amd64.deb | F970EC6A044A201C96AF0CB95F9F8530A1044B988FBDA3C0DE81E6281BD5A97C |\r\n| newrelic-dotnet-agent_10.29.0_amd64.tar.gz | 42404A1C5D04E70DA83F3357100221D1FE346A1F440FB28BE43F0E83CE32AD60 |\r\n| newrelic-dotnet-agent_10.29.0_arm64.deb | D2EB9AF71A1C8C47D4030874103A752902B57431A1A8A6C993E294F67DC14185 |\r\n| newrelic-dotnet-agent_10.29.0_arm64.tar.gz | 52CA20D220A3A2BBD83D6282C611D4033EEC52254A2211DE2A6C69D9A3430742 |\r\n| NewRelicDotNetAgent_10.29.0_x64.msi | A6A6FF1E75748DDF899C6F4FAB2069E9944CDC980BAB3735037378D8F2D4B003 |\r\n| NewRelicDotNetAgent_10.29.0_x64.zip | 0A5245E496878686369727B7EE122947FF9F1124694F421D881746EFFCAE3721 |\r\n| NewRelicDotNetAgent_10.29.0_x86.msi | E887078C36A59D6167E00FAFAC64D6F3582E7350C5BE54D3DDAFC12065E61C6A |\r\n| NewRelicDotNetAgent_10.29.0_x86.zip | AFDDA5AB1FC39981A9A4DA9DB3DAC1FFFCFBB7D3DB745217A0C715A44AE8F7D6 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-29-0","eolDate":"2025-08-20"},{"agent":"dotnet","date":"2024-08-05","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.28.0","features":["Improve serverless mode detection.","Set application name via command line with the .msi installer."],"bugs":["Better Lambda web request input parameter validation.","Revert recent Profiler warning fixes to address reported instability.","SQS instrumentation could cause InvalidOperationException."],"security":[],"supportedOperatingSystems":null,"description":"New features Improve serverless mode detection (#2661 ) (5f5dda8 ) Set application name via command line with the .msi installer (#2648 ) (369dcba ) Fixes Better Lambda web request input parameter validation. (#2653 ) (810d4af ), closes #2652 Revert recent Profiler warning fixes to address reported instability (#2663 ) (b3c9cd1 ) SQS instrumentation could cause InvalidOperationException (#2645 ) (#2646 ) (40b6ad5 ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.28.0-1.x86_64.rpm | 1D957AA1BB4BF1A0197E6AF99AD71727AE52E597689487B4B0ED3F5BD83D179E |\n| newrelic-dotnet-agent_10.28.0_amd64.deb    | 1EC0C7EB82795F5DA9A866C42E4E46A7D69B650ACACF81E8634993824609045B |\n| newrelic-dotnet-agent_10.28.0_amd64.tar.gz | 8AEB38A6D6332C62542B80752A233469DAFB556F4F98DF90A6F0121978E61509 |\n| newrelic-dotnet-agent_10.28.0_arm64.deb    | 93360002A1675BA99DD4390A3E30DA4C1E5DEFDAB31011F13D8E05CC46A40B33 |\n| newrelic-dotnet-agent_10.28.0_arm64.tar.gz | 6034A8750CA474C5FEE6018A115DBF4B7687113E18EB224F458A128EA4810E1F |\n| NewRelicDotNetAgent_10.28.0_x64.msi        | 2B07D467CF195B6EC0D0C64D7E3D6750944D6AC31151DAE6055E536FA66EB0ED |\n| NewRelicDotNetAgent_10.28.0_x64.zip        | F93C700EED54DF6AB9E3CD72927ACB8ABA2DCC75F5CBD754A62D17741CB00DF7 |\n| NewRelicDotNetAgent_10.28.0_x86.msi        | B65FB02DB4260AB00ED32CE4F488648045A327C418B9F8CC519899DB1BEBCE7B |\n| NewRelicDotNetAgent_10.28.0_x86.zip        | E277519F8A5717ECD56E6D9B38F73492044554424647C223FE4D767EFF45F887 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-28-0","eolDate":"2025-08-05"},{"agent":"dotnet","date":"2024-07-16","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.27.0","features":["Add support for disabling LLM monitoring at the account level.","Instrumentation for Amazon Simple Queuing Service (AWSSDK.SQS)."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New features Add support for disabling LLM monitoring at the account level. (#2592 ) (c31451a ) Instrumentation for Amazon Simple Queuing Service (AWSSDK.SQS) (#2620 ) (ac738ba ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.27.0-1.x86_64.rpm | EABD653EFD81FA2041D187766DBB0ECFEF77AB4654A82B0D428BB765C623D8D6 |\n| newrelic-dotnet-agent_10.27.0_amd64.deb    | 645739F566663E0775BBDAA99EF29A302B2110B2C39C5809876E97CF32FE3D70 |\n| newrelic-dotnet-agent_10.27.0_amd64.tar.gz | 66DD9B2374719D0C5CA341889802F1543174761EB97680FF6A80F83290E66F58 |\n| newrelic-dotnet-agent_10.27.0_arm64.deb    | D252CF820D18B8BA75CB418EA77E5440A5A686324635AB456C22648E9FAD7EC3 |\n| newrelic-dotnet-agent_10.27.0_arm64.tar.gz | C19279180A10755B6A37090B3BB1E48189C8BA5C9A73F8D3CA50D37F9A00D196 |\n| NewRelicDotNetAgent_10.27.0_x64.msi        | F450DDFE765BEECA0012FE6317CE1C84C235D694865A29B59C34DDA101431F65 |\n| NewRelicDotNetAgent_10.27.0_x64.zip        | E8B4BACE96DF455F63ADEE9C5369AD0DA1DBAB2E3D5FB2B19E902AD1DE53EBB3 |\n| NewRelicDotNetAgent_10.27.0_x86.msi        | 81BB6CF762B6AA9D2FEDC3EF586D95E5209310232F25ACA573B17BB346DD3FF0 |\n| NewRelicDotNetAgent_10.27.0_x86.zip        | 660B9721C94D4139AD2EE2C850A3A9102A1DBBBE7D48B598682603522FE88121 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-27-0","eolDate":"2025-07-16"},{"agent":"dotnet","date":"2024-06-26","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.26.0","features":["Add an option to disable the file system watcher.","Add support for capturing container id from AWS ECS.","Add support for using Sitecore.Logging and log4net together."],"bugs":["Prevent NullReferenceExeption on APIGatewayProxyRequest.","Refactor to eliminate usage of `.GetAwaiter().GetResult()` in Framework builds."],"security":[],"supportedOperatingSystems":null,"description":"Notice The .NET Agent now supports instrumenting AWS Lambda functions. See documentation for details: https://docs.newrelic.com/docs/serverless-function-monitoring/aws-lambda-monitoring/get-started/monitoring-aws-lambda-serverless-monitoring/ . (d96e29f ) New features Add an option to disable the file system watcher. (#2536 ) (27d0ed0 ) Add support for capturing container id from AWS ECS. (#2481 ) (c018b8a ) Add support for using Sitecore.Logging and log4net together (#2537 ) (332529b ) Fixes Prevent NullReferenceExeption on APIGatewayProxyRequest (#2529 ) (18d833f ) Refactor to eliminate usage of .GetAwaiter().GetResult() in Framework builds. (#2534 ) (#2535 ) (cfb2c28 ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.26.0-1.x86_64.rpm | 253225B5BEC4125305257F04F7702A21E9B0DCD56E56473A769DFA90DB83E502 |\n| newrelic-dotnet-agent_10.26.0_amd64.deb    | FDF7FCC93CA8E6A6F74E766BC9E7B0AD6F3E20238161622B5A494FB436CF6654 |\n| newrelic-dotnet-agent_10.26.0_amd64.tar.gz | B9E4A474A5F414353AB63050298292AD505B6D32F3696521C7B1754DDAE6A3D3 |\n| newrelic-dotnet-agent_10.26.0_arm64.deb    | 07000D1304026973342310258AB2D4D6A5E58A8AEB330825C1D1FA1963DAC2FF |\n| newrelic-dotnet-agent_10.26.0_arm64.tar.gz | 630CC8A9F13546A9B34FA39221F8357FE57018ECD27027B9853498F2FCC30F11 |\n| NewRelicDotNetAgent_10.26.0_x64.msi        | 5930588478DB4371EDCE531EDBD25057DC91857372A429271E68DC79F2D645AD |\n| NewRelicDotNetAgent_10.26.0_x64.zip        | 950FC6B39E8819305E9BA7494C5BEEC28D2625476D3348514E4747B032B88564 |\n| NewRelicDotNetAgent_10.26.0_x86.msi        | AA2FFF0BCF8E4E3A09D65B21F83A1203F9432DBCFC987E8C56C05FB48828C365 |\n| NewRelicDotNetAgent_10.26.0_x86.zip        | C2B951E244E6692B22438DEAE7D3346591F8BCEC26AAB1B3A86C4CF6EC583914 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-26-0","eolDate":"2025-06-26"},{"agent":"dotnet","date":"2024-06-04","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.25.1","features":[],"bugs":["Agent license key should be optional in Serverless mode.","Nested logging contexts should not disable context data for Microsoft.Extensions.Logging (2508)."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Agent license key should be optional in Serverless mode. (#2499 ) (#2500 ) (801edc3 ) Nested logging contexts should not disable context data for Microsoft.Extensions.Logging (2508) (#2516 ) (6196af5 ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.25.1-1.x86_64.rpm | 246945D9E35B02939B1899378304F31DE1266AAC6B14F63C960CFBBEC83710F6 |\n| newrelic-dotnet-agent_10.25.1_amd64.deb    | A0D2698E8C464470A06066E6B8D86260C4B4088DF933FF5F1B5BA0936D1B1105 |\n| newrelic-dotnet-agent_10.25.1_amd64.tar.gz | 1D5137FD0BF3BE108667F10592C3EEB0545ACCD0C5B87940D0ABA9F9E6D7B71A |\n| newrelic-dotnet-agent_10.25.1_arm64.deb    | E9A926205826450B2E88E7297B2F79974AE7F08694EDE06359C3C3224D406ABD |\n| newrelic-dotnet-agent_10.25.1_arm64.tar.gz | 5FB88F2C8A6071D25D2568B3B2ED00B96D30173541EBF59055ECB27FFB7B6FAC |\n| NewRelicDotNetAgent_10.25.1_x64.msi        | C85867346D8940CAAEBFEFF24B8238156F130EB5A6A03966FF30917051C12946 |\n| NewRelicDotNetAgent_10.25.1_x64.zip        | E85CBB69E45D4610CF021BCFA284D70DF7A0D7D0EA77238664EF154572F1538A |\n| NewRelicDotNetAgent_10.25.1_x86.msi        | E9F6982941E760F18C75FE8E7A82A21FAA1129415E08664E401EC20FC007158A |\n| NewRelicDotNetAgent_10.25.1_x86.zip        | 4E376D72F922D44BC3BE305D63CA7B309C39BD0120C6E679EAE817293C45ABBE | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-25-1","eolDate":"2025-06-04"},{"agent":"dotnet","date":"2024-05-21","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.25.0","features":["Add support for AWS Lambda `APIGatewayHttpApiV2ProxyRequest`.","Enable configuration of ignored and expected HTTP status code errors with environment variables."],"bugs":["Accept inbound tracing headers in Kafka consume method instrumentation.","Upgrade Wix to v5 to fix an issue with non-elevated installs."],"security":[],"supportedOperatingSystems":null,"description":"New features Add support for AWS Lambda APIGatewayHttpApiV2ProxyRequest (#2472 ) (3f06bf6 ) Enable configuration of ignored and expected HTTP status code errors with environment variables (#2487 ) (eeb574f ) Fixes Accept inbound tracing headers in Kafka consume method instrumentation (#2488 ) (476378a ) Upgrade Wix to v5 to fix an issue with non-elevated installs (#2471 ) (acd12fa ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.25.0-1.x86_64.rpm | 0E77C3A3F80D52980DA7483A83456570B9C6A599E7EA545CD8E4BFEA90C42CD0 |\n| newrelic-dotnet-agent_10.25.0_amd64.deb    | C8EE8E0D26DF26558BEFC0A8391473A49FDEE477F0EECDB44C352DFB159BF5A9 |\n| newrelic-dotnet-agent_10.25.0_amd64.tar.gz | B47DF5FCCFBA74E1A0CF44EAB713496C3A8199333A3180C0F69A72569CB5CBDB |\n| newrelic-dotnet-agent_10.25.0_arm64.deb    | 50A8F0F130986AAB1096666BE4C9EC331277E60B5D8B355E09258CB0B64EABD8 |\n| newrelic-dotnet-agent_10.25.0_arm64.tar.gz | 3E387A0F417776F693C3ECDBF6E023D46573B005C28F7FC5AB731F68E6D540AF |\n| NewRelicDotNetAgent_10.25.0_x64.msi        | FF666ABD7301597011EE09BCED65CC0F4CD4D43D9ADE4E3A76D792D34D82BFEB |\n| NewRelicDotNetAgent_10.25.0_x64.zip        | 4FF80F8F0923F26D76240240C10EBA814E2FB6CCB7ED590D52BA69CE727FDCC2 |\n| NewRelicDotNetAgent_10.25.0_x86.msi        | 81DA2A71B94B38462C45BD25CC8E7289E5DB90098424686251C18204D0A5E01F |\n| NewRelicDotNetAgent_10.25.0_x86.zip        | 74E6E22D02B19EC189D6FC0240B6FB67FA7AEA0540FA2BB0630B7F721FAF6BBD | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-25-0","eolDate":"2025-05-21"},{"agent":"dotnet","date":"2024-05-08","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.24.0","features":["Add preliminary support for AWS Lambda instrumentation."],"bugs":["Fix bug in distributed tracing when `excludeNewrelicHeader` is set to true."],"security":[],"supportedOperatingSystems":null,"description":"Notice Due to an ongoing issue with the WiX Toolset, the Windows MSI installer must be run as admin. This will be addressed in an upcoming release. (4d40da5 ) New features Add preliminary support for AWS Lambda instrumentation. For details on how to enable this functionality, please contact your New Relic representative. (4d40da5 ) Fixes Fix bug in distributed tracing when excludeNewrelicHeader is set to true (#2457 ) (1f95c9c ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.24.0-1.x86_64.rpm | 40924C1E0D9E619C5F5334F077E65C2CEC20A431E2F03B5840D3FAA7E4D4907B |\n| newrelic-dotnet-agent_10.24.0_amd64.deb    | 017A1106DD404D07177C88339D63B039272C81733D5F57E12A9C896FF2FBFAB9 |\n| newrelic-dotnet-agent_10.24.0_amd64.tar.gz | 464558E58C040F00E0EA75DA535E797B71D3C66ED7DBF5C177D9A720649CEF82 |\n| newrelic-dotnet-agent_10.24.0_arm64.deb    | 19D6E872DEADED4EE0403A60DDE8E640413263ADE46ED0BC139ABB67152D38EE |\n| newrelic-dotnet-agent_10.24.0_arm64.tar.gz | E5A38C703476A3822E6EDB6DD87F44E4963A0E7AC435E19C2D759717ECC7A86D |\n| NewRelicDotNetAgent_10.24.0_x64.msi        | C13040F16502EAB1E1F5236C032E8A2C1ADFFDFCEDCC2F0E9356F02B8301BCFA |\n| NewRelicDotNetAgent_10.24.0_x64.zip        | C2F718A06F887DC1B96DAC2084E19C64E00D34FF1BAAAE6726335E7F7185AB1C |\n| NewRelicDotNetAgent_10.24.0_x86.msi        | 34448A4C0488FE4CA79BBD032A1E9288B589E58F49A2CFFA3FD5A529BC02AEBA |\n| NewRelicDotNetAgent_10.24.0_x86.zip        | 92E62CF8C04EFCC890CEE98D8276076B55669253B7273906E60F3570B1B34617 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-24-0","eolDate":"2025-05-08"},{"agent":"dotnet","date":"2024-04-24","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.23.1","features":[],"bugs":["Fix duplicate key error when using Kafka with DT enabled.","Fix incorrectly tagging AIM data when AIM is disabled."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Fix duplicate key error when using Kafka with DT enabled (#2433 ) (6a85c03 ) Fix incorrectly tagging AIM data when AIM is disabled (#2408 ) (30d12bb ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.23.1-1.x86_64.rpm | 9A842490786F505B257740E5D4EA2387968464833283380D7564330E0BAA9737 |\n| newrelic-dotnet-agent_10.23.1_amd64.deb    | 00075BB9F2276A79F617F3AF147FFAE488A485DED139477B9E6E679F07EB4339 |\n| newrelic-dotnet-agent_10.23.1_amd64.tar.gz | A35320228DCD48A8A33DE7FB719A7B1D676E96F29A3551416A62FCFDF423C38C |\n| newrelic-dotnet-agent_10.23.1_arm64.deb    | 5FD1BB3BCAAC0D3CD87E06D74513D91C4D20B377E992284B8AAA8836E3C276CD |\n| newrelic-dotnet-agent_10.23.1_arm64.tar.gz | CFF07630360B552F37F5D7DC7A3D3BA477BF14C0E4937E4F4B6A57B3FEEAE8CE |\n| NewRelicDotNetAgent_10.23.1_x64.msi        | 19125A5B60475E5A5E7DDCFE3AF236B132A68C43DB05AD5E50FD8E41873286FC |\n| NewRelicDotNetAgent_10.23.1_x64.zip        | 2AE2D9CC5F50A78448CBE64E316FC8D4B61571E593C70A13C9966945E1E905CE |\n| NewRelicDotNetAgent_10.23.1_x86.msi        | 3CB4D59D65C3A75A90F61408F0877BBA25A94DFFE9B4EC4B4E4DD3921D9B8E3D |\n| NewRelicDotNetAgent_10.23.1_x86.zip        | 644C6663455FF05948E5C796970ABEB05C1671DB0FC9B6B85CCF0512873FCB1D | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-23-1","eolDate":"2025-04-24"},{"agent":"dotnet","date":"2024-04-02","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.23.0","features":["A new AI monitoring related public API method has been added - [SetLlmTokenCountingCallback](https\":\"//docs.newrelic.com/docs/apm/agents/net-agent/net-agent-api/set-llm-token-counting-callback/).","Add auto-instrumentation for AWS Bedrock.","**deps\":\"** Updated `Elastic.Clients.ElasticSearch` instrumentation points to work with v8.12.1+.","New configuration options are available specific to [AI monitoring](https\":\"//docs.newrelic.com/docs/apm/agents/net-agent/configuration/net-agent-configuration/#ai_monitoring)."],"bugs":["Handle InvalidOperationException in StringsHelper.CleanUri() [#2373](https\":\"//github.com/newrelic/newrelic-dotnet-agent/issues/2373)."],"security":[],"supportedOperatingSystems":null,"description":"Notice When AI monitoring is enabled, the agent will now capture AI LLM related data. This data will be visible under a new APM tab called AI Responses. See our AI Monitoring documentation  for more details. (a6f3364 ) New features A new AI monitoring public API method has been added: SetLlmTokenCountingCallback  (a6f3364 ) Add auto-instrumentation for AWS Bedrock (a6f3364 ) deps:  Updated Elastic.Clients.ElasticSearch instrumentation points to work with v8.12.1+ (453d15e ) New configuration options are available specific to AI monitoring . (a6f3364 ) Fixes Handle InvalidOperationException in StringsHelper.CleanUri() #2373  (#2374 ) (9f1a6af ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.23.0-1.x86_64.rpm | 0CCD555CD1C14167B53787DBB20CB30662E7AD602FAFA04B3B8E3AFB07ECAE12 |\n| newrelic-dotnet-agent_10.23.0_amd64.deb    | AF0D0E52908AEF2D68C1A8439BF4AC57B6E23444E1DC18009E6EB54C44BB29FE |\n| newrelic-dotnet-agent_10.23.0_amd64.tar.gz | 62889849857A11D305DD7246E72E95C13BF783433A20EF959671DA75EECF683C |\n| newrelic-dotnet-agent_10.23.0_arm64.deb    | 8912C96530EFC4A4054D54C4AAD6E69DF6258D590B912200D21CA0124AEB97E4 |\n| newrelic-dotnet-agent_10.23.0_arm64.tar.gz | 374E975D385F3BFE0FB39645AEBD5D45C44B952FE8DD1B18CDA630F133B72D60 |\n| NewRelicDotNetAgent_10.23.0_x64.msi        | D24DE2FC40702D6F0A9AFBC5DBE09C4A3B54A3D75A48D2370526A0B15C098D13 |\n| NewRelicDotNetAgent_10.23.0_x64.zip        | 3ED84284C6B7B0D446D8509F4B7C4F0829955C02292E43419BB65CEE61BD5569 |\n| NewRelicDotNetAgent_10.23.0_x86.msi        | 029A8E31EA350CFC7386D58DB097C79C70A791550556ACA37B551787F5DA5A96 |\n| NewRelicDotNetAgent_10.23.0_x86.zip        | 1643D1696FF855F710B78983BED24280EC74284F327F026EEAC29743F27DB6D4 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-23-0","eolDate":"2025-04-02"},{"agent":"dotnet","date":"2024-03-20","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.22.0","features":["Add a new API method to time currently unsupported datastore method calls.","Add transaction ID to intrinsic attributes for error events and traces regardless of DT/CAT settings."],"bugs":["Fix a context data capture when the Microsoft.Extensions.Logging console logger is used (thanks [@lowell-trimble](https\":\"//github.com/lowell-trimble)!)."],"security":[],"supportedOperatingSystems":null,"description":"New features Add a new API method to time currently unsupported datastore method calls. (#2320 ) (81abc5c ) Add transaction ID to intrinsic attributes for error events and traces regardless of DT/CAT settings (#2341 ) (1df0342 ) Fixes Fix a context data capture when the Microsoft.Extensions.Logging console logger is used (thanks @lowell-trimble !) (#2261 ) (#2315 ) (f8422d6 ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.22.0-1.x86_64.rpm | 3CD5AB7FA9801DE2647B9AB96972F39C411D2BA80ED23562FD45D998AFC150E2 |\n| newrelic-dotnet-agent_10.22.0_amd64.deb    | A1DF21AAD826DF7C19F4BA78EA368A78E93DF73BDC90B30432859248D3F25487 |\n| newrelic-dotnet-agent_10.22.0_amd64.tar.gz | A3D5E5C0BD1B53BF7709538F078EB9383413EC8B3D2DDBEB01520B89A26AE3FD |\n| newrelic-dotnet-agent_10.22.0_arm64.deb    | 1A8B8F57FFB2A9FF694E92D573BEA7915F698012252F802FF2ABFAAAC9A585AA |\n| newrelic-dotnet-agent_10.22.0_arm64.tar.gz | 2B3E1C063F114D46B141F5FC8B459A9181D7FDF05D93FBED315E7CB5AD362664 |\n| NewRelicDotNetAgent_10.22.0_x64.msi        | CF1E5F39AD039EC3A27E6BB91291912008F248194968E76E147CFF713C4B2972 |\n| NewRelicDotNetAgent_10.22.0_x64.zip        | F1AFFBC42D4716525DDBF6ECB72FB59A51DC30A411B3E4F09CCE705FA2A67D12 |\n| NewRelicDotNetAgent_10.22.0_x86.msi        | 9228160738A52991E766F845CBFBB1E6186B24D5E4C00FE37A636E524C81B5DB |\n| NewRelicDotNetAgent_10.22.0_x86.zip        | A899006B2F0CE7E634F56EA315FEAE2C0AD1B7FF7B92165E651D27C833FC8017 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-22-0","eolDate":"2025-03-20"},{"agent":"dotnet","date":"2024-03-08","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.21.1","features":[],"bugs":["Update regex parsing for CGroup v1 to match agent spec."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Update regex parsing for CGroup v1 to match agent spec. (#2286 ) (7fa3410 ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.21.1-1.x86_64.rpm | A27ED33B3143CE9C175CC92BC31327B63080AF8F9051D5BA511ADD008A746E27 |\n| newrelic-dotnet-agent_10.21.1_amd64.deb    | 401CD8C8F6746B996247446CEC82D10C78DE4ABDD60898E94E601FC0E5E4900E |\n| newrelic-dotnet-agent_10.21.1_amd64.tar.gz | 04C05690A1868CC06FF02DA47A9AB123325A9573C94E5E6BF16C83BE205C51E2 |\n| newrelic-dotnet-agent_10.21.1_arm64.deb    | 2AA56F45A1A248BA6377F0FF7EFC62EEA566F5FA175635D066E6FFB2DED43E55 |\n| newrelic-dotnet-agent_10.21.1_arm64.tar.gz | EC1742249326FD46848591A192C20C45BB77C22FBBEB6CD9D40B828C24084E91 |\n| NewRelicDotNetAgent_10.21.1_x64.msi        | 2142B864383DF18607B934BE608F70ACFDC0A4819802E89D539B9F9CF34282C5 |\n| NewRelicDotNetAgent_10.21.1_x64.zip        | 0F48FB9C9F1CDB24F3653D1B79993AE825D6D9405F380AC7B887E7EAAEE9A335 |\n| NewRelicDotNetAgent_10.21.1_x86.msi        | 18D2950904EE6010050AE4A33FED63CE91180B903A5818D2BD6477C00F812824 |\n| NewRelicDotNetAgent_10.21.1_x86.zip        | 79F000CF1B5DACB96E573ADF4B331FE5E49165CBFA7ECA73C70F96B20B390567 | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-21-1","eolDate":"2025-03-08"},{"agent":"dotnet","date":"2024-02-27","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.21.0","features":["Add new configuration options for logging to control log file size, log retention and log rollover strategy.","Allows instrumentation to be disabled from a newrelic.config file."],"bugs":["Certain Profiler log messages did not print correctly when running under Linux.","Use original regex to get container id from cgroup v1 in fallback case."],"security":[],"supportedOperatingSystems":null,"description":"Notice Browser monitoring instrumentation  for ASP.NET CORE v6+ web applications  is disabled by default but can be manually enabled by following these instructions . (da8dd44 ) New features Add new configuration options for logging to control log file size, log retention, and log rollover strategy. Refer to our log configuration documentation  for details. (#1880 ) (#2264 ) (d33714f ) Allows instrumentation to be disabled from a newrelic.config file. (#2250 ) (1632adb ) Fixes Certain Profiler log messages did not print correctly when running under Linux. (#2200 ) (#2209 ) (1b75bf9 ) Use original regex to get container id from cgroup v1 in fallback case (#2263 ) (9ecb88d ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.21.0-1.x86_64.rpm | D111CE285E5B06A21FC69ABB05205555C8E9038736055709ED534642BB8F09BB |\n| newrelic-dotnet-agent_10.21.0_amd64.deb    | 85BD60BFA393EC7C3113BC38737BCD8EE1C0D63CEC909488AE878D6933D86173 |\n| newrelic-dotnet-agent_10.21.0_amd64.tar.gz | 96CE28A45C5973162985DF0C3451426A2520EAC252078F498B7A6F67BB55CF4D |\n| newrelic-dotnet-agent_10.21.0_arm64.deb    | 05EA3709853F6809699F0151FAE5AAC9854AB177FB5CC6EEE97D8BD7D8ED2EE1 |\n| newrelic-dotnet-agent_10.21.0_arm64.tar.gz | 6A90A9924910B8CC1BF76BAE327F5AF4193B23AC052CA639314346EED1F9993E |\n| NewRelicDotNetAgent_10.21.0_x64.msi        | FE60CABF0073F56781323303C92909C07C2821B7D5828B796EE1DA21AE051CFF |\n| NewRelicDotNetAgent_10.21.0_x64.zip        | 615070E1492C11A0558F28DA12026BB2CA14A5A47C5692863B1CDCCD5907BA30 |\n| NewRelicDotNetAgent_10.21.0_x86.msi        | B8FE066C59C883CC3BF637ADF6BC9FA85C603F041AE1B98DD5B7EC2BFD45F7FF |\n| NewRelicDotNetAgent_10.21.0_x86.zip        | BA1E7DF9BC3DB39500BC755BBCB94F6979DE86BC1EAE1DF79825A90B2AF8ACAD | Updating your agent Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-21-0","eolDate":"2025-02-27"},{"agent":"dotnet","date":"2024-01-17","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.20.2","features":[],"bugs":["Eliminate intermittent deadlock on agent startup.","Path to agentinfo.json was built incorrectly, leading to file not found errors when running on Linux.","Prevent multiple SessionCache instances from being created.","Prevent null reference exceptions while serializing LoadedModuleWireModelCollection."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Eliminate intermittent deadlock on agent startup. (#2183 ) (#2184 ) (11c0241 ) Path to agentinfo.json was built incorrectly, leading to file not found errors when running on Linux. (#2156 ) (#2157 ) (bd7e0c3 ) Prevent multiple SessionCache instances from being created. (#2180  ) (#2186 ) (08a3015 ) Prevent null reference exceptions while serializing LoadedModuleWireModelCollection. (#2185 ) (#2187 ) (afb6352 ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.20.2-1.x86_64.rpm | 72BE4D4AD59D0815E400235D9A73E1368DB4E54EA2E2FCF9A0DD6CB48D70948B |\n| newrelic-dotnet-agent_10.20.2_amd64.deb    | EF8CADB865F654E6BDA99E48F0D21BD438DBD9A3E6C09C819A776A4E8295B302 |\n| newrelic-dotnet-agent_10.20.2_amd64.tar.gz | 30B1E88B4260E3D6990DD323C0C75FD325E1316FC2C2B83C801294A233E1292B |\n| newrelic-dotnet-agent_10.20.2_arm64.deb    | 77D2D58515AC6762143A7E5FA46F85B49A07408303B781B46D43438C4E0ADC2E |\n| newrelic-dotnet-agent_10.20.2_arm64.tar.gz | 666B0D369091ED9703BCB33767A5546FE2D0CAB9FA87DB912A4B9A42AB15F563 |\n| NewRelicDotNetAgent_10.20.2_x64.msi        | E32BADCCE44BDFFA227459852B2718BE25E9B8FF6ECF2A9C81B6EAD3B5F5BBBD |\n| NewRelicDotNetAgent_10.20.2_x64.zip        | 4FCEB544B298C1CE2D9C2AAE709E197ACAB1513BCAAF4B022942071C6EE8E9F9 |\n| NewRelicDotNetAgent_10.20.2_x86.msi        | 0AF83E48F2ABFD9834E35CAB538171C81D30E10DDC0E094B660A512CBACB8EE0 |\n| NewRelicDotNetAgent_10.20.2_x86.zip        | F2DD01816492612912FA36D03D928ED83273871E22BB67D274F34F59492957E7 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-20-2","eolDate":"2025-01-17"},{"agent":"dotnet","date":"2023-12-13","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.20.1","features":[],"bugs":["Fix a crash that can occur when the profiler logs certain characters.","Improve handling of .NET environments and settings from appsettings.*.json files.","Obfuscate logged appSettings values.","Revert RabbitMQ HandleBasicDeliver instrumentation change from [#1972](https\":\"//github.com/newrelic/newrelic-dotnet-agent/issues/1972).","Update instrumentation to support Elasticsearch v8.11.0."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Fix a crash that can occur when the profiler logs certain characters. (#1982 ) (#2109 ) (742d232 ) Improve handling of .NET environments and settings from appsettings.*.json files (#2125 ) (3c21fe9 ) Obfuscate logged appSettings values (#2110 ) (2d8da68 ) Revert RabbitMQ HandleBasicDeliver instrumentation change from #1972 . Resolves #2047  (#2118 ) (0525182 ) Update instrumentation to support Elasticsearch v8.11.0 (#2100 ) (9effb5d ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.20.1-1.x86_64.rpm | 2651EF327078D357E5912DBAD66FDAB6F89A0F90B9CFD07C7DCA54CF1BC81B90 |\n| newrelic-dotnet-agent_10.20.1_amd64.deb    | 9CA48C3ED91757E42987E2C896F4CE0B808D5762B348F8C9F4F7C7369378A577 |\n| newrelic-dotnet-agent_10.20.1_amd64.tar.gz | 346F13E4162442AE1AFA8AE2E7BD8476F7F3E28687024F6280170EDCC04E9D3F |\n| newrelic-dotnet-agent_10.20.1_arm64.deb    | 24151F0E633610A821EC93680D626D933BED0513B4AE0C37CAA33663C96EF783 |\n| newrelic-dotnet-agent_10.20.1_arm64.tar.gz | D3A9F0DBA480F5AF3283B93639A6460DB9938BAB09411DC936BC4E3BAF9716B8 |\n| NewRelicDotNetAgent_10.20.1_x64.msi        | 965E41355B74CF1213CAB9D1C39B2C2BA0162AB4ACE4538603D51AFCA909DF6C |\n| NewRelicDotNetAgent_10.20.1_x64.zip        | 924D7A5E6D38CF8C88E3D99E4C188AA76B530283898F2783C19987BD9C5FDE7C |\n| NewRelicDotNetAgent_10.20.1_x86.msi        | D1ABD460E77CC4DBF00DB8382D08D888A797CF7FBFF311415EF0E35437AAE0F3 |\n| NewRelicDotNetAgent_10.20.1_x86.zip        | C339F20C60FA388632BAC785A2E2C68059DB46F236960F470E1DE8B7F0F46B78 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-20-1","eolDate":"2024-12-13"},{"agent":"dotnet","date":"2023-11-28","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.20.0","features":["Allow the agent to run in environments with read-only filesystems."],"bugs":["Defensively handle null source address in MassTransit instrumentation.","During browser agent injection, don't set ContentLength if headers have already been sent.","Remove dependency on Serilog.Expressions."],"security":[],"supportedOperatingSystems":null,"description":"New features Allow the agent to run in environments with read-only filesystems. (#2085 ) (09ab29d ) Fixes Defensively handle null source address in MassTransit instrumentation. (#2055 ) (0249582 ) During browser agent injection, don't set ContentLength if headers have already been sent. Resolves #2051  (#2059 ) (c191aa6 ) Remove dependency on Serilog.Expressions. Resolves #2083 . (9e355f3 ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.20.0-1.x86_64.rpm | 05CCBF42D85A7110DDE9506910004067E1086A2AE1ED96522173BF8FAC3CF97A |\n| newrelic-dotnet-agent_10.20.0_amd64.deb    | 7093B6A0AAA1D06C5C9588C604D9BD3BE599AB5FD7ED75910434420DE708347C |\n| newrelic-dotnet-agent_10.20.0_amd64.tar.gz | 16C88CC03A54FE6A5564EBC3247975FFFE77BDDC171F2C34F93139CAB858300D |\n| newrelic-dotnet-agent_10.20.0_arm64.deb    | C6C2E16258F25AB948515168631184E165D6BD995C8D37714113063272510D3D |\n| newrelic-dotnet-agent_10.20.0_arm64.tar.gz | 3168B6FF8E970BD986C6815BEECAE6C9F8A69F837712A900C97652EF2FC3C9B8 |\n| NewRelicDotNetAgent_10.20.0_x64.msi        | 4C297A6475DADD9B522AD2587303F5E13A3A5DB1C8479A91C4C4A773C6C4C678 |\n| NewRelicDotNetAgent_10.20.0_x64.zip        | 55C4C9D350857F140C1A5DFFDF04E68089195AADA5F1843DF1718E95713A42FD |\n| NewRelicDotNetAgent_10.20.0_x86.msi        | 7903FE9C3D6222CF5226831685CD89527BC0CE95CEC4D3E1836E83B7B03807D2 |\n| NewRelicDotNetAgent_10.20.0_x86.zip        | 64572F6373AB5550260A19BA27CA97750802BE4F672EC6B96E5E02439A997304 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-20-0","eolDate":"2024-11-28"},{"agent":"dotnet","date":"2022-10-03","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.2.0","features":["Add environment variable to configure SendDataOnExit","Send Code Level Metrics for CodeStream integration by default"],"bugs":["Fix occasional crash during exit when using SendDataOnExit","Properly inject new versions of the Browser Agent script","Add missing instrumentation for Microsoft.Data.SqlClient","Fix missing log messages when local decoration was used with NLog","Improve serialization of complex custom attributes","Include additional profiler environment variables in debug startup logs","Resolve race condition during agent reconnect where disabled data types could breifly be sent"],"security":[],"supportedOperatingSystems":null,"description":"New Features Add new environment variables to control SendDataOnExit functionality: NEW_RELIC_SEND_DATA_ON_EXIT, NEW_RELIC_SEND_DATA_ON_EXIT_THRESHOLD_MS. #1250 Enables integration with CodeStream code-level metrics by default. This allows you to see golden signals in your IDE through New Relic CodeStream without altering agent configuration. Learn more here . For any issues or direct feedback, please reach out to support@codestream.com.  #1255 Fixes Resolves an issue where the .NET Core agent could crash during application shutdown when SendDataOnExit functionality was triggered. #1254 Resolves an issue where the .NET agent incorrectly injects the browser agent script inside HTML pages. #1247 Resolves an issue where some instrumentation was missing for Microsoft.Data.SqlClient in .NET Framework. #1248 Resolves an issue with local log decoration for NLog where the original log message was not included in the output. #1249 Resolves an issue where the .NET agent failed to serialize custom attributes containing some non-primitive types. #1256 Includes missing profiler environment variables in debug logs during application startup. #1255 Resolves an issue where the .NET agent still sends up disabled event types during reconnecting period. #1251 Checksums | File                                      | SHA - 256  Hash                                                  |\n| ----------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.2.0-1.x86_64.rpm | 7A858BD492CBD40285D0C94CCF2C962EB2AF42D80B5736550E06D510B2FE769F |\n| newrelic-dotnet-agent_10.2.0_amd64.deb    | 2B6D05EBC19B051702EA4FBE9ABA80CC5BD431D45D943652B8B1B1EFC3730D61 |\n| newrelic-dotnet-agent_10.2.0_amd64.tar.gz | DED11457AD8BF1BB15FB7EA2F6F3E786E603201FD7D5370642EE9E19E8DA4510 |\n| newrelic-dotnet-agent_10.2.0_arm64.deb    | 50D7AE765199EE8A4FBE171E3418D6F59C95E4436E1127317E0DD254FFD22C7B |\n| newrelic-dotnet-agent_10.2.0_arm64.tar.gz | CB7BF9C7739A2DAFB77EDE24D4E0DDC8300665077B36C3FB48DA6EAB41F4FF92 |\n| NewRelicDotNetAgent_10.2.0_x64.msi        | C053944AD9B0F79358A997FB26ED504675E36F606F25C5B27DB07B844127E1EC |\n| NewRelicDotNetAgent_10.2.0_x64.zip        | F61CD3AA34AF50D12145679946E1D3EFCB7EDB438D1F7908C0215F99D645A5F1 |\n| NewRelicDotNetAgent_10.2.0_x86.msi        | 6548DDD56CE1E47E74170A4F741946524B83A51EED99C76DE2DAC1A09E3054A1 |\n| NewRelicDotNetAgent_10.2.0_x86.zip        | 26695340A63007F29F36F6C8D6499B917C15FEC68590750311CF9B6F7E32BD9C | Support statement New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.20.262.0 . Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-2-0","eolDate":"2023-10-03"},{"agent":"dotnet","date":"2023-11-10","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.19.2","features":[],"bugs":["ASP.NET Core 6+ browser agent injection is disabled by default."],"security":[],"supportedOperatingSystems":null,"description":"Fixes ASP.NET Core 6+ browser agent injection is disabled by default. (e571ac1 ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.19.2-1.x86_64.rpm | 5D2730F78B115B8976A671BCA3738DC18B2DBD499040E16F5FD610E35C1E9D08 |\n| newrelic-dotnet-agent_10.19.2_amd64.deb    | 08135B6EEAFECC5A577C3C7AFDC6D194D0BC551ADD7488B6165BAD8D8822A76F |\n| newrelic-dotnet-agent_10.19.2_amd64.tar.gz | F83661897C99B923F4345C6527F063618E196E10CDD52F4128E701628A8848EF |\n| newrelic-dotnet-agent_10.19.2_arm64.deb    | FF8B98808362194C4809FDFDB4E1153ED7806AF794F38384E8BDE7342A450A88 |\n| newrelic-dotnet-agent_10.19.2_arm64.tar.gz | 5FEA6FEB4672B293722105D0DBFD173F25226E231220C6E55E4FABF34D56E7EF |\n| NewRelicDotNetAgent_10.19.2_x64.msi        | 5301FE3F2B1980DEC3804E9CAA7007D2F23A7E21B28A35FFFC9222BB66727FC0 |\n| NewRelicDotNetAgent_10.19.2_x64.zip        | 139A8E2921C3E0F460F202053C7111B65F11120FFE278D229B813B39FF5624CC |\n| NewRelicDotNetAgent_10.19.2_x86.msi        | 3E005FCD410F2468E10F379AFBDF9E9A383333827BD040CA894F23E9F4DE2536 |\n| NewRelicDotNetAgent_10.19.2_x86.zip        | E6280B9A0CD96BACB5E07F2C3B555040FF858CAE6E5F68F52D2A444B6AFC3A74 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-19-2","eolDate":"2024-11-10"},{"agent":"dotnet","date":"2023-11-08","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.19.1","features":[],"bugs":["Add defensive coding and exception handling during ASP.NET Core 6+ browser injection."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Add defensive coding and exception handling during ASP.NET Core 6+ browser injection. (#2035 ) (#2038 ) (5ddd0ea ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.19.1-1.x86_64.rpm | F763C2117A46565DD99ED90A488A512860B728EAA8EEB244799C18501CA9D80B |\n| newrelic-dotnet-agent_10.19.1_amd64.deb    | A0E6A9C6D79D4396F02DFDFDA5AF26823CF9F57C782F7DF1E09B5B94CFE8AD49 |\n| newrelic-dotnet-agent_10.19.1_amd64.tar.gz | 14497966D9EE13EB34F9BCBF4FC275AECAC9C7E94CD8C95F1A8384D9490FCBC6 |\n| newrelic-dotnet-agent_10.19.1_arm64.deb    | 8859E5BE34AAFD14833498B41F360F87398886807E79AFCBB56E5E92143E22B0 |\n| newrelic-dotnet-agent_10.19.1_arm64.tar.gz | B11197E2F0A41737294FDD2EF4C7CDD6CAE9FB8F8D227D7348054BECA5A7FA5C |\n| NewRelicDotNetAgent_10.19.1_x64.msi        | 1553FE508663D979A959D8CA72A2BDBDD5F730C37F91A6AE64239F1BC05ED72C |\n| NewRelicDotNetAgent_10.19.1_x64.zip        | 7E2502532774D254A6B9197F85AF84981978E824478AFEAF657B5C4E29AC80BE |\n| NewRelicDotNetAgent_10.19.1_x86.msi        | 764217C3B4EDE0EBADC8BA356B7DA83F835D8BAB974944BF66A50589FA61A991 |\n| NewRelicDotNetAgent_10.19.1_x86.zip        | D0A974073188F34914D962ABD06820B74D76E53D85EBCA458BD762F0E8EBCCD8 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date . See the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-19-1","eolDate":"2024-11-08"},{"agent":"dotnet","date":"2023-11-08","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.19.0","features":["Add a supportability metric (Supportability/Logging/Forwarding/Empty) when an \"empty\" log event is not forwarded.","Add automatic browser agent injection for ASP.NET Core v6+ web applications.","Add automatic instrumentation for ASP.NET Core v6+ Razor Pages.","Add automatic instrumentation of MassTransit clients v7.1.0 and newer.","Add new span attributes to more closely match OTel spec.","Allow forwarding of logs where context data is present but the message and exception are missing.","Enable auto-instrumentation for Confluent.Kafka versions 1.4.0 to 2.x.x.","Update RabbitMQ instrumentation to capture more message consumption scenarios."],"bugs":["Ensure log lines are written to the audit log file when audit logging is enabled.","Fix a segfault when using sendDataOnExit with Linux on Docker.","Reduce exception logging on CallVendorApi failures."],"security":[],"supportedOperatingSystems":null,"description":"New features Add a supportability metric (Supportability/Logging/Forwarding/Empty) when an \"empty\" log event is not forwarded. Resolves #1472  (1db5335 ) Add automatic browser agent injection for ASP.NET Core v6+ web applications. (14c6bb1 ) Add automatic instrumentation for ASP.NET Core v6+ Razor Pages. (14c6bb1 ) Add automatic instrumentation of MassTransit clients v7.1.0 and newer. #1282  (3b79002 ) Add new span attributes to more closely match OTel spec. This includes server.address and server.port for database calls, and thread.id where appropriate. (9500d4d ) Allow forwarding of logs where context data is present but the message and exception are missing. Previously, logs with no message or exception were not forwarded, even if they held context data. (1db5335 ) Enable auto-instrumentation for Confluent.Kafka versions 1.4.0 to 2.x.x. (#1990 ) (9f8d22f ) Update RabbitMQ instrumentation to capture more message consumption scenarios. (3b79002 ) Fixes Ensure log lines are written to the audit log file when audit logging is enabled. (#2028 ) (#2029 ) (c6b940d ) Fix a segfault when using sendDataOnExit with Linux on Docker. (#2018 ) (3ac75a0 ) Reduce exception logging on CallVendorApi failures. Resolves #2005  (#2006 ) (bf4102b ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.19.0-1.x86_64.rpm | 974F97AB59C6238E0FB581D460BC6947333687AC4F7CDC4ECD643F4DB82A70A3 |\n| newrelic-dotnet-agent_10.19.0_amd64.deb    | B04EF61A2806A1C72C3C1914207332BE8AC33517F57D88069B4F73D9E3FBD24A |\n| newrelic-dotnet-agent_10.19.0_amd64.tar.gz | FF51604E6568C6DB0134916C0ACFC5B3E456B85CC0312A6CA904C94B10DCBA74 |\n| newrelic-dotnet-agent_10.19.0_arm64.deb    | A0A50986BC4679D5ACAE399FF4E05EF3F2F5C7840F2BB88E5B3BDE7E2843630F |\n| newrelic-dotnet-agent_10.19.0_arm64.tar.gz | 824B3E844576246C913FE8550CDFD163DED17E69B994F50A3DAD8C43836DC3CE |\n| NewRelicDotNetAgent_10.19.0_x64.msi        | 1122F7F497D07D7FB8B01033B730938BB23AC7241322863F2913F54043D367D5 |\n| NewRelicDotNetAgent_10.19.0_x64.zip        | C0B151EF5C6F8010E56AD238C0B382CDA36AE923229E25C29192D7BDD7EBC5CD |\n| NewRelicDotNetAgent_10.19.0_x86.msi        | 62FC78CD6189FD16E0698A4685265AAE7FB98A54C4D3C88CAA1E10F64307C270 |\n| NewRelicDotNetAgent_10.19.0_x86.zip        | C43A28596AC7B785D14BC66526937C625EBA3D836B92671741B61B1626E1A262 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-19-0","eolDate":"2024-11-08"},{"agent":"dotnet","date":"2023-10-17","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.18.0","features":["Enable configuration of High Security Mode via environment variable (NEW_RELIC_HIGH_SECURITY).","Enable startup logging to Event Log for all applications on Windows."],"bugs":["Detect Docker container id on cgroup v2.","Update Serilog EventLog sink configuration to enable event source creation (if the app is running with admin privileges)."],"security":[],"supportedOperatingSystems":null,"description":"New features Enable configuration of High Security Mode via environment variable (NEW_RELIC_HIGH_SECURITY). (a86d98d ), closes #1948 Enable startup logging to Event Log for all applications on Windows. (#1969 ) (cdac8b7 ) Fixes Detect Docker container id on cgroup v2. (#1943 ) (9c7e114 ) Update Serilog EventLog sink configuration to enable event source creation (if the app is running with admin privileges). (#1963 ) (274072b ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.18.0-1.x86_64.rpm | B030DD515D6C7EFEA25BD4FB4AC72EABB67BC159B666077817EC20929DF88F46 |\n| newrelic-dotnet-agent_10.18.0_amd64.deb    | D3CCCFD0CBD561B7BFDEE727861AE5D8FE76C4E810B7D2E311C86CB224430209 |\n| newrelic-dotnet-agent_10.18.0_amd64.tar.gz | 3B57E85BC7129D103880CD210B1A9E764D81D7DFB457DA0D7BB5D8CC0488E904 |\n| newrelic-dotnet-agent_10.18.0_arm64.deb    | 1B6C47FFEF30CF72B440889DE3749B917456B7336855224D4AD712C256A9282A |\n| newrelic-dotnet-agent_10.18.0_arm64.tar.gz | D3F3CB72F17B7386F6F4FFF8AAF1CB335DD69A45590E22008B6C7DA23537403C |\n| NewRelicDotNetAgent_10.18.0_x64.msi        | 04FB52FE54801B06D155831D5AA4065087AF870770F832514B761064A45ED3D4 |\n| NewRelicDotNetAgent_10.18.0_x64.zip        | 020DB3263BE55DCEF1EFD1FAD80340A365952092C7A436A077CCDC962875B2A4 |\n| NewRelicDotNetAgent_10.18.0_x86.msi        | 024C10F6B9830A4DAB2FD18F55EF15F1AA6ABD63F5FFC359EEA965101FFDFAB4 |\n| NewRelicDotNetAgent_10.18.0_x86.zip        | 372590D12D69FE61172A24E36C88C54768CD090AA2EB8049634DD9AB827805B3 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-18-0","eolDate":"2024-10-17"},{"agent":"dotnet","date":"2023-09-26","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.17.0","features":["Add more detail to \"heartbeat\" message in log.","Use structured logging for internal logs."],"bugs":["Reinstate max number of log files."],"security":[],"supportedOperatingSystems":null,"description":"New Features Add more detail to \"heartbeat\" message in log. (#1884 ) (c0c1362 ) Use structured logging for internal logs (#1903 ) (0031700 ) Fixes Reinstate max number of log files. (#1930 ) (41eef7b ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.17.0-1.x86_64.rpm | 2A02FC288EDDD1BACABA9E9A1BF5D864932081C0DA3238767DD0B81785F77485 |\n| newrelic-dotnet-agent_10.17.0_amd64.deb    | 99B03F39E80250E9962F5C4789C22A3A3FCD20CE8A0FB458C0065109377E414D |\n| newrelic-dotnet-agent_10.17.0_amd64.tar.gz | 26EE53058E7AB044FF896F9641C6592C37F5ADFE5D7C809B7DECDB0D0714FFB8 |\n| newrelic-dotnet-agent_10.17.0_arm64.deb    | E6FA46B9356F47A63B6A5FF4E2ABA4240ED2598BC84546AF6D5BF746A9C494E9 |\n| newrelic-dotnet-agent_10.17.0_arm64.tar.gz | 98226BC0FF1B7B015ECF867536D49148E817533E265E911862ECA2D0F6C6E978 |\n| NewRelicDotNetAgent_10.17.0_x64.msi        | 8FEA2A59FDE61657D3C1C049445B273D13EAE980AF111AC5B92E36E5C29C80BC |\n| NewRelicDotNetAgent_10.17.0_x64.zip        | 958B664396C771292E5987A306E6CEFD7514FAF88F47C426935D98B240FDD709 |\n| NewRelicDotNetAgent_10.17.0_x86.msi        | 694B774708344150824799EFE13270FA4F615B3FC2CFF72C430C8B125A1E8175 |\n| NewRelicDotNetAgent_10.17.0_x86.zip        | 25E036594252C51F4F29CC94AB5F77EE34D124603DAA923A8D788EC31ED15B19 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-17-0","eolDate":"2024-09-26"},{"agent":"dotnet","date":"2023-09-12","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.16.0","features":["Add 32bit profiler path to IIS registry when installing 64bit agent.","Prevent using different bitness installer when in-place upgrading."],"bugs":["Fix misleading log message on transaction name change.","Fix NRHttpClientFactory so that it creates only one client.","Prevent broken traces when HttpClient content headers contain tracing headers.","Remove the retained file count limit for Agent log files."],"security":[],"supportedOperatingSystems":null,"description":"Notice The transactionTracer.stackTraceThreshold setting has been deprecated and no longer has any effect. (#1896 ) (20ab0e7 ) New Features Add 32bit profiler path to IIS registry when installing 64bit agent. (#1890 ) (65dd50b ) Prevent using different bitness installer when in-place upgrading. (#1890 ) (65dd50b ) Fixes Fix misleading log message on transaction name change. (#1857 ) (#1886 ) (737b4f1 ) Fix NRHttpClientFactory so that it creates only one client. (#1873 ) (fc88ff7 ) Prevent broken traces when HttpClient content headers contain tracing headers. (#1843 ) (#1888 ) (541dd2c ) Remove the retained file count limit for Agent log files. (#1879 ) (e49250a ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.16.0-1.x86_64.rpm | FD89D6E43C864A63673644EDA742BFAA13C0E8BC6111C2B3FCD878A4B0AA54DD |\n| newrelic-dotnet-agent_10.16.0_amd64.deb    | DA8C6EFB5FD9EA5670B8370B2276A42466199F7C3FB8DF91C82EE524FB1A0E1B |\n| newrelic-dotnet-agent_10.16.0_amd64.tar.gz | F2EE033A647CBA3D38AE48191BAB42F9BD73B46AAF835B0A4AE0DE2102E1E5CD |\n| newrelic-dotnet-agent_10.16.0_arm64.deb    | 0A025E5B04063E3F15668D611AD6FB4742A15742670C66DF2096D745D95407B2 |\n| newrelic-dotnet-agent_10.16.0_arm64.tar.gz | CD79725E2A6AC1943068E7DC4E6D1D23D3D6CCDF6AC90CEA5F50E02B6AD81DC1 |\n| NewRelicDotNetAgent_10.16.0_x64.msi        | CC63CC96DB417EBC28175A758246DF3EB6BFEFA189EB2396CF82ACF1D93A540E |\n| NewRelicDotNetAgent_10.16.0_x64.zip        | 2EA1E3F9CD7CE2851E4EEE89D94BEFEDF10A601CD182557C3AA90BD7069833D3 |\n| NewRelicDotNetAgent_10.16.0_x86.msi        | 0C35D1FB242061171252518BD6DE92216575CC1C9B7D7234C6590FACE6B27A92 |\n| NewRelicDotNetAgent_10.16.0_x86.zip        | 660752DE75F147FAF1F662DCF1134AE690598409B84CC88A51715777B2837A1B | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-16-0","eolDate":"2024-09-12"},{"agent":"dotnet","date":"2023-08-29","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.15.0","features":["Add support for Serilog.Extensions.Logging and NLog.Extensions.Logging.","Log a warning when an unsupported .NET version is detected.","Use HttpWebRequest instead of HttpClient on .NET Framework."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Features Add support for Serilog.Extensions.Logging and NLog.Extensions.Logging. (#1860 ) (#1859 ) (ad24201 ) Log a warning when an unsupported .NET version is detected. (#1852 ) (7da3e59 ) Use HttpWebRequest instead of HttpClient on .NET Framework (#1853 ) (8d6cf0f ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.15.0-1.x86_64.rpm | 76CC53EB6BD61AAFB4ECA6E1D6E4D55F9247502502F835C32351B1E577C7400D |\n| newrelic-dotnet-agent_10.15.0_amd64.deb    | 213A3D41177C20CFB37E68D19CAF98A4AA014E1D69FE6F3C438EC50895C0D562 |\n| newrelic-dotnet-agent_10.15.0_amd64.tar.gz | 1DF8FF60780AE05D56277A9414DA0C1C2A436C56C864E5E5959706D1323E84F5 |\n| newrelic-dotnet-agent_10.15.0_arm64.deb    | 1E678FC5D9124C55789D88781BE257FE8A1A45F11DE1C2B677E782725E049D47 |\n| newrelic-dotnet-agent_10.15.0_arm64.tar.gz | 441F7411DF339E696069C051302647732A0535312529F5AF51E1693F25E35256 |\n| NewRelicDotNetAgent_10.15.0_x64.msi        | 9B980CE512E5F85C73C7EF814E9C61DB3B14FB6AD88373359F063D9E651970BC |\n| NewRelicDotNetAgent_10.15.0_x64.zip        | A00ECE00905199AAEB6DE7AE9CA37C07EDC87EE2794D703330087F979AF20E57 |\n| NewRelicDotNetAgent_10.15.0_x86.msi        | 7784AB50CF7FF9AFE0193ADAA7FAF06CF4061FA096652140284DF0269B5AADCD |\n| NewRelicDotNetAgent_10.15.0_x86.zip        | 58A106ACAAEF28545F319D4F3D640A023C0F0F407173553AA9CBD8588FE2DD5B | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-15-0","eolDate":"2024-08-29"},{"agent":"dotnet","date":"2023-08-08","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.14.0","features":["Add support for Sitecore.Logging."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Features Add support for Sitecore.Logging. (#1790 ) (#1795 ) (6d1934a ) Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.14.0-1.x86_64.rpm | B5259A630AEE43CEA46CD7FD213059DA99E9E95570CA42D7ECA394BD654421D9 |\n| newrelic-dotnet-agent_10.14.0_amd64.deb    | DC0E49A2AB1199541871744F2FB276C6F8C850A1CA486D90DF5717434A454F5E |\n| newrelic-dotnet-agent_10.14.0_amd64.tar.gz | F3607C0A7C8F1B048BFB4273189343E0ABC46B3712D1601041AF512A4462BC7D |\n| newrelic-dotnet-agent_10.14.0_arm64.deb    | 13F5A8CD9DA721C9DD28CC352EF8B871FDECCE65EEF48346714D33B821337592 |\n| newrelic-dotnet-agent_10.14.0_arm64.tar.gz | 606834C550B58A7E993E81708BD81C663E33DB09B03D18B9FE9BA455EA7D373B |\n| NewRelicDotNetAgent_10.14.0_x64.msi        | E72379F5101E9F6FD90EEEA2BDD18E0480C6CA74A508A107D718CB28CEE935E1 |\n| NewRelicDotNetAgent_10.14.0_x64.zip        | 5C43D2BEB306AB8F5BF85761950730F191B30C400B933F58CADC642D166A68F7 |\n| NewRelicDotNetAgent_10.14.0_x86.msi        | F665FFC6A6C7FD3B1A170E384CB4F28DAD3E5FB14AFF8BCFEDE19606999502CB |\n| NewRelicDotNetAgent_10.14.0_x86.zip        | 625A54A79D87CA56466E4CAD5162C4D0C59AA8D0DE4EF94025274046EFC359EC | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-14-0","eolDate":"2024-08-08"},{"agent":"dotnet","date":"2023-07-18","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.13.0","features":["Add support for filtering log events based on a list of log levels so that they are not forwarded to New Relic. Also adds new logging metrics to count the total number of filtered log events (Logging/denied).","Instrument OpenAsync() for SQL libraries."],"bugs":["Refactor StackExchange.Redis v2+ instrumentation to eliminate potential memory leaks.","Remove invalid trailing comma added to W3C tracestate header.","Update the MSI UI to clean up formatting and readability issues."],"security":["Update Grpc.Net.Client library to address Dependabot alerts."],"supportedOperatingSystems":null,"description":"Security Update Grpc.Net.Client library to address Dependabot alerts. (#1768 ) (#1769 ) (eee7564 ) New Features Add support for filtering log events based on a list of log levels so that they are not forwarded to New Relic. Also adds new logging metrics to count the total number of filtered log events (Logging/denied). Refer to our application logging configuration  documentation for more details. (#1760 ) (#1761 ) (#1762 ) (#1766 ) (aadce3a ) Instrument OpenAsync() for SQL libraries. (#1725 ) (a695ce6 ) Fixes Refactor StackExchange.Redis v2+ instrumentation to eliminate potential memory leaks. (902b025 ) Remove invalid trailing comma added to W3C tracestate header. (#1779 ) (790a3b7 ) Update the MSI UI to clean up formatting and readability issues. (#1748 ) (3fbc543 ) Once published, you can find the release artifacts for this release here  or on NuGet.org . Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.13.0-1.x86_64.rpm | E589D2BD0DA972CB8ECE27A2BCC55E5EC5724F049AEF1993606F1AFBCE7E34B9 |\n| newrelic-dotnet-agent_10.13.0_amd64.deb    | BB8A5F34E85CAA468BEFED90803339A49E6139618CAB208493772F76F95E1321 |\n| newrelic-dotnet-agent_10.13.0_amd64.tar.gz | 730089417451F14E749BBAF5B66482FDBA920CE0D313999A1AB51F6F6388C613 |\n| newrelic-dotnet-agent_10.13.0_arm64.deb    | 9079245A6BCA2589B8A6A71AD62B8BE1944BA3B3F6A56446FE488385E6E70AE1 |\n| newrelic-dotnet-agent_10.13.0_arm64.tar.gz | DFAC11B4E07118F2C1F1E28F78785CE61EE96D1EEFAD1F3116F83994AD60B59E |\n| NewRelicDotNetAgent_10.13.0_x64.msi        | 5B37B9736B32B0D32466115066BC43EB5D1D59C08749E5BB5A04A1431B31907A |\n| NewRelicDotNetAgent_10.13.0_x64.zip        | EDE778E4393772439BAE0EFB5266604A18028CBBB955B9A40C543ECAEF6B51F9 |\n| NewRelicDotNetAgent_10.13.0_x86.msi        | A66A75309281CBC902E393EC391F0FBB849A7BA9F115E4F72C82A830EC2E5312 |\n| NewRelicDotNetAgent_10.13.0_x86.zip        | 9B9A94D705B66C326FCE83794B08D6C45EEEC4BF796B4F9E1B994DFBFB587407 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-13-0","eolDate":"2024-07-18"},{"agent":"dotnet","date":"2023-06-27","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.12.1","features":[],"bugs":["Resolved an issue in the `all_solutions.yml` workflow where the MSI installers were built with a self-signed certificate rather than the production code signing certificate."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Resolved an issue in the all_solutions.yml workflow where the MSI installers were built with a self-signed certificate rather than the production code signing certificate. (386a277 ) Once published, you can find the release artifacts for this release here  or on NuGet.org . Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.12.1-1.x86_64.rpm | 93229E66F85ADD5C8DE3613DE5DABD5F478A39950B3C2BD91107A8DA887F2B6A |\n| newrelic-dotnet-agent_10.12.1_amd64.deb    | A7290CB37CBE3F292E29DE38094CDD64476256F9F39684A1FCD15766C41D8BF7 |\n| newrelic-dotnet-agent_10.12.1_amd64.tar.gz | 532BF3165293BBCFBD2A10FA91A7D6BC401CFAE02CF66B8B12FE41007694BACB |\n| newrelic-dotnet-agent_10.12.1_arm64.deb    | 7855DACADEF0ED0488378FDBA47029F7F230714CA0A36DA13F45650C4B2332AD |\n| newrelic-dotnet-agent_10.12.1_arm64.tar.gz | 84E67F92D9A378EF036C4462CEAE1BE3760DBEE331DD1EBE99305726CDE29355 |\n| NewRelicDotNetAgent_10.12.1_x64.msi        | F0D5070F786929550C230BE50920A24A701639D398A8BF5BA33C187231B0C94C |\n| NewRelicDotNetAgent_10.12.1_x64.zip        | 32AE640A2F2C4F672206D528E6EE950C8DE1CF6F159D822CF97513A033AFA307 |\n| NewRelicDotNetAgent_10.12.1_x86.msi        | 58374479848A26A164E19424E9BAA00E164AC05F2A2D8B658C7C865CAAFB31FA |\n| NewRelicDotNetAgent_10.12.1_x86.zip        | B6D8A5B29D1088AD387A372B805064B78DCCCC7AE3A5CF0DFA76DD996ED3791A | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-12-1","eolDate":"2024-06-27"},{"agent":"dotnet","date":"2023-06-26","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.12.0","features":["Add instrumentation for newer MongoDB.Client methods.","Add support for MySql.Data version 8.0.33+."],"bugs":["Add more validation to msi installer.","Cache the AgentEnabled setting value.","Exclude WebResource.axd and ScriptResource.axd from browser instrumentation (via default config).","Format and log audit-level messages only when audit logging is enabled.","Handle empty Request.Path values in AspNetCore middleware wrapper.","Include config file path in the \"Agent is disabled \" message on all platforms.","Update install script to correctly stop and restart IIS."],"security":[],"supportedOperatingSystems":null,"description":"New Features Add instrumentation for newer MongoDB.Client methods. (#1732 ) (1aa5680 ) Add support for MySql.Data version 8.0.33+. (#1708 ) (69d15df ) Fixes Add more validation to msi installer. (#1716 ) (d7bb7f2 ) Cache the AgentEnabled setting value. (#1723 ) (1624938 ) Exclude WebResource.axd and ScriptResource.axd from browser instrumentation (via default config). (#1711 ) (2fcce95 ) Format and log audit-level messages only when audit logging is enabled. (#1734 ) (f71521f ) Handle empty Request.Path values in AspNetCore middleware wrapper. (#1704 ) (8b734a5 ) Include config file path in the \"Agent is disabled \" message on all platforms. (#1727 ) (1a56612 ) Update install script to correctly stop and restart IIS. (#1740 ) (3b91dff ) Once published, you can find the release artifacts for this release here  or on NuGet.org . Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.12.0-1.x86_64.rpm | 26C56108CEDDB22090EE5DD101C4A7E9B0D6D8285D50B7845CAE25F4F9B925EE |\n| newrelic-dotnet-agent_10.12.0_amd64.deb    | 22A4D7250944235B79419E2FE65DB6143365286A4DAA18E28BB6DC8B31CBFC6C |\n| newrelic-dotnet-agent_10.12.0_amd64.tar.gz | 9253433AEA7A340EB8EF32BF6236929D20E23BDF2EAC2068B45E02652EDE8D98 |\n| newrelic-dotnet-agent_10.12.0_arm64.deb    | 7ECD087B9BB2F41E01C9D9C6AB002D953F87D4531B9A572F0CC03ABF9CA33816 |\n| newrelic-dotnet-agent_10.12.0_arm64.tar.gz | CAEBCBDD60559D7337F126044FCE403190CD5A3DE98C2761538D8E7324A0635B |\n| NewRelicDotNetAgent_10.12.0_x64.msi        | 453A1BAC9FE971250AF8AC1A83EFFFB3528E13F8759E793C35FA4C068B371924 |\n| NewRelicDotNetAgent_10.12.0_x64.zip        | 9225783BD0CA78E3C6D80BA88806FDE1C9FC293B1872CA1B9C3C9EE3B5367E18 |\n| NewRelicDotNetAgent_10.12.0_x86.msi        | 4A6EDEDE498C29049A2ECF9ECBE09032D7B23AAB53311BF9B4C6857117C47C94 |\n| NewRelicDotNetAgent_10.12.0_x86.zip        | 95EFAE598174C1A0193BD0DFB5A0353C3D966556CF82CC829DB7E8A678BCAAD4 | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents . We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date .\nSee the New Relic .NET agent EOL policy doc  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-12-0","eolDate":"2024-06-26"},{"agent":"dotnet","date":"2023-06-07","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.11.0","features":["Add detailed assembly reporting to enable Vulnerability Management support.","Add minimal support for Devart Oracle client.","Use Serilog instead of log4net for internal logging."],"bugs":["Clear transaction context for held transactions and async WCF client instrumentation timing.","Stop double injecting headers with HttpClient on .NET Framework"],"security":[],"supportedOperatingSystems":null,"description":"We recommend you update the agent regularly, at least every 3 months. Read more about keeping your agent up to date . This release is supported for one year after its release date. For a full list of supported versions and their support periods, please see our EOL policy doc . New Features Add detailed assembly reporting to enable Vulnerability Management support. (#1685 ) (f249753 ) Adds minimal support for Devart Oracle client. (181a628 ) Use Serilog instead of log4net for internal logging.  (#1661 ) (51080df ) Fixes Clearing transaction context for held transactions and async WCF client instrumentation timing. (#1608 ) (db9a48e ) Stop double injecting headers with HttpClient on .NET Framework (#1679 ) (e8bdc34 ) Once published, you can find the release artifacts for this release here  or on NuGet.org . Checksums | File                                       | SHA - 256  Hash                                                  |\n| ------------------------------------------ | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.11.0-1.x86_64.rpm | 00890284A4CEDE8C74A55B137E439BD9779C7C34928C619BA1F4B49B2943BC53 |\n| newrelic-dotnet-agent_10.11.0_amd64.deb    | 0E311777C9B9CE3F19CE2BCD86ED73B9141BF61B9C7B9781A2454676B0607063 |\n| newrelic-dotnet-agent_10.11.0_amd64.tar.gz | 8A00AAC013EA551B2F34E85DBA2F9D5B097CAF75E236EAC45E26FBCB6D929D43 |\n| newrelic-dotnet-agent_10.11.0_arm64.deb    | 829737C856438C4B9FB5A7287EE3203A473AEE8511357BE301EB741C2DA8A160 |\n| newrelic-dotnet-agent_10.11.0_arm64.tar.gz | 7A1E0088AFB35909FC76F462F97E819479F62F18795BBDE4A0B9C381227B6695 |\n| NewRelicDotNetAgent_10.11.0_x64.msi        | CA9329B32FFB50DBADEF0657FD20BD309C2240744B444D2D7927F9B78A5292FA |\n| NewRelicDotNetAgent_10.11.0_x64.zip        | 6561B1283B2C01AC740D3FD9D52B1FCA01A6449EF103B07BE630F23CDECEFCE3 |\n| NewRelicDotNetAgent_10.11.0_x86.msi        | 1B38DEF4444FE27F10017293691C743BBED74ABB5255D755F6DEE72E0F8BA8C6 |\n| NewRelicDotNetAgent_10.11.0_x86.zip        | 2072DFA2A737A0B57E9ED08954D8059DBF56C36D02194DC7F91CE688CA19CC8D | Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-11-0","eolDate":"2024-06-07"},{"agent":"dotnet","date":"2023-04-26","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.10.0","features":["Add additional logging when RUM injection is being skipped.","Add instrumentation for .NET Elasticsearch clients.","Move TLS config logging closer to connect."],"bugs":["Add missing instrumentation to MSI installer","Add NServiceBus instrumentation to the MSI installer for .NET Core/5+.","IsOsPlatform() can fail on older .NET Framework Versions."],"security":[],"supportedOperatingSystems":null,"description":"We recommends you to update the agent regularly, at least every 3 months. Read more about keeping your agent up to date . This release is supported for one year after its release date. For a full list of supported versions and their support periods, please see our EOL policy doc . As of this release, the oldest supported version is .NET agent 8.27.139.0 . New Features Add additional logging when RUM injection is being skipped. (#1561 ) (e1b8eca ) Add instrumentation for .NET Elasticsearch clients. (#1575 ) (8e49d7b ) Move TLS config logging closer to connect. (#1562 ) (0ff3ddd ) Fixes Add missing instrumentation to MSI installer (#1569 ) (b65b117 ) Add NServiceBus instrumentation to the MSI installer for .NET Core/5+. (#1576 ) (3cae03e ) IsOsPlatform() can fail on older .NET Framework Versions (#1552 ) (699c205 ) Once published, you can find the release artifacts for this release here  or on NuGet.org . Checksums File SHA - 256  Hash newrelic-dotnet-agent-10.10.0-1.x86_64.rpm 8429831E81012C58359083083766DC3FA8D2156ACCEA5D77FE9486965E3CAC88 newrelic-dotnet-agent_10.10.0_amd64.deb 7BC7C9631BA1055C9CFD7CE6A40BCB4A91C59709CA05920B4D8474BFA5DDB2DE newrelic-dotnet-agent_10.10.0_amd64.tar.gz 0B8F7D49CC28A568D9316C9DBD1560CE15AB23886F3DFDC89A55E447BD37DB0E newrelic-dotnet-agent_10.10.0_arm64.deb 706B5A22CB6A814BF56B2E5752EA24573F9DDD96314E6443824D127BB569CD49 newrelic-dotnet-agent_10.10.0_arm64.tar.gz 7C373CC56FFCD75637210042FD8410C1A31DF4A45A7BA54451AC82781C3595CE NewRelicDotNetAgent_10.10.0_x64.msi 779AB4D7223381A436414AC905F2124251557C79B6C1C8F5BC9911D9D339ABD5 NewRelicDotNetAgent_10.10.0_x64.zip BB1F08E489C3726EED3516FC115AEC6754917123B3E8CE4AD0C742A8FDD6635D NewRelicDotNetAgent_10.10.0_x86.msi 0F6DFE2FFD1563145A209D5F1A211E52750C7DCA2AAEA069705FE47BEC186D02 NewRelicDotNetAgent_10.10.0_x86.zip 04227164837B98C618EF86620E15E9D862939994CF7BCD93752C62DF9820401B Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-10-0","eolDate":"2024-04-26"},{"agent":"dotnet","date":"2022-09-12","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.1.0","features":["Add support for label creation via application configuration files","Log agent environment variables at debug level during startup","Capture and forward exception details for log events","Add new API to set the segment or span name"],"bugs":["Fix intermittent logs in async scenarios","Properly calculate event pool limits when configured via environment variable"],"security":["Respect the configured log level for Microsoft.Extensions.Logging instrumentation"],"supportedOperatingSystems":null,"description":"Notice:  If using Microsoft.Extensions.Logging as your logging framework of choice, please use .NET agent version 10.1.0 or newer.  We encourage you to adopt the newer version due to bug #1230 , which we fixed in #1237 , that was resolved in .NET agent version 10.1.0. New Features Support of setting up labels via appsettings.json and app/web.config file. #1204 Additional DEBUG-level logging of all environment variables. Forwarded application logs now capture exception details including, error message, error stack, and error class. #1228 Log events with no message will now be accepted if an exception is present in the log event. The error stack is created using the stack of the inner exception, up to 5 levels deep, just like existing Agent error reporting. Adds a new SetName() method to the Agent API for spans which allows customization of segment/span/metric names. #1238 Fixes Resolves an issue where log forwarding could drop logs in async scenarios. #1174 Resolves an issue where more logs were forwarded than expected from Microsoft.Extensions.Logging. #1237 Resolves an agent configuration bug where values set in the MAX_EVENT_SAMPLES_STORED and MAX_TRANSACTION_SAMPLES_STORED environment variables, which configure the maximum samples stored per one-minute harvest interval, were not being properly converted to apply to the five-second harvest interval for those data types. #1239 Checksums | File                                      | SHA - 256  Hash                                                  |\n| ----------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.1.0-1.x86_64.rpm | 44B3FF7D21084633900F26EA1174DA58562100EC5469BDD9C297E608435C3F1D |\n| newrelic-dotnet-agent_10.1.0_amd64.deb    | 64609D1E3B1B4BE0912F723CED0EA629DA4E5129F676E2B20A83830714D1E63F |\n| newrelic-dotnet-agent_10.1.0_amd64.tar.gz | 3F479B759C6FC953FD8DB2954C4E0577AB51DD22185B2EA44948BAFB2D67A74A |\n| newrelic-dotnet-agent_10.1.0_arm64.deb    | D7B61C6227FF2FB7269DD777F475BFA6E56EB39E98D66078339FF74E63D174A1 |\n| newrelic-dotnet-agent_10.1.0_arm64.tar.gz | EFB9FD6121884E14F1EA8D48324D48DA216CD0FFDAA6CC356FB82DEC3D7215C3 |\n| NewRelicDotNetAgent_10.1.0_x64.msi        | DF62C96B669A72A1B428A1F8DDD14453DA58DE36BE74BD5FC05D8571365BC610 |\n| NewRelicDotNetAgent_10.1.0_x64.zip        | E0FCCD38C7B302C44B2892FA41B05536B75C7E8576FB4491EF6B6BFB987237AD |\n| NewRelicDotNetAgent_10.1.0_x86.msi        | AFBEAFC5A2E1701801FB2181DBD3445CA26C3F08BE87EB8BE098988A2CA36026 |\n| NewRelicDotNetAgent_10.1.0_x86.zip        | 05FB612F76647777547F1E105960D55C08DF8296E348986C56CB558DB83830BB | Support statement New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.19.353.0 . Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-1-0","eolDate":"2023-09-12"},{"agent":"dotnet","date":"2022-07-19","downloadLink":"https://download.newrelic.com/dot_net_agent/latest_release","version":"10.0.0","features":["Add Log Forwarding support for Microsoft.Extensions.Logging in .NET framework applications","Report all non-sensitive configuration options during agent connect"],"bugs":["Resolve situation where the slowest transaction trace was not always reported","Add SMSvcHost.exe to internal agent ignore list","Update Application Logging attribute log.level to be level"],"security":[],"supportedOperatingSystems":null,"description":"Notice:  If using Microsoft.Extensions.Logging as your logging framework of choice, please use .NET agent version 10.1.0 or newer.  We encourage you to adopt the newer version due to bug #1230 , which we fixed in #1237 , that was resolved in .NET agent version 10.1.0. New Features Adds support for forwarding application logs to New Relic for .NET Framework 4.6.2 and newer applications using Microsoft.Extensions.Logging. #1172 Additional agent configuration options are now visible and easily accessible through the UI on NR1. Agent configuration is also now reported during agent connect. This information can be seen in the APM->Environment->Agent Initialization view. #1174 Fixes Resolves an issue with transaction trace aggregation where the slowest transaction trace was not always captured due to a race condition. #1166 Adds an ignore rule to prevent profiling SMSvcHost.exe. #1182 Updates applicationLogging attribute log.level to be level. #1144 Deprecations/Removed Features This is a major release of the agent, and contains breaking changes. See the migration guide  for details. This agent release targets .NET Framework 4.6.2 and .NET Standard 2.0. The minimum supported runtime versions for profiled applications are .NET Framework 4.6.2+ and .NET Core 3.1+. The scriptable installers have been removed. #1170 Windows installation files have been consolidated and renamed. #1187 The Linux installation packages have been renamed. #1180 Castle.Monorail instrumentation has been removed. #1177 Checksums | File                                      | SHA - 256  Hash                                                  |\n| ----------------------------------------- | ---------------------------------------------------------------- |\n| newrelic-dotnet-agent-10.0.0-1.x86_64.rpm | 0D8501038F29E563F9B94473A54976421CDC84B6A9596615D29E7CCFD76B85F3 |\n| newrelic-dotnet-agent_10.0.0_amd64.deb    | C0C111356EBF540A6DCA57D144A7946639A09D20FC000F364C392B4E1FAB2CD9 |\n| newrelic-dotnet-agent_10.0.0_amd64.tar.gz | 24F788273F257DCA688676962E415A2AA66BC6548503781E60139F131DC096A6 |\n| newrelic-dotnet-agent_10.0.0_arm64.deb    | EAEF890DD7B4B349A4CCB1CEFE50137346F82CF92510627A4946D441BD4EA2D0 |\n| newrelic-dotnet-agent_10.0.0_arm64.tar.gz | 4F1042CBD4F2E19902B2BF7AF38275E3152C38C667F7BB1C07A55FA3F238377E |\n| NewRelicDotNetAgent_10.0.0_x64.msi        | 00B3D8C00B94334E30FB2B6016F293392C5F8FD493C82F2010DA44FDE68F02D6 |\n| NewRelicDotNetAgent_10.0.0_x64.zip        | 48B8BDF456CA3EB8AAAF173038CF1CC5D5A7399558D4146FB8204F3A57AD3ED9 |\n| NewRelicDotNetAgent_10.0.0_x86.msi        | 88D4EA3C0A98DF3474B69EFA9374EECD0D542967433530643132E49F08EF22BC |\n| NewRelicDotNetAgent_10.0.0_x86.zip        | 39B163EF4433994CD1D20E7883ECA0101CB53B920FF3D0353D5950D62BD8A95E | Support statement New Relic recommends that you update the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is .NET agent 8.29.0 . Updating Follow standard procedures to update the .NET agent . If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-0-0","eolDate":"2024-07-19"},{"agent":"dotnet","date":"2019-10-17","downloadLink":null,"version":"8.20.262.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Improved support for WCF. Support for Task-based (TAP) service calls. Distributed Tracing and CAT are automatically supported for HTTP-based binding types (such as BasicHTTP, WebHTTP, WSHTTP). Non-HTTP binding types (such as NetTCP, MSMQ, Named Pipes) are instrumented, but do not automatically support Distributed Tracing and CAT. [.NET Core]  Adds support for .NET Core 3.1 beginning with preview 1. Performance Metrics: The .Net Agent collects information about application performance in the following areas. Memory and CPU Utilization Garbage Collection Threadpool Usage and Throughput Please refer to online documentation  for further information. Fixes [.NET Framework]  Fix an issue where reading application settings from web.config or app.config could prevent the agent from starting up. [.NET Framework]  Fix an issue where the agent caused an application to deadlock when using a ConfigurationBuilder . This was commonly seen in applications using the AzureKeyVaultConfigBuilder . Fix an issue introduced in 8.16 where Memory and CPU metrics failed to update. Upgrading Follow standard procedures to update the .NET agent . If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents .","slug":"docs/release-notes/agent-release-notes/net-release-notes/agent-8202620","eolDate":"2022-10-17"},{"agent":"java","date":"2026-07-29","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/9.4.0/","version":"9.4.0","features":["Removal of @NewField annotations from some modules","Cluster mode support for Lettuce 6.0 and 6.5","New modules for Vert.x web and Vert.x core 5.x","Java Server Faces instrumentation","Portlet instrumentation","Update of shadow build-time plugin","Legacy point cut removals","http.request.method attribute added to external calls","Decorate JFR data with APM labels","Decorate OTel dimensional metrics with otlp_resource_attributes"],"bugs":["MDC leak in Log4j2","Remove java.rmi namespaced exceptions","Correct servlet exception attribute key for WildFly 27","Fix servlerless mode console output","Cleanuo up shadowed enum values","Netty Reactor HTTP segment cleanup","Token count for async operations"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Removed linking metadata blob @NewFields from log4j-2.11 module 2917 Added support for cluster mode in the lettuce-6.0 and lettuce-6.5 modules 2922 Added new instrumentation modules for Vert.x web and core 5.x 2920 Added new Java Server Faces instrumentation modules to replace legacy point cuts 2944 Added a new Portlet module to replace legacy point cuts 2953 Migrated shadow plugin from com.github.johnrengelman to com.gradleup 2945 Added weave class instrumentation replacement for HandlerMethodInvoker3PointCut point cut 2967 Removed @NewField annotations from the jdbc-generic module 2963 Removed HandlerMethodInvokerPointCut point cut 2977 Removed SpringPointCut point cut 2990 Added new http.request.method attribute to all external HTTP spans 2985 \n3010 Added support for decorating JFR data with APM labels (as configured in the java agent) 3007 [Hybrid Agent] Decorated OpenTelemetry dimensional metrics with otlp_resource_attributes from connect response 2956 Fixes Fixed MDC leak issue in the apache-log4j-2.11 module 2926 Removed java.rmi namespaced exceptions 2932 Used Jakarta servlet exception attribute in the wildfly-27 module 2929 Serverless mode now sent payload to the console if file pipe wasn't written 2975 Changed ForceRestartException log to INFO 2989 Added a new build time Patcher instance to remove problem enum values from the shadowed jspecify library @NullMarked class 2982 Cleaned up segment instances for Netty Reactor HTTP calls 3004 Fixed transaction linking metadata during some async operations 3006 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-940","eolDate":"2027-07-29"},{"agent":"java","date":"2026-05-28","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/9.3.0/","version":"9.3.0","features":["Solr 9 JMX module","New centralized token counting strategy for capturing token counts from LLM Responses.","Support for capturing JDBC batch operations; specifically the addBatch() and executeBatch() methods.","XML RPC instrumentation module to replace legacy point cut","Add a new JFR specific config `jfr.use_display_name`.","Remove unneeded segment creation in java.xmlrpc module","Update aws-bedrock-runtime-2.20 Module with a new token counting strategy for each of the models.","New license key obfuscation algorithm","Support for Micronaut Http Clients versions 3.5.0+","Support for Apache Camel 3.9.0 and up","Support for Kafka Clients 4.0.0 and up","AWS DAX Support starting from 2.0.0 to latest","Add instrumentation for Spring AI completion and embedding clients for versions 1.0.0 and up.","Core Tracing - Drop SpanEvents and Re-Parent dropped SpanLinks","Support Micronaut's BlockingHttpClient","Add support for AI Model Context Protocol 1.0.0 to latest."],"bugs":["Fixes excessive number of unexpired async tokens when instrumenting Micronaut","Resolution of Mule 4.9 IllegalAccessError","Fix coroutines instrumentation.","Fix a mis-recording of the Instrumented and Kept metrics for Core Tracing, as they were originally being recorded as a time metric."],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Add log_level_denylist config to default yaml 2830 Solr 9 JMX module\n2821 New centralized token counting strategy for capturing token counts from LLM Responses. 2837 Support for capturing JDBC batch operations; specifically the addBatch() and executeBatch() methods. 2840 XML RPC instrumentation module to replace legacy point cut 2841 Add a new JFR specific config jfr.use_display_name. If set to true, the agent will set the JFR host name to the value in the process_host.display_name configuration. The default is false to preserve old behavior. If jfr.use_display_name is true but the display_name config is empty, the JfrService will fallback to the old behavior for the host name. 2847 Remove unneeded segment creation in java.xmlrpc module 2853 Update aws-bedrock-runtime-2.20 Module with a new token counting strategy for each of the models.\n2845 New license key obfuscation algorithm\n2864 Support for Micronaut Http Clients versions 3.5.0+ 2834 Support for Apache Camel 3.9.0 and up\n2896 \n2901 Support for Kafka Clients 4.0.0 and up 2896 Internal dependency Log4j Core Upgrade from 2.17.1 to 2.25.4 2833 AWS DAX Support starting from 2.0.0 to latest 2873 Add instrumentation for Spring AI completion and embedding clients for versions 1.0.0 and up.  This adds new instrumentation modules: 2842 Core Tracing - Drop SpanEvents and Re-Parent dropped SpanLinks 2881 Pointcut replacements Remove SpringDispatcherPointCut and SpringExceptionHandlerPointCut and instead move the functionality into our Spring instrumentation modules. Replace HandlerInterceptorPointCut\n2871 \n2886 Support Micronaut’s BlockingHttpClient 2860 Add support for AI Model Context Protocol 1.0.0 to latest. 2880 Fixes Fix coroutines instrumentation. Fixes include: Better tracking of asynchronous behavior by instrumenting gaps that were found where execution can jump to another thread. Better naming on Coroutines and Continuations. Existing naming was too generic. New naming identifies according to whether it is started via runBlocking, async, withContext or launch. Removed some utility methods that were no longer used\n2802 Fixes excessive number of unexpired async tokens when instrumenting Micronaut. 2792 Resolution of Mule 4.9 IllegalAccessError 2859 Fix a mis-recording of the Instrumented and Kept metrics for Core Tracing, as they were originally being recorded as a time metric. 2881 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-930","eolDate":"2027-05-28"},{"agent":"java","date":"2026-04-08","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/9.2.0/","version":"9.2.0","features":["“Java 26 support”","“AWS Lambda monitoring”","“Adds log_level_denylist config”","“Auto app naming support for logs”","“Auto app naming support for trace samplers”","“Auto app naming entity supportability metrics”","“Instrumentation for OpenTelemetry 1.59.0+”","“Region aware event/metric ingest URIs”","“Adds Cloud Metadata Bypass Proxy config”","“Adds support for multiple versions of Caffeine”","“Updates core tracing to handle async spans”","“Adds support for explain plans that utilize SQL arrays”","“Adds generic Queue as a transport type”","“Adds support for Reactor Netty Http client”"],"bugs":["“Fix NPE with distributed tracing payload”","“Expires Tokens when a Reactive Subscription is canceled”","“Evict threads from `TheadTracker` cache to prevent a memory leak”","“Resolves a deadlock between harvest thread and JVM shutdown thread”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Adds Java 26 support 2734 Adds Serverless mode for AWS Lambda monitoring with the Java agent 2609  2615  2625  2633  2640  2641  2647  2673  2716  2721  2735  2723  2740  2769  2782  2794  2797  2796  2806 Adds new application_logging.forwarding.log_level_denylist config 2764 Implements region aware event/metric ingest URIs 2749  2790 Adds support for associating logs to corresponding entity when enable_auto_app_naming is true 2627 Add opentelemetry-sdk-extension-autoconfigure-1.59.0 instrumentation for OpenTelemetry 1.59.0+ 2786 Adds support for associating adaptive sampler to corresponding entity when enable_auto_app_naming is true 2805 Adds supportability metrics for each entity created when enable_auto_app_naming is true 2808 Implements Cloud Metadata Bypass Proxy config 2791 Adds support for multiple versions of Caffeine in the agent 2807 Adds support for explain plans that utilize SQL arrays 2815 Adds generic 'Queue' as a transport type 2820 Adds support for Reactor Netty Http client calls 2817 Fixes Fixes an edge case where ill-formed payloads caused an NPE when accessing the sampled field on the NR payload 2762 Expires Tokens when a Reactive Subscription is canceled 2798 Adds logic to manually evict any dead threads from the TheadTracker cache to prevent a memory leak 2811 Resolves a deadlock between harvest thread and JVM shutdown thread 2539 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-920","eolDate":"2027-04-08"},{"agent":"java","date":"2026-02-12","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/9.1.0/","version":"9.1.0","features":["“Adds Java Hybrid Agent implementation”","“Adds support for the addition of SQL metadata comments for Query Performance Monitoring (QPM)”","“Enhancements to correct issues related to ignores in Kotlin Coroutines.”","“Adds support for agent metadata actions”"],"bugs":["“Fix broken trace propagation with w3c headers”","“Fix multihost preference config”","“Fixed problem where suspend ignores was not being read”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements The Java Hybrid Agent: offering a \"best-of-both-worlds\" experience by combining New Relic’s deep visibility with OpenTelemetry API compatibility . This release includes comprehensive support for the OpenTelemetry Tracing, Metrics, and Logs APIs, as well as standalone library and native framework instrumentation. Key enhancements like Span Links and Events on Spans are now available, ensuring seamless interoperability in mixed-mode environments. Hybrid Agent OpenTelemetry API Support by @jasonjkeller in 2711 Enhancements to coroutine ignores by @dhilpipre in 2726 Add agent metadata action - @mvicknr in 2732 \n2745 Fixes Fix broken trace propagation with w3c headers by @jasonjkeller in 2299 Fix multihost preference config @jtduffy in 2720 Fixed problem where suspend ignores was not being read by @dhilpipre in 2663 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-910","eolDate":"2027-02-12"},{"agent":"java","date":"2026-01-14","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/9.0.0/","version":"9.0.0","features":["“Config to delete stale agent temp jars”","“Inclusion option for selectively instrumenting applications”"],"bugs":["“Fix IllegalAccessError in AWS S3 Instrumentation”","“Fix mislabeled instrumentation version for logback-class-1.5.20”","“Fix logging message for max attribute value”","“Correct Otel-style Sampler priorities”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Add config to delete stale agent temp jars on startup by @jtduffy in 2676 Add \"inclusion\" option to compliment the exclude configuration for selectively instrumenting applications @jtduffy in 2638 To use this feature, set the environment variable NEW_RELIC_STARTUP_JAVA_ARTIFACT_INCLUDES or system property newrelic.config.startup_java_artifact_includes. Specify the artifacts that should be instrumented as a comma-separated list. Fixes Resolve IllegalAccessError by moving wrapper class out of S3AsyncClient_Instrumentation by @jtduffy in 2503 Fix mislabeled instrumentation version on log events in logback-classic-1.5.20 by @jasonjkeller in 2594 Fixed logging message for max attribute value by @jeffalder in 2680 Corrected Trace Ratio sampler priorities by @jtduffy in 2583 Removals Removes deprecated jdbc-inet-* modules by @obenkenobi in 2572 Removes deprecated java.completable-future-jdk8 instrumentation by @obenkenobi in 2562 Removes aws wrap instrumentation by @obenkenobi in 2567 Removes jdbc-sybase-6 module by @obenkenobi in 2614 Removes play 2.3 instrumentation by @obenkenobi in 2568 Removes deprecated thrift-0.8 module by @obenkenobi in 2569 Removes deprecated solr 4.0 & 5.0 modules by @obenkenobi in 2570 Removes deprecated module grails-1.3 by @obenkenobi in 2573 Removes deprecated module hibernate-3.3 by @obenkenobi in 2574 Removes deprecated footer injection API by @sharvath-newrelic in 2620 Removes deprecated Struts 1 pointcuts by @obenkenobi in 2561 Removes deprecated module glassfish-3 by @sharvath-newrelic in 2575 Removes deprecated rabbit-amqp modules 2.5.0, 2.4.1, 1.7.2 by @obenkenobi in 2571 Removes deployment marker function by @jtduffy in 2589 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-900","eolDate":"2027-01-14"},{"agent":"java","date":"2024-02-08","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.9.1/","version":"8.9.1","features":[],"bugs":["Apache HttpClient 5.1+ instrumentation fixes"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Check HttpHost instance for null before dereferencing it when certain execute() methods are called 1722 Do an instanceof check in the complete() method before class cast  1719 Null check on the response object before trying to report an external call 1719 Deprecations The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679 The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 spring-3.0.0 netty-3.4 Struts v1 Update to the latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the New Relic agent directory backed up. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new agent versions. You can use diff or another diffing utility to see what's changed and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like this: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure you get the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-891","eolDate":"2025-02-08"},{"agent":"java","date":"2024-01-31","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.9.0/","version":"8.9.0","features":["“Instrumentation for Spring Webclient 5/6 captures http status code and message”","“Add status code to `grpc-1.40.0` client instrumentation”","“Add config to set the size limit of attributes on custom events”","“Add Spring instrumentation modules to support proper transaction naming”","“Add instrumentation for Vert.x 4.5.x web client and futures”","“Update Security Agent to Public Release version `1.1.0`”","“The browser header injection API now adds both the header and footer scripts”"],"bugs":["“Remove erroneous printing of stack trace in `SlowTransactionManager`”","“Convert the `ProcessPointCut` over to a weaver instrumentation module”","“Remove support for setting agent config with lower-case","dotted environment variable names”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Instrumentation for Spring Webclient 5/6 now captures http status code and http status message 1658 Add status code to grpc-1.40.0 client instrumentation  1673 Add config to set the size limit of attributes on custom events (i.e. newrelic.config.custom_insights_events.max_attribute_value). Default size is 255 characters and the max is 4095. 1683 Add Spring instrumentation modules to support proper transaction naming (route + HTTP method) of traditional annotated spring controllers as well as controllers that inherit annotations from interfaces, super classes or custom annotations. Note that because the new instrumentation can change transaction names, enabling this \"enhanced transaction naming\" is gated by the newrelic.config.class_transformer.enhanced_spring_transaction_naming agent configuration option, which is false by default. Thanks to @mgr32 for their help with validating the naming changes. 1675 Add instrumentation for Vert.x 4.5.x web client and futures 1704 Fixes Remove erroneous printing of stack trace in SlowTransactionManager 1684 Convert the ProcessPointCut over to a weaver instrumentation module to better handle cases where it is used in a multi-threaded environment. 1685 Removals Remove support for setting agent config with rarely used lower-case, dotted environment variable names (e.g. newrelic.config.labels). Customers relying on lower-case, dotted environment variables should switch to the standard upper-case, underscore names (e.g. NEW_RELIC_CONFIG_LABELS). There are no changes to documented system property behavior (via newrelic.config., server-side config, YAML, or standard environment variable (via NEW_RELIC_). 1598 Deprecations The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679 The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 spring-3.0.0 netty-3.4 Struts v1 IAST Update Security Agent to Public Release version 1.1.0 1710 Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.1.0 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-890","eolDate":"2025-01-31"},{"agent":"java","date":"2024-01-18","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.8.1/","version":"8.8.1","features":[],"bugs":["Fix NullPointerExceptions from Synthetics headers"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixed a NullPointerException when working with Synthetics headers 1690 Deprecations The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 spring-3.0.0 netty-3.4 Struts v1 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, results such as below will print to the console: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, we will no longer support older releases once they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-881","eolDate":"2025-01-18"},{"agent":"java","date":"2023-12-21","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.8.0/","version":"8.8.0","features":["“Add support for Jetty 12”","“Add support for Vert.x versions 4.0.0 through 4.4.x ”","“Add support for r2dbc-postgresql 0.9.2 till latest”","“Add log4j2 JsonLayout support”","“Add the httpstatus attribute in the external segment for Spring Webclient ”","“Enabled slow transaction detection by default and increased the threshold to 10 minutes ”","“Add support for string formatting with JBoss Logging”","“Add logic to remove specific classes from being excluded from being weaved if the security/CSEC agent is enabled”","“Updated IAST to 1.0.7 public preview”"],"bugs":["“Fix transaction naming in Spring controllers with a CGLIB proxy”","“Fix a `NullPointerException` caused by ServletContext in servlet instrumentation modules”","“Fix a memory leak caused by Lettuce instrumentation”","“Fix a bug where invalidating a license key causes a memory leak”","“Add a workaround for a memory leak that may occur in rare scenarios with instrumentation using the legacy async API in the Java Agent”","“Fix a `NullPointerException` caused by RPMServiceManager”"],"security":["“Prevent license_key value from being written to the agent logs when using debug and/or audit_mode logging”"],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Add support for Jetty 12, including Jetty’s implementation of the Jakarta EE 8, 9, and 10 specs. 1621 Add support for Vert.x versions 4.0.0 through 4.4.x 1588 Add instrumentation for graphql-java 21 1454 Instrument r2dbc-postgresql 0.9.2 till latest 1413 Reintroduce the legacy HTTP Attributes that were removed in v8.0.0  to support customers with alerts and dashboards that require them 1671 \nThe attributes are: httpResponseCode httpResponseMessage response.status response.statusMessage Attribute reporting is configurable via the following means. YAML: System property: Environment variable: The configuration options are: standard : The agent will send new standard attributes. This configuration is recommended but requires that any alerts or dashboards using attributes be updated to use these new attributes. This setting will reduce the amount of ingest used for attribute reporting. legacy : The agent will send the legacy attributes referenced above. Customers with alerts or dashboard requiring these attributes can continue to be used as-is.  This setting will reduce the amount of ingest used for attribute reporting. both : This is the default configuration, the agent will send BOTH legacy AND standard HTTP attributes. This configuration was intended to support customers that are unable to modify their alerts or dashboards but this configuration will increase data ingest. Add an interface for our error API. Our error API can now be called via the code NewRelic.getAgent().getErrorApi() 1577 Add log4j2 JsonLayout support and support log4j2 till latest. 1545 Add httpstatus in the external segment for Spring Webclient 1610 Enable slow transaction detection by default and bump the threshold to 10 minutes 1629 Add support for string formatting with JBoss Logging. 1650 Add logic to remove specific classes from being excluded from being weaved if the IAST security feature is enabled. 1453 The affected classes belong in the following formats: ^java/security/.* ^javax/crypto/.* These are crypto classes which can cause class circularity errors if they get too far along in the class transformer. ^net/sf/saxon.* If you wish to re-include these excluded rules, you can do so via the following means. YAML: System property: Environment variable: Prevent license_key value from being written to the agent logs when using debug and/or audit_mode logging 1653 IAST The IAST feature now also supports Async HTTP client version 2 and above 142 Added support for Sun Net HTTP Server 142 JSON version bump to 1.1.1 142 Add critical error logging via LogMessage event 142 Fixes Fix transaction naming in Spring controllers with a CGLIB proxy. Transactions now use the actual class name as opposed to the proxied class name.  1574 Fix a NullPointerException caused by ServletContext in servlet instrumentation modules. 1636 Fix a memory leak caused by Lettuce instrumentation. Duplicate code for  transaction linking has been removed from the Lettuce instrumentation and is handled by netty-reactor instead. 1608 Fix a bug where invalidating a license key causes a memory leak. Reconnection tasks are now capped in the event of a LicenseException.   1606 Fix a NullPointerException caused by RPMServiceManager 1604 Add a workaround for a memory leak that may occur in rare scenarios with instrumentation using the legacy async API in the Java Agent (which async servlets and Jetty Continuations use). 1555 You can configure the option via the following means: Agent config file (this will update dynamically if the config file is changed) System Property Environment Variable IAST DynamoDB v2 issue: missing attribute values for conditionCheck method in case of transactWriteItems operation on DynamoDB 142 Fixed an Insecure cookie attack vulnerability.  142 Never print LicenseKey 142 Deprecations The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 spring-3.0.0 netty-3.4 Struts v1 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another di…","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-880","eolDate":"2024-12-21"},{"agent":"java","date":"2023-10-26","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.7.0/","version":"8.7.0","features":["“Adds support for Java 21”","“Add experimental config option to run the agent with unsupported java versions”","“Add a new thread ID attribute to spans”","“Include stack traces in client spans”","“Add new configuration to enable/disable low priority instrumentation security.low-priority-instrumentation.enabled for the CSEC agent”","“Adds support for getting the containerId from a docker container with Linux cgroup v2”","“Add database and external span attributes to correlate to metric data in accordance with Open Telemetry specs”","“Add stall detection which can be configured. It is disabled by default.”","“Add instrumentation for r2dbc postgresql 0.9.2”","“Security agent version bump to 1.0.6 public preview”"],"bugs":["“Fixed a bug where a ClassCircularityError was thrown by Sonarqube9.9 ”","“Fix a bug where the Java agent fails to detect spring-security-oauth2-client.jar”","“Fix a bug where Spring 6/ Spring Boot3 does not report underlying exception/stacktrace when a @RestControllerAdvice class is used”","“Fix HttpUrlConnection instrumentation so segment timing is accurate”","“Fixes a bug in Spring 6 instrumentation where transactions are incorrectly named in certain scenarios”","“Add a configurable fix for JBoss EAP / Wildfly where if customers are using the J2EE/Jakarta Management API","the application fails to startup”","“Resolve missing class exception on Scala instrumentation”"],"security":["“Upgrade OkHttp to 4.12.0”","“Upgrade commons-codec to v1.13”"],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Adds support for Java 21 1546 Add experimental config option to run the agent with unsupported java versions 1480 Add intrinsic attribute thread.id to spans to allow for faceting queries by thread ID 1513 Include stack traces in client spans 1507 Adds support for getting the containerId from a docker container with Linux cgroup v2. 1529 Add database and external span attributes to correlate to metric data in accordance with Open Telemetry specs. Certain old attributes are removed. 1525 New attributes: db.system db.operation db.collection server.address server.port Removed attributes: component peer.hostname Add slow transaction detection which can be configured. It is disabled by default. 1542 \nE.g: Add instrumentation for r2dbc postgresql 0.9.2 to 0.9.x 1410 Security Agent: Add new configuration to enable/disable low priority instrumentation security.low-priority-instrumentation.enabled for the CSEC agent. Default value is false. 1515 Security Agent: Cassandra DB v3.0+ Support: The Security agent now supports Cassandra DB version 3.0 and above 122 Security Agent: HttpClient v5.0+ Support: The Security agent now also supports HttpClient version 5.0 and above 122 Security Agent: Support for std-out logging 122 Security Agent: Added feature for Daily log rollover 122 Security Agent: Support for logger config: log_file_count and log_limit_in_kbytes 122 Security Agent: Relocating all our instrumentation packages under the package com.newrelic.agent.security.instrumentation.*  122 Fixes Fixed a bug where a ClassCircularityError was thrown by Sonarqube9.9 1522 Fix a bug where the Java agent fails to detect spring-security-oauth2-client.jar 1462 Fix a bug where Spring 6/ Spring Boot3 does not report underlying exception/stacktrace when a @RestControllerAdvice class is used 1538 Fix HttpUrlConnection instrumentation so segment timing is accurate 1537 Fixes a bug in Spring 6 instrumentation where transactions are incorrectly named in certain scenarios. 1544 \nSuch include: \"built-in\" controllers that don't have @RestController-like annotations, e.g. /actuator/health (see Actuator endpoints ) custom controllers that don't use @RestController directly (e.g. using custom annotations) requests returning 401s / 404s Add a fix for JBoss EAP / Wildfly where if customers are using the J2EE/Jakarta Management API, the application fails to startup. 1549 \nThis is done by adding the system property com.newrelic.jboss.jsr77.fix and setting it to true.\nE.g. Customers using JBoss EAP 7.4+ or Wildfly 23+ will need to manually configure the io.undertow.servlet module and add\njava.management as a dependency.\nThis translates to doing the following steps: Opening the file modules/system/layers/base/io/undertow/servlet/main/module.xml Adding the XML element <module name=\"java.management\"/> inside the body of the <dependencies> tag Here is what the configured XML file may look like: Resolve missing class exception on Scala instrumentation 1528 Security Agent: Fixed ClassNotFoundException for IOStreamHelper class with Glassfish 122 Security Update agent dependency commons-codec to v1.13 1548 Update JFR daemon to 1.11.1. This upgrade updates the underlying OkHttp dependency to version 4.12.0 1561 Deprecations The following instrumentation modules will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 spring-3.0.0 netty-3.4 Struts v1 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New…","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-870","eolDate":"2024-10-26"},{"agent":"java","date":"2023-09-07","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.6.0/","version":"8.6.0","features":["Support latest Wildfly","Support JBoss EAP 7.4","Support Spring Cache","Support Spring Cache","Kafka client node metrics","Kafka client config events","Improved Struts 2 instrumentation","Improved code-level metrics for Servlets"],"bugs":["Fixed a bug in the Spring instrumentation when OpenFeign was used.","Fixed a bug where utility classes were not weaved.","Fixed a bug where the agent would not properly send its dependencies."],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Support latest Wildfly #1373 Support latest JBoss EAP #1336 Spring Cache instrumentation #1458 This new instrumentation module allows you to see how your caches are performing. It provides hit/miss metrics as well as clear and evict.\nSearch \"Metrics Explorer\" for the new metrics: Kafka client node metrics #1338 This is a new instrumentation for Kafka clients. It provides metrics similar to the existing instrumentation module, but this provides them by node/topic, whereas the existing one only uses topic. This module is disabled by default, check the documentation  for more information. Kafka client config events #1338 This new instrumentation module sends the Kafka configuration as events periodically. This module is disabled by default, check the documentation  for more information. Improved Struts 2 instrumentation #1457 The Struts 2 instrumentation has been refactored to use a newer instrumentation technique, which allows it to be disabled. Improved code-level metrics for Servlets. #1394 Security Agent: Support for Apache log4j 3.0.0-alpha1. Security Agent: Support for Commons.jxpath. Security Agent: Add agent monitoring details and matrix to health check. Security Agent: Limiting the supported version range for Jetty. Fixes Fixed a bug in the Spring instrumentation when OpenFeign was used. #1197 Fixed a bug where utility classes were not weaved. #1073 Fixed a bug where the agent would not properly send its dependencies. #1340 Security Agent: Issue with HealthChecking having empty process stats issue Deprecations aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 spring-3.0.0 netty-3.4 Struts v1 (legacy pointcut instrumentation) Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-860","eolDate":"2024-09-07"},{"agent":"java","date":"2023-07-27","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.5.0/","version":"8.5.0","features":["“Kafka Connect instrumentation”","“Security agent version bump to 1.0.4 public preview”"],"bugs":["“Implement getStatus for NRWrapper in Servlet v5 and v6 instrumentation”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Note:  This release note has been corrected to remove Struts 2 from the list of deprecations. New features and improvements Kafka Connect instrumentation: Adds metrics  and transaction tracing  for version 2.0.0+ #1324 Kafka: Added metrics to understand the relationship between consumers, producers, topics and nodes #1223 IAST: Limiting the supported version range for Apache log4j due to the new version release of Apache log4j on 21 June 2023 #80 IAST: Support for indication what all API-IDs are scanned or being scanned #80 All existing instrumnetation now supports Jakarta 10 EE Fixes Implement the getStatus() method in the NRWrapper class for version 5 and 6 of Servlet instrumentation #1315 Deprecations aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 spring-3.0.0 netty-3.4 Struts 1 (legacy pointcut instrumentation) Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-850","eolDate":"2024-07-27"},{"agent":"java","date":"2023-06-15","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.4.0/","version":"8.4.0","features":["Added a public preview of the Interactive Application Security Testing (IAST) mode of the New Relic Security agent"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Added a public preview of the Interactive Application Security Testing  (IAST) mode of the New Relic Security agent . The New Relic Security agent IAST mode is in public preview and should only be used in non-production environments. To learn about how to use IAST, check out our documentation . By default, the New Relic Security agent IAST mode is completely disabled. To enable it, set both newrelic.config.security.agent.enabled=true and newrelic.config.security.enabled=true. Full configuration options are detailed below (note that the security section should be indented two spaces under the pre-existing common section in the newrelic.yml config file): Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-840","eolDate":"2024-06-15"},{"agent":"java","date":"2023-06-01","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.3.0/","version":"8.3.0","features":["On-the-fly Class Retransformation","Enhanced Logging for Cats Effect 2","Batched Payload and Compression for Infinite Tracing","HttpClient v5.0+ Support","High-security mode disables user tracking","Updated JFR Version","Selective RollingFileAppender Usage"],"bugs":["Fixed Cats Effect 2 Logging"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Batch payloads and compression for Infinite Tracing: Enhanced performance by providing option to enable payload compression and batching for Infinite Tracing 1146 . HttpClient v5.0+ support: The Java agent now supports HttpClient version 5.0 and above 1252 . On-the-fly class retransformation: Classes with Trace annotation are now retransformed upon attach, enhancing instrumentation flexibility 1147 . Enhanced logging for Cats Effect 2: Log Cats Effect 2 instrumentation at finest log level 1173 . High-security mode disables user tracking\n1261 . Selective RollingFileAppender Usage: The RollingFileAppender is now only used when log_limit_in_kbytes is greater than 0, improving logging efficiency 1228 . Fixes Fixed Cats Effect 2 logging: Addressed issues with Cats Effect 2 logging for better reliability 1269 . Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-830","eolDate":"2024-06-01"},{"agent":"java","date":"2025-12-17","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.25.1/","version":"8.25.1","features":null,"bugs":["Fixes Kotlin Coroutine with CancellableContinuation"],"security":null,"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixes Kotlin Coroutine error about third party implementation of CancellableContinuation Deprecations aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 netty-3.4 Struts v1 spring-3.0.0 thrift-0.8 solr-4.0.0 solr-5.0.0 jdbc-inet-merlia jdbc-inet-oranxo grails-1.3 rabbit-amqp-1.7.2 rabbit-amqp-2.4.1 rabbit-amqp-2.5.0 rabbit-amqp-2.7.0 glassfish-3 hibernate-3.3 hibernate-3.5 jdbc-jtds Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8251","eolDate":"2026-12-17"},{"agent":"java","date":"2025-11-12","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.25.0/","version":"8.25.0","features":["Adds Java 25 Support","Adds Logback-1.5.20 Support","Introduces a config option to update Spring Controller transaction naming"],"bugs":["Error Class Naming: fixed parsing logic","Error Logging: fixed potential memory issue"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Adds Java 25 Support by @deleonenriqueta in 2512 Adds support for Logback-1.5.20 by @jtduffy in 2535 Introduces a config option to disable the execution of the call and exec SQL parser regular expressions by @jtduffy in 2490 Adds support for Kotlin Coroutines v1.4+ by @dhilpipre in 2454 Adds support for Kotlin Coroutines Suspend Functions generated outside of Kotlin Coroutines by @dhilpipre in 2456 Introduces a preference config for multiple hosts during datastore detection by @jbedell-newrelic in 2508 Adds a system property to configure the artifact skip function by @jtduffy in 2509 Adds a configuration option allowing Spring Controller transactions to be named using the controller class name and method name by @sharvath-newrelic in 2532 Implements SamplerConfig, centralizing all distributed_tracing.sampler configs into the SamplerConfig by @jasonjkeller in 2529 Updates kafka-clients-spans-0.11.0.0 producer instrumentation to use modern distributed tracing API’s with W3C Trace Context support by @sharvath-newrelic in 2516 Fixes Fixes parsing of error class names by @sharvath-newrelic in 2497 Fixes a potential memory issue caused by excessively large stack traces in error logging by @jtduffy in 2498 Clarify logging messages for invalid attributes on custom events and logging events by @sharvath-newrelic in 2501 Deprecations The following instrumentation modules are deprecated and will be removed in the next major release. aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 netty-3.4 Struts v1 spring-3.0.0 thrift-0.8 solr-4.0.0 solr-5.0.0 jdbc-inet-merlia jdbc-inet-oranxo grails-1.3 rabbit-amqp-1.7.2 rabbit-amqp-2.4.1 rabbit-amqp-2.5.0 rabbit-amqp-2.7.0 glassfish-3 hibernate-3.3 hibernate-3.5 jdbc-jtds Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8250","eolDate":"2026-11-12"},{"agent":"java","date":"2025-09-03","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.24.0/","version":"8.24.0","features":["“Support MongoDB Reactive Streams 5.2.0 and up”","“Jedis 6 support”"],"bugs":["CouchBase: Add skip class to prevent double instrumentation","Spring WebClient 5.x: Only wrap headers instead of the entire response"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Support MongoDB Reactive Streams 5.2.0 and up by @obenkenobi in 2465 Jedis 6 support by @kanderson250 in 2466 Fixes CouchBase: Add skip class to prevent double instrumentation by @jtduffy in 2462 Spring WebClient 5.x: Only wrap headers instead of the entire response by @jtduffy in 2464 Deprecations aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 netty-3.4 Struts v1 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8240","eolDate":"2026-09-03"},{"agent":"java","date":"2025-08-13","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.23.0/","version":"8.23.0","features":["“Support v24 of GraphQL”","“Add lettuce 6.5 instrumentation”","“Add lettuce dbName to datastore params where available”","“Add an environment variable to skip instrumenting certain applications”"],"bugs":["“Fix a bug where SQS messages with 8 attributes are not sent to AWS”","“Trim the ‘Subscriptions’ bit off the end of the topic name in azure service bus client”","“Fix AutoConfiguredOpenTelemetrySdk config”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Update to support v24 of graphql by @jtduffy in 2425 Add lettuce 6.5 instrumentation by @kanderson250 in 2430 Bump commons-lang version to 3.18.0 by @jtduffy in 2421 Add lettuce dbName to datastore params where available by @kanderson250 in 2423 Add an environment variable to skip implementing certain applications. The environment variable name is  NEW_RELIC_STARTUP_JAVA_ARTIFACT_SKIPS. The value of it is a comma separated list of main classes, executable jar files or Java based tools/apps that the agent should NOT instrument (e.g. NEW_RELIC_STARTUP_JAVA_ARTIFACT_SKIPS=keytool,myapp.jar,IgnoreThisClass) by @jtduffy in 2433 Fixes Fix a bug where SQS messages with 8 attributes are not sent to AWS. SQS messages need less then 8 attributes to pass distributed trace headers by @obenkenobi in 2422 Trim the \"Subscriptions\" bit off the end of the topic name in azure service bus client by @jbedell-newrelic in 2440 Fix AutoConfiguredOpenTelemetrySdk config by @jasonjkeller in 2451 Deprecations The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 netty-3.4 Struts v1 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8230","eolDate":"2026-08-13"},{"agent":"java","date":"2025-07-09","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.22.0/","version":"8.22.0","features":["“Azure ServiceBus 7.15.0”","“Linking metadata for Azure App Services”","“Connection errors”","“Verify shadowed jars”","“Log and obfuscate invalid keys added as attributes to logs and events”","“Remove MonoFlatMapMain instrumentation”"],"bugs":["“Relocate IntelliJ annotations library”","“Support server side sampling_target configuration”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Azure ServiceBus 7.15.0 instrumentation by @jbedell-newrelic in 2384 Linking metadata for Azure App services by @jbedell-newrelic in 2399 Connection errors now logged at SEVERE by @jtduffy in 2377 Log and obfuscate invalid keys added as attributes to logs and events by @jtduffy in 2388 Fixes Relocate IntelliJ annotations library by @meiao in 2383 Support server side sampling_target configuration by @jtduffy in 2386 Remove MonoFlatMapMain Instrumentation to correct potential memory leaks by @deleonenriqueta in 2400 Deprecations The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 netty-3.4 Struts v1 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8220","eolDate":"2026-07-09"},{"agent":"java","date":"2025-05-29","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.21.0/","version":"8.21.0","features":["“Enhances visibility into Reactor flatMap calls”","”Adds new instrumentation for Spring-Kafka”","“Adds kafka-clients-spans-consumer instrumentation with distributed tracing support“","“Adds KafkaConsumerConfig event support for Kafka 3.7+”"],"bugs":["“Fixes the distributed_tracing.sampler config”","“Fixes an Illegal Access Error that can occur when using Scala 2.12 and JDK 11”","“Fixes the netty.http2.frame_read_listener.start_transaction configuration”","“Adds a restriction on when to add distributed trace headers for SQS messages”","“Allows the org.crac JAR to be shadowed”","“Backports NullPointerException fix to older versions of vertx-core instrumentation”","“Prevents excessive transaction segments from being created by HttpUrlConnection method calls”"],"security":["“Upgrades the com.newrelic.agent.java:infinite-tracing-protobuf for better security with infinite tracing”","“Replaces snakeyaml with com.konloch:safeyaml to address a security vulnerability”"],"supportedOperatingSystems":null,"description":"Known issues : This release has a known issue with certain uses of Netty Reactor that can cause memory leaks.\nPlease consider using another version. Download this agent version New features and improvements Enhances visibility into Reactor Mono.flatMap calls 2308 Adds new instrumentation for Spring-Kafka and distributed tracing when using the core Kafka client library 2312 Adds KafkaConsumerConfig event support for Kafka 3.7+ 2358 Fixes Fixes the distributed_tracing.sampler config 2330 Fixes an Illegal Access Error that can occur when using Scala 2.12 and JDK 11. In cases where Scala 2.12 is not detectable by the agent (we check the system classloader for this - notably, sbt will load Scala classes into custom Scala loaders), there is also a feature flag to manually enable the fix via system property -Dnewrelic.config.class_transformer.illegal_access_fix=true 2334 Fix netty 'Unknown' transactions 2274  2355 This fix moves previous netty instrumentation changes behind a feature flag, which provides additional visibility in some cases involving HTTP2 transactions. To reenable this granularity (at the possible cost of seeing ‘Unknown’ transactions), use the config setting: 8.20 has a logic error in the agent config so the fix is only official in agent version 8.21 and up. Adds a restriction on when to add distributed trace headers for SQS messages. This is based on how large the contents of a message is in bytes and the and the size of attributes. Messages with size greater than 251 KB and/or with 9 or more attributes are excluded from getting distributed trace headers added 2353 Allows the org.crac JAR to be shadowed to prevent conflicts with customer environments. 2344 Backports changes made in PR #1927 to prevent NullPointerExceptions to older versions of the vertx-core instrumentation 2327 Prevents excessive transaction segments from being created by HttpUrlConnection method calls (e.g. getInputStream) when they are not associated with an external call. This behavior can be controlled by the following config options: NEW_RELIC_CLASS_TRANSFORMER_COM_NEWRELIC_INSTRUMENTATION_HTTPURLCONNECTION_VERBOSE=false, sys prop -Dnewrelic.config.class_transformer.com.newrelic.instrumentation.httpurlconnection.verbose=false, or equivalent stanza in newrelic.yml. Default setting is true (i.e. non-external getInputStream and other response handler methods will be reported as before). 2365 Security Upgrades the com.newrelic.agent.java:infinite-tracing-protobuf for better security with infinite tracing 2339 Replaces snakeyaml with com.konloch:safeyaml to address a security vulnerability 2333 Deprecations The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 netty-3.4 Struts v1 IAST CSEC Version Update to 1.7.0 2348 \nChangelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.7.0 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8210","eolDate":"2026-05-29"},{"agent":"java","date":"2025-04-15","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.20.0/","version":"8.20.0","features":["“Support for CRaC”","“Support for JDK24”","“Add sampling options when an inbound traceparent exists”","“Support for Undertow”","“Support for Couchbase Client”"],"bugs":["“Fix netty Unknown transactions”","“Refactor AWS docker id fetch to use 5s timeout”","“Option to apply Kotlin fix to all methods”","“Prevent cache lock for long DB statement parsing”","“Add config for java.sql classloader”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Support for CRaC 2250 Support for JDK24 2284 Added sampling options when an inbound traceparent exists 2279 These options define how the agent should handle sampling of spans, depending on sampling decisions that were made for their parent span by an upstream entity. The configuration options remote_parent_sampled and remote_parent_not_sampled specify what to do in the case the parent span was sampled or not sampled, respectively. See the documentation  for full configuration details. Support for Undertow as a stand-alone module 2269 This instrumentation is disabled by default to avoid conflicts with existing Wildfly instrumentation. To enable this instrumentation for stand-alone Undertow server apps, use the configuration setting: Support for Couchbase Client 2203 If the Couchbase Client Experimental Module  is currently in use, remove it from your extensions directory before upgrading to this version of the Java Agent. Fixes ~Fix netty 'Unknown' transactions 2274 ~ ~This fix moves previous netty instrumentation changes behind a feature flag, which provides additional visibility in some cases involving HTTP2 transactions. To reenable this granularity (at the possible cost of seeing ‘Unknown’ transactions), use the config setting~: Refactor AWS docker id fetch to use 5s timeout 2275 Feature flag to apply Kotlin ArrayIndexOutOfBoundsException fix to all methods 2307 This fix addresses errors that may be seen when running the Java Agent in an environment where Kotlin suspends functions are used. To use this fix, set the system property -Dnewrelic.config.class_transformer.clear_return_stacks=true Prevent cache lock for long DB statement parsing 2294 Add config to specify whether java.sql is loaded by platform classloader 2267 Deprecations The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 netty-3.4 Struts v1 Known issues : This release has a known issue with Netty where 'Unknown' transactions persist, please update to a later version. Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8200","eolDate":"2026-04-15"},{"agent":"java","date":"2023-05-03","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.2.0","version":"8.2.0","features":["Added support for Java 20"],"bugs":["Prevented a NullPointerException from the lettuce instrumentation","Fix failure with browser agent auto injection for tomcat versions 8.5.87+ and 9.0.74+"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Added support for Java 20 1226 Fixes Prevented a NullPointerException from the lettuce instrumentation 1204 Fix failure with browser agent auto injection for tomcat versions 8.5.87+ and 9.0.74+ 1225 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-820","eolDate":"2024-05-03"},{"agent":"java","date":"2025-03-11","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.19.0/","version":"8.19.0","features":["“Support Adding Labels to APM Forwarded Logs”","“Add support for server-side application logging configs”","“Add response attributes for http4s server modules”"],"bugs":["“invokeSuspend edge case fix”","“Rename and reenable aws sqs modules”","“Update JFR service to run as a daemon”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements 2238  Support Adding Labels to APM Forwarded Logs by @deleonenriqueta 2246  Update Config File to Include APM Forwarded Log Labels Options by @deleonenriqueta 2243  Add response attributes for http4s server modules by @kanderson250 2230  Default proxy_scheme setting to \"http\" by @jtduffy 2259  Add support for server-side application logging configs by @obenkenobi Fixes 2228  invokeSuspend edge case fix by @kanderson250 2258  Rename and reenable aws sqs modules by @kanderson250 2245  Update JFR service to run as a daemon by @kanderson250 IAST CSEC Version bump to 1.6.1 2252 Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.6.1 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8190","eolDate":"2026-03-11"},{"agent":"java","date":"2025-01-30","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.18.0/","version":"8.18.0","features":["“Added scala3 source detection “",{"“Vertx":"decreased the amount of tokens created”"},{"“kafka-clients-metrics":"Refactor node topic metrics”"},"“New instrumentation module for Struts2 v6.7.0”","“New instrumentation module for Kafka 3.9”",{"“All AWS instrumentation modules":"do not hide http request”"},"“Added support for distributed tracing in AWS SQS”","“Added relationship metric support for Kafka clients node metrics”"],"bugs":["“Fix edge case in JsonTemplateLayout with certain escaped sequences”","“Correct Apdex on transaction event if an error is present”","“Don't add null port to hostname attribute on JFR events”","“Fix memory issue with httpclient-5.0 instrumentation”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements 2172  Add scala3 source detection by @kanderson250 2185  Vertx: decrease amount of tokens created by @meiao 2199  Instrumentation module for Struts2 v6.7.0 by @jtduffy 2203  Kafka 3.9 support by @meiao 2204  Sqs distributed trace by @obenkenobi 2202  Kafka clients node metrics by @meiao Fixes 2187  Fix edge case in JsonTemplateLayout with certain escaped sequences by @jtduffy 2191  Correct Apdex on transaction event if an error is present by @jtduffy 2192  Don't add null port to hostname attribute on JFR events by @jasonjkeller 2197  Fix memory issue with httpclient-5.0 instrumentation by @jasonjkeller Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8180","eolDate":"2026-01-30"},{"agent":"java","date":"2024-12-19","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.17.0/","version":"8.17.0","features":["“Add support for jdbc-mariadb 3.0.0 till latest and r2dbc-mariadb 1.1.2 till latest ”","“Auto discover AWS account ID in the DynamoDB and Lambda SDKs”","“Support pekko-http on scala 3 for versions 1.0.0 till latest”","“Allow JFR queue size and harvest interval to be configured via agent config”","“Add AWS Firehose SDK Instrumentation”","“”","“Implement a new instrumentation module for r2dbc-mysql 1.1.3+”","“Memory usage reduced for the r2dbc-mssql and m2dbc-mysql modules”"],"bugs":["“Resolved a potential token timeout issue with the reactor-3.3.0 module”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Add support for jdbc-mariadb 3.0.0 till latest and r2dbc-mariadb 1.1.2 till latest - credit to @dhilpipre - clone of 2142 by @jtduffy in 2146 Auto discover AWS account ID in the DynamoDB instrumentation by @meiao in 2148 Auto discover AWS account ID in the Lambda sdk instrumentation by @meiao in 2167 Support pekko-http on scala 3 for versions 1.0.0 till latest by @kanderson250 in 2163 Allow JFR queue size and harvest interval to be configured via agent config by @jtduffy in 2168 \nNew configs are: Add AWS Firehose SDK Instrumentation for versions 2.1.0 till latest by @obenkenobi in 2149 Implement a new instrumentation module for r2dbc-mysql 1.1.3+ by @jbedell-newrelic in 2169 Memory usage reduced for the r2dbc-mssql and m2dbc-mysql modules by @jbedell-newrelic in 2169 Log when multiple, different, traceparent headers found on inbound request and only report invalid parent header count supportability metric when that scenario occurs by @jtduffy in 2154 Expected NPE in noticeTracer no longer logs full stack trace by @jasonjkeller in 2143 Fixes Resolved a potential token timeout issue with the reactor-3.3.0 module by @jbedell-newrelic in 2169 IAST CSEC version bump to 1.6.0 2173 Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.6.0 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8170","eolDate":"2025-12-19"},{"agent":"java","date":"2024-11-14","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.16.0/","version":"8.16.0","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Obfuscate JVM properties 2114 \nThe Java agent will now obfuscate values passed to JVM properties. For example: -Dprop=12345 will now be sent as -Dprop=obfuscated. The documentation  has information on how to disable obfuscation and how to add exceptions. Cloud API 2081 \nThe Cloud API allows cloud provider account information to be provided to the agent. This will allow the agent to populate the cloud.resource_id attribute in calls to select cloud services.\nThe API documentation  has information on how to use it programmatically.\nThis information can also be provided using a configuration option . Support distributed tracing for Kafka Stream 3.7.x 2095 Report if agent was installed via Azure site extension 2094 Lazy initialization of GUIDs on DefaultTracers 2088 Java HttpClient:  Addition of status code to reported externals 2089 AWS Lambda: populate cloud.resource_id using data from Cloud API 2115 Kinesis Data Streams: populate cloud.resource_id 2112 DynamoDB: populate cloud.resource_id 2113 Fixes Use recordResponseTimeMetric instead of recordMetric 2128 Use WeakReference HttpUrlConnection instrumentation 2082 Fix a bug where Jetty 12 would not properly link distributed traces 2140 Update to JFR daemon 1.13.0 2129 \nThis update changes the HTTP client used, which caused problems with some proxies. IAST CSEC version bump to 1.5.1 2076 Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.5.1 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8160","eolDate":"2025-11-14"},{"agent":"java","date":"2024-10-01","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.15.0/","version":"8.15.0","features":["AWS Lambda SDK instrumentation","Flyway migration events","AWS Kinesis SDK","Kafka Client Node metrics","Glassfish JUL logging","Java 23","ECS Fargate docker id","Actuator endpoint transaction naming"],"bugs":["Slick 3.5.0 PrioritizedRunnable","Netty HTTP/2 Http2Headers null pointer exception"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Addition of AWS Lambda SDK instrumentation 1998 Reporting of Flyway migration events 2021 Add support for using an environment variable for config file location 2022 Support AWS Kinesis V1 and V2 SDKs 2031 Addition of kafka-clients-node-metrics-3.7.0 Instrumentation module 2039 Add instrumentation for glassfish-jul-extension logging library 2049 Java 23 support 2055 Support reporting of ECS Fargate Docker ids 2050 Actuator endpoint transaction naming for Spring Boot 3 2077 Fixes Slick 3.5.0 instrumentation bug fix 2025 Protect against Http2Headers methods throwing exceptions in Netty instrumentation 2042 Fix an issue where the Kinesis instrumentation is generating ERROR logs due to a NullPointerException 2052 IAST CSEC version bump to 1.5 2076 Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.5.0 Full Changelog : https://github.com/newrelic/newrelic-java-agent/compare/v8.14.0...v8.15.0 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8150","eolDate":"2025-10-01"},{"agent":"java","date":"2024-08-21","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.14.0/","version":"8.14.0","features":["“Java agent supports disabling AI Monitoring at the account/organization level”","”HikariCP instrumentation now captures additional metrics”","”Adds new instrumentation module for kafka-clients-metrics-3.7.0”","”Adds new instrumentation module for jedis-5.0.0”","”Adds new instrumentation module for vertx-sqlclient-4.4.2”","”The newrelic-scala-api for Scala 3 will now be published to Maven”","”New AWS MQ attributes will be added to spans”","”Clarify Javadoc comments for @Trace API”"],"bugs":["“Fixes a netty-reactor issue that was causing high memory usage”","”Netty instrumentation will start transactions for HTTP/2 requests”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements The Java agent supports disabling AI Monitoring at the account/organization level 1972 HikariCP instrumentation now captures additional metrics 1976 Adds new instrumentation module for kafka-clients-metrics-3.7.0 2001 Adds new instrumentation module for jedis-5.0.0 1969 Adds new instrumentation module for vertx-sqlclient-4.4.2 2004 The newrelic-scala-api for Scala 3 will now be published to Maven 1995 New AWS MQ attributes will be added to spans 1977 Clarify Javadoc comments for @Trace API 2009 Fixes Fixes a netty-reactor issue that was causing high memory usage 1978 Netty instrumentation will start transactions for HTTP/2 requests 1994 Deprecations The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 spring-3.0.0 netty-3.4 Struts v1 IAST CSEC Version bump to 1.4.1 2010 Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.4.1 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8140","eolDate":"2025-08-21"},{"agent":"java","date":"2024-07-11","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.13.0/","version":"8.13.0","features":["“Add linking attributes to SQS spans”","“Add support for Graphql 22”","“Add support for JSP v4”","“Add support for HikariCP 2.4.0”","“Enhance CompletableFuture instrumentation for JDK11+”","“Enable RUM script injection via JSP v3 Tag library”","“Fetch the docker container ID for ECS Fargate instances”"],"bugs":["“Fix R2dbc postgresql 0.9.2 memory leak”","“Start vertx-web transactions for HTTP/2 requests”","“Update JFR Instance Naming”","“Close instrumentation gap for akka-http 10.2.0+”","“Start transactions in the Jetty12 core server”","“Clean up tracers after exceptions to prevent memory leaks”","“Add security-related class excludes during class transformer creation”","“Add null checks to vertx 4.5.1 instrumentation ”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Add attributes to AWS SQS spans that allow linking to SQS entities 1954 Add support for Graphql 22.0+ 1912 Add support for JSP v4 1951 Add instrumentation for HikariCP 2.4.0 to replace existing extension module.1964 Note: If the New Relic HikariCP incubator module  is currently in use, delete it from the new relic jar’s extension folder before upgrading to this version of the Java Agent. Enhance CompletableFuture instrumentation for JDK11+ 1908 Enable RUM script injection via JSP v3 Tag library 1943 Fetch the docker container ID for ECS Fargate instances 1952 Fixes Fix R2dbc postgresql 0.9.2 instrumentation to prevent memory leaks  1916 Update vertx-web instrumentation to start transactions for HTTP/2 requests 1959 Update JFR Instance Naming to display correct number of JVMs  1928 Close instrumentation gap for akka-http 10.2.0+ 1955 Start transactions in the Jetty12 core server 1950 Clean up dtTracers and externalTracers after exceptions to prevent memory leaks 1902 Add security-related class excludes during normal class transformer creation 1918 Add null checks to vertx 4.5.1 instrumentation 1927 IAST CSEC Version bump to 1.4.0 1956 Changelog Deprecations The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679 The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 spring-3.0.0 netty-3.4 Struts v1 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8130","eolDate":"2025-07-11"},{"agent":"java","date":"2024-05-23","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.12.0/","version":"8.12.0","features":["“Add Support for Java 22”","“Add AI Monitoring Support or Java v2 Bedrock Runtime Client versions 2.20.157 and above”","“Add support for Pekko Http”","“Enhance log forwarding to include ‘caused by’ section”"],"bugs":["“Resolve various thread hopping issues with Spring Reactor call chains”","“Refactor the daily logfile rolling job to support all platforms”","“Fix Ning memory leak”"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Add support for Java 22 1819 Add AI Monitoring support for AWS SDK for Java v2 Bedrock Runtime Client versions 2.20.157 and above 1837 Enhance log forwarding to include caused by  section 1857 Add support for Pekko Http 1850 Add local decorating for Log4j 2 users utilizing JsonTemplateLayout 1866 Performance improvements on SQL checks 1887 Fixes Resolve various thread hopping issues with Spring Reactor call chains 1883 Refactor the daily logfile rolling job to support all platforms 1888 Fix Ning memory leak 1903 IAST Update Security Agent to Public Release version 1.3.0 1896 Changes/Fixes Deprecations The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679 The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 spring-3.0.0 netty-3.4 Struts v1 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8120","eolDate":"2025-05-23"},{"agent":"java","date":"2024-04-25","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.11.1/","version":"8.11.1","features":["“Update Security Agent to Public Release version `1.2.1`”"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Features Update Security Agent to Public Release version 1.2.1 Deprecations The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679 The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 spring-3.0.0 netty-3.4 Struts v1 IAST Update Security Agent to Public Release version 1.2.1 1870 Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.2.1 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8111","eolDate":"2025-04-25"},{"agent":"java","date":"2024-04-11","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.11.0/","version":"8.11.0","features":["Add HTTP/2 Support For Netty 4.1.16.Final +","Support external calls inside Spring Reactor call chains","Support for Apache Pekko. (Support for Pekko HTTP coming soon)","Add configuration to allow the OTel SDK integration to be completely disabled","Treat OpenTelemetry @WithSpan annotation as @Trace in the Java Agent API","IAST: Json Version bump to 1.2.0"],"bugs":["Fix high CPU usage with HttpURLConnection","Prevent duplicate HTTP external calls when using the DynamoDB SDK","IAST: Fix issue related to the instrumentation of the Rhino JavaScript Engine that occurred while reading the script"],"security":["IAST: Replay header decryption due to Security Findings"],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Add HTTP/2 support for Netty 4.1.16.Final + 1815 Support external calls inside Spring Reactor call chains 1828 Support for Apache Pekko (i.e. the pekko-actor library). Support for Pekko HTTP coming soon.  1811 Add configuration to allow the OTel SDK integration to be completely disabled 1821 Configuration via yaml: Configuration via system property: Treat OpenTelemetry @WithSpan  annotation as @Trace  in the Java Agent API  1841 Fixes Fix high CPU usage with HttpURLConnection by reverting InboundWrapper changes introduced in 8.10.0 1840 Prevent duplicate HTTP external calls when using the DynamoDB SDK 1827 Deprecations The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679 The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 spring-3.0.0 netty-3.4 Struts v1 IAST Changes Json Version bump to 1.2.0 207 IAST replay header decryption due to Security Findings 207 Fixes Fix issue related to the instrumentation of the Rhino JavaScript Engine that occurred while reading the script 211 Changelog: v8.10.0...v8.11.0 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8110","eolDate":"2025-04-11"},{"agent":"java","date":"2024-03-28","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.10.0/","version":"8.10.0","features":["Support for Spring Webflux 6.1.x","Support for Spring Batch v4.0+","Scala 3 API","Zio 1 instrumentation improvements","Support for Zio 2","Enhanced clustered Solr JMX metrics","Add transaction GUID to Errors"],"bugs":["Prevent NullPointerException when setting the user id outside of a transaction","Disallow Real Time Profiling when High Security Mode is enabled","Prevent ClassCircularityErrors in some specific circumstances","Properly removing files when log_daily is enabled","Decreased memory held by the agent when HTTP calls are made","Prevent duplicate DT headers for gRPC","Properly updating how many log messages are sent after configuration change","Prevent exceptions when reading lambda bytecode","Reduce interval for JDBC caches"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version This version of the agent introduced a bug that can cause significant CPU and memory usage increases and potential deadlocks if your application uses HttpUrlConnection or any libraries that use it under the hood. Agent version 8.11.0 fixes this problem. Alternatively, disabling the HttpUrlConnection instrumentation would prevent the issue. For example, -Dnewrelic.config.class_transformer.com.newrelic.instrumentation.httpurlconnection.enabled=false. Disabling this instrumentation will have the effect that the client's external calls will not be recorded. We strongly recommend that you use the latest agent versions. They include all the latest code fixes and provide access to the latest platform features. New features and improvements Support for Spring Webflux 6.1.x 1761 Support for Spring Batch v4.0+ 1792 Scala 3 API 1772 ZIO 1 instrumentation improvements 1739 Support for ZIO 2 1778 Enhanced clustered Solr JMX metrics 1812 Add transaction GUID to Errors 1813 Fixes Prevent NullPointerException when setting the user id outside of a transaction 1762 Disallow Real Time Profiling when High Security Mode is enabled 1764 Prevent ClassCircularityErrors in some specific circumstances 1763 Properly removing files when log_daily is enabled 1754 Decreased memory held by the agent when HTTP calls are made 1775 Prevent duplicate DT headers for gRPC 1783 Properly updating how many log messages are sent after configuration change 1784 Prevent exceptions when reading lambda bytecode 1794 Reduce interval for JDBC caches 1809 Deprecations The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679 The following instrumentation modules are deprecated and will be removed in the next major release: aws-wrap-0.7.0 java.completable-future-jdk8 play-2.3 spring-3.0.0 netty-3.4 Struts v1 IAST Changes Ning Async HTTP client Support: The security agent now also supports com.ning:async-http-client 1.0.0 and higher 152 , 118 , 116 Jersey Support: The security agent now also supports Jersey 2.0 and higher 150 , 149 Mule Support: The security agent now also supports Mule server version 3.6 to 3.9.x 144 , 143 Jetty v12 Support: The security agent now also support Jetty version 12 and higher 106 Lettuce Support: The security agent now also supports Lettuce 4.4.0.Final and higher 125 Fixes Extract Server Configuration to resolve IAST localhost connection with application for Wildfly server 192 Trustboundary events now will have list of string as parameter schema Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent . Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-8100","eolDate":"2025-03-28"},{"agent":"java","date":"2023-04-13","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.1.0/","version":"8.1.0","features":["Added support for Webflux 6","Added support for Spring JMS 6","Added support for Mongodb Reactive Streams","Added support for Kafka Streams","Error fingerprint - supply your own errors inbox group names","User tracking","Invoking `token.link()` outside a transaction will instrument that method to start an async transaction","The Kafka clients instrumentation has new metrics to list the nodes: `MessageBroker/Kafka/Nodes/...`"],"bugs":["Fix ClassCircularityError when agent attaches","Fix NullPointerException thrown when calling `addCustomAttributes`","Make sure `TokenAndRefCount.token` is never null","Using a time based cache to store database connection data to prevent a memory leak when instrumenting MySQL client with replication","Decreased the number of threads used in the HttpUrlConnection instrumentation","Fix an issue when HttpUrlConnection is used with the legacy cross application tracing","Performance improvement in Netty’s RequestWrapper","Gracefully shutdown the agent if it encounters issues on startup","Fix WeavedMethod and InstrumentedMethod annotations when applied to constructors.","Performance improvements when using Tomcat","Fixed a bug that caused the agent to not report some exceptions","Updated DockerData to increase the number of container IDs detected","Reduce the number of threads used in Kafka clients instrumentation"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Added support for Webflux 6 1181 Added support for Spring JMS 6 1088 Added support for Mongodb Reactive Streams 1164 Added support for Kafka Streams 1170 Support for Kafka Streams comes in two flavors, metrics and spans. Metrics are enabled by default, while spans are disabled by default. To enable spans add the following to your newrelic.yml  configuration under the common section: Error fingerprint - supply your own errors inbox group names 1195 Are your error occurrences grouped poorly? Set your own error fingerprint via a callback function. A new public API method has been added that will accept a user defined proc. The proc will be invoked for each noticed error and whenever it returns a string, that string will be used as the error group name for the error and will take precedence over any server-side grouping that takes place with the New Relic errors inbox. This gives users much greater control over the grouping of their errors. For more information check our API: Error Grouping  and APM: Group errors tab  pages. User tracking - associate errors with a user id 1188 You can now see the number of users impacted by an error group. Identify the end user with a new public API method that will accept a string representation of a user id and associate that user id with the current transaction. Transactions and errors will then have a new enduser.id agent attribute associated with them. This will allow agent users to tag transactions and errors as belonging to given user ids in support of greater filtering and alerting capabilities. For more information check the [Newrelic.setUserId ](https://newrelic.github.io/java-agent-api/javadoc/com/newrelic/api/agent/NewRelic.html#setUserName(java.lang.String)  documentation and the Track users impacted with errors inbox  page. Invoking token.link() outside a transaction will instrument that method to start an async transaction 1140 The Kafka clients instrumentation has new metrics to list the nodes: MessageBroker/Kafka/Nodes/&lt;node> 1130 Fixes Fix ClassCircularityError when agent attaches 1137 Fix NullPointerException thrown when calling addCustomAttributes 1115 Make sure TokenAndRefCount.token is never null 1149 Using a time based cache to store database connection data to prevent a memory leak when instrumenting MySQL client with replication 1114 Decreased the number of threads used in the HttpUrlConnection instrumentation 1145 Fix an issue when HttpUrlConnection is used with the legacy cross application tracing 1142 Performance improvement in Netty’s RequestWrapper 1163 Gracefully shutdown the agent if it encounters issues on startup 1136 Fix WeavedMethod and InstrumentedMethod annotations when applied to constructors.  1153 Performance improvements when using Tomcat 1131 Fixed a bug that caused the agent to not report some exceptions 1176 Updated DockerData to increase the number of container IDs detected 1178 Reduce the number of threads used in Kafka clients instrumentation 1056 Grammar changes [1175](https://github.com/newrelic/newrelic-java-agent/pull/1175  and [1190]https://github.com/newrelic/newrelic-java-agent/pull/1190 ) Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-810","eolDate":"2024-04-13"},{"agent":"java","date":"2023-02-23","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.0.1/","version":"8.0.1","features":[],"bugs":["Fixes for the HttpUrlConnection instrumentation","Ensure that TokenAndRefCount.token is never null","Fix NullPointerException being thrown when calling addCustomAttributes","Fix ClassCircularityError when agent attaches"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date . New features and improvements Fixes Various fixes to the HttpUrlConnection instrumentation. See the README  for full details 1145 . Ensure that TokenAndRefCount.token is never null 1148 . Correct a possible NullPointerException being thrown when calling addCustomAttributes 1141 . Fix ClassCircularityError when agent attaches 1139 . Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-801","eolDate":"2024-02-23"},{"agent":"java","date":"2023-01-26","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/8.0.0/","version":"8.0.0","features":["Added support for Slick 3.4.0 on Scala 2.13","Added support for Embedded Tomcat JMX","Updated the Java agent's snakeyaml dependency to 1.33","Added tracer debug logging","Improved logging when using the recordCustomEvent API now includes event type, key and value","Added Log4j1 instrumentation to support auto log forwarding","Added JBoss Logging instrumentation to support auto log forwarding","Real-time profiling using JFR metrics can now be dynamically enabled/disabled via agent configuration","Removed instrumentation: cassandra-datastax-2.1.2, httpclient-3.0, jdbc-embedded-derby-10.2.1.6, jdbc-embedded-derby-10.10.1.1, jetty-7, jetty-7.6, jetty-9, jetty-9.0.4, jetty-9.1, mongodb-2.12, mongodb-2.14, mongodb-3.0, okhttp-3.0.0, okhttp-3.4.0, okhttp-3.5.0","The previously deprecated httpResponseCode, response.status, and response.statusMessage transaction/span attributes were removed. These have been replaced by http.statusCode and http.statusText."],"bugs":["NOTICE: HttpURLConnection instrumentation is broken in the 8.0.0 release, use Java agent 8.0.1 or higher instead","Removed leading slash in JCache metric names","Fixed a bug that was preventing Log4j2 metrics from getting disabled properly","Added a missing delimiter in POSTGRES_DIALECT_PATTERN","Fixed a ClassCastException in GraphQL 16/17","Refactored grpc-1.40.0 instrumentation to ensure that tokens were properly being linked across threads","Fixed a bug that was causing transactions to fail to link when the Spring Webclient would timeout and emit a ReadTimeoutException"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version This release includes a change to the HttpURLConnection instrumentation that creates a TimerTask to help ensure complete externals reporting. Under some circumstances this may result in a large number of threads being created, which may exhaust the maximum allocated to the JVM, causing it to stop. This issue has been fixed in the 8.0.1 release  and it's highly recommended that you update to this version of the Java agent. New features and improvements Added support for Slick 3.4.0 on Scala 2.13 Added support for Embedded Tomcat JMX Updated the Java agent's snakeyaml dependency to 1.33 Added tracer debug logging, which will appear when -Dnewrelic.config.log_level=finest\nand -Dnewrelic.debug=true are set Improved logging when using the recordCustomEvent API now includes event type, key and value Added Log4j1 instrumentation to support auto log forwarding Added JBoss Logging instrumentation to support auto log forwarding Real-time profiling for Java using JFR metrics  can now be dynamically enabled/disabled via agent configuration Fixes Removed leading slash in JCache metric names Fixed a bug that was preventing Log4j2 metrics from getting disabled properly Added a missing delimiter in POSTGRES_DIALECT_PATTERN Fixed a ClassCastException in GraphQL 16/17 Refactored HttpURLConnection instrumentation to fix several bugs that were affecting external calls and distributed traces Refactored grpc-1.40.0 instrumentation to ensure that tokens were properly being linked across threads Fixed a bug that was causing transactions to fail to link when the Spring Webclient would timeout and emit a ReadTimeoutException Removals The following previously deprecated instrumentation modules were removed: cassandra-datastax-2.1.2 httpclient-3.0 jdbc-embedded-derby-10.2.1.6 jdbc-embedded-derby-10.10.1.1 jetty-7 jetty-7.6 jetty-9 jetty-9.0.4 jetty-9.1 mongodb-2.12 mongodb-2.14 mongodb-3.0 okhttp-3.0.0 okhttp-3.4.0 okhttp-3.5.0 The previously deprecated httpResponseCode, response.status, and response.statusMessage transaction/span attributes were removed. These have been replaced by http.statusCode and http.statusText. If you've any custom dashboards or alerts that query the httpResponseCode, response.status, and response.statusMessage attributes then they will need to be updated to instead use http.statusCode and http.statusText. Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-800","eolDate":"2024-01-26"},{"agent":"java","date":"2022-07-28","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.9.0/","version":"7.9.0","features":["Jakarta EE 8 compatibility","Jetty 10 instrumentation","Add support to pass a boolean environment variable NEWRELIC_DEBUG where setting it to true activates the debug configuration","Improved performance by internally replacing regex replace with iterative char replace"],"bugs":["Update the httpurlconnection instrumentation to use newer distributed tracing APIs so that spans are correctly marked as external calls in distributed traces","Illegal Access Exception is no longer thrown from apps using NR agent with scala 2.12 and Java 11"],"security":["Update to jfr-daemon 1.9.0 to address CVE-2020-29582"],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Where applicable, existing instrumentation has been tested and verified as compatible with Jakarta EE 8. 900 Add new instrumentation to support Jetty 10. 936 Update to jfr-daemon 1.9.0 to address CVE-2020-29582 and improve CPU overhead. 937 Add support to pass a boolean environment variable NEWRELIC_DEBUG where setting it to true activates the debug configuration. 890 Improved performance by internally replacing regex replace with iterative char replace (thanks to @zowens for this contribution) 933 Fixes Update the httpurlconnection instrumentation to use newer distributed tracing APIs so that spans are correctly marked as external calls in distributed traces and contain the expected http.* attributes. 885 Illegal Access Exception is no longer thrown from apps using NR agent with scala 2.12 and Java 11. 876 Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life . Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.7.0 and 7.8.0, the results printed to the console will be: In this example, these lines were added to the default newrelic.yml in Java agent version 7.8.0. If you are moving to 7.8.0 or higher, you should add these new lines to your original newrelic.yml.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-790","eolDate":"2024-07-28"},{"agent":"java","date":"2022-06-16","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.8.0/","version":"7.8.0","features":["Update to Caffeine 2.9.3","Refactored the log.level attribute name on LogEvents to instead be level","Kafka instrumentation supports metrics for kafka-clients versions 3.x","Update to jfr-daemon 1.8.0","Lettuce instrumentation supports lettuce-core 4.3 up to 6.x"],"bugs":["Fixed CQLParser","Removed akka-http-core bindAndHandle instrumentation to resolve scenarios where duplicated transactions could result"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Updated the agent to use caffeine 2.9.3 832 Refactored the log.level attribute name on LogEvents to instead be level 858 Kafka instrumentation - supports metrics for kafka-clients versions 3.x. 860  and 865 Update to jfr-daemon 1.8.0 869 Lettuce instrumentation - supports lettuce-core 4.3 up to 6.x.  Please remove any other (experimental/incubating) lettuce extensions or else Redis database metrics could be doubled. 872 Fixes Fixed CQLParser getOperationAndTableName exception handling. Exceptions are now handled within the CQLParser. 857 Removed akka-http-core bindAndHandle instrumentation to resolve scenarios where duplicated transactions could result 850  (see Scala Akka HTTP core instrumentation  for more details) Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-780","eolDate":"2024-06-16"},{"agent":"java","date":"2022-05-03","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.7.0/","version":"7.7.0","features":["Support for Java 18","APM logs in context log forwarding is now enabled by default","Support for the Postgres, MySQL, Oracle & MSSQL R2DBC connectors"],"bugs":[],"security":["Patches a security issue related to an older version of jszip that is included in the Java agent API Javadoc jar"],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Supports Java 18 813 APM logs in context. Automatic application log forwarding is now enabled by default. This version of the agent will automatically send enriched application logs to New Relic. To learn more about this feature see Java: Configure logs in context , and additional configuration options are available Java agent configuration: Config file . To learn about how to toggle log ingestion on or off by account see Disable automatic logging  817 Added instrumentation support for the Postgres, MySQL, Oracle & MSSQL R2DBC connectors 810 , 816 , 829 , and 828 Fixes Patches a security issue related to an older version of jszip that is included in the Java agent API Javadoc jar 820 Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-770","eolDate":"2024-05-03"},{"agent":"java","date":"2022-04-04","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.6.0/","version":"7.6.0","features":["Added APM logs in context feature to provide log metrics, log forwarding, and log enriching","Instrumentation support for the MariaDB & H2 R2DBC connectors","Support for Jedis 4.0.0+","Support for Cassandra dataStax 4+"],"bugs":["Guard against intermittent null pointer exceptions","Support CSP nonce parameter for RUM header and footer","Fixed an issue with auto app naming and distributed tracing transactions","Increased maximum TransactionError message size"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements APM logs in context: a quick way to view logs no matter where you are in the platform Adds support for logging metrics which shows the rate of log message by severity in the Logs chart in the APM Summary  view. This is enabled by default in this release. Adds support for forwarding application logs to New Relic. This automatically sends application logs that have been enriched to power automatic logs in context. This is disabled by default in this release. This may be on by default in a future release. Adds support for enriching application logs written to disk or standard out. This can be used with another log forwarder to power logs in context if in-agent log forwarding is not desired. We recommend enabling either log forwarding or local log decorating, but not both features. This is disabled by default in this release. To learn more about APM logs in context and the configuration options, please see the documentation here . 718 Added instrumentation support for the MariaDB & H2 R2DBC connectors 799  724 Updated agent support for Jedis 4.0.0+ 698 Updated agent support for Cassandra dataStax 4+ 690 Fixes Guard against intermittent null pointer exceptions 707 Support CSP nonce parameter for RUM header and footer 591 Fixed an issue with auto app naming and distributed tracing transactions 566 Increased maximum TransactionError message size 581 The httpResponseCode, response.status and response.statusMessage transaction/span attributes are deprecated and will be removed in a future release. These have been replaced by http.statusCode and http.statusText 513 : Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-760","eolDate":"2024-04-04"},{"agent":"java","date":"2022-01-12","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.5.0/","version":"7.5.0","features":["Update HTTP response code attribute names. This will add http.statusCode and http.statusText to spans and transactions","Provide support for Datastax/Cassandra WrappedStatments","Add instrumentation for gRPC 1.40.0+","Add suppressed exceptions to ThrowableError.stackTrace","Add Scala instrumentation and Scala API for Monix Tasks","Add instrumentation for Mongo async/reactivestreams drivers versions 3.4.x to 4.1.x","Scala Cats Effect 3 API to support passing the transaction by implicit reference","Add Instrumentation for Play WS 2.6.0 under Scala 2.13","Agent optimization: change String.replaceAll in favor of Pattern.compile"],"bugs":["Fixes a memory leak with Real-time profiling using JFR","Enhancements for Spring WebFlux and Reactor Netty instrumentation to address gaps in instrumentation","Handle null pointer exceptions in hostname lookup","Properly expire tokens used in CompletableFuture instrumentation","Add additional exception handling to catch ConnectionPoolTimeoutException errors","Resolve Solr FilterCache Memory Leak","Reintroduce MongoDB sync instrumentation","Fix Sql obfuscation","Agent configuration expected_status_codes is not honored when a transaction exception is encountered","Scala Cats Effect - ensure Http4s transaction tracer is created on request run","Fix Akka HTTP bindFlow","Address Caffeine cache causing memory leak and OOM condition"],"security":["Upgrade log4j-core version to 2.17.1 to address security vulnerability CVE-2021-44832","Update Async-Http-Client library version to 2.0.35 to address security vulnerability CVE-2017-14063"],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Update to jfr-daemon 1.7.0 - fixes a memory leak condition by cleaning up copies of JFR recordings. Also updated to use version 0.13.1 of the telemetry-sdk 638 Update HTTP response code attribute names. This will add http.statusCode and http.statusText to spans and transactions 513 Provide support for Datastax/Cassandra WrappedStatments. 525 Add instrumentation for gRPC 1.40.0+ 518 Add suppressed exceptions to ThrowableError.stackTrace 405 Add Scala instrumentation and Scala API for Monix Tasks 543 Add instrumentation for Mongo async/reactivestreams drivers versions 3.4.x to 4.1.x 609 Scala Cats Effect 3 - modified the API to support passing the transaction by implicit reference, rather than using ThreadLocal variables 578 Add Instrumentation for Play WS 2.6.0 under Scala 2.13 594 Agent optimization: change String.replaceAll in favor of Pattern.compile 592 Fixes Upgrade log4j-core version to 2.17.1 to address security vulnerability CVE-2021-44832  625 Enhancements for Spring WebFlux and Reactor Netty instrumentation to address gaps in instrumentation. Also includes support for upgraded Spring Security configurations 538 Update Async-Http-Client library version to 2.0.35 to address security vulnerability CVE-2017-14063   577 Handle null pointer exceptions in hostname lookup 587 Properly expire tokens used in CompletableFuture instrumentation to reduce memory usage and prevent telemetry reporting delays 634 Add additional exception handling to catch ConnectionPoolTimeoutException errors, which may lead to an unrecoverable agent state 637 Resolve Solr FilterCache Memory Leak 613 Reintroduce MongoDB sync instrumentation (erroneously removed in a prior release while async support was added) 635 Fix Sql obfuscation so that it applies correctly to queries with certain formatting 632 Agent configuration expected_status_codes is not honored when a transaction exception is encountered 565 Scala Cats Effect - ensure Http4s transaction tracer is created on request run. This resolves some invalid tracer states that were causing null pointer exceptions 530 Fix Akka HTTP bindFlow 555 Address Caffeine cache causing memory leak and OOM condition  593 Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-750","eolDate":"2024-01-12"},{"agent":"java","date":"2021-12-20","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.4.3/","version":"7.4.3","features":[],"bugs":[],"security":["Upgraded log4j to 2.17.0 to mitigate the security vulnerability CVE-2021-45105"],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Upgraded log4j to 2.17.0 to mitigate the security vulnerability CVE-2021-45105 . 605 Recommended Java versions This fix is recommended if you are running on Java 8 - 17. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-743","eolDate":"2023-12-20"},{"agent":"java","date":"2021-12-14","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.4.2/","version":"7.4.2","features":[],"bugs":[],"security":["Upgraded log4j to 2.16.0 to mitigate the security vulnerability CVE-2021-45046"],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Upgraded log4j to 2.16.0 to mitigate the security vulnerability CVE-2021-45046 . 605 Recommended Java versions This fix is recommended if you are running on Java 8 - 17. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-742","eolDate":"2023-12-14"},{"agent":"java","date":"2021-12-10","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.4.1/","version":"7.4.1","features":[],"bugs":[],"security":["Upgraded log4j to 2.15.0 to mitigate the security vulnerability CVE-2021-44228"],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Upgraded log4j to 2.15.0 to mitigate the security vulnerability CVE-2021-44228 . 605 Recommended Java versions This fix is recommended if you are running on Java 8 - 17. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-741","eolDate":"2023-12-10"},{"agent":"java","date":"2021-10-28","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.4.0/","version":"7.4.0","features":["Support for Java 17","Distributed tracing is on by default. Cross application tracing is now deprecated and disabled by default","Instrumentation support for GraphQL-Java 17.0+","Support for ARM64/Graviton2 platforms"],"bugs":["The existing MongoDB sync client instrumentation was incorrectly applying when MongoDB reactive or async client was being used"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Support for Java 17 #433 Distributed tracing is on by default and deprecates cross-application tracing #486 Increases the default maximum number of samples stored for span events from 1000 to 2000. The maximum number of samples stored for span events can be configured via the max_samples_stored configuration in the newrelic.yml. This feature causes an increase in the consumption of data. The amount of increase will depend on the application. This feature can be disabled by adding the following to the agent yaml config nested under the common section: Auto-instrumentation support for GraphQL-Java 17.0+ #487 This version tested agent support for the ARM64/Graviton2 platform Fixes The existing MongoDB sync client instrumentation was incorrectly applying when MongoDB reactive or async client was being used, which could lead to segment timeouts and long transaction response times. #476 Deprecations and removed features Cross application tracing is now deprecated, and disabled by default. To continue using it, enable it with cross_application_tracer.enabled = true and distributed_tracing.enabled = false. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-740","eolDate":"2023-10-28"},{"agent":"java","date":"2021-09-30","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.3.0/","version":"7.3.0","features":["Support for Java 16","Instrumentation for java.net.http.HttpClient","Migrate the Agent’s caching library from Guava to Caffeine","Removed support for the anorm-2.0 instrumentation module"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Support for Java 16 Auto-instrumentation support for java.net.http.HttpClient Migrate the Agent’s caching library from Guava to Caffeine  (Special thanks to community member Stephan Schroevers  for this contribution) Caffeine provides an in-memory cache  using a Google Guava inspired API. The improvements draw on the author’s experience designing Guava's cache and ConcurrentLinkedHashMap. We expect this change to provide improvement in cases where we saw thread contention and deadlocks attributable to the Guava library. Fixes Removed support for the anorm-2.0 instrumentation module The artifacts that this module instrumented are no longer available. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-730","eolDate":"2023-09-30"},{"agent":"java","date":"2021-09-09","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.2.0/","version":"7.2.0","features":["Add Scala instrumentation for STTP versions 2 & 3, Akka-HTTP, HTTP4s and STTP core backends","Add Scala instrumentation for Cats-effect v2","Add Scala instrumentation for ZIO v1","Add Scala instrumentation for HTTP4s client & server v0.21","Add Scala instrumentation for Play 2.3-2.8","Add Scala instrumentation for Akka-HTTP v10.1 & v10.2","Scala APIs provided for explicit instrumentation of Cats-effect v2 and ZIO v1","AWS v2 DynamoDB instrumentation","GraphQL 16 instrumentation"],"bugs":["JFR feature causing excessive overhead when enabled","Existing MongoDB instrumentation was partially applying when MongoDB Reactive Streams was being used"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Scala Library Instrumentation #362  and #363 STTP versions 2 & 3  Akka-HTTP, HTTP4s and STTP core backends Cats-effect v2 ZIO v1 HTTP4s client & server v0.21 Play 2.3-2.8 Akka-HTTP v10.1 & v10.2 For more information, see Scala instrumentation . Scala API support (see PRs above) Scala APIs provided for explicit instrumentation of several of above libraries in case auto-instrumentation is not desired Cats-effect v2 ZIO v1 AWS v2 DynamoDB Instrumentation #343 Synchronous and asynchronous AWS v2 APIs are auto-instrumented similarly to v1 APIs For more information, see Add support for AWS SDK 2 DynamoDB sync/async clients GraphQL 16 Instrumentation #396 Create meaningful transaction names Create meaningful spans Reporting GraphQL errors For more information, see GraphQL for Java JFR feature causing excessive overhead when enabled JFR #203 Refactored code to use less memory. Fixes The existing MongoDB instrumentation was partially applying when MongoDB Reactive Streams is being used. Disable weaving package when MongoDB 4.x+ reactive driver detected #341 For more information, see Spring Reactive DB Drivers - MongoDB Support Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-720","eolDate":"2023-09-09"},{"agent":"java","date":"2022-11-15","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.11.1/","version":"7.11.1","features":["Update snakeyaml lib to v1.33 security patch"],"bugs":["Fix bug with log4j2 metrics","Adds a previously missing delimiter in POSTGRES_DIALECT_PATTERN"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date . New features and improvements Fixes Fix bug with log4j2 metrics 1068 Adds a previously missing delimiter in POSTGRES_DIALECT_PATTERN \"|\" 1050 Update snakeyaml lib to v1.33 security patch 1077 Deprecation notice The following instrumentation modules have been deprecated for removal: cassandra-datastax-2.1.2 httpclient-3.0 jdbc-embedded-derby-10.10.1.1 jetty-7 jetty-7.6 jetty-9 jetty-9.0.4 jetty-9.1 mongodb-2.12 mongodb-2.14 mongodb-3.0 okhttp-3.0.0 okhttp-3.4.0 okhttp-3.5.0 The httpResponseCode, response.status and response.statusMessage transaction/span attributes are deprecated and will be removed in a future release. These have been replaced by http.statusCode and http.statusText. Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-7111","eolDate":"2023-11-15"},{"agent":"java","date":"2022-10-27","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.11.0/","version":"7.11.0","features":["Support for Java 19","Support for Play 2.8.16+","Support for ojdbc8 v21.1.0.0+","Support for Semeru/OpenJ9 JVMs","Support log forwarding for java.util.logging","Agent log forwarding now collects context data via MDC","This version increases the default limit of custom events from 10,000 events per minute to 30,000 events per minute","Code-level metrics is on by default"],"bugs":["Prevent an exception from being thrown in the Jedis instrumentation","Improvement on Http4s transactions","Fix noticeError API not verifying whether errors were expected","Adds command for Lettuce queries to clusters","Fix exception when building up the agent jar from a clean repo","Better error handling for code-level metrics","Fix HttpUrlConnection spans not terminating on exception"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Support Java 19 1022 Support Play 2.8.16+ 981 Support ojdbc8 v21.1.0.0+ 1042 Support Semeru/OpenJ9 JVMs 993 Support log forwarding for java.util.logging (JUL) 1049 Support forwarding log context data 866 The agent can now forward data in Mapped Diagnostic Context (MDC, logback/slf4j) and ThreadContext (log4j2) as attributes when forwarding log records. When the feature is enabled, these attributes will be added to the log records with a context. prefix. For details on how to enable this feature see the documentation for context_data . Custom Event Limit Increase  1036 This version increases the default limit of custom events from 10,000 events per minute to 30,000 events per minute. In the scenario that custom events were being limited, this change will allow more custom events to be sent to New Relic. There is also a new configurable maximum limit of 100,000 events per minute. To change the limits, see the documentation for max_samples_stored . To learn more about the change and how to determine if custom events are being dropped, see our Explorers Hub post . Code-level metrics on by default 1037 The code-level metrics functionality introduced with agent 7.10 is now enabled by default. This feature will cause an increase in the consumption of data. The amount depends on the application. To disable code-level metrics, see instructions on our code-level metrics documentation . Fixes Prevent an exception from being thrown in the Jedis instrumentation 1011 Improvement on Http4s transactions 1006 Fix noticeError API not verifying whether errors were expected 1014 Adds command for Lettuce queries to clusters 1031 Fix exception when building up the agent jar from a clean repo 1048 Better error handling for code-level metrics 1021  1051 Fix HttpUrlConnection spans not terminating on exception 1053 Deprecation notice The following instrumentation modules are being deprecated for removal: cassandra-datastax-2.1.2 httpclient-3.0 jdbc-embedded-derby-10.10.1.1 jetty-7 jetty-7.6 jetty-9 jetty-9.0.4 jetty-9.1 mongodb-2.12 mongodb-2.14 mongodb-3.0 okhttp-3.0.0 okhttp-3.4.0 okhttp-3.5.0 The httpResponseCode, response.status and response.statusMessage transaction/span attributes are deprecated and will be removed in a future release. These have been replaced by http.statusCode and http.statusText. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life . Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like: In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-7110","eolDate":"2023-10-27"},{"agent":"java","date":"2021-07-15","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.1.1/","version":"7.1.1","features":[],"bugs":["Due to overhead caused in some applications Real-time profiling for Java using JFR metrics is now disabled by default"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Real-time profiling for Java using JFR metrics Due to overhead caused in some applications Real-time profiling for Java using JFR metrics \nis now disabled by default. It can be enabled using the agent settings (newrelic.yml) . Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-711","eolDate":"2023-07-15"},{"agent":"java","date":"2022-09-15","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.10.0/","version":"7.10.0","features":["Added Jakarta EE 9/9.1 compatible instrumentation","Code level metrics","Agent log forwarding adds new attributes to log events"],"bugs":["Fixed an issue with distributed tracing headers not being added on external requests made with the HttpUrlConnection client"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements Added the following Jakarta EE 9/9.1 compatible instrumentation: Jetty 11 Tomcat 10 Enterprise Java Beans 4.0 Jakarta RS/WS Jersey 3+ Jersey Client 3 JSP 3 Servlet 5 & 6 Jakarata.xml JMS 3 Glassfish 6.0 Open Liberty 21.0.0.12+ Code level metrics For traced methods in automatic instrumentation or from @Trace annotations, the agent is now capable of reporting metrics with method-level granularity. When the new functionality is enabled , the agent will associate source-code-related metadata with some metrics. Then, when the corresponding Java class file that defines the methods is loaded up in a New Relic CodeStream -powered IDE, the four golden signals  for each method will be presented to the developer directly. Agent log forwarding now adds the following attributes to log events for the log4j2 and logback1.2 frameworks: thread.name thread.id logger.name logger.fqcn error.class error.stack error.message Fixes Fixed an issue with distributed tracing headers not being added on external requests made with the HttpUrlConnection client Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life . Full changelog : https://github.com/newrelic/newrelic-java-agent/compare/v7.9.0...v7.10.0 Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.7.0 and 7.8.0, the results printed to the console will be: In this example, these lines were added to the default newrelic.yml in Java agent version 7.8.0. If you are moving to 7.8.0 or higher, you should add these new lines to your original newrelic.yml.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-7100","eolDate":"2023-09-15"},{"agent":"java","date":"2021-07-07","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.1.0/","version":"7.1.0","features":["Java instrumentation by XML traceLambda and traceByReturnType properties added","Scala APIs to allow Scala code to be instrumented using a fluent Scala API","Real-time profiling for Java using JFR metrics is enabled by default instead of the Java annotations"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Known issues Some customers saw increased overhead when Real-time profiling is enabled. See notice  below on how to disable it. New features and improvements: Java instrumentation by XML new properties: traceLambda - to trace lambdas inside a method traceByReturnType - to trace all methods in a class that return a given type These are compatible with Java and Scala. For more information, see\nJava instrumentation by XML . Scala APIs New artifacts allow Scala code to be instrumented using a fluent Scala API\ninstead of the Java annotations. There are specific artifacts for versions\n2.10, 2.11, 2.12, 2.13 of Scala. Scala 3.0 users can use the 2.13 artifact. For more information, see Scala instrumentation . Real-time profiling for Java using JFR metrics This feature is now enabled by default. This feature will cause an increase in the consumption of data. The amount depends on the application. This feature can be disabled by adding the following to the agent yaml config nested under the common section: For more information, see JFR core README . Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-710","eolDate":"2023-07-07"},{"agent":"java","date":"2021-06-15","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.0.1/","version":"7.0.1","features":[],"bugs":["Fixes an issue where the agent would break OkHttp versions 3.X and lower"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixes an issue where the agent would break OkHttp versions 3.X and lower. (#324 )","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-701","eolDate":"2023-06-15"},{"agent":"java","date":"2021-06-09","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/7.0.0/","version":"7.0.0","features":["This version of the agent only supports Java 8+","Real-time profiling for Java using JFR metrics","Adds support for akka http with Scala 2.13","Class annotation to trace lambda methods","Class annotation to trace methods by return type"],"bugs":["Fixes an issue that could cause multiple versions of akka-http-core instrumentation to apply at the same time","The agent will now log dropped events at FINE instead of WARN to decrease verbosity","Fixes Javadoc comments that incorrectly stated that, when calling the noticeError API multiple times, the first error would be reported when in fact it's the last error that is reported"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements: Real-time profiling for Java using JFR metrics  is now fully integrated into the Java agent. See the JFR core README  for additional details. This feature requires a supported version of Java 8 (specifically version 8u262 or higher) or Java 11 or higher and is currently disabled by default. To enable it set the following in your yaml (indented 2 spaces under the common section). Notice:  If you were previously using the jfr-daemon jar  as an agent extension or standalone process you should remove that option to avoid potential conflicts with the JFR service that is now built into the agent. Not compatible with Java 7. In order to continue to innovate and efficiently provide new capabilities to our customers who run on the JVM, this and future agent versions aren't compatible with Java 7. If you're running Java 7, you may continue to use Java agent 6.5.0 or lower. For details, see this topic on\nthe Explorers Hub . Adds support for akka http with Scala 2.13. #271 Class annotation to trace lambda methods. #274 Class annotation to trace methods by return type. #275 Fixes: Fixes an issue that could cause multiple versions of akka-http-core instrumentation to apply at the\nsame time. #208 The agent will now log dropped events at FINE instead of WARN to decrease\nverbosity. #296 Fixes Javadoc comments that incorrectly stated that, when calling the noticeError API multiple times,\nthe first error would be reported when in fact it's the last error that is reported. #313 Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life . Known Issues OkHttp This release contains a bug that breaks OkHttp versions 3.X and below. All affected users should upgrade to 7.0.1.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-700","eolDate":"2023-06-09"},{"agent":"java","date":"2022-03-03","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/6.5.4/","version":"6.5.4","features":[],"bugs":[],"security":["Changed log4j version to 2.12.4 to mitigate the security vulnerability CVE-2021-44832. This version of the agent is not compatible Java 7."],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Changed log4j version to 2.12.4 to mitigate the security vulnerability CVE-2021-44832 . 766 Mitigation for Java 7 This release is compatible with Java 7. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life . Update to latest version [#procedures] To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console. Then, to update to the latest Java agent version: Back up the entire  Java agent root directory  to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number. Download the agent. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory . Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed . Restart your Java dispatcher. If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory. Update agent config differences [#diff] We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings. For example, if you diff the default newrelic.yml files for Java agent versions 7.7.0 and 7.8.0, the results printed to the console will be: In this example, these lines were added to the default newrelic.yml in Java agent version 7.8.0. If you are moving to 7.8.0 or higher, you should add these new lines to your original newrelic.yml.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-654","eolDate":"2024-03-03"},{"agent":"java","date":"2021-12-21","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/6.5.3/","version":"6.5.3","features":[],"bugs":[],"security":["Update to log4j 2.12.3 to mitigate CVE-2021-45105"],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Changed log4j version to 2.12.3 to mitigate the security vulnerability CVE-2021-45105 . 605 Mitigation for Java 7 This release is compatible with Java 7. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-653","eolDate":"2023-12-21"},{"agent":"java","date":"2021-12-15","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/6.5.2/","version":"6.5.2","features":[],"bugs":[],"security":["Updated log4j version to 2.12.2 to mitigate the security vulnerability CVE-2021-45046. This version of the agent is not compatible Java 7."],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Changed log4j version to 2.12.2 to mitigate the security vulnerability CVE-2021-45046 . 605 Mitigation for Java 7 This release is compatible with Java 7. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-652","eolDate":"2023-12-15"},{"agent":"java","date":"2021-12-10","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/6.5.1/","version":"6.5.1","features":[],"bugs":[],"security":["Upgraded log4j to 2.15.0 to mitigate the security vulnerability CVE-2021-44228. This version of the agent is not compatible Java 7."],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Upgraded log4j to 2.15.0 to mitigate the security vulnerability CVE-2021-44228 . 605 Recommended Java versions Log4j 2.15.0, which fixes the security vulnerability CVE-2021-44228 , is only compatible with Java 8+. Therefore, this version of the agent is not compatible with Java 7 and is only recommended if you are using Java 8+ and are otherwise unable to upgrade to Java agent 7.4.1. Mitigation for Java 7 Java agent versions 4.12.0 through 6.5.0 (which support Java 7) use Log4j 2.11.2  which falls into the affected range. For Java 7 users the recommended mitigation from Apache Log4j Security Vulnerabilities  is to set the system property -Dlog4j2.formatMsgNoLookups=true. Mitigation: In releases 2.10, this behavior can be mitigated by setting the system property log4j2.formatMsgNoLookups. For releases 2.7 and 2.14.1, all PatternLayout patterns can be modified to specify the message converter as %m{nolookups} instead of just %m. For releases 2.0-beta9 and 2.10.0, the mitigation is to remove the JndiLookup class from the classpath: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class Note : The alternate approach of defining the LOG4J_FORMAT_MSG_NO_LOOKUPS=true environment variable will not work with the NR Java Agent. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-651","eolDate":"2023-12-10"},{"agent":"java","date":"2021-04-26","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/6.5.0/","version":"6.5.0","features":["The agent no longer bundles SSL certificates with it and the use_private_ssl option that configured the agent to use the previously bundled certificates has been removed"],"bugs":["Incorrect transaction naming when using JAX-RS sub-resources","Reactor Netty instrumentation improvements and fixes"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features and improvements: The agent no longer bundles SSL certificates with it and the use_private_ssl option that configured the agent to use\nthe previously bundled certificates has been removed. By default, the agent will use the SSL truststore provided by\nthe JVM unless it is explicitly configured to use a different truststore with the ca_bundle_path option. See\nConfiguring your SSL certificates \nfor more details. Fixes: Fixes an issue that could cause incorrect transaction naming when using JAX-RS sub-resources. Reactor Netty instrumentation improvements and fixes. Deprecation notice Java 7 compatibility deprecation In order to continue to innovate and efficiently provide new capabilities to our customers who run on the JVM, Java 7\nsupport has been deprecated and this will be the last version of the agent compatible with it. If you are running Java 7, you may continue to use Java agent 6.5.0 or lower. For more information, see the Explorers Hub post . Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and\nperformance benefits. Additionally, older releases will no longer be supported when they reach\nend-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-650","eolDate":"2023-04-26"},{"agent":"java","date":"2021-03-02","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/6.4.2/","version":"6.4.2","features":[],"bugs":["Some instrumentation modules (e.g. jax-rs-1.0) could have a WeaveViolation and not apply properly"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixes an issue that could cause some instrumentation modules (e.g. jax-rs-1.0) to have a WeaveViolation and not apply properly.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-642","eolDate":"2023-03-02"},{"agent":"java","date":"2021-02-02","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/6.4.1/","version":"6.4.1","features":[],"bugs":["Spans would not get sent to Infinite Tracing"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixes an issue in 6.4.0 where spans would not get sent to Infinite Tracing.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-641","eolDate":"2023-02-02"},{"agent":"java","date":"2021-01-27","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/6.4.0/","version":"6.4.0","features":["Spring Webflux/Netty Reactor instrumentation improvements","The agent will now utilize a backoff sequence on connection retries to Infinite Tracing","New distributed tracing APIs have been added to better support general use cases for propagating distributed tracing headers (insertDistributedTraceHeaders/acceptDistributedTraceHeaders)","Updated the Java agent’s snakeyaml dependency to 1.27"],"bugs":["There is an issue with this agent release that could lead to spans not being sent to Infinite Tracing. Please use 6.4.1 instead.","In some environments the jar collector service could lead to high CPU utilization at application startup. The agent now provides a configurable rate limiter, with a reasonable default, for processing jars detected in the application’s environment."],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Note: There is an issue with this agent release that could lead to spans not being sent to Infinite Tracing. Please use 6.4.1  instead. New Features and Improvements: Spring Webflux/Netty Reactor instrumentation improvements for enhanced tracing across asynchronous thread hops. The agent will now utilize a backoff sequence on connection retries to Infinite Tracing. New distributed tracing APIs have been added to better support general use cases for propagating distributed tracing headers. In particular the new APIs provide enhanced support for W3C Trace Context  but are flexible enough to support other header protocols that may be supported by the agent in the future. Previous distributed tracing APIs have been deprecated and are subject to removal in a future agent release. See documentation here . Transaction.insertDistributedTraceHeaders(Headers)  is used to create and insert distributed tracing headers (both newrelic and W3C Trace Context) into a Headers data structure. Transaction.acceptDistributedTraceHeaders(TransportType, Headers)  is used to accept the distributed tracing headers sent from the calling service and link these services together in a distributed trace. Fixes: Updated the Java agent’s snakeyaml dependency to 1.27. In some environments the jar collector service could lead to high CPU utilization at application startup. The agent now provides a configurable rate limiter, with a reasonable default, for processing jars detected in the application’s environment. See documentation here . Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-640","eolDate":"2023-01-27"},{"agent":"java","date":"2020-12-17","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/6.3.0/","version":"6.3.0","features":["Support for Spring Webflux versions 5.3+","Added reactor-netty.errors.enabled configuration to allow disabling error reporting in Subscriber::onError","Support for Scala 2.13 and frameworks compiled with 2.13 Akka-http or Play","Updated the Java agent’s Apache HttpClient dependency to 5.13"],"bugs":["The netty-4.0.8 instrumentation would sometimes not start a Transaction on channelRead","Spring Webclient could report the wrong URL when multiple HTTP calls to several URLs occurred in parallel"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Spring Webflux The Java agent now supports Spring Webflux versions 5.3+ Added reactor-netty.errors.enabled configuration to allow disabling error reporting in Subscriber::onError. Scala 2.13 The Java agent now provides support for Scala 2.13 and frameworks compiled with 2.13 Akka-http, Play Fixes The netty-4.0.8 instrumentation would sometimes not start a Transaction on channelRead, potentially affecting instrumentation dependent on it including: Spring, Akka and Play Updated the Java agent’s Apache HttpClient dependency to 5.13 Spring Webclient could report the wrong URL when multiple HTTP calls to several URLs occurred in parallel","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-630","eolDate":"2022-12-17"},{"agent":"java","date":"2020-11-17","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/6.2.1/","version":"6.2.1","features":[],"bugs":["Fixes an issue where Spring-Webflux applications with endpoints returning Flux or empty content could become unresponsive"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixes an issue where Spring-Webflux applications with endpoints returning Flux or empty content could become unresponsive","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-621","eolDate":"2022-11-17"},{"agent":"java","date":"2020-11-10","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/6.2.0/","version":"6.2.0","features":["Adds support for Akka Http Core 10.2.0","Adds support for gRPC 1.30.0","Adds support for map and flatmap async external calls in spring webflux framework","Adds support for Play 2.16.3","The agent now supports parsing cgroup ids that do not contain docker-"],"bugs":["Prevents the agent from logging a timeout exception when using New Relic Edge with Infinite Tracing","Prevents the agent from logging a socket exception when trying to retrieve cloud provider information in a non-cloud environment","Adds New Relic EU certifications if ca_bundle_path is specified. This fix also reintroduces the use_private_ssl config, which can be set to add NR agent certs to the truststore."],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features Adds support for Akka Http Core 10.2.0 . Thank you jobicarter  for reporting this issue. Adds support for gRPC 1.30.0 . Thank you jef  for submitting this request and trying it out. Adds support for map and flatmap async external calls in spring webflux framework . Previously the agent didn’t support client calls that occurred within the map or flatmap methods within the spring webflux framework. External calls such as serviceB and serviceC in the example below would not get reported to New Relic: Adds support for Play 2.16.3 . Many thanks to junder31  for this contribution. Improvements The agent now supports parsing cgroup ids that do not contain docker- . Previously, the agent only supported docker cgroup ids that contained docker- in them, such as 1:cpu:/system.slice/docker-12345abcde.scope. The agent now supports parsing cgroup ids such as 1:cpu:/system.slice/crio-12345abcde.scope. Fixes Prevents the agent from logging a timeout exception when using New Relic Edge with Infinite Tracing but the agent hasn’t sent spans in a while . Prevents the agent from logging a socket exception when trying to retrieve cloud provider information in a non-cloud environment . Adds New Relic EU certifications  if ca_bundle_path is specified . This fix also came with the reintroduction of the use_private_ssl config, which can be set to add our agent certs to the truststore. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-620","eolDate":"2022-11-10"},{"agent":"java","date":"2020-09-30","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/6.1.0/","version":"6.1.0","features":["Java 15 support","Added Segment.addCustomAttribute APIs","Newrelic.addCustomParameter API now supports boolean values","The Java agent now includes the newrelic.com SSL certificate"],"bugs":["The agent would try to read environment variables using system-property syntax","Fixed an issue where applications could fail to start due to the agent attempting to access the JMX MBean server before it was initialized"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Java 15 The New Relic Java agent is now fully compatible with version 15 of the OpenJDK and Hotspot JDKs. APIs New Segment.addCustomAttribute(...) APIs  have been added for adding attributes directly to spans. Newrelic.addCustomParameter API  now supports boolean values Fixes The agent would try to read environment variables using system-property syntax. It will now log the correct syntax and ignore the incorrect value. Notes The Java agent now includes the newrelic.com SSL certificate.  In previous agent versions, applications using a custom Truststore would have to provide their certificate or use the use_private_ssl configuration which was removed in 6.0.0. Fixed an issue where applications could fail to start due to the agent attempting to access the JMX MBean server before it was initialized.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-610","eolDate":"2023-09-30"},{"agent":"java","date":"2020-08-26","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/6.0.0/","version":"6.0.0","features":["Agent linking metadata can be accessed via JMX","Support for OkHTTP 4.4","Improve agent reconnect behavior","SSL certificates are no longer bundled with the agent. Users previously using use_private_ssl should now use the ca_bundle_path option to provide their own certs"],"bugs":["Fix for asynchronous jar file collection","Fix for Real Time Streaming","Fix race condition that could cause connection pool exhaustion"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Register an MBean  to expose the agent linking metadata. Support for okhttp 4.4  instrumentation. Improve reconnect behavior  by not  pinning to preconnected collector host instance. Fixes Fix for asynchronous jar file collection . Collection of modules will no longer block the initial first harvest. Fix for Real Time Streaming. The first Real Time Streaming harvest will no longer be delayed by 30 seconds. Fix for reactor-netty verifier versions Fix race condition around connection pool exhaustion  by separating pool timeout from connection timeout. Note re: certificate bundle use_private_ssl This release removed the certificate bundle from the agent artifact. Users previously using use_private_ssl should now use the ca_bundle_path configuration directive . For more information, see the Java v6.0.0 release on GitHub .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-600","eolDate":"2023-08-26"},{"agent":"java","date":"2019-12-10","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.9.0/","version":"5.9.0","features":["AWS SDK support for S3, SQS, and SNS","Distributed Tracing now supports traces originating from the New Relic Browser agent","The agent no longer has a dependency on ANTLR"],"bugs":["The ca_bundle_path configuration setting would fail to correctly import certificates when running on IBM J9","Clarified the startup log message about the state of browser monitoring for the current application","The agent logger would sometimes throw a NullPointerException","The agent would stop reporting Kafka metrics when one or more clients where closed","HttpURLConnection instrumentation could cause a NullPointerException in the agent logs and fail to report External metrics"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements AWS SDK AWS S3 - The Java agent now reports calls to Amazon S3 using AmazonS3 and S3Client as external metrics AWS SQS - The Java agent now reports calls to Amazon SQS using AmazonSQS, AmazonSQSAsync, SqsClient as message queue metrics AWS SNS - The Java agent now reports calls to Amazon SQS using AmazonSNS, AmazonSNSAsync, SnsClient as message queue metrics Distributed Tracing - The agent now supports distributed traces  originating from the New Relic Browser agent Fixes The ca_bundle_path configuration setting would fail to correctly import certificates when running on IBM J9 Clarified the startup log message about the state of browser monitoring for the current application. The agent logger would sometimes throw a NullPointerException The agent would stop reporting Kafka metrics when one or more clients where closed HttpURLConnection instrumentation could cause a NullPointerException in the agent logs and fail to report External metrics Deprecated Jar Collector system properties prefixed with newrelic.config.module and environment variables prefixed with NEW_RELIC_MODULE are deprecated and will be removed in a future agent release. Instead use the newrelic.config.jar_collector and NEW_RELIC_JAR_COLLECTOR prefixes. Removed dependency The agent no longer has a dependency on ANTLR.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-590","eolDate":"2022-12-10"},{"agent":"java","date":"2019-10-29","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.8.0/","version":"5.8.0","features":["gRPC enhancements","Vert.x 3.8 support","XML custom instrumentation support for leaf tracers","Class Histogram extension for heap memory analysis","Support for Jedis 3.0.0 and higher","Lettuce 4 and 5 instrumentation available in the Java agent incubator","Telemetry SDK for Java introduced"],"bugs":["Solr 7 instrumentation would not report Update JMX metrics","HttpURLConnection instrumentation produced External metrics only when network methods (getInputStream, getResponseCode) are called","MongoDB instrumentation could report duplicate metrics"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features gRPC gRPC error reporting is now configurable Response codes, component type, and method type are now recorded as attributes. The agent now reports the gRPC status code rather than \"translating\" to HTTP status codes. Vert.x The Java agent now provides visibility into your applications built using the Vert.x 3.8. The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls made with Vert.x HTTP client. XML custom instrumentation The custom XML instrumentation XSD has been enhanced to support now include support for specifying leaf tracers . Class Histogram A new Class Histogram extension  is now available to report heap memory details as events. Jedis Added support for Jedis 3.0.0 and higher. You can now see your Jedis calls in breakdowns in the overview chart, entries in the Databases tab, and segments in transaction traces. Lettuce Instrumentation modules for Lettuce 4 and 5 are now available via the Java agent incubator . New OSS SDK We now have an open source Telemetry SDK for Java  for sending telemetry data to New Relic. The current SDK supports sending dimensional metrics to the Metric API and spans to the Trace API. Fixes The Solr 7 instrumentation would not report Update JMX metrics. HttpURLConnection instrumentation produced External metrics only when network methods (getInputStream, getResponseCode) are called. MongoDB instrumentation would report duplicate metrics when applications invoked MongoClientOptions.build() more than once.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-580","eolDate":"2022-10-29"},{"agent":"java","date":"2019-09-25","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.7.0/","version":"5.7.0","features":["Java 13 support","Update Guava dependency"],"bugs":["Calls to NewRelic.getAgent().getTracedMethod().addOutboundRequestHeaders() could cause an exception","NoClassDefFoundError could occur when a spring controller was used without a root level RequestMapping annotation","The gc_time metric is disabled by default as its results are often misleading"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Java 13 The New Relic Java agent is now fully compatible with version 13 of the OpenJDK and Hotspot JDKs. Bug fixes Calls to NewRelic.getAgent().getTracedMethod().addOutboundRequestHeaders() will no longer throw an exception if a traced method has started but a transaction has not. This could happen by calling this in a method annotated with @Trace(async=true) before a token is linked. Updates Guava to the newest release. NoClassDefFoundError would occur in agent logs when a spring controller is used without a root level RequestMapping annotation. The gc_time metric, which was enabled by default in version 5.2.0, has now been disabled by default since its results are often misleading.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-570","eolDate":"2022-09-25"},{"agent":"java","date":"2019-09-17","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.6.0/","version":"5.6.0","features":["Added getTraceMetadata, getTraceId, getSpanId, isSampled, and getLinkingMetadata APIs"],"bugs":["Spring Webflux WebClient would not track external calls when constructed with baseUrl(String baseUrl)","The NewRelic.getAgent().getConfig().getValue() api would not check configuration values set via environment variables","completable-future instrumentation could hold a reference to Tokens after they were expired, which could cause excessive memory usage","Error traces could report to the wrong application when auto_app_naming is enabled","MongoDB instrumentation would instrument the same builder used by the async and reactive-streams drivers, resulting in excessive memory usage and incorrect transaction times"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New APIs Added getTraceMetadata() . This provides information about the currently executing trace, including the trace and span ids as well as it’s sampled state getTraceId() , which provides the currently executing trace’s identifier from the TraceMetadata. getSpanId() , which provides the span identifier associated with the currently executing span from the TraceMetadata. isSampled() , returns whether or not the current transaction is part of a sampled distributed trace from the TraceMetadata. Added getLinkingMetadata() , which provides an opaque map of key/value pairs that can be used to correlate this application in the New Relic backend. Fixes Spring Webflux WebClient would not track external calls when constructed with baseUrl(String baseUrl) The NewRelic.getAgent().getConfig().getValue() api would not check configuration values set via environment variables The agent’s completable-future instrumentation could hold a reference to Tokens after they were expired, which could cause excessive memory usage. Error traces could report to the wrong application when auto_app_naming is enabled and there were errors from two different application names getting reported during the same harvest The agent’s MongoDB instrumentation would instrument the same builder used by the async and reactive-streams drivers, resulting in excessive memory usage and incorrect transaction times. Note:  The agent will no longer instrument the sync MongoDB driver if the async and/or reactive-streams drivers are on the application’s classpath.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-560","eolDate":"2022-09-17"},{"agent":"java","date":"2019-09-04","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.5.0/","version":"5.5.0","features":["Support for Real Time Streaming","Java agent now uses persistent connections when connecting to New Relic, reducing overhead"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New features Support for Real Time Streaming Event data is now sent to New Relic every five seconds, instead of every minute. As a result, transaction, error, and custom events will now be available in New Relic dashboards in near real time. For more information on how to view your events with a five-second refresh, see the real time streaming documentation . Note that the overall limits on how many events can be sent per minute have not changed. Also, span events, metrics, and trace data is unaffected, and will still be sent every minute. Improvements The Java agent now uses persistent connections when connecting to New Relic, reducing overhead.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-550","eolDate":"2022-09-04"},{"agent":"java","date":"2019-08-27","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.4.0/","version":"5.4.0","features":["New Relic x-ray feature is EOL","Support for OkHttp 4.0","Agent configuration settings set via environment variables are shown on the Environment page","Performance improvements"],"bugs":["Transaction Traces could omit segments when using the spring @Async annotation with servlets","Jax-RS instrumentation was not starting transactions","Race condition during agent startup could manifest as a NoClassDefFoundError","Akka-http instrumentation would attempt multiple retransforms of the same class","noticeError API would drop custom attributes that weren't of type String, Number, or Boolean"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Notes x-ray and any x-ray related attributes and identifiers will no longer be available in this version of the java agent. The New Relic x-ray feature reached end-of-life on April 17, 2019 Improvements OkHttp This release adds support for OkHttp 4.0. You will now see OkHttp calls as external calls  in New Relic. Agent configuration settings set via environment variables will be available on the Environment page. Improves performance of the Java agent. Fixes Transaction Traces  would occasionally miss segments when using the spring @Async annotation with servlets. Jax-RS instrumentation was not starting transactions. A potential race condition during agent startup that would manifest as a NoClassDefFoundError for internal New Relic classes. Akka-http instrumentation would attempt multiple retransforms of the same class. The noticeError API would drop custom attributes that weren't of type String, Number, or Boolean, such as an Enum or other custom types.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-540","eolDate":"2022-08-27"},{"agent":"java","date":"2019-07-24","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.3.0/","version":"5.3.0","features":["Support for gRPC version 1.22","Support for Alibaba's Dragonwell JDK","Support for Azul's Zing JVM","Configurable Security Policies (CSP)"],"bugs":["LinkageError for applications using both OpenJ9 and Log4J log manager","ClassNotFoundException for applications that specify a Log4j ContextSelector via the -DLog4jContextSelector system property","Akka-http instrumentation could name transactions incorrectly","JaxRS instrumentation did not apply to cases where a concrete class implements the same method from two different interfaces","JMX metrics weren't reported when one or more composite attributes were null","Race condition that could throw a NullPointerException","Akka-http path matching instrumentation could produce NullPointerExceptions","ignore_status_codes system property was not getting applied correctly"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements gRPC The Java agent now has support for gRPC version 1.22 Dragonwell JDK The Java agent now fully supports Alibaba's Dragonwell JDK Azul Zing The Java agent now supports Azul's Zing JVM Enables ability to migrate to Configurable Security Policies (CSP)  on a per agent basis for accounts already using High-security mode (HSM . When both HSM and CSP are enabled for an account, an agent (this version or later) can successfully connect with either high_security: true or the appropriate security_policies_token configured. Fixes LinkageError for applications using both OpenJ9 and Log4J log manager ClassNotFoundException for applications that specify a Log4j ContextSelector via the -DLog4jContextSelector system property Akka-http instrumentation would name transactions incorrectly when using an asynchronous onComplete callback to match routes The agent’s JaxRS instrumentation did not apply to cases where a concrete class implements the same method from two different interfaces The agent would not report JMX metrics when one or more composite attributes were null Race condition that could throw a NullPointerException in the agent log during class transformation Akka-http path matching instrumentation could produce NullPointerExceptions when using a \"repeat\" path segment with no values. Transactions that pass some values will report as-is, but transactions that pass no values will be reported with a different segment in the metric name: \"().repeat()\" ignore_status_codes system property was not getting applied correctly","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-530","eolDate":"2022-07-24"},{"agent":"java","date":"2019-06-26","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.2.0/","version":"5.2.0","features":["Adds instrumentation for mongo-java-driver clients created using the MongoClients class","New configuration option to report custom HTTP request headers","Datastore span events now include a db.collection attribute","A maximum of 10,000 transaction events per minute is now enforced"],"bugs":["Long-running transactions with a large number of segments could cause an excessive amount of memory usage"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements MongoDB This release adds instrumentation for mongo-java-driver clients created using the MongoClients class  Previous versions of the agent only supported the MongoClient() constructor  Note: The MongoDB Asynchronous Java Drivers are not yet supported. Custom request header attributes The Java agent now provides a new configuration option to report HTTP request header(s) as transaction attributes . See the documentation  for more details. Distributed tracing Datastore span events  now include a db.collection attribute. This field represents the collection or primary table name for the associated query. It is accessible in Insights, Distributed Tracing, and anywhere you get your favorite spans. GC Time The Java agent now records time spent waiting for garbage collection during the duration of a transaction and includes the GC time on the corresponding transaction trace as well as the transactions time chart. This setting is configurable as follows in the newrelic.yml: Fixes Fixes an issue where very long-running transactions with a large number of segments  would cause an excessive amount of memory usage. The agent will no longer trace segments once the segment_limit  has been reached. Notes The Java agent now enforces a maximum of 10,000 transaction events  per minute.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-520","eolDate":"2022-06-26"},{"agent":"java","date":"2020-07-27","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.14.0/","version":"5.14.0","features":["The Java agent now provides the extensions.reload_modified configuration to disable reloading extensions during runtime","The Java agent now provides updated instrumentation for reactor-netty-0.8.0+ to link the Transaction across threads","Java agent log files is now formatted using log4j's ISO8610_OFFSET_DATE_TIME_HHMM and it is rendered like this in all locales"],"bugs":["Solr instrumentation could throw a NullPointerException"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Agent Extensions The Java agent now provides a configuration to disable reloading extensions during runtime. extensions: reload_modified: false Spring Webflux The Java agent now provides updated instrumentation for reactor-netty-0.8.0+ to link the Transaction across threads. In previous agent versions, Transactions would be named /NettyDispatcher. Logging format To make the agent log easier to sort and read across locales, the date/time format has changed. The new format is log4j's ISO8610_OFFSET_DATE_TIME_HHMM and it is rendered like this in all locales: 2020-07-10T08:33:00,328-0700 [9550 1] com.newrelic INFO: New Relic Agent: Loading configuration file \"lib/./newrelic.yml\" 2020-07-10T08:33:00,423-0700 [9550 1] com.newrelic INFO: Using default collector host: collector.newrelic.com All other data on the log line remains the same. Fixes Solr instrumentation could throw a NullPointerException when Query.toString() returned null.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-5140","eolDate":"2023-07-27"},{"agent":"java","date":"2020-06-16","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.13.0/","version":"5.13.0","features":["Additional info will be copied from transaction events onto span events when using distributed or Infinite Tracing","Added TracedMethod.addCustomAttribute APIs for adding attributes to spans","The Java agent now uses AWS's IMDS v2 to gather instance information"],"bugs":["Jetty JMX metrics would not report when running embedded in Spring Boot","Local configuration settings could revert to the default following an agent reconnect"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Distributed tracing: With distributed tracing spans  and/or Infinite Tracing , the Java agent will now incorporate additional information from the transaction event  on to the root span event  of the transaction. New TracedMethod.addCustomAttribute(...) APIs  have been added for adding attributes directly to spans. Note:  Any attribute include or exclude settings specific to transaction events should be applied to your span attributes configuration or your global attributes configuration. The Java agent now uses AWS's IMDS v2 to gather instance information. Fixes Jetty JMX metrics would not report when running embedded in Spring Boot. Local configuration settings could revert to the default following an agent reconnect.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-5130","eolDate":"2023-06-16"},{"agent":"java","date":"2020-05-15","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.12.1/","version":"5.12.1","features":[],"bugs":["With distributed tracing enabled and Infinite Tracing disabled, a bug could cause spans to be omitted from distributed traces"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Notes Bug fixes This is a patch release that resolves an issue in 5.12.0. With distributed tracing enabled and Infinite Tracing disabled, a defect in version 5.12.0 causes spans to be omitted from distributed traces. Any customers currently on 5.12.0 are strongly  encouraged to upgrade to this 5.12.1 patch release.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-5121","eolDate":"2023-05-15"},{"agent":"java","date":"2020-05-05","downloadLink":null,"version":"5.12.0","features":["Infinite Tracing on New Relic Edge","Spring PatchMapping annotation will now be used to start and name transactions","Span Events now report error attributes if an error occurs"],"bugs":["Solr Instrumentation could cause a NullPointerException","The JDBC ResultSet instrumentation is now disabled by default","The quartz_job configuration did not affect applications using Quartz-2.0 and higher"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New Features Added support for Infinite Tracing on New Relic Edge . Infinite Tracing observes 100% of your distributed traces and provides visualizations for the most actionable data so you have the examples of errors and long-running traces so you can better diagnose and troubleshoot your systems. You configure your agent to send traces to a trace observer in New Relic Edge. You view your distributed traces through the New Relic’s UI. There is no need to install a collector on your network. Infinite Tracing is currently available on a sign-up basis. If you would like to participate, please contact your sales representative. Known Issue In-process spans from Java services will not appear in distributed traces. All users should upgrade to 5.12.1. Improvements Spring Spring PatchMapping annotation will now be used to start and name transactions. SQL Common Table Expressions in SQL Server, Postgres, and MySQL will report Datastore Metrics  Datastore/<vendor>/statement/<first cte name>/with and Datastore/<vendor>/operation/with Distributed Tracing Span events  now report error attributes if an error occurs: TransactionError events will also contain a corresponding spanId attribute indicating where the error occurred. Fixes Solr Instrumentation could cause a NullPointerException in the agent logs for queries containing null parameters The JAVA_ENV environment variable configuration has been deprecated. Use NEW_RELIC_ENVIRONMENT to set the environment configuration for the agent  to use The JDBC ResultSet instrumentation is now disabled by default internally. Applications configured solely via system properties and/or environment variables can enable with: -Dnewrelic.config.class_transformer.com.newrelic.instrumentation.jdbc-resultset.enabled=true or NEW_RELIC_CLASS_TRANSFORMER_COM_NEWRELIC_INSTRUMENTATION_JDBC-RESULTSET_ENABLED=TRUE The quartz_job configuration did not affect applications using Quartz-2.0 and higher","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-5120","eolDate":"2023-05-05"},{"agent":"java","date":"2020-03-18","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.11.0/","version":"5.11.0","features":["Java 14 support","Real-time profiling for Java using JFR metrics extension"],"bugs":["The agent would log a NullPointerException when trying to accept distributed trace payloads before it had connected","Fixes an issue where W3C headers from New Relic’s .NET agent could produce malformed W3C traceparent headers","The agent now logs ForceRestartExceptions at warning level rather than severe","The noticeError API now supports reporting attributes of boolean and number types"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Java 14 The New Relic Java agent is now fully compatible with version 14 of the OpenJDK and Hotspot JDKs. Java Flight Recorder A new Java Flight Recorder agent extension  is now available to report real-time Java profiling metrics for application running on Java 14, including thread allocation, garbage collection and heap memory Fixes The agent would log a NullPointerException when trying to accept distributed trace payloads before it had connected to rpm.newrelic.com Fixes an issue where W3C headers from New Relic’s .NET agent could produce malformed W3C traceparent headers The agent now logs ForceRestartExceptions at warning level rather than severe The noticeError API now supports reporting attributes of boolean and number types rather than their string representations","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-5110","eolDate":"2023-03-18"},{"agent":"java","date":"2019-06-13","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.1.1/","version":"5.1.1","features":[],"bugs":["Fixed bugs in the gRPC instrumentation","Fixed memory leak","Agent could cause the gRPC server listeners to fail to execute its completed and cancelled methods"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes gRPC This release fixes two bugs in the Java agent's gRPC instrumentation. We highly recommend customers using gRPC instrumentation to upgrade to this and or later agent versions. References to transaction segments were not being removed correctly, which can cause a memory leak The agent could cause the gRPC server listeners to fail to execute its completed and/or cancelled methods, which can cause unexpected behavior","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-511","eolDate":"2022-06-13"},{"agent":"java","date":"2020-01-29","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.10.0/","version":"5.10.0","features":["Support for W3C Trace Context","Adds instrumentation for queries in versions 3.8+ of the Datastax Cassandra driver","AWS Async SDK for S3, SQS, and SNS"],"bugs":["Changes to several config property names","The strip_exception_messages config now excludes nested exception messages","The agent will now use a lightweight tracer for SQL tracers beyond the segment_limit","The agent would fail to report the Docker containerId for some combinations of systemd and Kubernetes","The agent logger could fail to log"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Support for W3C Trace Context, with easy upgrade from New Relic trace context Distributed tracing now supports W3C Trace Context  headers for HTTP and gRPC protocols when distributed tracing is enabled. Our implementation can accept and emit both W3C trace header format and New Relic trace header format. This simplifies agent upgrades, allowing trace context to be propagated between services with older and current releases of New Relic agents. With this release, W3C trace header format will always be accepted and emitted. New Relic trace header format will be accepted, and you can optionally disable emission of the New Relic trace header format. The New Relic trace header format can disabled using this config or as documented here : newrelic.config.distributed_tracing.exclude_newrelic_header = true Also, see Known issues and workarounds . Cassandra This release adds instrumentation for queries in versions 3.8+ of the Datastax Cassandra driver, including slow query  support. You’ll see relevant breakdowns in the overview chart, entries on the Databases page, and segments in transaction traces. AWS Async SDK AWS S3 - The Java agent now reports calls to Amazon S3 using the S3AsyncClient as external metrics AWS SQS - The Java agent now reports calls to SqsAsyncClient as message queue metrics AWS SNS - The Java agent now reports calls to Amazon SQS using SNSAsyncClient as message queue metrics Fixes In an effort to modernize our language and improve clarity, we have renamed several config values. The old names will still work for now, but they will all be removed in the next major version. transaction_tracer.slow_query_whitelist is now transaction_tracer.collect_slow_queries_from strip_exception_messages.whitelist is now strip_exception_messages.allowed_classes command_parser.blacklist is now command_parser.disallow The strip_exception_messages config now excludes nested exception messages The agent will now use a lightweight tracer for SQL tracers beyond the segment_limit , improving performance in cases with a high number of segments. The agent would fail to report the Docker containerId for some combinations of systemd and Kubernetes The agent logger would fail to log with: “ERROR RollingFileAppender 'File': No TriggeringPolicy provided” when newrelic.config.log_file_count>1 and newrelic.config.isDaily=false and newrelic.config.log_limit_bytes=0 Known issues and workarounds If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream Java New Relic agents to this agent release.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-5100","eolDate":"2023-01-29"},{"agent":"java","date":"2019-05-29","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.1.0/","version":"5.1.0","features":["Support for @PATCH JAX-RS annotation","The agent now sends data to New Relic using gzip compression by default","jdbc-resultset instrumentation is now disabled by default due to overhead"],"bugs":["Scala instrumentation could cause an IllegalArgumentException","Cross Application Tracing headers could be incorrectly parsed","Kafka instrumentation would report WakeupExceptions as errors in New Relic","Fixes a Log4J ClassCastException for applications running on the IBM J9 JVM","The agent now supports using the thread profiler when the send_environment_info configuration is disabled"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements JAX-RS This release adds support for @PATCH JAX-RS annotation. The agent will create and name transactions based @PATCH annotations. Fixes Fixes an issue in the Scala instrumentation that would cause an Java.lang.IllegalArgumentException: to be thrown when the Lightbend Cinnamon agent is in use. Fixes an issue where Cross Application Tracing headers  were incorrectly parsed when Distributed Tracing  is enabled. Applications that use both Distributed Tracing and Cross Application Tracing will no longer report external transaction breakdown metrics. Fixes an issue where the agent’s Kafka instrumentation would report WakeupExceptions as errors in New Relic. These exceptions will no longer be reported. Fixes a Log4J ClassCastException for applications running on the IBM J9 JVM that set a custom logging manager via the -Djava.util.logging.manager system parameter. The agent now supports using the thread profiler  when the send_environment_info configuration  is disabled. Notes The agent now sends data to New Relic using gzip compression by default. To use the previous compression set the compressed_content_encoding configuration value to deflate The jdbc-resultset instrumentation is now disabled by default in the newrelic.yml and will be disabled by default in all future releases. Known Issues Fixed in 5.1.1 gRPC This release contains two bugs in the Java agent's gRPC instrumentation. We highly recommend customers using gRPC instrumentation to upgrade to this and or later agent versions. References to transaction segments were not being removed correctly, which can cause a memory leak The agent could cause the gRPC server listeners to fail to execute its completed and/or cancelled methods, which can cause unexpected behavior","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-510","eolDate":"2022-05-29"},{"agent":"java","date":"2019-04-24","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/5.0.0","version":"5.0.0","features":["gRPC support","Vert.x 3.7 support","OkHttp 3.14.x support","spray-can client support","Support for Derby JDBC 10.15.1.3","Java agent now reports JMX stats for off-heap direct byte buffers","The recordCustomEvent API has been updated"],"bugs":["The agent no longer requires a newrelic.yml even when the `app_name` and `license_key` configuration options are set via environment variables and/or system properties","HttpSessions JMX metrics were not reporting for Websphere Liberty Profile","The transaction_events.max_samples_stored configuration value in the newrelic.yml would incorrectly override the system properties or environment variable values","Applications running on WildFly 12 - 15 would fail start with NoClassDefFound errors","Play applications where external calls inside of future callbacks using async-http-client would not be recorded","Setting log_limit_in_kbytes could result in the agent not logging to the agent log file","Webflux status codes which were not recognized by Spring Webflux caused a 500 status code to be returned"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements gRPC The Java agent now supports gRPC. You will now see transactions , errors , external calls , and distributed traces  for all of your gRPC-based clients and services. Vert.x-3.7 The Java agent now supports Vert.x 3.7. The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions  based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls  made with Vert.x HTTP client. OkHttp 3.14.0 This release adds support for OkHttp 3.14.x. You will now see OkHttp 3.14 calls as external calls  in New Relic. spray-can The Java agent now supports the spray-can client. The agent will now capture outbound http calls made with the spray-can client and report them as external calls  and/or distributed traces . Embedded Derby 10.15.1.3 The Java agent has expanded support for Derby JDBC up to and including version 10.15.1.3. JVM monitoring The Java agent now reports JMX stats for off-heap direct byte buffers. These metrics are available via the JVM page recordCustomEvent API The recordCustomEvent API has been updated to accept Map<String,?> as a second parameter instead of Map<String,Object>, allowing maps such as Map<String,String> to be passed without having to cast the type of the map's value. Fixes The agent no longer requires a newrelic.yml even when the app_name and license_key configuration options are set via environment variables and/or system properties. For more information, see the Java environment variables documentation . HttpSessions JMX metrics were not reporting for Websphere Liberty Profile applications. The transaction_events.max_samples_stored configuration value in the newrelic.yml would incorrectly override the system properties or environment variable values. Applications running on WildFly 12 - 15 would fail start with NoClassDefFound errors for Java agent classes. Play applications where external calls inside of future callbacks using async-http-client would not be recorded. Setting log_limit_in_kbytes would result in the agent not logging to the agent log file if log_file_count was also set to less than 2. Webflux status codes which were not recognized by Spring Webflux caused a 500 status code to be returned and an exception in application logs. Known Issues gRPC: Fixed in 5.1.1 This release contains two bugs in the Java agent's gRPC instrumentation. We highly recommend customers using gRPC instrumentation to upgrade to this and/or later agent versions. References to transaction segments were not being removed correctly, which can cause a memory leak. The agent could cause the gRPC server listeners to fail to execute its completed and/or cancelled methods, which can cause unexpected behavior. Deprecation Notes Self installer The New Relic Java agent's self-installer has been removed in order to provide a more consistent user experience. To install the Java agent, add the full path to the newrelic.jar to the -javaagent flag in your JVM options. For more information on installing the agent on specific application servers , Docker , Maven , or Gradle , see the JVM argument documentation . Deprecated instrumentation The following instrumentation modules have been moved out of the default Java agent, and are now provided as a separate download . To continue using these modules, just add them to the agent's extensions directory  in your newrelic folder or wherever your extensions directory is configured . Akka 2.0 Akka 2.1 Akka-http 1.0 Akka-http 2.0 - 2.4.1 Akka-http 2.4.2 - 2.4.4 Hystrix 1.2 Hystrix 1.3 Play 1 (instrumentation for Play-1.x is not available as an extension.) Play 2.0 Play 2.1 Play 2.2 Solr 3.1 - 3.4 Solr 3.5 Solr 3.6","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-500","eolDate":"2022-04-24"},{"agent":"java","date":"2018-12-18","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.9.0/","version":"4.9.0","features":["The request.uri attribute is now included in Transaction events and corresponding Transaction Error events","Distributed Tracing can now be enabled at the same time as auto app naming","Akka HTTP 10.1.5 and above support"],"bugs":["NullPointerException could occur in Hystrix instrumentation","HttpsURLConnection getInputStream() method could cause some scoped external metrics to be double-counted","Fixes issues preventing agent from connection to an HTTP proxy that does not requires a username or password","Prevents unnecessary dependencies from showing up in the newrelic-agent pom","Fixes deadlocks caused by instrumentation of sun/nio/cs/ classes","Fixes an issue where custom jmx metrics with periods in the attribute name would not get recorded"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements The 'request.uri' attribute is now included in Transaction events and corresponding Transaction Error events. As a result this attribute can now be queried in New Relic. It may be excluded via the exclude list in the attributes section of the yaml config file . It is also excluded when High-security mode is enabled. Distributed Tracing can now be enabled at the same time as auto app naming . Each application created by this setting will share an event reservoir for Distributed Tracing. Updates Akka HTTP instrumentation to support the newest version of Akka HTTP, 10.1.5 and above. Fixes Fixes a possible NullPointerException that could occur in Hystrix instrumentation and propagate into application code. Fixes a bug where usage of the HttpsURLConnection getInputStream() method could cause some scoped external metrics to be double-counted. Fixes an issue that prevents the agent from connecting to an HTTP proxy that does not requires a username or password. When configured to use an HTTP proxy by using proxy_host and proxy_port, the agent would look for proxy_username and proxy_password. If those weren't provided, the agent would use an empty string for proxy_username and proxy_password. Prevents unnecessary dependencies from showing up in the newrelic-agent pom Fixes deadlocks occurring in agent 4.7.0 that were caused by instrumentation of classes in the sun/nio/cs/.* package Fixes an issue where custom jmx metrics with '.'s in the attribute name would not get recorded.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-490","eolDate":"2021-12-18"},{"agent":"java","date":"2018-11-13","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.8.0/","version":"4.8.0","features":[],"bugs":["Agent could break webpage rendering","Transactions were kept alive until they timed out","Agent could stop reporting following a ForceDisconnectException resulting in OutOfMemory Exceptions","Agent now validates that app_names only contains three application names","Long segment times when a custom WSRequestFilter is used that modifies an outbound play-ws request"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixed an issue where the agent would break webpage rendering by inserting New Relic Browser monitoring javascript into the <header> tag of pages which were missing <head> tags. Certain frameworks, like Spring Cloud Gateway, triggered a bug in the Spring webflux instrumentation, causing transactions to stay open until they timed out. This bug resulted in more memory pressure and looked like a memory leak. This has been fixed in this release. Fixed an issue where the agent would stop reporting to New Relic following a ForceDisconnectException and accumulate transaction data resulting in OutOfMemory Exceptions. The agent now validates that app_names only contains three application names. If the agent is configured to report more than three application names, the agent will log a warning message and stop reporting to New Relic. When a custom WSRequestFilter is used that modifies an outbound play-ws request, the agent would report overly long segments due to Segment timeouts and will also result in a loss of External/ metrics. This has been fixed.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-480","eolDate":"2021-11-13"},{"agent":"java","date":"2018-10-03","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.7.0/","version":"4.7.0","features":["Java 11 support","Solr 7.0 JMX Metrics"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Java 11 The New Relic Java agent is now fully compatible with Java 11. For more on JDK releases and the Java agent, see this topic on the Explorers Hub . Solr 7.0 JMX Metrics The Java agent now collects JMX metrics for Solr 7.0","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-470","eolDate":"2021-10-03"},{"agent":"java","date":"2018-09-24","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.6.0/","version":"4.6.0","features":["Spring 5 and WebFlux"],"bugs":["Agent could cause an application deadlock","Agent would not capture JMX Datasource information from Tomcat when JDNI GlobalNamingResources was used"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Spring 5 The Java Agent now provides instrumentation for Spring 5 and Webflux. The agent will name transactions based on router functions as well as Spring controller and spring web annotations. The agent also provides support for Spring WebClient to capture external requests and timing. Spring 5 instrumentation works with Spring Boot, Tomcat, and Jetty.   Note if you have previously disabled Spring instrumentation : There is a new spring-4.3.0 instrumentation module that gets used in place of the previous spring-4.2.0 module for any customers running Spring 4.3.0 and above. If you had previously disabled support for spring-4.2.0 and you are running spring-4.3.0 you will want to change your class_transformer section in your newrelic.yml from: to: Fixes Fixes an issue where the agent could cause an application deadlock when two tokens are created and linked from the other’s thread. This affects users of the New Relic token API and also users of the Hystrix framework. Fixes an issue where the agent would not capture JMX Datasource information from Tomcat when JDNI GlobalNamingResources is used. Known Issues Transaction reporting to New Relic may be delayed by up to 10 minutes when Spring WebClient is used to create http requests that never execute.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-460","eolDate":"2021-09-24"},{"agent":"java","date":"2018-09-04","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.5.0/","version":"4.5.0","features":["Apache HttpAsyncClient","Vert.x 3.5","JBoss EAP 7","Play 2.7","WebSphere Liberty ThreadPool metrics"],"bugs":["OKHttp 3 was not tracking external total time correctly","For some JDBC drivers, the agent would execute additional getMetaData queries","Scala instrumentation could result in incorrect throughput, invalid or negative data in transaction segments, or inability to ignore status codes","play-ws instrumentation could cause ClassNotFound exceptions"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Apache HttpAsyncClient The Java agent now provides instrumentation for Apache HttpAsyncClient 4.1+. You will see your HttpAsyncClient calls as externals in New Relic. AsyncHttpClient The Java agent now provides instrumentation for AsyncHttpClient. You will now see the time spent in external service calls made using AsyncHttpClient in New Relic. If the external service is also running New Relic, you will see cross application tracing (CAT) details as well. Vert.x 3.5 The Java agent now provides visibility into your applications built using the Vert.x 3.5. The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls made with Vert.x HTTP client. JBoss EAP 7 The Java Agent now provides instrumentation for JBoss EAP 7. You will now see the same visibility into your web transactions, app server stats, and frameworks that you have with previous versions of JBoss EAP. Play 2.7 The Java Agent now provides instrumentation for Play 2.7. The previous Java agent release supports versions of Play up to 2.6. WebSphere Liberty Added ThreadPool metrics for WebSphere Liberty Profile. You will now see the active threads in the Threads tab of the JVM metrics page Fixes Fixes an issue where OKHttp 3 was not tracking external total time correctly. Fixes an issue where for some JDBC drivers, the agent would execute additional getMetaData queries.. Fixes an issue with the agent’s Scala instrumentation that could result in incorrect throughput, invalid or negative data in transaction segments, or inability to ignore status codes. Fixes an issue with the play-ws instrumentation that caused ClassNotFound exceptions to occur in the agent logs when withHeaders is used. This could result incomplete transactions and attributes in RPM.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-450","eolDate":"2021-09-04"},{"agent":"java","date":"2018-08-08","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.4.0/","version":"4.4.0","features":["Java 10 suppport","Dropped Java 6 support","Akka 2.5 and Akka HTTP 10.1","Solr 7","WebLogic datasource"],"bugs":["Java agent 4.3.0 would not report data depending on the locale setting of the JVM","Agent could cause significant increase in CPU load","Fixed a ConcurrentModificationException caused by ning instrumentation","Fixed issue with auto app naming and distributed tracing"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Java 10 The New Relic Java agent is now fully compatible with Java 10. For more on JDK release and the Java agent, see this topic on the Explorers Hub . Not compatible with Java 6 In order to continue to innovate and efficiently provide new capabilities to our customers who run on the JVM, this and future agent versions are not compatible with Java 6. If you are running Java 6, you may continue to use Java agent 4.3.0 or lower. For details, see this topic on the Explorers Hub . Akka 2.5 and Akka HTTP 10.1 The Java agent now supports Akka 2.5.x and Akka HTTP 10.1.x. You will see your Akka HTTP calls as New Relic transactions, see the hand-offs between Akka actors, and understand the calls to other databases and services. Solr 7 The Java agent now supports Solr 7.x. New Relic’s Solr support reports database calls to Solr servers as well as monitors the Solr server itself. Known Issue: JMX stats collection for Solr 7 isn't supported as of this release. WebLogic datasource The Java agent now displays health data about WebLogic’s datasource in the Datasource tab under the JVM page. Fixes Fixed an issue where the Java agent 4.3.0 would not report data depending on the locale setting of the JVM. Java Agent 4.3.0 failed to send event data if the JVM locale is set to use a comma as the decimal. You would see NumberFormatException in the agent log. Fixed a rare issue where the agent will incorrectly attempt to continually retransform classes when an extension with a modification date in the future is used, causing a significant increase in CPU load. Fixed a ConcurrentModificationException caused by ning instrumentation that manifests in Mule instrumentation that causes the request it affects to be retried and the Java agent to not report header data. Fixed an issue where if enable_auto_app_naming was set to true and distributed_tracing.enabled was set to true it would sample every distributed trace event. Now if the agent has both configs enabled, it will not turn on distributed tracing.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-440","eolDate":"2021-08-08"},{"agent":"java","date":"2018-07-31","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.3.0/","version":"4.3.0","features":["Distributed tracing","Added proxy_scheme configuration option"],"bugs":["Transaction throughput counts could be artificially inflated when using async servlets in Jersey","JBoss and Wildfly datasources could cause a LinkageError"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Distributed tracing Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before. Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide  before you enable this feature. To enable distributed tracing, set enabled to true in the distributed_tracing section in the newrelic.yml config file. Added configuration option proxy_scheme to allow the agent to connect via https only proxies. Fixes Fixed an issue where transaction throughput counts could be artificially inflated when using async servlets in Jersey. Fixed an issue where JBoss and Wildfly datasources could cause a LinkageError.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-430","eolDate":"2021-07-31"},{"agent":"java","date":"2018-06-12","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.2.0/","version":"4.2.0","features":[],"bugs":["Transactions were being kept alive for too long when application is under heavy GC","Akka routing instrumentation could cause extra memory usage","Bug in Play WS instrumentation where exceptions thrown by instrumentation were propagated out to the application code","Jersey Client and HttpUrlConnection external calls could be double instrumented","Total time and response time for a long running task could be misreported"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Bug fixes Fixed a bug where transactions were being kept alive for too long when application is under heavy GC, causing inaccurate throughput to be reported. Fixed a bug in which Akka routing instrumentation could cause extra memory usage. When this is the case, the transaction throughput will look significantly lower than anticipated. Fixed a rare bug in Play WS instrumentation where exceptions thrown by instrumentation were propagated out to the application code, potentially causing the request to error. Fixed a bug where Jersey Client and HttpUrlConnection could be double instrumented, resulting in inflated external call count. Fixed a bug where the total time and response time for a long running task could be misreported.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-420","eolDate":"2021-06-12"},{"agent":"java","date":"2019-03-27","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.12.1/","version":"4.12.1","features":[],"bugs":["Fixed an issue where an exception would be thrown during agent initialization","Fixed a regression that could cause a NullPointerException","Fixed issue where setting the log_limit_in_kbytes greater than 0 and log_file_count equal to 1 would result in the agent not logging to the agent log file"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixed an issue where an exception would be thrown during agent initialization which caused the application to shut down when the log file is not writable. In previous agent versions there was an undocumented behavior where the agent would log to STDOUT instead. Fixed a regression where a NullPointerException would be logged and instrumentation would not be applied when using an XML extension with comments preceding the instrumentation section. Fixed issue where setting the log_limit_in_kbytes greater than 0 and log_file_count equal to 1 would result in the agent not logging to the agent log file.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-4121","eolDate":"2022-03-27"},{"agent":"java","date":"2019-03-20","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.12.0/","version":"4.12.0","features":["Java 12 support","Supports the kafka-clients library","Added ignoreErrors to the Transaction API","Added new version of addCustomParameters API that accepts a Map","Updated the noticeError API Javadoc to clarify behavior"],"bugs":["Fixed an issue with Jax-RS subresource transaction naming","Fixed a bug in the agent's Jetty metric sampling","Fixed a NullPointerException that can occur when cross application tracing configuration is explicitly disabled","Fixed an issue where transactions would be named incorrectly when using custom Akka Http stream directives or a pathEnd directive followed by a Segment directive","Fixed an issue where certain usages of Akka and Scala would prevent transactions from being reported","The Java agent no longer includes Jaxb or Logback dependencies. A new dependency on Log4j2 has been added."],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Kafka-clients The Java agent now supports the kafka-clients library. The agent will automatically report up Kafka metrics to New Relic. Optional support is provided for reporting Kafka metrics as Insights events and for enabling distributed tracing. More information can be found in the New Relic documentation . Java 12, Coretto and Zulu The New Relic Java agent is now fully compatible with Java 12. This release also adds support for the Amazon Coretto and Azul Zulu JDKs. New APIs Added ignoreErrors()  to the Transaction API, allowing all errors reported within a specific transaction to be ignored. Added addCustomParameters(Map<String, Object>)  API, allowing multiple custom parameters to be added to a transaction at once. Updated the noticeError()  API documentation to clarify that when the api is invoked multiple times while in a transaction, only the first error will be reported. Deprecated APIs The custom transport channel API is now deprecated in favor of the Distributed Tracing  API. The skipTransactionTrace attribute on the @Trace annotation is now deprecated. The excludeFromTransactionTrace  attribute should be used in its place. Deprecated Instrumentation JetS3t Removed built-in instrumentation for JetS3t. The agent will continue to report external calls made with the JetS3t client. Fixes Fixed an issue with Jax-RS subresource transaction naming where the root path is duplicated when a nested resource structure is used. This could lead to transactions being named incorrectly for incoming requests to a Jax-RS framework. Fixed a bug in the agent's Jetty metric sampling that could prevent Jetty specific metrics from being reported when the number of threads returned by JMX is zero. Fixed a NullPointerException that can occur when cross application tracing configuration is explicitly disabled. Fixed an issue where transactions would be named incorrectly when using custom Akka Http stream directives or a pathEnd directive followed by a Segment directive. Fixed an issue where certain usages of Akka and Scala would prevent transactions from being reported to New Relic. This would also manifest as a NullPointerException in the agent log at finest level. The Java agent no longer includes Jaxb or Logback dependencies. A new dependency on Log4j2 has been added","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-4120","eolDate":"2022-03-20"},{"agent":"java","date":"2019-02-12","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.11.0/","version":"4.11.0","features":["Vert.x 3.6","Wildfly 12-15"],"bugs":["Fixed an issue where applications using neo4j bolt JDBC driver could fail to start","The log_daily configuration did not respect documented precedence","Fixed a bug that caused the Spring Webflux instrumentation to fail to apply","Fixed an issue where transactions would not be fully reported if distributed_tracing.enabled=true and cross_application_tracer.enabled=false","Fixed an issue where Akka Http application would not start with the agent attached when using sbt","Fixed an issue where the agent could fail to determine the hostname"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements: Vert.x 3.6 The Java agent now provides visibility into your applications built using the Vert.x 3.6. The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls made with Vert.x HTTP client. Wildfly 12-15 The agent now supports Wildfly versions 12 through 15. Fixes: Fixed an issue where applications using neo4j bolt JDBC driver could fail to start. The log_daily configuration did not respect documented precedence. Fixed a bug that caused the Spring Webflux instrumentation to fail to apply for spring-webflux versions greater than 5.0.*. Fixed an issue where transactions would not be fully reported if distributed_tracing.enabled = true and cross_application_tracer.enabled = false. Fixed an issue where Akka Http application would not start with the agent attached when using sbt. Fixed an issue where the agent could fail to determine the hostname . Known Issues Fixes in 4.12.0 Fixed an issue with Jax-RS subresource transaction naming where the root path is duplicated when a nested resource structure is used. This could lead to transactions being named incorrectly for incoming requests to a Jax-RS framework. Fixed a bug in the agent's Jetty metric sampling that could prevent Jetty specific metrics from being reported when the number of threads returned by JMX is zero. Fixed a NullPointerException that can occur when cross application tracing configuration is explicitly disabled. Fixed an issue where transactions would be named incorrectly when using custom Akka Http stream directives or a pathEnd directive followed by a Segment directive. Fixed an issue where certain usages of Akka and Scala would prevent transactions from being reported to New Relic. This would also manifest as a NullPointerException in the agent log at finest level. The Java agent no longer includes Jaxb or Logback dependencies. A new dependency on Log4j2 has been added. Fixes in 4.12.1 Fixed an issue where an exception would be thrown during agent initialization which caused the application to shut down when the log file is not writable. In previous agent versions there was an undocumented behavior where the agent would log to STDOUT instead. Fixed a regression where a NullPointerException would be logged and instrumentation would not be applied when using an XML extension with comments preceding the instrumentation section. Fixed issue where setting the log_limit_in_kbytes greater than 0 and log_file_count equal to 1 would result in the agent not logging to the agent log file. Fixes in 5.0.0 The agent no longer requires a newrelic.yml even when the 'app_name' and 'license_key' configuration options are set via environment variables and/or system properties. For more details, see [Java agent configuration(]https://docs.newrelic.com/docs/agents/java-agent/configuration/java-agen... ). HttpSessions JMX metrics were not reporting for Websphere Liberty Profile applications. The transaction_events.max_samples_stored configuration value in the newrelic.yml would incorrectly override the system properties or environment variable values Applications running on Wildfly 12 - 15 would fail start with NoClassDefFound errors for Java agent classes. Play applications where external calls inside of future callbacks using async-http-client would not be recorded. Setting log_limit_in_kbytes would result in the agent not logging to the agent log file if log_file_count was also set to less than 2. Webflux status codes which were not recognized by Spring Webflux caused a 500 status code to be returned and an exception in application logs. Fixes in 5.1.0 Fixed an issue in the Scala instrumentation that would cause an Java.lang.IllegalArgumentException: to be thrown when the Lightbend Cinnamon agent is in use. Fixed issue where cross application tracing headers  were incorrectly parsed when distributed tracing  is enabled. Applications that use both distributed tracing and cross application tracing will no longer report external transaction breakdown metrics. Fixed an issue where the agent’s Kafka instrumentation would report WakeupExceptions as errors in New Relic. These exceptions will no longer be reported. Fixed a Log4J ClassCastException for applications running on the IBM J9 JVM that set a custom logging manager via the -Djava.util.logging.manager system parameter. The agent now supports using the thread profiler  when the send_environment_info configuration  is disabled. Fixes in 5.2.0 Fixed an issue where very long-running transactions with a large number of segments  would cause an excessive amount of memory usage. The agent will no longer trace segments once the segment_limit  has been reached. Fixes in 5.3.0 Akka-http instrumentation would name transactions incorrectly when using an asynchronous onComplete callb…","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-4110","eolDate":"2022-02-12"},{"agent":"java","date":"2019-01-23","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.10.0/","version":"4.10.0","features":["Adds Transaction event attributes that provide context between your Kubernetes cluster and services","The Java agent now supports setting all configuration options via Environment variables","Adds instrumentation for the Akka HTTP client, versions 10.0 to 10.1.x","Support for MySQL connector 8.0.x","Adds support for Akka Http 10.1.6","Span event attributes can now be filtered using include/exclude rules","Rename transaction trace segment parameter key from uri to http.url and rename trace key from database_name to db.instance"],"bugs":["Fixes an issue where Akka HTTP instrumentation can cause higher than normal memory usage"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements This release adds Transaction event attributes that provide context between your Kubernetes cluster and services. For details on the benefits (public beta coming soon) see this blog post . The Java agent now supports setting all configuration options via Environment variables. Environment variables will take precedence over newrelic.yml but cannot be updated dynamically since they are read statically on application startup. Adds instrumentation for the Akka HTTP client, versions 10.0 to 10.1.x. This client is used via the Http().singleRequest() method and the agent will now automatically capture these requests as External metrics. Support for MySQL connector 8.0.x Adds official support for Akka Http 10.1.6 Span event attributes can now be filtered using include / exclude rules. Rename transaction trace segment parameter key from uri to http.url and rename trace key from database_name to db.instance. Fixes Fixes an issue where Akka HTTP instrumentation can cause higher than normal memory usage when an async Directive is used in the route for an Akka HTTP based app. This can also result in mis-named transactions for any paths underneath the custom Directive.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-4100","eolDate":"2022-01-23"},{"agent":"java","date":"2018-05-02","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.1.0/","version":"4.1.0","features":["Configuration for custom_insights_events.max_samples_stored format in YAML has been changed","The agent will log a warning message when it detects that the java.endorsed.dirs property is used"],"bugs":["Ensure that custom events added during a transaction do not get discarded if the transaction is ignored","Addresses cases where the agent could not parse database statements that included the IGNORE and INTO keywords"],"security":["Addresses security issue with PostgreSQL"],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Configuration for custom_insights_events.max_samples_stored format in YAML has been changed. For agents 4.1.0 and above, the old .yml config setting will be ignored, which will result in the agent defaulting to max samples stored of 10,000 custom events. When you update your agent, please migrate to the new format: The agent will log a warning message when it detects that the java.endorsed.dirs property is used. Classes in these directories cannot be instrumented by the agent because they are loaded by the bootstrap classloader. Fixes Ensure that custom events added during a transaction do not get discarded if the transaction is ignored via a call to NewRelic.ignoreTransaction(). A security update that corrects an issue affecting PostgreSQL that could occur if High-security mode was enabled (or record_sql was set to off) and a query ran slow enough to trigger an explain plan. If the above conditions were met the agent may not have properly stripped out all information from the query. For information on this fix, see the security bulletin . Addresses cases where the agent could not parse database statements that included the IGNORE and INTO keywords.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-410","eolDate":"2021-05-02"},{"agent":"java","date":"2018-04-19","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.0.1/","version":"4.0.1","features":[],"bugs":["Fixes an issue Introduced in 3.48.0 with event sampling"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixes an issue Introduced in 3.48.0 with event sampling. The agent would only report the first max_samples_stored  events in a given minute reporting period and disregard the remainder for that minute. With the fix, the agent randomly samples those events across the reporting period.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-401","eolDate":"2021-04-19"},{"agent":"java","date":"2018-04-04","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/4.0.0/","version":"4.0.0","features":["Removed the SSL configuration option","Minimum version required for use in EU data center"],"bugs":["Thread profiler could cause a StackOverflowError exception"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Removed the SSL configuration option: SSL is now always used in communication with New Relic servers. The newrelic.yml ssl configuration and -Dnewrelic.config.ssl system property are no longer used. Setting either value to anything other than true will result in logging a warning. Minimum version required for use in EU data center. Fixes Fixes an issue where the thread profiler  could fail to report. In this case, the agent logged a java.lang.StackOverflowError.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-400","eolDate":"2021-04-04"},{"agent":"java","date":"2014-07-31","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.9.0/","version":"3.9.0","features":["Support for new Cross Application Trace map","Support for RabbitMQ","Support for SOAP over CXF","Absolute maximum for max_samples_stored lifted"],"bugs":["Enable Cross Application Tracing for all valid uses of HttpURLConnection","Allow setting the logback.ContextSelector system property","Wrong Application name in App Map when Auto App Naming is enabled"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version New Features Support for new Cross Application Trace map This release enhances cross application tracing with the new trace map  visualization of your app's cross application calls. The new visualization helps you spot bottlenecks in external services within transaction traces  and gives you an end-to-end understanding of how the transaction trace is used by other applications and services. This leads to faster problem diagnosis and better collaboration across teams. All agents involved in the cross application communication must be upgraded  to see the complete graph. You can view cross application traces in the transaction trace drill-down . Support for RabbitMQ You can now see messages sent to and received from RabbitMQ 2.7.0 or higher. The time spent processing a dequeued message is shown as a Message transaction. Support for SOAP over CXF In this release, we provide automated instrumentation of your SOAP calls when using CXF 2.7. Improvements Absolute maximum for max_samples_stored lifted In previous versions of the agent, max_samples_stored could not be set to more than 10000. This restriction has been lifted, which can help avoid sampling. Fixes Enable Cross Application Tracing for all valid uses of HttpURLConnection Prior to this, certain uses of HttpURLConnection between two New Relic apps would fail to be recognized as Cross Application Traces and instead show up as external calls. Allow customers to set the system property logback.ContextSelector Prior to this fix, the agent would throw a ClassNotFoundException when the system property logback.ContextSelector was set. Wrong Application name in App Map when Auto App Naming is enabled When the enable_auto_app_naming config setting is set to true, the auto-named apps are incorrectly identified as the default app in the App Map.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-390","eolDate":"2017-07-31"},{"agent":"java","date":"2014-07-28","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.8.2/","version":"3.8.2","features":[],"bugs":["Instrumentation missing including browser monitoring","Missing metrics with Java 2 Security","Agent could stop reporting transactions","Agent not reporting external services in Play 2.3"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixed: Instrumentation missing including browser monitoring There was a bug in the agent that caused several instrumentation modules to not be loaded. This bug occurred when no extensions directory existed or the extensions directory was empty. This fix will allow auto-RUM to report normally. This bug was introduced in 3.8.0. Fix: Missing metrics with Java 2 Security When Java 2 Security was enabled, the agent failed to report some metrics. This bug was introduced in 3.8.0. Fix: Agent could stop reporting transactions For Jetty applications, the agent could stop reporting transactions if an uncaught exception was thrown. This bug was introduced in 3.6.0. Fix: Agent not reporting external services in Play 2.3 The Java Agent was not reporting calls to external services.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-382","eolDate":"2017-07-28"},{"agent":"java","date":"2014-07-10","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.8.1/","version":"3.8.1","features":[],"bugs":["EJB application transaction metrics reporting correctly for WebLogic","App Map incomplete"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Notes Fix: EJB application transaction metrics reporting correctly for WebLogic In version 3.8.0 of the agent, EJB application transaction metrics for WebLogic were reporting the data as the average value per a bean instead of the total value per an application. This has been fixed and the data can now be found under the JVM tab. Fix: App Map incomplete If a web request made an external call to another app, the app making the web request did not appear in the App Map. Moreover, subsequent external calls to other apps did not appear in the App Map either.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-381","eolDate":"2017-07-10"},{"agent":"java","date":"2014-06-30","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.8.0/","version":"3.8.0","features":["Experimental support for Java SE 8","Support for Hibernate 4.3"],"bugs":["Cross-Application Tracing didn't trace when caller used WLS 11g and SOAP","Old DocumentationBuilderFactory can cause agent to disable itself","Agent not detecting async servlets in WebSphere 8.x"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Notes Experimental support for Java SE 8 This version includes experimental support for Java 8. Code that is known to work with Java SE 8 and compiled for Java 6 or 7 (such as Tomcat 8, Play Framework 2.3, etc) should work fine. We would like your feedback if you run into any trouble running code compiled for Java SE 8. Please only try this in non-production environments. We are eager for your feedback as we work to make Java 8 support production-ready. To enable Java SE 8 compatibility, set the following system property on your system: -Dnewrelic.enable.java.8 Support for Hibernate 4.3 The Java agent now reports details on calls to Hibernate 4.3 as well as previous versions. Fix: Cross-Application Tracing didn't trace when caller used WLS 11g and SOAP. In Oracle WebLogic Server 11g, cross-application tracing (CAT) failed for external calls originating in the default SOAP pipeline, producing an exception in the log. This bug has been fixed. Fix: Old DocumentationBuilderFactory can cause agent to disable itself When using a DocumentBuilderFactory implementation compiled with Java 1.4 or below an abstract method error was being thrown, causing the agent to disable itself. Fix: Agent not detecting async servlets in WebSphere 8.x The Java Agent was not detecting the call to AsyncContext.complete(), so it was not reporting async servlet calls.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-380","eolDate":"2017-06-30"},{"agent":"java","date":"2014-06-11","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.7.2/","version":"3.7.2","features":["Support for Play 2.3"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Notes Support for Play 2.3 The Java Agent now provides full support for Play 2.3. In particular, transaction naming is based on the controller action.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-372","eolDate":"2017-06-11"},{"agent":"java","date":"2014-06-03","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.7.1/","version":"3.7.1","features":[],"bugs":["NewRelic.setRequestAndResponse API call was not backward-compatible","NewRelic.setRequestAndResponse can cause LinkageError","ignoreTransaction attribute ignored","Auto-RUM failed to add the New Relic header script to JSP pages","Naming of CGLib classes","Agent works properly inside a folder with + in the path"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Notes Fix: NewRelic.setRequestAndResponse API call was not backward-compatible Implementation classes of the com.newrelic.api.agent.Request and com.newrelic.api.agent.Response interfaces compiled with a pre-3.5.0 version of newrelic-api.jar threw a java.lang.AbstractMethodError when used with a 3.5.0 or higher version of the Agent. Fix: NewRelic.setRequestAndResponse can cause LinkageError For some app servers, calling NewRelic.setRequestAndResponse API caused a java.lang.LinkageError: loader constraint violation Fix: ignoreTransaction attribute ignored The ignoreTransaction=\"true\" attribute in custom xml had no effect. The transaction was not ignored even with \"true\" set. Fix: In rare cases, Auto-RUM failed to add the New Relic header script to JSP pages. Fix: Naming of CGLib classes Improved the fix in 3.7.0 for excluding the random part from the name of CGLib generated class. Fix: Agent works properly inside a folder with + in the path Improved the fix in 3.7.0 for a directory path with a + character.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-371","eolDate":"2017-06-03"},{"agent":"java","date":"2014-05-20","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.7.0/","version":"3.7.0","features":["Flexible capturing of attributes","Agent-Side High Security Configuration","Discovery of hostname reported to New Relic","Improved JMX metric naming","Improved Jetty coverage"],"bugs":["Naming of CGLib classes","JMS transaction naming","Potential memory leak from database calls","VerifyError can occur when using Nevado JMS"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Notes Flexible capturing of attributes The Java agent offers the ability to fine tune the attributes being sent to New Relic. Please see our docs site for more information on configuring attributes: https://docs.newrelic.com/docs/java/java-agent-attributes Agent-Side High Security Configuration If your account is set to high security in the New Relic UI, you must add the following to your local newrelic.yml configuration file: Without this property, the agent will stop collecting data when high security is enabled in the New Relic UI. See https://docs.newrelic.com/docs/subscriptions/high-security Discovery of hostname reported to New Relic If New Relic reports an IP address for your hostname, you can now control whether the host name is an IP version 4 or 6 address by setting the following property in your newrelic.yml configuration file: Improved JMX metric naming You can now set the metric name when configuring JMX metrics through a custom yaml file using the property \"root_metric_name\". Note, all of the JMX metrics will still be prefixed with \"JMX\" and end with the name of the attribute. See https://docs.newrelic.com/docs/java/custom-jmx-yaml-examples Fix: Naming of CGLib classes CGLib auto generated classes with Spring resulted in poor metric names. The agent now excludes the random part from the name. Fix: JMS transaction naming JMS onMessage instrumentation now uses a lower priority for naming transactions and honors the enable_auto_transaction_naming config. Improved Jetty coverage Jetty versions 9.04 through 9.06 were not instrumented. This has been fixed. Fix: Potential memory leak from database calls In some cases when database work is performed outside of a New Relic transaction, a memory leak could occur. This bug has been present in the agent since 3.5.0. Fix: VerifyError can occur when using Nevado JMS.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-370","eolDate":"2017-05-20"},{"agent":"java","date":"2014-04-24","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.6.0/","version":"3.6.0","features":["Enhanced XML for custom instrumentation"],"bugs":["Agent could cause VerifyError","Embedded Jetty instrumentation","Exceptions incorrectly reported","Embedded Tomcat not reporting JMX Builtin metrics","Apache HttpClient 4.3 not consistently reported","RESTEasy transactions","JBoss 7 port not reported correctly","Auto-RUM bug","Errors not reporting with some versions WebSphere 7.0","Agent works properly inside a folder with + in the path","Agent HttpClient logging","Inconsistent State with Play 1.2.x","Invalid errors for Stripes","Hanging threads in the Agent with SQL Prepared Statements","Request queue time was incorrect for some versions of nginx","XML entity expansion with non-SSL connection to New Relic","Agent can cause application thread to hang"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Notes Enhanced XML for custom instrumentation The custom XML xsd has been enhanced to support the instrumentation of interfaces, subclasses, and method annotations. These enhancements give you much more flexibility to identify transactions and add monitoring of components without changes to your source code. Fix: Agent could cause VerifyError In specific cases, the agent could cause verification errors. Fix: Embedded Jetty instrumentation Starting with the 3.3.1 agent, transactions were not reported for some configurations of embedded Jetty. Fix: Exceptions incorrectly reported In some cases exceptions were reported even if configured to be ignored. Fix: Embedded Tomcat not reporting JMX Builtin metrics In newer versions of embedded Tomcat the agent wasn't collecting JMX metrics properly. Fix: Apache HttpClient 4.3 not consistently reported The Java agent now instruments Apache HttpClient 4.3 calls, including the new call patterns introduced in 4.3. Fix: RESTEasy transactions In certain instances, transactions between applications were not getting linked correctly when RESTEasy was used. Fix: JBoss 7 port not reported correctly The port was not reported correctly for some JBoss users. Fix: Auto-RUM bug Starting in version 3.5.0 of the Java agent, in rare cases Auto-RUM could cause the New Relic footer script to be placed within a script tag. Fix: Errors not reporting with some versions WebSphere 7.0 In some Fix Packs of WebSphere 7.0, the agent did not report errors properly. Fix: Agent works properly inside a folder with + in the path The Java agent did not initialize properly when in a folder with a + character in the pathname. Fix: Agent HttpClient logging The Agent's HttpClient was writing to the app server's log when it discovered a log4j appender. Fix: Inconsistent State with Play 1.2.x In some cases the agent was logging an \"Inconsistent state!\" message and not reporting a transaction. Fix: Invalid errors for Stripes The Agent was erroneously reporting spurious 404 errors for web apps using Stripes. Fix: Hanging threads in the Agent with SQL Prepared Statements Under rare circumstances, threads could hang in the Agent when an application with multiple threads made heavy use of SQL Prepared Statements. Fix: Request queue time was incorrect for some versions of nginx Nginx fractional second header values for queue and server start times are now parsed correctly. Fix: XML entity expansion with non-SSL connection to New Relic Fixed an XML entity expansion vulnerability that only occurs when the agent is configured with ssl: false; the default is true. The agent already has other protection against unauthorized entity expansion. This fix is an additional layer of protection. Fix: In rare case, agent can cause application thread to hang Under rare circumstances, an application thread could hang when an application with multiple threads made heavy use of SQL Prepared Statements.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-360","eolDate":"2017-04-24"},{"agent":"java","date":"2014-03-27","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.5.1/","version":"3.5.1","features":[],"bugs":["Auto-RUM bug","Agent stops reporting","Occasionally missed web transaction when using ResultSet","X-Ray Sessions bugs"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: Auto-RUM bug Starting in version 3.5.0 of the Java agent, in rare cases Auto-RUM could cause the New Relic header to be placed within a script tag. This bug has been fixed. Fix: In rare cases, agent stops reporting In rare cases, the Java Agent hung on socketRead while performing an SSL handshake and would not report data until JVM restart. This bug has been fixed. Fix: Occasionally missed web transaction when using ResultSet In version 3.5.0 of the agent some transactions that use a JDBC ResultSet were missing in the UI. The agent log would show an \"Inconsistent State\" error. This bug has been fixed. Fix: X-Ray Sessions bugs. X-Ray Sessions sometimes returned no transaction traces. A memory leak with X-Ray Sessions when many sessions were run was also fixed.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-351","eolDate":"2017-03-27"},{"agent":"java","date":"2014-03-05","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.5.0/","version":"3.5.0","features":["WildFly 8.0 support"],"bugs":["PostgreSQL explain plan bug","SQL parameter obfuscation didn't work if the parameter value contained a newline","Agent no longer supports obfuscation of individual fields","Agent could fail to reconnect to New Relic","Transaction name specified in XML configuration was being ignored","Jetty 9.1 transactions were not showing up in 3.3.x or higher agents","Websphere 7.0 was not being instrumented","Solr tabs in UI not always appearing"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 New Relic supports WildFly 8.0 The Java Agent now provides instrumentation for WildFly 8.0. You will see the same great visibility into your web transactions, app server stats, and frameworks that you have with previous versions of JBoss. Fix: PostgreSQL explain plan bug Fixes PostgreSQL bug that allowed parameters to be sent in explain plans under some circumstances. Parameters are now masked prior to sending when explain plans are enabled (explain_enabled: true) and record_sql is set to 'obfuscated'. Fix: SQL parameter obfuscation didn't work if the parameter value contained a newline The record_sql: obfuscated config setting did not properly mask parameters when it included a newline character. This bug has been fixed. Agent no longer supports obfuscation of individual fields Previous versions of the agent allowed an obfuscated_sql_fields option to select specific field names to obfuscate when record_sql: raw. We have discovered rare cases in which this feature would not mask SQL parameters correctly, so we have removed the configuration option. Now, if obfuscated_sql_fields is set, the setting of record_sql: raw is ignored and _all_ fields are masked. Fix: In some cases, an agent could fail to reconnect to New Relic Fixed several issues that in rare cases could cause the agent to cease reporting data until JVM restart. Fix: Transaction name specified in XML configuration was being ignored In some cases transaction names set in XML files in the extensions folder were being ignored. This bug has been fixed in this release. Fix: Jetty 9.1 transactions were not showing up in 3.3.x or higher agents Starting with the 3.3.1 agent, customers were not seeing transactions from Jetty 9.1. This bug has been fixed. Fix: Websphere 7.0 was not being instrumented Starting in agent version 3.3.0, WebSphere 7.0 was not being instrumented. This bug has been fixed. Fix: Solr tabs in UI not always appearing If you are running a Solr application and not seeing any tabs, please update to this version.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-350","eolDate":"2017-03-05"},{"agent":"java","date":"2018-03-12","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.48.0/","version":"3.48.0","features":["Tomcat, WebSphere Liberty, or Resin now have data source information available","CompletableFuture instrumentation is more efficient","Disabling SSL connections to New Relic has been deprecated. SSL connections are enabled by default."],"bugs":["Fixed an issue that in rare cases prevented Play async transaction tracking","Fixed a memory leak that could occur in Spymemcached instrumentation","Fix to disable attributes.include lists when High-security mode is enabled","Fixed an issue where errors outside of a transaction did not contain custom attributes on the event","Fixed an issue that caused the UI to not display errors that had error messages over 255 bytes"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Customers using Tomcat, WebSphere Liberty, or Resin now have data source information available. Data source information includes the number of active and idle connections, as well as the maximum possible connections. This information can be seen under the Data Source tab on the JVMs page CompletableFuture instrumentation is more efficient Disabling SSL connections to New Relic has been deprecated. SSL connections are enabled by default. In a future release, the option to disable SSL will be removed. Bug fixes Fixed an issue that in rare cases prevented Play async transaction tracking Fixed a memory leak that could occur in Spymemcached instrumentation Fix to disable attributes.include lists when High-security mode is enabled Fixed an issue where errors outside of a transaction did not contain custom attributes on the event Fixed an issue that caused the UI to not display errors that had error messages over 255 bytes","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3480","eolDate":"2021-03-12"},{"agent":"java","date":"2018-03-07","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.47.1/","version":"3.47.1","features":[],"bugs":[],"security":["A security update corrects an issue where the agent may report DB query results to New Relic or re-issue an SQL statement"],"supportedOperatingSystems":null,"description":"Download this agent version Bug fixes A security update corrects an issue where the agent may report DB query results to New Relic or re-issue an SQL statement. For information on the bug fix, see the security bulletin . Known Issues Fixes in 3.48.0 Fixes an issue that in rare cases prevented Play async transaction tracking Fixes a memory leak that could occur in Spymemcached instrumentation Fix to disable attributes.include lists when High-security mode is enabled Fixes an issue where errors outside of a transaction did not contain custom attributes on the event Fixes an issue that caused the UI to not display errors that had error messages over 255 bytes Fixes in 4.0.0 Fixes an issue where the Thread Profiler could fail to report. In this case, the agent logged a java.lang.StackOverflowError Fixes in 4.1.0 Ensure that custom events added during a transaction do not get discarded if the transaction is ignored via a call to NewRelic.ignoreTransaction(). A security update that corrects an issue affecting PostgreSQL that could occur if High-security mode was enabled (or record_sql was set to off) and a query ran slow enough to trigger an explain plan. If the above conditions were met the agent may not have properly stripped out all information from the query. For information on this fix, see the security bulletin. Fixes an issue where the agent could not parse database statements that included the IGNORE and INTO keywords. Fixes in 4.2.0 Fixes a bug where transactions were being kept alive for too long when application is under heavy GC, causing inaccurate throughput to be reported. Fixes a bug in which Akka routing instrumentation could cause extra memory usage. When this is the case, the transaction throughput will look significantly lower than anticipated. Fixes a rare bug in Play WS instrumentation where exceptions thrown by instrumentation were propagated out to the application code, potentially causing the request to error. Fixes a bug where Jersey Client and HttpUrlConnection could be double instrumented, resulting in inflated external call count. Fixes a bug where the total time and response time for a long running task could be misreported. Fixes in 4.3.0 Fixes an issue where transaction throughput counts could be artificially inflated when using async servlets in Jersey. Fixes an issue where JBoss and Wildfly datasources could cause a LinkageError. Fixes in 4.4.0 Fixes an issue where the Java agent 4.3.0 would not report data depending on the locale setting of the JVM. Java Agent 4.3.0 failed to send event data if the JVM locale is set to use a comma as the decimal. You would see NumberFormatException in the agent log. Fixes a rare issue where the agent will incorrectly attempt to continually retransform classes when an extension with a modification date in the future is used, causing a significant increase in CPU load. Fixes a ConcurrentModificationException caused by ning instrumentation that manifests in Mule instrumentation that causes the request it affects to be retried and the Java agent to not report header data. Fixes an issue where if enable_auto_app_naming was set to true and distributed_tracing.enabled was set to true it would sample every distributed trace event. Now if the agent has both configs enabled, it will not turn on distributed tracing. Fixes in 4.5.0 Fixes an issue where OKHttp 3 was not tracking external total time correctly. Fixes an issue where for some JDBC drivers, the agent would execute additional getMetaData queries.. Fixes an issue with the agent’s Scala instrumentation that could result in incorrect throughput, invalid or negative data in transaction segments, or inability to ignore status codes. Fixes an issue with the play-ws instrumentation that caused ClassNotFound exceptions to occur in the agent logs when withHeaders is used. This could result incomplete transactions and attributes in RPM. Fixes in 4.6.0 Fixes an issue where the agent could cause an application deadlock when two tokens are created and linked from the other’s thread. This affects users of the New Relic token API and also users of the Hystrix framework. Fixes an issue where the agent would not capture JMX Datasource information from Tomcat when JDNI GlobalNamingResources is used. Fixes in 4.7.0 None Fixes in 4.8.0 Fixed an issue where the agent would break webpage rendering by inserting New Relic Browser monitoring javascript into the <header> tag of pages which were missing <head> tags. Certain frameworks, like Spring Cloud Gateway, triggered a bug in the Spring webflux instrumentation, causing transactions to stay open until they timed out. This bug resulted in more memory pressure and looked like a memory leak. This has been fixed in this release. Fixed an issue where the agent would stop reporting to New Relic following a ForceDisconnectException and accumulate transaction data resulting in OutOfMemory Exceptions. The agent now validates that app_names only contains three application names. I…","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3471","eolDate":"2021-03-07"},{"agent":"java","date":"2018-02-05","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.47.0/","version":"3.47.0","features":["Instrumentation for Jersey Client versions 1.x and 2.x","request.uri is collected as an agent attribute"],"bugs":["Fixes a bug in Jersey 2 instrumentation where external segments could time out","Agent may have incorrectly reported the transaction thread name to New Relic as New Relic Token Expiration Handler","Agent was incorrectly bundling javax.xml and jregex packages","Wildfly instrumentation could cause async servlet transactions to go unreported"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Jersey Client The agent now provides instrumentation for Jersey Client versions 1.x and 2.x. You will see your calls using the Jersey Client APIs as Externals in New Relic, whether you are using the synchronous or reactive client API. request.uri collected as an agent attribute You can now control the collection of request.uri on errors and transaction Traces you would other attributes. For more information on agent attributes see here . Fixes Fixes a bug in Jersey 2 instrumentation where external segments could time out, causing an abnormally large \"total time\" for a transaction. This bug would occur if a client disconnected while being sent a response or if an unstable network is in place where an IOException occurs during response. In some cases, the agent may have incorrectly reported the transaction thread name to New Relic as \"New Relic Token Expiration Handler\". Agent was incorrectly bundling javax.xml and jregex packages Fixes an issue in the Wildfly instrumentation that could cause async servlet transactions to go unreported.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3470","eolDate":"2021-02-05"},{"agent":"java","date":"2018-01-08","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.46.0","version":"3.46.0","features":["Support for Websphere 9 Traditional and Liberty Profile servers"],"bugs":["Fixes a potential deadlock scenario caused by the Java agent in high throughput applications running on Vert.x","Usage of the setNull method on the JDBC interface now reports up null in the query string sent to New Relic, instead of incorrectly reporting up the sqlType as the value","Fixes a JVM crash that can occur when running the Java agent with the non-default spring-aop-2 instrumentation enabled"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Websphere 9 With this release, the Java agent now supports Websphere 9, both Traditional and Liberty Profile. More information on how to install and configure the Java agent on Websphere can be found here: IBM WebSphere Application Server . Bug Fixes Fixes a potential deadlock scenario caused by the Java agent in high throughput applications running on Vert.x. Usage of the setNull() method on the JDBC interface now reports up null in the query string sent to New Relic, instead of incorrectly reporting up the sqlType as the value. Fixes a JVM crash that can occur when running the Java agent with the non-default spring-aop-2 instrumentation enabled.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3460","eolDate":"2021-01-08"},{"agent":"java","date":"2017-12-11","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.45.0","version":"3.45.0","features":["RabbitMQ 5.0 support"],"bugs":["Exceptions thrown within scala Future/CallbackRunnable code could cause inaccurate transaction times","Deadlock could occur when tracking asynchronous activity in Vert.x"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements RabbitMQ The agent now provides instrumentation for RabbitMQ 5.0. Note: This release changes instrumentation for all supported versions of RabbitMQ to use the exchange name instead of routing keys for the transaction name and produce/consume metrics. This should provide more meaningful transaction names, but will change what transactions you see in New Relic. Now reports queue purge No longer reports misleading MessageBroker consume metric for callbacks/message listeners Adds message properties to tracer attributes, and a configuration to disable them: Bug Fixes Exceptions thrown within scala Future/CallbackRunnable code could cause inaccurate transaction times Deadlock could occur when tracking asynchronous activity in Vert.x.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3450","eolDate":"2020-12-11"},{"agent":"java","date":"2017-11-07","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.44.1","version":"3.44.1","features":[],"bugs":["Fixes an issue where an Akka HTTP 10.x application could fail at runtime with a NullPointerException"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Note If you are using Akka Http 10.x, use this 3.44.1 release rather than 3.44.0. Bug Fixes Fixes an issue where an Akka HTTP 10.x application could fail at runtime with a NullPointerException.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3441","eolDate":"2020-11-07"},{"agent":"java","date":"2017-11-06","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.44.0","version":"3.44.0","features":["This release contains a bug that could cause an Akka HTTP 10 app to fail at runtime with a NullPointerException. It is recommended to use a newer version.","Supports Play 2.6, Akka HTTP 10, and Scala 2.12","Lowers overhead for Play, Akka, and Scala and introduses the scala_futures_as_segments config option"],"bugs":["Tomcat could cause a ClassFormatException error at startup","High-throughput applications with daily logging enabled and a specified log limit could cause log files to grow without bound","The agent could leak memory when instrumenting the Ning Async Http Client","Akka HTTP content type was not reported"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Known Issue This release contains a bug that could cause an Akka HTTP 10 app to fail at runtime with a NullPointerException. Please use version 3.44.1  instead. Improvements Supports Play 2.6, Akka HTTP 10, and Scala 2.12. The agent now provides instrumentation for Play 2.6.x. It also provides instrumentation for Akka HTTP 10. It supports Scala 2.12.x, so Play and Akka HTTP transactions show full detail, including async activity using Scala Promises and Futures. Lowers overhead for Play, Akka, and Scala. This agent release imposes lower overhead for applications that use Play, Akka, and Scala. The reduction in overhead will be most notable in lightweight applications and microservices. Unlike previous versions of the agent, by default the agent will not report Scala Futures as transaction segments, and those Futures will not contribute to the transaction’s reported Total Time. For most customers, this change will provide more concise information in transaction trace details, with no loss of insight. If those segments are valuable to you, and you are willing to incur higher overhead, you can enable that instrumentation with the following setting: Bug Fixes The 3.43.0 version of the agent caused Tomcat to report a ClassFormatException error at startup. The error did not affect the application or agent. High-throughput applications with daily logging enabled and a specified log limit could cause log files to grow without bound. The agent could leak memory when instrumenting the Ning Async Http Client. Akka HTTP content type was not reported.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3440","eolDate":"2020-11-06"},{"agent":"java","date":"2017-09-27","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.43.0/","version":"3.43.0","features":["Java 9 support"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Java 9 The Java agent can now be run with Oracle Java SE 9 ! You can run your applications on the Java 9 runtime JVM, and run applications compiled at the Java 9 language level. By default, this release of New Relic's Java agent does not support applications configured for the new Java 9 modular mode, such as Jigsaw. In order to run in this mode with the agent, your application must be configured to require the java.sql module through one of these two options: Add requires java.sql; to your module-info.java class Use the --add-modules=java.sql command line flag","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3430","eolDate":"2020-09-27"},{"agent":"java","date":"2017-08-28","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.42.0","version":"3.42.0","features":["Supports Hystrix version 1.5","Improved metadata collection for cloud providers"],"bugs":["Fixed bug that caused agent to not report error rate metrics","Improved Hystrix transaction reporting to better handle cases where an Observable is created that never executes","Fixed an issue where JAX-RS subresources would not be picked up for transaction naming","Fixed a bug with DataNucleus that was preventing instance level and query information from being picked up","Fixed a bug that caused the agent to report external calls made with Commons HTTPClient as unknown host"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Hystrix With this release, the Java agent now supports Hystrix version 1.5. Improved metadata collection for cloud providers The agent now collects additional metadata when running in AWS, GCP, Azure, and PCF. This information is used to provide an enhanced experience when the agent is deployed on those platforms. Bug Fixes Fixed bug that caused agent to not report error rate metrics. The UI would show application errors, but error rate would show up as 0%. This was introduced in 3.38.0. Improved Hystrix transaction reporting to better handle cases where an Observable is created that never executes. Fixed an issue where JAX-RS subresources would not be picked up for transaction naming, resulting in an incorrect or incomplete transaction name. Fixed a bug with DataNucleus that was preventing instance level and query information from being picked up. Fixed a bug that caused the agent to report external calls made with Commons HTTPClient as \"unknown host\". Known Issues Fixed in 3.44.0 High-throughput applications with daily logging enabled and a specified log limit could cause log files to grow without bound. The agent could leak memory when instrumenting the Ning Async Http Client. Akka HTTP content type was not reported. Fixed in 3.46.0 In rare cases, a Vert.x application running this version of the agent can deadlock. Usage of the setNull() method on the JDBC interface now reports up null in the query string sent to New Relic instead of incorrectly reporting up the sqlType as the value. JVM crash that can occur when running the Java agent with the non-default spring-aop-2 instrumentation enabled.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3420","eolDate":"2020-08-28"},{"agent":"java","date":"2014-01-23","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.4.2/","version":"3.4.2","features":[],"bugs":["Solr caches and Solr updates data not appearing","JVM tab thread pool, session, and transaction data not appearing"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: Solr caches and Solr updates data not appearing Starting with version 3.4.1, Solr caches and updates were not appearing in the UI. This bug has been fixed. Fix: JVM tab thread pool, session, and transaction data not appearing Starting with version 3.4.1, some data was not appearing under the JVM tab. This bug has been fixed.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-342","eolDate":"2017-01-23"},{"agent":"java","date":"2017-07-25","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.41.0/","version":"3.41.0","features":["Vert.x toolkit versions 3.3.0 through 3.4.2","Slick 3.2","Added ExtendedRequest API class to report content-length for HTTP responses"],"bugs":["Fixed bug in Netty instrumentation that cause erroneous reporting of NettyDispatcher transactions","Fixed bug that caused agent to not report error rate metrics"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Vert.x The Java agent now provides visibility into your applications built using the Vert.x toolkit (supported versions 3.3.0 through 3.4.2). The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls made with Vert.x HTTP client. Slick With this release, the Java agent now supports Slick 3.2 API Added ExtendedRequest API class to report content-length for HTTP responses. See Transaction.setWebResponse API  for more details. Bug fixes Fixed bug in Netty instrumentation that cause erroneous reporting of NettyDispatcher transactions. This affected transactions responding large incoming requests. Fixed bug that caused agent to not report error rate metrics. The UI would show application errors, but error rate would show up as 0%. This was introduced in 3.38.0.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3410","eolDate":"2020-07-25"},{"agent":"java","date":"2014-01-21","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.4.1/","version":"3.4.1","features":[],"bugs":["In some cases, Play 2.2 didn't report transactions","Improved performance when instrumented code is not running in a transaction"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: In some cases, Play 2.2 didn't report transactions When a chain of promises resolved, specifically using Future.flatMap(), lingering promises prevented the transaction from completing, in which case the transaction wouldn't be reported for the app. This is now tracked correctly. Fix: Improved performance when instrumented code is not running in a transaction Avoids unnecessary work when code instrumented by the Java agent is not running in the scope of a transaction.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-341","eolDate":"2017-01-21"},{"agent":"java","date":"2017-06-26","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.40.0/","version":"3.40.0","features":["DynamoDB","Support for Solr versions 6.5.0+"],"bugs":["Fixed an instrumentation gap that prevented agent from capturing instance-level information about database queries for non-blocking IO driver configurations","Fixes an issue where usage onCompleted handler(s) with the ning async http client could cause a transaction to end too early"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements DynamoDB\nThe Java agent now provides visibility into your applications’ usage of DynamoDB when using the client versions 1.11.106 and greater. You will see the calls in the application breakdown, in trace details, on the Databases page, in Transaction maps, and in Service maps. Solr\nWith this release, the java agent now supports Solr versions 6.5.0+. Bug Fixes: Fixed an instrumentation gap that prevented agent from capturing instance-level information about database queries for non-blocking IO driver configurations. Fixes an issue where usage onCompleted handler(s) with the ning async http client could cause a transaction to end too early, resulting in missed instrumentation.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3400-0","eolDate":"2020-06-26"},{"agent":"java","date":"2014-01-16","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.4.0/","version":"3.4.0","features":["Additional functionality to API call addCustomParameter"],"bugs":["Java agent should honor enable_auto_app_naming","Setting configuration properties in newrelic.yml configuration file","Java agent should honor JAX-RS annotations with New Relic annotations","Play transaction does not complete until timeout expires"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: Java agent should honor enable_auto_app_naming Starting with Java agent 3.3.1, the enable_auto_app_naming flag was being ignored. This bug has been fixed. Fix: Setting configuration properties in newrelic.yml configuration file. Starting with version 3.0, some properties such as max_stack_trace_lines could not be set in the newrelic.yml configuration property. This bug has been fixed. Fix: Java agent should honor JAX-RS annotations with New Relic annotations New Relic's Java agent should handle methods that contain a New Relic annotation along with a JAX-RS annotation correctly. Previously the New Relic annotation was being ignored. Fix: Play transaction does not complete until timeout expires New Relic's Java agent now handles firstCompletedOf to Futures correctly. Additional functionality to API call addCustomParameter New Relic's API call addCustomParameter will now add the custom parameters to New Relic. For more information, see http://newrelic.com/software-analytics","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-340","eolDate":"2017-01-16"},{"agent":"java","date":"2017-05-30","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.39.1","version":"3.39.1","features":[],"bugs":["Fixed an issue in which the agent could send a raw SQL query as a transaction attribute when an error was thrown"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes: Fixed an issue in which the agent could in rare cases send a raw SQL query as a transaction attribute when an error was thrown","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3391","eolDate":"2020-05-30"},{"agent":"java","date":"2017-05-23","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.39.0","version":"3.39.0","features":[],"bugs":["Fixed an issue in which setting agent_enabled to false in newrelic.yml caused an IncompatibleClassChangeError","Agent throws an exception if null keys or values are passed to the recordCustomEvent API","Agent throws a NullPointerException in the application during JDBC calls","VerifyError is thrown in the application code when using Spring or JAX-RS annotations on a Kotlin method with a default parameter","Fixed an issue where external HTTP metrics could be reported outside of a transaction when using HttpURLConnection"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Bug fixes Fixed an issue in which setting \"agent_enabled\" to false in newrelic.yml caused an IncompatibleClassChangeError in the application on startup. The agent can now be disabled without side-effect. Fixed an issue where the agent throws an exception if null keys or values are passed to the recordCustomEvent() API. The agent now ignores these null values. Fixed a rare issue where the agent throws a NullPointerException in the application during JDBC calls. The agent now reports these calls but may report an “Unknown” database. Fixed an issue where a VerifyError is thrown in the application code when using Spring or JAX-RS annotations on a Kotlin method with a default parameter. Fixed an issue where external HTTP metrics could be reported outside of a transaction when using HttpURLConnection. The agent now ignores these calls.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3390","eolDate":"2020-05-23"},{"agent":"java","date":"2017-04-24","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.38.0/","version":"3.38.0","features":["Expected Errors feature","A path to a custom SSL certificate bundle can now be specified in the agent configuration using ca_bundle_path"],"bugs":["Tomcat could see duplicated or misnamed transactions for async endpoints","Transactions could be reported with an inflated apdex","Fixed a bug where the loaded class count on the JVM tab is reported as a much larger value than the actual number of loaded classes","Response times in ServletRequestListener.requestInitialized would incorrectly appear much larger than the actual values when using JBoss"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Expected Errors\nThis release provides you with several flexible error configuration options to control how your errors are reported. With this addition, you can now configure certain exceptions that you expect your application logic will throw. These “expected errors” will not be counted towards your application error rate and Apdex; you will only be alerted on errors that truly affect the health of your application.\nExpected errors can be configured by exception class or HTTP response code. When specifying an exception class, you can provide an error message to match. See the documentation  for details. Custom CA Bundle A path to a custom SSL certificate bundle can now be specified in the agent configuration by using the following top level configuration: Fixes Fixed a bug where applications running on Tomcat could see duplicated or misnamed transactions for async endpoints. Fixed a bug that caused transactions to report with an inflated apdex. The affected transactions had to meet the following conditions: A status code >= 400 No error set on the transaction markResponseSent() or addOutboundHeaders() was not called from the API\nIn this case, the agent will now consider that transaction call to be frustrating for the purposes of calculating apdex. Fixed a bug where the loaded class count on the JVM tab is reported as a much larger value than the actual number of loaded classes. In certain circumstances this bug can cause memory and CPU over-utilization. Fixed a bug where response times in ServletRequestListener.requestInitialized() would incorrectly appear much larger than the actual values when using JBoss.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3380","eolDate":"2020-04-24"},{"agent":"java","date":"2017-03-29","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.37.0/","version":"3.37.0","features":["New APIs for instrumenting asynchronous work","Adds support for OkHttp 3.6.x"],"bugs":["Applications running on Tomcat 8.5 could see duplicated or misnamed Transactions for async endpoints","Users of Spring AOP can get an UndeclaredThrowableException","Fixes root and current working directory jars not showing up in the UI","Fixes an issue which prevented the Solr updates and Solr caches tabs from displaying in the New Relic UI"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Async APIsThis release adds new APIs for instrumenting asynchronous work. If your transactions have asynchronous work (such as database queries or external calls) that is not automatically monitored by the Java Agent, you can use the APIs to link that work to your transactions. For more information, see the documentation . OkHttp 3.6This release adds support for OkHttp 3.6.x. You will now see OkHttp 3.6 calls as external calls in New Relic. Fixes Fixes an issue where applications running on Tomcat 8.5 could see duplicated or misnamed Transactions for async endpoints. Fixes an edge case issue where users of Spring AOP can get an UndeclaredThrowableException when using the Java Agent. Fixes root and current working directory jars not showing up in the UI. Fixes an issue which prevented the Solr updates and Solr caches tabs from displaying in the New Relic UI for applications that are reporting Solr data for the first time.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3370","eolDate":"2020-03-29"},{"agent":"java","date":"2017-02-15","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.36.0/","version":"3.36.0","features":["New agent APIs for custom instrumentation of frameworks, messaging systems, database calls, and external calls","Support for Solr versions 5 and 6"],"bugs":["Fixes a bug that prevents an application from starting up when a JAX-RS annotated method contains more than 8 parameters","Fixes an issue that affected Spring and JAX-RS applications compiled with the Java 8 flag javac -parameters","Fixes bug that affected applications implementing JAX-RS endpoints using static methods","The agent now reports WildFly dispatcher name and version","Fixes a bug in which Queue Time could be misreported on the Overview page","Fixes an issue in which custom Hystrix Commands that are subclassed multiple times in Groovy cause an application to throw an exception on startup"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements APIs This release adds a number of APIs  that will allow you to instrument and get expanded visibility into frameworks, libraries, and any custom code that New Relic does not automatically instrument. In addition to instrumenting your web frameworks, you can also instrument calls to and from messaging systems, database calls, and external calls ! By passing context about your code to the APIs, you will get the same reporting, including cross application tracing, that you get with New Relic’s built-in instrumentation. Solr This release adds support for Solr versions 5 and 6 (up to and including version 6.3.0). Fixes Fixes a bug that prevents an application from starting up when a JAX-RS annotated method contains more than 8 parameters. Fixes an issue that affected Spring and JAX-RS applications compiled with the Java 8 flag javac -parameters. The issue would cause the application to throw a java.lang.reflect.MalformedParametersException exception. Fixes bug that affected applications implementing JAX-RS endpoints using static methods. The agent now reports WildFly dispatcher name and version. Fixes a bug in which Queue Time could be misreported on the Overview page for customers injecting the X-Queue-Start or X-Request-Start HTTP headers. This fix brings the Java Agent into compliance with the behavior of other New Relic Agents. Fixes an issue in which custom Hystrix Commands that are subclassed multiple times in Groovy cause an application to throw an exception on startup.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3360","eolDate":"2020-02-15"},{"agent":"java","date":"2017-01-17","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.35.2","version":"3.35.2","features":[],"bugs":["Fixes an issue where an application can fail to start with a VerifyError when using Spring AOP, Jersey, or any JAX-RS framework"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Note If you are using Spring AOP, Jersey, or any JAX-RS framework, use this 3.35.2 release rather than 3.35.0 or 3.35.1. Fixes Fixes an issue where an application can fail to start with a:\njava.lang.VerifyError: Bad local variable type error\nwhen using Spring AOP, Jersey, or any JAX-RS framework with Java Agent 3.35.0 or 3.35.1.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3352","eolDate":"2020-01-17"},{"agent":"java","date":"2017-01-12","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.35.1","version":"3.35.1","features":["This release contains a bug that could cause the app to fail with a VerifyError. It is not advised to use this version."],"bugs":["Fixes an issue where an application can fail to start with a ClassFormatError when using Spring, Jersey, or any JAX-RS framework"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Known Issue This release contains a bug that could cause the app to fail with a VerifyError. Please use version 3.34.0  instead. We will release a fix for the issue when we have thoroughly tested the fix for edge cases. Fixes Fixes an issue where an application can fail to start with a ClassFormatError when using Spring, Jersey, or any JAX-RS framework with Java Agent v3.35.0.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3351","eolDate":"2020-01-12"},{"agent":"java","date":"2017-01-11","downloadLink":null,"version":"3.35.0","features":["Several customers have reported an issue with this release in which the app fails with a ClassFormatError. For this reason, this release is not recommended and has been removed from New Relic's download site","JAX-RS/Jersey 2","OkHttp 3.5"],"bugs":["Fixes an edge case in Spray Client instrumentation where a NullPointerException was being thrown","Fixes a potential StackOverflowException from Netty instrumentation","Fixes a bug that prevented display of JMX metrics for Oracle WebLogic Server 12.2","Fixes issue where SQL parsing would throw a StackOverflowError","Improve performance of complex SQL statement parsing"],"security":[],"supportedOperatingSystems":null,"description":"Improvements Known Issue Several customers have reported an issue with this release in which the app fails with a ClassFormatError. For this reason, this release is not  recommended and has been removed from New Relic's download site. Please use release 3.34.0 instead. We keep the note here because the 3.35.0 is still available on the Maven Central Repository. We will release a fix for the issue as soon as possible. Changes JAX-RS/Jersey 2 This agent release officially adds support for JAX-RS 1.1-2.0. The release instruments the @Suspend annotation when using the Jersey 2 implementation of JAX-RS. OkHttp 3.5 This release updates our instrumentation to cover OkHttp 3.5. Fixes Fixes an edge case in Spray Client instrumentation where a NullPointerException was being thrown into customer logs Fixes a potential StackOverflowException from Netty instrumentation when calling ServerBootstrap.bind() many times Fixes a bug that prevented display of JMX metrics for Oracle WebLogic Server 12.2 Fixes issue where SQL parsing would throw a StackOverflowError and prevent large database statements from being sent up to New Relic Improve performance of complex SQL statement parsing in the agent, reducing overhead for apps that make many SQL calls","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3350","eolDate":"2020-01-11"},{"agent":"java","date":"2016-12-14","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.34.0/","version":"3.34.0","features":["Database instance information for Solr","IBM JDK 8 Support"],"bugs":["Asynchronous instrumentation could interact with instrumentation for JDBC ResultSet or a limited set of other frameworks, leading to loss of transaction reporting","Fixed an issue in which transactions that executed the Spring Framework error handler could be given a generic name","The X-Ray sessions feature could cause the Agent to stop reporting transactions","Fixed a bug in the agent that prevented Error Events from linking to corresponding Traced Errors when created outside of a transaction","Fixed a Tomcat-specific issue where Transactions would incorrectly report extremely long response times","Improved metric grouping issues in several frameworks including Akka tell calls","Fixed bug in noticeError API","Fixed an issue where custom XML instrumentation could cause a null pointer exception","Agent API method recordCustomEvent could cause loss of custom events created using this API"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Solr The agent now reports database instance information for Solr. With the additional database instance information , transaction traces and slow query traces will provide the database server and database name for the queries displayed. IBM JDK 8 Support The newest versions of WebSphere Application Server and WebSphere Liberty Profile ship with the IBM JDK 8. This release is compatible with IBM JDK 8. Fixes Fixed an issue in which asynchronous instrumentation could interact with instrumentation for JDBC ResultSet or a limited set of other frameworks, leading to loss of transaction reporting. Fixed an issue in which transactions that executed the Spring Framework error handler could be given a generic name. These transactions will now retain their previously-assigned name. Fixed a bug introduced in 3.33.0 where use of the X-Ray sessions feature could cause the Agent to stop reporting transactions. Fixed a bug in the agent that prevented Error Events from linking to corresponding Traced Errors when created outside of a transaction Fixes a Tomcat-specific issue where Transactions would incorrectly report extremely long response times in the ServletRequestListener.requestInitialized() method. Improved metric grouping issues in several frameworks including Akka tell calls. Fixed bug in noticeError API. The agent now includes custom attributes in errors when the API is called outside a Transaction. Fixed an issue where custom XML instrumentation could cause a null pointer exception in application code when custom attributes are set for a method that passes a null parameter. Fixed an issue in the Agent API method recordCustomEvent() that could cause loss of custom events created using this API. Customer who do not use the recordCustomEvent() API are not affected. Previously, unexpected argument types could result in the loss of both the event and additional custom events recorded in the same 1-minute period. As a result of this fix, users of the recordCustomEvent API may discover that events that have never been visible in the Insights API become visible. Known issues Fixed in 3.35.2 Applications that use the Spray Client instrumentation may throw a NullPointerException into customer logs Applications that use the Netty instrumentation may get a StackOverflowException when calling ServerBootstrap.bind() many times Oracle WebLogic Server 12.2 applications will not display WebLogic specific JMX metrics SQL parsing may throw a StackOverflowError and prevent large database statements from being sent up to New Relic Fixed in 3.36.0 Queue Time may be misreported on the Overview page for applications injecting the X-Queue-Start or X-Request-Start HTTP headers Applications that have custom Hystrix Commands that are subclassed multiple times in Groovy can cause an application to throw an exception on startup Fixed in 3.37.0 Solr: Applications that use Solr and have reported to New Relic APM previously with an agent version prior to 3.34.0 will not display the Solr page","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3340","eolDate":"2019-12-14"},{"agent":"java","date":"2016-11-02","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.33.0/","version":"3.33.0","features":["Database instance reporting"],"bugs":["Fixed a bug in Play 2.5 instrumentation that could cause the agent to report shorter response times when using Action.async","SQL stored procedure names are now reported","Fixed an issue where explain plans were not being executed for versions 9.0-9.3 of PostgreSQL","Fixed an issue where the agent could cause a Mule application request to fail","Fixed an issue where JVM versions that do not support ThreadCpuTime() would throw an UnsupportedOperationException","Fixed a potential memory leak in versions of Jetty 7 and 8 when using CometD","Fixed an issue where the Hystrix toObservable method was double counting metrics"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Database instance reporting The agent now reports database instance information  for most supported databases. With the additional database instance information, transaction traces and slow query traces will provide the database server and database name for the queries displayed. You will see instance-level information when connecting by using the following drivers: Any JDBC driver, including those in our compatibility doc . DataStax Cassandra driver (2.1.2, 3.0 to 3.1). Jedis Redis driver (1.4 to 2.9). Mongo (2.12.0 to 2.13.3, 3.1 to 3.3). Spymemcached (2.11 to 2.12). Note that instance-level information is not reported for calls to the getBulk API method.. Bug fixes Fixed a bug in Play 2.5 instrumentation that could cause the agent to report shorter response times when using Action.async. SQL stored procedure names are now reported in more edge cases such as “exec @param = stored_procedure” Fixed an issue where explain plans were not being executed for versions 9.0-9.3 of PostgreSQL. Fixed an issue where the agent could cause a Mule application request to fail with a NotSerializableException reported in the application log. Fixed an issue where JVM versions that do not support ThreadCpuTime() would throw an UnsupportedOperationException, preventing the JVM from starting. Fixed a potential memory leak in versions of Jetty 7 and 8 when using CometD. Fixed an issue where the Hystrix toObservable method was double counting metrics on newer versions of Java 7 and all versions of Java 8.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3330","eolDate":"2019-11-02"},{"agent":"java","date":"2016-09-19","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.32.0/","version":"3.32.0","features":["Support for WebLogic versions 12.2.x","Improvements in Java agent startup time"],"bugs":["Fixed bug in spymemcached instrumentation that would incorrectly name segments","Improved Play 2.5 instrumentation","Fixed a bug that could cause cross application tracing to display URLs as Unknown in transaction traces","Fixed a bug in Jetty 9.3 instrumentation where transactions were not reported and memory was leaked"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements WebLogic This release adds official support for WebLogic versions 12.2.x Performance Improvements Improvements in Java agent startup time, particularly on modular ClassLoader architectures (such as JBoss) Fixes: Fixed bug in spymemcached instrumentation that would incorrectly name segments in transaction traces  that contained “get-and-touch” operations. Improved Play 2.5 instrumentation Fixed memory leak for large POST requests. Fixed incorrect response times. Previously, large uploads could cause inflated response times. The agent now tracks PlayRequestHandler and no longer shows the short-lived NettyDispatcher transactions. Fixed a bug that could cause cross application tracing to display URLs as “Unknown” in transaction traces  when the URL did not include the port number. Fixed a bug in Jetty 9.3 instrumentation where transactions were not reported and memory was leaked if an incoming async request was wrapped by a framework or Jetty itself.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3320","eolDate":"2019-09-19"},{"agent":"java","date":"2014-01-10","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.3.2/","version":"3.3.2","features":[],"bugs":["Duplicate annotation exception","WildFly VerifyError"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: Duplicate annotation exception In some rare cases involving generated a proxy class, the application may encounter an exception AnnotationFormatError: Duplicate annotation for class That bug has been fixed in this version. Fix: VerifyError In certain cases such as the Wildfly app server, the application may encounter a VerifyError. That bug has been fixed in this version.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-332","eolDate":"2017-01-10"},{"agent":"java","date":"2016-08-10","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.31.1/","version":"3.31.1","features":[],"bugs":["Fixed a bug that caused a StackOverflow exception for drivers that execute a query on Connection.getMetaData"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixed a bug that caused a StackOverflow exception for drivers that execute a query on Connection.getMetaData(). Note:  This issue was introduced in Java agent version 3.30.0 .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3311","eolDate":"2019-08-10"},{"agent":"java","date":"2016-08-03","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.31.0/","version":"3.31.0","features":["Mule ESB 3.6-3.8 including the new HTTP Connector","OkHttp client 3.0-3.4","Akka HTTP 2.4.5","Spring transaction naming"],"bugs":["Fixed an issue that was preventing Jetty JMX threads metrics from being pulled","Fixed bug in the recordMetric API","Fixed a memory leak in the Async Servlet instrumentation","Fixed a bug in the setRequestAndResponse API"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Mule ESB 3.6-3.8 including the new HTTP Connector This release adds instrumentation for Mulesoft Mule ESB Server versions 3.6-3.8, including the new HTTP Connector  made available in Mule 3.6. This release continues to support the old HTTP Transport. Mule ESB Server instances will appear as \"dispatchers\" on the overview page  and the JVM metrics page . Requests to an HTTP (operation-based) Connector will show in New Relic as web transactions. All of the usual features of New Relic APM are supported including alerting, error reporting, JMS puts and takes, cross application tracing, transaction traces, key transactions, external services, and database call reporting. OkHttp client 3.0-3.4 This release adds instrumentation for OkHttp client for versions 3.0-3.4. Both synchronous and asynchronous calls are supported, as well as the usual features for HTTP clients in New Relic APM such as cross application tracing  and the external services  page. Akka HTTP 2.4.5 The Java agent now reports and names transactions received through Akka HTTP 2.4.5, in addition to previously available Akka HTTP support. Spring transaction naming The java agent now supports naming transactions based on the path element of Spring RequestMapping annotation. Fixes Fixed an issue that was preventing Jetty JMX threads metrics from being pulled in later versions of Jetty 9.X. Fixed bug in the recordMetric API  that in rare cases could start an unwanted long running transaction. Fixed a memory leak in the Async Servlet instrumentation. Fixed a bug in the setRequestAndResponse API  that could throw a java.lang.NumberFormatException in the customer’s application when the circuit breaker trips.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3310","eolDate":"2019-08-03"},{"agent":"java","date":"2014-01-07","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.3.1/","version":"3.3.1","features":["JMS Messaging","Grails 1.3.7 to 2.3.x","Updated instrumentation for supported app servers"],"bugs":["New Relic did not instrument Apache HttpClient 4.3","Java Agent failed on Weblogic with a certicate exception","Java Agent suppressed application logging","Java Agent was logging error messages regarding weaved classes","Text instructions in the sample newrelic.yml file were improved"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 JMS Messaging New Relic now gives you insight into the performance of your JMS message processing, both incoming and outgoing messages. New Relic now shows transactions initiated via JMS 1.1 message receipt. These transactions show up in the New Relic UI as background tasks of type \"Message\". In addition, JMS 1.1 message creation is shown in transaction traces. Grails 1.3.7 to 2.3.x New Relic now provides first-class visibility into your Grails applications. Grails web transactions are now named based on the Grails controller. The transactions track the details of your calls to JDBC, Hibernate, and other important frameworks, and provides full access to the New Relic Java agent API from Groovy. Grails installation instructions can be found here Updated instrumentation for supported app servers New Relic has updated the instrumentation of the application servers we support. In the process, we have updated the list of app servers that we instrument. For a current list of supported app server versions, see https://docs.newrelic.com/docs/java/new-relic-for-java Fix: New Relic did not instrument Apache HttpClient 4.3 Previous versions of the agent did not instrument HttpClient 4.3.x. That version is now properly supported. Fix: Java Agent failed on Weblogic with a certicate exception In some cases running Weblogic, the Java Agent would fail certificate validation when connecting to New Relic. That bug has been fixed. Fix: Java Agent suppressed application logging In version 3.2.3, the Java agent sometimes suppressed application logging. That bug has been fixed in this version. Fix: Java Agent was logging error messages regarding \"weaved classes\" In version 3.2, the Java agent wrote innocuous error messages to its log similar to the following: ERROR: javax/servlet/ServletOutputStream is marked as a weaved class, but no methods are matched to be weaved. That bug has been fixed in this version. Fix: Text instructions in the sample newrelic.yml file were improved If you are upgrading from a previous version of the agent, consider applying your configuration to this new version of the yml file.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-331","eolDate":"2017-01-07"},{"agent":"java","date":"2016-07-20","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.30.1/","version":"3.30.1","features":[],"bugs":[],"security":["Fixed a security issue that could send external HTTP request parameters to New Relic via transaction traces"],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixed a security issue that could send external HTTP request parameters to New Relic via transaction traces  for applications that do all of the following: Use Java agent 3.6.0 or higher* Use Apache HttpClient 4.0 or higher Haven’t disabled transaction_traces *For Java agent versions 3.6.0-3.25.0, this issue only affects cross-application traces . Recommended for applications that may include sensitive information in external service call request parameters. If you can’t upgrade the agent immediately, there are a few workarounds: Disable transaction traces Disable only cross-application tracing . This resolves the issue with Java agents prior to 3.26.0. You can also delete existing transaction traces .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3301-1","eolDate":"2019-07-20"},{"agent":"java","date":"2016-06-28","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.30.0/","version":"3.30.0","features":["Mule ESB 3.4 - 3.6","Play 2.5","Cassandra async 2.1.2+ and 3.x","Async Http Client 2.x","Transaction traces for key transactions","JDBC performance and overhead improved"],"bugs":["Fixed multiple issues related to Java Agent logging","Fixed a bug where transactions could timeout during agent harvest","Resolved Metric grouping issue in Spray/Akka instrumentation","ClassCircularityError could be induced by the agent when running with a custom security manager","Fixed issue where a database connection can get labeled as JDBC instead of the more specific database name"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Mule ESB 3.4 - 3.6 This release adds instrumentation for Mulesoft Mule ESB Server versions 3.4 through 3.6. Requests to an HTTP Transport will show in New Relic as web transactions. Mule ESB Server instances will appear as \"dispatchers\" on the overview page  and the JVM metrics page . All of the usual features of New Relic APM are supported including alerting, error reporting, JMS puts and takes, cross application tracing, transaction traces, key transactions, external services, and database call reporting. NOTE: The newer HTTP operation-based Connector is not yet supported. Play 2.5 This release adds instrumentation for the Play 2.5 framework. The previous Java Agent release supports versions of Play up to 2.4. Cassandra async 2.1.2+ and 3.x This release adds instrumentation for asynchronous queries in versions 2.1.2+ and 3.x of the Datastax Cassandra driver, including slow query  support. You’ll see relevant breakdowns in the overview chart, entries on the Databases page, and segments in transaction traces. Async Http Client 2.x This release adds instrumentation for external service  calls made using Async Http Client versions 2.x. If the called external service is also running New Relic, you will see cross application tracing  details as well. This instrumentation will also capture external calls made from Play WSAPI (which uses Async Http Client). Transaction traces for key transactions If you set an Apdex value for a key transaction , the agent will now capture transaction traces based on that key transaction's Apdex value  if it's smaller than the application’s Apdex value . JDBC performance and overhead improved This release offers better performance and lower overhead of JDBC instrumentation, especially in situations with large numbers of connections. Fixes: Fixed multiple issues related to Java Agent logging including: ClassCastExceptions thrown into customer application logs Agent logging being diverted into customer application logs Fixed a bug where transactions could timeout during agent harvest, resulting in missing metrics and logging: \"Traced activity timed out after 600 seconds. The traced_activity_timeout configuration parameter can be used to adjust this timeout.” Resolved Metric grouping issue  in Spray/Akka tell instrumentation. The agent now names temporary actors \"temp\". In rare cases a ClassCircularityError could be induced by the agent when running with a custom security manager. Fixed issue where a database connection can get labeled as \"JDBC\" instead of the more specific, supported database type such as \"MySQL\" or \"PostgreSQL\". This issue specifically affects customers running with a proxying or delegating JDBC connection.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3300","eolDate":"2019-06-28"},{"agent":"java","date":"2016-05-24","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.29.0/","version":"3.29.0","features":["JDBC instrumentation improvements","Instrumentation for the Cassandra Datastax 3.0 Driver including slow query support"],"bugs":["Fixed a bug which caused some applications that use Play and Ning AsyncHttpClient to miss transactions","Fixed an issue which would cause the thread profiler to not report data while profiling some Scala classes","Fixed a bug where a RuntimeException is thrown during class transformation","Fixed a bug where Tomcat ClassLoaders could leak memory when using a JDBC driver bundled in your application"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements JDBC instrumentation JDBC ResultSet instrumentation performance has been improved. Instrumentation has been added for: i-Net Merlia 7.0.3 database driver Generic JDBC drivers Cassandra This release adds instrumentation for the Cassandra Datastax 3.0 Driver including slow query support. You’ll see relevant breakdowns in the overview chart, entries in the Databases tab, and segments in transaction traces. Note:  Uses of the client's async API are not currently supported. Fixes: Fixed a bug which caused some applications that use Play and Ning AsyncHttpClient to miss transactions. Fixed an issue which would cause the thread profiler to not report data while profiling some Scala classes. Fixed a rare bug where a RuntimeException is thrown during class transformation which can prevent some instrumentation from being applied. Fixes a rare case where Tomcat ClassLoaders could leak memory when using a JDBC driver bundled in your application after reloading a web application.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3290","eolDate":"2019-05-24"},{"agent":"java","date":"2016-04-20","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.28.0/","version":"3.28.0","features":["Slow query tracking for Cassandra","Synchronous calls for MongoDB Java driver 2.14","Apache Tomcat 8.5","Support for Akka forwarding and Akka broadcasting","Support for additional JDBC drivers"],"bugs":["Fixed a bug that could cause Akka Http instrumentation to throw a NullPointerException","Fixed a bug in the Spymemcached instrumentation that would report operations with the name None instead of the correct operation name","Fixed a bug that could cause highly asynchronous applications to experience a memory leak"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Cassandra This release adds slow query tracking  to Cassandra queries made via the Datastax driver. You’ll now see slow CQL queries on the Databases page  and within Transaction Traces. You must add the following to your newrelic.yml configuration  to enable this feature in High-security mode : MongoDB The Java agent now reports synchronous calls made via MongoDB Java driver 2.14. You will see MongoDB represented on the Overview page, on the Databases page, and in Transaction traces. Note: The asynchronous driver is not yet supported. Apache Tomcat This release adds support for Tomcat 8.5 Akka This release adds support for Akka forwarding and Akka broadcasting. The agent will now trace messages broadcast or forwarded to actors. When the system sends a message to an Actor, the agent now reports the name of the actor system that sent the message. Previously, the agent reported “deadletters” under these circumstances. Async performance This release adds performance enhancements for asynchronous frameworks, especially Hystrix. Performance in Hystrix will noticeably improve for most applications, and will be up to 3x faster when tracing low-latency requests (response time <3ms). Performance for low-latency Play applications will be up to 30% faster. JDBC This release adds support for the following JDBC drivers: MySQL 6.0.2 and higher i-Net Oranxo 3.06 i-Net MERLIA 8.04.03 and 8.06 Fixes Fixed a bug that could cause Akka Http instrumentation to throw a NullPointerException into customer code. Fixed a bug in the Spymemcached instrumentation that would report operations with the name “None” instead of the correct operation name. Fixed a bug that could cause highly asynchronous applications to experience a memory leak in the NewRelic TransactionService.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3280","eolDate":"2019-04-20"},{"agent":"java","date":"2016-03-30","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.27.0/","version":"3.27.0","features":["Spymemcached client versions 2.11 to 2.12","JDBC Drivers","Added command_parser config"],"bugs":["Fixed an issue where the agent treated HTTP headers as being case sensitive","Fixed an issue where error data could be dropped","Fixed a bug in spray-http and akka-http routing libraries","Fixed various issues related to the proper handling of multibyte character encoding","Fixed a bug that could cause the Thread Profiler to time out","Fixed a bug when making SQL queries from an asynchronous framework"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Spymemcached The Java agent now provides visibility into your applications’ usage of Memcached when using the Spymemcached client versions 2.11 to 2.12. You will see the calls in the application breakdown, in trace details , on the Databases page , in Transaction maps , and in Service maps . JDBC Drivers This release adds support for the following JDBC drivers: INet Oracle Driver (Oranxo) 3.14 Sybase (jConnect) JDBC 3 driver Fixes Fixed an issue where the agent treated HTTP headers as being case sensitive, causing CAT to miss under certain conditions. Fixed an issue where error data could be dropped, causing 413 status code errors to be reported in the agent log. Fixed a bug in spray-http and akka-http routing libraries where response times and/or route names could be reported incorrectly when using Futures within the route. Fixed various issues related to the proper handling of multibyte character encoding. Fixed a bug in Java agent version 3.26.x that could cause the Thread Profiler to time out. Fixed a bug where an error could get printed to the agent log when making SQL queries from an asynchronous framework. Notes In support of an upcoming feature, the Java agent is now capable of reporting class metadata including class method signatures, method annotations, class annotations, field annotations, field types, and field names. This reporting is on by default and can be explicitly disabled in the agent by setting the property in your newrelic.yml configuration file:","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3270","eolDate":"2019-03-30"},{"agent":"java","date":"2016-02-25","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.26.1/","version":"3.26.1","features":["Adds improved support for PostgreSQL 8.0+ with jdbc3+"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements PostgreSQL This release adds improved support for PostgreSQL 8.0+ with jdbc3+. All of these versions now include support for explain plans.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3261","eolDate":"2019-02-25"},{"agent":"java","date":"2016-02-23","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.26.0/","version":"3.26.0","features":["The agent now identifies external calls when Spray Client is used","The agent now tracks Futures started in Spray routes","The agent now identifies transactions when spray-can is used without spray-routing","The agent now tracks async activity created by Typesafe/Lightbend's functional-relational-mapper, Slick","JDBC instrumentation now provides more consistent and complete data for supported JDBC drivers"],"bugs":["Fixed a bug where CXF would name transactions based on auto-generated proxy classes","Fixed a bug in EJB instrumentation that could cause a NullPointerException","Fixed a bug where the EJB instrumentation erroneously set transaction names","Fixed a bug in the Cross Application Tracing API that caused Application Response time to be attributed to other transaction time","Fixed a bug in request queueing calculations where queueing time could show up as a steadily increasing value","Fixed a bug that prevented HttpURLConnection External metrics from reporting on the IBM J9 JVM","With Spray routing, fixed a bug that incorrectly set the transaction name of similar route names","Fixed a bug where some transaction traces would report external segments for non I/O calls in Apache HttpClient","The Java Agent will now read Cross Application Tracing HTTP header names regardless of case","Fixed a bug that could cause cross application tracing between the New Relic Java Agent and non-Java New Relic Agents to fail"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Spray Client The agent now identifies external calls when Spray Client is used. You will see your Spray Client calls with the hostname and port of the destination. The calls also have support for Cross Application Tracing, and are shown in Service Maps and Transaction Maps. The agent now tracks Futures started in Spray routes. The agent now identifies transactions when spray-can is used without spray-routing. Slick The agent now tracks async activity created by Typesafe/Lightbend's functional-relational-mapper, Slick. If the underlying database driver is supported by the agent the database activity will be traced. Improvements for JDBC The Java agent’s JDBC instrumentation now provides more consistent and complete data for supported JDBC drivers. The Java agent supports the following drivers: MySQL 5.1.4 - 5.1.x PostgreSQL 8.2-504 - 9.4-1206 (jdbc4 and jdbc41 drivers only) Oracle ojdbc14, ojdbc5, ojdbc6, ojdbc7 Microsoft SQLServer 2.0 - 4.2 jTDS 1.2 - 1.3.x DB2 9.1 - 10.x Derby 10.6.1.0 - 10.x H2 1.0.x - 1.4.x HSQL 1.7.2.2 - 2.x MariaDB 1.1.7 - 1.3.x Note  Previous versions of the Java Agent had partial “generic” support for other JDBC drivers. The new, improved JDBC instrumentation replaces the “generic” JDBC instrumentation. Fixes Fixed a bug where CXF would name transactions based on auto-generated proxy classes. The agent now normalizes CXF transaction names. Fixed a bug in EJB instrumentation that could cause a NullPointerException in application code. Fixed a bug where the EJB instrumentation erroneously set transaction names. In this version, the agent records a metric. Fixed a bug in the Cross Application Tracing API that caused Application Response time to be attributed to other transaction time, and prevented linking of transaction traces when doing CAT. Fixed a bug in request queueing calculations where queueing time could show up as a steadily increasing value instead of the correct time. Fixed a bug that prevented HttpURLConnection External metrics from reporting on the IBM J9 JVM. With Spray routing, fixed a bug that incorrectly set the transaction name of similar route names or set them to \"Unknown Route\". Fixed a bug where some transaction traces would report external segments for non I/O calls in Apache HttpClient. The Java Agent will now read Cross Application Tracing HTTP header names regardless of case. Fixed a bug that could cause cross application tracing between the New Relic Java Agent and non-Java New Relic Agents to fail. Known Issues Postgres JDBC This release does not contain support for some versions of the PostgreSQL jdbc3 drivers supported in previous releases. We recommend that you use 3.26.1.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3260","eolDate":"2019-02-23"},{"agent":"java","date":"2016-01-18","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.25.0/","version":"3.25.0","features":["Performance improvements"],"bugs":["JAX-RS annotations on interfaces were not being observed","Spray and Akka-HTTP instrumentation weren't applying when using Scala 2.10","Fixed an issue that caused Play 2.x requests to produce empty responses when the circuit breaker is tripped","Fixed an issue where setting enable_custom_tracing to false could inadvertently disable Netty instrumentation"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Performance improvements The Java agent now starts up to 50% faster. Your applications will be available that much sooner. Fixes In some cases JAX-RS annotations on interfaces were not being observed, causing transactions using JAX-RS services to be named on the servlet rather than the web servicepath and method. Fixed an issue that prevents Spray and Akka-HTTP instrumentation from applying when using Scala 2.10. Fixed an issue that caused Play 2.x requests to produce empty responses when the circuit breaker is tripped. Fixed an issue where setting enable_custom_tracing to false could inadvertently disable Netty instrumentation. Known Issues Fixed in 3.29.0 Applications that use Play and Ning AsyncHttpClient may miss transactions. The thread profiler may not report data while profiling certain Scala classes. Fixed in 3.28.0 Fixed a bug that could cause Akka Http instrumentation to throw a NullPointerException into customer code. Fixed in 3.27.0 Fixed an issue where the agent treated HTTP headers as being case sensitive, causing CAT to miss under certain conditions. Fixed various issues related to the proper handling of multibyte character encoding. Fixed in 3.26.x CXF instrumentation can name transactions based on auto-generated proxy classes. Later agents now normalizes CXF transaction names. EJB instrumentation may cause a NullPointerException in application code, and erroneously set transaction names. In later versions, the agent records a metric. The Cross Application Tracing API caused Application Response time to be attributed to other transaction time, and prevented linking of transaction traces when doing CAT. Request queuing calculations could show queuing time as a steadily increasing value instead of the correct time. HttpURLConnection External metrics may not report on the IBM J9 JVM. Transaction traces may report external segments for non I/O calls in Apache HttpClient. The Java agent will now read Cross Application Tracing HTTP header names regardless of case. Fixed a bug that could cause cross application tracing between the New Relic Java agent and non-Java New Relic agents to fail.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3250","eolDate":"2019-01-18"},{"agent":"java","date":"2015-12-21","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.24.1/","version":"3.24.1","features":[],"bugs":["Fixed an issue that caused Play 2.x requests to produce empty responses when the circuit breaker is tripped"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixed an issue that caused Play 2.x requests to produce empty responses when the circuit breaker is tripped.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3241","eolDate":"2018-12-21"},{"agent":"java","date":"2015-12-15","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.24.0/","version":"3.24.0","features":["The Java agent now reports synchronous calls to the Mongo Java Driver 2.12 through 3.1","The Java agent now reports and names transactions received through Akka HTTP 1.0, Akka HTTP 2.0 and Spray"],"bugs":["EJB instrumentation could cause a StackOverflowException","Netty instrumentation could throw a NullPointerException","Improve performance when using Cross Application Tracing","Transaction might not be reported when using Akka with mutable messages"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements: MongoDB The Java agent now reports synchronous calls to the Mongo Java Driver 2.12 through 3.1. You will see the Mongo operations in breakdowns in the Applications Overview chart, entries in the Databases tab, and segments in transaction traces. Note:  The asynchronous driver is not supported. Akka HTTP and Spray The Java agent now reports and names transactions received through Akka HTTP 1.0, Akka HTTP 2.0 and Spray. Transactions are named intuitively based on route DSLs. This instrumentation also supports Cross Application Tracing from calling systems. With our previously released support for Akka, your Akka HTTP and Spray applications will now include activity of those transactions all the way through your actor systems. Fixes: In rare cases the Java agent's EJB instrumentation could cause a StackOverflowException to appear in application logs. In some cases the Java agent's Netty instrumentation could throw a NullPointerException to application code. Improve performance when using Cross Application Tracing and a large number of threads. In some cases the transaction would not be reported when using Akka with mutable messages. Known Issues: Play 2.x requests will produce empty responses when the circuit breaker is tripped. We recommend Play 2.x users disable the circuit breaker  when using Java agent versions 3.22 or higher.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3240","eolDate":"2018-12-15"},{"agent":"java","date":"2015-12-01","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.23.0/","version":"3.23.0","features":["Hystrix instrumentation"],"bugs":["Fixes a bug in Cross Application Tracing","Resolved an issue where an application running on Tomcat and containing a large number of static JSPs (5000+) could cause a memory leak"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Hystrix instrumentation This release contains support for versions 1.0.2 through 1.4 of the Hystrix framework. You will now see timing information related to each Hystrix Command's run and getFallback methods. Chained Hystrix commands will be linked into one transaction. Fixes This release fixes a bug in New Relic's Cross Application Tracing (CAT)  that could cause incorrect service and transaction maps. The problem would happen when non-identical applications, with identical transaction names, would appear to be communicating (in the Transaction / Service maps), when in fact, they were not. Note:  Using a combination of pre-3.23.0 and 3.23.0+ can result in external calls between the old and new agents to not show up in the map. To fix this, upgrade all of your agents to 3.23.0+ at the same time Resolved an issue where an application running on Tomcat and containing a large number of static JSPs (5000+) could cause a memory leak within the agent.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3230","eolDate":"2018-12-01"},{"agent":"java","date":"2013-12-16","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.2.3/","version":"3.2.3","features":[],"bugs":["JBoss 7 fails to start with Java 1.6"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: JBoss 7 fails to start with Java 1.6 Starting with version 3.2.0 of the Java agent, JBoss 7 application servers fail to start when running Java 1.6. An IllegalStateException is printed to System.out. This bug has been fixed.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-323","eolDate":"2016-12-16"},{"agent":"java","date":"2015-11-16","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.22.1/","version":"3.22.1","features":[],"bugs":["Fixed an issue that caused Ning's AsyncHttpClient WebSockets requests to fail, or the application not to start","Fixed an issue that could cause an extra transaction to be created, a background transaction named NettyDispatcher","Removed the deprecated bootstrap.classpath configuration"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixed an issue that caused Ning's AsyncHttpClient WebSockets requests to fail, or the application not to start. Fixed an issue that could cause an extra transaction to be created, a background transaction named NettyDispatcher. Removed the deprecated bootstrap.classpath configuration, as it could result in the Java agent's instrumentation failing to load.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3221","eolDate":"2018-11-16"},{"agent":"java","date":"2015-11-06","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.22.0/","version":"3.22.0","features":["Play Framework 2.4 Instrumentation","The deprecated -Dnewrelic.bootstrap_classpath system property can result in missing instrumentation and should not be used","Netty 3.4 - 4.x Instrumentation","AsyncHttpClient Instrumentation 1.0.2 - 1.9.x","Akka Instrumentation 2.0 - 2.4"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Play Framework 2.4 Instrumentation, and Play Framework 2 Improvements Previous Java Agent releases supported the Play Framework up to version 2.3. This release includes instrumentation for Play 2.4.x. This release provides more insight than ever before for all versions of Play 2, including improved segment names, and better signal-to-noise ratio in transaction details. This instrumentation also takes advantage of the new response time line  in the New Relic UI. Because Play is a reactive framework that encourages concurrent activity, your total time for transaction components will often be greater than the response time. If the total time is less than response time, it may indicate resource exhaustion. By separating the total time from the response time, you get a clear picture of when you are getting the benefit of concurrency. If you have used the Java Agent to monitor Play before this release, you may see a decrease in response time. The new response time metric more accurately reflects the time from initial request to response. We support Play applications written in Java or Scala 2.9.3 - 2.11.x. Note:  The deprecated -Dnewrelic.bootstrap_classpath system property can result in missing instrumentation and should not be used. Netty 3.4 - 4.x Instrumentation This release updates our Netty support to include versions from 3.4 to 4.x. Previous release supported up to Netty 3.9. The agent will start transactions for server inbound I/O. The agent will instrument Netty HTTP methods to enable cross application tracing (CAT) in Netty transactions. AsyncHttpClient Instrumentation 1.0.2 - 1.9.x In this release, you will see the time spent in external service calls made using AsyncHttpClient (also known as Ning Http Client). If the external service is also running New Relic, you will see cross application tracing (CAT) details as well. This includes external calls made from Play WSAPI, which uses AsyncHttpClient. Note:  As in previous releases, Play 1 applications will not report AsyncHttpClient activity. Akka Instrumentation 2.0 - 2.4 This release enhances our Akka instrumentation by linking an actor message sender to an actor message receiver in the same transaction. In order to avoid over-instrumentation, our Akka instrumentation does not actually start transactions. If you would like a given actor call to mark the beginning of a transaction, you will need to use the @Trace(dispatcher=true) annotation , or some other form of custom instrumentation . Notes: This release supports core Akka, not all Akka extensions. In particular, it does not identify transactions that have been routed by Spray, Akka HTTP, or Akka Streams. We have heard from customers that these frameworks are important, and we expect to support them soon! Stay tuned to the Java agent incubator , since we may provide an early access instrumentation module for these frameworks before we release them in the agent. Known Issues: If your application uses AsyncHttpClient's WebSockets, do not use this version.  AsyncHttpClient WebSockets requests will fail, or the application will not start. In some cases, calls to NewRelic's getBrowserTimingHeader and getBrowserTimingFooter are ignored.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3220","eolDate":"2018-11-06"},{"agent":"java","date":"2013-12-12","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.2.2/","version":"3.2.2","features":[],"bugs":["Play 2.2 instrumentation in action methods","Invalid exclusive time errors with Play 2.2","Inaccurate async wait time with Play 2.x"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: Play 2.2 instrumentation in action methods In version 3.2.0 and 3.2.1, the Java agent failed to instrument calls present in a controller's action method. This means database calls, external calls, and custom instrumented calls within the action method were not being reported to New Relic. This bug has been fixed. Fix: Invalid exclusive time errors with Play 2.2 In version 3.2.0 and 3.2.1, the Java agent sometimes reported error messages to the newrelic log indicating an \"Invalid exclusive time\". This error has been fixed. Fix: Inaccurate async wait time with Play 2.x In version 3.2.0 and 3.2.1, the Java agent reported an async wait time for Play 2.x transactions that was too large. This bug has been fixed.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-322","eolDate":"2016-12-12"},{"agent":"java","date":"2015-10-01","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.21.0/","version":"3.21.0","features":["Advanced Analytics for APM Errors","The Java Agent now collects information on request/response headers and request method for web transactions"],"bugs":["Fixed a memory leak in async continuations instrumentation for Jetty 7 and 8","Improved error handling with invalid JMX yaml extension files","Improved Circuit Breaker logging","Fixed a bug in Tomcat 7+ instrumentation where request parameters could occasionally get stripped"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Advanced Analytics for APM Errors With this release, the agent reports TransactionError  events. These new events power the beta feature Advanced Analytics for APM Errors  (apply here  to participate). The error events are also available today through New Relic Insights  . Advanced Analytics for APM Errors lets you see all of your errors, with granular detail. Filter and group by any attribute to analyze them. Take action to resolve issues through collaboration. Fixes Fixed a memory leak in async continuations instrumentation for Jetty 7 and 8. Improved error handling with invalid JMX .yml  extension files. Improved Circuit Breaker  logging in the event of a Circuit Breaker trip. Fixed a bug in Tomcat 7+ instrumentation where request parameters could occasionally get stripped when using an async servlet with capture_params set to true. Notes The Java Agent now collects the following information for web transactions: Accept, Host, User-Agent, Content-Length HTTP request headers HTTP request method, for example POST or GET Content-Type HTTP response header Known issues Fixed in 3.25.0: Setting enable_custom_tracing configuration flag to false can inadvertently disable Netty instrumentation. In some cases JAX-RS annotations on interfaces are not observed, causing transactions using JAX-RS services to be named on the servlet rather than the web servicepath and method. Fixed in 3.24.1: The Java agent's Play 2 transaction tracing instrumentation may be incomplete and cause gaps in cross application tracing. Fixed in 3.24.0: The Java agent's EJB instrumentation may cause a StackOverflowException to appear in application logs. Applications may continue to experience the additional Circuit Breaker overhead even when disabled. The Java agent may experience increased overhead when using Cross Application Tracing and a large number of threads. Fixed in 3.23.0 This release may experience a memory leak within the agent for Tomcat containing a large number of static JSPs (5000+). When a transaction makes multiple calls to a database with the same obfuscated SQL, a NullPointerException is may get thrown in the agent. This release contains a bug in New Relic's Cross Application Tracing (CAT) that can cause incorrect service and transaction maps. The problem happens when non-identical applications, with identical transaction names, would appear to be communicating (in the Transaction / Service maps), when in fact, they were not. Using a combination of pre-3.23.0 and 3.23.0+ can result in external calls between the old and new agents to not show up in the map. To fix this, upgrade all of your agents to 3.23.0+ at the same time.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3210","eolDate":"2018-10-01"},{"agent":"java","date":"2013-12-06","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.2.1/","version":"3.2.1","features":[],"bugs":["Exceptions thrown from conflicting JAXB versions","Usage of the newrelic.bootstrap_classpath system property","Data collection for customers using the IBM JVM without WebSphere"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: Exceptions thrown from conflicting JAXB versions The New Relic Java agent now supports customers using any JAXB or Xerces version. This bug was introduced in version 3.1.0. Fix: Usage of the newrelic.bootstrap_classpath system property In version 3.2.0, the newrelic.bootstrap_classpath system property caused an IllegalAccessError. That bug has been fixed. Note also that this system property has been deprecated and should not be used. Fix: Data collection for customers using the IBM JVM without WebSphere New Relic now supports customers using an IBM JVM without running WebSphere. In this scenario, you must set the sync_startup flag set to true in the common section of their newrelic.yml.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-321","eolDate":"2016-12-06"},{"agent":"java","date":"2015-09-01","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.20.0/","version":"3.20.0","features":["JCache API instrumentation"],"bugs":["Circuit Breaker alerts now better align with data displayed in JVMs tab","Java Agent's HttpURLConnection instrumentation could report incorrect external response time metrics","The Java Agent's MongoDB instrumentation no longer reports errors due to runtime exceptions","Guice dynamic proxies could be instrumented, potentially causing MGI issues","Deadlock would occur at startup on some WebSphere applications","Missing Cross Application Tracing information on WebLogic 12 when using HttpURLConnection"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements: JCache The Java Agent now instruments the JCache API. The instrumentation times cache operations of implementations of the JCache API. To get additional information about your operations in the Databases page, enable com.newrelic.instrumentation.jcache-datastore-1.0.0 in your newrelic.yml . This will incur additional overhead. Fixes: Circuit Breaker  alerts now better align with data displayed in JVMs tab. In some cases the Java Agent's HttpURLConnection instrumentation could report incorrect external response time metrics The Java Agent's MongoDB instrumentation no longer reports errors due to runtime exceptions that are caught and handled by applications. Fixed an issue where Guice dynamic proxies could be instrumented, potentially causing MGI issues . In rare cases a deadlock would occur at startup on some WebSphere applications. Fixed an issue that could cause missing Cross Application Tracing information on WebLogic 12 when using HttpURLConnection.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3200","eolDate":"2018-09-01"},{"agent":"java","date":"2013-12-03","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.2.0/","version":"3.2.0","features":["Glassfish 4 metrics for JVM Memory, Thread Pool, and Transactions","Decreased agent overhead for Play 2","Manually disable auto RUM instrumentation for specific pages","akka.actor.ActorKilledException is now ignored by default","New Relic reports host capacity information","Report JVM name and revision to New Relic as part of JVM description"],"bugs":["Support for Play 2.2","Background tasks created by an @Trace annotation with a 'metricName' element did not show up in the New Relic UI"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Glassfish 4 metrics for JVM Memory, Thread Pool, and Transactions New Relic now displays JVM memory, thread pool, and transaction metrics for Glassfish 4. To expose these metrics, please set http-service, transaction- service, and web-container monitoring within Glassfish to high. To see the metrics in New Relic, go to Monitoring > JVMs. Decreased agent overhead for Play 2 This version of the agent reduces the overhead that it incurs on Play 2. Play 2 users should upgrade for improved performance. In addition to general overhead improvements, New Relic has introduced a new setting to reduce overhead even more for particularly low-latency applications. Note that this setting will make the call info in Trace Details more generic. Manually disable auto RUM instrumentation for specific pages For supported JSP engines, New Relic automatically adds RUM (Real User Monitoring) elements to the response HTML. If you like auto-RUM, but do not want to apply it to all pages, you can now disable it for select pages. The configuration property disabled_auto_pages in the browser_monitoring section can now be used to disable auto RUM instrumentation for a comma delimited list of pages. For example, akka.actor.ActorKilledException is now ignored by default The ActorKilledException is commonly thrown in Play applications as a control mechanism in normally functioning applications. In previous versions, this exception inflated the reported error rate. These exceptions are now ingored by default. You can override the default ignore_errors list to provide your own exceptions or to omit the ActorKilledException. New Relic reports host capacity information New Relic now reports physical CPU cores, logical CPU cores (hyperthreads), and physical memory. On non-Linux platforms, the agent runs a subprocess to retrieve this information. To see the info in New Relic, go to Settings > Environment > Environment Snapshot. Report JVM name and revision to New Relic as part of JVM description Recording the JVM name in addition to the vendor allows differentiation between different JVMs from the same vendor. To see these values in New Relic, go to Settings > Environment > Environment Snapshot and look for the \"Java VM\" and \"Java VM Version\" settings. Fix: Support for Play 2.2 Web transactions were not being correctly captured under some circumstances for Play 2.2 applications. Web transactions are now correctly reported. Also note the change in command line syntax as of Play 2.2: https://docs.newrelic.com/docs/java/play-installation-for-java Fix: Background tasks created by an @Trace annotation with a 'metricName' element did not show up in the New Relic UI.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-320","eolDate":"2016-12-03"},{"agent":"java","date":"2015-08-13","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.19.2/","version":"3.19.2","features":[],"bugs":["Fixed an issue that could cause NoClassDefFoundErrors when using JDBC ResultSet instrumentation on JBoss"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixed an issue that could cause NoClassDefFoundErrors when using JDBC ResultSet instrumentation on JBoss.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3192","eolDate":"2018-08-13"},{"agent":"java","date":"2015-08-07","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.19.1/","version":"3.19.1","features":[],"bugs":["JBoss 4.x could fail to start due to a NullPointerException","Dropwizard appservers could fail to start due to a ClassCastException during log initialization"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes In some cases JBoss 4.x could fail to start due to a NullPointerException. In some cases Dropwizard appservers could fail to start due to a ClassCastException during log initialization.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3191","eolDate":"2018-08-07"},{"agent":"java","date":"2015-07-29","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.19.0/","version":"3.19.0","features":["Redis improvements"],"bugs":["HttpClient 3 instrumentation could overstate the external call count","Agent could report errors that it was configured to ignore","Some line numbers did not display correctly in stack traces"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Redis The agent’s Redis instrumentation is now more efficient. Fixes In some cases the HttpClient 3 instrumentation could overstate the external call count. In rare cases the agent would report errors that it was configured to ignore. Some line numbers did not display correctly in stack traces.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3190","eolDate":"2018-07-29"},{"agent":"java","date":"2015-07-01","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.18.0/","version":"3.18.0","features":["Jetty","Thrift","Resin","Heap Alerting","Exception messages for allow list"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Jetty Updated Jetty instrumentation to support Jetty 9.3. Thrift Added support for Apache Thrift 0.8 and greater. This instrumentation automatically adds timing to Thrift calls and sets transaction names based on Thrift method names. It can be disabled in the newrelic.yml by adding: Resin The New Relic Resin Instrumentation now reports errors as HttpErrors, allowing them to be ignored. Heap Alerting A new heap utilization metric has been created for alerting purposes. This metric tracks the percentage of heap in use as a number between 0 and 1, where 0 means no heap usage and 1 means a full heap. The new metric is: Memory/Heap/Utilization Exception messages for allow list Java exception messages will now be obfuscated when high-security mode is enabled. If specific exception messages should be allowed through, they can be added to your allow list with the following configuration property: The allow list is a comma-delimited string of exception class package + class name. This can be enabled or disabled independently of high-security mode with the following property:","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3180","eolDate":"2018-07-01"},{"agent":"java","date":"2015-06-30","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.17.1/","version":"3.17.1","features":[],"bugs":["Fix for ERROR: Inconsistent state"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Fixed a bug in 3.17.0, that in rare cases could cause an application thread to die. In this case, the agent log has many messages, “ERROR: Inconsistent state!”","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3171","eolDate":"2018-06-30"},{"agent":"java","date":"2015-06-11","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.17.0/","version":"3.17.0","features":["Websphere Liberty Profile","Performance improvements","Customize hostname displayed in APM","WebLogic and WebSphere instance name available","Custom instrumentation of transaction attributes is disabled by default"],"bugs":["Very large thread profiles were failing to report to RPM","Cross application tracing date was failing to report when using Jersey 2 endpoints","Spring AOP instrumentation is now disabled by default","RabbitMQ metrics could double-report for some versions of RabbitMQ","In rare cases the agent would report a LinkageError"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Websphere Liberty Profile The Java agent now provides instrumentation for WebSphere Liberty Profile . This includes web transaction visibility, Cross Application Tracing, and app server stats. Performance improvements The Java agent now starts more quickly so applications are available sooner. This release also reduces agent overhead at run time. Customize hostname displayed in APM A new configuration setting has been added: process_host.display_name . When set in the newrelic.yml  configuration file, the display name identifies the host in the APM UI , along with the hostname that the agent automatically captures. In addition, the display name can be set using the NEW_RELIC_PROCESS_HOST_DISPLAY_NAME environment variable. This property can be viewed in all Insights transaction events. WebLogic and WebSphere instance name available The instance name for WebLogic and WebSphere application servers is now available in transaction traces, traced errors, and Insights transaction events. Custom instrumentation of transaction attributes is disabled by default Custom attributes defined using the Instrumentation  tab in the UI are now disabled by default. In order to enable these attributes, you must have High-security mode disabled and you must place the following text in the common: block of your newrelic.yml : Fixes Very large thread profiles were failing to report to RPM, causing the site to display a time out message. The agent will now truncate the size of the profile before sending. Cross application tracing date was failing to report when using Jersey 2 endpoints. Spring AOP instrumentation is now disabled by default. It was exercising a bug in certain versions of Java 8 that caused the JVM to crash. To re-enable, include the following in your newrelic.yml : RabbitMQ metrics could double-report for some versions of RabbitMQ. This was introduced in Java agent version 3.16.1 and is fixed in this version. In rare cases the agent would report a LinkageError.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3170","eolDate":"2018-06-11"},{"agent":"java","date":"2015-05-14","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.16.1/","version":"3.16.1","features":["Redis","RabbitMQ","Cross Application Tracing API","Play 2 Framework","Circuit Breaker","Added configuration to disable Deadlock Detection","Reduced the memory overhead of the Java agent"],"bugs":["Play 2 Framework","The proxy_host name is no longer sent to New Relic","Fixed issue where external transactions were reported twice when using HttpURLConnection","The Java Agent now honors the segment_limit setting for async traces","Cross-application requests from other New Relic-instrumented applications will reliably appear in the App and Transaction maps"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements: Redis Added support for the Jedis client versions 1.4.0 or higher. You can now see your Redis calls in breakdowns in the overview chart, entries in the Databases tab, and segments in transaction traces. RabbitMQ Updated RabbitMQ instrumentation to support RabbitMQ 3.5 and higher. Cross Application Tracing API Use the cross application tracing API when the agent does not provide cross application tracing support for your application. See the documentation Play 2 Framework Improved instrumentation for Play controller classes. Circuit Breaker Starting in this release, the New Relic Java agent detects when memory is nearly exhausted and trips a “circuit breaker” that limits the agent’s memory usage. The agent won’t report transactions while the circuit breaker is tripped, so throughput will be understated. In the rare case that the circuit breaker trips, the New Relic UI will provide more information. For more details, see the documentation . Added configuration to disable Deadlock Detection Under very heavy load conditions with many threads, the Deadlock Detector service may slow response time. You can now disable this feature with the following setting: Reduced the memory overhead of the Java agent Fixes: Play 2 Framework The Java Agent now honors the segment_limit setting for async traces, and can now handle much deeper async traces. This is useful to decrease if you're experiencing slower response time or high memory overhead when executing large async transactions. Cross-application requests from other New Relic-instrumented applications will reliably appear in the App and Transaction maps. The proxy_host name is no longer sent to New Relic. Fixed issue where external transactions were reported twice when using HttpURLConnection. Previously, this caused throughput to appear doubled.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3161","eolDate":"2018-05-14"},{"agent":"java","date":"2015-03-31","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.15.0/","version":"3.15.0","features":["Labels and Rollups","You can now update Custom instrumentation XML in the extensions folder and it will be reloaded within a minute"],"bugs":["Prior to this version, some thread profiles would time out and not display","The Java Agent now works around IBM JVM bug IV25688"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements: Labels and Rollups The New Relic Java agent now supports the ability to apply labels to applications, so that you can easily sort, filter, and page through all of the applications on your account's Applications list. Configuration can be done in the newrelic.yml file: More information on using labels to categorize your applications can be found in the New Relic APM documentation . With this version of the Java Agent, you can update Custom instrumentation XML in the extensions folder and it will be reloaded within a minute. Fixes: Prior to this version, some thread profiles would time out and not display. Thread profiles will now complete reliably. The Java Agent now works around IBM JVM bug IV25688 . The agent will scale back a small amount of its instrumentation on old IBM JVMs to avoid inducing the bug. The workaround should leave most customers unaffected. Loss of instrumentation caused by the workaround can be fixed by upgrading the JVM to the latest service release.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3150","eolDate":"2018-03-31"},{"agent":"java","date":"2015-02-25","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.14.0/","version":"3.14.0","features":["Synthetic transaction tracing","EJB Session Beans","Unified view for SQL database and NoSQL datastore products","Datastax Cassandra client","MongoDB client","API Reported Errors"],"bugs":["The Java Agent may now capture traces for transactions that resulted in an error","Updated default newrelic.yml to use transaction_events.max_samples_stored instead of deprecated option","JBoss dispatcher reports correctly for clustered environments where jboss.home and jboss.home.dir are not set","Resolved a bug which caused certain Jetty configurations to stop sending metric data","Under very light load, the Agent could send incorrect transaction timestamps","Fixed parsing error in log_file_count setting"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements: Synthetic transaction tracing Synthetic monitors lets you monitor your site from around the world. When you use synthetic monitoring to monitor your Java application, up to 20 detailed transaction traces will now be captured every minute when the application is probed from synthetics. To learn more about this feature, visit our documentation EJB Session Beans The Java agent now monitors Enterprise Java Beans (EJB) 3.0 session beans. The agent instruments @Stateless and @Stateful EJBs, and those that extend java.ejb.SessionBean. The agent traces methods declared by corresponding interfaces annotated with @Remote and @Local. Unified view for SQL database and NoSQL datastore products. The response time charts in the application overview page will now include NoSQL datastores, such as Cassandra and MongoDB,and also the product name of existing SQL databases such as MySQL, Postgres, Oracle, etc. For existing SQL databases, in addition to the existing breakdown of SQL statements and operations, the queries are now also associated with the database product being used. For NoSQL datastores, such as Cassandra and MongoDB, we have now added information about operations performed against those products, similar to what is being done for SQL databases. This new unified Databases page will enable the filtering of metrics and operations by product, and includes a table listing all operations. Because this introduces a notable change to how SQL database metrics are collected, it is important that you upgrade the agent version on all hosts.If you are unable to transition to the latest agent version on all hosts at the same time, you can still access old and new metric data for SQL databases, but the information will be split across two separate views. Datastax Cassandra client Added support for the Datastax Cassandra client versions 2.1.2 or higher. This will include breakdowns in the overview chart, entries in the Databases tab, and segments in transaction traces. Note: uses of the client's async API will not be captured in transaction traces. MongoDB client Added support for MongoDB client versions 2.12.0 up to but not including 3.0+. This will include breakdowns in the overview chart, entries in the Databases tab, and segments in transaction traces. API Reported Errors API reported errors can now be prioritized on a transaction over tracer reported errors. Add the following config to allow prioritizing: Fixes: The Java Agent may now capture traces for transactions that resulted in an error (4xx or 5xx response code). Prior to this release, the agent would only capture traces for successful responses. Updated default newrelic.yml to use transaction_events.max_samples_stored instead of deprecated analytics_events.max_samples_stored property. JBoss dispatcher reports correctly for clustered environments where jboss.home and jboss.home.dir are not set. Resolved a bug which caused certain Jetty configurations to stop sending metric data. Under very light load, the Agent could send incorrect transaction timestamps. Fixed parsing error in log_file_count setting. Prior to this release, this setting produced one more log file than expected.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3140","eolDate":"2018-02-25"},{"agent":"java","date":"2015-01-20","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.13.0/","version":"3.13.0","features":["Custom Insights events API","The agent now captures and reports thread profiles in XRay Sessions for non-web transactions"],"bugs":["Incorrect JMS transaction names for users of Oracle ATG Web Commerce"],"security":["Application code could encounter a NoClassDefFoundError"],"supportedOperatingSystems":null,"description":"Download this agent version Improvements: Custom Insights events API In addition to attaching custom attributes to the events that the Java agent generates automatically for each transaction, you can now record custom event types into Insights with the new NewRelic.getAgent().getInsights().recordCustomEvent API. The agent now captures and reports thread profiles in XRay Sessions for non-web transactions. Fixes: Incorrect JMS transaction names for users of Oracle ATG Web Commerce In rare cases, application code would encounter a NoClassDefFoundError for one or more classes contained in the newrelic.jar.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3130","eolDate":"2018-01-20"},{"agent":"java","date":"2014-12-22","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.12.1/","version":"3.12.1","features":["Play 2 async activity is no longer tracked when transaction is ignored","Reduced GC overhead when monitoring Play 2 applications","Reduced memory usage when inspecting slowest SQL statements","stack_based_naming now false by default"],"bugs":["Memory leak when applications using servlets are continuously reloaded inside the JVM","Memory leak with long running transactions performing a high number of external calls","Sometimes with JBoss application servers, two JVMs were being displayed in the UI when there was actually only one"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Play 2 async activity is no longer tracked when transaction is ignored. Reduced GC overhead when monitoring Play 2 applications. Reduced memory usage when inspecting slowest SQL statements. Config Changes stack_based_naming now false by default. The stack_based_naming in the transaction_tracer section is now false by default. Stack-based naming caused significant overhead in many Scala applications, so it now must be set to true explicitly. Set to true for better naming of trace detail segments in Scala Play applications. Fixes Memory leak when applications using servlets are continuously reloaded inside the JVM. Memory leak with long running transactions performing a high number of external calls. In some cases for JBoss application servers, two JVMs were being displayed in the UI when there was actually only one.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3121","eolDate":"2017-12-22"},{"agent":"java","date":"2014-11-06","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.12.0/","version":"3.12.0","features":[],"bugs":["Various bug fixes"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes Various bug fixes","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3120","eolDate":"2017-11-06"},{"agent":"java","date":"2014-09-30","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.11.0/","version":"3.11.0","features":["Spring Web Services","Support for Auto-RUM and precompiled JSPs"],"bugs":["Under some circumstances the agent would report a LinkageError","Grails 2 transaction names had extra slash","Fix for auto-RUM","Reduce overhead of Akka instrumentation when not used in conjunction with Play/Netty","RabbitMQ instrumentation reported unnecessary transactions"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Spring Web Services The Java Agent now supports Spring Web Services. Transactions are named based on the SOAP method name. The agent also reports the SOAP version, content type, and SOAP Action. Support for Auto-RUM and precompiled JSPs The Java agent now provides auto rum support when precompiling JSPs. To use auto rum when precompiling JSP files, add the agent as a java agent to your pre-compilation process. Fixes Fix: Under some circumstances the agent would report a LinkageError Fix: Grails 2 transaction names had extra slash Fix for auto-RUM In some cases when a script tag is before a head tag in a JSP file, the auto RUM instrumentation was failing to place the initial New Relic header script in the page. Fix: Reduce overhead of Akka instrumentation when not used in conjunction with Play/Netty Fix: RabbitMQ instrumentation reported unnecessary transactions basicPublish, basicGet, and nextDelivery no longer start short-lived  transactions.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3110","eolDate":"2017-09-30"},{"agent":"java","date":"2013-11-05","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.1.1/","version":"3.1.1","features":[],"bugs":["In some cases, metrics were not reported in Play 2 apps","The Java Agent was unable to instrument classes in WSO2 API Manager"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: In some cases, metrics were not reported in Play 2 apps The Java Agent now reports all metric data consistently. Fix: The Java Agent was unable to instrument classes in WSO2 API Manager The Java Agent now reports data for WSO2 applications.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-311","eolDate":"2016-11-05"},{"agent":"java","date":"2014-08-26","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.10.0/","version":"3.10.0","features":["Support for Java SE 8","RequestMapping annotation used to name web transactions","Servlet UserPrincipal name can be reported as an attribute","Non-Web Transactions can now be made Key Transactions with a custom apdex T"],"bugs":["WebSphere JMX metrics reported when global security is enabled","Web transactions not always reported","WebSphere 7 reports active thread count on the JVM tab","Excess error reporting in Play apps","Request headers are not read when cross application tracing is disabled","NewRelic API methods prematurely deprecated"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Improvements Full support for Java SE 8 The New Relic Java agent now supports Java SE 8! Applications can now run on a Java 8 JVM, including those compiled to target Java 8 (i.e. -target 1.8). The system property newrelic.enable.java.8 is no longer necessary. @RequestMapping annotation used to name web transactions Where available, Spring Web Transactions are now named using the URI path pattern defined in the @RequestMapping annotation. This generally provides even more meaningful transaction names than controller methods. To disable this and revert back to naming using controllers, add this config to your newrelic.yml: WebSphere JMX metrics reported when global security is enabled Prior to this version, JMX metrics could not be pulled by the agent with WebSphere when global security was enabled. This means custom JMX metrics in a yaml file and default JMX metrics displayed on the JVM Threads and Http Sessions tabs were not reported. Servlet UserPrincipal name can be reported as an attribute With this release, you can enable the capturing of the UserPrincipal name so that it is available in New Relic and as a transaction trace attribute. To enable: Non-Web Transactions can now be made Key Transactions with a custom apdex T This feature will be available in the RPM UI very soon. It requires this or a higher version of the agent. Fixes Fix: Web transactions not always reported. In some unusual cases the Agent stopped reporting web transactions. The agent would log an error that included the phrase \"Inconsistent state\" Fix: WebSphere 7 reports active thread count on the JVM tab The thread pool active count being displayed in the UI was actually the pool size. Fix: Excess error reporting in Play apps In Scala/Play apps, the agent was incorrectly logging errors when promises were resolved with a Failure. Fix: Request headers are not read when cross application tracing is disabled Disabling cross application tracing using these config settings did not stop the Agent from reading request headers. Fix: NewRelic API methods prematurely deprecated In 3.9.0, some API calls in com.newrelic.api.agent.NewRelic were prematurely deprecated. We are in the process of providing a more complete API for the New Relic agent. In an upcoming release, these methods may become deprecated, but with a stable and superior API alternative.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-3100","eolDate":"2017-08-26"},{"agent":"java","date":"2013-10-21","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.1.0/","version":"3.1.0","features":["Percentiles and Histograms","JAX-RS annotation instrumentation","JAX-WS instrumentation","The newrelic-api-sources.jar is now included in the zip file"],"bugs":["In some cases, agent had excessive overhead on Spring AOP apps","Play Framework instrumentation was ignoring the ignoreTransaction call","Potential memory leak when app continually creates ClassLoaders","Agent zip distribution did not include the API source jar",""],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 . Percentiles and Histograms The Java Agent now captures data that provides percentile and histogram views in the New Relic UI. JAX-RS annotation instrumentation The Java Agent now instruments and names web transactions based on javax.ws.rs annotations. JAX-WS instrumentation The Java Agent now instruments methods on classes that are marked with the javax.jws.WebService annotation. Fix: In some cases, agent had excessive overhead on Spring AOP apps The agent should now perform well for any Spring AOP application. Fix: Play Framework instrumentation was ignoring the ignoreTransaction call The Play Framework 2.x instrumentation now honors the New Relic API ignoreTransaction call. Fix: Potential memory leak when app continually creates ClassLoaders The Java Agent now handles applications where ClassLoaders are continuously created. Fix: Agent zip distribution did not include the API source jar The newrelic-api-sources.jar is now included in the zip file.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-310","eolDate":"2016-10-21"},{"agent":"java","date":"2013-10-03","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.0.1/","version":"3.0.1","features":[],"bugs":["Issue at startup with JBoss and Glassfish","RUM not auto-instrumented for JSPs"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: Issue at startup with JBoss and Glassfish An issue in the 3.0.0 version caused startup of some versions of JBoss and Glassfish to fail. This version fixes that issue. Fix: RUM not auto-instrumented for JSPs The Java Agent should auto-instrument RUM header and footer in JSPs when using the Jasper engine. This did not work in 3.0.0. This version fixes that issue.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-301","eolDate":"2016-10-03"},{"agent":"java","date":"2013-10-01","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/3.0.0/","version":"3.0.0","features":["Spring AOP instrumentation","Performance Improvements","Requires Java SE 6 or 7"],"bugs":["Hibernate improvements","Removed need for WebSphere SSL work-around"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Spring AOP instrumentation This version instruments any call that passes through an AOP pointcut that you have declared in your Spring application. This gives your additional insight into the call time of key Spring beans. Performance Improvements This version contains optimizations that reduce agent overhead. Fixes: Hibernate improvements In this version, we provide more consistent detail into Hibernate calls across supported version of Hibernate (3.3 - 4.2). Fix: Removed need for WebSphere SSL work-around Previous versions sometimes required a work-around when using WebSphere. This version removes the need for a work-around. NOTE: Requires Java SE 6 or 7 Java Agent 3.0 requires Java SE 6 or 7. At signup or on the release notes page , you have the option to download a version of the agent that works with Java SE 5.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-300","eolDate":"2016-10-01"},{"agent":"java","date":"2012-10-09","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.9.0/","version":"2.9.0","features":["Support for Key Transactions","More metrics available in Custom Dashboards"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Key Transactions. Key Transactions let you closely monitor these important key business transactions and receive alerts when they are performing poorly. For more information see the full documentation . More metrics available in Custom Dashboards","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-290","eolDate":"2015-10-09"},{"agent":"java","date":"2012-09-11","downloadLink":null,"version":"2.8.0","features":["Supports basic proxy authentication for the case where there is a proxy server between the agent and the internet. The configuration uses proxy_user and proxy_password settings.","To avoid reporting the same transaction trace repeatedly, the agent reports a number of the slowest transactions"],"bugs":["Transaction trace reported to wrong app if enable_auto_app_naming and browser requested a transaction trace"],"security":[],"supportedOperatingSystems":null,"description":"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 Supports basic proxy authentication for the case where there is a proxy server between the agent and the internet. The configuration uses proxy_user and proxy_password settings. To avoid reporting the same transaction trace repeatedly, the agent reports a number of the slowest transactions. Bug fix: Transaction trace reported to wrong app if enable_auto_app_naming and browser requested a transaction trace","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-280","eolDate":"2015-09-11"},{"agent":"java","date":"2012-07-31","downloadLink":null,"version":"2.7.0","features":["Add skipTransactionTrace element to @Trace annotation to tell Agent to drop method from transaction trace","Add -Dnewrelic.bootstrap_classpath=true system property to append newrelic.jar to bootstrap classpath","Support RUM reporting to multiple applications"],"bugs":["Asynchronous processing time not reported correctly in Play 1.2.4","CXF transaction names not set to URI path if protocol is https"],"security":[],"supportedOperatingSystems":null,"description":"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 Add skipTransactionTrace element to @Trace annotation to tell Agent to drop method from transaction trace Add -Dnewrelic.bootstrap_classpath=true system property to append newrelic.jar to bootstrap classpath Support RUM reporting to multiple applications (RUM3) Bug fix: Asynchronous processing time not reported correctly in Play 1.2.4 Bug fix: CXF transaction names not set to URI path if protocol is https","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-270","eolDate":"2015-07-31"},{"agent":"java","date":"2012-06-06","downloadLink":null,"version":"2.6.0","features":["Java 7: Native support for instrumenting classes compiled to Java 7 bytecode","Audit Mode: mode which logs all data sent to New Relic in the newrelic_agent.log"],"bugs":["Prevent agent instrumentation from changing the Serial Version UID","Prevent memory leak when client applications start and subsequently stop a thread before completing a transaction","Prevent stack overflow exception when executing queries using the Postgres 9.0.x JDBC driver","Fix dispatch handler instrumentation for Jetty 7.5.x","Set the application port correctly under Jetty 4.x","Make the transacation_tracer configuration settings respect command line and environment overrides"],"security":[],"supportedOperatingSystems":null,"description":"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 Java 7: Native support for instrumenting classes compiled to Java 7 bytecode Audit Mode: mode which logs all data sent to New Relic in the newrelic_agent.log Bug fix: Prevent agent instrumentation from changing the Serial Version UID (introduced in 2.2.0) Bug fix: Prevent memory leak when client applications start and subsequently stop a thread before completing a transaction (introduced in 2.2.0) Bug fix: Prevent stack overflow exception when executing queries using the Postgres 9.0.x JDBC driver Bug fix: Fix dispatch handler instrumentation for Jetty 7.5.* (introduced in 2.5.0) Bug fix: Set the application port correctly under Jetty 4.* Bug fix: Make the transacation_tracer configuration settings respect command line and environment overrides","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-260","eolDate":"2015-06-06"},{"agent":"java","date":"2012-05-01","downloadLink":null,"version":"2.5.0","features":["Browser traces"],"bugs":["OC4J does not start","AbstractMethodError calling getRemoteUser in Tomcat and Glassfish","Deployment does not use SSL port if SSL is configured","NullPointerException getting request URI in Jetty 4.x and 5.x","JSP compiler error with auto RUM in Tomcat 5","Transaction parameters removed if error is reported but response status 400","No request parameters in Resin 3.x","AbstractMethodError calling getContextPath() with Tomcat 5.x","Ignore transaction before transaction started stops transaction reporting"],"security":[],"supportedOperatingSystems":null,"description":"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 Browser traces Bug fix: OC4J does not start (introduced in 2.2.0) Bug fix: AbstractMethodError calling getRemoteUser in Tomcat and Glassfish Bug fix: Deployment does not use SSL port if SSL is configured (introduced in 2.2.0) Bug fix: NullPointerException getting request URI in Jetty 4.x and 5.x Bug fix: JSP compiler error with auto RUM in Tomcat 5 Bug fix: Transaction parameters removed if error is reported but response status < 400 Bug fix: No request parameters in Resin 3.x Bug fix: AbstractMethodError calling getContextPath() with Tomcat 5.x (introduced in 2.2.0) Bug fix: Ignore transaction before transaction started stops transaction reporting","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-250","eolDate":"2015-05-01"},{"agent":"java","date":"2012-04-18","downloadLink":null,"version":"2.4.2","features":[],"bugs":["ClassLoader.loadClass deadlock"],"security":[],"supportedOperatingSystems":null,"description":"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 Bug fix: ClassLoader.loadClass deadlock (introduced in 2.4.0)","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-242","eolDate":"2015-04-18"},{"agent":"java","date":"2012-04-02","downloadLink":null,"version":"2.4.1","features":[],"bugs":["AssertionError in WebLogic"],"security":[],"supportedOperatingSystems":null,"description":"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 Bug fix: AssertionError in WebLogic (introduced in 2.2.0)","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-241","eolDate":"2015-04-02"},{"agent":"java","date":"2012-03-27","downloadLink":null,"version":"2.4.0","features":["Add stall_threshold setting for reporting stall errors"],"bugs":["ClassNotFoundException with JBoss AS 7","NoClassDefFoundError with Glassfish 3.1.2","ClassCastException with Glassfish 3.1.1","Agent stops reporting web transactions","Instrumentation error in Jetty 7.5.4","Possible unknown host for external call with HttpClient 3.0.1","Stall error reporting broken","agent_enabled setting not working"],"security":[],"supportedOperatingSystems":null,"description":"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 Bug fix: ClassNotFoundException with JBoss AS 7 (introduced in 2.2.0) Bug fix: NoClassDefFoundError with Glassfish 3.1.2 (introduced in 2.2.0) Bug fix: ClassCastException with Glassfish 3.1.1 (introduced in 2.2.0) Bug fix: Agent stops reporting web transactions (introduced in 2.2.0) Bug fix: Instrumentation error in Jetty 7.5.4 (introduced in 2.2.0) Bug fix: possible unknown host for external call with HttpClient 3.0.1 (introduced in 2.3.0) Bug fix: stall error reporting broken Bug fix: agent_enabled setting not working Add stall_threshold setting for reporting stall errors","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-240","eolDate":"2015-03-27"},{"agent":"java","date":"2012-02-13","downloadLink":null,"version":"2.3.1","features":[],"bugs":["Agent logging breaks webapp log4j configuration"],"security":[],"supportedOperatingSystems":null,"description":"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 Bug fix: Agent logging breaks webapp log4j configuration (introduced in 2.3.0)","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-231","eolDate":"2015-02-13"},{"agent":"java","date":"2012-02-01","downloadLink":null,"version":"2.3.0","features":["Play! framework support","Create web transactions using custom instrumentation","Use log4j instead of Java API logging"],"bugs":["RUM auto instrumentation fixes","Multiple app names in app_name setting out of order","Possible java.lang.IllegalArgumentException with parameterized SQL","WebSphere instrumentation broken"],"security":[],"supportedOperatingSystems":null,"description":"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 Play! framework support Create web transactions using custom instrumentation Use log4j instead of Java API logging Bug fix: RUM auto instrumentation fixes Bug fix: multiple app names in app_name setting out of order (introduced in 2.2.0) Bug fix: possible java.lang.IllegalArgumentException with parameterized SQL (introduced in 2.2.0) Bug fix: WebSphere instrumentation broken (introduced in 2.2.0)","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-230","eolDate":"2015-02-01"},{"agent":"java","date":"2015-01-08","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.21.7","version":"2.21.7","features":[],"bugs":["Fixed an issue that in rare cases could cause the agent to cease reporting data until JVM restart"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version Fixes This is a bugfix release for the legacy Java SE5 version of the agent. Unless you are a Java SE5 user, use the latest version of the New Relic Java agent. Fixed an issue that in rare cases could cause the agent to cease reporting data until JVM restart. Known issues X-ray sessions sometimes return no transaction traces. Many x-ray session runs can cause a memory leak. Play framework Higher overhead with Play 2 than later releases. Does not work properly with Play 2.2 Counts akka.actor.ActorKilledException as an error. Play transaction does not complete until timeout expires When using Play, ignoreTransaction call does not take effect In some cases running Weblogic, the Java agent fails certificate validation when connecting to New Relic. This may require a workaround . This release contains some inconsistencies in the instrumentation of Hibernate across versions. This release requires a workaround  to use SSL with WebSphere. Potential memory leak when app continually creates ClassLoaders. Rare memory leak if agent does not report to New Relic for an extended period. When running IBM JVM without WebSphere, you must set the sync_startup flag set to true in the common section of newrelic.yml: sync_startup: true. Workaround If you require a workaround for one of these issues, please open a ticket at support.newrelic.com .","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2217","eolDate":"2018-01-08"},{"agent":"java","date":"2014-04-24","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.21.6/","version":"2.21.6","features":[],"bugs":["XML entity expansion with non-SSL connection to New Relic"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Note : This is a bugfix release for the legacy Java SE5 version of the agent. Unless you are a Java SE5 user, use the latest version of the agent. The 3.x agent works with Java SE 6 and 7. If you are using Java SE 5, this is the release for you. Fix: XML entity expansion with non-SSL connection to New Relic Fixed an XML entity expansion vulnerability that only occurs when the agent is configured with ssl: false; the default is true. The agent already has other protection against unauthorized entity expansion. This fix is an additional layer of protection.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2216","eolDate":"2017-04-24"},{"agent":"java","date":"2014-03-05","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.21.5/","version":"2.21.5","features":["Agent no longer supports obfuscation of individual fields"],"bugs":["PostgreSQL explain plan bug","SQL parameter obfuscation didn't work if the parameter value contained a newline","Private trust store location for use_private_ssl flag"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 3.x agent works with Java SE 6 and 7. If you are using Java SE 5, this is the release for you. PostgreSQL explain plan bug There was a PostgreSQL bug that allowed parameters to be sent in explain plans under some circumstances. To avoid this issue, the New Relic agent now does not report explain plans for PostgreSQL. Agent no longer supports obfuscation of individual fields Previous versions of the agent allowed an obfuscated_sql_fields option to select specific field names to obfuscate when record_sql: raw. We have discovered rare cases in which this feature would not mask SQL parameters correctly, so we have removed the configuration option. Now, if obfuscated_sql_fields is set, the setting of record_sql: raw is ignored and _all_ fields are masked. Fix: SQL parameter obfuscation didn't work if the parameter value contained a newline The record_sql: obfuscated config setting did not properly mask parameters when it included a newline character. This bug has been fixed. Fix: Private trust store location for use_private_ssl flag The 2.21.4 agent did not properly load a private trust store used with the use_private_ssl flag. This bug has been fixed.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2215","eolDate":"2017-03-05"},{"agent":"java","date":"2013-09-10","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.21.4/","version":"2.21.4","features":[],"bugs":["Metric Grouping Issue with Netty","Make Cookie parsing more robust when running on Netty","Agent could not connect to New Relic in non-DNS environments","Relic in environments where DNS was used for hostname resolution. * Fix: In 2.21.2 and 2.21.3 an"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: Metric Grouping Issue with Netty The request URL was referenced in some metric names, causing Metric Explosion. The URL is no longer included in the metric name. Fix: Make Cookie parsing more robust when running on Netty Cases where the Cookie header was malformed were causing exceptions to be thrown. Agent now makes a better effort to capture the individual valid parts. Fix: Agent could not connect to New Relic in non-DNS environments Fixed an issue which caused the agent to only be able to connect to New Relic in environments where DNS was used for hostname resolution. Fix: In 2.21.2 and 2.21.3 an @Trace annotation ignored the transaction for Apdex An @Trace annotation on a method called in a web transaction had the side-effect of ignoring the transaction for calculating the Apdex score.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2214","eolDate":"2016-09-10"},{"agent":"java","date":"2013-08-13","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.21.3/","version":"2.21.3","features":[],"bugs":["Agent did not run with J2SE 5.0"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: Agent did not run with J2SE 5.0 (aka JDK 1.5) Release 2.21.0 - 2.21.2 did not run correctly on J2SE 5.0. On startup, the agent reports: If you are running J2SE 5.0, please update to agent version 2.21.3.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2213","eolDate":"2016-08-13"},{"agent":"java","date":"2013-08-10","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.21.2/","version":"2.21.2","features":[],"bugs":["Longer application startup time","File location changes"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: Longer application startup time Release 2.21.0 introduced an issue that could cause application startup to be slower than in previously releases. This fix returns application startup time to normal. Fix: File location changes Release 2.21.0 introduced a change to file locations within the newrelic zip file. This fix reverts the locations to what they were previously.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2212","eolDate":"2016-08-10"},{"agent":"java","date":"2013-08-09","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.21.1/","version":"2.21.1","features":[],"bugs":["Fix for NoClassDefFoundError with NewRelic API"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: In 2.21.0, calls to NewRelic class can cause NoClassDefFoundError In 2.21.0, if your application calls the NewRelic class and does not include the newrelic-api.jar, the application would throw a NoClassDefFoundError. With this fix, the separate newrelic-api.jar is not required. However, it is recommended that your application include the newrelic-api.jar so that calls to the NewRelic API resolve with or without the agent installed.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2211","eolDate":"2016-08-09"},{"agent":"java","date":"2013-08-07","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.21.0/","version":"2.21.0","features":["X-Ray sessions","Improved compatibility with Java 1.5"],"bugs":["@Trace annotation ignored the transaction for Apdex","HTTP status code for Errors","Spring exception handling","Reading Post Parameters for Resin 3","JVM Tab Metrics Not Showing up for Tomcat Applications","Reduce DNS problems","JVM tab metrics showing for all Applications In JVM","Using a Proxy now works with SSL Enabled","Akka error reporting"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 X-Ray sessions Adds support for X-Ray sessions. An X-Ray session collects Transaction Traces and a thread profile for a Key Transaction. Fix: In 2.20.0 an @Trace annotation ignored the transaction for Apdex An @Trace annotation on a method called in a web transaction had the side-effect of ignoring the transaction for calculating the Apdex score. Fix: HTTP status code for Errors If the HTTP status code for a web transaction was less than 400, the HTTP status code reported in the error was 500. The actual status code for the web request is now reported. Fix: Spring exception handling The Exception argument in the Spring DispatcherServlet processHandlerException method was reported as an Error with an HTTP status code of 500. The actual status code in the HTTP response is now reported. Fix: Reading Post Parameters for Resin 3 Prior to this fix, post parameters in Resin 3 were always read using the default properties even if the application tried to read the post parameters using non-default properties or by just grabbing the request input stream. Fix: JVM Tab Metrics Not Showing up for Tomcat Applications Prior to this fix, if the service name in service.xml was not Catalina, then metrics would not appear under the JVM tab. Additionally, if you are using an embedded Tomcat 5/6, metrics should now appear under the JVM tab. Fix: Improved compatibility with Java 1.5 In the custom xml validator, there were references to String.isEmpty() which was not available until Java 1.6. Those have been removed. Fix: Reducing DNS problems by not automatically adding '.' to the domain name By default the '.' is included. But if changed, then the '.' won't be added. Fix: JVM tab metrics showing for all Applications In JVM Metrics under the Thread, Session, and Transaction tabs used to only appear under the main application. The data will now be shown for all applications running in the specific JVM. Fix: Using a Proxy now works with SSL Enabled In prior releases proxy authentication would fail when SSL was enabled. We now do proxy authentication using the java.net.Authenticator. Fix: Akka error reporting If an actor throws an exception or the message times out, an error is reported. Previously, no error was reported.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2210","eolDate":"2016-08-07"},{"agent":"java","date":"2011-12-29","downloadLink":null,"version":"2.2.1","features":[],"bugs":["ClassFormatError and NoClassDefFoundError instrumenting proxy classes","Transaction trace threshold not working","Infinite loop instrumenting parameterized SQL statements"],"security":[],"supportedOperatingSystems":null,"description":"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 Bug fix: ClassFormatError and NoClassDefFoundError instrumenting proxy classes Bug fix: transaction trace threshold not working (introduced in 2.2.0) Bug fix: infinite loop instrumenting parameterized SQL statements","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-221","eolDate":"2014-12-29"},{"agent":"java","date":"2013-07-01","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.20.0/","version":"2.20.0","features":["Glassfish 2.1 JVM tab"],"bugs":["Solr cache metrics","Fix NullPointerException","Support custom extension XML file for WebSphere"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Glassfish 2.1 JVM tab: The JVM tab will now show thread, session, and transaction metrics for Glassfish 2.1. Fix: Solr cache metrics: The solr cache metrics do not appear with versions 2.18 and 2.19 of the agent. This has been fixed, and all solr metrics should now appear. Fix: NullPointerException in New Relic agent logs when NewRelic API called: In certain circumstances, a call to a method on the NewRelic class can generate a NullPointerException in the agent logs. It does not cause a NullPointerException in your application. Fix: Support custom extension XML file for WebSphere with JRE: Prior to this fix, an attempt to use a custom extension XML file with a IBM JRE would lead to a ClassNotFoundException.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2200","eolDate":"2016-07-01"},{"agent":"java","date":"2011-12-06","downloadLink":null,"version":"2.2.0","features":["Performance improvements","Support server-side configuration"],"bugs":["Byte-code instrumentation causes class loading deadlock and OS memory explosion"],"security":[],"supportedOperatingSystems":null,"description":"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 Performance improvements Support server-side configuration Bug fix: byte-code instrumentation causes class loading deadlock and OS memory explosion","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-220","eolDate":"2014-12-06"},{"agent":"java","date":"2013-06-14","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.19.1/","version":"2.19.1","features":[],"bugs":["Play now captures GET and POST parameters correctly if capture_params is enabled","Disabled instrumentation used to time template rendering for Play 2"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix for 2.19.0 known issue: Play now captures GET and POST parameters correctly if capture_params is enabled. Disabled overly ambitious instrumentation used to time template rendering for Play 2. Resulted in unintended classes being instrumented.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2191","eolDate":"2016-06-14"},{"agent":"java","date":"2013-05-29","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.19.0/","version":"2.19.0","features":["Play 2 Instrumentation","Support added for Jetty 9"],"bugs":["Agent can cause java.lang.VerifyError on code compiled with Java 7","The Java Agent detects status codes for Apache Felix correctly by default"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Play 2 Instrumentation Provides insight into Play 2.x Java and Scala applications. Adds instrumentation to Netty server, Akka actor calls, Scala Promises and Futures, and the WS API calls. Known issue: Request parameters are not captured properly even if capture_params is enabled. Support added for Jetty 9 (tested on 9.0.0 through Jetty 9.0.3). Fix: Agent can cause java.lang.VerifyError on code compiled with Java 7 In certain cases, if your application code or third party libraries are compiled with Java 7, you may get a java.lang.VerifyError. This fix allows the agent to work correctly in those cases. Fix: The Java Agent detects status codes for Apache Felix correctly by default. The property take_last_status is now deprecated.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2190","eolDate":"2016-05-29"},{"agent":"java","date":"2013-05-07","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.18.0/","version":"2.18.0","features":["New metrics are displayed under the JVM tab"],"bugs":["When naming transactions, the property enable_auto_transaction_naming should be honored","Strip query string from HTTP Referer"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 New metrics are displayed under the JVM tab While the metrics displayed differ between application servers, common metrics include loaded class count, active thread count, active thread count per thread pool, active session count per application, and active transaction count. In order to see these metrics, JMX must be enabled on your app server. Fix: When naming transactions, the property enable_auto_transaction_naming should be honored There was an issue where transactions using the Spring Framework were ignoring the property. Fix: Strip query string from HTTP Referer Query strings can potentially contain sensitive information. To prevent that data from being sent to New Relic, only the host and path portion of the referer are captured.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2180","eolDate":"2016-05-07"},{"agent":"java","date":"2013-04-17","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.17.2/","version":"2.17.2","features":[],"bugs":["Fixed bug in which application code can throw NoSuchMethodError"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: Fixed bug in which application code can throw NoSuchMethodError In some cases using Java agent 2.17.0 and 2.17.1, application code was throwing an exception java.lang.NoSuchMethodError: java.lang.Boolean.valueOf(B)Ljava/lang/Byte; This usually occurred when calling a ResultSet implementation.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2172","eolDate":"2016-04-17"},{"agent":"java","date":"2013-04-12","downloadLink":null,"version":"2.17.1","features":[],"bugs":["Reverted transaction naming change on ColdFusion"],"security":[],"supportedOperatingSystems":null,"description":"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 Fix: Reverted transaction naming change on ColdFusion, introduced in 2.17.0. That change caused issues with certain modes of ColdFusion.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2171","eolDate":"2016-04-12"},{"agent":"java","date":"2013-04-11","downloadLink":null,"version":"2.17.0","features":["Agent reports JDBC ResultSet query time","Adds a stack trace in a transaction trace for all methods taking longer than stack trace threshold","Better transaction naming on ColdFusion"],"bugs":["Avoid retransform exception on IBM JREs"],"security":[],"supportedOperatingSystems":null,"description":"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 reports JDBC ResultSet query time This change gives you deeper insight into your database time by displaying ResultSet processing time in aggregate metrics and transaction traces. Fix: Avoid retransform exception on IBM JREs In some IBM JRE versions, the agent logged an INFO level exception and did not instrument select classes. This fix allows these classes to be instrumented properly. Adds a stack trace in a transaction trace for all methods taking longer than stack trace threshold. This differs from 2.16 which only provided stack traces for a limited number of methods. Better transaction naming on ColdFusion","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2170","eolDate":"2016-04-11"},{"agent":"java","date":"2013-03-25","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.16.0/","version":"2.16.0","features":["Adds a stack trace in the transaction trace for slow methods","Cross Application Tracing support for HttpURLConnection","Queuing time more broadly supported"],"bugs":["Cross Application Tracing does not correlate consistently when using WebSphere, WebLogic, Resin, and Glassfish","Work-around for Oracle JVM bug that in rare cases causes a native memory leak"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Adds a stack trace in the transaction trace for slow methods. This change provides additional insight into your slowest transactions.You can adjust how slow a method is before it generates the stack trace by setting stack_trace_treshold (in seconds). Cross Application Tracing support for HttpURLConnection. Adds request and response headers to external calls using the HttpURLConnection library to provided better performance data when calling applications monitored by other New Relic Agents (Java, .NET, and Ruby, with others coming soon). Fix: Cross Application Tracing does not correlate consistently when using WebSphere, WebLogic, Resin, and Glassfish. Cross Appplication Tracing did not correlate calling and called applications when the HTTP response was large. Queuing time more broadly supported. The 'X-Queue-Start' and 'X-Request-Start' request headers for Heroku and other frontend web servers are interpreted and reported. Previously, queuing time was not reported for Heroku. Work-around for Oracle JVM bug that in rare cases causes a native memory leak In rare cases, the Oracle JVM can leak native OS memory (not heap space) when classes are intercepted by the agent. This setting turns off interception of classes that are loaded after the given number of seconds. The agent will continue to monitor classes loaded before this time.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2160","eolDate":"2016-03-25"},{"agent":"java","date":"2013-03-13","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.15.1/","version":"2.15.1","features":[],"bugs":["Cross Application Tracing does not correlate consistently when using Tomcat 6+"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: Cross Application Tracing does not correlate consistently when using Tomcat 6+ Cross Appplication Tracing did not correlate calling and called applications when the called application ran in Tomcat 6 or later and the HTTP response was greater than about 7k.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2151","eolDate":"2016-03-13"},{"agent":"java","date":"2013-02-28","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.15.0/","version":"2.15.0","features":["Cross Application Tracing added","Instrumentation for AmazonS3Client version 1.x","Java Agent supports a daily roll over log","Java Agent now communicates with New Relic via HTTPS by default","Java Agent installer improvements"],"bugs":["Default hostname reported","Web transactions naming in Spring MVC version 3.x"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Cross Application Tracing The Cross Application Tracing feature adds request and response headers to external calls using the Apache HttpClient libraries to provided better performance data when calling applications monitored by other New Relic Agents (Java, .NET, and Ruby, with others coming soon). The 2.14.0 release links aggregated data across applications. This release also links transaction traces. The configuration setting introduced in 2.14.0 to enable/disable Cross Application Tracing in newrelic.yml has changed. The old setting: 'cross_application_tracing: true' is deprecated. The new setting is cross_application_tracer:   enabled: true The default setting is true. Set to false to disable Cross Application Tracing. Instrumentation added for the AmazonS3Client version 1.x The New Relic Agent now offers support for version 1.0 to current of the com.amazonaws.services.s3.AmazonS3 interface. New Relic Java Agent support a daily roll over log To roll over the agent log every day, set the property log_daily to true. Set the property log_file_count to the number of day logs you would like to keep. New Relic Java Agent now communicates with New Relic via HTTPS by default rather than HTTP If you have an existing installation and wish to use HTTPS to communicate with New Relic, edit your newrelic.yml file to include ssl: true in the common section. We recommend this for existing customers in order to improve the security of your communications with New Relic. Java Agent installer improvements The Java Agent installer now supports JBoss 7.x AS and JBoss 6.x EAP in standalone mode. Instructions for manually installing the Java Agent on JBoss 7.x AS and JBoss 6.x EAP can be found at https://newrelic.com/docs/java/installing-the-java-agent-on-jboss . Fix: Default hostname reported This release reverts the change in 2.14.0 that effected the way that the hostname is reported. With this release, the agent reports the default hostname rather than short form in order to correlate with New Relic server monitoring. Fix: Web transactions naming in Spring MVC version 3.x This bug caused customers using Spring 3.0.1 and above to often have web transactions named by the servlet rather than controller method. This has been fixed such that a separate metric is created for each controller method.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2150","eolDate":"2016-02-28"},{"agent":"java","date":"2013-02-15","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.14.1/","version":"2.14.1","features":[],"bugs":["Application errors using java.net.HttpURLConnection"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: Application errors using java.net.HttpURLConnection. The bug, introduced in 2.14.0, could cause errors in code that uses java.net.HttpURLConnection. Possible errors could occur in XML parsing, incorrect http response status, or BeanCreationException in Spring. As part of this fix the agent does not add a 'X-NewRelic-ID' header to outbound requests using java.net.HttpURLConnection.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2141","eolDate":"2016-02-15"},{"agent":"java","date":"2013-02-08","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.14.0/","version":"2.14.0","features":["Adds a X-NewRelic-ID header to outbound requests using the Apache HttpClient or HttpURLConnection libraries","Add report of physical server memory on Unix/Linux machines"],"bugs":["Includes property take_last_status to only grab the final http status code","Now correctly patches Apache Felix ClassLoaders","Time will now display correctly for the first hour of the day when using log4j","RUM header was missing a semicolon at the end of the last statement","Java agent now reports hostnames consistent with the output of hostname -s"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Fix: New Relic includes property take_last_status to only grab the final http status code. By default, New Relic reports any error status code. However, when this property is set to true, only the last http status code will be reported. This property should be set when using Apache Felix. Fix: New Relic now correctly patches Apache Felix ClassLoaders. Fix: Time will now display correctly for the first hour of the day when using log4j. Fix: RUM header was missing a semicolon at the end of the last statement. Some browsers prefer semicolons everywhere. Adds a X-NewRelic-ID header to outbound requests using the Apache HttpClient or HttpURLConnection libraries. This change helps improve the correlation of performance between services in a service-oriented architecture for a forthcoming feature. In the meantime, if you wish to disable the header, set 'cross_application_tracing: false' in newrelic.yml. Fix: Java agent now reports hostnames consistent with the output of \"hostname -s\" to match all other agents Add report of physical server memory (in addition to JVM memory) on Unix/Linux machines","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2140","eolDate":"2016-02-08"},{"agent":"java","date":"2013-01-16","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.13.0/","version":"2.13.0","features":["Agent can be configured to not send JVM arguments","Agent reports full URL in external service calls for transaction traces","Agent logging improvements"],"bugs":["ResinServletTracerFactory no longer causing SkipServletTracerFactory errors"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 can be configured to not send JVM arguments to the New Relic server The property send_jvm_props can be set to false, which will cause JVM arguments to no longer be sent to the server. Use this setting if you set sensitive system properties on the command line. Agent reports full URL in external service calls for transaction traces The agent now will provide the full URL if available in transaction traces for external calls. Fix: ResinServletTracerFactory no longer causing SkipServletTracerFactory errors When hitting the ResinServletTracerFactory inside a transaction, a SkipServletTracerFactory excetion will no longer be thrown. Agent logging improvements We have improved the clarity of logging messages, adjusted logging levels to be more appropriate, and increased logging performance.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2130","eolDate":"2016-01-16"},{"agent":"java","date":"2012-12-06","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.12.0/","version":"2.12.0","features":["Agent reports jars used by applications to the Environments tab"],"bugs":["Auto-RUM of JSP breaks HTML","Key Transaction ApdexT value not used","With OC4J using PolicyClassLoader, no metrics displayed","External metrics for HttpClient include port if host is an IP address"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 reports jars used by applications to the Environments tab in the UI The Environments tab in the New Relic UI now shows the jars used by your application. Fix: In certain cases, auto-RUM of JSP breaks HTML An angle-bracket in quotes in a META tag causes the agent to produce invalid HTML for JSP. The fix produces valid HTML for this case. Fix: Key Transaction ApdexT value not used In v2.10 - v2.11, the application-level ApdexT value is used for Key Transactions rather than the ApdexT for the Key Transaction itself. In this release, the ApdexT for the Key Transaction is used. Fix: With OC4J using PolicyClassLoader, no metrics displayed In the case where OC4J uses the PolicyClassLoader, the agent generates a java.lang.StackOverflowError in the log and does not provide metrics. In this release, the error does not occur. Fix: External metrics for HttpClient include port if host is an IP address In the case where an external service call uses HttpClient with an IP address rather than a hostname, the port number is also included. In this release, the port number is not displayed.","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2120","eolDate":"2015-12-06"},{"agent":"java","date":"2011-11-07","downloadLink":null,"version":"2.1.2","features":["Performance improvements"],"bugs":["Parse inner select SQL statements","Execute SQL statement not recognized"],"security":[],"supportedOperatingSystems":null,"description":"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 Performance improvements Bug fix: parse inner select SQL statements Bug fix: execute SQL statement not recognized","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-212","eolDate":"2014-11-07"},{"agent":"java","date":"2012-11-28","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.11.0/","version":"2.11.0","features":["Support Jetty Continuations","Support Servlet 3.0 async API for WebSphere"],"bugs":["ClassCircularityError in JBoss","Agent does not detect Solr 4.0","NewRelicIgnoreApdex annotation ignored"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Jetty Continuations Support Servlet 3.0 async API for WebSphere Bug fix: java.lang.ClassCircularityError in JBoss Bug fix: Agent does not detect Solr 4.0 Bug fix: NewRelicIgnoreApdex annotation ignored","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2110","eolDate":"2015-11-28"},{"agent":"java","date":"2012-11-13","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.10.1/","version":"2.10.1","features":["Remove stall detection"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Remove stall detection","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2101","eolDate":"2015-11-13"},{"agent":"java","date":"2012-10-31","downloadLink":"https://download.newrelic.com/newrelic/java-agent/newrelic-agent/2.10.0/","version":"2.10.0","features":["Instrumentation of Servlet 3.0 async processing","Custom instrumentation configured through an XML file","Request attribute for setting app name now allows multiple app names"],"bugs":["Auto RUM inserts header and footer into script tags"],"security":[],"supportedOperatingSystems":null,"description":"Download this agent version 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 Instrumentation of Servlet 3.0 async processing. Processing initiated by startAsync is included in metrics and transaction traces. Custom instrumentation configured through an XML file. For details see the documentation. Request attribute for setting app name now allows multiple app names Bug fix: auto RUM inserts header and footer into script tags","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-2100","eolDate":"2015-10-31"},{"agent":"java","date":"2011-10-07","downloadLink":null,"version":"2.1.0","features":["Report slow SQL statements","Performance improvements","Continue to record metrics after transaction trace limit is reached"],"bugs":["Never drop data","Agent destructively reads request parameters in Resin","Default transaction trace threshold should be apdex_f","Don't obfuscate digits in SQL statements that are part of table name"],"security":[],"supportedOperatingSystems":null,"description":"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 Report slow SQL statements Performance improvements Continue to record metrics after transaction trace limit is reached Bug fix: never drop data Bug fix: Agent destructively reads request parameters in Resin Bug fix: default transaction trace threshold should be apdex_f Bug fix: Don't obfuscate digits in SQL statements that are part of table name","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-210","eolDate":"2014-10-07"},{"agent":"java","date":"2011-08-30","downloadLink":null,"version":"2.0.4","features":["Allow logging to standard out","Allow configuration of the agent via environment variables"],"bugs":["RUM: handle duplicate injection of our JS header and footer","Fix the license key hint that is inserted into the auto-generated configuration file"],"security":[],"supportedOperatingSystems":null,"description":"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 Bug fix: RUM: handle duplicate injection of our JS header and footer Bug fix: fix the license key hint that is inserted into the auto-generated configuration file Allow logging to standard out Allow configuration of the agent via environment variables","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-204","eolDate":"2014-08-30"},{"agent":"java","date":"2011-08-04","downloadLink":null,"version":"2.0.3","features":[],"bugs":["RUM: Tag files not compiling in Jasper","RUM: header not always inserted after meta tags","NullPointerException if filter config is null","Fix IE measurement problem in RUM footer","API calls should not throw exceptions"],"security":[],"supportedOperatingSystems":null,"description":"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 Bug fix: RUM: Tag files not compiling in Jasper Bug fix: RUM: header not always inserted after meta tags Bug fix: NullPointerException if filter config is null Bug fix: Fix IE measurement problem in RUM footer Bug fix: API calls should not throw exceptions","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-203","eolDate":"2014-08-04"},{"agent":"java","date":"2011-06-16","downloadLink":null,"version":"2.0.2","features":["Installer support for Glassfish"],"bugs":["Auto RUM compiler error instrumenting some JSPs","Auto RUM should inject header after meta tags","Installer does not modify start script if another javaagent switch is present","Agent breaks request URI parsing in Tomcat: JSESSIONID not removed","Some compilers unable to compile JSP with auto RUM"],"security":[],"supportedOperatingSystems":null,"description":"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 Bug fix: Auto RUM compiler error instrumenting some JSPs Bug fix: Auto RUM should inject header after meta tags Bug fix: Installer does not modify start script if another javaagent switch is present Bug fix: Agent breaks request URI parsing in Tomcat: JSESSIONID not removed (introduced in 1.4.0) Bug fix: Some compilers unable to compile JSP with auto RUM Installer support for Glassfish","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-202","eolDate":"2014-06-16"},{"agent":"java","date":"2011-05-23","downloadLink":null,"version":"2.0.1","features":[],"bugs":["JBoss fails to start with JMX errors"],"security":[],"supportedOperatingSystems":null,"description":"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 Bug fix: JBoss fails to start with JMX errors (introduced in 1.4.0)","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-201","eolDate":"2014-05-23"},{"agent":"java","date":"2011-05-09","downloadLink":null,"version":"2.0.0","features":["Auto Real User Monitoring","Support for X-Request-Start, X-Queue-Start, and X-Queue-Time request headers"],"bugs":["newrelic-api.jar does not work with Java 1.5","NullPointerException instrumenting HttpClient","Setting request attribute 'com.newrelic.agent.TRANSACTION_NAME' not working","Uncaught exceptions not logged during startup","Thread profiling fails if CPU time not supported","Error is ignored only if it is the root cause"],"security":[],"supportedOperatingSystems":null,"description":"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 Auto Real User Monitoring Support for X-Request-Start, X-Queue-Start, and X-Queue-Time request headers Bug fix: newrelic-api.jar does not work with Java 1.5 Bug fix: NullPointerException instrumenting HttpClient Bug fix: setting request attribute \"com.newrelic.agent.TRANSACTION_NAME\" not working (broken in 1.4.0) Bug fix: uncaught exceptions not logged during startup Bug fix: thread profiling fails if CPU time not supported Bug fix: error is ignored only if it is the root cause","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-200","eolDate":"2014-05-09"},{"agent":"java","date":"2011-04-11","downloadLink":null,"version":"1.4.0","features":["Real User Monitoring"],"bugs":["Setting 'ignore_status_codes' to a single value is ignored"],"security":[],"supportedOperatingSystems":null,"description":"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: Real User Monitoring Bug fix: setting 'ignore_status_codes' to a single value is ignored","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-140","eolDate":"2014-04-11"},{"agent":"java","date":"2011-03-17","downloadLink":null,"version":"1.3.0","features":["Component-based transaction naming","Agent API","Multiple applications enhancements","Send data to RPM in UTF-8 format"],"bugs":["ClassCastException setting record_sql: off"],"security":[],"supportedOperatingSystems":null,"description":"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: Component-based transaction naming Agent API Multiple applications enhancements Send data to RPM in UTF-8 format Bug fix: ClassCastException setting record_sql: off","slug":"docs/release-notes/agent-release-notes/java-release-notes/java-agent-130","eolDate":"2014-03-17"},{"agent":"go","date":"2020-09-03","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.9.0","version":"3.9.0","features":["When sending serverless telemetry using the nrlambda integration, the agent now support an externally-managed named pipe"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"3.9.0 Changes When sending Serverless telemetry using the nrlambda integration, support an externally-managed named pipe. The articles below provide additional instructions on support for an externally-managed named pipe in lambdas: Legacy manual instrumentation Enable monitoring for AWS Lambda Layer installation instructions Sample Go application","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-390","eolDate":"2023-09-03"},{"agent":"go","date":"2020-07-15","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.8.1","version":"3.8.1","features":[],"bugs":["Fixed an issue that could cause orphaned Distributed Trace spans when using SQL instrumentation"],"security":[],"supportedOperatingSystems":null,"description":"3.8.1 Bug Fixes Fixed an issue that could cause orphaned Distributed Trace spans when using SQL instrumentation like nrmysql.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-381","eolDate":"2023-07-15"},{"agent":"go","date":"2020-07-01","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.8.0","version":"3.8.0","features":["It is now possible to include a host field in web transactions in the WebRequest struct"],"bugs":["Fixed an issue where spans and transactions timestamps could be offset incorrectly in the UI","The host header is now being correctly captured and recorded in the request.headers.host attribute"],"security":[],"supportedOperatingSystems":null,"description":"3.8.0 Changes When marking a transaction as a web transaction using Transaction.SetWebRequest , it is now possible to include a Host field in the WebRequest  struct, which defaults to the empty string. Bug Fixes The Host header is now being correctly captured and recorded in the request.headers.host attribute, as described here . Previously, the timestamps on Spans and Transactions were being written using different data types, which sometimes caused rounding errors that could cause spans to be offset incorrectly in the UI. This has been fixed.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-380","eolDate":"2023-07-01"},{"agent":"go","date":"2020-06-18","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.7.0","version":"3.7.0","features":["If a time out when attempting to send data, instead of dropping the data, the agent will save it and attempt to send it with the next harvest"],"bugs":["Fixed a bug where a bad https connection which uses Header.Set could potentially block all https requests"],"security":[],"supportedOperatingSystems":null,"description":"3.7.0 Changes When Config.Transport is nil, no longer use the http.DefaultTransport when communicating with the New Relic backend. This addresses an issue with shared transports as described in golang/go#33006 . If a timeout occurs when attempting to send data to the New Relic backend, instead of dropping the data, we save it and attempt to send it with the next harvest. Note data retention limits  still apply and the agent will still start to drop data when these limits are reached. We attempt to keep the highest priority events and traces.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-370","eolDate":"2023-06-18"},{"agent":"go","date":"2020-06-09","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.6.0","version":"3.6.0","features":["Add custom attributes directly to spans"],"bugs":["Fixed bug where it was impossible to exclude error.class and error.message attributes from the root span","Fixed bug that caused Go's data race warnings to trigger when using newrelic.NewRoundTripper"],"security":[],"supportedOperatingSystems":null,"description":"3.6.0 New Features Added support for adding custom attributes directly to spans . These attributes will be visible when looking at spans in the distributed tracing UI. Example: Custom attributes added to the transaction with txn.AddAttribute are now also added to the root span and will be visible when looking at the span in the distributed tracing UI. These custom attributes can be disabled from all destinations using Config.Attributes.Exclude or disabled from spans specifically using Config.SpanEvents.Attributes.Exclude. Agent attributes added to the transaction are now also added to the root span event and will be visible when looking at the span in the distributed tracing UI. These attributes include the request.uri and the request.method along with all other attributes listed in the attributes section of our godocs . These agent attributes can be disabled from all destinations using Config.Attributes.Exclude or disabled from spans specifically using Config.SpanEvents.Attributes.Exclude. Bug Fixes Fixed an issue where it was impossible to exclude the attributes error.class and error.message from the root span. This issue has now been fixed. These attributes can now be excluded from all spans using Config.Attributes.Exclude or Config.SpanEvents.Attributes.Exclude. Fixed an issue that caused Go's data race warnings to trigger in certain situations when using the newrelic.NewRoundTripper. There were no reports of actual data corruption, but now the warnings should be resolved. Thank you to @blixt for bringing this to our attention!","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-360","eolDate":"2023-06-09"},{"agent":"go","date":"2020-05-20","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.5.0","version":"3.5.0","features":["Added support for Infinite Tracing"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"3.5.0 New Features Added support for Infinite Tracing on New Relic Edge . Infinite Tracing observes 100% of your distributed traces and provides visualizations for the most actionable data so you have the examples of errors and long-running traces so you can better diagnose and troubleshoot your systems. You configure your agent  to send traces to a trace observer in New Relic Edge. You view your distributed traces through the New Relic’s UI. There is no need to install a collector on your network. Infinite Tracing is currently available on a sign-up basis. If you would like to participate, please contact your sales representative. Changes nrgin.Middleware  uses Context.FullPath()  for transaction names when using Gin version 1.5.0 or greater. Gin transactions were formerly named after the Context.HandlerName() , which uses reflection. This change improves transaction naming and reduces overhead. Please note that because your transaction names will change, you may have to update any related dashboards and alerts to match the new name. If you wish to continue using Context.HandlerName() for your transaction names, use nrgin.MiddlewareHandlerTxnNames  instead. Note: As part of agent release v3.4.0, a v2.0.0 tag was added to the nrgin package. When using go modules however, it was impossible to install this latest version of nrgin. The v2.0.0 tag has been removed and replaced with v1.1.0.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-350","eolDate":"2023-05-20"},{"agent":"go","date":"2020-03-23","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.4.0","version":"3.4.0","features":null,"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"3.4.0 New Features Attribute http.statusCode has been added to external span events representing the status code on an http response. This attribute will be included when added to an ExternalSegment in one of these three ways: Using NewRoundTripper  with your http.Client Including the http.Response as a field on your ExternalSegment Using the new ExternalSegment.SetStatusCode  API to set the status code directly To exclude the http.statusCode attribute from span events, update your agent configuration like so, where cfg is your newrelic.Config  object. Error attributes error.class and error.message are now included on the span event in which the error was noticed, or on the root span if an error occurs in a transaction with no segments (no chid spans). Only the most recent error information is added to the attributes; prior errors on the same span are overwritten. To exclude the error.class and/or error.message attributes from span events, update your agent configuration like so, where cfg is your newrelic.Config  object. Changes Use Context.FullPath()  for transaction names when using Gin version 1.5.0 or greater. Gin transactions were formerly named after the Context.HandlerName() , which uses reflection. This change improves transaction naming and reduces overhead. Please note that because your transaction names will change, you may have to update any related dashboards and alerts to match the new name.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-340","eolDate":"2023-03-23"},{"agent":"go","date":"2020-02-11","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.3.0","version":"3.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"3.3.0 New Features Added support for GraphQL in two new integrations: graph-gophers/graphql-go  with v3/integrations/nrgraphgophers . Documentation Example graphql-go/graphql  with v3/integrations/nrgraphqlgo . Documentation Example Added database instrumentation support for snowflakedb/gosnowflake . Documentation Example Changes When using newrelic.StartExternalSegment  or newrelic.NewRoundTripper , if existing cross application tracing or distributed tracing headers are present on the request, they will be replaced instead of added. The FromContext  API which allows you to pull a Transaction from a context.Context will no longer panic if the provided context is nil. In this case, a nil is returned. Known Issues and Workarounds If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream Go New Relic agents to this agent release.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-330","eolDate":"2023-02-11"},{"agent":"go","date":"2020-01-27","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.2.0","version":"3.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"3.2.0 New Features Added support for v7 of go-redis/redis  in the new v3/integrations/nrredis-v7  package. Documentation Example Changes Updated Gorilla instrumentation to include request time spent in middlewares. Added new nrgorilla.Middleware and deprecated nrgorilla.InstrumentRoutes. Register the new middleware as your first middleware using Router.Use . See the godocs examples  for more details. Known Issues and Workarounds If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream Go New Relic agents to this agent release.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-320","eolDate":"2023-01-27"},{"agent":"go","date":"2021-03-18","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.11.0","version":"3.11.0","features":["Aerospike is now included on the list of recognized datastore names","Added support for version 8 of go-redis"],"bugs":["Fixed a bug where stack traces would not be logged when the agent is configured with cfg.ErrorCollector.RecordPanics","Added license files to some integrations packages to ensure compatibility with package.go.dev","Changed logging levels for messages resulting from Infinite Tracing load balancing opeartions from being logged as errors to being logged from debugging messages"],"security":[],"supportedOperatingSystems":null,"description":"3.11.0 New Features Aerospike is now included on the list of recognized datastore names. Thanks @vkartik97 for your PR! #233 Added support for version 8 of go-redis. Thanks @ilmimris for adding this instrumentation! #251 Changes Changed logging level for messages resulting from Infinite Tracing load balancing operations. These were previously logged as errors, and now they are debugging messages. #276 Fixed When the agent is configured with cfg.ErrorCollector.RecordPanics set to true, panics would be recorded by New Relic, but stack traces would not be logged as the Go Runtime usually does. The agent now logs stack traces from within its panic handler, providing similar functionality. #278 Added license files to some integrations packages to ensure compatibility with package.go.dev. Now the documentation for our integrations shows up again on go.docs. Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3110","eolDate":"2023-03-18"},{"agent":"go","date":"2021-01-11","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.10.0","version":"3.10.0","features":[],"bugs":[],"security":["To keep up with the latest security protocols implemented by Amazon Web Services, the agent now uses AWS IMDSv2"],"supportedOperatingSystems":null,"description":"3.10.0 New Features To keep up with the latest security protocols implemented by Amazon Web Services, the agent now uses AWS IMDSv2  to find utilization data. #249 Changes Updated the locations of our license files so that Go docs https://pkg.go.dev  will display our agent. Thanks @tydavis for your PR to fix this! #254 Added an Open Source repo linter GitHub action that runs on push. #262 Updated the README.md file to correctly show the support resources from New Relic. #255 Support statement New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is 2.2.0 .","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3100","eolDate":"2023-01-11"},{"agent":"go","date":"2020-01-15","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.1.0","version":"3.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Support for W3C Trace Context, with easy upgrade from New Relic trace context. Distributed Tracing now supports W3C Trace Context headers for HTTP and gRPC protocols when distributed tracing is enabled. Our implementation can accept and emit both W3C trace header format and New Relic trace header format. This simplifies agent upgrades, allowing trace context to be propagated between services with older and newer releases of New Relic agents. W3C trace header format will always be accepted and emitted. New Relic trace header format will be accepted, and you can optionally disable emission of the New Relic trace header format. When distributed tracing is enabled with Config.DistributedTracer.Enabled = true, the Go agent will now accept W3C's traceparent and tracestate headers when calling Transaction.AcceptDistributedTraceHeaders . When calling Transaction.InsertDistributedTraceHeaders , the Go agent will include the W3C headers along with the New Relic distributed tracing header, unless the New Relic trace header format is disabled using Config.DistributedTracer.ExcludeNewRelicHeader = true. Also, see Knowns Issues and Workarounds. Added support for elastic/go-elasticsearch  in the new v3/integrations/nrelasticsearch-v7  package. Known Issues and Workarounds If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream Go New Relic agents to this agent release.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-310","eolDate":"2023-01-15"},{"agent":"go","date":"2019-12-17","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.0.0","version":"3.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"3.0.0 We are pleased to announce the release of Go Agent v3.0.0! This is a major release that includes some breaking changes that will simplify your future use of the Go Agent. Please pay close attention to the list of Changes. Changes A full list of changes and a step by step checklist on how to upgrade can be found in the v3 Migration Guide . New Features Support for Go Modules. Our Go agent integration packages support frameworks and libraries which are changing over time. With support for Go Modules, we are now able to release instrumentation packages for multiple versions of frameworks and libraries with a single agent release; and support operation of the Go agent in Go Modules environments. This affects naming of our integration packages, as described in the v3 Migration Guide (see under \"Changes\" above). Detect and set hostnames based on Heroku dyno names. When deploying an application in Heroku, the hostnames collected will now match the dyno name. This serves to greatly improve the usability of the servers list in APM since dyno names are often sporadic or fleeting in nature. The feature is controlled by two new configuration options Config.Heroku.UseDynoNames and Config.Heroku.DynoNamePrefixesToShorten.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-300","eolDate":"2022-12-17"},{"agent":"go","date":"2026-08-11","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.44.2","version":"3.44.2","features":["Add attribute for aws.lambda.eventSource.eventType"],"bugs":["Fixed TransactionTrace backtrace, exclusieDurationMs, and timestamp"],"security":["Dependabot bumps for nrgrpc and nrconnect"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.44.2 Added aws.lambda.eventSource.eventType attribute support for the nrlambda integration Fixed TransactionTrace fixes backtrace shows properly in the UI -> Fixed an issue where backtraces weren't properly displaying in NR1 timestamp no longer null -> Fixed an issue where timestamp always showed as null exclusive_duration_millis no longer null -> Fixed an issue where exclusive_duration_millis always showed as null Security Dependabot security updates nrgrpc bump google.golang.org/grpc to 1.82.1 nrconnect bump golang.org/x/net to 0.55.0 Support statement We use the latest version of the Go language. At a minimum, use a version of Go that the Go team still supports.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-44-2","eolDate":"2027-08-11"},{"agent":"go","date":"2026-06-22","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.44.1","version":"3.44.1","features":[],"bugs":["Corrected incorrect tag for previous release"],"security":["Dependabot bumps for nrgochi, nrmongo, nrmongo-v2, and nrnats"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.44.1 Fixed Corrected incorrect tag for previous release Security Dependabot security updates nrgochi integration updated to v5.2.4 nrmongo integration updated to v1.17.7 nrmongo-v2 integration updated to v2.4.2 nrnats integration updated to v2.11.15 Support statement We use the latest version of the Go language. At a minimum, use a version of Go that the Go team still supports.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-44-1","eolDate":"2027-06-22"},{"agent":"go","date":"2026-06-11","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.44.0","version":"3.44.0","features":["New Integration for Anthropic SDK","New Integration for GocqlX"],"bugs":["Unblocked integrationsupport testing","Fixed a bug in sqlparse to support optional INTO statements in sql integrations","Fixed a bug in rnats that caused flaky testing"],"security":["Bumped nrfiber"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.44.0 Added   * Added Support for Anthropic SDK nranthropic\n  * Added Support for GocqlX nrgocqlx Fixed   * Export Internal Test Types via integrationsupport to unblock external test consumers\n    * Thank you to community member @nitinprajwal for contributing to this solution\n  * Fixed a bug in sqlparse to support optional INTO statements in sql integrations\n  * Fixed a bug in nrnats that caused flaky testing Security   * Dependabot Security Bumps\n    * nrfiber Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-44-0","eolDate":"2027-06-11"},{"agent":"go","date":"2026-04-28","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.43.3","version":"3.43.3","features":["EXPERIMENTAL - Added a config option `ConfigAppLogDecoratingWithinMessage` to allow Local Log Decorator to appear within a message field.  This can only be applied to the `logcontext-v2/nrlogrus` integration. The `logcontext-v2/nrlogrus` integration will be bumped to v1.1.4."],"bugs":[],"security":["Dependabot security bumps for `nrawsbedrock`, `nrawssdk-v2`and `nrpgx5`"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.43.3 Feature EXPERIMENTAL: Added a config option ConfigAppLogDecoratingWithinMessage to allow Local Log Decorator to appear within a message field.  This can only be applied to the logcontext-v2/nrlogrus integration. The logcontext-v2/nrlogrus integration will be bumped to v1.1.4. Security Dependabot security bumps nrawsbedrock (integration will be bumped to v1.1.1) nrawssdk-v2 (integration will be bumped to v1.2.7) nrpgx5 (integration will be bumped to v1.3.4)` Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-43-3","eolDate":"2027-04-28"},{"agent":"go","date":"2026-04-16","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.43.2","version":"3.43.2","features":[],"bugs":["Fixed a bug in `replacementResponseWriter` where the `Unwrap` function wasn't being promoted as a part of an anoynmous struct"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.43.2 Fixed Fixed a bug in replacementResponseWriter where the Unwrap function wasn't being promoted as a part of an anoynmous struct Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-43-2","eolDate":"2027-04-16"},{"agent":"go","date":"2026-04-09","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.43.1","version":"3.43.1","features":[],"bugs":["Fixed a bug where we were importing the incorrect version of the `nrsecureagent` in our `nrgrpc` integration"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.43.1 Fixed Fixed a bug where we were importing the incorrect version of the nrsecureagent in our nrgrpc integration Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-43-1","eolDate":"2027-04-09"},{"agent":"go","date":"2026-04-02","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.43.0","version":"3.43.0","features":["Added Unwrap support for replacement response writer","Added support for lambda function URL request and response in the `nrlambda` integration","Added additional span attributes for opensearch/elasticssearch endpoints","Added support for 'WITH' clause in sqlparse"],"bugs":["Fixed failing httptest"],"security":["Bumped nrgrpc version","Dependabot security bumps for `logcontext/nrlogrus` `logcontext/nrlogrusplugin` `logcontext-v2/nrlogrus`and `nrfiber`"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.43.0 Added Added UnWrap support for replacement response writer Thank you to community member @ArturFortunato for contributing to this solution Added support for Lambda function URL request and response in the nrlambda integration Thank you to community member @rittneje for contributing to this solution Added additional Span attribute for Opensearch/elastic search endpoint in the nrawssdk integration Added Support for \"WITH\" clauses to sqlparse Fixed Fixed failing httptest Security Updated CI/CD go version Bumped nrgrpc version Dependabot security bumps logcontext/nrlogrus logcontext/nrlogrusplugin logcontext-v2/nrlogrus nrfiber Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-43-0","eolDate":"2027-04-02"},{"agent":"go","date":"2025-11-19","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.42.0","version":"3.42.0","features":["Added new max samples configuration options for Transactions, Custom Insights, Errors, and Logs","Added support for MultiValueHeaders in nrlambda"],"bugs":["Removed unused variables in nrpxg5","Fixed a bug where error events did not correctly mark expected errors"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.42.0 Added Added ConfigTransactionEventsMaxSamplesStoredand ConfigErrorCollectorMaxSamplesStored allowing full control of maximum samples stored for Transaction Events, Custom Insights Events, Error Events, and Log Events Added support for the MultiValueHeaders property when extracting the headers from events.APIGatewayProxyResponse in nrlambda Thank you to community member @rittneje for contributing to this solution Fixed Removed unused variables and modernize by replacing interface with any in the nrpxg5 integration Fixed a bug where error events did not correctly mark expected errors Thank you to community member @driimus for contributing to this solution Bumped nrwriter integration to use v1.0.2 Thank you to community member @hiicharm for spotting this. Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-42-0","eolDate":"2026-11-19"},{"agent":"go","date":"2025-09-24","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.41.0","version":"3.41.0","features":["Added Remote Parent Sampling"],"bugs":[],"security":["Bumped github.com/gofiber/fiber/v2 to v2.52.9","Bumped golang.org/x/net to v0.38.0"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.41.0 Added Added DistributedTracer.Sampler config options for controlling the sampling behavior for Inbound Requests for distributed traces To configure the sampler, added ConfigRemoteParentSampled(flag RemoteParentSamplingConfig) and ConfigRemoteParentNotSampled(flag RemoteParentSamplingConfig) which handles sampling behavior based on what the remote parent has flagged Flags added are \"always_on\", \"always_off\", and \"default\" which can be called using RemoteParentSamplingConfig Example: newrelic.ConfigRemoteParentSampled(newrelic.AlwaysOff) Added OOM Monitoring Tests Increased Secure Agent Test Coverage Fixed Updated third-party library versions due to reported security or other supportability issues: github.com/gofiber/fiber/v2 from 2.52.7 to 2.52.9 in nrfiber integration golang.org/x/net from 0.25.0 to 0.38.0 in nrconnect integration Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-41-0","eolDate":"2026-09-24"},{"agent":"go","date":"2025-07-18","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.40.1","version":"3.40.1","features":[],"bugs":["Reverted utilization.go back to v3.39.0","Removed awssupport_test.go tests that added direct dependencies to go module"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.40.1 Fixed Reverted utilization.go back to v3.39.0 release due to deadlock bug Removed awssupport_test.go tests that added direct dependencies to go module Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-40-1","eolDate":"2026-07-18"},{"agent":"go","date":"2025-07-16","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.40.0","version":"3.40.0","features":["Added `txn.IgnoreApdex()` function to ignore Apdex score for a given transaction","Added Custom Attributes via environment variables `NEW_RELIC_APPLICATION_LOGGING_FORWARDING_CUSTOM_ATTRIBUTES`","Added `nrconnect` integration for connect library. Connect is a slim library for building browser and gRPC-compatible HTTP APIs","Added `nrmongo-v2` integration supporting the mongodb-v2 library"],"bugs":["Overhauled GitHub Actions Test Suite","Enhanced query parameter representation in nrpgx5 integration","Fixed a bug where a race condition would occur in identifying container utilization","Capture DynamoDB table name and index name in DatastoreSegment"],"security":[" `github.com/gofiber/fiber/v2` to 2.52.7 in `nrfiber` integration","`github.com/go-chi/chi/v5` to 5.2.2 in `nrgochi` integration"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.40.0 Added Added txn.IgnoreApdex() function to ignore Apdex score for a given transaction Added Custom Attributes via environment variables NEW_RELIC_APPLICATION_LOGGING_FORWARDING_CUSTOM_ATTRIBUTES Added nrconnect integration for connect library. Connect is a slim library for building browser and gRPC-compatible HTTP APIs Thank you to community member @castaneai for contributing to this solution Added nrmongo-v2 integration supporting the mongodb-v2 library Overhauled GitHub Actions Test Suite Added dockerized database support for mongodb and pgx5 integrations Fixed Enhanced query parameter representation in nrpgx5 integration Fixed a bug where a race condition would occur in identifying container utilization. Capture DynamoDB table name and index name in DatastoreSegment Thank you to community member @rittneje for contributing to this solution Updated third-party library versions due to reported security or other supportability issues: github.com/gofiber/fiber/v2 to 2.52.7 in nrfiber integration github.com/go-chi/chi/v5 to 5.2.2 in nrgochi integration Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-40-0","eolDate":"2026-07-16"},{"agent":"go","date":"2025-05-08","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.39.0","version":"3.39.0","features":["Added nrfiber integration for go fiber framework","Updated nrslog example with new API","Added Optional Path Filtering to nrgin middleware","Added ConfigDatastoreKeysEnabled to nrreddis integration allowing for reporting the names of keys along with the datastore operations","Switched GitHub Action Testing Suite from an Emulated ARM layer to Native ARM layers","Added support for time objects for attribute values for nrslog"],"bugs":["Fixed linking metadata location in log messages"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.39.0 Added Added nrfiber integration for go fiber framework Thank you to community member @MitulShah1 for contributing to this solution Updated nrslog example with new API Thank you to community member @frankywahl for contributing to this solution Add Optional Path Filtering Function to nrgin Middleware Thank you to community member @frknikiz for contributing to this solution Added ConfigDatastoreKeysEnabled to nrreddis integration allowing for reporting the names of keys along with the datastore operations Switched GitHub Action Testing Suite from an Emulated ARM layer to Native ARM layers Added support for time objects for attribute values for nrslog Fixed Fixed linking metadata location in log messages Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-39-0","eolDate":"2026-05-08"},{"agent":"go","date":"2025-03-20","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.38.0","version":"3.38.0","features":["Created integration package for Go-Chi","Added IsEnded() method for transaction typs allowing for a straightforward approach to check if transactions are ended"],"bugs":["Added caveat to API docs about local log decoration in zap integration"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.38.0 Added Added new integration nrgochi v1.0.0 for support for go-chi library Added IsEnded() method for the Transaction type. Allowing for a straightforward approach to checking if a transaction has ended Community Member @frknikiz contributed to this solution Fixed Added caveat to API docs about local log decoration in zap integration Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-38-0","eolDate":"2026-03-20"},{"agent":"go","date":"2025-02-26","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.37.0","version":"3.37.0","features":["Created a 1.4 version of slog integration","Now custom application tags (labels) may be added to all forwarded log events","Added memory allocation limit detection/response mechanism to facilitate calling custom functions to perform application-specific resource management functionality"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.37.0 Added Implemented a new approach to integrating New Relic with SLOG that is more lightweight, out of the way, and collects richer data. These changes have been constructed to be completely backwards-compatible with v1 of nrslog. Changes include: Wrapping slog.Handler objects with errors to allow users to handle invalid use cases A complete rework of log enrichment so that New Relic linking metadata does not invalidate JSON, BSON, or YAML scanners. This new approach will instead inject the linking metadata as a key-value pair. Complete support for With(), WithGroup(), and attributes for automatic instrumentation. Performance operations. Robust testing (close to 90% coverage). This updates logcontext-v2/nrslog to v1.4.0. Now custom application tags (labels) may be added to all forwarded log events. Enabled if ConfigAppLogForwardingLabelsEnabled(true) or NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LABELS_ENABLED=TRUE May exclude labels named in ConfigAppLogForwardingLabelsExclude(\"label1\",\"label2\",...) or NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LABELS_EXCLUDE=\"label1,label2,...\" Labels are defined via ConfigLabels(...) or NEW_RELIC_LABELS Added memory allocation limit detection/response mechanism to facilitate calling custom functions to perform application-specific resource management functionality, report custom metrics or events, or take other appropriate actions, in response to rising heap memory size. Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-37-0","eolDate":"2026-02-26"},{"agent":"go","date":"2025-01-16","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.36.0","version":"3.36.0","features":["Security agent improvements"],"bugs":["Added missing license files","Fixed module dependencies in nrgrpc integration","corrects handling of panic(nil)"],"security":[""],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.36.0 Enhanced Internal improvements to securityagent integration to better support trace handling and other support for security analysis of applications under test, now v1.3.4; affects the following other integrations: nrecho, now v1.1.4 nrecho-v4, now v1.1.3 nrgin, now v1.3.3 nrgorilla, now v1.2.3 nrgraphqlgo, now v1.0.2 nrhttprouter, now v1.1.3 Fixed Added missing license files. Fixed module dependencies in nrgrpc integration, now v1.4.5 Corrects handling of panic(nil) to no longer try to keep pre-Go-1.21 behavior but to allow newer language semantics for that condition. Fixes issue 975 .","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-36-0","eolDate":"2026-01-16"},{"agent":"go","date":"2024-10-24","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.35.1","version":"3.35.1","features":["Faster Trace ID generation"],"bugs":["Security agent bug hotfix: Don't update the security agent until the Go agent has completed its connect process"],"security":[""],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.35.1 Fixed Security agent bug hotfix: Don't update the security agent until the Go agent has completed its connect process PR Faster Trace ID generation Community member @ankon  contributed this change Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-35-1","eolDate":"2025-10-24"},{"agent":"go","date":"2024-10-10","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.35.0","version":"3.35.0","features":["Enables sharing of response headers with the csec-security-agent","`error.Error()` value for log attributes","Enhanced url support for amqp server connections"],"bugs":["nrawssdk-v2 integration examples of `AppendMiddlewares` corrected","Zerolog integration correction to example program `import` statement","Zerolog integration JSON parser bug caused a runtime panic in some circumstances","Fixed handling of `panic(nil)`. This was made necessary by changes introducted to Go as of 1.21","Fixed a race condition that was possible due to code level metrics accessing a contended memory address","Fixed an issue where Integer size flagged when converting unsigned to signed values","Workflow corrections for CI processes in github"],"security":[""],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.35.0 Added Enhanced security features (adds support for secure cookie even reporting) Enables sharing of response headers with the csec-security-agent. Now uses error.Error() value for log attributes Thanks to @ejsolberg for the PR nramqp integration cloud services entity relationship changes Enhances url support for amqp server connections Fixed nrawssdk-v2 integration examples of AppendMiddlewares corrected. Thanks to @Meroje for the PR Zerolog integration correction to example program import statement. Fixes issue #950 Zerolog integration JSON parser bug caused a runtime panic in some circumstances. Fixes issue #955 Fixed handling of panic(nil). This was made necessary by changes introducted to Go as of 1.21. A race condition was possible due to code level metrics accesses to a contended memory address. Fixes issue #949 Fixes issue #957 Integer size issues flagged when converting unsigned to signed values. Workflow corrections for CI processes in github. Fixes issue #946 Updated to use latest grpc and protobuf versions. Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-35-0","eolDate":"2025-10-10"},{"agent":"go","date":"2024-08-01","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.34.0","version":"3.34.0","features":["Configure the agnet to write logs using Zerolog","Configure the agnet to write logs using log/slog","Collect user attributes in Logrus using nrlogrus","Collect user attributes in Slog using nrslog","Added support for the RegisterTLSConfig method in nrmysql"],"bugs":["Fixed a bug where nrlogurs would not print any logs if the agnet was shut down","Switched protobuff to google.golang.org/protobuff in the go agent"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.34.0 Added logcontext-v2/nrlogrus can now collect user attributes logcontext-v2/nrslog can now collect user attributes Use slog to manage Go agent logs with the new nrslog library Use zerolog go manage Go agent logs with the new nrzerolog library Support for RegisterTLSConfig in nrmysql Fixed logcontext-v2/nrlogrus will still print user logs without issues if the Go agent has already been shut down Switched protobuff to google.golang.org/protobuff in modfile Support statement We use the latest version of the Go language. At a minimum, you should use no version of Go older than what's supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-34-0","eolDate":"2025-08-01"},{"agent":"go","date":"2024-07-02","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.33.1","version":"3.33.1","features":["Improved comments on nropenai","Increased max span events default limit to 2,000 to align with agent specifications","Added support for gRPC API endpoints and HTTP status codes in the nrsecurity integration","Added feature to detect route of an incoming request for all supported frameworks in the nrsecurity integration"],"bugs":["Fixed a minor bug relating to ExpectStatusCodes in app_run.go","Fixed an issue with nrzap attributes not properly being forwarded"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.33.1 Added Increased max span events default limit to 2,000 to align with agent specifications. Updated support for latest New Relic security agent release. Added support for gRPC API endpoints and HTTP status codes in the nrsecurity integration. Added feature to detect route of an incoming request for all supported frameworks in the nrsecurity integration. Fixed Fixed an issue with nrzap attributes not properly being forwarded. Improved comments on nropenai. Fixed a minor bug relating to ExpectStatusCodes in app_run.go. Support statement We use the latest version of the Go language. At a minimum, you should use no version of Go older than what's supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-33-1","eolDate":"2025-07-02"},{"agent":"go","date":"2024-05-01","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.33.0","version":"3.33.0","features":["Zap Field Attributes Support"],"bugs":["Fixed an issue where running containers on AWS would falsely flag Azure Utilization","Context-driven handler for nrslog","Fixed a typo with nrecho field name"],"security":["Bumped csec-go-agent to v1.2.0"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.33.0 Added Support for Zap Field Attributes Fixed Fixed an issue where running containers on AWS would falsely flag Azure Utilization Fixed a typo with nrecho Changed nrslog example to use a context-driven handler Support statement We use the latest version of the Go language. At a minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-33-0","eolDate":"2025-05-01"},{"agent":"go","date":"2024-04-04","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.32.0","version":"3.32.0","features":["Handler to take New Relic transaction data from context automatically when using `nrslog` integration","Adds new wrapper function for the `nrecho`, `nrgin`, and `nrgorilla` integrations for use in the New Relic Security Agent"],"bugs":["Adds missing license file to the `nropenai` integration","Changes `*bedrockruntime.Client` parameters in `nrawsbedrock` integration to use a more general interface type, allowing the use of custom types which extend the bedrock client type","Fixes `pgx5` pool example","Updated unit tests to check `Transaction.Ignore`","Updated `nrzap` unit tests to add background logger sugared test case"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.32.0 Added Updates to support for the New Relic security agent to report API endpoints Adds new wrapper function for the nrecho, nrgin, and nrgorilla integrations Handler to take New Relic transaction data from context automatically when using nrslog integration (thanks, @adomaskizogian!) Fixed Adds missing license file to the nropenai integration Changes *bedrockruntime.Client parameters in nrawsbedrock integration to use a more general interface type, allowing the use of custom types which extend the bedrock client type Fixes pgx5 pool example Updated unit tests to check Transaction.Ignore Updated nrzap unit tests to add background logger sugared test case. Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-32-0","eolDate":"2025-04-04"},{"agent":"go","date":"2024-03-27","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.31.0","version":"3.31.0","features":["go-openai AI library instrumentation","awsbedrock AI library instrumentation","Dockerfile in the `examples/server` sample app which facilitates the easy creation of a containerized ready-to-run sample app for situations where that makes testing easier"],"bugs":[".Ignore was not ignoring transaction","Added nil error check in wrap function","Fixed  `WrapBackgroundCore` background logger not sending logs to New Relic","Corrected pgx5 integration example which caused a race condition"],"security":["`github.com/jackc/pgx/v5` to 5.5.4 in `nrpgx5` integration"," `google.gopang.org/protobuf` to 1.33.0 in `nrmicro` and `nrgrpc` integrations","`github.com/jackc/pgx/v4` to 4.18.2 in `nrpgx` integration"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.31.0 Added Integration packages to instrument AI model invocations (see below). New package nrawsbedrock v1.0.0 introduced to instrument calls to Amazon Bedrock  Runtime Client API InvokeModel and InvokeModelWithResponseStream calls. Also provides a simple one-step method which invokes stream invocations and harvests the response stream data for you. New package nropenai v1.0.0 introduced to instrument calls to OpenAI using NRCreateChatCompletion, NRCreateChatCompletionStream, and NRCreateEmbedding calls. Dockerfile in the examples/server sample app which facilitates the easy creation of a containerized ready-to-run sample app for situations where that makes testing easier. Fixed .Ignore was not ignoring transaction. Fixes Issue #845 . Added nil error check in wrap function. Fixes Issue #862 . WrapBackgroundCore background logger was not sending logs to New Relic. Fixes Issue #859 . Corrected pgx5 integration example which caused a race condition. Thanks to @WillAbides! Fixes Issue #855 . Updated third-party library versions due to reported security or other supportability issues: github.com/jackc/pgx/v5 to 5.5.4 in nrpgx5 integration google.gopang.org/protobuf to 1.33.0 in nrmicro and nrgrpc integrations github.com/jackc/pgx/v4 to 4.18.2 in nrpgx integration AI Monitoring Configuration New configuration options are available specific to AI monitoring. These settings include: AIMonitoring.Enabled, configured via ConfigAIMonitoring.Enabled(bool ) [default false] AIMonitoring.Streaming.Enabled, configured via ConfigAIMonitoringStreamingEnabled(bool ) [default true] AIMonitoring.Content.Enabled, configured via ConfigAIMonitoringContentEnabled(bool ) [default true] AI Monitoring Public API Methods Two new AI monitoring related public API methods have been added, as methods of the newrelic.Application value returned by newrelic.NewApplication: app.RecordLLMFeedbackEvent app.SetLLMTokenCountCallback AI Monitoring New Relic AI monitoring is the industry’s first APM solution that provides end-to-end visibility for AI Large Language Model (LLM) applications. It enables end-to-end visibility into the key components of an AI LLM application. With AI monitoring, users can monitor, alert, and debug AI-powered applications for reliability, latency, performance, security and cost. AI monitoring also enables AI/LLM specific insights (metrics, events, logs and traces) which can easily integrate to build advanced guardrails for enterprise security, privacy and compliance. AI monitoring offers custom-built insights and tracing for the complete lifecycle of an LLM’s prompts and responses, from raw user input to repaired/polished responses. AI monitoring provides built-in integrations with popular LLMs and components of the AI development stack. This release provides instrumentation for OpenAI \nand Bedrock . When AI monitoring is enabled with ConfigAIMonitoringEnabled(true), the agent will now capture AI LLM related data. This data will be visible under a new APM tab called AI Responses. See our AI Monitoring documentation  for more details. Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-31-0","eolDate":"2025-03-27"},{"agent":"go","date":"2024-02-15","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.30.0","version":"3.30.0","features":["Added new integration, logcontext-v2/nrslog, which instruments logging via the new slog library"],"bugs":["Redacts license keys from error reporting"],"security":["Updated the depencency on nrsecurityagent to 1.0.0"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it becomes available. If your organization has established practices that prevent you from updating to the latest version, ensure that you regularly update your agents to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.30.0 Added Updated the depencency on nrsecurityagent to 1.0.0. Added new integration, logcontext-v2/nrslog, which instruments logging via the new slog library. Fixed Redacts license keys from error reporting. Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what the Go team itself supports.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-30-0","eolDate":"2025-02-15"},{"agent":"go","date":"2024-01-25","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.29.1","version":"3.29.1","features":["Added Dockerized Unit Tests for Github Actions"],"bugs":["Updated version on security agent"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.29.1 Added Added Dockerized Unit Tests for Github Actions Fixes Updated version on security agent Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-29-1","eolDate":"2025-01-25"},{"agent":"go","date":"2023-12-14","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.29.0","version":"3.29.0","features":["Security agent integration `nrsecurityagent` now reports security configuraiton information along with the overall Go Agent configuration values","Code-Level Metrics collection efficiency enhancement allows user callback function for as-needed (and just-in-time) evaluation of custom code locations rather than up-front location overrides, via the `WithCodeLocationCallback` CLM option","Added extended synthetics support for new `X-Newrelic-Synthetics-Info` HTTP headers"],"bugs":["Documentation fixes","Removed deprecated `ROADMAP.md` file"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization's practices prevent you from updating, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.29.0 Added Security agent integration nrsecurityagent now reports security configuraiton information along with the overall Go Agent configuration values. (Updates nrsecurityagent to v1.2.0.) Code-Level Metrics collection efficiency enhancement allows user callback function for as-needed (and just-in-time) evaluation of custom code locations rather than up-front location overrides, via the WithCodeLocationCallback CLM option. Deprecates WithCodeLocation option (although the latter function is still supported for compatibility with existing code). Added extended synthetics support for new X-Newrelic-Synthetics-Info HTTP headers. Documentation fixes. Removed deprecated ROADMAP.md file. Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what's supported by the Go team themselves.\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-29-0","eolDate":"2024-12-14"},{"agent":"go","date":"2023-11-30","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.28.1","version":"3.28.1","features":["Added Supportability Metrics to nrfasthttp","Always Link Transaction IDs to traces regardless of if Distributed Tracing is enabled or not"],"bugs":["Fixed an issue where nil Request.Body could be set to non-nil request.Body with zero length when the security agent is enabled"],"security":["More Secure URL Redaction"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.28.1 Added Added Supportability Metrics to nrfasthttp Always Link Transaction IDs to traces regardless of if Distributed Tracing is enabled or not Fixed Fixed an issue where nil Request.Body could be set to non-nil request.Body with zero length when the security agent is enabled Security More Secure URL Redaction Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-28-1","eolDate":"2024-11-30"},{"agent":"go","date":"2023-11-16","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.28.0","version":"3.28.0","features":[],"bugs":["Fixed an issue where fasthttp would not properly register security agent headers","Fixed issue where usage of io.ReadAll() was causing a memory leak"],"security":["Bumped gRPC from 1.54.0 -> 1.56.3 in the following packages /v3/integrations/nrgrpc, /v3/, /v3/integrations/nrgrpc","Bumped golang.org/x/net from 0.8.0 -> 0.17.0 in package /v3/integrations/nrgraphqlgo"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.28.0 Fixed Bumped gRPC from 1.54.0 -> 1.56.3 in the following packages /v3/integrations/nrgrpc, /v3/, /v3/integrations/nrgrpc Bumped golang.org/x/net from 0.8.0 -> 0.17.0 in package /v3/integrations/nrgraphqlgo Fixed issue where nrfasthttp would not properly register security agent headers Move fasthttp instrumentation into a new integration package, nrfasthttp Fixed issue where usage of io.ReadAll() was causing a memory leak Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-28-0","eolDate":"2024-11-16"},{"agent":"go","date":"2023-10-19","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.26.0","version":"3.27.0","features":["Automatic Instrumentation for RabbitMQ","Support for Docker in cgroupv2"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.27.0 Added Added Support for getting Container ID's from cgroup v2 docker containers A new instrumentation package for RabbitMQ with distributed tracing support: nramqp Fixed Unit tests repairs and improvements Removed deprecated V2 code from the repository. The support timeframe for this code has expired and is no longer recommended for use. Bumped github.com/graphql-go/graphql from 0.7.9 to 0.8.1 Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-27-0","eolDate":"2024-10-19"},{"agent":"go","date":"2023-09-28","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.26.0","version":"3.26.0","features":["Extended implementation of nrpgx5 integration to support Postgres direct operations with jackc/pgx/v5"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.26.0 Added Extended implementation of the nrpgx5 integration (now v1.2.0). This instruments Postgres database operations using the jackc/pgx/v5 library, including the direct access mode of operation as opposed to requiring code to use the library compatible with the standard database/sql library. Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-26-0","eolDate":"2024-09-28"},{"agent":"go","date":"2023-09-18","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.25.1","version":"3.25.1","features":["Added support for FastHTTP package"],"bugs":["Security agent fails to correctly parse NEW_RELIC_SECURITY_AGENT_ENABLED environment variable."],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from updating to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.25.1 Added Added support for the FastHTTP package: Added newrelic.WrapHandleFuncFastHTTP() and newrelic.StartExternalSegmentFastHTTP() functions to instrument fasthttp context and create wrapped handlers. These functions work similarly to the existing ones for net/http. Added client-fasthttp and server-fasthttp examples to help get started with FastHTTP integration. Fixed Corrected a bug where the security agent failed to correctly parse the NEW_RELIC_SECURITY_AGENT_ENABLED environment variable. Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-25-1","eolDate":"2024-09-18"},{"agent":"go","date":"2023-09-18","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.25.0","version":"3.25.0","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"This release was retracted. Use 3.25.1  instead. Support statement We use the latest version of the Go language. At a minimum, you should be using no version of Go older than what is supported by the Go team themselves (for exmample, Go versions 1.19 and later are supported). We recommend updating to the latest agent version as soon as it's available. If you can't update to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-25-0","eolDate":"2024-09-18"},{"agent":"go","date":"2023-08-10","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.24.1","version":"3.24.1","features":[],"bugs":["Performance improvement around calls to security agent. In some cases, unnecessary setup operations were being performed even if there was no security agent present to use that"],"security":["Bumped nrmongo to v1.1.1","Bumped nrawssdk-v1 to 1.1.2","Bumped nrawssdk-v2 to 1.2.2","Bumped nrecho-v3 to 1.0.2","Bumped nrecho-v4 to 1.0.4","Bumped nrhttprouter to 1.3.0","Bumped nrlambda to v1.2.2","Bumped nrnats to 1.1.5","Bumped nrreddis-v8 to v1.0.1"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.24.1 Fixed Performance improvement around calls to the security agent. In some cases, unnecessary setup operations were being performed even if there was no security agent present to use that. These are now conditional on the security agent being present in the application (note that this will enable the setup code if the security agent is present  in the application, regardless of whether it’s currently enabled to run). This affects: Base agent code (updated to v3.24.1) nrmongo integration (updated to v1.1.1) Fixed unit tests for integrations that were failing because code-level metrics are enabled by default now: nrawssdk-v1 (updated to v1.1.2) nrawssdk-v2 (updated to v1.2.2) nrecho-v3 (updated to v1.0.2) nrecho-v4 (updated to v1.0.4) nrhttprouter (updated to v1.3.0) nrlambda (updated to v1.2.2) nrnats (updated to v1.1.5) nrredis-v8 (updated to v1.0.1) Changed Updated all integration go.mod files to reflect supported Go language versions. Support statement We use the latest version of the Go language. At a minimum, you should be using no version of Go older than what is supported by the Go team themselves (i.e., Go versions 1.19 and later are supported).\nWe recommend updating to the latest agent version as soon as it’s available. If you can’t upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ )\nSee the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-24-1","eolDate":"2024-08-10"},{"agent":"go","date":"2023-07-31","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.24.0","version":"3.24.0","features":["Turned Code Level Metrics on by default","Added Name() method for Transaction values to get the current transaction name","Added new test case for InfoInterceptorStatusHandler function in the gRPC integration","Added new test case to check if the nrsecurityagent is enabled in the gRPC integration"],"bugs":["Fixed a bug where expected errors weren't being properly marked as expected on new relic dashboards"],"security":["Bumped gin from 1.9.0 to 1.9.1","Bumped gosnowflake from 1.6.16 to 1.6.19","Bumped nrsecurityagent to 1.1.0 with improved reporting of gRPC protocol versions"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.24.0 Added Turned Code Level Metrics on by default Added new test case to check if the nrsecurityagent is enabled in the gRPC integration Added new test case for InfoInterceptorStatusHandler function in the gRPC integration Added Name() method for Transaction values to get the current transaction name. Fixed Bumped gin from 1.9.0 to 1.9.1 Bumped gosnowflake from 1.6.16 to 1.6.19 Bumped nrsecurityagent to 1.1.0 with improved reporting of gRPC protocol versions. Fixed a bug where expected errors weren't being properly marked as expected on new relic dashboards We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-24-0","eolDate":"2024-07-31"},{"agent":"go","date":"2023-06-28","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.23.1","version":"3.23.1","features":["ConfigDatastoreRawQuery(true) allows raw SQL queries to be captured","Enriched serverless debug logs"],"bugs":["removed test timeout for trace_observer_test.go","Added license to nrsecurityagent","nrnats test is now using go 1.19"],"security":["bumped graphql-go to v1.3.0 in nrgraphgophers"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.23.1 Added Added newrelic.ConfigDatastoreRawQuery(true) configuration option to allow raw SQL queries to appear in new relic dashboards Added enriched serverless debug logging for faster debugging Fixed Removed timeouts on two tests in trace_observer_test.go Bumped nrnats test to go1.19 Bumped graphql-go to v1.3.0 in the nrgraphgophers integration Added license file to nrsecurityagent integration Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves (i.e., Go versions 1.19 and later are supported). We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-23-1","eolDate":"2024-06-28"},{"agent":"go","date":"2023-06-20","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.23.0","version":"3.23.0","features":["adds nrsecurityagent integration to support IAST application security testing"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.23.0 Adds the nrsecurityagent integration for performing Interactive Application Security Testing (IAST) of your application. To learn how to use IAST, check out our documentation . Support statement We use the latest version of Go. You should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-23-0","eolDate":"2024-06-20"},{"agent":"go","date":"2023-06-02","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.22.1","version":"3.22.1","features":[],"bugs":["fix changelog and agent version bug"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.22.1 Fixed Corrects an error in the release process for 3.22.1. Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-22-1","eolDate":"2024-06-02"},{"agent":"go","date":"2023-06-01","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.22.0","version":"3.22.0","features":["Instrumentation for Sarama Kafka","Instrumentation for Zap with logs in context","Integration tests for nrlogrus and nrzapintegrations","Updated integration tests for nrlogxi"],"bugs":[],"security":["Bumped sys package to v0.1.0 in the nrmssql integration","Bumped net package to v0.7.0 in the nrgrpc, nrmssql , and nrnats integrations","Bumped aws-sdk-go package to v1.34.0 in the nrawssdk-v1 integration","Bumped text  package to v0.3.8 in the nrnats,  and nrpgx integrations","Bumped gin package to v1.9.0 in the nrgin integration","Bumped crypto package to v0.1.0 in the nrpgx  integration","Fixed integration tests in nrnats package not correctly showing code coverage"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.22.0 Added New Apache Kafka integration nrsarama that instruments the Sarama library https://github.com/Shopify/sarama New logs in context integration logcontext-v2/nrzap that instruments the zap logging framework https://github.com/uber-go/zap Integration tests created for the nrlogrus and nrzapintegrations Updated integration tests for nrlogxi Security Fixes Bumped sys package to v0.1.0 in the nrmssql integration Bumped net package to v0.7.0 in the nrgrpc, nrmssql , and nrnats integrations Bumped aws-sdk-go package to v1.34.0 in the nrawssdk-v1 integration Bumped text  package to v0.3.8 in the nrnats,  and nrpgx integrations Bumped gin package to v1.9.0 in the nrgin integration Bumped crypto package to v0.1.0 in the nrpgx  integration Fixed integration tests in nrnats package not correctly showing code coverage Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-22-0","eolDate":"2024-06-01"},{"agent":"go","date":"2023-04-27","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.21.1","version":"3.21.1","features":["Instrumentation for Redis v9"],"bugs":[],"security":["Go version bump to 1.18"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.21.1 Added nrredis-v9: automatic instrumentation for Go redis v9 Fixed Agent now requires Go version 1.18 or higher. Removed support for Go version 1.17. This version of Go is outside of the support window. Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-21-1","eolDate":"2024-04-27"},{"agent":"go","date":"2023-03-30","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.21.0","version":"3.21.0","features":["Error Fingerprinting","User Tracking","Disable Parameterized Query Collection nrpgx-5"],"bugs":[],"security":["Improved grpc test coverage"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.21.0 Added New errors inbox features: User tracking: You can now see the number of users impacted by an error group. Identify the end user with the setUser method. Error fingerprint: Are your error occurrences grouped poorly? Set your own error fingerprint via a callback function. Ability to disable reporting parameterized query in nrpgx-5 Fixed Improved test coverage for gRPC integration, nrgrpc Support statement We use the latest version of the Go language. At minimum, you should be using no version of Go older than what is supported by the Go team themselves. See the Go agent EOL Policy  for details about supported versions of the Go agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-21-0","eolDate":"2024-03-30"},{"agent":"go","date":"2023-03-09","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.20.4","version":"3.20.4","features":["Improved ignore error performence","Expected HTTP status code errors"],"bugs":["Error message truncation","Span event limit config option"],"security":["aws sdk go unencrypted hash vulnerability"],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . 3.20.4 Please note that the v2 Go agent is no longer supported according to our EOL policy. Fixed nrmssql driver updated to use version maintained by Microsoft Bug where error messages were not truncated to the maximum size, and would get dropped if they were too large Bug #643 where number of span events was hard coded to 1000, and config setting was being ignored Unencrypted hash vulnerability in v1.15.0 of github.com/aws/aws-sdk-go patched by bumping to v1.33.0 Added Improved performance of ignore error code checks in agent HTTP error codes can be set as expected by adding them to ErrorCollector.ExpectStatusCodes in the config Support Statement We also using the latest version of the Go language. At minimum, you should at least be using no version of Go older than what is supported by the Go team themselves. See the Go Agent EOL Policy  for details about supported versions of the Go Agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-20-4","eolDate":"2024-03-09"},{"agent":"go","date":"2023-01-19","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.20.3","version":"3.20.3","features":["Snowflake driver updated to golang 1.17"],"bugs":["Performance improvements for compression"],"security":[],"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date . 3.20.3 Please note that the v2 go agent is no longer supported according to our EOL policy. Fixed Performance Improvements for compression nrsnowflake updated to golang 1.17 versions of packages Support Statement We also using the latest version of the Go language. At minimum, you should at least be using no version of Go older than what is supported by the Go team themselves. See the Go Agent EOL Policy  for details about supported versions of the Go Agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-20-3","eolDate":"2024-01-19"},{"agent":"go","date":"2022-12-14","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.20.2","version":"3.20.2","features":["New NoticeExpectedError() method allows you to capture errors that you are expecting to handle, without triggering alerts"],"bugs":["More defensive harvest cycle code that will avoid crashing even in the event of a panic"],"security":["Update nats-server version to avoid known zip-slip exploit","Update labstack/echo version to mitigate known open redirect exploit"],"supportedOperatingSystems":null,"description":"3.20.2 We recommend updating to the latest agent version as soon as it’s available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version that's at most 90 days old. Read more about keeping your agent up to date . Added New NoticeExpectedError() method allows you to capture errors that you are expecting to handle, without triggering alerts Fixed More defensive harvest cycle code that will avoid crashing even in the event of a panic Update nats-server version to avoid known zip-slip exploit Update labstack/echo version to mitigate known open redirect exploit","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-20-2","eolDate":"2023-12-14"},{"agent":"go","date":"2022-11-15","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.20.1","version":"3.20.1","features":["Added new integration nrpgx5"],"bugs":["Implemented better handling of Code Level Metrics reporting when the data is excessively long"],"security":[],"supportedOperatingSystems":null,"description":"3.20.1 We recommend updating to the latest agent version as soon as it’s available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date . Added New integration nrpgx5 v1.0.0 to instrument github.com/jackc/pgx/v5. Changed Changed the following TraceOption function to be consistent with their usage and other related identifier names. The old names remain for backward compatibility, but new code should use the new names. WithIgnoredPrefix -> WithIgnoredPrefixes WithPathPrefix -> WithPathPrefixes Implemented better handling of Code Level Metrics reporting when the data (e.g., function names) are excessively long, so that those attributes are suppressed rather than being reported with truncated names. Specifically: Attributes with values longer than 255 characters are dropped. No CLM attributes at all will be attached to a trace if the code.function attribute is empty or is longer than 255 characters. No CLM attributes at all will be attached to a trace if both code.namespace and code.filepath are longer than 255 characters.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-20-1","eolDate":"2023-11-15"},{"agent":"go","date":"2022-11-02","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.20.0","version":"3.20.0","features":["Added the Module Dependency Metrics feature that collects the list of modules imported into your application","Application Log Forwarding is now enabled by default","Increased the default amount of custom events being collected per minute from 10,000 events to 30,000 events"],"bugs":["fixed a bug in zerologWriter where comma separated fields in log message confused the JSON parser and could cause panics"],"security":[],"supportedOperatingSystems":null,"description":"3.20.0 PLEASE READ  these changes, and verify your config settings to ensure your application behaves how you intend it to. This release changes some default behaviors in the go agent. Added The Module Dependency Metrics feature was added. This collects the list of modules imported into your application, to aid in management of your application dependencies, enabling easier vulnerability detection and response, etc. This feature is enabled by default, but may be disabled by explicitly including ConfigModuleDependencyMetricsEnable(false) in your application, or setting the equivalent environment variable or Config field direclty. Modules may be explicitly excluded from the report via the ConfigModuleDependencyMetricsIgnoredPrefixes option. Excluded module names may be redacted via the ConfigModuleDependencyMetricsRedactIgnoredPrefixes option. This is enabled by default. Application Log Forwarding will now be ENABLED  by default Automatic application log forwarding is now enabled by default. This means that logging frameworks wrapped with one of the logcontext-v2 integrations  will automatically send enriched application logs to New Relic with this version of the agent. To learn more about this feature, see the APM logs in context documentation . For additional configuration options, see the Go logs in context documentation . To learn about how to toggle log ingestion on or off by account, see our documentation to disable automatic  logging via the UI or API. If you are using a logcontext-v2 extension, but don't want the agent to automatically forward logs, please configure ConfigAppLogForwardingEnabled(false) in your application. Environment variables have been added for all application logging config options: NEW_RELIC_APPLICATION_LOGGING_ENABLED NEW_RELIC_APPLICATION_LOGGING_FORWARDING_ENABLED NEW_RELIC_APPLICATION_LOGGING_FORWARDING_MAX_SAMPLES_STORED NEW_RELIC_APPLICATION_LOGGING_METRICS_ENABLED NEW_RELIC_APPLICATION_LOGGING_LOCAL_DECORATING_ENABLED Custom Event Limit Increase This version increases the DEFAULT  limit of custom events from 10,000 events per minute to 30,000 events per minute. In the scenario that custom events were being limited, this change will allow more custom events to be sent to New Relic. There is also a new configurable MAXIMUM  limit of 100,000 events per minute. To change the limits, set ConfigCustomInsightsEventsMaxSamplesStored(limit) to the limit you want in your application. To learn more about the change and how to determine if custom events are being dropped, see our Explorers Hub post . New config option ConfigCustomInsightsEventsEnabled(false) can be used to disable the collection of custom events in your application. Changed Changed the following names to be consistent with their usage and other related identifier names. The old names remain for backward compatibility, but new code should use the new names. ConfigCodeLevelMetricsIgnoredPrefix -> ConfigCodeLevelMetricsIgnoredPrefixes ConfigCodeLevelMetricsPathPrefix -> ConfigCodeLevelMetricsPathPrefixes NEW_RELIC_CODE_LEVEL_METRICS_PATH_PREFIX -> NEW_RELIC_CODE_LEVEL_METRICS_PATH_PREFIXES NEW_RELIC_CODE_LEVEL_METRICS_IGNORED_PREFIX -> NEW_RELIC_CODE_LEVEL_METRICS_IGNORED_PREFIXES When excluding information reported from CodeLevelMetrics via the IgnoredPrefixes or PathPrefixes configuration fields (e.g., by specifying ConfigCodeLevelMetricsIgnoredPrefixes or ConfigCodeLevelMetricsPathPrefixes), the names of the ignored prefixes and the configured path prefixes may now be redacted from the agent configuration information sent to New Relic. This redaction is enabled by default, but may be disabled by supplying a false value to ConfigCodeLevelMetricsRedactPathPrefixes or ConfigCodeLevelMetricsRedactIgnoredPrefixes, or by setting the corresponding Config fields or environment variables to false. Fixed #583 : fixed a bug in zerologWriter where comma separated fields in log message confused the JSON parser and could cause panics. Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you’re getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life. We also recommend using the latest version of the Go language. At minimum, you should at least be using no version of Go older than what is supported by the Go team themselves. See the Go Agent EOL Policy  for details about supported versions of the Go Agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-20-0","eolDate":"2023-11-02"},{"agent":"go","date":"2022-09-21","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.19.2","version":"3.19.2","features":["Updated nrgin integration to more accurately report code locations when code level metrics are enabled","Internal dev process and unit test improvements"],"bugs":[],"security":["Updated minimum version for the nrawssdk-v2, nrecho-v4, nrgrpc, nrmongo, nrmysql, nrnats, and nrstan modules to now require Go Agent 3.18.2 or later","The Go Agent now requires protobuf 1.5.2 and grpc 1.49.0"],"supportedOperatingSystems":null,"description":"3.19.2 Changed Updated nrgin integration to more accurately report code locations when code level metrics are enabled. The Go Agent and all integrations now require Go version 1.17 or later. Updated minimum versions for third-party modules. nrawssdk-v2, nrecho-v4, nrgrpc, nrmongo, nrmysql, nrnats, and nrstan now require Go Agent 3.18.2 or later the Go Agent now requires protobuf 1.5.2 and grpc 1.49.0 Internal dev process and unit test improvements. Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you’re getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life. We also recommend using the latest version of the Go language. At minimum, you should at least be using no version of Go older than what is supported by the Go team themselves. See the Go Agent EOL Policy  for details about supported versions of the Go Agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-19-2","eolDate":"2023-09-21"},{"agent":"go","date":"2022-09-16","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.19.1","version":"3.19.1","features":["Moved the location of the nrwriter module"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"3.19.1 - Hotfix Release Changed Moved the v3/internal/logcontext/nrwriter module to v3/integrations/logcontext-v2/nrwriter Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you’re getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life. See the Go Agent EOL Policy for details about supported versions of the Go Agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-19-1","eolDate":"2023-09-16"},{"agent":"go","date":"2022-09-15","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.19.0","version":"3.19.0","features":["Added logcontext-v2/logWriter plugin which is a new logs in context plugin that supports the standard library logging package","Added the logcontext-v2/zerologWriter plugin which is a more robust plugin that supports a richer set of features than the previous zerolog plugin"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"3.19.0 Added logcontext-v2/logWriter plugin: a new logs in context plugin that supports the standard library logging package. logcontext-v2/zerologWriter plugin: a new logs in context plugin for zerolog that will replace the old logcontext-v2/zerolog plugin. This plugin is more robust, and will be able to support a richer set of features than the previous plugin. see the updated logs in context documentation  for information about configuration and installation. Changed the logcontext-v2/zerolog plugin will be deprecated once the 3.17.0 release EOLs. Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life. See the Go Agent EOL Policy  for details about supported versions of the Go Agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-19-0","eolDate":"2023-09-15"},{"agent":"go","date":"2022-09-07","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.18.2","version":"3.18.2","features":["Added WithDefaultFunctionLocation trace option to indicate a fallback function to use for Code Level Metrics","Improved performance of Code Level Metrics","Added WithCodeLevelMetrics trace option to force collection of Code Level Metrics data","Added CodeLevelMetricsScopeLabelToValue function to convert a list of strings describing CLM scopes","Added text marshaling and unmarshaling for the CodeLevelMetricsScope value","The FunctionLocation function now accepts any number of function values instead of just a single one","The NEW_RELIC_CODE_LEVEL_METRICS_SCOPE environment variable now accepts a comma-separated list of pathnames"],"bugs":["Improved the implementation of Code Level Metrics internals to improve speed, robustness, and thread safety","Corrected the implementation of the WrapHandle and WrapHandleFunc functions so that they consistently report the function being invoked by the http framework"],"security":[],"supportedOperatingSystems":null,"description":"3.18.2 Added Added WithDefaultFunctionLocation trace option. This allows the caller to indicate a fall-back function to use for CLM in case no other location was found first. Added caching versions of the code-level metrics functions ThisCodeLocation and FunctionLocation , and trace options WithThisCodeLocation  and  WithFunctionLocation. These improve performance by caching the result of computing the source code location, and reuse that cached result on all subsequent calls. Added a WithCodeLevelMetrics trace option to force the collection of CLM data even if it would have been excluded as being out of the configured scope. (Note that CLM data are never collected if CLM is turned off globally or if the WithoutCodeLevelMetrics option was specified for the same transaction.) Added an exported CodeLevelMetricsScopeLabelToValue function to convert a list of strings describing CLM scopes in the same manner as the NEW_RELIC_CODE_LEVEL_METRICS_SCOPE environment variable (but as individual string parameters), returning the CodeLevelMetricsScope value which corresponds to that set of scopes. Added a new CodeLevelMetricsScopeLabelListToValue function which takes a comma-separated list of scope names exactly as the NEW_RELIC_CODE_LEVEL_METRICS_SCOPE environment variable does, and returns the CodeLevelMetrics value corresponding to that set of scopes. Added text marshaling and unmarshaling for the CodeLevelMetricsScope value, allowing the CodeLevelMetrics field of the configuration struct to be converted to or from JSON or other text-based encoding representations. Changed The WithPathPrefix trace option now takes any number of string parameters, allowing multiple path prefixes to be recognized rather than just one. The FunctionLocation function now accepts any number of function values instead of just a single one. The first such parameter which indicates a valid function, and for which CLM data are successfully obtained, is the one which will be reported. The configuration struct field PathPrefix is now deprecated with the introduction of a new PathPrefixes field. This allows for multiple path prefixes to be given to the agent instead of only a single one. The NEW_RELIC_CODE_LEVEL_METRICS_SCOPE environment variable now accepts a comma-separated list of pathnames. Fixed Improved the implementation of CLM internals to improve speed, robustness, and thread safety. Corrected the implementation of the WrapHandle and WrapHandleFunc functions so that they consistently report the function being invoked by the http framework, and improved them to use the new caching functions and ensured they are thread-safe. This release fixes issue #557 . Compatibility Notice As of release 3.18.0, the API was extended by allowing custom options to be added to calls to the Application.StartTransaction method and the WrapHandle  and WrapHandleFunc functions. They are implemented as variadic functions such that the new option parameters are optional (i.e., zero or more options may be added to the end of the function calls) to be backward-compatible with pre-3.18.0 usage of those functions. This prevents the changes from breaking existing code for typical usage of the agent. However, it does mean those functions' call signatures have changed: StartTransaction(string) -> StartTransaction(string, ...TraceOption) WrapHandle(*Application, string, http.Handler) -> WrapHandle(*Application, string, http.Handler, ...TraceOption) WrapHandleFunc(*Application, string, func(http.ResponseWriter, *http.Request))    -> WrapHandleFunc(*Application, string, func(http.ResponseWriter, *http.Request), ...TraceOption) If, for example, you created your own custom interface type which includes the StartTransaction method or something that depends on these functions' exact  call semantics, that code will need to be updated accordingly before using version 3.18.0 (or later) of the Go Agent. Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you’re getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life. See the Go Agent EOL Policy  for details about supported versions of the Go Agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-18-2","eolDate":"2023-09-07"},{"agent":"go","date":"2022-08-18","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.18.1","version":"3.18.1","features":["Extended the IgnoredPrefix configuration value for Code-Level Metrics so that multiple such prefixes may be given instead of a single one"],"bugs":["Corrected some small errors in documentation of package features"],"security":[],"supportedOperatingSystems":null,"description":"3.18.1 Added Extended the IgnoredPrefix configuration value for Code-Level Metrics so that multiple such prefixes may be given instead of a single one. This deprecates the IgnoredPrefix configuration field of Config.CodeLevelMetrics in favor of a new slice field IgnoredPrefixes. The corresponding configuration option-setting functions ConfigCodeLevelMetricsIgnoredPrefix and WithIgnoredPrefix now take any number of string parameters to set these values. Since those functions used to take a single string value, this change is backward-compatible with pre-3.18.1 code.  Accordingly, the NEW_RELIC_CODE_LEVEL_METRICS_IGNORED_PREFIX environment variable is now a comma-separated list of prefixes.  Fixes Issue #551 . Fixed Corrected some small errors in documentation of package features. Fixes Issue #550 Compatibility Notice As of release 3.18.0, the API was extended by allowing custom options to be added to calls to the Application.StartTransaction method and the WrapHandle and WrapHandleFunc functions. They are implemented as variadic functions such that the new option parameters are optional (i.e., zero or more options may be added to the end of the function calls) to be backward-compatible with pre-3.18.0 usage of those functions. This prevents the changes from breaking existing code for typical usage of the agent. However, it does mean those functions' call signatures have changed: StartTransaction(string) -> StartTransaction(string, ...TraceOption) WrapHandle(*Application, string, http.Handler) -> WrapHandle(*Application, string, http.Handler, ...TraceOption) WrapHandleFunc(*Application, string, func(http.ResponseWriter, *http.Request))\t-> WrapHandleFunc(*Application, string, func(http.ResponseWriter, *http.Request), ...TraceOption) If, for example, you created your own custom interface type which includes the StartTransaction method or something that depends on these functions' exact call semantics, that code will need to be updated accordingly before using version 3.18.0 (or later) of the Go Agent. Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you’re getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life. See the Go Agent EOL Policy  for details about supported versions of the Go Agent and third-party components.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-18-1","eolDate":"2023-08-18"},{"agent":"go","date":"2022-08-01","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.18.0","version":"3.18.0","features":["Code-level metrics are now available for instrumented transactions","V2 logs-in-context plugin is available for Logrus"],"bugs":["Fixed issue with custom event limits and number of distributed tracing spans to more accurately follow configured limits"],"security":[],"supportedOperatingSystems":null,"description":"3.18.0 Added Code-level metrics are now available for instrumented transactions. This is off by default but once enabled via ConfigCodeLevelMetricsEnabled(true) transactions will include information about the location in the source code where StartTransaction was invoked. Adds information about where in your source code transaction traces originated. See the Go agent documentation for details on configuring  code-level metrics and how to instrument  your code using them. New V2 logs-in-context plugin is available for Logrus, packed with all the features you didn't know you wanted: Automatic log forwarding Log metrics Capture logs anywhere in your code; both inside or outside of a transaction. Use the Logrus formatting package of your choice Local log decorating is now available for the new logcontext-v2/nrlogrus plugin only. This is off by default but can be enabled with ConfigAppLogForwardingEnabled(true). Fixed Fixed issue with custom event limits and number of distributed tracing spans to more accurately follow configured limits. Compatibility Notice This release extends the API by allowing custom options to be added to calls to the Application.StartTransaction method and the WrapHandle and WrapHandleFunc functions. They are implemented as variadic functions such that the new option parameters are optional (i.e., zero or more options may be added to the end of the function calls) to be backward-compatible with pre-3.18.0 usage of those functions.\nThis prevents the changes from breaking existing code for typical usage of the agent. However, it does mean those functions' call signatures have changed: StartTransaction(string) -> StartTransaction(string, ...TraceOption) WrapHandle(*Application, string, http.Handler) -> WrapHandle(*Application, string, http.Handler, ...TraceOption) WrapHandleFunc(*Application, string, func(http.ResponseWriter, *http.Request)) -> WrapHandleFunc(*Application, string, func(http.ResponseWriter, *http.Request), ...TraceOption) If, for example, you created your own custom interface type which includes the StartTransaction method or something that depends on these functions' exact call semantics, that code will need to be updated accordingly before using version 3.18.0 of the Go Agent. Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you’re getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life. Note that the oldest supported version of the Go agent is 2.11.0.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-18-0","eolDate":"2023-08-01"},{"agent":"go","date":"2022-06-29","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.17.0","version":"3.17.0","features":["Logs in context is now supported for zerolog","Added integration for MS SQL Server","Added config function ConfigCustomInsightsEventsMaxSamplesStored for limiting the number of samples stored in a custom insight event"],"bugs":["Improved speed of building distributed trace header JSON payload","Renamed gRPC attributes to conform to existing naming conventions"],"security":["Updated nrgin integration to mitigate security issue in 3rd party dependency"],"supportedOperatingSystems":null,"description":"3.17.0 Added Logs in context now supported for zerolog. This is a quick way to view logs no matter where you are in the platform. Adds support for logging metrics which shows the rate of log messages by severity in the Logs chart in the APM Summary view. This is enabled by default in this release. Adds support for forwarding application logs to New Relic. This automatically sends application logs that have been enriched to power APM logs in context. This is disabled by default in this release. This will be on by default in a future release. To learn more about APM logs in context see the documentation here . Includes the RecordLog function for recording log data from a single log entry An integrated plugin for zerolog to automatically ingest log data with the Go Agent. Resolves issue 178 , issue 488 , issue 489 , issue 490 , and issue 491  . Added integration for MS SQL Server (PR 425 ; thanks @ishahid91!) This introduces the nrmssql integration v1.0.0. Added config function ConfigCustomInsightsEventsMaxSamplesStored for limiting the number of samples stored in a custom insights event. Fixes issue 476 Fixed Improved speed of building distributed trace header JSON payload. Fixes issue 505 . Renamed the gRPC attribute names from  GrpcStatusLevel, GrpcStatusMessage, and GrpcStatusCode to grpcStatusLevel, grpcStatusMessage, and grpcStatusCode respectively, to conform to existing naming conventions for New Relic agents. Fixes issue 492 . Updated go.mod for the nrgin integration to mitigate security issue in 3rd party dependency. Updated go.mod for the nrawssdk-v1 integration to properly reflect its dependency on version 3.16.0 of the Go Agent. Updated go.mod for the nrlambda integration to require aws-lambda-go version 1.20.0. (PR 356 ; thanks MattWhelan!) Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you’re getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life. Note that the oldest supported version of the Go Agent is 2.11.0.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-17-0","eolDate":"2024-06-29"},{"agent":"go","date":"2022-05-26","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.16.1","version":"3.16.1","features":[],"bugs":["Incremented version number of the nrawssdk-v1 integration to resolve an incompatibility issue"],"security":["Upgraded dependency on gRPC package in order to fix a security vulnerability"],"supportedOperatingSystems":null,"description":"3.16.1 Fixed Changed dependency on gRPC from v1.27.0 to v1.39.0. This in turn changes gRPC's dependency on x/crypto to v0.0.0-20200622213623-75b288015ac9, which fixes a security vulnerability in the x/crypto standard library module. Fixes issue #451 . Incremented version number of the nrawssdk-v1 integration from v1.0.1 to v1.1.0 to resolve an incompatibility issue due to changes to underlying code. Fixes issue #499 Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you’re getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-16-1","eolDate":"2024-05-26"},{"agent":"go","date":"2022-05-19","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.16.0","version":"3.16.0","features":["Distributed Tracing is now the default mode of operation. It may be disabled by user configuration","Added support for gathering memory statistics via PhysicalMemoryBytes functions for OpenBSD","Deprecated Cross Application Tracing"],"bugs":["Corrected some sample code to be cleaner","Updated version of nats-streaming-server","Correction to nrpkgerrors so that nrpkgerrors.Wrap now checks if the error it is passed has attributes, and if it does, copies them into the New Relic error it creates"],"security":[],"supportedOperatingSystems":null,"description":"3.16.0 Added Distributed Tracing is now the default mode of operation. It may be disabled by user configuration if so desired. PR #495 To disable DT, add newrelic.ConfigDistributedTracerEnabled(false) to your application configuration. To change the reservoir limit for how many span events are to be collected per harvest cycle from the default, add newrelic.ConfigDistributedTracerReservoirLimit(newlimit ) to your application configuration. The reservoir limit's default was increased from 1000 to 2000. The maximum reservoir limit supported is 10,000. Note that Cross Application Tracing is now deprecated. Added support for gathering memory statistics via PhysicalMemoryBytes functions for OpenBSD. Fixed Corrected some example code to be cleaner. Updated version of nats-streaming-server. PR #458 Correction to nrpkgerrors so that nrpkgerrors.Wrap  now checks if the error it is passed has attributes, and if it does, copies them into the New Relic error it creates.\nThis fixes issue #409  via PR #441 . This increments the nrpkgerrors version to v1.1.0. Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you’re getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-16-0","eolDate":"2024-05-19"},{"agent":"go","date":"2021-12-06","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.15.2","version":"3.15.2","features":["Strings logged using the agents built-in logger will have strings of the form license_key=_hex-string_ changed to license_key=[redacted]"],"bugs":[],"security":null,"supportedOperatingSystems":null,"description":"3.15.2 Added Strings logged via the Go agent's built-in logger will have strings of the form license_key=hex-string  changed to license_key=[redacted] before they are output, regardless of severity level, where hex-string  means a sequence of upper- or lower-case hexadecimal digits and dots ('.'). This incorporates PR #415 . Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you’re getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-15-2","eolDate":"2023-12-06"},{"agent":"go","date":"2021-10-27","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.15.1","version":"3.15.1","features":[],"bugs":["Updated support for SQL database instrumentation across the board to more accurately extract database table names from SQL queries"],"security":["Updated nrecho-v4 integration to address a security concern arising from downstream dependencies"],"supportedOperatingSystems":null,"description":"3.15.1 Fixed Updated support for SQL database instrumentation across the board for the Go Agent’s database integrations to more accurately extract the database table name from SQL queries. Fixes Issue #397 . Updated the go.mod file in the nrecho-v4 integration to require version 4.5.0 of the github.com/labstack/echo package. This addresses a security concern arising from downstream dependencies in older versions of the echo package, as described in the release notes  for echo v4.5.0. ARM64 Compatibility Note The New Relic Go Agent is implemented in platform-independent Go, and supports (among the other platforms which run Go) ARM64/Graviton2 using Go 1.17+. Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you’re getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-15-1","eolDate":"2023-10-27"},{"agent":"go","date":"2021-09-02","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.15.0","version":"3.15.0","features":["Added new integration for nrpgx","Enhanced debugging logs so that New Relic license keys are redacted from log output"],"bugs":[],"security":["Updated mongodb driver version to fix security issues in external dependency","Updated nrgin integration version to address a vulnerability found in lower versions of the gin package"],"supportedOperatingSystems":null,"description":"3.15.0 Fixed Updated mongodb driver version to 1.5.1 to fix security issue in external dependency. Fixes Issue #358  and Issue #370 . Updated the go.mod file in the nrgin integration to require version 1.7.0 of the github.com/gin-gonic/gin package. This addresses CVE-2020-28483  which documents a vulnerability in versions of github.com/gin-gonic/gin earlier than 1.7.0. Added New integration nrpgx added to provide the same functionality for instrumenting Postgres database queries as the existing nrpq integration, but using the pgx  driver instead. This only covers (at present) the use case of the pgx driver with the standard library database/sql. Fixes Issue #142  and Issue #292 Changed Enhanced debugging logs so that New Relic license keys are redacted from the log output. Fixes Issue #353 . Updated the advice in GUIDE.md to have correct go get commands with explicit reference to v3. Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-15-0","eolDate":"2023-09-02"},{"agent":"go","date":"2021-07-20","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.14.1","version":"3.14.1","features":["Upgraded the nrgrpc integration to version 1.3.1"],"bugs":["Fixed a typographical error in the nrgrpc unit test"],"security":[],"supportedOperatingSystems":null,"description":"3.14.1 Fixed A typographical error in the nrgrpc unit tests was fixed. Fixes Issue #344 .\nThis updates the nrgrpc integration to version 1.3.1. Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-14-1","eolDate":"2023-07-20"},{"agent":"go","date":"2021-07-12","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.14.0","version":"3.14.0","features":["Added DistributedTraceHeadersFromJSON() function to build distributed trace headers from a JSON string","Improved the NR AWS SDK V2 integration to use the current transaction rather than the one passed in during middleware creation"],"bugs":["Updated integration tags so that pkg.go.dev displays documentation for each integration correctly","Fixed an issue where the nrgrpc server integration would report all non-OK grpc statuses as errors"],"security":[],"supportedOperatingSystems":null,"description":"3.14.0 Fixed Integration tags and go.mod files for integrations were updated so that pkg.go.dev  displays the documentation for each integration correctly. The nrgrpc server integration was reporting all non-OK grpc statuses as errors. This has now been changed so that only selected grpc status codes will be reported as errors. Others are shown (via transaction attributes) as \"warnings\" or \"informational\" messages. There is a built-in set of defaults as to which status codes are reported at which severity levels, but this may be overridden by the caller as desired. Also supports custom grpc error handling functions supplied by the user. This is implemented by adding WithStatusHandler() options to the end of the UnaryServerInterceptor() and StreamServerInterceptor() calls, thus extending the capability of those functions while retaining the existing functionality and usage syntax for backward compatibility. Added advice on the recommended usage of the app.WaitForConnection() method. Fixes [https://github.com/newrelic/go-agent/issues/296](Issue #296) Added Added a convenience function to build distributed trace header set from a JSON string for use with the AcceptDistributedTraceHeaders() method. Normally, you must create a valid set of HTTP headers representing the trace identification information from the other trace so the new trace will be associated with it. This needs to be in a Go http.Header type value. If working only in Go, this may be just fine as it is. However, if the other trace information came from another source, possibly in a different language or environment, it is often the case that the trace data is already presented to you in the form of a JSON string. This new function, DistributedTraceHeadersFromJSON(), creates the required http.Header value from the JSON string without requiring manual effort on your part. We also provide a new all-in-one method AcceptDistributedTraceHeadersFromJSON() to be used in place of AcceptDistributedTraceHeaders(). It accepts a JSON string rather than an http.Header, adding its trace info to the new transaction in one step. Fixes [https://github.com/newrelic/go-agent/issues/331](Issue #331) Changed Improved the NR AWS SDK V2 integration to use the current transaction rather than the one passed in during middleware creation, if nil is passed into nrawssdk-v2.AppendMiddlewares. Thanks to @HenriBeck for noticing and suggesting improvement, and thanks to @nc-wittj for the fantastic PR! #328 Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-14-0","eolDate":"2023-07-12"},{"agent":"go","date":"2021-06-02","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.13.0","version":"3.13.0","features":["Replaced the NR AWS SDK V2 integration for the v3 agent with a newer version"],"bugs":["Fixed a bug where grpc errors would not record error responses when using the UnaryServerInterceptor() or StreamServerInterceptor() functions"],"security":[],"supportedOperatingSystems":null,"description":"3.13.0 Fixed Replaced the NR AWS SDK V2 integration for the v3 agent with a new version that works. See the v3/integrations/nrawssdk-v2/example/main.go file for an example of how to use it. Issues #250  and #288  are fixed by this PR. #309 Fixes issue #221 : grpc errors reported in code watched by UnaryServerInterceptor() or StreamServerInterceptor() now create error events which are reported to the UI with the error message string included.  #317 Fixes documentation in GUIDE.md for txn.StartExternalSegment() to reflect the v3 usage. Thanks to @abeltay for calling this to our attention and submitting PR #320 . Changes The v3/examples/server/main.go example now uses newrelic.ConfigFromEnvironment(), rather than explicitly pulling in the license key with newrelic.ConfigLicense(os.Getenv(\"NEW_RELIC_LICENSE_KEY\")). The team is starting to use this as a general systems integration testing script, and this facilitates testing with different settings enabled. Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-13-0","eolDate":"2023-06-02"},{"agent":"go","date":"2021-05-03","downloadLink":"https://github.com/newrelic/go-agent/tree/v3.12.0","version":"3.12.0","features":[],"bugs":["Fixed a bug where using DAX to query a dynamodb table would cause a nil dereference panic"],"security":[],"supportedOperatingSystems":null,"description":"3.12.0 Changes Updated CHANGELOG.md release notes language, to correct typographical errors and clean up grammar. #289 Fixed When using DAX to query a dynamodb table, the New Relic instrumentation panics with a nil dereference error. This was due to the way that the request is made internally such that there is no HTTPRequest.Header defined, but one was expected. This correction checks for the existence of that header and takes an appropriate course of action if one is not found. #287  Thanks to @odannyc for reporting the issue and providing a pull request with a suggested fix. Support Statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-3-12-0","eolDate":"2023-05-03"},{"agent":"go","date":"2019-07-10","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.9.0","version":"2.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.9.0 New Features Added support for gRPC  monitoring with the new _integrations/nrgrpc  package. This package supports instrumentation for servers and clients. Server Example Client Example Added new ExternalSegment  fields Host, Procedure, and Library. These optional fields are automatically populated from the segment's URL or Request if unset. Use them if you don't have access to a request or URL but still want useful external metrics, transaction segment attributes, and span attributes. Host is used for external metrics, transaction trace segment names, and span event names. The host of segment's Request or URL is the default. Procedure is used for transaction breakdown metrics. If set, it should be set to the remote procedure being called. The HTTP method of the segment's Request is the default. Library is used for external metrics and the \"component\" span attribute. If set, it should be set to the framework making the call. \"http\" is the default. With the addition of these new fields, external transaction breakdown metrics are changed: External/myhost.com/all will now report as External/myhost.com/http/GET (provided the HTTP method is GET). HTTP Response codes below 100, except 0 and 5, are now recorded as errors. This is to support gRPC status codes. If you start seeing new status code errors that you would like to ignore, add them to Config.ErrorCollector.IgnoreStatusCodes or your server side configuration settings. Improve logrus  support by introducing nrlogrus.Transform , a function which allows you to turn a logrus.Logger  instance into a newrelic.Logger . Example use: As a result of this change, the nrlogrus  package requires logrus  version v1.1.0 and above.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-290","eolDate":"2022-07-10"},{"agent":"go","date":"2019-06-18","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.8.1","version":"2.8.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.8.1 Bug Fixes Removed nrmysql.NewConnector since go-sql-driver/mysql  has not yet released mysql.NewConnector.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-281","eolDate":"2022-06-18"},{"agent":"go","date":"2019-06-11","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.8.0","version":"2.8","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.8.0 New Features Support for Real Time Streaming Event data is now sent to New Relic every five seconds, instead of every minute. As a result, transaction, error, and custom events will now be available in New Relic dashboards in near real time. For more information on how to view your events with a five-second refresh, see the real time streaming documentation . Note that the overall limits on how many events can be sent per minute have not changed. Also, span events, metrics, and trace data is unaffected, and will still be sent every minute. Introduce support for databases using database/sql . This new functionality allows you to instrument MySQL, PostgreSQL, and SQLite calls without manually creating DatastoreSegment s. Database Library Supported Integration Package go-sql-driver/mysql _integrations/nrmysql lib/pq _integrations/nrpq mattn/go-sqlite3 _integrations/nrsqlite3 Using these database integration packages is easy! First replace the driver with our integration version: Second, use the ExecContext, QueryContext, and QueryRowContext methods of sql.DB , sql.Conn , sql.Tx , and sql.Stmt  and provide a transaction-containing context. Calls to Exec, Query, and QueryRow do not get instrumented. If you are using a database/sql  database not listed above, you can write your own instrumentation for it using InstrumentSQLConnector , InstrumentSQLDriver , and SQLDriverSegmentBuilder . The integration packages act as examples of how to do this. For more information, see the Go agent documentation on instrumenting datastore segments . Bug Fixes The http.RoundTripper  returned by NewRoundTripper  no longer modifies the request. Our thanks to @jlordiales for the contribution.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-28","eolDate":"2022-06-11"},{"agent":"go","date":"2019-03-26","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.7.0","version":"2.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.7.0 New Features Added support for server side configuration. Server side configuration allows you to set the following configuration settings in the New Relic APM UI: Config.TransactionTracer.Enabled Config.ErrorCollector.Enabled Config.CrossApplicationTracer.Enabled Config.TransactionTracer.Threshold Config.TransactionTracer.StackTraceThreshold Config.ErrorCollector.IgnoreStatusCodes For more information see the server side configuration documentation . Added support for AWS Lambda functions in the new nrlambda  package. Please email lambda_preview@newrelic.com  if you are interested in learning more or previewing New Relic Lambda monitoring. This instrumentation package requires aws-lambda-go version v1.9.0  or higher. Documentation Working example","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-27","eolDate":"2022-03-26"},{"agent":"go","date":"2019-03-12","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.6.0","version":"2.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.6.0 New Features Added support for async: the ability to instrument multiple concurrent goroutines, or goroutines that access or manipulate the same Transaction. The new Transaction.NewGoroutine() Transaction method allows transactions to create segments in multiple goroutines! NewGoroutine returns a new reference to the Transaction. This must be called any time you are passing the Transaction to another goroutine which makes segments. Each segment-creating goroutine must have its own Transaction reference. It does not matter if you call this before or after the other goroutine has started. All Transaction methods can be used in any Transaction reference. The Transaction will end when End() is called in any goroutine. Example passing a new Transaction reference directly to another goroutine: Example passing a new Transaction reference on a channel to another goroutine: Added integration support for aws-sdk-go  and aws-sdk-go-v2 . When using these SDKs, a segment will be created for each out going request. For DynamoDB calls, these will be Datastore segments and for all others they will be External segments. v1 Documentation v2 Documentation Added span event and transaction trace segment attribute configuration. You may control which attributes are captured in span events and transaction trace segments using the Config.SpanEvents.Attributes and Config.TransactionTracer.Segments.Attributes settings. For example, if you want to disable the collection of \"db.statement\" in your span events, modify your config like this: To disable the collection of all attributes from your transaction trace segments, modify your config like this: Bug Fixes Fixed a bug that would prevent External Segments from being created under certain error conditions related to Cross Application Tracing. Miscellaneous Improved linking between Cross Application Transaction Traces in the APM UI. When Config.CrossApplicationTracer.Enabled = true, External segments in the Transaction Traces details will now link to the downstream Transaction Trace if there is one. Additionally, the segment name will now include the name of the downstream application and the name of the downstream transaction. Update attribute names of Datastore and External segments on Transaction Traces to be in line with attribute names on Spans. Specifically: \"uri\" => \"http.url\" \"query\" => \"db.statement\" \"database_name\" => \"db.instance\" \"host\" => \"peer.hostname\" \"port_path_or_id\" + \"host\" => \"peer.address\"","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-26","eolDate":"2022-03-12"},{"agent":"go","date":"2019-02-14","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.5.0","version":"2.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.5.0 Added support for New Relic Browser  using the new BrowserTimingHeader method on the Transaction  which returns a BrowserTimingHeader . The New Relic Browser JavaScript code measures page load timing, also known as real user monitoring. The Pro version of this feature measures AJAX requests, single-page applications, JavaScript errors, and much more! Example use: The Go agent now collects an attribute named request.uri on Transaction Traces, Transaction Events, Error Traces, and Error Events. request.uri will never contain user, password, query parameters, or fragment. To prevent the request's URL from being collected in any data, modify your Config like this:","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-25","eolDate":"2022-02-14"},{"agent":"go","date":"2019-01-31","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.4.0","version":"2.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.4.0 Notes Introduced Transaction.Application method which returns the Application that started the Transaction. This method is useful since it may prevent having to pass the Application to code that already has access to the Transaction. Example use: The Transaction.AddAttribute method no longer accepts nil values since our backend ignores them.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-24","eolDate":"2022-01-31"},{"agent":"go","date":"2019-01-24","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.3.0","version":"2.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.3.0 Notes Added support for Echo  in the new nrecho package. Documentation Example Introduced Transaction.SetWebResponse(http.ResponseWriter) method which sets the transaction's response writer. After calling this method, the Transaction may be used in place of the http.ResponseWriter to intercept the response code. This method is useful when the http.ResponseWriter is not available at the beginning of the transaction (if so, it can be given as a parameter to Application.StartTransaction). This method will return a reference to the transaction which implements the combination of http.CloseNotifier, http.Flusher, http.Hijacker, and io.ReaderFrom implemented by the ResponseWriter. Example: The Transaction's http.ResponseWriter methods may now be called safely if a http.ResponseWriter has not been set. This allows you to add a response code to the transaction without using a http.ResponseWriter. Example: The agent will now collect environment variables prefixed by NEW_RELIC_METADATA_ and KUBERNETES_SERVICE_HOST. These will be added to Transaction events to provide context between your Kubernetes cluster and your services. For details on the benefits (currently in beta) see this blog post The agent now collects the fully qualified domain name of the host and local IP addresses for improved linking with our Infrastructure product.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-23","eolDate":"2022-01-24"},{"agent":"go","date":"2018-12-18","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.2.0","version":"2.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.2 Notes The Transaction parameter to NewRoundTripper  and StartExternalSegment  is now optional: If it is nil, then a Transaction will be looked for in the request's context (using FromContext ). Passing a nil transaction is STRONGLY  recommended when using NewRoundTripper  since it allows one http.Client.Transport to be used for multiple transactions. Example use: Introduced Transaction.SetWebRequest(WebRequest) method which marks the transaction as a web transaction. If the WebRequest parameter is non-nil, SetWebRequest will collect details on request attributes, url, and method. This method is useful if you don't have access to the request at the beginning of the transaction, or if your request is not an *http.Request (just add methods to your request that satisfy WebRequest ). To use an *http.Request as the parameter, use the NewWebRequest  transformation function. Example: Fixed Debug in nrlogrus package. Previous versions of the New Relic Go Agent incorrectly logged to Info level instead of Debug. This has now been fixed. Thanks to @paddycarey for catching this. nrgin.Transaction  may now be called with either a context.Context or a *gin.Context. If you were passing a *gin.Context around your functions as a context.Context, you may access the Transaction by calling either nrgin.Transaction  or FromContext . These functions now work nicely together. For example, FromContext  will return the Transaction added by nrgin.Middleware . Thanks to @rodriguezgustavo for the suggestion.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-22","eolDate":"2021-12-18"},{"agent":"go","date":"2019-12-11","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.16.3","version":"2.16.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes New Relic's Go agent v3.0 is currently available for review and beta testing. Your use of this pre-release is at your own risk. New Relic disclaims all warranties, express or implied, regarding the beta release. If you do not manually take steps to use the new v3 folder you will not see any changes in your agent. This is the third release of the pre-release of Go agent v3.0. It includes changes due to user feedback during the pre-release. The existing agent in`\"github.com/newrelic/go-agent\"` is unchanged. Fixes The Go agent v3.0 code in the v3 folder has the following changes: A ConfigFromEnvironment  bug has been fixed.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-2163","eolDate":"2022-12-11"},{"agent":"go","date":"2019-12-10","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.16.2","version":"2.16.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.16.2 New Relic's Go agent v3.0 is currently available for review and beta testing. Your use of this pre-release is at your own risk. New Relic disclaims all warranties, express or implied, regarding the beta release. If you do not manually take steps to use the new v3 folder you will not see any changes in your agent. This is the second release of the pre-release of Go agent v3.0. It includes changes due to user feedback during the pre-release. The existing agent in \"github.com/newrelic/go-agent\" is unchanged. The Go agent v3.0 code in the v3 folder has the following changes: Transaction names created by WrapHandle , WrapHandleFunc , nrecho-v3 , nrecho-v4 , nrgorilla , and nrgin  now include the HTTP method. For example, the following code: now creates a metric called WebTransaction/Go/GET /users instead of WebTransaction/Go/users. As a result of this change, you may need to update your alerts and dashboards. The ConfigFromEnvironment  config option is now strict. If one of the environment variables, such as NEW_RELIC_DISTRIBUTED_TRACING_ENABLED, cannot be parsed, then Config.Error will be populated and NewApplication  will return an error. ConfigFromEnvironment  now processes NEW_RELIC_ATTRIBUTES_EXCLUDE and NEW_RELIC_ATTRIBUTES_INCLUDE.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-2162","eolDate":"2022-12-10"},{"agent":"go","date":"2019-12-02","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.16.1","version":"2.16.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.16.1 New Relic's Go agent v3.0 is currently available for review and beta testing. Your use of this pre-release is at your own risk. New Relic disclaims all warranties, express or implied, regarding the beta release. If you do not manually take steps to use the new v3 folder, as described below, you will not see any changes in your agent. This 2.16.1 release includes a new v3.0 folder which contains the pre-release of Go agent v3.0; Go agent v3.0 includes breaking changes. We are seeking feedback and hope that you will look this over and test out the changes prior to the official release. This is not an official 3.0 release, it is just a vehicle to gather feedback on proposed changes . It is not tagged as 3.0 in Github and the 3.0 release is not yet available to update in your Go mod file. In order to test out these changes, you will need to clone this repo in your Go source directory, under [go-src-dir]/src/github.com/newrelic/go-agent. Once you have the source checked out, you will need to follow the steps in the second section of v3/MIGRATION.md . A list of changes and installation instructions is included in the v3 folder and can be found here For this pre-release (beta) version of Go agent v3.0, please note: The changes in the v3 folder represent what we expect to release in 2 weeks as our major 3.0 release. However, as we are soliciting feedback on the changes and there is the possibility of some breaking changes before the official release. This is not an official 3.0 release; it is not tagged as 3.0 in Github and the 3.0 release is not yet available to update in your Go mod file. If you test out these changes and encounter issues, questions, or have feedback that you would like to pass along, please open up an issue here  and be sure to include the label 3.0. For normal (non-3.0) issues/questions we request that you report them via our support site  or our community forum . Please only report questions related to the 3.0 pre-release directly via GitHub. New Features V3 will add support for Go Modules. The go.mod files exist in the v3 folder, but they will not be usable until we have fully tagged the 3.0 release officially. Examples of version tags we plan to use for different modules include: v3.0.0 v3/integrations/nrecho-v3/v1.0.0 v3/integrations/nrecho-v4/v1.0.0 Changes The changes are the ones that we have requested feedback previously in this issue . A full list of changes that are included, along with a checklist for upgrading, is available in v3/MIGRATION.md .","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-2161","eolDate":"2022-12-02"},{"agent":"go","date":"2019-11-22","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.16.0","version":"2.16.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.16.0 Upcoming The next release of the Go Agent is expected to be a major version release to improve the API and incorporate Go modules. Details available here: https://github.com/newrelic/go-agent/issues/106  We would love your feedback! Bug Fixes Fixed an issue in the nrhttprouter  integration where the transaction was not being added to the requests context. This resulted in an inability to access the transaction from within an httprouter.Handle  function. This issue has now been fixed.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-2160","eolDate":"2022-11-22"},{"agent":"go","date":"2019-10-24","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.14.1","version":"2.15.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.15.0 New Features Added support for monitoring MongoDB  queries with the new _integrations/nrmongo  package. Example application Full godocs Documentation Added new method Transaction.IsSampled() that returns a boolean that indicates if the transaction is sampled. A sampled transaction records a span event for each segment. Distributed tracing must be enabled for transactions to be sampled. false is returned if the transaction has finished. This sampling flag is needed for B3 trace propagation and future support of W3C Trace Context. Added support for adding B3 Headers  to outgoing requests. This is helpful if the service you are calling uses B3 for trace state propagation (for example, it uses Zipkin instrumentation). You can use the new _integrations/nrb3  package's nrb3.NewRoundTripper  like this:","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-2150","eolDate":"2022-10-24"},{"agent":"go","date":"2019-10-15","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.14.1","version":"2.14.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.14.1 Bug Fixes Removed the hidden \"NEW_RELIC_DEBUG_LOGGING\" environment variable setting which was broken in release 2.14.0.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-2141","eolDate":"2022-10-15"},{"agent":"go","date":"2019-10-14","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.14.0","version":"2.14.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.14.0 New Features Added support for a new segment type, MessageProducerSegment , to be used to track time spent adding messages to message queuing systems like RabbitMQ or Kafka. Added new attribute constants for use with message consumer transactions. These attributes can be used to add more detail to a transaction that tracks time spent consuming a message off a message queuing system like RabbitMQ or Kafka. They can be added using txn.AddAttribute . It is recommended that at most one message is consumed per transaction. Added support for Go 1.13's Error wrapping . Transaction.NoticeError now uses Unwrap  recursively to identify the error's cause (the deepest wrapped error) when generating the error's class field. This functionality will help group your errors usefully. For example, when using Go 1.13, the following code: captures an error with message \"problem in alpha: problem in beta: socket error\" and class \"main.socketError\". Previously, the class was recorded as \"*fmt.wrapError\". A Stack field has been added to Error , which can be assigned using the new NewStackTrace  function. This allows your error stack trace to show where the error happened, rather than the location of the NoticeError call. Transaction.NoticeError not only checks for a stack trace (using StackTracer ) in the error parameter, but in the error's cause as well. This means that you can create an Error  where your error occurred, wrap it multiple times to add information, notice it with NoticeError, and still have a useful stack trace. Take a look! In this example, the topmost stack trace frame recorded is \"gamma\", rather than \"execute\". Added support for configuring a maximum number of transaction events per minute to be sent to New Relic. It can be configured as follows: For additional configuration information, see our documentation Miscellaneous Updated the nrmicro  package to use the new segment type MessageProducerSegment  and the new attribute constants: nrmicro.ClientWrapper  now uses newrelic.MessageProducerSegments instead of newrelic.ExternalSegments for calls to Client.Publish . nrmicro.SubscriberWrapper  updates transaction names and adds the attribute message.routingKey. Updated the nrnats  and nrstan  packages to use the new segment type MessageProducerSegment  and the new attribute constants: nrnats.StartPublishSegment  now starts and returns a newrelic.MessageProducerSegment type. nrnats.SubWrapper  and nrstan.StreamingSubWrapper  updates transaction names and adds the attributes message.routingKey, message.queueName, and message.replyTo.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-2140","eolDate":"2022-10-14"},{"agent":"go","date":"2019-09-23","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.13.0","version":"2.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.13.0 New Features Added support for HttpRouter  in the new _integrations/nrhttprouter  package. This package allows you to easily instrument inbound requests through the HttpRouter framework. Documentation Example Added support for github.com/uber-go/zap  in the new _integrations/nrzap  package. This package allows you to send agent log messages to zap.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-2130","eolDate":"2022-09-23"},{"agent":"go","date":"2019-09-17","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.12.0","version":"2.12.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added new methods to expose Transaction details: Transaction.GetTraceMetadata() returns a TraceMetadata  which contains distributed tracing identifiers. Transaction.GetLinkingMetadata() returns a LinkingMetadata  which contains the fields needed to link data to a trace or entity. Added a new plugin for the Logrus logging framework  with the new _integrations/logcontext/nrlogrusplugin  package. This plugin leverages the new GetTraceMetadata and GetLinkingMetadata above to decorate logs. To enable, set your log's formatter to the nrlogrusplugin.ContextFormatter{} The logger will now look for a newrelic.Transaction inside its context and decorate logs accordingly. Therefore, the Transaction must be added to the context and passed to the logger. For example, this logging call must be transformed to include the context, such as: For full documentation see the godocs  or view the example . Added support for NATS  and NATS Streaming  monitoring with the new _integrations/nrnats  and _integrations/nrstan  packages. These packages support instrumentation of publishers and subscribers. NATS Example NATS Streaming Example Enables ability to migrate to Configurable Security Policies (CSP)  on a per agent basis for accounts already using High-security mode (HSM) . Previously, if CSP was configured for an account, New Relic would not allow an agent to connect without the security_policies_token. This led to agents not being able to connect during the period between when CSP was enabled for an account and when each agent is configured with the correct token. With this change, when both HSM and CSP are enabled for an account, an agent (this version or later) can successfully connect with either high_security: true or the appropriate security_policies_token configured - allowing the agent to continue to connect after CSP is configured on the account but before the appropriate security_policies_token is configured for each agent.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-2120","eolDate":"2022-09-17"},{"agent":"go","date":"2019-08-22","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.11.0","version":"2.11.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added support for Micro  monitoring with the new _integrations/nrmicro  package. This package supports instrumentation for servers, clients, publishers, and subscribers. Server Example Client Example Publisher and Subscriber Example Full godocs Documentation Added support for creating static WebRequest instances manually via the NewStaticWebRequest function. This can be useful when you want to create a web transaction but don't have an http.Request object. Here's an example of creating a static WebRequest and using it to mark a transaction as a web transaction:","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-2110","eolDate":"2022-08-22"},{"agent":"go","date":"2019-07-31","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.10.0","version":"2.10.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.10.0 New Features Added support for custom events when using nrlambda . Example Lambda handler which creates custom event:","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-2100","eolDate":"2022-07-31"},{"agent":"go","date":"2018-08-28","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.1.0","version":"2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.1.0 New Go Agent now supports distributed tracing Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before. Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide  before you enable this feature. To enable distributed tracing, set the following fields in your config. Note that distributed tracing and cross application tracing cannot be used simultaneously. Please refer to the distributed tracing section of the guide  for more detail on how to ensure you get the most out of the Go agent's distributed tracing support. New distributed trace calls/functions Added functions NewContext  and FromContext  for adding and retrieving the Transaction from a Context. Handlers instrumented by WrapHandle , WrapHandleFunc , and nrgorilla.InstrumentRoutes  may use FromContext  on the request's context to access the Transaction. Thanks to @caarlos0 for the contribution! Though NewContext  and FromContext  require Go 1.7+ (when context  was added), RequestWithTransactionContext  is always exported so that it can be used in all framework and library instrumentation.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-21","eolDate":"2021-08-28"},{"agent":"go","date":"2018-05-15","downloadLink":"https://github.com/newrelic/go-agent/tree/v2.0.0","version":"2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"2.0.0 New The End() functions defined on the Segment, DatastoreSegment, and ExternalSegment types now receive the segment as a pointer, rather than as a value. This prevents unexpected behaviour when a call to End() is deferred before one or more fields are changed on the segment. In practice, this is likely to only affect this pattern: Instead, you will now need to separate the literal from the deferred call: When creating custom and external segments, we recommend using newrelic.StartSegment()  and newrelic.StartExternalSegment() , respectively. Added GoDoc badge to README. Thanks to @mrhwick for the contribution! Config.UseTLS configuration setting has been removed to increase security. TLS will now always be used in communication with New Relic Servers.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-20","eolDate":"2021-05-15"},{"agent":"go","date":"2017-04-18","downloadLink":"https://github.com/newrelic/go-agent","version":"1.9","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Added support for github.com/gin-gonic/gin  in the new nrgin package. Documentation","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-19","eolDate":"2020-04-18"},{"agent":"go","date":"2017-03-17","downloadLink":"https://github.com/newrelic/go-agent","version":"1.8","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixed incorrect metric rule application when the metric rule is flagged to terminate and matches but the name is unchanged. Segment.End(), DatastoreSegment.End(), and ExternalSegment.End() methods now return an error which may be helpful in diagnosing situations where segment data is unexpectedly missing.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-18","eolDate":"2020-03-17"},{"agent":"go","date":"2017-02-16","downloadLink":"https://github.com/newrelic/go-agent","version":"1.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Added support for gorilla/mux  in the new nrgorilla package. Documentation Example","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-17","eolDate":"2020-02-16"},{"agent":"go","date":"2017-02-09","downloadLink":"https://github.com/newrelic/go-agent","version":"1.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Added support for custom error messages and stack traces. Errors provided to Transaction.NoticeError will now be checked to see if they implement ErrorClasser  and/or StackTracer . Thanks to @fgrosse for this proposal. Added support for pkg/errors . Thanks to @fgrosse for this work. documentation example Fixed tests for Go 1.8.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-16","eolDate":"2020-02-09"},{"agent":"go","date":"2016-10-12","downloadLink":"https://github.com/newrelic/go-agent","version":"1.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Added support for slow query traces. Slow datastore segments will now generate slow query traces viewable on the datastore tab. These traces include a stack trace and help you to debug slow datastore activity . Added new DatastoreSegment  fields ParameterizedQuery, QueryParameters, Host, PortPathOrID, and DatabaseName. These fields will be shown in transaction traces and in slow query traces.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-14","eolDate":"2019-10-12"},{"agent":"go","date":"2016-10-07","downloadLink":"https://github.com/newrelic/go-agent","version":"1.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Added a timeout parameter to the Application.Shutdown method.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-13","eolDate":"2019-10-07"},{"agent":"go","date":"2016-10-06","downloadLink":"https://github.com/newrelic/go-agent","version":"1.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Added support for instrumenting short-lived processes: The new Application.Shutdown method allows applications to report data to New Relic without waiting a full minute. The new Application.WaitForConnection method allows your process to defer instrumentation until the application is connected and ready to gather data. Full documentation here: application.go Example short-lived process: examples/short-lived-process/main.go Error metrics are no longer created when ErrorCollector.Enabled = false. Added support for http://wwwgithub.com/mgutz/logxi . See https://github.com/newrelic/go-agent/blob/master/_integrations/nrlogxi/v1/nrlogxi.go . Fixed bug where Transaction Trace thresholds based upon Apdex were not being applied to background transactions.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-12","eolDate":"2019-10-06"},{"agent":"go","date":"2017-11-29","downloadLink":"https://github.com/newrelic/go-agent/tree/v1.11.0","version":"1.11","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added support for Cross Application Tracing (CAT). Please refer to the upgrading section of the guide  for more detail on how to ensure you get the most out of the Go agent's new CAT support. The agent now collects additional metadata when running within Amazon Web Services, Google Cloud Platform, Microsoft Azure, and Pivotal Cloud Foundry. This information is used to provide an enhanced experience when the agent is deployed on those platforms.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-111","eolDate":"2020-11-29"},{"agent":"go","date":"2017-10-24","downloadLink":"https://github.com/newrelic/go-agent/tree/v1.10.0","version":"1.10","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Added new RecordCustomMetric method to Application . This functionality can be used to track averages or counters without using custom events. See Custom Metric Documentation Fixed import needed for logrus. The import Sirupsen/logrus had been renamed to sirupsen/logrus. Thanks to @alfred-landrum for spotting this. Added ErrorAttributer , an optional interface that can be implemented by errors provided to Transaction.NoticeError to attach additional attributes. These attributes are subject to attribute configuration. Added Error , a type that allows direct control of error fields. Updated license to address scope of usage.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-110","eolDate":"2020-10-24"},{"agent":"go","date":"2016-09-07","downloadLink":"https://github.com/newrelic/go-agent","version":"1.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Added support for Transaction Traces. Stack trace filenames have been shortened: Any thing preceding the first /src/ is now removed.","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-11","eolDate":"2019-09-07"},{"agent":"go","date":"2016-08-08","downloadLink":"https://github.com/newrelic/go-agent","version":"1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Removed BetaToken from the Config structure. Breaking Datastore change: datastore package contents moved to top level newrelic package. datastore.MySQL has become newrelic.DatastoreMySQL. Breaking Attributes change: attributes package contents moved to top level newrelic package. attributes.ResponseCode has become newrelic.AttributeResponseCode. Some attribute name constants have been shortened. Added \"runtime.NumCPU\" to the environment tab. Thanks sergeylanzman for the contribution. Prefixed the environment tab values \"Compiler\", \"GOARCH\", \"GOOS\", and \"Version\" with \"runtime.\"","slug":"docs/release-notes/agent-release-notes/go-release-notes/go-agent-10","eolDate":"2019-08-08"},{"agent":"nodejs","date":"2015-06-05","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.20.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Triaged a defect in native promise instrumentation Transactions used to be lost acrossed chained .then calls. The way promises are wrapped has been changed to fix this issue. Added support for Slow Queries Slow Query information will now appear in the UI for Node agent users. This feature allows you to see a trace for slow datastore queries. Read more about this feature in our documentation","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/nodejs-agent-1200","eolDate":"2018-06-05"},{"agent":"nodejs","date":"2015-05-21","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.19.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixed an issue with Error tracing Previously the agent could sometimes cause issues with user serialization of error Âobjects after they passed through the error tracing code. MongoDB cursor count method is now instrumented The count method on MongoDB cursors is now instrumented. Previously, count would not be included in transaction traces. Fixed a typo in NEWS.md Previously the release notes for v1.19.1 were included as notes for 1.19.0. This has now fixed thanks to @bruun","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/nodejs-agent-1192","eolDate":"2018-05-21"},{"agent":"nodejs","date":"2015-05-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.19.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixed a bug in native ES6 Promise instrumentation. Previously the Promise instrumentation would cause instanceof Promise to return false even if the object was a promise. This also caused an incompatibility with async-listener. instanceof checks will now work on both the wrapped and unwrapped Promise object.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/nodejs-agent-1191","eolDate":"2018-05-14"},{"agent":"nodejs","date":"2015-04-16","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.18.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Wrapped all our calls to JSON.parse in try/catch. Previously, only calls that were considered unsafe due to external data input were wrapped. We are taking a more defensive stance and wrapping them all now. Timers attached to global are now instrumented correctly in all version of io.js. As of v1.6.3 of io.js, timers are no longer lazily loaded from the timers module, and are placed directly on the global object. The agent now takes this change into account and accurately wraps the timer methods. Improved handling of cross-application tracing headers. Paths that include multibyte characters will now show up correctly in cross application maps","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/nodejs-agent-1183","eolDate":"2018-04-16"},{"agent":"nodejs","date":"2015-02-25","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.17.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Added instrumentation for modules in Node core. Added support for native Promises in Node.js 0.12 and io.js 1.x. Traces will now contain separate segments for async waits and callbacks. Updated instrumentation for MongoDB to support previously un-instrumented methods for 1.x and 2.x versions of the node-mongodb-native driver. Fixed a bug in the recording of transaction metrics. Previously this would cause a duplicate of the transaction metric to be displayed in the transaction breakdown chart Unified view for SQL database and NoSQL datastore products. The response time charts in the application overview page will now include NoSQL datastores, such as Cassandra and MongoDB,and also the product name of existing SQL databases such as MySQL, Postgres, Oracle, etc. For existing SQL databases, in addition to the existing breakdown of SQL statements and operations, the queries are now also associated with the database product being used. For NoSQL datastores, such as Cassandra and MongoDB, we have now added information about operations performed against those products, similar to what is being done for SQL databases. This new unified Databases page will enable the filtering of metrics and operations by product, and includes a table listing all operations. Because this introduces a notable change to how SQL database metrics are collected, it is important that you upgrade the agent version on all hosts. If you are unable to transition to the latest agent version on all hosts at the same time, you can still access old and new metric data for SQL databases, but the information will be split across two separate views.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/nodejs-agent-1170","eolDate":"2018-02-25"},{"agent":"nodejs","date":"2023-02-06","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.9.0","features":["Add support for url obfuscation using regex.","Add a new tracking type of instrumentation for logging metrics."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added support for URL obfuscation using regex (Thanks for your contribution @matewilk) For Distributed Tracing, this means that: Incoming and outgoing requests' path will be obfuscated Transaction's request.url attribute will be obfuscated Span's http.uri path will be obfuscated For transactions, this means that: Transaction trace details url will be obfuscated With the following example configuration, URL obfuscation will turn /api/v1/users/12345456/edit to /api/v1/users/**/edit. You can also use environment variables to configure URL obfuscation: Add a new tracking type of instrumentation.  This will be responsible for logging Supportability/Features/Instrumentation/OnResolved/<pkg> and Supportability/Features/Instrumentation/OnResolved/<pkg>/Version/<version> metrics when packages are required. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-9-0","eolDate":"2024-02-06"},{"agent":"nodejs","date":"2023-01-25","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.8.1","features":["Instrument `winston.loggers.add.","Change GCP metadata parsing to use `json-bigint`."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Changed GCP metadata parsing to use json-bigint to avoid loss of precision from numerical instance ID. Instrumented winston.loggers.add so it works like winston.createLogger. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-8-1","eolDate":"2024-01-25"},{"agent":"nodejs","date":"2023-01-17","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.8.0","features":["Update `getBrowserTimingHeader` by adding `allowTransactionlessinject` to function options."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Updated getBrowserTimingHeader to allow the browser agent to be generated even when not in a transaction by adding allowTransactionlessInjection to function options. allowTransactionlessInjection is a boolean option, and when set to true, will allow injection of the browser agent when not in a transaction. This is intended to be used in frameworks that build Static Site Generation(SSG). Note that if you're using this option, you may need to wait until the Node agent has established a connection before calling getBrowserTimingHeader. To wait until the agent is connected, you can add the following check to your code: Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-8-0","eolDate":"2024-01-17"},{"agent":"nodejs","date":"2023-01-03","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.7.5","features":["Add a check to the code level metrics utility to ensure filePath was set before adding the `code.*` attributes."],"bugs":["Fix connection issue where listing of dependencies and packages from symlinked nested directories created an infinite loop."],"security":[],"supportedOperatingSystems":null,"description":"Notes Added a check to the code level metrics utility to ensure filePath was set before adding the code.* attributes. Updated to latest version of @newrelic/test-utilities. Fixed issue where listing of dependencies and packages from symlinked nested directories created an infinite loop which caused the agent to never connect. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-7-5","eolDate":"2024-01-03"},{"agent":"nodejs","date":"2022-12-15","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.7.4","features":[],"bugs":["Fix system info gathering to prevent unhandled promise rejection when an error occurs reading `/proc` information."],"security":[],"supportedOperatingSystems":null,"description":"Notes Fixed system info gathering to prevent unhandled promise rejection when an error occurs reading /proc information. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-7-4","eolDate":"2023-12-15"},{"agent":"nodejs","date":"2022-12-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.7.3","features":["Add support for Code Level Metrics on API methods."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added support for Code Level Metrics on API methods: startSegment, startBackgroundTransaction, and startWebTransaction. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-7-3","eolDate":"2023-12-12"},{"agent":"nodejs","date":"2022-12-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.7.2","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Updated @grpc/grpc-js instrumentation to work with 1.8.0. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-7-2","eolDate":"2023-12-07"},{"agent":"nodejs","date":"2022-12-06","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.7.1","features":["Reintroduce throttling during startup to prevent EMFILE issues.","Add a new test stanza to run Restify >=10 on Node 18.","Add `newrelic.noticeError()` example to our API docs.","Remove async from benchmark tests, fix failing benchmark suites, and remove deprecated suites."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Reintroduced throttling during reading of instrumented application's dependency tree during startup, to prevent EMFILE issues. Improved Restify support Added a new test stanza to run restify >=10 on Node 18. Update our versioned tests to support Restify 9.0.0. Laid foundation for supporting Code Level Metrics via CodeStream . Note that this integration is not fully finished and should not be used. Improved the readability and maintainability of agent by reducing the Cognitive Complexity  of various aspects of the agent. Added newrelic.noticeError() example to our API docs. Upgraded @grpc/grpc-js from 1.6.9 to 1.7.3. Upgraded @grpc/proto-loader from 0.6.13 to 0.7.3. Removed async from benchmark tests, fixed failing benchmark suites, and removed deprecated suite. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-7-1","eolDate":"2023-12-06"},{"agent":"nodejs","date":"2022-11-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.7.0","features":["Add new configuration option, `grpc.ignore_status_codes`."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added new configuration option, grpc.ignore_status_codes, which can be used to select nonzero gRPC status codes to ignore and not report as errors. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-7-0","eolDate":"2023-11-14"},{"agent":"nodejs","date":"2022-11-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.6.0","features":["Drop support for `vision` and instead only instrument `@hapi/vision`.","Update configuration system to automatically create an environment variable mapping for a new config value.","Remove `transaction_tracer.hide_internals` configuration."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Dropped support for vision, and instead only instrument @hapi/vision. Updated configuration system to automatically create an environment variable mapping for a new config value. It will follow a convention of NEW_RELIC_PATH_TO_CONFIG_KEY. For example if there is a new configuration option of config.nested.object_path.enabled the env var would be NEW_RELIC_NESTED_OBJECT_PATH.ENABLED. Removed transaction_tracer.hide_internals configuration. All of the internal configuration is now handled by Javascript symbols instead of non-enumerable properties, so there is no longer a performance penalty, as symbols are already hidden by default. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-6-0","eolDate":"2023-11-09"},{"agent":"nodejs","date":"2022-10-26","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.5.0","features":["Increase the default limit of custom events from 1,000 events per minute to 3,000 events per minute.","Add a document for our current feature flags."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Increased the default limit of custom events from 1,000 events per minute to 3,000 events per minute. In the scenario that custom events were being limited, this change will allow more custom events to be sent to New Relic. There is also a new configurable maximum limit of 100,000 events per minute. To change the limits, see the docs for custom_insights_events . To learn more about the change and how to determine if custom events are being dropped, see our Explorers Hub post . Updated CI process to include collection of code coverage statistics. Added a [doc about our current feature flags)(https://github.com/newrelic/node-newrelic/blob/main/documentation/feature-flags.md ). Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-5-0","eolDate":"2023-10-26"},{"agent":"nodejs","date":"2022-10-24","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.4.0","features":["Remove legacy agent async context propagation.","Add an API for enqueuing application logs for forwarding.","Add a new context manager that leverages AsyncLocalStorage for async context propagation."],"bugs":["Fix an issue with the ES Module loader that properly registers instrumentation.","Fix `cassandra-driver` instrumentation to properly set instance details on query segments/spans."],"security":[],"supportedOperatingSystems":null,"description":"Notes Removed legacy agent async context propagation. The default behavior is now what was behind the feature_flag.new_promise_tracking. You can read more about the difference here . Fixed an issue with the ES Module loader that properly registers instrumentation when the file path included url encoded characters. Added an API for enqueuing application logs for forwarding Note : If you're including a serialized error make sure it's on the error key of the log event: Fixed cassandra-driver instrumentation to properly set instance details on query segments/spans. Added a new context manager that leverages AsyncLocalStorage for async context propagation. This will be available via a feature flag config.feature_flag.async_local_context Alternatively you can set the environment variable of NEW_RELIC_FEATURE_FLAG_ASYNC_LOCAL_CONTEXT=1 By enabling this feature flag it should make the agent use less memory and CPU. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-4-0","eolDate":"2023-10-24"},{"agent":"nodejs","date":"2022-10-17","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.3.0","features":["Add instrumentation to bunyan to support application logging.","Add c8 to track code coverage.","Add documentation about custom instrumentation in ES module applications."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added instrumentation to bunyan to support application logging use cases: forwarding, local decorating, and metrics.\nBig thanks to @brianphillips for his contribution Added c8 to track code coverage. Added documentation about custom instrumentation in ES module applications Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-3-0","eolDate":"2023-10-17"},{"agent":"nodejs","date":"2022-10-06","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.2.0","features":["Remove `application_logging.forwarding.enabled` stanza from sample config as the feature is now enabled by default.","Add ability to instrument ES Modules with the New Relic ESM Loader.","Add support for custom ESM instrumentation.","Add supportability metric."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added ability to instrument ES Modules with the New Relic ESM Loader. Example ESM application Added support for custom ESM instrumentation. There is structure to registering custom ESM instrumentation.  Set the relative path to the instrumentation entry point via api.esm.custom_instrumentation_entrypoint Sample custom ESM instrumentation entrypoint All the newrelic.instrument* methods will still work except newrelic.instrumentLoadedModule.  This is because it is geared toward CommonJS modules. Added test for asserting ESM loader functionality on ESM-only package Added supportability metric of Supportability/Nodejs/Collector/MaxPayloadSizeLimit/<endpoint> when max_payload_size_in_bytes configuration value is exceeded. Removed application_logging.forwarding.enabled stanza from sample config as the feature is now enabled by default. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-2-0","eolDate":"2023-10-06"},{"agent":"nodejs","date":"2023-04-04","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.15.0","features":["Added a new configuration option `heroku.use_dyno_names` to specify whether or not to use `process.env.DYNO` for naming the host name and display host"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added a new configuration option heroku.use_dyno_names to specify whether or not to use process.env.DYNO for naming the host name and display host.  This option defaults to true.  If you are on heroku and do not want this functionality set heroku.use_dyno_names to false.  You can also control this configuration options with the environment variable of NEW_RELIC_HEROKU_USE_DYNO_NAMES. Thanks @benney-au-le  for your contribution 🚀 Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-15-0","eolDate":"2024-04-04"},{"agent":"nodejs","date":"2023-03-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.14.1","features":[],"bugs":["Fix to properly detect attempts to load agent more than once."],"security":[],"supportedOperatingSystems":null,"description":"Notes Restored assigning loaded version of agent to require.cache as __NR_cache instead of a symbol to properly detect attempts at loading agent twice. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-14-1","eolDate":"2024-03-23"},{"agent":"nodejs","date":"2023-03-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.14.0","features":["Add new API `setErrorGroupCallback` to allown error grouping by setting `error.group.name` attribute."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added new API function called setErrorGroupCallback, which provides a way for you to customize the error.group.name attribute of errors that are captured by the agent. This attribute controls how the Errors Inbox functionality groups similar errors together. To learn more about this function, please refer to our example app . Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-14-0","eolDate":"2024-03-23"},{"agent":"nodejs","date":"2023-03-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.13.0","features":["Update http instrumentation to no longer remove the `x-new-relic-disable-dt` header when using AWS SDK v3.","Add API method `setUserID` to provide ability to group transaction events, traces, and errors within a transaction.`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Updated http instrumentation to no longer remove the x-new-relic-disable-dt header when using AWS SDK v3.  This was done to prevent the \"The request signature we calculated does not match the signature you provided. Check your key and signing method.\" error from AWS SDK. Added an API method setUserID to provide an ability to associate a unique identifier with a transaction event, transaction trace and errors within transaction.  The attribute will be enduser.id. Added default configuration for security agent. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-13-0","eolDate":"2024-03-20"},{"agent":"nodejs","date":"2023-03-15","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.12.1","features":["Add ability to mark errors as expected using `newrelic.noticeError.","Ability to disable distributed tracing for aws-sdk >= 3.290.0."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added ability to mark errors as expected when using newrelic.noticeError, by adding an optional boolean: newrelic.noticeError(error, {customAttributes}, true|false) when there are custom error attributes. newrelic.noticeError(error, true|false) if there are no custom error attributes. expected errors do not affect error metrics or Apdex. Added ability to disable distributed tracing for aws-sdk 3.290.0 and higher. Updated README header image to latest OSS office required images Updated @grpc/grpc-js from 1.8.8 to 1.8.9 Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-12-1","eolDate":"2024-03-15"},{"agent":"nodejs","date":"2023-03-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.12.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This version of the agent was not available, and has been deprecated. The NPM release pipeline did not run successfully. New Relic recommends installing Node agent v9.12.1 instead. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-12-0","eolDate":"2024-03-14"},{"agent":"nodejs","date":"2023-03-08","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.11.0","features":["Add instrumentation for Prisma(`@prisma/client`) with minimum supported version 4.0.0."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added instrumentation for Prisma(@prisma/client). Miniumum supported version of @prisma/client is 4.0.0. Captures spans for queries. It names them based on the model and action.(i.e. Datastore/statement/Prisma/user/create) For statements and queries using the $queryRaw, $executeRaw, $queryRawUnsafe, and $executeRawUnsafe the names will be aligned with the raw SQL.(i.e. Datastore/statement/Prisma/User/select) Captures database metrics for all statements and queries. Captures SQL Traces. Provides connection between application and database server via service maps. Huge shoutout to @osmanmrtacar for the original contribution Updated @grpc/protoloader from 0.7.4 to 0.7.5. Updated @grpc/grpc-js from 1.8.7 to 1.8.8. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-11-0","eolDate":"2024-03-08"},{"agent":"nodejs","date":"2023-02-21","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.10.2","features":[],"bugs":["Replace `request.aborted` with `response.close` in HTTP instrumentation.","Fix ignoring reporting errors of certain status codes and parse codes as integers."],"security":[],"supportedOperatingSystems":null,"description":"Notes Fix: Replaced request.aborted with response.close in HTTP instrumentation. Fixed issue where setting NEW_RELIC_GRPC_IGNORE_STATUS_CODES wasn't properly parsing the codes as integers, thus not ignoring reporting errors of certain status codes. Upgraded @grpc/grpc-js from 1.8.4 to 1.8.7. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-10-2","eolDate":"2024-02-21"},{"agent":"nodejs","date":"2023-02-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.10.1","features":[],"bugs":["Fix error with Lambda/ALB serverless instrumentation when no response headers were included."],"security":[],"supportedOperatingSystems":null,"description":"Notes Fixed error with Lambda/ALB serverless instrumentation when no response headers were included Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-10-1","eolDate":"2024-02-13"},{"agent":"nodejs","date":"2023-02-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.10.0","features":["Expose a method on API to obfuscate sql:`newrelic.obfuscateSql`.","Add support for Multi Value Parameter from API Gateway and ALB events for Lambdas."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Exposed a method on API  to obfuscate sql: newrelic.obfuscateSql. Add support for Multi Value Parameters  from API Gateway and ALB events for Lambdas. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-10-0","eolDate":"2024-02-09"},{"agent":"nodejs","date":"2022-09-22","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.1.0","features":["Add experimental loader to support instrumentation of CommonJS packages in ECMAScript Module(ESM) applications.","Enhance supportability metrics for ESM support.","Add new metrics to track usage of ESM loader.","Update instrumentation map for tracking metrics.","Enabled re-throwing ESM import errors of `newrelic.js`."],"bugs":["Fix an issue with mongodb instrumentation where IPv6 address([::1]) was not getting mapped to localhost when setting the host attribute on the segment."],"security":[],"supportedOperatingSystems":null,"description":"Notes Added experimental loader  to support instrumentation of CommonJS packages in ECMAScript Module(ESM) applications. It only supports versions of Node.js >= 16.12.0. It is subject to change due to its experimental stability. Enhanced supportability metrics for ESM support. Added new metrics to track usage of ESM loader(Supportability/Features/ESM/Loader and Supportability/Features/ESM/UnsupportedLoader). Updated instrumentation map to include an optional \"friendly name\" for tracking metrics. Enabled re-throwing ESM import errors of newrelic.js so that the user is informed to rename it to newrelic.cjs Fixed an issue with mongodb instrumentation where IPv6 address([::1]) was not getting mapped to localhost when setting the host attribute on the segment. Added a test ESM loader to properly mock out agent in versioned tests. Added ESM versioned tests for: express, pg, mongodb, and @grpc/grpc-js. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-1-0","eolDate":"2023-09-22"},{"agent":"nodejs","date":"2022-09-06","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.0.3","features":["Update gRPC client instrumentation to respect `grpc.record_errors` when deciding to log errors on gRPC client requests."],"bugs":["Fix transaction name finalization to properly copy the appropriate transaction name to root segment."],"security":[],"supportedOperatingSystems":null,"description":"Notes Updated gRPC client instrumenation to respect grpc.record_errors when deciding to log errors on gRPC client requests. Fixed transaction name finalization to properly copy the appropriate transaction name to root segment. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-0-3","eolDate":"2023-09-06"},{"agent":"nodejs","date":"2022-08-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.0.2","features":["Expose `compressed_content_encoding` configuration and defaulted it to 'gzip'.","Add a special case to serialize BigInts.","Add `minami` back as a dev dependency for use with `jsdoc-conf.js`."],"bugs":["Fix public jsdoc generation."],"security":[],"supportedOperatingSystems":null,"description":"Notes Added unit test suite for lib/logger.js. Added destructive integration test for Configuration instantiation. Added a special case to serialize BigInts when sending them to New Relic. BigInts can appear in log data that our customers may be trying to forward. Exposed  compressed_content_encoding configuration and defaulted it to \"gzip\". Fixed public jsdoc generation. Addedminami back as a dev dependency for use with jsdoc-conf.js. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-0-2","eolDate":"2023-08-23"},{"agent":"nodejs","date":"2022-08-18","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.0.1","features":["Handle setting the logging metric name to `UNKNOWN` when using custom log levels in pino and/or winston.","Remove 3rd party `async` library from agent code."],"bugs":["Fix properly setting logging metrics when using custom levels with winston."],"security":[],"supportedOperatingSystems":null,"description":"Notes Fixed properly setting logging metrics when using custom levels with winston. Handled setting the logging metric name to UNKNOWN when using custom log levels in pino and/or winston.\nThanks for your contribution @billouboq. Removed unnecessary unit test and fixture for OSS license generation. Updated versioned tests to remove the use of the async module. Removed 3rd party async library from agent code. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-0-1","eolDate":"2023-08-18"},{"agent":"nodejs","date":"2022-08-03","downloadLink":"https://www.npmjs.com/package/newrelic","version":"9.0.0","features":["Drop Node 12.x support.","Remove certificate bundle from agent.","The agent now excludes port when making external HTTPS requests to port 443.","Remove ability to disable async hooks based promise context tracking via the `await_support` feature flag.","Remove instrumentation for the obsolete.","Update the minimum version of `pg` to be 8.2.x.","Update the minimum supported version of hapi to be >= v20.0.0.","Add official parity support for Node 18."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added official parity support for Node 18. BREAKING : Dropped Node 12.x support.  For further information on our support policy, see Node agent compatibility . Upgraded @newrelic/superagent @newrelic/aws-sdk @newrelic/koa @newrelic/native-metrics and @newrelic/test-utilities to the latest major versions Removed Node 12 from CI workflows. Updated engines stanza to be >=14. Updated all versioned tests stanza to be >=14 Converted fs.rmdirSync to fs.rmSync in test/unit/config/config-location.test.js. Converted uses of /dev/null to os.devNull in tests. BREAKING : Removed certificate bundle from agent. The configuration value config.feature_flag.certificate_bundle will no longer work. The agent no-longer includes the New Relic certificate bundle when using the 'certificates' configuration (commonly with proxies). If you find this breaking your current environment, we recommend getting a CA bundle such as the one from Mozilla. BREAKING : The agent now excludes port when making external HTTPS requests to port 443 to be in compliance with the spec and other agents. Previous external segments would be named External/example.com:443 when using default HTTPS port.\nThe external segment will now be named External/example.com. BREAKING : Removed ability to disable async hooks based promise context tracking via the await_support feature flag. This also removes the legacy Promise instrumentation. Released the await_support feature flag. The agent now relies on async_hooks to track async promise propagation.  The net result is the if you had feature_flag.await_support set to false, the legacy instrumentation tracked every function in a promise chain as a separate segment. BREAKING : Removed instrumentation for the obsolete oracle  npm package. BREAKING : Updated the minimum version of pg to be 8.2.x.  This is the earliest support version that runs on Node 14+. BREAKING : Updated the minimum supported version of hapi to be >= v20.0.0. All versions < v20.0.0 are deprecated by hapi for security reasons, see their support policy . Dropped tests for hapi < v20.0.0. Bumped @newrelic/test-utilities to ^7.0.0. This new version of test utilities defaults the number of concurrent jobs to currently available CPUs. For local development on modern machines, this can speed up full versioned test runs by 30-40%. Introduced JOBS ENV var for agent versioned test runs to control number of attempted concurrent test folder runs. Set to 4 for CI runs in GHA. Removed the async library from distributed tracing and pricing integration tests Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-9-0-0","eolDate":"2023-08-03"},{"agent":"nodejs","date":"2022-03-22","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.9.1","features":[],"bugs":["Fix `shim.wrapReturn` to call `Reflect.construct` in construct Proxy trap.  Also include `newTarget` to work with inherited classes."],"security":[],"supportedOperatingSystems":null,"description":"Notes Fixed shim.wrapReturn to call Reflect.construct in construct Proxy trap.  Also including newTarget to work with inherited classes. Added link to New Relic Node.js Examples repository. Excluded installing dependencies in versioned-external folders when running integration tests.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-9-1","eolDate":"2024-03-22"},{"agent":"nodejs","date":"2022-03-15","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.9.0","features":["Add support for `initializeUnorderedBulkOp`, and `initializeOrderedBulkOp` in mongodb v3 instrumentation.","Update logger to delay and queue logging until configuration is parsed.","Add `NEW_RELIC_ALLOW_ALL_HEADERS` as a boolean environment variable with same behavior as existing `allow_all_headers`.","Updated the AWS IMDBS v2 endpoint to use `latest`."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added support for initializeUnorderedBulkOp, and initializeOrderedBulkOp in mongodb v3 instrumentation. Thanks to Denis Lantsman (@dlants) for the contribution. Updated logger to delay logging until configuration is parsed. The logger will now queue all log entries that occur before the agent can parse the configuration. Thanks to Cody Landry (@codylandry) for the contribution. Added NEW_RELIC_ALLOW_ALL_HEADERS as a boolean environment variable, same behavior as existing allow_all_headers. Updated the AWS IMDBS v2 endpoint to use latest to align with the internal agent specification. Bumped @newrelic/koa to ^6.1.1. Added Next.js to External Modules list in README. Updated mysql and mysql2 versioned tests to run against their own databases on the MySQL instance. Removed upper-bound testing from restify versioned tests so future major versions will be covered. Removed upper-bound testing from mysql2 versioned tests to cover existing and future major versions. Continues to skip version 1.6.2 which had a bug that broke tests which was resolved in 1.6.3. Updated @hapi/hapi Node 16 versioned test runs to run against @hapi/hapi >=20.1.2 so future major releases will be ran. Fixed sparse checkout of non-default branch for external versioned tests. Added external versioned tests for the Apollo Server plugin instrumentation. Added nock delay to test timeouts in utilization integration tests. Added newrelic-node-nextjs to external versioned tests to be run on every PR. Updated external version test running to support more test scenarios. Adds test/versioned-external to lint ignore to avoid issues for scripts in tests that auto run linting tools (next/react). Adds index.js and nr-hooks.js to files automatically checked-out for test runs.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-9-0","eolDate":"2024-03-15"},{"agent":"nodejs","date":"2022-02-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.8.0","features":["Update AWS metadata capture to utilize IMDSv2.","Update minimum Node version warning to output the current Node version from process."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Updated AWS metadata capture to utilize IMDSv2. Fixed link to discuss.newrelic.com in README Updated minimum Node version warning to output current Node version from process. Bumped @newrelic/native-metrics to ^7.1.1. Added Nextjs to a framework constant within the webframework-shim. Updated shim to pass active segment to inContext callback. Bumped @grpc/grpc-js to ^1.5.5. Bumped @grpc/proto-loader to ^0.6.9. Bumped @newrelic/superagent to ^5.1.0. Bumped @newrelic/koa to ^6.1.0. Bumped async to ^3.2.3. Resolved several npm audit warnings for dev deps. Fixed Post Release workflow by properly configuring git credentials so it can push API docs to branch Added set -e in publish docs script to exit on possible failures Removed redundant npm ci in publish API docs script Added ability to ignore certain PRs in bin/pending-prs.js report to slack Updated README to include @newrelic/pino-enricher as an external module. Fixed documentation in a sample of the Datastore Instrumentation for Node.js. Added a new mongo:5 container to npm run sevices to test mongodb driver >=4.2.0. Fixed conditions in post release workflow to function when triggered via successful release and manual invoked. Updated method for retrieving agent version from repository by using cat package.json | jq .version Fixed minor formatting and spelling issues in create-docs-pr.js. Fixed an issue with the docs PR script that assumed \\n in the NEWS.md file when extract version and release date","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-8-0","eolDate":"2024-02-23"},{"agent":"nodejs","date":"2022-01-18","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.7.1","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Bumped @newrelic/aws-sdk to ^4.1.1. Upgraded @newrelic/test-utilities to ^6.3.0. Includes helpers.getShim so sub packages properly execute. Resolved dependabot and certain npm audit warnings. Automation and CI improvements: Added a script to be used by agent developers to add a PR to docs-website after the release of agent. Changed the trigger for post release jobs. Updated the create-release-tag script to pass in workflows to check before creating tag. Fixed create-release-tag to properly filter out all async workflow run checks Updated agent release to pass in a different list of workflows vs the default Fixed release creation reusable workflow by passing in repo to bin/create-release-tag.js and bin/create-github-release.js. Added workflow_dispatch to Agent Post Release workflow for manual testing. Added a reusable workflow to create a release tag, publish to NPM and publish a GitHub release. Updated agent release workflow to reference reusable workflow. Added a new workflow to update RPM and publish API docs on a published release event type.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-7-1","eolDate":"2024-01-18"},{"agent":"nodejs","date":"2022-01-04","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.7.0","features":["Update `onResolved` instrumentation hook to only be called the first time we see a specific module filepath resolved.","Remove `tracer.segment` in place of direct usage of context manager."],"bugs":["Fix an issue where `instrumentLoadedModule` would return `true` even if the instrumentation handler indicated it did not apply instrumentation.","Fix an issue where expected status code ranges would not be parsed until ignored status codes were also defined."],"security":[],"supportedOperatingSystems":null,"description":"Notes Updated onResolved instrumentation hook to only be called the first time we see a specific module filepath resolved. Removed tracer.segment in place of direct usage of context manager. Fixed an issue where multiple calls to instrumentLoadedModule resulted in re-instrumenting the same module. Fixed issue where instrumentLoadedModule would return true even if the instrumentation handler indicated it did not apply instrumentation. Added support metrics for tracking when instrumentation was applied per module. Supportability/Features/Instrumentation/OnResolved/<module-name> Supportability/Features/Instrumentation/OnResolved/<module-name>/Version/<major version> Supportability/Features/Instrumentation/OnRequire/<module-name> Supportability/Features/Instrumentation/OnRequire/<module-name>/Version/<major version> Fixed issue where expected status code ranges would not be parsed until ignored status codes were also defined. Added an input changelog_file to pass in name of changelog.  This defaults to NEWS.md but some repos use CHANGELOG.md Abstracted bin/prepare-release.js to work against other repositories. Added reusable prepare-release workflow that can be referenced in all other newrelic Node.js repositories. Updated pending PRs workflow to check all repos the team owns. Changed the event type from pull_request to pull_request_target to allow for auto assign of PRs to the Node.js Engineering Board Fixed add to board workflow to properly pass repository secrets into reusable board workflow. Changes token used to post issues to org level project board Runs versioned tests for external modules against tests defined in the external repository instead of tests published in npm modules. Added a reusable workflow to automatically add issues to the Node.js Engineering Board when created. Added CI job to update system configurations with new agent version on release. Moved methods.js under bluebird versioned test folder.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-7-0","eolDate":"2024-01-04"},{"agent":"nodejs","date":"2021-11-17","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.6.0","features":["Introduce a context management API to be used in place of manually calling tracer.segment get/set."],"bugs":["Fix an issue where `recordConsume` was not binding consumer if it was a promise."],"security":[],"supportedOperatingSystems":null,"description":"Notes Added onResolved instrumentation hook to apply instrumentation prior to module load. This hook fires after the module filepath has been resolved just prior to the module being loaded by the CommonJS module loader. Fixed issue where recordConsume was not binding consumer if it was a promise Pinned mongo versioned tests up to 4.2.0 until we can address #982 Introduced a context management API to be used in place of manually calling tracer.segment get/set.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-6-0","eolDate":"2023-11-17"},{"agent":"nodejs","date":"2021-11-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.5.2","features":[],"bugs":["Fix an issue where unhandled promise rejections were not getting logged as errors in a lambda execution."],"security":[],"supportedOperatingSystems":null,"description":"Notes Fixed issue where unhandled promise rejections were not getting logged as errors in a lambda execution","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-5-2","eolDate":"2023-11-09"},{"agent":"nodejs","date":"2021-11-03","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.5.1","features":[],"bugs":["Fix a bug where failure to retrieve CPU/Memory details for certain Linux distros could result in a crash."],"security":["Fix a high severity npm audit failure."],"supportedOperatingSystems":null,"description":"Notes Fixed bug where failure to retrieve CPU/Memory details for certain Linux distros could result in a crash. parseProcCPUInfo and parseProcMeminfo now check for null input prior to processing. Updated README to favor using -r to load the agent vs require('newrelic'). Updated @newrelic/test-utilities to 6.1.1 and applied a global sampling value of 10 for versioned tests. Migrated utilization unit tests from mocha to tap. Migrated logger unit tests from mocha to tap. Cleaned up or added future removal comments for several deprecation warnings. Added a script and corresponding CI job that will check for PRs that have been merged and not release and notify the team in a private slack channel. Updated the versioned test runner to always run against minor versions. Fixed a high severity npm audit failure.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-5-1","eolDate":"2023-11-03"},{"agent":"nodejs","date":"2021-10-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.5.0","features":["Add full support for Fastify v2 and v3. Fastify instrumentation is now GA.","Add experimental instrumentation for the undici http client behind a feature flag."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes 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  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 . Lastly, you must be using 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.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-5-0","eolDate":"2023-10-12"},{"agent":"nodejs","date":"2021-09-28","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.4.0","features":["Deprecate Cross Application Tracing (CAT).","Add support for Cassandra driver v4.0.0 and above."],"bugs":["Fix an issue with `clearTimeout` that could result in dropping parent segments or spans.","Fix an issue where DT headers would not be processed by `transaction-shim.handleCATHeaders()` when CAT was explicitly disabled."],"security":[],"supportedOperatingSystems":null,"description":"Notes 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). Fixed issue with clearTimeout that could result in dropping parent segments or spans.\nThis 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.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-4-0","eolDate":"2023-09-28"},{"agent":"nodejs","date":"2021-09-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.3.0","features":["Enable Distributed Tracing (DT) by default.","Add support for properly setting the `host` and `port` for mongodb requests that are to cluster.","Add several environment variables for the corresponding configuration items."],"bugs":["Fix an issue where `.fastify` and `.default` properties would be missing from the `fastify` export when instrumented."],"security":[],"supportedOperatingSystems":null,"description":"Notes Enabled Distributed Tracing (DT) by default. Added ability to configure the maximum number of spans that can be collected per minute via span_events.max_samples_stored and environment variable NEW_RELIC_SPAN_EVENTS_MAX_SAMPLES_STORED. Added supportability metric SpanEvent/Limit. Added support for properly setting the host and port for clustered MongoDB requests. Fixes issue where .fastify and .default properties would be missing from the fastify export when instrumented. Instrumentation now sets .fastify and .default properties to the wrapped fastify export function for fastify v3. Added the following environment variables for the corresponding configuration items: config item:  transaction_events.max_samples_stored\nenv var:  NEW_RELIC_TRANSACTION_EVENTS_MAX_SAMPLES_STORED config item:  custom_insights_events.max_samples_stored\nenv var:  NEW_RELIC_CUSTOM_INSIGHTS_EVENTS_MAX_SAMPLES_STORED config item:  error_collector.max_event_samples_stored\nenv var:  NEW_RELIC_ERROR_COLLECTOR_MAX_EVENT_SAMPLES_STORED Converted several unit tests to use the tap API. Changed assertions for two HTTP error message tests to work with all versions of Node.js.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-3-0","eolDate":"2023-09-09"},{"agent":"nodejs","date":"2021-08-25","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.2.0","features":["Add a new feature flag `unresolved_promise_cleanup`.","Support using `connect` to route middleware calls."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added a new feature flag unresolved_promise_cleanup that defaults to true only when new_promise_tracking feature flag is set to true.  If disabled, this will help with performance of agent when an application has a lot of promises.  To disable, in your config set feature_flag.unresolved_promise_cleanup to false or pass in the environment var of NEW_RELIC_FEATURE_FLAG_UNRESOLVED_PROMISE_CLEANUP=false when starting application with agent. WARNING : If you set unresolved_promise_cleanup to false, failure to resolve all promises in your application will result in memory leaks even if those promises are garbage collected Supported using connect to route middleware calls. Removed stubbed out tests in memcached unit tests. Refactored dropTestCollections in mongo versioned tests to await for all dropCollection operations to be finished before closing connection and returning. Ported remaining mocha tests in test/unit/instrumentation to exclusively use tap. Added @newrelic/eslint-config to rely on a centralized eslint ruleset. Removed integration tests for oracle. Converted config unit tests to fully use tap API and extracted related tests into more-specific test files. Added a pre-commit hook to check if package.json changes and run oss third-party manifest and oss third-party notices.  This will ensure the third_party_manifest.json and THIRD_PARTY_NOTICES.md up to date Replaced JSV with ajv for JSON schema validation in tests. Removed through in lieu of core Node.js implementation of Transform stream in tests.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-2-0","eolDate":"2023-08-25"},{"agent":"nodejs","date":"2022-08-02","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.17.1","features":["Bound the external client segment to the onReceiveStatus listener to propagate transaction context to the grpc client callbacks."],"bugs":["Fix issue where instrumented code invoked within a @grpc/grpc-js client callback would not get tracked by the agent.","Fix issue with truncate in `lib/util/application-logging.js`."],"security":[],"supportedOperatingSystems":null,"description":"Notes Fixed issue where instrumented code invoked within a @grpc/grpc-js client callback would not get tracked by the agent. Bound the external client segment to the onReceiveStatus listener to propagate transaction context to the grpc client callbacks. Fixed issue with truncate in lib/util/application-logging.js. It now checks that the argument is a string before checking its length. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-17-1","eolDate":"2023-08-02"},{"agent":"nodejs","date":"2022-07-27","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.17.0","features":["Add instrumentation for `grpc-js` server unary, client-streaming, server-streaming and bidirectional streaming handlers."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added gRPC server instrumentation . Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-17-0","eolDate":"2024-07-27"},{"agent":"nodejs","date":"2022-07-21","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.16.0","features":["Automatic application log forwarding is now enabled by default.","Add a support statement to our release notes."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Automatic application log forwarding is now enabled by default. This version of the agent will automatically send enriched application logs to New Relic. To learn more about about this feature, see the APM logs in context documentation . For additional configuration options, see the Node.js logs in context documentation . To learn about how to toggle log ingestion on or off by account, see our documentation to disable automatic logging  via the UI or API. Added a support statement to our release notes Added node 18 to CI workflows. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-16-0","eolDate":"2024-07-21"},{"agent":"nodejs","date":"2022-07-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.15.0","features":["Add instrumentation for grpc-js unary, streaming, and bidirectional client calls.","Add ability to disable server-side configuration via local configuration setting."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added instrumentation for grpc-js unary, streaming, and bidirectional client calls. Added ability to disable server-side configuration via local configuration setting: ignore_server_configuration or environmental variable of NEW_RELIC_IGNORE_SERVER_SIDE_CONFIG. Added tests for client, server and bidirectional streaming of gRPC client. Updated got  from 8.3.2 to 11.8.5. Updated moment  from 2.29.2 to 2.29.4 Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-15-0","eolDate":"2024-07-07"},{"agent":"nodejs","date":"2022-06-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.14.1","features":["Add defensive code in redis v4 instrumentation to check for `opts.socket` first before evaluating `opts.socket.path`."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added defensive code in redis v4 instrumentation to check for opts.socket first before evaluating opts.socket.path.\nThanks @RAshidAZ for your contribution! Updated @grpc/proto-loader to v0.6.13 to pickup security fixes in protobufjs.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-14-1","eolDate":"2024-06-09"},{"agent":"nodejs","date":"2022-06-06","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.14.0","features":[],"bugs":["Fix issue with `api.getBrowserTimingHeader` optional script unwrapping issue with util.format.","Fix winston instrumentation to not exit early when `winston.createLogger` is created without options.","Update pino instrumentation to not override user log configurations."],"security":[],"supportedOperatingSystems":null,"description":"Notes Fixed issue with api.getBrowserTimingHeader optional script unwrapping issue with util.format.\nThanks for your contribution @github-dd-nicolas Fixed winston instrumentation to not exit early when winston.createLogger is created without options. Updated pino instrumentation to not override user log configurations.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-14-0","eolDate":"2024-06-06"},{"agent":"nodejs","date":"2022-05-31","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.13.2","features":[],"bugs":[],"security":["Upgrade `protobufjs` to resolve  CVE-2022-25878"],"supportedOperatingSystems":null,"description":"Notes Upgraded protobufjs to resolve CVE-2022-25878 Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-13-2","eolDate":"2024-05-31"},{"agent":"nodejs","date":"2022-05-27","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.13.1","features":[],"bugs":["Fix passing undefined as formatter options to `winston.format.combine`"],"security":[],"supportedOperatingSystems":null,"description":"Notes Fixed passing undefined as a formatter options to winston.format.combine","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-13-1","eolDate":"2024-05-27"},{"agent":"nodejs","date":"2022-05-26","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.13.0","features":[],"bugs":["Move log forwarding logic so customer transports are not polluted with NR data.","Prevent transmitting logs when application level logging has been disabled."],"security":[],"supportedOperatingSystems":null,"description":"Notes Moved log forwarding logic to a transport so customer transports are not polluted with NR linking metadata and timestamp and error manipulations. Prevented transmitting logs when application level logging has been disabled.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-13-0","eolDate":"2024-05-26"},{"agent":"nodejs","date":"2022-05-24","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.12.0","features":["Add pino instrumentation to support log forwarding, decoration, and metrics.","Add an optional way to avoid wrapping browser agent script with script tag when using `api.getBrowserTimingHeader`."],"bugs":[],"security":["Upgrade `@grpc/proto-loader` to fix CVE-2022-25878 with `protobufjs`."],"supportedOperatingSystems":null,"description":"Notes Added instrumentation to pino to support application logging use cases: forwarding, local decorating, and metrics. Added supportability metrics about the data usage bytes of harvested data to the collector endpoints. Added an optional way to avoid wrapping browser agent script with the {'<script>'} tag when using api.getBrowserTimingHeader. This will ease usage with component-based libraries like React. Thanks to @github-dd-nicolas  for the contribution. Upgraded @grpc/proto-loader to fix a CVE  with protobufjs. Upgraded @newrelic/test-utilities to resolve a dev-only audit warning.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-12-0","eolDate":"2024-05-24"},{"agent":"nodejs","date":"2022-05-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.11.2","features":[],"bugs":["Fix winston instrumentation to no longer coerce every log line to be json."],"security":[],"supportedOperatingSystems":null,"description":"Notes Fixed winston instrumentation to no longer coerce every log line to be json.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-11-2","eolDate":"2024-05-23"},{"agent":"nodejs","date":"2022-05-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.11.1","features":[],"bugs":["Fix winston instrumentation that caused agent to crash when creating a winston logger from an existing instantiated logger."],"security":[],"supportedOperatingSystems":null,"description":"Notes Fixed an issue with winston instrumentation that caused agent to crash when creating a winston logger from an existing instantiated logger.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-11-1","eolDate":"2024-05-13"},{"agent":"nodejs","date":"2022-05-11","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.11.0","features":["Add application logging for Winston in the Node.js agent.","Support automatic instrumentation of Redis v4."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added application logging  for Winston in the Node.js agent Ability to forward logs, send log metrics, and perform local log decoration Added application log aggregator to collect logs with adaptive sampling and appropriate max samples stored. Added application_logging configuration and env vars with appropriate defaults. Added application_logging.enabled configuration value, defaulting to true. Set application_logging.forwarding.enabled to false when High-security mode (HSM) is set. Enabled log forwarding by default in the example config. Added sent, seen, and dropped metrics that collected on every harvest cycle around log lines. Added supportability metrics for some popular logging frameworks. Added supportability metrics to record if the logging features are enabled. Added a storage mechanism to transactions to keep logs until transaction ends. Removed distributed tracing setting from example config. Fixed a typo in lib/instrumentation/core/child_process.js. Thanks to Eito Katagiri (@eitoball) for the contribution. Support automatic instrumentation of Redis v4. Bumped moment  from v2.29.1 to v2.29.2. Bumped tap to v16.x. Updated ansi-regex to resolve a dev dependency audit warning.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-11-0","eolDate":"2024-05-11"},{"agent":"nodejs","date":"2022-04-18","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.10.0","features":["Add instrumentation for `mysql2/promise`.","Remove unused native CPU metric sampler."],"bugs":["Fix promise interceptor from re-throwing errors."],"security":[],"supportedOperatingSystems":null,"description":"Notes Added instrumentation for mysql2/promise. This previously only existed in our standalone @newrelic/mysql, but now gives feature partiy between the two. Removed unused native CPU metric sampler. This logic was no longer getting touched when running Node.js versions higher than 6.1.0. Fixed promise interceptor from re-throwing errors. Added transaction naming documentation ported from a discussion forum post . Added promises.tap.js to mysql2 versioned tests. Updated @newrelic/test-utilities to latest. Removed unused test file in restify versioned tests. Added --strict flag to versioned test runner to properly fail CI runs when test files are not included.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-10-0","eolDate":"2024-04-18"},{"agent":"nodejs","date":"2021-08-05","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.1.0","features":["Added necessary instrumentation to support v4 of `mongodb`."],"bugs":["Fix issue where Promise based `pg.Client.query` timings were always in sub-millisecond range.","Fix bug where `API.shutdown` would not harvest or keep process active effectively after an agent restart."],"security":[],"supportedOperatingSystems":null,"description":"Notes Added necessary instrumentation to support v4 of mongodb. Explicitly enabled APM for mongodb instrumentation(client.monitorCommands = true) Fixed issue where Promise based pg.Client.query timings were always in sub-millisecond range. Fixed bug where API.shutdown would not harvest or keep process active effectively after an agent restart. The agent will now correctly update its state to 'started' after a reconnect has completed. Added an eslint rule to verify every file includes the copyright statement. Fixed the homepage field in package.json to use https in the link to the github repo. Thank you @pzrq for the contribution.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-1-0","eolDate":"2023-08-05"},{"agent":"nodejs","date":"2021-07-26","downloadLink":"https://www.npmjs.com/package/newrelic","version":"8.0.0","features":["**BREAKING** Drop Node v10.x support.","**BREAKING**: The agent no-longer includes the New Relic certificate bundle automatically when using the 'certificates' configuration (commonly with proxies).","**BREAKING**: Remove `serverless_mode` as a feature flag."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added official parity support for Node 16. BREAKING : Dropped Node v10.x support. For further information on our support policy,\nsee: https://docs.newrelic.com/docs/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent . Upgraded @newrelic/superagent @newrelic/aws-sdk @newrelic/koa @newrelic/native-metrics and @newrelic/test-utilities to the latest major versions. Refactored creation of span event aggregator to prevent crash of gRPC when running on invalid Node.js version. Added check for minimum node version >= 12. Set package.json engines node field >= 12 and npm field to >=6. Removed Node v10 from ci workflow and smoke-test version matrix. Removed comments around replacing temporarilyOverrideTapUncaughtBehavior test helper function. Removed non-applicable semver checks for versions the agents no longer supports. BREAKING : The agent no-longer includes the New Relic certificate bundle automatically when using the 'certificates' configuration (commonly with proxies). If you find this breaking your current environment, you may leverage a feature-flag to temporarily restore this functionality. Example configuration: feature_flag: { certificate_bundle: true }. In this case, we recommend getting a certificate bundle for your environment such as the one from Mozilla. The New Relic bundle and feature flag will be fully removed in next major release. Defaulted config.feature_flags.certificate_bundle to false. BREAKING : Removed serverless_mode as a feature flag. The standard serverless_mode configuration still exists. Added hapi 19 and 20 to versioned tests for Node.js >=12 and <16 Added hapi ^20.1.2 to versioned tests for for Node.js >=16 Upgraded tap to v15. Upgraded https-proxy-agent to v5.0.0. Updated linting to always use latest LTS Node version. Updated CI and Smoke Test scripts to use setup-node@v2. Added no-const-assign to eslint ruleset. Pinned mongodb versioned tests to <4.0.0.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-0-0","eolDate":"2023-07-26"},{"agent":"nodejs","date":"2021-07-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.5.2","features":[],"bugs":["Fix bug where promise-based cursor methods would not properly measure the duration of execution."],"security":[],"supportedOperatingSystems":null,"description":"Bug Fixes Fixed bug where promise-based cursor methods would not properly measure the duration of execution.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-5-2","eolDate":"2023-07-07"},{"agent":"nodejs","date":"2021-06-21","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.5.1","features":[],"bugs":["Fix loading config from the main module's directory.."],"security":[],"supportedOperatingSystems":null,"description":"Improvements Moved all integration tests that required secrets to the smoke folder. Fixed LASP/CSP tests so they don't skip on runs where secrets are available. Modified self-signed SSL cert to use 'localhost' instead of 'ssl.lvh.me' for SSL testing. Removed unnecessary trace observer configuration validation for host and port. Bug Fixes Fixed loading config from the main module's directory. Thank you @alexpls for the contribution. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-5-1","eolDate":"2023-06-21"},{"agent":"nodejs","date":"2021-06-01","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.5.0","features":["Add default support for config files with a 'cjs' extension (`newrelic.cjs`) in addition to `newrelic.js`.","Add the ability to specify a custom config file name with the `NEW_RELIC_CONFIG_FILENAME` environment variable."],"bugs":["Fix an issue when using the 'new_promise_tracking' feature flag where segment mapping may not get cleaned up."],"security":[],"supportedOperatingSystems":null,"description":"Features Added default support for config files with a 'cjs' extension (newrelic.cjs) in addition to newrelic.js. Thank you to @Maddemacher for the contribution! Added ability to specify a custom config file name with the NEW_RELIC_CONFIG_FILENAME environment variable. Thank you to @Maddemacher for the contribution! Improvements Bumped @newrelic/test-utilities to ^5.1.0. Replaced deprecated util.isArray with Array.isArray. Removed unused listenerCount method on Shim. Properly bootstraped husky as a prepare script. Removed commented-out console log from fastify instrumentation. Bug Fixes Fixed issue when using the 'new_promise_tracking' feature flag where segment mapping may not get cleaned up for promises which never resolve but have all references removed (and thus get cleaned up by GC). Adds segment cleanup on 'destroy' when using 'new_promise_tracking' feature flag in addition to the existing 'promiseResolve' hook. Unfortunately, preventing leaks for this edge-case does come with additional overhead due to adding another hook. Memory gains from feature flag usage should still be worth the trade-off and reduced garbage collection may offset perf/CPU impacts or event still result in net gain, depending on the application. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-5-0","eolDate":"2023-06-01"},{"agent":"nodejs","date":"2021-05-11","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.4.0","features":["Handle a proxy misconfiguration of the collector and log an actionable warning message.","Log all New Relic metadata env vars at startup.","Add `flaky_code` and `success_delay_ms` handling of flaky grpc connections to infinite tracing."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Features Added flaky_code and success_delay_ms handling of flaky grpc connections to infinite tracing. Logged all New Relic metadata env vars at startup. Improvements Updated third party notices and manifest for husky and lint-staged. Updated redis versioned tests to use unique DB indexes per file to avoid collisions and flushing of in-progress tests. Pinned hapi 17 versioned tests to only minor/patch versions within 17.x. Bumped timeout for redis versioned tests. Wired up husky + lint staged to execute linting on all changed files in pre-commit hook. Added resources to README to highlight external modules that customers should be aware of and possibly use for their applications. Handled a proxy misconfiguration of collector and log an actionable warning message. Fixed images for improved reader experience. Thank you to @henryjw for the contribution. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-4-0","eolDate":"2023-05-11"},{"agent":"nodejs","date":"2021-04-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.3.1","features":["**Deprecation Warning:** The certificate bundle automatically included by New Relic when using the 'certificates' configuration (commonly with proxies) will be disabled by default in the next major version."],"bugs":["Fix issue with 'new_promise_tracking' feature flag functionality where segments for ended transactions would get propagated in certain cases."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Fixed issue with new_promise_tracking feature flag functionality where segments for ended transactions would get propagated in certain cases by promises that had no continuations scheduled (via await or manually). If you are experiencing high overhead levels with your promise usage and the agent attached, we recommend testing your application with  new_promise_tracking set to true to see if overhead is reduced. You'll also want to verify your data is still being captured correctly in case it falls into a known or unknown limitation of this approach. NOTE: With this new functionality turned on, chaining of promise continuations onto an already resolved promise across an async hop (scheduled timer) will result in state-loss. This is a less-common use-case but worth considering with your applications. Deprecation Warning:  The certificate bundle automatically included by New Relic when using the certificates configuration (commonly with proxies) will be disabled by default in the next major version. This is currently targeted for sometime in May. The bundle will be fully removed in later major versions. We recommend testing with the 'certificate_bundle' feature flag set to false to determine if you will need to modify your environment or setup your own appropriate bundle. Example configuration: feature_flag: { certificate_bundle: false }. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-3-1","eolDate":"2023-04-14"},{"agent":"nodejs","date":"2021-04-06","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.3.0","features":["Add new feature-flag 'new_promise_tracking' which enables cleaning up of segment references on native promise resolve instead of destroy."],"bugs":["Fix a memory leak introduced when Infinite Tracing is enabled."],"security":[],"supportedOperatingSystems":null,"description":"New Features Added new feature-flag 'new_promise_tracking' which enables cleaning up of segment references on native promise resolve instead of destroy. Includes usage of async-await. This can be enabled via feature_flag: { new_promise_tracking: true } in the config file or NEW_RELIC_FEATURE_FLAG_NEW_PROMISE_TRACKING=1 in your ENV vars. Applications with heavy promise usage or high-throughput applications with some promise usage should see moderate to high reduction in memory usage and may see a slight reduction in CPU usage. A bump in throughput may also be noticed in some cases. Results will vary by application. If you are experiencing high overhead levels with your promise usage and the agent attached, we recommend testing your application with  'new_promise_tracking' set to true to see if overhead is reduced. You'll also want to verify your data is still being captured correctly in case it falls into a known or unknown limitation of this approach.  NOTE: chaining of promise continuations onto an already resolved promise across an async hop (scheduled timer) will result in state-loss with this new functionality turned on. This is a less-common use-case but worth considering with your applications. Fixes Fixed memory leak introduced when Infinite Tracing is enabled. When Infinite Tracing endpoints reconnected they would instantiate a new gRPC client prior to calling client.recordSpan(). It appears several objects created by grpc-js (ChannelImplementation and child objects, promises, etc.) are held in memory indefinitely due to scheduled timers even when the client is no-longer referenced and the associated stream closed. We now avoid this situation by only creating the client once and then reusing it to establish new stream connections. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-3-0","eolDate":"2023-04-06"},{"agent":"nodejs","date":"2021-03-29","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Bumped @grpc/grpc-js to ^1.2.11. Bumped @grpc/proto-loader to ^0.5.6. Fixes Fixed issue where capturing axios request errors could result in a memory leak. The agent now clears error references on transaction end, which are not used for later processing. Errors returned from 'axios' requests contain a reference to the request object which deeper down has a handle to a promise in handleRequestError. The TraceSegment associated with that promise has a handle to the transaction, which through the error capture ultimately kept the promise in memory and prevented it from being destroyed to free-up the TraceSegment from the segment map. This change also has the benefit of  freeing up some memory early for transactions held onto for transaction traces. Agent no longer propagates segments for promises via async-hooks when the transaction associated with the parentSegment has ended. This change reduces the amount of context tracking work needed for certain rare edge-case scenarios involving promises. Added active transaction check to wrappedResEnd to prevent unecessary work for ended transactions in the case of multiple Response.prototype.end() invocations. Dev-only sub-dependency bump of 'y18n' to clear npm audit warnings. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-2-1","eolDate":"2023-03-29"},{"agent":"nodejs","date":"2021-03-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements The NEW_RELIC_NO_CONFIG_FILE environment variable is no longer needed to run the agent without a configuration file. If a configuration file is used with agent configuration environment variables, the environment variables will override the corresponding configuration file settings. Added feature flag to allow disabling of certificate bundle usage. Deprecation Warning:  The certificate bundle included by New Relic will be disabled by default and then fully removed in later major versions. We recommend testing with the certificate_bundle feature flag set to false to determine if you will need to modify your environment or setup your own appropriate bundle. Example configuration: feature_flag: { certificate_bundle: false }. Set distributed tracing to enabled in the newrelic.js template configuration file supplied with the agent. Added module root to shim.require() logging to aid debugging. Migrated from .npmignore to 'files' list in package.json to control which files are packaged. Thank you to @JamesPeiris for the initial nudge via PR to move in this direction. Converted remaining collector unit tests to use tap API. Added linting to scripts in /bin folder. Linting rules added are slightly more permissive than production rules and allow full ecma 8. Added new developer documentation to /docs folder. This information is ported over from private GHE wiki used prior to going open source. S/O @astorm for original versions of the function wrapping and module instrumentation docs. Fixes Fixed bug where applications with multiple names on a dynamically named host (UUID like) would have instances consolidated, losing per-host breakdowns. Removed 'host' from agent 'identifier' override to prevent server safety mechanism from kicking in. Host will still be used to identify unique agent instances, so was unnecessary to include as part of the identifier. This also resulted in additional processing overhead on the backend. The identifier override is still kept in place with multiple application names to continue to allow uniquely identifying instances on the same host with multiple application names where the first name may be identical. For example app_name['myName', 'unique1'] and app_name['myName', 'unique2']. These names would consolidate down into a single instance on the same host without the identifier override. Fixed bug where truncated http (external) or datastore segments would generate generic spans instead of appropriate http or datastore spans. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-2-0","eolDate":"2023-03-23"},{"agent":"nodejs","date":"2021-03-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.1.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Removed requirement to configure application name when running in AWS Lambda (serverless mode). Currently New Relic doesn't leverage the application name for Lambda invocations. The agent now defaults the application name in serverless mode to remove the requirement of end-user configuration while handling cases if it were to be leveraged in the future. Improved clarity of logging between 'no log file' or disabled agent startup issues. Logs no-config file error to initialized logger (stdout) in addition to existing console.error() logging. Adds specific message to no config file separate from being disabled. Stopped binding/propagating segments via setImmediate for ended transactions. Bumped @grpc/grpc-js to ^1.2.7. Added support metric to be able to track usage of cert bundle via usage of custom certificates. Fixes Fixed bug where agent would attempt to call the 'preconnect' endpoint on the redirect host returned by the previous 'preconnect' call when reconnecting to the New Relic servers. The 'preconnect' calls now always use the original agent configuration value. Subsequent endpoints (connect, harvest endpoints, etc.) will continue to leverage the new redirect host value returned by 'preconnect.' The original config values are no longer overridden. Fixed issue where a call to transaction.acceptDistributedTraceHeaders would throw an error when the headers parameter is a string. Removed index-bad-config test which tested a no-longer possible use-case. Removed license-key test logic from serverless-harvest test. Serverless mode does not require a license key as data transfer is handled by the integration. Removed aws-sdk versioned test filtering. Removed unused Travis CI scripts. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-1-3","eolDate":"2023-03-09"},{"agent":"nodejs","date":"2021-02-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.1.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Bumped @newrelic/aws-sdk to ^3.1.0. Fixes Fixed bug where the agent failed to reconnect to Infinite Tracing gRPC streams on Status OK at higher log levels. Node streams require all data be consumed for the end/status events to fire. We were only reading data at lower log levels where we'd use/log the data. This resulted in a failure to reconnect and 'ERR_STREAM_WRITE_AFTER_END' errors. The agent now always listens to the 'data' event, even if not logging, and will also reconnect (with 15 second delay) on any 'ERR_STREAM_WRITE_AFTER_END' error. Removed initial harvest send() call on streaming span event aggregator to prevent warning in logs. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-1-2","eolDate":"2023-02-23"},{"agent":"nodejs","date":"2021-02-01","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.1.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added workflow for publishing to npm when a v* tag is pushed to the repo. Fixes resolveMx test by using example.com for a valid exchange. Fixes Upgrade @grpc/grpc-js to v1.2.5 to fix non-propagation of internal http2 errors Now allows minor and patch auto-updates.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-1-1","eolDate":"2023-02-01"},{"agent":"nodejs","date":"2021-01-05","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added Fastify v3 support. Upgraded grpc version. Fixes Fixed SQL traces being generated with invalid ID. Fixed log message for minimum supported Node.js version. Fixed empty log message for Infinite Tracing connections. Fixed bug that prevented users from changing Infinite Tracing queue size.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-1-0","eolDate":"2023-01-05"},{"agent":"nodejs","date":"2020-12-01","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.0.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixes a bug where the http.statusCode attribute was not being captured for an async invoked lambda. Fixed typos in code comments, documentation, and debugging logger messages. Thank you @TysonAndre for the contribution.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-0-2","eolDate":"2022-12-01"},{"agent":"nodejs","date":"2020-11-17","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Fixed a bug where spans queued up during backpressure situations would be improperly formatted and ultimately dropped when sent to an Infinite Tracing trace observer. Updated @grpc/grpc-js to version v1.2.0. Updated tap to clear up npm audit issues around lodash sub-dependency.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-0-1","eolDate":"2022-11-17"},{"agent":"nodejs","date":"2020-11-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"7.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added official parity support for Node 14 Dropped Node v8.x support. For further information on our support policy, see: https://docs.newrelic.com/docs/agents/nodejs-agent/getting-started/compa... . Removed Node v8.x from CI Adds check that minimum Node version is >=10 and warns if >=15 Sets Node engine to >=10 BREAKING  Dropped support for Node v8.x HTTP get() function signature Strictly uses global.URL class in http core instrumentation Removes Nodejs 8.x - 9.x checks Update New Relic Dependencies to versions with updated Node version support @newrelic/aws-sdk v3.0.0 @newrelic/koa v5.0.0 @newrelic/native-metrics v6.0.0 @newrelic/superagent v4.0.0 @newrelic/test-utilities v5.0.0 BREAKING  Removed deprecated setIgnoreTransaction API method BREAKING  Removed deprecated httpResponseCode, response.status and httpResponseMessage http response attributes BREAKING  Removed the api.custom_parameters_enabled configuration item and associated environment variable NEW_RELIC_API_CUSTOM_PARAMETERS. Please use api.custom_attributes_enabled instead BREAKING  Removed deprecated Distributed Tracing API methods, createDistributedTracePayload() and acceptDistributedTracePayload() Finalized removal of ignored_params and capture_params Added additional logging to W3C Trace Context header creation","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-7-0-0","eolDate":"2022-11-09"},{"agent":"nodejs","date":"2020-06-08","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.9.0","features":["Add AWS API Gateway V2 Support to lambda instrumentation.","Add 'transaction.name' intrinsic to active span at time transaction name is finalized.","Add 'error.expected' attribute to span active at the time expected error was noticed.","Drop errors earlier during collection when error collection is disabled.","Remov allocation of logging-only objects used by transaction naming when those log levels are disabled."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Features Added AWS API Gateway V2 support to Lambda instrumentation. Added 'transaction.name' intrinsic to active span at time transaction name is finalized. This enables finding transaction name for traces that may not have a matching transaction event. Added 'error.expected' attribute to span active at time expected error was noticed. Improvements Dropped errors earlier during collection when error collection is disabled. Error attributes will no longer show up on spans when error collection has been disabled. Other unnecessary work will also be avoided. Removed allocation of logging-only objects used by transaction naming when those log levels are disabled. Upgraded escodegen from 1.12.0 to 1.14.1. Upgraded readable-stream from 3.4.0 to 3.6.0. Upgraded @grpc/proto-loader from 0.5.3 to 0.5.4. Converted facts unit test to use tap API. Converted transaction 'finalizeName...' unit tests to use tap API. Added several items to .npmignore to prevent accidental publishing. Fixed Redis client w/o callback versioned test flicker. Doesn't end transaction until error encountered. Increases wait time for first operation which has to complete for the second operation to be successful.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-690","eolDate":"2023-06-08"},{"agent":"nodejs","date":"2020-05-21","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.8.0","features":["Add whitespace trimming of license key configuration values."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Features Bumped @newrelic/native-metrics to ^5.1.0. Upgraded nan to ^2.14.1 to resolve 'GetContents' deprecation warning with Node 14. This version of the native metrics module is tested against Node 14 and includes a pre-built binary download backup for Node 14. Improvements Added whitespace trimming of license key configuration values. Previously, when a license key was entered with leading or trailing whitespace, it would be used as-is and result in a validation failure. This most commonly occurred with environment variable based configuration. Moved to GitHub actions for CI. Updated PR template and added initial issue templates. Converted most of the collector API unit tests to use the tap API. Split larger test groupings into their own test files.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-680","eolDate":"2023-05-21"},{"agent":"nodejs","date":"2020-05-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.7.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Added synthetics headers to transaction event intrinsics for Distributed Tracing Fixed stale comment documentation with regards to segment recording","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-671","eolDate":"2023-05-14"},{"agent":"nodejs","date":"2020-05-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added a configurable-length span queue to Infinite Tracing: infinite_tracing.span_events.queue_size. The queue length can be modified to balance the needs of keeping full traces against trade-off of memory usage and CPU overhead in a high-throughput application. Improvements Updated remaining /api unit tests to use tap API. Updated @grpc/grpc-js to v1.0.3. Fixes Fixed issue where API.instrumentLoadedModule could throw an exception when it failed. Error details will now be caught and logged. Resolved non-proxy minimist security warnings by bumping dependencies. These updates only impact development dependencies. Thank you to @devfreddy for the contribution. Updated minimist sub-deps to resolve most related security warnings. Updated tap to resolve remaining tap security warnings. Updated @newrelic/proxy.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-670","eolDate":"2023-05-07"},{"agent":"nodejs","date":"2020-04-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added support for Infinite Tracing on New Relic Edge . Infinite Tracing observes 100% of your distributed traces and provides visualizations for the most actionable data so you have the examples of errors and long-running traces so you can better diagnose and troubleshoot your systems. You configure your agent to send traces to a trace observer in New Relic Edge. You view your distributed traces through the New Relic’s UI. There is no need to install a collector on your network. Infinite Tracing is currently available on a sign-up basis. If you would like to participate, please contact your sales representative. Improvements Added function_version to lambda metadata payload. This is pulled from an invocation's context.functionVersion value.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-660","eolDate":"2023-04-20"},{"agent":"nodejs","date":"2020-03-19","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added error attributes to spans. The public api method noticeError() now attaches exception details to the currently executing span. Spans with error details are now highlighted red in the Distributed Tracing UI. Also, the attributes error.class and error.message are added to the span. If multiple errors are recorded for a single span, only the final error's attributes will be added to the span. Added ID of the span in which an error occurred to the corresponding transaction error event. Added new public API methods addCustomSpanAttribute and addCustomSpanAttributes to add attributes to the currently executing span. Added new attributes to http outbound spans: http.statusCode and http.statusText. Updated W3C Trace Context \"Known Issues and Workaround\" notes with latest accurate consideration. Converted unit tests to run via tap. Removes mocha dependency. Fixes Fixed route naming when hapi's pre route handlers share functions. Fixed child_process instrumentation so that handlers can be effectively removed when attached via .once() or manually removed via removeListener().","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-650","eolDate":"2023-03-19"},{"agent":"nodejs","date":"2020-02-27","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.4.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Support new http[s] get/request function signature in Node v10+ Added the following Span attributes: http.statusCode http.statusText The above attributes will be replacing the following deprecated  attributes: httpResponseCode response.status response.statusMessage The deprecated attributes will be removed with the next major release of the agent. Updates version check to be in alignment with our stated support policy  and the version constraints in package.json Redacts individual certificate configuration values before sending to server settings. When configured, these values will now appear like: {certificates.0: ****}. Known issues and workarounds If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream New Relic Node agents to this agent release.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-642","eolDate":"2023-02-27"},{"agent":"nodejs","date":"2020-02-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Removed calls to OutgoingMessage.prototype._headers in favor of using public getHeaders API (thanks to @adityasabnis for bringing this to our attention). Removed engine upper-bound to enable easier experimentation of newer Node versions with the agent for customers. Please see https://docs.newrelic.com/docs/agents/nodejs-agent/getting-started/compa...  for officially supported versions. Incompatibilities are expected for odd-numbered releases, which are not supported, and even-numbered releases before \"official\" support has been released. Reduced \"... Aggregator data send.\" log messages to debug level to reduce noise of default logs. Prevented passing CI with .only() in mocha tests. Removed CI restriction for Node 12.15. Node shipped a fix for the 12.16 breakage in 12.16.1. Reduced logging level of raw x-queue-start or x-request-start header values to avoid logging very large values at default logging levels. Fixes Bumped @newrelic/aws-sdk version to v1.1.2 from v1.1.1. https://github.com/newrelic/node-newrelic-aws-sdk/blob/master/CHANGELOG.md Notable improvements include: Fixed issue where instrumentation would crash pulling host and port values when AmazonDaxClient was used as the service for DocumentClient. Fixed issue where disabled agent would return an empty string instead of an empty object from API getLinkingMetadata(). This issue would cause the @newrelic/winston-enricher module to crash when attempting to inject log metatdata. Known issues and workarounds If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream New Relic Node agents to this agent release.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-641","eolDate":"2023-02-20"},{"agent":"nodejs","date":"2020-02-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added support for W3C Trace Context, with easy upgrade from New Relic trace context. Distributed tracing now supports W3C Trace Context  headers for HTTP protocols when distributed tracing is enabled. Our implementation can accept and emit both the W3C trace header format and the New Relic trace header format. This simplifies agent upgrades, allowing trace context to be propagated between services with older and newer releases of New Relic agents. W3C trace header format will always be accepted and emitted. New Relic trace header format will be accepted, and you can optionally disable emission of the New Relic trace header format. When distributed tracing is enabled with distributed_tracing.enabled: true, the Node agent will now accept W3C's traceparent and tracestate headers when calling TransactionHandle#acceptDistributedTraceHeaders or automatically via http instrumentation. When calling Transaction#insertDistributedTraceHeaders, or automatically via http instrumentation, the Node agent will include the W3C headers along with the New Relic distributed tracing header, unless the New Relic trace header format is disabled using distributed_tracing.exclude_newrelic_header:true. Added TransactionHandle#acceptDistributedTraceHeaders API for accepting both New Relic and W3C Trace Context distributed traces. Deprecated TransactionHandle#acceptDistributedTracePayload which will be removed in a future major release. Added TransactionHandle#insertDistributedTraceHeaders API for adding outbound distributed trace headers. Both W3C Trace Context and New Relic formats will be included unless distributed_tracing.exclude_newrelic_header: true. Deprecated TransactionHandle#createDistributedTracePayload which will be removed in a future major release. Known issues and workarounds If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream Node New Relic agents to this agent release. Improvements Improved transaction and trace ID generation. AWS Lambda Added collection of additional AWS Lambda event source meta data. Added event type detection for Lambda invocation events. Expanded ARN harvest to include ALB and CloudWatch. Fixes Fixed issue where Lambda invocation errors were not noticed in Node 10 or Node 12 environments. Pins Node 12 CI/testing version to v12.15 to avoid breakages with v12.16.0 until cause(s) resolved. Updated publish-docs script to use npm run instead of make. Known issues and workarounds If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream New Relic Node agents to this agent release.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-640","eolDate":"2023-02-12"},{"agent":"nodejs","date":"2020-01-27","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Bumped @newrelic/aws-sdk to v1.1.1 from v1.0.0. https://github.com/newrelic/node-newrelic-aws-sdk/blob/master/CHANGELOG.md  Notable improvements include: Added official support for API promise calls, fixing two critical bugs. Added check before applying instrumentation to avoid breaking for very old versions. Added bindPromise() to Shim prototype for direct usage by instrumentation. Previously, _bindPromise() was a private function in the Shim module. Updated language in agent to be in line with New Relic Standards. Fixes Fixed spelling in configuration error. Thank you to David Ray (@daaray) for the contribution. Fixed long-log truncation issue in Serverless mode.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-630","eolDate":"2023-01-27"},{"agent":"nodejs","date":"2019-11-25","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added getLinkingMetadata() method to the API. This new method can be used to retrieve the identifying information for the agent and current active span and trace. Please consult the documentation  for more information. Added getTraceMetadata() to the agent API. This new method can be used to retrieve the current active Distributed Tracing span and trace ids. Please consult the documentation  for more information. Added an isSampled() method to Transaction and TransactionHandle. This new method can be used to retrieve the sampling decision made for a given transaction. Please consult the documentation  for more information. Fixes Upgraded tap to resolve handlebars audit warnings.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-620","eolDate":"2022-11-25"},{"agent":"nodejs","date":"2019-11-05","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added @newrelic/aws-sdk module to agent for auto-include on install. Added splitting of application name using semicolons in the env var. Instrumented connection.execute for mysql2. Improvements @newrelic/native-metrics module is defaulted to disabled in serverless mode. This can reduce lambda cold-start times by up to 170ms. The native-metrics module can rarely load in serverless environments due to differences from build environment to deployed environment and offers little value in a serverless environment. Added env var NEW_RELIC_NATIVE_METRICS_ENABLED to enable/disable the native-metrics module Added a test for querying poolCluster.of() Added HTTP method to segment attributes for external requests. Updated the bin/ssl.sh such that it uses verbose output, will exit on first error code, and will refuse to proceed with LibreSSL (which can't generate certs). Added a clear sub-command to bin/ssl.sh that will allow developers to quickly remove generated ssl/cert files and regenerate (useful is switch between platforms via containers/docker and certs needs to be regenerated) Fixes Removed unused mysql bootstrap test code. Increased timeout for index-bad-version test to reduce flickers on Node 12. Changed file modification to leverage writeFile for watchFile test. This triggers the watcher in a reasonable amount of time much more consistently. Removed testing of Bluebird 3.7 on Node v10 until they fix the segfault issue .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-610","eolDate":"2022-11-05"},{"agent":"nodejs","date":"2019-10-29","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Added official parity support for Node 12. Exception: Errors resulting in unhandled rejections will no longer be scoped to the transaction that was active when the rejected promise was created. As of Node 12, the promise responsible for triggering the init async hook will no longer be passed through on the promise wrap instance. This breaks the linkage used to relate a given promise rejection to the transaction it was scheduled in. BREAKING  Removed support for Node 6, 7, and 9. The minimum supported version is now Node v8. For further information on our support policy, see: https://docs.newrelic.com/docs/agents/nodejs-agent/getting-started/compa... . Bumped version of @newrelic/superagent instrumentation to v2.0.0. Bumped version of @newrelic/native-metrics to v5.0.0. BREAKING  Bumped version of @newrelic/koa instrumentation to v3.0.0 @newrelic/koa update includes changes to transaction naming in addition to dropping Node versions 6, 7, and 9. See @newrelic/koarelease notes for what was included in v2.0.0 and v3.0.0 updates. https://github.com/newrelic/node-newrelic-koa/blob/master/NEWS.md . BREAKING  max_samples_stored behavior has changed to replace max_samples_per_minute. max_samples_per_minute is no longer a configuration parameter. The new behavior for max_samples_stored is as follows: \"The agent will collect all events up to this number per minute. If there are more than that, a statistical sampling will be collected.\" This usage of the configuration is consistent with other New Relic APM agents. If your application has previously used max_samples_per_minute as an upper bound, you may need to lower the threshold to a valid maximum to avoid data being dropped on the server. No larger than 10k is recommended. Updated utilization callback test to point to a host that can't represent a valid provider. Previously, location where CI provider runs tests could cause test to fail. Added support for Promise.allSettled() method in Bluebird 3.7. Bumped mongodb dev dependency past security warning. Fixed mongodb versioned tests so they are self-contained by using version under test for setup/teardown instead of agent dev-dependency version. Forced filename resolution if not already cached on module load. This should not occur in normal/non-test scenarios but provides a fall-back to maintain functionality. Refactored restify versioned tests to be less dependent on the order of asynchronous operations. Updated README to reference Pug rather than Jade.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-600","eolDate":"2022-10-29"},{"agent":"nodejs","date":"2020-10-28","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.14.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date . Fixes Fixed issue where gRPC connection used for infinite tracing could throw if the server shutdown during disconnect of an existing connection. Fixed bug where errors would still be collected for transactions with ignored error status codes in certain situations. Improvements Added Node 14 to CI test coverage. Many thanks to @jgeurts for the contribution. Bumped @grpc/grpc-js to 1.1.7. Bumped @grpc/proto-loader to ^0.5.5. Updated README for consistency. Converted errors ignore unit tests to tap API. Infinite tracing logging and support metric improvements. Increased logging level of certain infinite tracing / gRPC errors. Decreased logging interval of dropped span warning for infinite tracing. Added additional support metrics and logging for infinite tracing.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-6-14-0","eolDate":"2022-10-28"},{"agent":"nodejs","date":"2020-10-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.13.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Removed lodash as a development dependency Check for named pipe existence before each flush This removes the cached value used in 6.13.1 Improvements Update shim documentation Thank you to @ronen-e for the contribution!","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-6-13-2","eolDate":"2022-10-13"},{"agent":"nodejs","date":"2020-09-24","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.13.1","features":[],"bugs":["Fix the named-pipe check for lambda invocations to avoid race-condition."],"security":[],"supportedOperatingSystems":null,"description":"Fixes Fixed named-pipe check for lambda invocations to avoid race-condition. Named-pipe existence will now be checked just prior to first write and then cached. Improvements Updated README with community-plus header. Updated README config copy example. Added Open Source Policy workflow. Removed repository CoC in favor of centralized CoC at org root.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-6-13-1","eolDate":"2023-09-24"},{"agent":"nodejs","date":"2020-08-25","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.13.0","features":["Add the ability for the agent to write to a named pipe, instead of stdout, when in serverless mode."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Features Added ability for the agent to write to a named pipe, instead of stdout, when in serverless mode.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-6-13-0","eolDate":"2023-08-25"},{"agent":"nodejs","date":"2020-08-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.12.1","features":[],"bugs":[],"security":["Resolve an issue where transaction traces will still capture the request URI when the Node.js agent is configured to exclude the 'request.uri' attribute."],"supportedOperatingSystems":null,"description":"Fixes Security fix:  Resolves an issue where transaction traces will still capture the request URI when the Node.js agent is configured to exclude the 'request.uri' attribute. This can be problematic for certain customers in environments where sensitive information is included in the URI. See security bulletin NR20-02 . The request URI will now be excluded from transaction traces if the 'request.uri' attribute has been set to be excluded at either the top-level 'attributes.exclude' configuration or at the 'transaction_tracer.attributes.exclude' configuration.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-6-12-1","eolDate":"2023-08-20"},{"agent":"nodejs","date":"2020-08-10","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.12.0","features":["Upgrade `async` to `v3.2.0`."],"bugs":["Fix obfuscation of SQL queries with large data inserts.","On failed instrumentation, prevent multiple requires from re-wrapping shims."],"security":[],"supportedOperatingSystems":null,"description":"Improvements Updated guidelines and templates for contributing to the project. Updated SECURITY.md with coordinated disclosure program link. Upgrade async to v3.2.0. Special thanks to Yohan Siguret (@Crow-EH) for the contribution. Bumped @newrelic/native-metrics to ^5.3.0. Bumped @newrelic/aws-sdk to ^2.0.0. Bumped node-test-utilities to ^4.0.0. Bumped @newrelic/superagent to ^3.0.0. Bumps @newrelic/koa to ^4.0.0. Fixes Fixes obfuscation of SQL queries with large data inserts. Special thanks to Tomáš Hanáček (@tomashanacek) for tracking down the issue and providing the fix. On failed instrumentation, prevent multiple requires from re-wrapping shims. Special thanks to Ryan Copley (@RyanCopley) for the contribution.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-6-12-0","eolDate":"2023-08-10"},{"agent":"nodejs","date":"2020-07-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.11.0","features":["Add Distributed Tracing option to config file used for first time customers."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Features Updated to Apache 2.0 license Added CODE_OF_CONDUCT.md file Streamlined README.md file Updated CONTRIBUTING.md file Added additional guidance to bug report template Added copyright headers to all source files Improvements Added Distributed Tracing option to config file used for first time customers Converted some test files to Node-tap Removed \"hidden\" and unused code injector diagnostic capability Upgraded @grpc/grpc-js from 1.0.4 to 1.0.5","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-6-11-0","eolDate":"2023-07-07"},{"agent":"nodejs","date":"2020-06-22","downloadLink":"https://www.npmjs.com/package/newrelic","version":"6.10.0","features":["Add additional Transaction Information to Span Events.","Custom transaction attributes added via `API.addCustomAttribute` or `API.addCustomAttributes` will now be propagated to the currently active span, if available."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"New Features Additional Transaction Information applied to Span Events When Distributed Tracing and/or Infinite Tracing are enabled, the Agent will now incorporate additional information from the Transaction Event on to the currently available Span Event of the transaction. The following items are affected: aws-lambda related attributes error.message error.class error.expected http.statusCode http.statusText message.* parent.type parent.app parent.account parent.transportType parent.transportDuration Request Parameters request.parameters.* request.header.* request.method request.uri Custom Attributes Custom transaction attributes added via API.addCustomAttribute or API.addCustomAttributes will now be propagated to the currently active span, if available. Security Recommendation: Review your Transaction Event attributes configuration. Any attribute include or exclude setting specific to Transaction Events should be applied to your Span Attributes configuration or global attributes configuration. Please see Node.js agent attributes  for more on how to configure. Improvements Upgraded @grpc/grpc-js from 1.0.3 to 1.0.4 Modified redis callback-less versioned test to use commandQueueLength as indicator redis command has completed and test can continue. This is in effort to further reduce these test flickers. Additionally, added wait for client 'ready' before moving on to tests. Updated force secret test runs to run on branch pushes to the main repository.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-6-10-0","eolDate":"2023-06-22"},{"agent":"nodejs","date":"2019-05-28","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.9.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Shim#require will now operate as expected. Previously, the module interception code made the faulty assumption that a module's filepath would be resolved before the module load call was invoked. This caused the wrap filepath to be attributed to the modules being instrumented. This meant that attempted relative require calls using Shim#require would resolved from the incorrect path. The logic has been changed to keep a stack of the resolved filepaths, resolving the issue. Shim#wrapReturn now uses ES6 proxies to wrap its methods. This will accurately propagate look up and assignment onto the underlying wrapped function, while maintaining all previous functionality. Updated versioned test configurations to reflect current engine support. Moved third party notices to THIRD_PARTY_NOTICES.md Updates error message for license check to indicate all places that need to be updated.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-591","eolDate":"2022-05-28"},{"agent":"nodejs","date":"2019-05-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features serverless_mode feature flag is now enabled by default. Added instrumentLoadedModule method to the API, allowing end-users to manually apply an instrumentation to a loaded module. Useful for cases where some module needs to be loaded before newrelic Improvements Removed older versions of Cassandra from versioned tests For debug/test runs, shimmer will now cleanup the __NR_shim property on instrumented methods. This leftover property did not result in any negative behaviors but cleaning up for thoroughness and to prevent potential confusion. Fixes recordMiddleware promise parenting for certain cases where child segments are created within resolving middleware next() promises.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-590","eolDate":"2022-05-20"},{"agent":"nodejs","date":"2019-05-06","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Modifies MiddlewareSpec route property to allow functions. Defers route processing and segment naming until just before needed (each middleware invocation). Improvements Fixed outdated license ref in package.json. Middleware instrumentation now honors spec.appendPath for more cases and will not pop paths when it has not appended a path.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-580","eolDate":"2022-05-06"},{"agent":"nodejs","date":"2019-04-24","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added getStatusName to NameState. Now web transactions will be named after known status code messages (404, 405, and 501). Added appendPath option to MiddlewareSpec. Improvements Broke apart integration script test globs.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-570","eolDate":"2022-04-24"},{"agent":"nodejs","date":"2019-04-16","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.6.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Refactored config to log warning and disable distributed tracing if enabled in serverless mode, but missing required config setting. Serverless mode no longer sets different data collection limits. The agent will no longer crash the process in the event of unexpected calls to the harvest callback. Updated required config values when using distributed tracing in serverless_mode to only include account_id.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-564","eolDate":"2022-04-16"},{"agent":"nodejs","date":"2019-04-01","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.6.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes The agent will now accurately filter out request parameters while operating under CSP or HSM. You can find more information about this change in the Security Bulletin .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-563","eolDate":"2022-04-01"},{"agent":"nodejs","date":"2019-03-25","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.6.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Agent now respects attribute type restrictions on trace/segment attributes, as well as error event/trace attributes. Bug fixes Fixes potential for RangeError: Maximum call stack size exceeded error on Transaction/Trace end. Custom events no longer accept attributes with invalid types. The only attribute types accepted by the backend are boolean, string, and number; any attribute assigned to a custom event outside these types would be dropped on ingest. The agent now filters these attributes out, and logs out a helpful message detailing the issue.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-562","eolDate":"2022-03-25"},{"agent":"nodejs","date":"2019-03-11","downloadLink":null,"version":"5.6.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Updated log message for not adding attributes and change the log level to debug. Fixed an issue where exclusive time would be improperly calculated in some cases.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-561","eolDate":"2022-03-11"},{"agent":"nodejs","date":"2019-03-04","downloadLink":null,"version":"5.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added product attribute to existing datastore instrumentations. Added db.collection to datastore span event attributes. Improvements trusted_account_key, account_id, and primary_application_id may now be configured via a configuration file while in serverless mode. Optimized exclusive time duration calculator. Previously, the agent would spend a lot of time sorting redundant arrays while calculating the exclusive time for the segments of a trace. This has been refactored into a single postorder traversal over the tree which will calculate the exclusive time for all segments in the subtree rooted at a given segment. Fixes Fixed a bug where data belonging to distributed traces starting in the Node.js agent would be prioritized over data produced from traces starting in other language agents. Previously, the agent would use the same random number for both the transaction priority (used for data sampling) and the distributed tracing trace sampling decision (whether to create DT data for a given transaction). This random number reuse resulted in a bias that caused data from distributed traces started in the Node.js agent to be prioritized above data that belongs to distributed traces started in other language agents. The agent now makes individual rolls for each of these quantities (i.e. the transaction priority and trace sampling decision), eliminating the bias. Prevent a split on undefined location under certain conditions in Memcached.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-560","eolDate":"2022-03-04"},{"agent":"nodejs","date":"2019-02-19","downloadLink":null,"version":"5.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added SNS to message shim library names. Added check for collect_span_events in config sent from the server on connect. Collection of span events can be disabled from the server configuration, but not enabled. Improvements Refactored Segment#toJSON to be more readable. Added a try/catch to config initialization to safely handle invalid setting combinations. When an error is caught the agent is marked as disabled, which ultimately returns a stub API and keeps the process running. String truncation is now done using a binary search over the byte length of the string. Previously this truncation was done using a linear search for the proper byte length. Optimized segment and span attribute filtering. Fixes Fixed issue where shim.createSegment() could result in modifying the parent when opaque. Fixed issue where http-outbound would modify parent segments when parent is opaque. Moved processing of exclusive time attribute out of toJSON and into finalize to only be calculated once. Previously, serializing a segment would result in calculating and caching exclusive time which could result in issues if serialized prior to ending.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-550","eolDate":"2022-02-19"},{"agent":"nodejs","date":"2019-02-11","downloadLink":null,"version":"5.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added span_events and transaction_segments attribute destinations. Span event and segment attributes can now be filtered using the same include/exclude config rules as other types. See agent attribute configuration  for more details. Added metadata field to connect payload, for collecting NEW_RELIC_METADATA_-prefixed environment variables. Added DynamoDB to datastores. Added opaque option to datastore operation spec. Added Kubernetes utilization detection. Upgraded concat-stream and readable-stream to next major version. These modules had previously been held back due to support for Node <6. Since v5.0.0 we dropped that support thus enabling these updates. Added SQS as a supported messaging library name. Enabled tracking of callback via message-shim.recordConsume when no messageHandler provided. Improvements Replaced make rules with npm scripts. Bug fixes The agent will now consistently harvest in all response cases when in serverless mode. Previously, the agent's harvest was in a race with process suspension in the event of an uncaught exception, or responding without calling a callback. A synchronous harvesting process is now used to circumvent this racing issue. Fixed issue with socket connection errors causing the agent to stop attempting to connect at startup. Fixed opaque segment functionality for message-shim.recordProduce. Fixed opaque segment functionality for message-shim.recordConsume.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-530","eolDate":"2022-02-11"},{"agent":"nodejs","date":"2019-01-29","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Removed installation of Oracle container test scripts. Replaced explicit config.high_security === true checks with general truthiness checks. The agent will now treat any truthy value in the high_security config setting as if it is enabled. Bug fixes Fixed bug where agent would stop sending data to New Relic servers when a connectivity issue was encountered. Fixed unit test with incorrect usage of cross application tracing.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-521","eolDate":"2022-01-29"},{"agent":"nodejs","date":"2019-01-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added Neptune to the known database names. Improvements Updated log messages for missing configuration files to point at the base configuration. Previously the log messages pointed at an internal file defining default values for every configuration. Upgraded to @newrelic/native-metrics v4. Removed outdated config files. Removed old, outdated examples. Bug fixes Fixed an issue where old CAT headers would be injected while distributed tracing was enabled. This would happen if both cross_application_tracing.enabled and distributed_tracing.enabled were set to true and an instrumentation disabled tracing for an outbound request. Fixed access to ConglomerateShim in shimmer.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-520","eolDate":"2022-01-23"},{"agent":"nodejs","date":"2019-10-10","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.13.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added diagnostic code injector. The agent may now be configured to make transaction state checks via code injection. This may be turned on by setting code_injector.diagnostics.enabled to true. While this option is enabled, code around async boundaries will be added to track transactions, and log a message when they are not properly reinstated. Added back generation of entity stats logging and uninstrumented support metric generation on metric harvests. Removed legacy harvest code from main agent. Upgraded tap to latest version Upgraded mocha to latest version. Adds --exit flag to mocha test runs to prevent infinite runs on CI. Fixes primary_application_id now defaults to 'Unknown' in serverless mode to allow Distributed Tracing to function correctly when NEW_RELIC_PRIMARY_APPLICATION_ID is not defined. Updated https-proxy-agent to v3 for security fix. Shoutout to @asturur for the contribution. Fixed bug where API.shutdown() would not properly harvest when configured to. Fixed bug where multiple agent restarts would cause the number of 'stopped' listeners to exceed limit. Fixed inconsistent async return from collector API. This could result in an infinite loop due to attempting to merge before clearing. This bug should not have impacted normal agent runs but was uncovered for certain test cases. Fixed tests that leave work scheduled on the event loop. Fixed issue that could result in vendor utilization detection failure. As a part of this fix, the request that hits the timeout will immediately abort instead of hanging around for the default timeout.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-5131","eolDate":"2022-10-10"},{"agent":"nodejs","date":"2019-10-01","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Support for Real Time Streaming Event data is now sent to New Relic every five seconds, instead of every minute. As a result, transaction, error, and custom events will now be available in New Relic and Insights dashboards in near real time. For more information on how to view your events with a five-second refresh, see the real time streaming documentation . Note that the overall limits on how many events can be sent per minute have not changed. Also, span events, metrics, and trace data is unaffected, and will still be sent every minute. Now supports Restify 7 and 8. Distributed Tracing is now enabled by default in serverless mode. HTTPS connections to New Relic now use a keep alive HTTP-Agent. Improvements Maximum event limits are now enforced by the server. This includes a new maximum of 10000 transaction events per minute. Harvesting is now completed by individually scheduled harvesters per data type. Drops old odd-numbered node versions that are no longer supported by node from travis testing matrix Updated Mocha and Docker links in CONTRIBUTING.md. Fixes Bumps tap version to move beyond handlebars audit warning. Bumps Restify dev dependency past audit warning. Fixed bug where segment reference on the outbound request was enumerable. Fixed bug where incorrect config information was sent to New Relic. The agent will now end/serialize transactions in the event of an uncaught exception while operating in serverless mode.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-5130","eolDate":"2022-10-01"},{"agent":"nodejs","date":"2019-07-31","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.11.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Implements Expected and Ignored Errors functionality Adds support for scoped package name introduced in hapi v18 (@hapi/hapi). This will provide functionality at parity with instrumentation for hapi v17. Any new features may not yet be supported. Improvements Bumps jsdoc and lodash dev dependency to avoid upstream vulnerability warning. Adds detailed logging through harvest/collector code to increase supportability. Fixes Fixed bug where agent would count errors towards error metrics even if they were dropped due to the error collector being disabled. The agent will now properly track cached paths to files in loaded modules on Node versions >10. As of Node v11, the path to a file in a module being loaded will only be resolved on the first load; subsequent resolution of that file will use a cached value. The agent records this resolved path and uses it for relative file look ups in order to deep link into modules using Shim#require. Since the agent couldn't reliably get at the path on the subsequent calls to require, it now replicates the caching logic and hold onto the resolved path for a given file.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-5110","eolDate":"2022-07-31"},{"agent":"nodejs","date":"2019-06-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.10.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Enables ability to migrate to Configurable Security Policies (CSP) on a per agent basis for accounts already using High-security mode (HSM). When both HSM and CSP are enabled for an account, an agent (this version or later) can successfully connect with either high_security: true or the appropriate security_policies_token configured. high_security has been added as part of the preconnect payload. Improvements The agent now allows installation on node v11 and v12. This change relaxes the engines restriction to include Node v11 and v12. This does not constitute official support for those versions, and users on those versions may run into subtle incompatibilities. For those users who are interested in experimenting with the agent on v11 and v12, we are tracking relevant issues here: https://github.com/newrelic/node-newrelic/issues/279 . Fixes Lambda invocations ended with promises will now be recorded properly. Previously, the lambda instrumentation was not intercepting the promise resolution/rejection returned from a lambda handler. The instrumentation now properly observes the promise, and ends the transaction when the promise has finished. Lambda invocations will only attempt to end the related transaction a single time. In the event of two lambda response events (e.g. callback called, and a promise returned), the agent would attempt to end the transaction twice, producing an extraneous empty payload. The agent now limits itself to a single end call for a given transaction. The agent will now properly end transactions in the face of uncaught exceptions while in serverless mode.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-5100","eolDate":"2022-06-12"},{"agent":"nodejs","date":"2019-01-17","downloadLink":"https://www.npmjs.com/package/newrelic","version":"5.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added new shim type: ConglomerateShim This shim class is useful for instrumenting modules which implement several service interfaces of different types. Improvements Disabled logging by default when serverless_mode is enabled. Please note serverless/lambda monitoring is not yet officially released. null trace attribute values are no longer sent to New Relic. This change brings the Node agent in alignment with the behavior of other language agents.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-510","eolDate":"2022-01-17"},{"agent":"nodejs","date":"2019-01-08","downloadLink":null,"version":"5.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Dropped support for Node versions less than 6. Agent no longer creates transactions when in a stopped, stopping or errored state. Removed public API methods that have been deprecated since Agent v2: createTracer, createWebTransaction, createBackgroundTransaction, and addCustomParameter/(s). See the Migration Guide  for more information. Flagged API#setIgnoreTransaction as deprecated; TransactionHandle#ignore should be used instead. Released several feature flags. These flags are no longer used: feature_flag.custom_instrumentation feature_flag.custom_metrics feature_flag.synthetics feature_flag.native_metrics Added plugins.native_metrics.enabled configuration value. This configuration value controls the use of the @newrelic/native-metrics module. When set to false the agent will not attempt to load that module. Custom metrics recorded via recordMetric and incrementMetric API calls now automatically have the name prepended with 'Custom/'. Usages of these APIs that manually prepend with 'Custom/' will need to remove the manually specified one or will end up with metrics prepended with 'Custom/Custom/'. Dropped support for node-cassandra-cql. Removed from ignore_server_configuration config setting. Removed deprecated configuration settings capture_params and ignored_params. The agent will no longer cause a stack overflow when logging at trace level to stdout. Previously, the agent would inadvertently trigger a trace level log from its trace level log (through wrapping a nextTick call), causing a stack overflow. The agent now detects this case and aborts the nested call.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-500","eolDate":"2022-01-08"},{"agent":"nodejs","date":"2018-10-01","downloadLink":"https://www.npmjs.com/package/newrelic","version":"4.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added superagent as built-in instrumentation. This instrumentation just maintains transaction state when using the superagent module to make HTTP requests with either callbacks or promises. Updated noticeError API method to be partially functional in High-security mode. In HSM, any custom attributes will be ignored, but the error will still be tracked. This brings the Node agent in line with the behavior of other language agents. Added PromiseShim class for instrumenting promise libraries. Support for setting transaction_tracer.transaction_threshold to 0 has been added. Improvements Updated DT payload creation to use primary_application_id from connect response. Added protection against functions with modified prototypes in shim.applySegment. Replaced SQL ID hash generation algorithm with SHA1 instead of MD5 to allow usage in FIPS compliant environments. Leveraged 16 hex digits for creation of SQL ID. Upgraded ejs module to get rid of Github security warnings. The ejs module was only used for tests and not in main agent code. Changes DT payload configuration log messages to debug level as it is not uncommon for calls to occur before server configuration has been retrieved. Converted net instrumentation to use shim api. Converted child_process instrumentation to newer shim style. Converted Timers instrumentation to newer shim style. Converted zlib instrumentation to use shim API. Bug fixes Fixed codec.decode() callback bug that would re-call a callback with an error thrown within the callback. Fixed bug requiring Cross Application Tracing (CAT) to be enabled for Distributed Tracing (DT) createDistributedTracePayload and acceptDistributedTracePayload APIs to function. DT configuration will no longer consider CAT configuration. Fixed bug in wrap() that would fail to wrap callbacks if the callback index was 0. The agent now respects NEW_RELIC_TRACER_THRESHOLD. Previously, this environment variable was stored as a string. The environment variable is now stored as a float.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-490","eolDate":"2021-10-01"},{"agent":"nodejs","date":"2018-08-27","downloadLink":"https://www.npmjs.com/package/newrelic","version":"4.8.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Converted File System instrumentation to use newer shim style. Converted DNS instrumentation to newer shim style. Added tracking of callbacks to DNS instrumentation. Converted crypto instrumentation to newer shim style. Updated domains instrumentation to use an instrumentation shim. Refactored the global instrumentation to use the shim API. Ported inspector instrumentation to use an instrumentation shim. Ported async_hooks based promise instrumentation over to using shims. Added shim types for core instrumentations. Improved benchmark comparison output. Added http benchmark tests. Bug fixes Agent instrumentation will no longer interfere with promisification of core methods. Some core methods expose pre-promisified versions of the methods as a reference on the method itself. When instrumenting these methods, it neglected to forward these references onto the wrapper function. Now the instrumentation will properly forward property look ups to the original method. Fixed outbound https call to use example.com to resolve integration test issue. Fixed tests for ioredis 4.0.0 and above.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-481","eolDate":"2021-08-27"},{"agent":"nodejs","date":"2018-08-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"4.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Implemented enforcement of max_payload_size_in_bytes config value. Any payload during the harvest sequence that exceeds the configured limit will be discarded. Added JSON-formatted output to benchmarks to enable automated benchmark comparison. Updated the benchmark runner to measure specifically userland CPU overhead. Added DatastoreShim benchmarks. Bug fixes Fixed MongoDB instrumentation for driver versions greater than 3.0.6. Mongo 3.0.6 removed metadata the Agent relied upon to instrument the driver. This fixes that by going back to the old method of manually listing all objects and methods to instrument. Updated MySQL versioned tests to run against the latest release.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-480","eolDate":"2021-08-13"},{"agent":"nodejs","date":"2018-07-31","downloadLink":null,"version":"4.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added support for distributed tracing. Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before. Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide  before you enable this feature. To enable distributed tracing, set distributed_tracing.enabled to true in your newrelic.js file, or set NEW_RELIC_DISTRIBUTED_TRACING_ENABLED in your environment. Added a warning for too-new versions of Node.js during agent startup. Appropriately obfuscated SQL statements will now be included in all transaction traces. Previously, the agent would only include the SQL statements if the corresponding query was sufficiently slow. Added ability to execute instrumentation functions in the context of the segment the segment descriptor is describing. All record* methods supplied by all instrumentation shim classes now allow for a function to be executed under the context of the segment the record call will produce. This may be done by supplying a function in the inContext key for the segment descriptor passed to the record method. Reservoirs will now respect setting their size to 0.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-470","eolDate":"2021-07-31"},{"agent":"nodejs","date":"2018-07-24","downloadLink":null,"version":"4.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added full support for Node v10. Added instrumentation for crypto.scrypt. Added instrumentation for fs.realpath.native. Added instrumentation for process.setUncaughtExceptionCaptureCallback. Fixes Updated tests to use asyncResource.runInAsyncScope instead of emitBefore and emitAfter","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-460","eolDate":"2021-07-24"},{"agent":"nodejs","date":"2018-07-18","downloadLink":null,"version":"4.5.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes The agent will now properly remerge event data on collection failure. Previously, the agent wouldn't observe the correct format for remerging, causing undefined events to be pushed into the reservoir.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-451","eolDate":"2021-07-18"},{"agent":"nodejs","date":"2018-07-16","downloadLink":"https://www.npmjs.com/package/newrelic","version":"4.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Feature flags may now be set from environment variables. Using the naming convention NEW_RELIC_FEATURE_FLAG_<feature flag name in upper case>. Improvements Transaction events may be harvested in two payloads now. This change reduces the occurrence of harvests being rejected due to large payloads. Payloads will only be split when they are large (greater than 1/3 the maximum). Bug fixes Updated Hapi v17 instrumentation to wrap server export, in addition to Server.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-450","eolDate":"2021-07-16"},{"agent":"nodejs","date":"2018-07-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"4.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Replaced trusted_account_ids array with trusted_account_key. Added node v10 to the test matrix. Bug fixes Added config utilization env vars to the BOOLEAN_VARS set. This ensures that if these boolean config values are set outside of a config file, their values are respected, particularly when they are disabled.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-440","eolDate":"2021-07-12"},{"agent":"nodejs","date":"2018-07-09","downloadLink":null,"version":"4.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added nonce option for newrelic.getBrowserTimingHeader() This allows people to pass in a string to be injected as the nonce property of the generated script tag. Special thanks to João Vieira (@joaovieira) for contributing this feature! Expose the External segment on the http request instance for outbound calls. Fixes Added check to mark Hapi 'onPreResponse' extensions as error handlers. Previously, the agent was unable to mark any Hapi errors as handled, even if they were, resulting in inaccurate reporting. This change assumes that 'onPreResponse' extensions act as error handlers, so errors are only reported if they persist to the final response.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-430","eolDate":"2021-07-09"},{"agent":"nodejs","date":"2018-07-02","downloadLink":null,"version":"4.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added more tests for transaction naming with Restify. Fixes Fixed issue with tracking external requests to default ports. Special thanks to Ryan King for pinpointing the cause of this issue. Added extra check for handling arrays of functions when wrapping middleware mounters. This fixes a bug with the agent incorrectly assuming that arrays passed as the first argument in middleware would only contain route paths, causing a fatal error. The agent now reports the total time of the transaction on transaction events.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-421","eolDate":"2021-07-02"},{"agent":"nodejs","date":"2018-06-19","downloadLink":"https://www.npmjs.com/package/newrelic","version":"4.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added an option for using the finally method on promises for instrumentation. The promise instrumentation would use Promise#finally if available. This change is in response to Node v10 promises calling then inside their finally method, which caused infinite recursion in the agent's promise instrumentation. Added seen/sent/dropped supportability metrics for all event collections. Improvements Refactored harvest cycle into separate class. This refactoring eases managing harvested data and re-merging unharvested values on failure. No longer download gcc on test suites that do not require it. Bug fixes Updated WebFrameworkShim to handle arrays of routes when wrapping middleware mounters. Previously, a transaction that hit a shared middleware (eg, app.use(['/one', '/two'], ...)) would always be tagged with <unknown> in its name, due to the agent not interpreting arrays of paths. Now transaction names will include all paths for a shared middleware, comma-delimited, followed by the current route ('WebTransaction/Expressjs/GET//one,/two/one').","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-420","eolDate":"2021-06-19"},{"agent":"nodejs","date":"2018-06-11","downloadLink":null,"version":"4.1.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Make require() statements explicitly reference package.json as a .json file. This solves a problem when requiring/importing newrelic from a Typescript file. Check if process.mainModule.filename exists before using in missing config file check. When the agent is preloaded with Node's --require flag, mainModule is not yet defined when the agent checks for a config file, resulting in a TypeError in the event that no config file exists. Defaulting to the file path being executed in process.argv ensures that the app will not crash when preloaded without a config file. Updated dev dependency tap to v12.0.1. Fixed identification of errors with express. Previously the call next('router') was considered an error. This is actually valid usage of express and will no longer generate an error. Removed debug.internal_metrics configuration. This legacy debug configuration was never used since trace-level logging provides everything this did and more. Upgraded optional dependency @newrelic/native-metrics to v3. With this update comes pre-built binaries for Node 5 and 7. GC metrics are also now aggregated in C++ until the agent is ready to harvest them instead of hopping into JS for each event. Added additional checks to uninstrumented ensuring that files with names matching instrumented modules do not result in a false uninstrumented status. For example, some users load config/env info before the agent. In that case, a file responsible for exporting DB config information (config/redis.js), may result in a false uninstrumented status, because the agent would interpret redis.js as the module itself.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-415","eolDate":"2021-06-11"},{"agent":"nodejs","date":"2019-04-23","downloadLink":null,"version":"4.13.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed bug where agent would stop sending data to New Relic servers when a connectivity issue was encountered. The agent will no longer crash the process in the event of unexpected calls to the harvest callback.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-4131","eolDate":"2022-04-23"},{"agent":"nodejs","date":"2018-12-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"4.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features The agent now reacts to failed New Relic requests based on response code, as opposed to parsing an exception message in the response body. Improvements Fixed clearing of active harvest via _stopHarvester() Fixed handling of harvest endpoints when not all fail. Added agent state \"connecting\" to indicate when handshake with New Relic servers is starting. This can be triggered on startup and restarts. Added --no-package-lock to unit and integration rules. Released protocol_17 feature flag. Replaced nsp with npm audit in security checks. Collector now specify application/json content-type when data is compressed instead of octet-stream. Bumped ecmaVersion in test .eslintrc to 8","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-4130","eolDate":"2021-12-20"},{"agent":"nodejs","date":"2018-05-29","downloadLink":null,"version":"4.1.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed metric merging when using debug.internal_metrics. The debug metrics cache would cause timestamps for harvested metrics to get stuck at agent startup. This will no longer happen, and the debug cache is reset each harvest. Improvements Modularized configuration constants to improve readability.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-413","eolDate":"2021-05-29"},{"agent":"nodejs","date":"2018-12-03","downloadLink":"https://www.npmjs.com/package/newrelic","version":"4.12.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added IP address collection and forwarding of metadata headers for upcoming protocol 17. These features are currently behind the protocol_17 feature flag until all parts of protocol 17 are implemented. Improvements Converted error handling in CollectorAPI and RemoteMethod to callbacks. Previously many of the errors were thrown. For consistency with async errors, these are now handed to the callback instead of thrown. The old behavior could result in a crash under a few circumstances, such as when the agent exceeded a configured maximum payload size. These errors came from RemoteMethod._safeRequest. Since these errors are handed to the callback instead of thrown, this bug is no longer a potential. Refactored harvest interactions in preparation for protocol 17 status codes.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-4120","eolDate":"2021-12-03"},{"agent":"nodejs","date":"2018-05-22","downloadLink":null,"version":"4.1.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Updated use of fs.unlink without a callback to fs.unlinkSync. As of Node v10, the callback is no longer optional , which was causing a false test failure. Fixed access to properties on promisified methods.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-412","eolDate":"2021-05-22"},{"agent":"nodejs","date":"2018-11-15","downloadLink":"https://www.npmjs.com/package/newrelic","version":"4.11.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added protocol_17 feature flag. Flag will be removed and protocol will be hard-coded to 17 once functionality is released on New Relic backend. This release also includes changes to the agent to enable monitoring of Lambda functions. If you are interested in learning more or previewing New Relic Lambda monitoring please email lambda_preview@newrelic.com . Added waitForIdle option to API#shutdown. This new option will make the agent wait for all active transactions to finish before actually shutting down. This does not pre-empt creation of new transactions, so care must be taken to ensure the active transaction pool drains or the agent will never shut down. Improvements Added switch statement indenting standard to eslintrc Introduced \"warn\" level 2 space rule to eslintrc Upgraded @newrelic/test-utilities to v2. Bug fixes Changed totalTime attribute to be in decimal seconds instead of milliseconds for transaction events. Agent no longer produces spans on ignored transactions. Previously, the agent would produce distributed tracing span events regardless of the ignored status of the transaction the events originated from. Extended Restify instrumentation to mark possible transaction names in order to account for async response methods. Updated hapi@16 versioned tests to only run on Node 6 and above. Pinned mysql2 to <1.6.2 in versioned tests.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-4110","eolDate":"2021-11-15"},{"agent":"nodejs","date":"2018-05-15","downloadLink":"https://npmjs.org/package/newrelic","version":"4.1.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Optimized unhandledRejection reporting when using async_hooks. Replaced all uses of util._extend with Object.assign. Completed TODOs regarding the Node 0.10 and 0.12 deprecation. Added PriorityQueue serialization benchmarks. Bug fixes The agent no longer resizes the metric timeslice start time to be the earliest start time of the transactions that finish during the timeslice. Background transactions created may now be named through API#setTransactionName. Previously, the agent didn't respect the transaction naming precedence for background transactions. Background transaction naming behavior is now in line with web transaction behavior. Logger no longer tries to create very large log messages. When a message is created that would be too large to log, a process warning is emitted. The agent will now respect event count limits when merging data from a failed send. Previously, when merging data into an event pool the agent wouldn't maintain the size limit of the reservoir. Added check for a route prefix when wrapping Hapi route handlers. Previously, route prefixes specified via plugin options weren't being included in transaction names. Now, if the agent finds a route prefix associated with a given realm, it is prepended to the route path in the transaction name.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-411","eolDate":"2021-05-15"},{"agent":"nodejs","date":"2018-11-01","downloadLink":"https://www.npmjs.com/package/newrelic","version":"4.10.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added DatastoreShim#getDatabaseNameFromUseQuery This new method can be used to extract the database name from USE SQL queries. Improvements Added link to CONTRIBUTING.md file in README.md Thanks to Yuri Tkachenko (@tamtamchik) for the contribution. Added VS Code settings to git ignore. Fixed bug preventing Distributed Tracing (DT) from fully functioning when Cross Application Tracing (CAT) was disabled. Renames better-cat integration test organization to be distributed-tracing and updated some test verbiage to use DT or distributed tracing instead of CAT or cross application tracing. Bug fixes The agent will no longer break express routers in the case of using regex paths in a list. Previously, the agent would overwrite the regex with the source of the regex. The agent now makes a copy of the route array and mutates that instead. Attributes will now be properly propagated to PageView events. The agent may now be configured to pass attributes along to the browser agent. The attributes that match the include/exclude rules in the browser_monitor.attributes section will now be placed on PageView events.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-4100","eolDate":"2021-11-01"},{"agent":"nodejs","date":"2018-04-23","downloadLink":null,"version":"4.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added PriorityQueue class for collecting events. This replaces the Reservoir class for event sampling. Using priority sampling allows the agent to maintain randomness across a given time period while improving the chances that events will be coordinated across Transaction, Error, and Custom event pools. The agent will now allow external instrumentation modules to fail in a safe way. Previously, the agent would stop running if an externally loaded instrumentation failed for any reason. Due to the way external instrumentations can be updated independently, the agent should allow them to fail and carry on after logging a warning. Added the strip_exception_messages.enabled config option. The agent can now be configured to redact error messages on collected errors. Added the attributes.include_enabled config option. The agent can now be configured to disallow attribute include patterns to be specified. Fixes. Updated logic around wrapping route handlers when config object is present. Before, the agent would only attempt to wrap config.handler when any config object was present, without defaulting to the root handler if it didn't exist.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-410","eolDate":"2021-04-23"},{"agent":"nodejs","date":"2018-04-12","downloadLink":null,"version":"4.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes BREAKING: Updated the version of https-proxy-agent to v2.x - Dropped support for v0.10 and v0.12 of node. The version of https-proxy-agent used in the agent has a known security issue you can read about here: https://snyk.io/vuln/npm:https-proxy-agent:20180402  In order to resolve this issue, the dependency had to be updated to at least v2.2.0, which only supported node versions >=4. The update to this dependency forces the incompatibility of the agent with versions 0.10 and 0.12 of node. In order to use use the Node.js agent, please upgrade node to version >=4, or you can continue to use the agent on node versions 0.10 and 0.12 by pinning the agent to v3. You can read more about the issue here: https://docs.newrelic.com/docs/using-new-relic/new-relic-security/securi...","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-400","eolDate":"2021-04-12"},{"agent":"nodejs","date":"2018-04-10","downloadLink":null,"version":"3.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Added a type check to attribute validation, restricting values to primitive types (but not undefined). Previously the agent was only enforcing byte limits on string values, resulting in overly large arrays being collected. This brings the agent in line with other language agents. The DatastoreShim will now respect specified after handlers. Previously on methods like DatastoreShim#recordQuery the after handler would be dropped. The property is now correctly propagated to the underlying Shim#record call. The agent will now check that a specified parent segment is part of an active segment before running a method under instrumentation. Previously the agent would unconditionally run a method under a specified parent. The shim expects the parent to exist and be active, and will throw errors in the case where the parent belongs to an inactive transaction.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-331","eolDate":"2021-04-10"},{"agent":"nodejs","date":"2018-03-27","downloadLink":null,"version":"3.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added newrelic.startSegment(), which replaces newrelic.createTracer(). This new API method allows you to create custom segments using either callbacks or promises. Bug fixes Fixed bug in pre route config option in Hapi instrumentation. Only applies to Hapi v16 and below. The pre handler wrapping was not properly returning in cases when the element was a string referring to a registered server method, and as a result these elements would be replaced with undefined.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-330","eolDate":"2021-03-27"},{"agent":"nodejs","date":"2018-03-14","downloadLink":null,"version":"3.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added @newrelic/koa  as a dependency. This introduces instrumentation for Koa v2.0.0 or higher. It will be treated as first-party instrumentation within the agent, but publishing it as a separate module allows it to be installed independently according to users' needs. Improvements Refactored instrumentation hooks to work with modules. With this change it is now possible to link against external instrumentation modules.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-320","eolDate":"2021-03-14"},{"agent":"nodejs","date":"2018-03-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"3.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Promise based web framework middleware instrumentation now supports callback based sequencing. Previously, a promise based middleware was assumed to continue to the next middleware once the promise it returned resolved. This assumption has been relaxed to allow for a callback to be supplied to the middleware to invoke the next middleware.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-310","eolDate":"2021-03-13"},{"agent":"nodejs","date":"2018-03-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"3.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements 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 : 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. Adds support for EU Datacenter","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-300","eolDate":"2021-03-07"},{"agent":"nodejs","date":"2018-03-05","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.9.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes 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. Removed support for agent attributes include/exclude rules. These will be coming back in Node Agent v3.0.0. The fix for the above security bulletin required a backwards incompatible change to our attributes. Fixed bug in Bluebird instrumentation. Some methods were not instrumented correctly. This would cause a problem if a function was passed to these methods. Special thanks to Andreas Lind (@papandreou) for helping us find this bug.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-291","eolDate":"2021-03-05"},{"agent":"nodejs","date":"2018-02-27","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Note This release is deprecated due to an issue where the agent may capture transaction attributes regardless of agent settings. If you are using this release, upgrade your agent to agent version 2.9.1 or higher. For more information, see Security Bulletin NR18-06 . Improvements Added the WebFrameworkShim#savePossibleTransactionName method. This method may be used to mark the current running middleware as a potential responder. savePossibleTransactionName should be used if a middleware can't be determined to be a terminal middleware while it executes, but may be responsible for responding after execution has finished. Fixed dns.resolve results assertion. Expanded async_hooks tests around maintain transaction context. Added Koa to metric naming objects. Added callback prop to middlewareWithPromiseRecorder return spec. While we aren't actually wrapping any callback, this is a workaround that gives us access to the active segment. This ensures that all segments inside Koa transaction traces are named correctly, particularly in cases when transaction context may be lost. Updated after prop in middlewareWithPromiseRecorder return spec to set txInfo.errorHandled = true in cases when there is no error. Because Koa has no concept of errorware in the same sense as Express or Connect ((err, req, res, next)), the agent now assumes if a middleware resolves, any error that may have occurred can be marked as handled. Fixes Added check for parentSegment in async_hooks instrumentation, to help ensure that transaction context is maintained.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-290","eolDate":"2021-02-27"},{"agent":"nodejs","date":"2018-02-21","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Note This release is deprecated due to an issue where the agent may capture transaction attributes regardless of agent settings. If you are using this release, upgrade your agent to agent version 2.9.1 or higher. For more information, see Security Bulletin NR18-06 . New features Added instrumentation support for MongoDB version 3. Version 3 of mongodb  is now supported. Previously datastore host information (instance metrics) was incorrectly captured by the agent with mongodb v3. This has been fixed and all features should be functional now. Improvements Updated documentation for apdex_t setting and removed environment variable. This was never configurable on client side and the documentation was misleading. Documented environment variables for slow_sql configurations. Thanks to Olivier Tassinari (@oliviertassinari) for the update! Updated hapi/hapi-pre-17/package.json to run errors.tap.js in more versions. Added internal cache to unwrapped core modules for agent use. Improved logging around environment facts gathering. Bug fixes Enable certain agent attributes when high-security mode is enabled. During the switch from the old capture_params/ignored_params to the new attribute include/exclude rules, high-security mode was over-zealous in what attributes it disallowed. This has been trimmed back to be in line with other agents.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-280","eolDate":"2021-02-21"},{"agent":"nodejs","date":"2018-02-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.7.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Changed attributes.enabled to true by default. In the previous version we defaulted this to false to maintain parity with capture_params which defaulted to false. However, this is a invalid parity because attribute.enabled controls more attributes than capture_params. Improvements Removed unnecessary checks around Timer.unref() calls. unref has been supported since Node v0.9, meaning it will always be present in timers set by the agent (with 0.10 being the earliest supported version). Added a split in the node versions for the mysql2 and cassandra versioned tests. As of mysql2 v1.3.1 and cassandra v3.4.0 the minimum supported version of Node is 4. Replaced as many instances of {} as possible with Object.create(null). Removed extraneous logger arg in addCustomAttribute call. Bug fixes The agent will no longer generate browser data for ignored transactions. Expanded Hapi instrumentation to support route pre handlers . This is a Hapi route config option that was previously uninstrumented, causing transaction names to become invalid. This expanded instrumentation ensures that all additional handlers are wrapped and associated with the main route.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-271","eolDate":"2021-02-07"},{"agent":"nodejs","date":"2018-02-01","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added agent attribute filtering via include and exclude rules. Agent attributes  can now be controlled using fine grained include and exclude rules. These rules, described below, replace capture_params and ignored_params. Any attributes listed in ignored_params will be migrated to attributes.exclude internally, unless attributes.exclude is explicitly set. There are three new configuration properties added to the root config and each destination (more on destinations later). These new configurations are: attributes.enabled - Enables collection of attributes for the destination. attributes.include - A list of attributes or wildcard rules to include. attributes.exclude - A list of attributes or wildcard rules to exclude. The include and exclude rules can be exact rules (for example request.headers.contentLength), or wildcard rules which match just the beginning of attribute keys (for example request.headers.* would match any request header). These rules can be specified globally at the root of the configuration, or for specific destinations. These destinations are: transaction_tracer - Controls transaction trace attributes. transaction_events - Controls transaction event attributes. error_collector - Controls error event attributes. browser_monitoring - Controls browser/RUM transaction attributes. Renamed addCustomParameter to addCustomAttribute. The addCustomParameter method is now deprecated and will be removed in a future release of the agent. The addCustomAttribute method is a drop-in replacement for it. Added cache to agent attribute filtering. To minimize the overhead of applying attribute rules, the agent caches results of filtering specific attribute keys and destinations. The cache is limited to 1000 destination-key pairs by default but can be configured with attributes.filter_cache_limit. This cache offers a 10x improvement for applying filter rules for cache-hits. Added allow_all_headers to config options and updated http instrumentation. When set to true, the agent will collect all request headers. This collection respects the agent attribute include and exclude rules. A default set of exclusion rules are provided in newrelic.js. These rules exclude all cookies and authentication headers. Segments may now be flagged as opaque, causing internal segments to be omitted from the transaction trace. Improvements Added limits for agent attributes to keep monitoring overhead down. Attribute keys and values are limited to 255 bytes each. Keys which are larger than 255 bytes are dropped, and a warning message is logged. Values larger than 255 bytes are truncated to 255 bytes, respecting multi-byte UTF-8 encoding. Custom attributes are limited to 64 per transaction. Attributes beyond the 64th are silently ignored. Added error to collector connection failure log message. Renamed request_uri attribute to request.uri. This brings the attribute name in line with all other request attributes. Updated https-proxy-agent dependency from ^0.3.5 to ^0.3.6. Updated versioned tests where applicable to ensure most minor versions of instrumented modules work as expected. Fixed stalling test for v1 line of Mongo driver. Added tests verifying Hapi 404 transactions result in correctly named metrics. The Hapi instrumentation was doing the correct thing, but we did not have tests for this specific case. Bug fixes The agent will no longer crash when crypto.DEFAULT_ENCODING has been changed. Previously, the agent would assume the result of hash.digest() was an instance of a Buffer. If crypto.DEFAULT_ENCODING is changed, hash.digest() will return a string and the agent would crash. The agent now ensures that the value is a Buffer instance before moving on. Fixed error if process.config.variables.node_prefix missing. If process.config.variables.node_prefix is falsey (which can happen if using electron, leading to this issue https://support.newrelic.com/s/hubtopic/aAX8W0000008ZMO/new-relic-on-electron-nodejs ) the getGlobalPackages function in lib/environment.js will give an err when it shouldn't. Thanks to Jarred Filmer (@BrighTide) for the fix!","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-270","eolDate":"2021-02-01"},{"agent":"nodejs","date":"2018-01-18","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.6.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added regression test for promise instrumentation and stack overflows. Bug fixes Fixed naming bug in Restify instrumentation regarding parameters to next. The instrumentation previously considered any truthy value passed to next to be an error. It is possible to pass a string or boolean to next in Restify to control further routing of the request. This would cause the middleware's mounting path to be erroneously appended to the transaction name. Fixed access to bluebird.coroutine.addYieldHandler. This was accidentally not copied by our instrumentation making access to the function fail. This has been resolved and tests expanded to ensure no other properties were missed.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-261","eolDate":"2021-01-18"},{"agent":"nodejs","date":"2018-01-10","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added transaction_tracer.hide_internals configuration. This configuration controls the enumerability of the internal properties of the agent. Making these properties non-enumerable can have an impact on the performance of the agent. Disabling this option may decrease agent overhead. Improvements Refactored promise instrumentation. This new instrumentation is far more performant than the previous and maintains a more sensible trace structure under a wider range of sequences. Added concurrent environment scanning, limited to 2 reads at a time. This improves the performance of dependency scanning at agent startup, allowing the agent to connect to our services more quickly. Refactored instrumentation tests to run against wide range of module versions. Instrumentation tests will be run against all supported major versions of every instrumented module. For releases, we will test against every supported minor version of the modules. This vastly improves our test coverage and should reduce the instances of regressions for specific versions of modules. Added tests for all  of bluebird's promise methods. These tests ensure that we 100% instrument bluebird. Some gaps in instrumentation were found and fixed. Anyone using bluebird should upgrade. Bug fixes Fixed a crashing error in the hapi instrumentation. When recording the execution of an extension listening to a server event (for example, 'onPreStart') the agent would crash due to the lack of a raw property on the first argument passed to the extension handler. The agent now checks the event before wrapping the extension handler and checks for the existence of the raw property before attempting to dereference off of it. Fixed an incompatibility with the npm module mimic-response. The agent's HTTP instrumentation previously did not play well with the way mimic-response copied properties from an http.IncomingMessage. This caused modules that relied on that process, such as got, to hang. Fixed naming rule testing tool to use same url scrubbing as the agent itself.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-260","eolDate":"2021-01-10"},{"agent":"nodejs","date":"2017-05-03","downloadLink":"https://www.npmjs.com/package/@newrelic/beta-agent","version":"2.6.0-beta","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Dropped support for Express <4.6. New features Improved API for writing web framework instrumentation. Introduced a new WebFrameworkShim class for writing instrumentation. This shim can be accessed using the newrelic.instrumentWebframework API method. Improvements Incorporated fixes and features from 1.38.0, 1.38.1, and 1.38.2. Only one transaction is created for each request emitted by a server. Previously we created a transaction for each listener  on the request event. Fixed the beta sign up link in the README.md. Rewrote instrumentation for Connect, Director, Express, Hapi, and Restify. These instrumentations were rewritten using the new WebFrameworkShim. As a consequence of this rewrite, all our instrumentations now have feature parity, meaning every instrumentation will create Middleware metrics for your server. Tutorials on using the new instrumentation shim can be found on our API docs: http://newrelic.github.io/node-newrelic/ . Removed express_segments feature flag. This configuration previously controlled the creation of middleware metrics in our Express instrumentation. With the move to the WebFrameworkShim this was dropped.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-260-beta","eolDate":"2020-05-03"},{"agent":"nodejs","date":"2018-01-03","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added hapi v17 instrumentation Hapi v17 added support for promise-based middleware which broke transaction tracking in the agent. This caused issues in naming, as the agent will name the transaction after the path to the middleware that responded to a request. Added instrumentation for vision@5 Due to the way vision is mounted to the hapi server when using hapi v17.x, the agent's instrumentation would not pick up on the middleware being mounted. This new instrumentation now correctly times rendering done in the vision middleware. Added unwrapOnce method to shim object This new method can be used to unwrap a single layer of instrumentation. unwrapOnce is useful in cases where multiple instrumentations wrap the same method and unwrapping of the top level is required. Added isErrorWare checks around nameState.appendPath/nameState.popPath calls to avoid doubling up paths in transaction names Previously, the agent would append its transaction name with the path fragment where an error handler middleware was mounted. The extraneous path fragment will now be omitted, and the transaction will be named properly after the middleware that threw the error. Added support for pg 6 on Node 5 or higher Improvements Added parent property to webframework-shim segment description Refactored existing hapi instrumentation for different server.ext() invocations Refactored webframework-shim _recordMiddleware to construct different segment descriptions for callback- or promise-based middleware Updated node-postgres@^6 versioned tests to avoid deprecation warning on direct module connect and end calls Fixed running domain tests on Node 9.3.0. Improved logging for CAT headers and transaction name-state management. All json-safe-stringify calls now wrapped in try/catch Removed lib/util/safe-json Bug fixes Fixed creating supportability metric when mysql2 goes uninstrumented. Added a segmentStack.popto the middleware after in cases when an error is caught and there is no next handler Fixed determining parents for middleware segments when transaction state is lost and reinstated Added check to _recordMiddleware to avoid prepending a slash if original route is an array Changed logic in http instrumentation to attach response.status to the transaction as a string Updated startWebTransaction and startBackgroundTransaction to add nested transactions as segments to parent transactions","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-250","eolDate":"2021-01-03"},{"agent":"nodejs","date":"2017-02-22","downloadLink":"https://www.npmjs.com/package/@newrelic/beta-agent","version":"2.5.0-beta","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added support for recording interfaces that return promises instead of taking callbacks. See RecorderSpec.promise for more details. Thanks to Gert Sallaerts (@Gertt) for this contribution. Improvements Incorporated fixes and features from 1.36.2, 1.37.0, and 1.37.1. Domains are no longer preemptively instrumented, thus applications that do not use domains will not load the domain module. Including the domain module causes a small amount of extra overhead in other core libraries that must keep the domain state set correctly.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-250-beta","eolDate":"2020-02-22"},{"agent":"nodejs","date":"2017-12-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.4.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Added Peter Svetlichny to the contributors list! Improvements Optimized NameState#getPath. Optimized shim.record. Optimized shim.recordMiddleware. Upgraded eslint to v4. Bug fixes Fixed parsing SQL for queries containing newlines.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-242","eolDate":"2020-12-12"},{"agent":"nodejs","date":"2017-11-28","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.4.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added promise benchmarks to test non-async_hooks instrumentation. Added logging for external calls made outside of a transaction. Added logging for when unhandledRejection is noticed. Improved performance of creating and merging metrics. Improved performance of tracer.bindFunction. Removed try-catch around internal property setting on older versions of Node. Bug fixes Moved require calls for vendor metadata to module-level.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-241","eolDate":"2020-11-28"},{"agent":"nodejs","date":"2017-11-15","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Instrumentation will now only modify the arity of wrapped functions when needed. This can be controlled with the matchArity property on a WrapSpec. Disabling arity matching has a significant, positive impact on the performance of instrumentation. Improvements Added benchmarks for shimmer methods. Pinned hapi tests at v16 due to incompatibility in hapi v17 with Node.js versions <8. The agent's parsed queries will now only hold onto the stack that the query was made at, instead of an error object instance. Previously, the parsed query objects would hold onto an error instance, which would in turn hold onto references to all the functions in the stack when the error was created. This could cause memory issues if the functions were holding onto references to other pieces of data. Bug fixes Revert wrapping of https for Node ^8.9.1. The original cause for this problem was reverted by Node.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-240","eolDate":"2020-11-15"},{"agent":"nodejs","date":"2017-01-25","downloadLink":"https://www.npmjs.com/package/@newrelic/beta-agent","version":"2.4.0-beta","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Rewrote the cassandra-cql and memcached instrumentations using the DatastoreShim. Improved instrumentation matching. Previously, the agent would determine which instrumentation would run for a given module being loaded using the basename of the file path. This lead to false positives (e.g. myapp/lib/express.js would trigger the express instrumentation) which we previously just ignored. Matches are now determined using the string passed to require. This means you can now match local relative paths (./lib/something) as well as package-relative paths (amqplib/callback_api).","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-240-beta","eolDate":"2020-01-25"},{"agent":"nodejs","date":"2017-11-02","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.3.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added Node 9 to test suite. Removed problematic tests for ancient version of Hapi (7.1). Document purpose of throw in tracer to prevent developer confusion. Added script for running agent micro benchmarks. Added benchmarks for all the Shim and Tracer methods. Bug fixes Fixed a bug with Node >=8.9 that prevented https externals from being recorded.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-232","eolDate":"2020-11-02"},{"agent":"nodejs","date":"2017-10-24","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Agent will attempt to reconnect to the collector forever after backing off to 5 minute delays. Bug fixes Refactored environment scan to improve startup time and fix cyclical symlink resolving.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-231","eolDate":"2020-10-24"},{"agent":"nodejs","date":"2017-01-12","downloadLink":"https://www.npmjs.com/package/@newrelic/beta-agent","version":"2.3.1-beta","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Incorporated fixes from 1.36.1","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-231-beta","eolDate":"2020-01-12"},{"agent":"nodejs","date":"2017-10-16","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features The agent will now support the Node 8 await keyword by default . Improvements Added benchmark for performance of function wrapping. Added Garbage Collection information to async_hooks benchmark. Improved trace-level logging for capturing queries. Added cases for omitting the agent with and without async hooks to the async hooks microbenchmark. Bug fixes Pinned version of Mocha to 3.x due to the incompatibility of Mocha v4 and Node v0.10 and v0.12.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-230","eolDate":"2020-10-16"},{"agent":"nodejs","date":"2017-01-05","downloadLink":"https://www.npmjs.com/package/@newrelic/beta-agent","version":"2.3.0-beta","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features The @newrelic/native-metrics module is now an optional dependency of the agent. Now npm will attempt to install the module when the agent is installed. If it fails for whatever reason, the agent itself will still be installed correctly and the rest of the npm install will finish normally. Improvements Incorporated new features and fixes from 1.34.0, 1.35.1, and 1.36.0","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-230-beta","eolDate":"2020-01-05"},{"agent":"nodejs","date":"2017-09-26","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.2.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Hapi handlers will now preserve the defaults associated with them. Previously when wrapping handlers, the agent would drop the associated defaults on the ground, these are now properly forwarded to the wrapper. Big thanks to Sean Parmelee (@seanparmelee) for finding the root cause of this bug and reporting it! Fixed starting the agent with an invalid process version. Pinned request version for testing old versions of Node. Added tests for feature flags created at agent initialization.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-222","eolDate":"2020-09-26"},{"agent":"nodejs","date":"2017-09-11","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.2.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Added metrics for enabled/disabled feature flags. Bug fixes Fixed transaction naming for Hapi plugins. Thanks to Marc Höffl (@KeKs0r) for providing a reproduction!","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-221","eolDate":"2020-09-11"},{"agent":"nodejs","date":"2017-08-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added support for ignoring ranges of status codes. The configuration error_collector.ignore_status_codes can now take ranges of numbers. For example, ignore_status_codes: ['400-404'] would ignore 400, 401, 402, 403, and 404. Experimental instrumentation for async/await This is experimental instrumentation and has not yet been tested in a wide array of production environments. The feature is currently off by default behind a feature flag. To enable this experimental instrumentation, add await_support: true to the feature_flag setting in your agent config file. Improvements Updated examples and documentation regarding custom transaction creation. All examples and documentation now point at the newrelic.start*Transaction methods. Transaction state is now maintained in ChildProcess event listeners. Reducing logging verbosity in the SQL query obfuscator. Bug fixes Fixed a bug when a custom collector port was provided in the configuration that prevented redirected connections from working. Fixed a bug in Shim#record that could cause an exception when trying to create a new segment as part of an ended/inactive transaction. Fixed issue with custom Hapi handlers causing an error. Previously custom Hapi handlers defined using the server.handler() method were causing the Hapi server to return a 500 error. Now they are correctly handled and recorded as middleware functions.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-220","eolDate":"2020-08-23"},{"agent":"nodejs","date":"2016-11-09","downloadLink":"https://www.npmjs.com/package/@newrelic/beta-agent","version":"2.2.0-beta","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Incorporated new features and fixes from v1.30.4, v1.30.5, v1.31.0, v1.32.0, and v1.33.0.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-220-beta","eolDate":"2019-11-09"},{"agent":"nodejs","date":"2016-09-16","downloadLink":"https://www.npmjs.com/package/@newrelic/beta-agent","version":"2.1.1-beta","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Incorporated fixes from v1.30.1, v1.30.2, and v1.30.3.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-211-beta","eolDate":"2019-09-16"},{"agent":"nodejs","date":"2017-08-08","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Improved metadata collection for AWS, Azure, GCE, and Pivotal Cloud Foundry. Bug fixes Fixed a bug in PG query obfuscation for $ placeholders. The agent used to mis-detect $1 value placeholders as unmatched dollar-quoted strings causing the whole query to be obfuscated to just ?. These placeholders are now correctly detected and obfuscated.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-210","eolDate":"2020-08-08"},{"agent":"nodejs","date":"2016-08-29","downloadLink":"https://www.npmjs.com/package/@newrelic/beta-agent","version":"2.1.0-beta","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes You must read and agree to the Beta Agreement  before using this beta version of the agent. New features Added rowCallback property to datastore segment descriptors. With this parameter the shim will record the given function/parameter as a per-row callback which may be called multiple times. These calls will be counted up for traces. Improvements Incorporated fixes from v1.30.0 Rewrote PostgreSQL instrumentation using new DatastoreShim class. Reversed reverse_naming_rules default. Naming rules now default to evaluating in forward order.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-210-beta","eolDate":"2019-08-29"},{"agent":"nodejs","date":"2017-08-01","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.0.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Improved documentation for newrelic.start*Transaction and TransactionHandle. Formatting for the startWebTransaction and startBackgroundTransaction methods was fixed and documentation for the TransactionHandle class which getTransaction returns was added. Bug fixes Fixed parsing the table name from SQL queries. Quotes around the table name are now stripped after parsing the query and before constructing the metrics. Fixed unhandled rejection error caused by ioredis instrumentation.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-202","eolDate":"2020-08-01"},{"agent":"nodejs","date":"2017-07-25","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed issue with transaction events not including correct duration values. This issue was introduced in v2.0.0, and it has affected web transactions histogram and percentile charts. Fixed issue with Redis instrumentation causing the agent to crash in some cases. Previously, the Redis instrumentation would crash the agent when Redis commands were called without a callback and after the transaction has ended. Fixed issue with the agent crashing on Node v4.0-4.4 and v5.0-5.9. This issue was caused by incorrect shim for Buffer.from(), and it affected older minor versions of Node v4 and v5.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-201","eolDate":"2020-07-25"},{"agent":"nodejs","date":"2017-07-18","downloadLink":"https://www.npmjs.com/package/newrelic","version":"2.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The New Relic Node Agent v2 is here! This release contains major changes to the agent instrumentation API, making it easier to create and distribute your own instrumentation for third party modules. Check out Upgrade the Node agent  or the Migration Guide  for more information on upgrading your application to this version. BREAKING: Reversed naming and ignore rules. Naming rules are now applied in the order they are defined. BREAKING: De-duplicated HTTP request transactions. Only one transaction is created per request event emitted by an HTTP server. Previously this was one transaction per listener per event emitted. BREAKING: Stopped swallowing outbound request errors. Errors emitted by outbound HTTP requests will no longer be swallowed by the agent. BREAKING: Node v0.8 is no longer supported. Minimum version is now v0.10. The v1 agent will continue to support Node 0.8 but will no longer receive updates. BREAKING: npm v1 is no longer supported. Minimum version is now v2.0.0. New features Added API for writing messaging framework instrumentation. Introduced new MessageShim class for writing instrumentation. This shim can be accessed using the newrelic.instrumentMessages() API method. Added amqplib instrumentation. Applications driven by amqplib consumers will now have transactions automatically created for consumed messages. See Troubleshoot message consumers  for more information on this instrumentation and its limitations. Advanced instrumentation API is now generally available. New methods for instrumenting common modules were introduced during the Agent v2 beta. These APIs are now available to everyone: newrelic.instrument()/Shim: This method can be used to instrument generic modules, such as connection pooling libraries, task schedulers, or anything else not covered by a specialized class. newrelic.instrumentDatastore()/DatastoreShim: This method is good for instrumenting datastore modules such as mongodb, mysql, or pg. newrelic.instrumentWebframework()/WebFrameworkShim: This method is used for instrumenting web frameworks like restify or express. Documentation and tutorials for the new API can be found on our GitHub documentation page: http://newrelic.github.io/node-newrelic/ Improvements Rewrote built-in instrumentation using the new Shim classes. The following instrumentations have been rewritten: Datastores cassandra-driver ioredis memcached mongodb mysql node-cassandra-cql pg redis Web frameworks director express hapi restify The @newrelic/native-metrics module is now included as an optional dependency. This module will be installed automatically with Agent v2. If it fails to install the agent will still function.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-200","eolDate":"2020-07-18"},{"agent":"nodejs","date":"2016-08-04","downloadLink":"https://www.npmjs.com/package/@newrelic/beta-agent","version":"2.0.0-beta","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes You must read and agree to the Beta Agreement  before using this beta version of the agent. Dropped support for Node.js 0.6 and 0.8 as well as node-mysql package versions < 1.0.0. New features Improved API for writing instrumentation. Introduced new classes for writing instrumentation, Shim and DatastoreShim. These classes along with the new newrelic.instrument and newrelic.instrumentDatastore methods make writing 3rd party instrumentation much easier. Rewrote instrumentation for Cassandra, Redis, ioredis, MySQL, and MongoDB. These instrumentations were rewritten using the new DatastoreShim interface. Their functionality is largely unchanged but the new code should be easier to maintain and extend. Added public API documentation. Documentation for the New Relic agent API has been generated using JSDoc and is now hosted on GitHub at https://newrelic.github.io/node-newrelic . There you can find documentation on the new classes as well as the pre-existing API methods.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-200-beta","eolDate":"2019-08-04"},{"agent":"nodejs","date":"2014-08-08","downloadLink":null,"version":"1.9.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Fixed a bug in the express instrumentation where if you named an error handler function handle it would cause a recursion depth error.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-192","eolDate":"2017-08-08"},{"agent":"nodejs","date":"2014-07-30","downloadLink":null,"version":"1.9.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-191","eolDate":"2017-07-30"},{"agent":"nodejs","date":"2014-07-24","downloadLink":null,"version":"1.9.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-190","eolDate":"2017-07-24"},{"agent":"nodejs","date":"2014-07-18","downloadLink":null,"version":"1.8.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-181","eolDate":"2017-07-18"},{"agent":"nodejs","date":"2014-07-11","downloadLink":null,"version":"1.8.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-180","eolDate":"2017-07-11"},{"agent":"nodejs","date":"2014-07-02","downloadLink":null,"version":"1.7.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Plain http routes (i.e. routes outside of a framework) now apply config naming rules early. See rules for naming and ignoring requests . This fixes a bug where generating the Browser Timing Header  would not work without a framework (i.e. express, restify, hapi). Beta  support for connecting to newrelic via ssl through a proxy.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-175","eolDate":"2017-07-02"},{"agent":"nodejs","date":"2014-06-26","downloadLink":null,"version":"1.7.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-174","eolDate":"2017-06-26"},{"agent":"nodejs","date":"2014-06-20","downloadLink":null,"version":"1.7.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-173","eolDate":"2017-06-20"},{"agent":"nodejs","date":"2014-06-13","downloadLink":null,"version":"1.7.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-172","eolDate":"2017-06-13"},{"agent":"nodejs","date":"2014-06-05","downloadLink":null,"version":"1.7.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-171","eolDate":"2017-06-05"},{"agent":"nodejs","date":"2014-05-29","downloadLink":null,"version":"1.7.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-170","eolDate":"2017-05-29"},{"agent":"nodejs","date":"2014-05-22","downloadLink":null,"version":"1.6.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 New Relic Insights support no longer requires a feature flag. If you are a paying customer, you'll begin to see data show up in Insights as soon as you upgrade to 1.6.0. The agent will send event data for every transaction up to 10,000 per minute. After that events are statistically sampled. Event data includes transaction timing, transaction name, and any custom parameters. You can read what is sent in more detail here . You can read more about Insights here . Documentation for configuring this feature can be found here .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-160","eolDate":"2017-05-22"},{"agent":"nodejs","date":"2014-05-15","downloadLink":null,"version":"1.5.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fix a bug where if the user disabled the error collector, error count would be carried over harvest cycles instead of reset. This would result in an ever increasing error count until the app was restarted. New Relic Insights beta support. This is a feature for our paying customers. The support of Insights in the agent is beta, this means we don't recommend turning the feature on in production, but instead trying it out in development and staging environments. To enable Insights support add the following to your newrelic.js:","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-155","eolDate":"2017-05-15"},{"agent":"nodejs","date":"2014-05-08","downloadLink":null,"version":"1.5.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 On connect, the full newrelic module configuration is pushed to New Relic APM. Full config will be visible under the Agent initialization  tab, under the Settings  button in the APM application page. The reported settings will reflect the running  agent config, which may differ from the newrelic.js file depending on server-side, and environmental configuration.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-154","eolDate":"2017-05-08"},{"agent":"nodejs","date":"2014-05-01","downloadLink":null,"version":"1.5.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Express 4 support. Express 4 apps now have their transactions named correctly. Errors in the middleware chain are properly recorded.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-153","eolDate":"2017-05-01"},{"agent":"nodejs","date":"2014-04-24","downloadLink":null,"version":"1.5.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Fix issue where dangling symbolic links in the node_modules folder would crash the environment scraper.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-152","eolDate":"2017-04-24"},{"agent":"nodejs","date":"2014-04-18","downloadLink":null,"version":"1.5.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Upgrade continuation-local-storage dependency to 3.0.0. The newrelic node module uses cls to help join asynchronous transaction segments. The latest cls module includes a fix that prevents contexts from leaking across transactions.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-151","eolDate":"2017-04-18"},{"agent":"nodejs","date":"2014-04-11","downloadLink":null,"version":"1.5.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Add high-security compliance for accounts with enterprise security enabled. By default, the agent now works with high-security accounts, whereas previously agents would receive an Access Violation. Add a .addCustomParameter(name, value) api call for adding custom parameters to transaction traces, and extend the .noticeError(error, customParameters) for adding additional parameters to error traces. Documentation fix in the README.md for ignoring socket.io routes. Better support for disabling browser timing headers server side. Previously the agent would not pick up the server change until restart. The agent will now disable browser timing headers as soon as the next harvest cycle. Fix a socket hangup error that was causing some agents to fail to handshake with the New Relic servers.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-150","eolDate":"2017-04-11"},{"agent":"nodejs","date":"2017-06-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.40.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Node v8 is officially supported with the exception of async/await. Support for the new async/await  keywords is coming in a future release. Until this support is added, New Relic does not support and highly discourages using the Node.js agent with applications that utilize async/await, as it could result in transaction state loss and data being mixed between transactions. Fixes Fixed issues related to changes in the core networking modules that resulted in transaction state loss. Also instrumented new asynchronous API methods in crypto and inspector .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1400","eolDate":"2020-06-07"},{"agent":"nodejs","date":"2014-03-14","downloadLink":null,"version":"1.4.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Browser monitoring! Real User Monitoring! Which is also known as RUM! Whatever it's called, it allows you to see how long your pages take to load, not just on the server side, but in the browser! Wow! It's super cool! We know a lot of you have been waiting for this, and it's here! It's manually set up with an API call! Check the README for details! By default, all communication between New Relic for Node and New Relic's servers is now protected with crisp, clean TLS encryption. To minimize the CPU overhead of running connections over SSL (and it can be configured, see the README and the online documentation for details on how to return to plain HTTP), New Relic for Node is now using a keep-alive connection that will properly pipeline connections, for both HTTP and HTTPS. Improved the timings for a large class of MongoDB / Mongoose use cases. If you've encountered the issue where MongoDB trace segments last for an absurdly long duration, this should help.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-140","eolDate":"2017-03-14"},{"agent":"nodejs","date":"2026-09-16","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.5.0","features":["Added `browser_monitoring.version` configuration option"],"bugs":["Updated `http2` instrumentation to properly inject `traceparent` header with external segment id","Updated `undici` instrumentation to not attempt to create an external segment when transaction is not active"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added browser_monitoring.version configuration option (#4269 ) (b62ca00 ) When this is set, it will pin the browser agent version when using newrelic.getBrowserTimingHeader to the version selected. If you specify a version that is no longer supported or invalid, it will not resolve to any browser agent when calling newrelic.getBrowserTimingHeader. Bug fixes Updated undici instrumentation to not attempt to create an external segment when transaction is not active (#4278 ) (d634246 ) Updated http2 instrumentation to properly inject traceparent header with external segment id (#4279 ) (ccd7800 ) Code refactoring Refactored child_process instrumentation to use tracing channel instead of Shim (#4212 ) (5a39c38 ) Refactored dns instrumentation to subscribe to events emitted (#4224 ) (c04289f ) Miscellaneous chores Regenerated agent config json schema (#4275 ) (c2107ed ) Update secret naming (#4277 ) (09f5b25 ) Tests Added legacy-peer-deps to google adk tests to avoid peer dep conflict (#4280 ) (e4a6b35 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Node.js agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-5-0","eolDate":"2027-09-16"},{"agent":"nodejs","date":"2026-09-10","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.4.0","features":["Added support for `MessageBroker/Kafka/Cluster/{cluster_id}/{Produce|Consume}/{topic_name}` metrics","Updated GCP hostname to support more Cloud Run instance types"],"bugs":["Fixed duplicated router mount path in transaction names for async middleware","Fixed otlp payload format for metrics in AWS Lambda"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for MessageBroker/Kafka/Cluster/{cluster_id}/{Produce|Consume}/{topic_name} metrics (#4263 ) (3be98f1 ) Updated GCP hostname to support more Cloud Run instance types (#4256 ) (67bfd0d ) Bug fixes Fixed duplicated router mount path in transaction names for async middleware (#4272 ) (51a3bf4 ) Fixed otlp payload format for metrics in AWS Lambda (#4270 ) (5d29078 ) (upcoming feature; not yet available) Documentation Updated compatibility report (#4273 ) (40b3172 ) (#4267 ) (b4fa928 ) (#4253 ) (9fe7038 ) Miscellaneous chores Deprecated utilization.gcp_use_instance_as_host in favor of utilization.gcp_cloud_run.use_instance_as_host (#4258 ) (450303e ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-4-0","eolDate":"2027-09-10"},{"agent":"nodejs","date":"2026-08-24","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.3.9","features":[],"bugs":["Fixed @google/adk instrumentation for v2.0.0"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Fixed @google/adk instrumentation for v2.0.0 (#4243 ) (6f850a8 ) Code refactoring Co-located Attributes and PrioritizedAttributes under lib/attributes/ (#4227 ) (c2a01d2 ) Miscellaneous chores Added workflows to generate a config schema and version before agent release (#4161 ) (56987ca ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-3-9","eolDate":"2027-08-24"},{"agent":"nodejs","date":"2026-08-19","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.3.8","features":[],"bugs":["Updated `openai` instrumentation to support `>=7.5.0`"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated openai instrumentation to support >=7.5.0 (#4228 ) (062b569 ) Performance improvements Skipped gRPC/http2 instrumentation when parent segment is opaque (#4220 ) (ed2e9f3 ) Code refactoring Include all .mjs equivalents in openai instrumentation to properly function when using ESM (#4232 ) (55c4dd9 ) Removed dead wrapNoSegment code from zlib instrumentation (#4231 ) (56207ec ) Documentation Updated compatibility report (#4225 ) (679245c ) Miscellaneous chores Improved docs and benchmarking for attributes (#4207 ) (7dbcd04 ) Tests Fixed flaky CpuProfiler and sampling-rate integration tests (#4229 ) (edfe9a6 ) Widened error margin in ratio-based-sampler flaky test (#4234 ) (ff0496e ) Continuous integration Updated child_process.exec calls to child_process.execFile in bin/npm-commands.js (#4211 ) (f07a8cd ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-3-8","eolDate":"2027-08-19"},{"agent":"nodejs","date":"2026-08-10","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.3.7","features":[],"bugs":["Fixed OTEL metrics wrapping meters too many times","Updated `getBrowserTimingHeader` to handle when a transaction may not be finalized and still return the browser agent string without transaction intrinsics","Improved Apollo server resolver instrumentation performance"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Fixed OTEL metrics wrapping meters too many times (#4216 ) (6f917ad ) Improved Apollo server resolver instrumentation performance (#4206 ) (2a394e8 ) Updated getBrowserTimingHeader to handle when a transaction may not be finalized and still return the browser agent string without transaction intrinsics (#4209 ) (fbf636b ) Performance improvements Skipped context wrapping for skipped Apollo resolver segments (#4210 ) (6bf954b ) Documentation Updated compatibility report (#4202 ) (8811cd2 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-3-7","eolDate":"2027-08-10"},{"agent":"nodejs","date":"2026-08-04","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.3.6","features":[],"bugs":["Updated `addAttribute` to only increase the attributeCount for new attributes"],"security":[],"supportedOperatingSystems":null,"description":"Bug fixes Updated addAttribute to only increase the attributeCount for new attributes (#4184 ) (f05df73 ) Documentation Updated compatibility report (#4191 ) (5b5f8ce ) Miscellaneous chores Reverted clean-jsdoc-theme to 4.x (#4192 ) (e7b3ddf ) Tests Added unit tests for bin/git-commands.js (#4199 ) (a8bb311 ) Sync cross agent tests and fix related DT assertions (#4198 ) (44388c0 ) Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Node.js agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-3-6","eolDate":"2027-08-04"},{"agent":"nodejs","date":"2026-08-03","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.3.5","features":[],"bugs":["Set `ignoreApdex` warning log to `trace`-level"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Set ignoreApdex warning log to trace-level (#4188 ) (79bac5e ) Documentation Updated compatibility report (#4176 ) (3886190 ) Miscellaneous chores Removed update-snyk-prs workflow (#4185 ) (ab7722c ) Restored scrollbar on API docs (#4181 ) (3ea46fb ) Updated all @opentelemetry deps from 0.219.0 to 0.221.0 (#4179 ) (62c3779 ) Updated conventional commit dev deps to latest (#4178 ) (f4db525 ) Updated out of date dev deps: @matteo.collina/tspl, @newrelic/eslint-config, @slack/bolt, borp, c8, clean-jsdoc-theme, lint-staged and proxyquire (#4175 ) (e978762 ) Continuous integration Added a poll npm workflow to ensure new package version exists before executing any dependent workflows (#4182 ) (224c4f9 ) Normalized how we retrieve agent version from package.json (#4183 ) (949e620 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents  up to date. See the New Relic Node.js agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-3-5","eolDate":"2027-08-03"},{"agent":"nodejs","date":"2026-07-27","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.3.4","features":["Collect OTEL metrics in AWS Lambda"],"bugs":["Updated `openai` instrumentation to cache the results of `responses.parse` chain on openai custom promises"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Collect OTEL metrics in AWS Lambda (#4166 ) (204c166 ) Feature not generally available as of 2026-07-27. A future release will enable the necessary plumbing for full functionality. Bug fixes Updated openai instrumentation to cache the results of responses.parse chain on openai custom promises (#4173 ) (35dce3c ) Documentation Fixed typos in 14.3.1 release (#4170 ) (dd84830 ) Updated compatibility report (#4165 ) (33eceac ) Miscellaneous chores Updated @apm-js-collab/tracing-hooks to 0.13.0 (#4167 ) (153acec ) Updated @octokit/rest to 22.x (#4172 ) (55d90c2 ) Updated commander to v15 and added unit tests for scripts that use it (#4168 ) (e409204 ) Tests Updated runnables-streaming.js to consume the stream on the tracking metrics tests to avoid test time outs (#4169 ) (1a132bf ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-3-4","eolDate":"2027-07-27"},{"agent":"nodejs","date":"2026-07-22","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.3.3","features":["Collect on-CPU time alongside wall time in `CpuProfiler`","Add internal OTEL API to agent"],"bugs":["Avoid unconditional @opentelemetry/core require on agent startup"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Add internal OTEL API to agent (#4147 ) (b014f82 ) Collect on-CPU time alongside wall time in CpuProfiler (#4146 ) (3b440f3 ) Bug fixes Avoid unconditional @opentelemetry/core require on agent startup (#4163 ) (f31bbe4 ) Documentation Updated compatibility report (#4160 ) (8ba64fb ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-3-3","eolDate":"2027-07-22"},{"agent":"nodejs","date":"2026-07-21","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.3.2","features":[],"bugs":["Resolved mongodb host details at operation time to support `mongodb+srv://` clients"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Resolved mongodb host details at operation time to support mongodb+srv:// clients (#4155 ) (7fd4443 ) Documentation Updated compatibility report (#4156 ) (6058cf7 ) (#4153 ) (136f65a ) Miscellaneous chores Translated OTel exception into timed event (#4151 ) (36daebe ) Tests Fixed srv-connect DNS patching across mongodb driver versions (#4158 ) (ca4a7b0 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-3-2","eolDate":"2027-07-21"},{"agent":"nodejs","date":"2026-09-01","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.3.10","features":[],"bugs":["Prevented duplicate external segments when undici negotiates HTTP/2"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Prevented duplicate external segments when undici negotiates HTTP/2 (#4251 ) (c94b81b ) Code refactoring Split BedrockResponse and BedrockCommand into Converse and InvokeModel variants (#4235 ) (8235cf5 ) Updated Claude detection logic in InvokeModelCommand (#4245 ) (b090344 ) Documentation Updated compatibility report (#4249 ) (f69eecd ) Miscellaneous chores Pinned nestjs to unblock CI (#4248 ) (44abb5d ) Tests Added type: module for @nestjs/core tests, including version 12 (#4252 ) (7971d05 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-3-10","eolDate":"2027-09-01"},{"agent":"nodejs","date":"2026-07-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.3.1","features":[],"bugs":["Handled `$0` as a replacement in a metric normalization rule to return the matched string in its entirety"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Handled $0 as a replacement in a metric normalization rule to return the matched string in its entirety (#4150 ) (b57fcc8 ) Documentation Updated compatibility report (#4137 ) (3c1a2b3 ) Miscellaneous chores Attached serverless mode config to agent instance (#4140 ) (7a3592f ) Removed dead otlp_endpoint config option (#4142 ) (05b072f ) Continuous integration Reverted CI schedules to previous schedules (#4139 ) (b6f8708 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-3-1","eolDate":"2027-07-20"},{"agent":"nodejs","date":"2026-07-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.3.0","features":["Added source mapping support to heap profiler","Added source mapping support to CPU (wall time) profiler","Added `otlp_resource_attributes` to all outgoing OpenTelemetry metrics calls","Added support for `ai_monitoring.enabled`,`ai_monitoring.streaming.enabled`, and `ai_monitoring.record_content.enabled` to be assigned via server-side config"],"bugs":["Fixed OTEL crash when adding exceptions to spans","Fixed `bunyan` log forwarding multiple duplicate lines"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added source mapping support to heap profiler (#4122 ) (dcee39f ) Added source mapping support to CPU (wall time) profiler (#4095 ) (f6123bc ) Added otlp_resource_attributes to all outgoing OpenTelemetry metrics calls (#4128 ) (a0c1c5b ) Added support for ai_monitoring.enabled,ai_monitoring.streaming.enabled, and ai_monitoring.record_content.enabled to be assigned via server-side config (#4123 ) (c4d8032 ) Bug fixes Fixed bunyan log forwarding multiple duplicate lines (#4132 ) (b0f4242 ) Fixed OTEL crash when adding exceptions to spans (#4130 ) (508542e ) Documentation Updated compatibility report (#4125 ) (405b59b ) (#4107 ) (267a964 ) Miscellaneous chores Changed notify-release.yml schedule with our bot user (#4135 ) (a9318ae ) Changed versioned-security-agent.yml schedule with our bot user (#4134 ) (d7c6f64 ) Changed smoke-test schedule with our bot user (#4133 ) (400268e ) Sharded the versioned tests w/ security agent workflow (#4119 ) (fe200c4 ) Updated test runner to accept suites as positional parameters (#4117 ) (ac0985d ) Tests Added more scenarios to winston for constructing loggers (#4120 ) (ea90fc3 ) Added skip for winston test for ranges that do not support it (#4121 ) (e75e15e ) Applied sampling to pg-native tests to reduce the matrix under test (#4124 ) (b1ad2da ) Fixed flaky amqplib async-work duration assertions (#4118 ) (3544237 ) Removed timing race from common.request unit tests (#4113 ) (b22c25b ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-3-0","eolDate":"2027-07-14"},{"agent":"nodejs","date":"2026-07-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.2.1","features":[],"bugs":["Updated `winston` instrumenting to assign `handleExceptions` to the first NrTransport to avoid registering duplicate `uncaughtException` handlers"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated winston instrumenting to assign handleExceptions to the first NrTransport to avoid registering duplicate uncaughtException handlers (#4108 ) (d60a48d ) This would create a linear memory leak because the NrTransport objects for loggers no longer in use, would not be freed because of the global process.on('uncaughtException') handler Documentation Updated compatibility report (#4099 ) (058fde6 ) Continuous integration Pinned CI npm to 11 so native versioned suites build on Node 22 (#4114 ) (b844e94 ) Removed the 8 minute versioned shard timeout (#4111 ) (0ef6374 ) Attempted to fix memcached CI issue again (#4098 ) (f67fef5 ) Shard versioned tests across CI runners (#4101 ) (1471734 ) Tests Added samples to prisma and next to cut down on versions under test on packages we recommend using hybrid ageninstrumentation (#4112 ) (7d8bd7c ) Resolved grpc proto-loader from the running suite's node_modules (#4110 ) (5b5a9f8 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-2-1","eolDate":"2027-07-09"},{"agent":"nodejs","date":"2026-07-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.2.0","features":["Added Node.js 26 support","Added `span_id` and `trace_id` labels to `CpuProfiler` sample data","Added new GCP Cloud Run hostname logic to include `K_REVISION`","Added `profiling.source_mapping.enabled` config option","Removed `spanId` in outgoing `tracestate` header"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added Node.js 26 support (#4084 ) (4a7f777 ) Added span_id and trace_id labels to CpuProfiler sample data (#4049 ) (c2b1737 ) Added new GCP Cloud Run hostname logic to include K_REVISION (#4069 ) (02855dc ) Added profiling.source_mapping.enabled config option (#4090 ) (43add80 ) Removed spanId in outgoing tracestate header (#4091 ) (40a8bf1 ) Code refactoring Refactored mongodb instrumentation to subscribe to events emitted (#4059 ) (d2777ba ) Documentation Updated compatibility report (#4078 ) (047a063 ) Miscellaneous chores Addressed long standing CI flakes (#4093 ) (ae973a0 ) Fixed package version resolution on Node 26 (#4094 ) (73d14a9 ) Continuous integration Updated release-creation to use lts/* for node-version (#4080 ) (7eaed22 ) Updated setup-node job to include check-latest to ensure we are getting the latest version of node (#4079 ) (4a425f6 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-2-0","eolDate":"2027-07-07"},{"agent":"nodejs","date":"2026-06-25","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.1.2","features":[],"bugs":["Fixed Azure functions crashing when they include response headers"],"security":[],"supportedOperatingSystems":null,"description":"Bug fixes Fixed Azure functions crashing when they include response headers (#4070 ) (c88d2b7 ) Documentation Updated compatibility report (#4067 ) (0ae24b8 ) Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Node.js agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-1-2","eolDate":"2027-06-25"},{"agent":"nodejs","date":"2026-06-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.1.1","features":[],"bugs":[],"security":["Updated min version of `@opentelemetry` `0.x` packages to `^0.219.0`"],"supportedOperatingSystems":null,"description":"Notes Documentation Removed outdated Next.js documentation in repo (#4060 ) (185bb66 ) Updated compatibility report (#4047 ) (25cbd38 ) Miscellaneous chores Added proxy config support to OTEL metrics (#4041 ) (6c04b8a ) Added supportability metrics to OTEL metrics export (#4051 ) (db6e4e3 ) Updated min version of @opentelemetry 0.x packages to ^0.219.0 (#4065 ) (3f58ad0 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-1-1","eolDate":"2027-06-23"},{"agent":"nodejs","date":"2026-06-02","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.1.0","features":["Added support for native Next.js OTEL instrumentation via the Hybrid Agent"],"bugs":["Updated label parser to handle empty values in an object key"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for native Next.js OTEL instrumentation via the Hybrid Agent (#4040 ) (1944f39 ) Bug fixes Updated label parser to handle empty values in an object key (#4004 ) (73c00d7 ) Code refactoring Migrate @hapi/hapi and @hapi/vision to subscriber-based (#3995 ) (54c60a8 ) Refactored koa instrumentation to subscribe to events emitted (#4016 ) (e1f6c27 ) Updated MiddlewareWrapper maybeHandleError to only mark error as handled if there was a previously stored error (#4032 ) (1b21cc8 ) Documentation Removed linked to @newrelic/apollo-server-plugin as instrumentation was merged into agent (#4003 ) (9afd9cb ) Moved apollo-server docs to the docs website (#3994 ) (11ca2ae ) Updated compatibility report (#4028 ) (b16ad6e ) (#4014 ) (3efa1ff ) (#4002 ) (33a8236 ) Miscellaneous chores Deprecate instrumentLoadedModule API (#4034 ) (306ff86 ) Added audit logging for OTEL metrics (#4018 ) (494c836 ) Added OTEL rule to support Prisma 7 (#4013 ) (c142c60 ) Fix ordering of OTEL rules (#4025 ) (150476a ) Refactored OTEL transform rules (#3999 ) (48ff739 ) Fixed node-version in CI workflow (#4042 ) (dd05ea9 ) Updated codecov action (#4039 ) (31b9c84 ) Updated remote-method to use audit method of logger (#4038 ) (0e4507e ) Added baseline instructions for Claude bot (#4036 ) (c8f6649 ) Updated dependencies Removed unused dev dependencies (#4005 ) (e00f7d3 ) Updated @apm-js-collab/tracing-hooks to 0.9.1 (#4043 ) (f05e5d4 ) Updated commander to latest (#4021 ) (83b1d58 ) Updated nock to latest (#4022 ) (9bf79ab ) Updated sinon to latest (#4020 ) (0ced304 ) Updated protobufjs to latest (#4006 ) (45c61f3 ) Upgraded glob to 13 (#4008 ) (3053545 ) Upgraded got and rimraf to latest (#4007 ) (b967593 ) Tests Add stable http.request shim so AWS test agent setup works with smithy >=4.7.3 (#4010 ) (c5fd80a ) Added an undici versioned test to assert behavior with using a self signed cert and undici.Agent (#4026 ) (27507bc ) Refactor mongodb-esm tests to test >=4.1.4 (#4023 ) (d85767f ) Removed reliance on glob in lieu of fs.glob (#4019 ) (204f124 ) Updated undici.Agent versioned test to skip using custom dispatcher on versions <5.2.0 as it was not supported (#4029 ) (08cd079 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-1-0","eolDate":"2027-06-02"},{"agent":"nodejs","date":"2026-05-18","downloadLink":"https://www.npmjs.com/package/newrelic","version":"14.0.0","features":["Dropped support for Node.js 20","Updated minimum supported version of `@nestjs/cli` and `@nestjs/core` to `10.0.0`","Updated minimum supported version of `next` to 14","Updated minimum supported version of `bluebird` to `3.0.0`","Updated minimum supported version of `mysql2` to `3.0.0`","Updated minimum supported version for `cassandra-driver` to `4.0.0`","Removed instrumentation for `koa-route`","Removed `shim.prefixRouteParameters` as the logic was previously moved to when a transaction ends","Dropped support for `fastify` 3.x","Removed creating `MySQL Pool#query` segments","Removed instrumentation for `koa-router`","Removed Cross Application Tracing(CAT) functionality","Removed support for License, Application, and Security Policies(LASP)","Removed `shim.argsToArray`","Updated `config.distributed_tracing.exclude_newrelic_header` to be set to `true` by default","Migrated `@apollo/sever` instrumentation from a plugin(`@newrelic/apollo-server-plugin`) to traditional instrumentation"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes ⚠ BREAKING CHANGES This version of the Node.js agent is a SemVer MAJOR update and contains the following breaking changes. MAJOR versions may drop support for language runtimes that have reached End-of-Life according to the maintainer. Additionally, MAJOR versions may drop support for and remove certain instrumentation. For more details on these changes please see the migration guide . Dropped support for Node.js 20 Migrated @apollo/sever instrumentation from a plugin(@newrelic/apollo-server-plugin) to traditional instrumentation Removed Cross Application Tracing(CAT) functionality Removed support for License, Application, and Security Policies(LASP) Removed instrumentation for koa-route Removed instrumentation for koa-router Removed shim.prefixRouteParameters as the logic was previously moved to when a transaction ends Removed creating MySQL Pool#query segments Removed shim.argsToArray Updated minimum supported version of @nestjs/cli and @nestjs/core to 10.0.0 Updated minimum supported version of next to 14 Updated minimum supported version of bluebird to 3.0.0 Updated minimum supported version of mysql2 to 3.0.0 Updated minimum supported version for cassandra-driver to 4.0.0 Dropped support for fastify 3.x Updated config.distributed_tracing.exclude_newrelic_header to be set to true by default Features Dropped support for fastify 3.x (#3980 ) (720979b ) Dropped support for Node.js 20 (#3980 ) (5306223 ) Migrated @apollo/sever instrumentation from a plugin(@newrelic/apollo-server-plugin) to traditional instrumentation (#3980 ) (736e0a4 ) Removed shim.argsToArray (#3980 ) (9183d29 ) Removed shim.prefixRouteParameters as the logic was previously moved to when a transaction ends (#3980 ) (9f1408e ) Removed creating MySQL Pool#query segments (#3980 ) (1d5a6dd ) Removed Cross Application Tracing(CAT) functionality (#3980 ) (a87ed4d ) Removed instrumentation for koa-route (#3980 ) (40c10d9 ) Removed instrumentation for koa-router (#3980 ) (038ecc7 ) Removed support for License, Application, and Security Policies(LASP) (#3980 ) (bc09485 ) Updated config.distributed_tracing.exclude_newrelic_header to be set to true by default (#3980 ) (774ce08 ) Updated minimum supported version for cassandra-driver to 4.0.0 (#3980 ) (419337a ) Updated minimum supported version of @nestjs/cli and @nestjs/core to 10.0.0 (#3980 ) (120e6de ) Updated minimum supported version of bluebird to 3.0.0 (#3980 ) (369f920 ) Updated minimum supported version of mysql2 to 3.0.0 (#3980 ) (2861406 ) Updated minimum supported version of next to 14 (#3980 ) (80c5c0c ) Code refactoring Updated how exclusive time and trace total time is calculated (#3980 ) (b227ed6 ) Updated instances of tracer.bindFunction with tracer.runInContext to improve performance in hot paths (#3811 ) (5d77085 ) Documentation Updated compatibility report (#3990 ) (f3bb380 ) Miscellaneous chores Removed husky in lieu of git hooks, added security hardened options to npm install (#3988 ) (e3a7dda ) Updated production dependencies to the latest (#3996 ) (b710bac ) Tests Added minSupported to the nest js versioned tests package.json to ensure the compatibility report will show we support @nestjs/core (#3982 ) (bfa4aa1 ) Added prisma 7 tests (#3980 ) (116ee9c ) Moved versioned test runner code from @newrelic/test-utilties to agent (#3980 ) (d4f9a0c ) Removed @newrelic/test-utilities (#3980 ) (1751147 ) Decrease smoke-like esm tests' sample size (#3986 ) (40669fb ) Fixed test/lib/get-package-version.js (#3993 ) (5d31f08 ) Fixed version lookup issue in aws-sdk-v3 tests (#3992 ) (7be3f4a ) Restructure aws-sdk-v3 test runner to use groupedDependencies (#3984 ) (fc67490 ) Updated a few versioned test stanzas to reduce the number of combinations it runs (#3991 ) (d606305 ) Continuous integration Added contents: write to post-release to allow commit/push of api docs (#3978 ) (90c4e61 ) Updated remaining actions so they are running on Node 24 (#3980 ) (ea21934 ) Updated version of actions/download-artifact to v8 (#3980 ) (54a58b9 ) Updated versions of actions to ensure they are running on node 24 (#3980 ) (6302002 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-14-0-0","eolDate":"2027-05-18"},{"agent":"nodejs","date":"2017-05-11","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.39.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed a transaction state loss introduced in Node 7.10.0 when using net.createConnection. Added a new segment for net.connect, net.createConnection, and http.Agent#createConnection. Sockets created within a transaction also have their emit bound to the segment. Fixed a typo about the name of the default configuration file. Thanks Jacob LeGrone (@jlegrone)!","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1391","eolDate":"2020-05-11"},{"agent":"nodejs","date":"2017-05-02","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.39.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Error messages are redacted in High-security mode now. New configurations were added for disabling some New Relic API methods. These default to enabled and are all disabled in High-security mode. api.custom_parameters_enabled controls newrelic.addCustomParameters() api.custom_events_enabled controls newrelic.recordCustomEvent() api.notice_error_enabled controls newrelic.noticeError() Updated the default value for transaction_tracer.record_sql to obfuscated. This value was previously off by default. This change brings the New Relic Node Agent defaults in line with other New Relic Agents. Bug fixes Our when instrumentation better detects when a module is actually when. Thanks to Pasi Eronen (@pasieronen) for the contribution! Quiet a warning in our native promise instrumentation on Node 0.10. Fixed a bug in the generic pool instrumentation affecting version 3.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1390","eolDate":"2020-05-02"},{"agent":"nodejs","date":"2017-03-30","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.38.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes When.js hooks similar to Promise.onPotentiallyUnhandledRejection now function as intended. Previously, hooks like Promise.onPotentiallyUnhandledRejection would not work due to the way the agent wraps the promise constructor. When.js expects these handles to be assigned directly onto the promise constructor, and our wrapper was intercepting the assignment. The wrapper will now properly proxy these values and assign them onto the original constructor, restoring the proper behavior. Express route parameters will now be properly attached to the corresponding transaction. Previously, our express instrumentation would read the route parameters and place them on the segment responsible for matching the parameters. This behavior did not place the parameters on the transaction that the segments belonged to, causing the parameters to not show up properly on transaction traces and transaction events.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1382","eolDate":"2020-03-30"},{"agent":"nodejs","date":"2017-03-17","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.38.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed issue with when.js instrumentation not preserving all properties on wrapped Promise constructor. Previously, the when.js instrumentation would cause an unhandled exception when private methods on the Promise constructor were called (e.g. when adapting functions that do not use promises).","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1381","eolDate":"2020-03-17"},{"agent":"nodejs","date":"2017-03-16","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.38.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements We're excited to announce the addition of a new Node VMs page to the UI that provides a curated view of the cpu, memory, garbage collection, and event loop metrics that we have added over the past several releases of the node agent and native-metrics module. For more information, see our documentation. Added instrumentation of When.js promise library. Previously, the transaction state could get lost when multiple promises resolved close to each other. Fixed name of environment variable in error message when configuration file cannot be found. Thanks to @Maubic for the contribution! Updated tests to work with the latest version of Node 7.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1380","eolDate":"2020-03-16"},{"agent":"nodejs","date":"2017-02-16","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.37.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release is the same as v1.37.1  except it has been re-published to npm due to an issue with shrinkwrapping the previously published package.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1372","eolDate":"2020-02-16"},{"agent":"nodejs","date":"2017-02-16","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.37.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release has been re-published to npm as 1.37.2. Please use version 1.37.2  or higher. Improvements Agent now wraps emit on http request/response objects instead of relying on listeners. Improved documentation for newrelic.noticeError() and ignore_status_codes configuration. The documentation now makes it clear that errors recorded using noticeError() do not obey the ignore_status_codes configuration value. Removed unused yakaa dependency. Bug fixes Fixed a bug in normalization rules when replacements do not maintain initial /. Better de-duplication of errors when the same error instance is used multiple times. Server-side naming rules are now applied even when user defined ones have matched. Errors reported outside of a transaction now include their stack trace on the error analytics page. A potential stack overflow in trace serialization has been removed. Fixed an issue with our Express and domain instrumentation related to a loss of transaction state that could result in incorrect transaction names, traces, and events. Nested background transactions now report the correct number of metrics.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1371","eolDate":"2020-02-16"},{"agent":"nodejs","date":"2017-02-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.37.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features The agent now reports event loop metrics on supported platforms. The agent will now record the number of event loop ticks per minute and CPU time spent in each tick. This feature requires v2.1.0 or higher of the optional @newrelic/native-metrics module, and is supported on Node versions 0.12, 4, 6, and 7.You can read more about it on our docs site! Bug fixes The agent no longer creates a segment for each row returned from a PG query when the pg-query-stream module is used. Internal properties used in our promise instrumentation are now non-enumerable to prevent unexpected keys showing up for clients. Agent now uses safe stringification when encoding payloads in order to prevent an issue with circular references. Fixed issue with the agent holding the process open when retrying to connect to the collector. Improvements Removed io.js from our test suite, since it has not been supported for some time. Quieted a log message warning users about their own settings. Fixed typo in a log message. Thanks to Dave Bobak (@davebobak) for the contribution.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1370","eolDate":"2020-02-09"},{"agent":"nodejs","date":"2017-01-26","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.36.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed issue with timing Redis operations when called without a callback. Previously these operations would continue to be timed until the transaction ended, and as a result reported incorrect times. Transactions that result in a 404 HTTP error are now named \"(not found)\". Previously these transactions were reported with no name (e.g. get /). When the newrelic.js configuration file is not present, the agent now logs a message to the console and no longer prevents the app from starting up.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1362","eolDate":"2020-01-26"},{"agent":"nodejs","date":"2017-01-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.36.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Stop collecting URL parameters from the HTTP referer header The Node agent collects the request headers during an error trace to help determine the root cause of problems. The referer header is the URI that identifies the address of the webpage that linked to the resource being requested. It is possible that the referer URI may contain sensitive information in the request query parameters. New Relic has found that the query parameters are not properly stripped during the error trace. This update fixes this by stripping the query parameters from the referer in the request header before sending this data to New Relic. This release fixes New Relic Security Bulletin NR17-01 . Improvements Improved logging of modules that did not get instrumented.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1361","eolDate":"2020-01-12"},{"agent":"nodejs","date":"2016-12-21","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.35","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added CPU metric gathering to Node.js versions <6.1 As of this release the agent will attempt to gather CPU usage metrics via the optional @newrelic/native-metrics module. Added additional memory usage classification metrics. The agent will now report memory metrics that break down memory by its current use. For more information on these features, see our documentation.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1360","eolDate":"2019-12-21"},{"agent":"nodejs","date":"2016-12-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.35.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Removed automatic installation of @newrelic/native-metrics. Due to the way npm v3+ flatten dependencies, a bug in the version of npm packaged with Node v5, and npm v1's ungraceful handling of scoped packages we have opted to not automatically install this module. If you would like to see native metrics for your application, you can add the @newrelic/native-metrics module to your package.json and the Node Agent will automatically pick it up. Corrected attribution of the Bluebird patch in the last release's notes. Thanks to Matt Lavin (@mdlavin) for this correction!","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1351","eolDate":"2019-12-13"},{"agent":"nodejs","date":"2016-12-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.35.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release has been unpublished from npmjs.org. Please use version 1.35.1  or higher. New features The agent will now report garbage collection statistics on supported platforms. On node versions 0.10, 0.12, 4, 6, and 7 the agent will now record the time spent in, the number of, and type of garbage collection cycles. You can read more about it on our docs site! Bug fixes The agent no longer double counts MySQL query times when using a connection pool. Previously, when using a pool of connections a query done through the pool would be recorded as the time it took on the pool, as well as the connection, effectively counting the time twice. This is no longer the case. The agent will no longer lose transaction state across Bluebird's promise.nodify. Thanks to Matt Lavin (@mdlavin) for this contribution!","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1350-superseded","eolDate":"2019-12-12"},{"agent":"nodejs","date":"2016-11-10","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.34.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features The agent now collects CPU metrics when running under Node 6.1.0 and higher. Node 6.1.0 introduced an API to get CPU time usage of the running Node process. We are now collecting this data as new metrics. The agent now has a separate configuration for audit logging. Previously the data that the agent sends to the collector was logged only in trace logging mode, making the logs unnecessarily large and noisy. The agent can now include this data independent of the logging level using separate configuration settings. A new API method addCustomParameters() has been added to allow adding multiple custom parameters at once. Thanks to Austin Peterson (@AKPWebDesign) for this contribution! Improvements Updated tests to run on Node 7. Node 7 is officially supported as of the previous release, v1.33.0. The shutdown() API now waits for connection to collect pending data. When a flag to collect pending data is provided to the shutdown() method, the agent now ensures a connection to the collector has been established. This is useful when the Node process is short-lived, such as in AWS Lambda. Added running the nsp (Node Security Platform) tool to the test suite to help with detecting security-related vulnerabilities. Bug fixes The setIgnoreTransaction() API now works for background transactions. Fixed issue with synthetic result not displaying a link to the corresponding transaction trace.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1340","eolDate":"2019-11-10"},{"agent":"nodejs","date":"2016-10-31","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.33.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features The agent now collects database instance information for Memcached operations. This information (database server and database name) is displayed in transaction traces and slow query traces. Improvements socket.io long-polling requests are now ignored by default. Collecting metrics for these requests is typically not desirable since they are frequent and do not represent business transactions. Previously we recommended adding an ignore rule manually. Now it is included by default. Improved test coverage for Postgres and MongoDB instrumentations.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1330","eolDate":"2019-10-31"},{"agent":"nodejs","date":"2016-10-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.32.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features The agent now collects database instance information  for MySQL and MongoDB operations. This information (database server and database name) is displayed in transaction traces and slow query traces. Datastore instance configuration can now be done through environment variables. These can be set through NEW_RELIC_DATASTORE_INSTANCE_REPORTING_ENABLED and NEW_RELIC_DATASTORE_DATABASE_NAME_REPORTING_ENABLED Bug fixes The agent will no longer crash the process when an express param handler is executed when a transaction is not active.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1320","eolDate":"2019-10-20"},{"agent":"nodejs","date":"2014-02-14","downloadLink":null,"version":"1.3.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Includes a nearly total rewrite of the connection layer that the module uses to communicate with New Relic's servers: More useful logs! All of the logging has been reviewed closely to maximize its value and usefulness at pretty much every level. In practice, this means that the messages logged at 'info' and higher should only be for things that are relevant to you as a customer, and at 'debug' and 'trace' should be much more useful for us when we help you isolate issues with New Relic in your applications. See data faster! As part of the connection handshake with New Relic, the module will now send any performance metrics gathered during the startup cycle immediately, instead of waiting a minute for the first full harvest cycle. Get data to New Relic more reliably! When the module has issues connecting to New Relic, it's more consistent and resilient about holding your performance data for later delivery. Use less bandwidth! Performance data delivery to New Relic is now sequential instead of simultaneous. This means that the bandwidth used by New Relic will be less bursty, especially on hosts running many instrumented applications (or cluster workers). Better implementation! There were a number of architectural problems with the old version of the connection layer, which (among other things) made it difficult to test. The new version is simpler, has a much cleaner API, and has many, many more tests.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-132","eolDate":"2017-02-14"},{"agent":"nodejs","date":"2016-10-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.31.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features The agent now collects database instance information  for PostgreSQL and Redis operations. This information (database server and database name) is displayed in transaction traces and slow query traces.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1310","eolDate":"2019-10-12"},{"agent":"nodejs","date":"2014-02-01","downloadLink":null,"version":"1.3.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Always cast ignored status codes to numbers so that people using environment-variable configuration or strings in config still get error status ignored properly. If you disabled server-side configuration, the server was still able to set the value of apdex_t for your app. This was an oversight, and has been corrected. Before, if you had request renaming rules, if the end result was the same as the match pattern (mapping /path to /path), they would be silently ignored. This has been fixed. MySQL instrumentation handles callback more consistently, so the transaction tracer doesn't get confused and stop tracking transactions with MySQL calls in them.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-131","eolDate":"2017-02-01"},{"agent":"nodejs","date":"2016-10-04","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.30.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed issue with aborted requests causing the agent to crash in some cases. Previously the agent would crash when the client request aborted before Express server sent a response and encountered an error. Improvements Upgraded integration tests to work with the latest version of node-tap.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1305","eolDate":"2019-10-04"},{"agent":"nodejs","date":"2016-09-27","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.30.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Fixed format of external calls metric. External service URLs will now be formatted the same as they are in the originating application. Improved instrumentation of native promises. Native promises now use the same instrumentation as Bluebird, making instrumentation easier to maintain and more consistent across libraries. Bug fixes Fixed issue with reloading normalization rules from the server. Upon reset, the agent will clear the existing naming rules, removing any vestigial rules that may have changed or been disabled. Fixed issue with key transactions Apdex metric. Key transactions now effect the global Apdex metric according to their own ApdexT instead of the default ApdexT value. Fixed issue with closing transactions when the request is aborted. Previously, aborted requests would result in the transaction remaining open indefinitely. Now the transaction will be correctly finished and its resources freed.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1304","eolDate":"2019-09-27"},{"agent":"nodejs","date":"2016-09-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.30.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release is the same as v1.30.2  except it has been published using npm 2 to make sure all nested bundled dependencies are included.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1303","eolDate":"2019-09-14"},{"agent":"nodejs","date":"2016-09-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.30.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release has been unpublished from npmjs.org. Please use version 1.30.3  or higher. New features Added instrumentation of the param() function in Express. The agent will now create metrics and transaction segments when the Express param() function is called as a part of a route. This also fixes an issue with transaction naming when the HTTP response is ended within a param() method. Bug fixes Fixed an issue with naming Express transactions that result in 404 errors. Previously transactions were not always correctly normalized for URLs that caused 404 errors. The transactions will now always be reported with the same normalized name (e.g. \"get /\"). Fixed instrumentation of Express v4.0 - v4.5. Previously transactions were not correctly named on older versions of Express 4. Improvements Minor upates to logging.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1302","eolDate":"2019-09-13"},{"agent":"nodejs","date":"2016-09-01","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.30.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes The shutdown method is now on the stub API. Previously when the agent was disabled the stub API passed back on require did not have the shutdown method. Thanks goes to Vlad Fedosov (@StyleT) for this contribution! Global timers will now be wrapped correctly regardless of being wrapped by something else. The logic to check whether to wrap the global timers was looking to see if the global timers were the same function reference as the ones in the timers module. This would break in cases where either the global or timers functions had been wrapped. Director instrumentation now correctly handles the case of null route handlers being passed in. Previously the agent's director instrumentation would crash in cases of null route handlers in director.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1301","eolDate":"2019-09-01"},{"agent":"nodejs","date":"2016-08-25","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.30.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features A number of improvements and fixes to transaction naming rules. Added attributes terminate_chain, replace_all, and precedence to allow more control over how naming rules are executed. Please see the updated documentation in our README file. The order in which naming rules are executed can now be reversed with a feature flag reverse_naming_rules. When applying naming rules, the regular expression matching is now case insensitive. We have added a tool for testing naming rules. When the agent is installed, the tool can be run in terminal by executing node node_modules/.bin/newrelic-naming-rules. We have also improved our trace logging around transaction naming. Improvements Added trace logging to track number of transactions and segments in progress, and to better track segments created with the Express instrumentation. Fixed mysql2 tests that were not being run correctly. Bug fixes Fixed issue with reporting errors from domains. When an error is handled by using the error event of the domain, it is no longer reported as an uncaught exception.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1300","eolDate":"2019-08-25"},{"agent":"nodejs","date":"2014-01-18","downloadLink":null,"version":"1.3.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Spumko's Hapi! This support works with both Hapi 1.x and 2.0.0, and like our Express and Restify instrumentation will automatically name transactions after Hapi paths (get it) and time how long it takes to render views. Before, transaction naming and ignoring rules didn't work with Express and Restify routes. This has been addressed and the documentation has been clarified. Much gratitude to everyone who helped us figure out how to get this right, and for dealing with the previous, unclear documentation. Parameters in the ignored params list weren't being ignored in all cases. A very annoyingly chatty log message had its priority level dropped several levels.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-130","eolDate":"2017-01-18"},{"agent":"nodejs","date":"2026-01-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.9.2","features":[],"bugs":["Updated message consumer subscribers to properly time the consumption actions"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated message consumer subscribers to properly time the consumption actions (#3660 ) (ef1b611 ) Documentation Updated compatibility report (#3654 ) (ca16dae ) Miscellaneous chores Update OTEL metrics test (#3661 ) (ae84b62 ) Tests Added cross agent tests for sampler configuration and sampling rate scenarios (#3648 ) (fa0e2d1 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-9-2","eolDate":"2027-01-14"},{"agent":"nodejs","date":"2026-01-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.9.1","features":[],"bugs":["Updated `getHostnameSafe` to invalidate the cache is trying to assign the host based on the gcp cloud run id","Updated logic to properly assign content and role in LangChain chat completion messages"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated getHostnameSafe to invalidate the cache is trying to assign the host based on the gcp cloud run id (#3650 ) (d395c76 ) Updated logic to properly assign content and role in LangChain chat completion messages (#3638 ) (407bcb6 ) Documentation Updated compatibility report (#3643 ) (8929ab3 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-9-1","eolDate":"2027-01-12"},{"agent":"nodejs","date":"2026-01-08","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.9.0","features":["Added instrumentation support for `iovalkey`","Added `entity_guid` to Agent Control health file","Added support for OTel span events","Additional support for partial granularity traces (Not available for production use"],"bugs":["Updated samplers to properly assign sampling decisions based on appropriate context","Updated `undici` instrumentation to track the active and parent segment as symbols on request to properly end active request","Account for links added during transaction"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added entity_guid to Agent Control health file (#3594 ) (f42a501 ) Added instrumentation support for iovalkey (#3612 ) (55f5d6e ) Added support for OTel span events (#3600 ) (5b7c340 ) Additional support for partial granularity traces (Not available for production use) Added compact type for partial granularity traces. (#3608 ) (73b0381 ) Added core tracing supportability metrics (#3610 ) (c465f4c ) Updated metric names for full and partial traces to consolidate like values (#3620 ) (b201338 ) Bug fixes Account for links added during transaction (#3606 ) (488b678 ) Updated samplers to properly assign sampling decisions based on appropriate context (#3641 ) (4bbdddf ) Updated undici instrumentation to track the active and parent segment as symbols on request to properly end active request (#3619 ) (9baebe5 ) Code refactoring Removed unused distributed_tracing.in_process_spans.enabled logic. Partial granularity tracing replaces it (#3611 ) (1d5584e ) Updated @langchain/core instrumentation to subscribe to events emitted (#3493 ) (d1e90e4 ) Documentation Updated compatibility report (#3635 ) (74ac737 ) Miscellaneous chores Changed Langchain to LangChain, expand version range (#3629 ) (d77239e ) Copy OTEL status metadata to segment (#3613 ) (4057e80 ) deps:  Updated @newrelic/security-agent to v3.0.0 (#3637 ) (a84fa74 ) Don't create OpenAI segments if ai_monitoring is disabled (#3625 ) (b4f0010 ) Limit number of span links on segments (#3621 ) (c923c30 ) Updated Azure publishing with OIDC steps (#3633 ) (14c41c0 ) Tests Centralized indices for redis versioned tests (#3636 ) (34f6562 ) Changed LangChain tool test to >=0.2.0 (#3631 ) (3a4980f ) Fix LangChain test targets (#3634 ) (6504eb8 ) Refactored LangChain versioned tests (#3624 ) (12ae601 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-9-0","eolDate":"2027-01-08"},{"agent":"nodejs","date":"2025-12-15","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.8.1","features":[],"bugs":["Updated AWS Lambda instrumentation to skip wrapping handler callback if not present"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated AWS Lambda instrumentation to skip wrapping handler callback if not present (#3602 ) (d56e27d ) Documentation Updated compatibility report (#3596 ) (ed24527 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-8-1","eolDate":"2026-12-15"},{"agent":"nodejs","date":"2025-12-11","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.8.0","features":["Added support for `@langchain/aws`","Additional support for partial granularity traces (Not available for production use)"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for @langchain/aws (#3563 ) (56c4a78 ) Additional support for partial granularity traces (Not available for production use) Added partial granularity tracking metrics (#3566 ) (061f0fc ) updated AlwaysOn sampler to set priority to 3 for full trace and 2 for partial trace (#3577 ) (e7bcff4 ) Updated the span generation process (#3585 ) (74777d5 ) Code refactoring Converted AWS Bedrock's LlmError to use LlmErrorMessage (#3567 ) (8b2bb42 ) Updated @google/genai instrumentation to subscribe to events emitted (#3467 ) (e8d9ba1 ) Updated bunyan instrumentation to subscribe to events emitted (#3589 ) (f1e5f12 ) Documentation Updated compatibility report (#3592 ) (7455533 ) Miscellaneous chores Refactor span link serialization (#3574 ) (103044d ) Tests Moved mock aws bedrock server creation to test/lib/aws-server-stubs/index.js (#3593 ) (270df81 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-8-0","eolDate":"2026-12-11"},{"agent":"nodejs","date":"2025-12-08","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.7.0","features":["Updated `koa` instrumentation to properly wrap `Router` when using `@koa/router@15.0.0`+","Added ability to configure a ratio based sampler","Updated configuration to allow `adaptive.sampling_target` to be set for `config.distributed_tracing.sampler.root`, `config.distributed_tracing.sampler.remote_parent_sampled`, and `config.distributed_tracing.sampler.remote_parent_not_sampled`","Added support for OTEL span links","Replaced `default` with `adaptive` as the default for samplers","Preliminary support for partial granularity traces (Not available for production use)"],"bugs":["Fixed normalization of OTEL hrtime"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Updated koa instrumentation to properly wrap Router when using @koa/router@15.0.0+ (#3550 ) (f1e08ad ) Added ability to configure a ratio based sampler (#3501 ) (f300bd5 ) To assign a ratio based sampler, set config.distributed_tracing.sampler.root, config.distributed_tracing.sampler.remote_parent_sampled, or config.distributed_tracing.sampler.remote_parent_not_sampled to { trace_id_ratio_based: { ratio: <float between 0 and 1> }} To assign via environment variables set NEW_RELIC_DISTRIBUTED_TRACING_SAMPLER_<TYPE>='trace_id_ratio_based' and NEW_RELIC_DISTRIBUTED_TRACING_SAMPLER_<TYPE>_RATIO=<float between 0 and 1> where <TYPE> is one of ROOT, REMOTE_PARENT_SAMPLED, or REMOTE_PARENT_NOT_SAMPLED Updated configuration to allow adaptive.sampling_target to be set for config.distributed_tracing.sampler.root, config.distributed_tracing.sampler.remote_parent_sampled, and config.distributed_tracing.sampler.remote_parent_not_sampled (#3532 ) (44f51dd ) Added support for OTEL span links (#3528 ) (e840690 ) Replaced default with adaptive as the default for samplers (#3543 ) (3f03162 ) Preliminary support for partial granularity traces (Not available for production use) Added essential type for partial granularity traces (#3547 ) (3d85fb5 ) Added reduced type for partial granularity traces. (#3540 ) (cfa8f41 ) Added partial granularity samplers and assign transactions with isPartialTrace when partial granularity sampling decisions have been made (#3544 ) (1535a82 ) Refactored samplers into classes and store them on agent.sampler.* (#3527 ) (ad63441 ) Updated Samplers class to normalize logger messages, short circuit when applicable and remove optional chaining checks (#3546 ) (4f7684c ) Updated samplers to assign priority between 0-1 when DT is disabled or both full and partial granularity are disabled (#3559 ) (7a1c37e ) Updated transaction to store partial granularity indicator as .partialType (#3561 ) (a7f20d8 ) Updated when partial granularity rules are applied (#3553 ) (a4bdf4f ) Added toString and get [Symbol.toStringTag]() to default Sampler class (#3562 ) (771168d ) Bug fixes Fixed normalization of OTEL hrtime (#3564 ) (707fe7d ) Documentation Updated compatibility report (#3551 ) (02268a4 ) Added internal doc for attributes (#3539 ) (68543b6 ) Miscellaneous chores Improved logging around preconnect payload Added more logging around assigning hostname during preconnect (#3568 ) (3ee4d38 ) Improved GCP utilization logging (#3552 ) (e6c4141 ) Utilization resolution is now done concurrently (#3556 ) (8386360 ) Collected OTEL instrumentation scope metadata on all OTEL spans. (#3554 ) (75703c4 ) Improved OTEL hrtime processing (#3557 ) (8f187b1 ) Renamed config opentelemetry_bridge to opentelemetry (#3565 ) (c9d156f ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-7-0","eolDate":"2026-12-08"},{"agent":"nodejs","date":"2025-11-19","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.6.6","features":["Added configurations for `distributed_tracing.samplers.partial_granularity` and `distributed_tracing.samplers.full_granularity`"],"bugs":["Updated `app.use` or `router.use` Express instrumentation to properly wrap all middleware defined"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated app.use or router.use Express instrumentation to properly wrap all middleware defined (#3520 ) (d3b20d0 ) Documentation Updated compatibility report (#3522 ) (72ec652 ) (#3516 ) (35defb0 ) Tests Pinned next.js to skip 11.0.10 and 11.0.11 (#3521 ) (20977ee ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-6","eolDate":"2026-11-19"},{"agent":"nodejs","date":"2025-11-17","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.6.5","features":[],"bugs":["Updated MessageConsumerSubscriber to wait for consumer callback to end when it is a promise","Updated express instrumentation to ignore error when the `next` handler passes `route` or `router`"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated express instrumentation to ignore error when the next handler passes route or router (#3513 ) (724b218 ) Updated MessageConsumerSubscriber to wait for consumer callback to end when it is a promise (#3510 ) (45667a0 ) Documentation Updated compatibility report (#3498 ) (ef41b38 ) Tests Updated aws sdk v3 s3 test to no longer test DeleteBucketCommand (#3512 ) (df27448 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-5","eolDate":"2026-11-17"},{"agent":"nodejs","date":"2025-11-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.6.4","features":[],"bugs":["Updated MessageProducerSubscriber to properly set the sampled flag on traceparent","Updated `MessageConsumerSubscriber` to end transaction created for a given message consumption","Updated the bedrock middleware to be registered with a `high` priority to ensure payload is properly deserialized"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated MessageConsumerSubscriber to end transaction created for a given message consumption (#3503 ) (ba30818 ) Updated MessageProducerSubscriber to properly set the sampled flag on traceparent (#3505 ) (0b1a9a8 ) Updated the bedrock middleware to be registered with a high priority to ensure payload is properly deserialized (#3500 ) (63e531b ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-4","eolDate":"2026-11-13"},{"agent":"nodejs","date":"2025-11-11","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.6.3","features":[],"bugs":["Updated openai instrumentation to properly handle streaming when `stream_options.include_usage` is set","Updated `@google/genai` to properly handle assigning token counts to LlmCompletionSummary message","Updated AWS Bedrock instrumentation to properly assign token counts"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated @google/genai to properly handle assigning token counts to LlmCompletionSummary message (#3495 ) (f805d38 ) Updated AWS Bedrock instrumentation to properly assign token counts (#3491 ) (b1687f6 ) Updated openai instrumentation to properly handle streaming when stream_options.include_usage is set (#3494 ) (37c43f5 ) Code refactoring Update mysql and mysql2 instrumentation to subscribe to events emitted (#3423 ) (2e38914 ) Documentation Cleaned up README links and outdated verbiage (#3484 ) (51e6d7a ) Updated compatibility report (#3477 ) (859f27f ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-3","eolDate":"2026-11-11"},{"agent":"nodejs","date":"2025-10-29","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.6.2","features":[],"bugs":["Updated express instrumentation to properly instrument an array of middleware defined on a route"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated express instrumentation to properly instrument an array of middleware defined on a route (#3473 ) (e383c4e ) Documentation documented how to use the subscriber based instrumentation (#3432 ) (3b3ab72 ) Updated compatibility report (#3471 ) (964543b ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-2","eolDate":"2026-10-29"},{"agent":"nodejs","date":"2025-10-28","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.6.1","features":[],"bugs":["Updated middleware wrapper to not wrap handler if it is not a function"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated middleware wrapper to not wrap handler if it is not a function (#3469 ) (c702689 ) Documentation Updated compatibility report (#3466 ) (5853657 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-1","eolDate":"2026-10-28"},{"agent":"nodejs","date":"2025-10-27","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.6.0","features":["Added instrumentation for http2 client methods"],"bugs":["Updated `ioredis` instrumentation to handle breakage of errors when using `.pipeline`","Updated `openai` `instrumentStream` function to handle empty chunk when `include_usage` is set"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added instrumentation for http2 client methods (#3284 ) (bda7aea ) Bug fixes Updated ioredis instrumentation to handle breakage of errors when using .pipeline. (#3457 ) (49f4d93 ) Updated openai instrumentStream function to handle empty chunk when include_usage is set (#3427 ) (f804940 ) Code refactoring Update express instrumentation to subscribe to events emitted (#3424 ) (bbf3d01 ) Updated instances in instrumentation of Array.forEach for a more performant for...of or for index loop (#3463 ) (99484ce ) Updated instances of Array.forEach for a more performant for...of or for index loop (#3440 ) (48c37bf ) Updated token calculation for aws-bedrock LLM Events (#3445 ) (9450181 ) Updated token calculation for google-genai LLM Events (#3431 ) (41d32be ) Updated token calculation for openai LLM Events (#3430 ) (b8678cc ) Documentation Updated compatibility report (#3459 ) (f253b97 ) Miscellaneous chores Update release workflows (#3444 ) (d1ec158 ) Tests Added a randomString helper to agent_helper and use it in ioredis to avoid flappy tests, also updated local instances of random strings in kafka, elasticsearch and opensearch tests (#3462 ) (4deb6d8 ) Fixed conflict between ioredis and ioredis-esm by running flushdb instead of flushall to avoid index getting removed mid test (#3464 ) (5e3f0a8 ) Fixed express async error test to purposely misspell a method to emit a crash (#3435 ) (ff9f064 ) Moved aws-sdk-v3 common.js requirement of semver (#3461 ) (6a380ef ) Pinned Next.js tests to <16.0.0 (#3446 ) (10787a1 ) Updated minimum tested version of @langchain/core to 1.0.0 (#3437 ) (b61f67a ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-6-0","eolDate":"2026-10-27"},{"agent":"nodejs","date":"2025-10-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.5.0","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Code refactoring Updated fastify instrumentation to subscribe to events emitted (#3407 ) (51e361e ) Updated pg and pg-native instrumentation to subscribe to events emitted (#3397 ) (04af258 ) Updated config.instrumentation.timers.enabled to false to disable timers.setTimeout and timers.setInterval by default. (#3414 ) (b925d3d ) To re-enable, set config.instrumentation.timers.enabled to true in config or set NEW_RELIC_INSTRUMENTATION_TIMERS_ENABLED=true Documentation Updated compatibility report (#3413 ) (fef98dd ) Miscellaneous chores Added a new diagnostics base class and migrated undici to use new class (#3408 ) (8047bf1 ) Created directory for samplers (#3419 ) (dd2d3df ) Styles Require check-types and require-returns-type jsdoc (#3400 ) (e4cd687 ) Require jsdoc check*, implements-on-classes, and some no-undefined-types (#3404 ) (4fa645b ) Require jsdoc require-returns-check and require-property-* (#3403 ) (1008073 ) Tests Added helper to get version of package when package.json not exported, and updated tests that need it (#3411 ) (5ae02c7 ) Fixed fastify segment tree assertion when security agent is enabled (#3422 ) (b2cf6ed ) Refactored mcp tests to listen on new port for every streaming test, removed unncessary shutdown of process (#3420 ) (17db813 ) Updated an openai assertion with setTimeout disabled (#3421 ) (ceec8f9 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-5-0","eolDate":"2026-10-14"},{"agent":"nodejs","date":"2025-09-29","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.4.0","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Code refactoring Update amqplib instrumentation to subscribe to events emitted (#3377 ) (fecbb08 ) Updated cassandra-driver instrumentation to subscribe to events emitted. (#3372 ) (bb87cd8 ) Documentation Updated compatibility report (#3385 ) (b79be72 ) Miscellaneous chores Updated @apm-js-collab/tracing-hooks to latest to take advantage of wasm optimizations (#3398 ) (cda56cc ) Styles Require jsdoc/valid-types and jsdoc/check-param-names (#3368 ) (5d1b1d9 ) Require jsdoc require-param-description and require-param-type (#3391 ) (3785d0c ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-4-0","eolDate":"2026-09-29"},{"agent":"nodejs","date":"2025-09-22","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.3.3","features":["Added support for tracing callback on subscribers"],"bugs":["Updated `openai` instrumentation to properly return APIPromise to avoid crashing when using `completions.parse` or `responses.parse`"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for tracing callback on subscribers (#3371 ) (e6ad52e ) Bug fixes Updated openai instrumentation to properly return APIPromise to avoid crashing when using completions.parse or responses.parse (#3382 ) (c7ccf26 ) Documentation Updated compatibility report (#3370 ) (754c2f0 ) Miscellaneous chores Removed unused loader.mjs (#3376 ) (66a9fd5 ) Updated metrics for OTel Bridge enablement/disablement (#3381 ) (b976c37 ) Updated supportability metric names for OTel Bridge enablement… (#3383 ) (c7c1d6c ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-3","eolDate":"2026-09-22"},{"agent":"nodejs","date":"2025-09-10","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.3.2","features":[],"bugs":["Added defensive code for obtaining `protocol` in outbound http calls"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Added defensive code for obtaining protocol in outbound http calls (#3367 ) (ecda4e8 ) Code refactoring Benchmark test names (#3357 ) (229ff0d ) Documentation Updated compatibility report (#3351 ) (cf9f95d ) Continuous integration Benchmark tests run on push on main (#3359 ) (c0f81c3 ) Changed NUGET_SOURCE workflow to variable (#3364 ) (10692db ) Fix benchmark workflow (#3365 ) (7da99b5 ) Updated the GH_RELEASE_TOKEN to point to our bot user PAT instead of python agent (#3363 ) (06eb5c1 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-2","eolDate":"2026-09-10"},{"agent":"nodejs","date":"2025-09-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.3.1","features":[],"bugs":["Default `requestParameters` to an object to avoid crash in `transaction.addRequestParameters`"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Default requestParameters to an object to avoid crash in transaction.addRequestParameters (#3361 ) (ecd0d1d ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-1","eolDate":"2026-09-09"},{"agent":"nodejs","date":"2025-09-08","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.3.0","features":["Added MCP `StreamableHTTPClientTransport` support"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added MCP StreamableHTTPClientTransport support (#3337 ) (7189a35 ) Code refactoring Removed instances of url.parse. Streamlined how http instrumentation creates relevant attributes. (#3340 ) (1fc1e1a ) Updated openai instrumentation to subscribe to events emitted (#3331 ) (04dd677 ) Documentation Updated compatibility report (#3344 ) (e422919 ) Miscellaneous chores Refactored OTEL bridge signals setup (#3244 ) (ec8edef ) Tests Added more cassandra-driver tests (#3323 ) (d2e9d10 ) Fixed long running benchmark test and add shimmer.subscribers benchmark test (#3349 ) (15253c0 ) Fixed langchain openai streaming tests by explicitly passing streaming: true to chat model (#3346 ) (4f12499 ) Fixed openai test after migration to tracing channel (#3336 ) (0d01e29 ) Hardened batch-span-streamer.test.js to avoid random failures in CI (#3338 ) (2077ce3 ) Continuous integration Set benchmark host default to staging (#3332 ) (55f6b8d ) Updated the redis container to use the official redis image as bitnami/redis is moving and no reason to use a 3rd party image (#3342 ) (8ffb393 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-3-0","eolDate":"2026-09-08"},{"agent":"nodejs","date":"2026-05-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.20.0","features":["Updated how license keys are redacted in logs","Instrument Google ADK `FunctionTool.runAsync`","Added instrumentation for Google ADK `BaseAgent.runAsync`","Updated `@azure/functions` instrumentation to a subscriber type"],"bugs":["Updated `tracer.bindFunction` to touch segment if a promise is fulfilled or rejected","Updated aws sdk v3 instrumentation to handle using `@smithy/smithy-client` 4.13.0+","Updated `connect` instrumentation queries to handle file restructure in `<3.4.0`"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added instrumentation for Google ADK BaseAgent.runAsync (#3905 ) (c6c51d5 ) Instrument Google ADK FunctionTool.runAsync (#3935 ) (57f9ed7 ) Updated @azure/functions instrumentation to subscriber type (#3915 ) (227e779 ) Updated how license keys are redacted in logs (#3945 ) (6289502 ) Bug fixes Updated connect instrumentation queries to handle file restructure in <3.4.0 (#3923 ) (00b615c ) Updated tracer.bindFunction to touch segment if a promise is fulfilled or rejected (#3967 ) (712db61 ) Updated aws sdk v3 instrumentation to handle using @smithy/smithy-client 4.13.0+ (#3965 ) (5e0fe24 ) Code refactoring Removed reliance on AsyncLocalStorage.enterWith for undici, domain and process._fatalException instrumentation (#3894 ) (612b449 ) Documentation Updated compatibility report (#3941 ) (214b353 ) (#3934 ) (5a962d4 ) (#3909 ) (ad6fa8a ) Miscellaneous chores Added log line when max_trace_segments is hit (#3933 ) (46b9238 ) Comment out assertSegmentDuration for client-dynamodb test (#3972 ) (590cd3e ) Fix issue with amqplib tests (#3969 ) (a770000 ) Refactored Connect instrumentation to subscriber type (#3912 ) (e5d87b7 ) Refactored kafkajs instrumentation to subscriber type (#3958 ) (72e383c ) Remove actualTime vs segmentDuration assertion in memcached tests (#3932 ) (98c50e0 ) Updated @apm-js-collab/tracing-hooks to 0.7.0 (#3949 ) (5c99cd1 ) Tests Added assertSegmentDuration custom assertion and added it to memcached tests (#3875 ) (b28d866 ) Continuous integration Applied least-privilege model to all workflows to appease CodeQL (#3961 ) (237d5b9 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-20-0","eolDate":"2027-05-12"},{"agent":"nodejs","date":"2025-08-21","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.2.1","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Code refactoring Updated agent to use @apm-js-collab/tracing-hooks for the CJS/ESM registration for tracing channel based instrumentation (#3324 ) (4b2c14f ) Documentation Updated compatibility report (#3330 ) (2831a89 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-2-1","eolDate":"2026-08-21"},{"agent":"nodejs","date":"2025-08-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.2.0","features":["Added ability to register `Supportability/Features/Instrumentation/OnRequire/<pkg>` metrics for subscriber based instrumentation","Added instrumentation for `@modelcontextprotocol/sdk` client calls `client.callTool`, `client.readResource`, and `client.getPrompt`","Added esm loader hook and commonjs patch to work with orchestrion-js"],"bugs":["Fixed logic around detecting OTEL packages","Updated `shimmer.setupSubscribers` to properly setup and skip subscribers that are disabled"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added ability to register Supportability/Features/Instrumentation/OnRequire/<pkg> metrics for subscriber based instrumentation (#3312 ) (87bfa40 ) Added esm loader hook and commonjs patch to work with orchestrion-js (#3312 ) (415aeba ) Added instrumentation for @modelcontextprotocol/sdk client calls client.callTool, client.readResource, and client.getPrompt (#3312 ) (5d9790b ) Bug fixes Fixed logic around detecting OTEL packages (#3326 ) (4df30e5 ) Updated shimmer.setupSubscribers to properly setup and skip subscribers that are disabled (#3312 ) (cf5b3ec ) Code refactoring Added ability to disable subscribers via config.instrumentation.<pkg-name>.enabled (#3312 ) (55f8fe7 ) Added ability to prevent creation of segments in subscriber based instrumentation when parent is marked as internal and of the same package (#3322 ) (91f91c2 ) Removed id parameter from opensearch class (#3312 ) (8be00ce ) Updated opensearch instrumentation to subscribe to events emitted (#3312 ) (9a27a5d ) Updated elasticsearch instrumentation to subscribe to events emitted (#3312 ) (a3e2348 ) Updated ioredis instrumentation to subscribe to events emitted (#3312 ) (90b97d2 ) Updated pino instrumentation to subscribe to events emitted (#3312 ) (28bbe9f ) Updated subscribers to have a common createSegment that creates, assigns attributes, starts segment (#3317 ) (aa3f8d9 ) Updated undici instrumentation to remove its reliance on shim. Also updated storing the relevant segments on context instead of symbols on the request object (#3312 ) (ec17fa7 ) Documentation Updated compatibility report (#3313 ) (749ddc9 ) (#3304 ) (cc000a7 ) Miscellaneous chores change from ending segment to touching for feature parity with shim (#3312 ) (4d39fc5 ) Updated eslint configuration (#3296 ) (5c168a6 ) Tests Fixed obtaining opensearch package version for older versions we instrument (#3314 ) (e45ab27 ) Removed unnecessary prisma.$use in tests to unpin (#3303 ) (db20324 ) Continuous integration Allow users to run benchmark tests even if not sending metrics (#3307 ) (1be1514 ) Change benchmark tests to use TEST_LICENSE (#3325 ) (1f7f733 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-2-0","eolDate":"2026-08-20"},{"agent":"nodejs","date":"2026-04-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.19.2","features":[],"bugs":["Fixed `child_process` instrumentation to avoid leaking event handlers subscribed to `once`"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Fixed child_process instrumentation to avoid leaking event handlers subscribed to once (#3907 ) (ad0b1f6 ) Documentation Updated compatibility report (#3897 ) (0ed2202 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-19-2","eolDate":"2027-04-20"},{"agent":"nodejs","date":"2026-04-15","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.19.1","features":[],"bugs":["Fixed detecting AWS SDK message attributes presence"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Fixed detecting AWS SDK message attributes presence (#3903 ) (e81dc61 ) Tests Updated minAgentVersion for Anthropic versioned tests (#3900 ) (e1f6c32 ) Reorganized the test utilities in AWS versioned tests (#3895 ) (3025571 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-19-1","eolDate":"2027-04-15"},{"agent":"nodejs","date":"2026-04-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.19.0","features":["Added instrumentation support for `@anthropic-ai/sdk`","Updated OTel DB attributes to stable names from semantic conventions 1.40.0","Added distributed tracing propagation to AWS SDK v3 SNS"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added instrumentation support for @anthropic-ai/sdk (#3881 ) (e8713bb ) Updated OTel DB attributes to stable names from semantic conventions 1.40.0 (#3826 ) (6d3000d ) Added distributed tracing propagation to SNS (#3893 ) (8fc1144 ) Code refactoring Refactor @aws-sdk v3 instrumentation to subscribe to events emitted Added @aws-sdk/smithy-client subscriber (#3877 ) (0e350fc ) Added @smithy/smithy-client send subscriber with AWS Bedrock Middleware (#3864 ) (5e0a6d1 ) Moved generic AWS Client middleware to subscriber (#3889 ) (3cb1e1b ) Updated aws-sdk/dynamodb instrumentation to a subscriber middleware (#3891 ) (ff677a2 ) Updated aws sdk v3 instrumentation to split out bedrock utilities from actual wrapped middleware (#3883 ) (eed340e ) Updated Lambda instrumentation to a subscriber middleware (#3890 ) (12f8284 ) Refactored SNS instrumentation to subscriber type (#3876 ) (b9f3326 ) Refactored SQS instrumentation to subscriber type (#3880 ) (de46dee ) Refactored LlmErrorMessage to use vendor-specific subclasses (#3882 ) (5b0fd2b ) Refactored amqplib to use message broker constants (#3879 ) (77621fb ) Documentation Updated compatibility report (#3874 ) (ae887c4 ) Miscellaneous chores Updated @apm-js-collab/tracing-hooks to 0.6.0 (#3884 ) (f6ef470 ) Updated Undici tests to cover version 8 (#3896 ) (f27e75f ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-19-0","eolDate":"2027-04-13"},{"agent":"nodejs","date":"2026-03-30","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.18.0","features":["Instrumented grpc server stream to bind async context to stream event handlers"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Instrumented grpc server stream to bind async context to stream event handlers (#3855 ) (92c70a8 ) Code refactoring Refactored when instrumentation to subscribe to events emitted (#3866 ) (1b55c5a ) Refactored memcached instrumentation to subscribe to events emitted (#3849 ) (915b320 ) Refactored bluebird instrumentation to subscribe to events emitted (#3858 ) (e3d84c2 ) Refactored q instrumentation to subscribe to events emitted (#3853 ) (9fdb0b8 ) Refactored grpc-js client instrumentation to subscriber type (#3856 ) (057fca2 ) Refactored grpc-js server instrumentation to subscriber type (#3805 ) (ca3010a ) Updated @langchain/core subscribers to properly instrument the tool class methods (#3850 ) (2d17eed ) Documentation Updated compatibility report (#3831 ) (9156a6a ) Miscellaneous chores Added subscriber packages to load-externals (#3868 ) (83adcc4 ) Tests Removed unused context manager feature flag for running versioned tests (#3851 ) (15c9757 ) Updated core tracing cross agent tests (#3860 ) (08e4570 ) Fixed issue with span links test (#3863 ) (23a8594 ) Removed segment duration timing threshold in memcached tests (#3869 ) (bd24410 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-18-0","eolDate":"2027-03-30"},{"agent":"nodejs","date":"2026-03-19","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.17.0","features":["Added support for Continuous Profiling"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for Continuous Profiling (#3834 ) (6d8d5b5 ) Added server-side configuration for profiling.enabled (#3790 ) (0d44e5b ) (#3847 ) (e57223c ) Added delay + duration to ProfilingAggregator (#3815 ) (8000665 ) Added supportability metrics for profiling (#3801 ) (19bbb7e ) Prevented ProfilingAggregator from running in serverless mode (#3806 ) (e4db0f4 ) Disabled profiling.enabled when high security mode is enabled (#3803 ) (9d4eebb ) Added Heap profiler (#3751 ) (8262f6b ) Added Cpu Profiler (#3747 ) (2c2097f ) Note : Continuous Profiling UI is coming soon! While the Node.js agent now supports Continuous Profiling data collection, the visualization experience will debut in Limited Preview starting next week. If you would like to get early access to the profiling dashboards and UI features, please reach out to your Account Executive (AE) about how to opt-in to the preview. Code refactoring Refactor winston instrumentation to subscribe to events emitted (#3808 ) (4af2f48 ) Documentation Updated compatibility report (#3824 ) (0cfb356 ) Tests Added segment duration tests for ioredis/iovalkey (#3825 ) (9738bc8 ) Added segment duration timing tests for mysql2 (#3820 ) (bb424ff ) Changed structure of bedrock tests to avoid getting instrumented core libraries from first test (#3838 ) (886a36c ) Changed structure of lambda and sns tests to avoid getting instrumented core libraries from first test (#3836 ) (414044d ) Updated @aws-sdk/lib-dynamodb version range (#3829 ) (d28c938 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-17-0","eolDate":"2027-03-19"},{"agent":"nodejs","date":"2026-03-11","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.16.0","features":[],"bugs":["Updated `@apm-js-collab/tracing-hooks` to `0.5.0`, to allow instrumentation on windows environments."],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated @apm-js-collab/tracing-hooks to 0.5.0, to allow instrumentation on windows environments. (#3819 ) (d8f6d0f ) This version of @apm-js-collab/tracing-hooks includes the windows path fix for @apm-js-collab/code-transformer, see . Code refactoring Updated redis v3 instrumentation to subscribe to events emitted (#3802 ) (4d18302 ) Documentation Updated compatibility report (#3813 ) (27cb0a5 ) Tests Add redis-client and node-redis-client segment duration timing tests (#3810 ) (f07bcfe ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-16-0","eolDate":"2027-03-11"},{"agent":"nodejs","date":"2026-03-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.15.0","features":["Added `time_to_first_token` for AWS Bedrock","Added `time_to_first_token` for Google Gen AI","Added `time_to_first_token` for OpenAI","Added `time_to_first_token` for `LlmChatCompletionSummary`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added time_to_first_token for LlmChatCompletionSummary (#3781 ) (737f374 ) Added time_to_first_token for AWS Bedrock (#3804 ) (a993b00 ) Added time_to_first_token for Google Gen AI (#3785 ) (d90ee70 ) Added time_to_first_token for OpenAI (#3782 ) (07cfd57 ) Code refactoring Migrated redis 4+ instrumentation to subscribe to events emitted (#3773 ) (add6827 ) Documentation Updated compatibility report (#3800 ) (5228cdc ) (#3795 ) (1d6fe52 ) (#3791 ) (e79db5b ) (#3777 ) (12fe4c6 ) Miscellaneous chores Added version comment for agent-metadata.yml (#3779 ) (1267293 ) Refactored nestjs instrumentation to subscriber type (#3792 ) (f7feb25 ) Removed @langchain/core peer dep from langchain openai and aws tests (#3788 ) (e670bb1 ) Removed unneccessary generic-pool context propagation (#3786 ) (bdd35fb ) Removed unnecessary superagent context propagation (#3798 ) (81650e1 ) Updated @apm-js-collab/tracing-hooks to 0.4.0 (#3787 ) (d85fb2b ) Updated version format in agent-metadata.yml (#3778 ) (61759e9 ) Tests Updated langchain vectorstore tests to use a custom vectorstore to simplify the testing process (#3793 ) (0fd9b54 ) Updated version range for langgraph tests (#3794 ) (e02ce99 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-15-0","eolDate":"2027-03-09"},{"agent":"nodejs","date":"2026-02-24","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.14.0","features":["Added functionality to ingest logs from Azure Functions App automatically","Added support for error causes","Added ability to delay the start of the Profiler and run for n milliseconds before shutting down."],"bugs":["Updated `@google/genai` subscriber to handle the new `embedContentInternal` method in 1.42.0"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added ability to delay the start of the Profiler and run for n milliseconds before shutting down. (#3758 ) (8503d25 ) Added functionality to ingest logs from Azure Functions App automatically (#3772 ) (0c70ba2 ) Added support for error causes (#3769 ) (7c5aae3 ) Bug fixes Updated @google/genai subscriber to handle the new embedContentInternal method in 1.42.0 (#3771 ) (e96c974 ) Code refactoring AWS Bedrock llm events refactor (#3759 ) (7ff953d ) Google Gen AI LLM event refactor (#3748 ) (f1e3a0e ) LangGraph LlmAgent event, remove old LlmEvent base (#3761 ) (39d1d9a ) Updated the reparenting logic for compact mode of partial traces to assign parent id to entry span (#3768 ) (5196318 ) Documentation Updated compatibility report (#3774 ) (5d04bba ) Miscellaneous chores Added API key to enable support for GH action (#3760 ) (a521e80 ) Added call to agent metadata workflow - step 1 (#3750 ) (90eeaec ) Added span id to all debug/trace level logs in span.applyPartialTraceRules (#3766 ) (8c57230 ) Renamed file and fix cache output (#3757 ) (1ac00ea ) Set up metadata action to run with releases (#3762 ) (66efb13 ) Updated @langchain/core version for langchain-openai tests (#3763 ) (c27213e ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-14-0","eolDate":"2027-02-24"},{"agent":"nodejs","date":"2026-02-17","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.13.0","features":["Added `delay` and `duration` to profiling config","Updated the profiling config properties","Added ProfilingManager class, used to orchestrate profilers","Updated `RemoteMethod` to handle sending `pprof_data` through the collector","Added `ProfilingAggregator` that will be used to collect and send `pprof_data` telemetry","Added profiling configuration"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Feature Release With this release, we are making available our Node.js Hybrid Agent.\r\nThe Node.js Hybrid Agent provides a future-proof observability solution with\r\nintegrated support for OpenTelemetry Tracing, Metrics, and Logs APIs. Key\r\nenhancements like Span Links and Events on Spans are now available, ensuring\r\nseamless interoperability in mixed-mode environments. It is designed to bridge\r\nthe gap for Node.js teams looking to adopt OpenTelemetry standards while\r\nmaintaining backwards compatibility with their existing New Relic dashboards. A full product announcement, and documentation for this feature, is\r\ncoming soon. Please subscribe to our news releases \r\nto be kept up-to-date. Features Added delay and duration to profiling config (#3754 ) (a7f06e0 ) Added ProfilingAggregator that will be used to collect and send pprof_data telemetry (#3732 ) (738045c ) Added profiling configuration (#3733 ) (2b4d7d8 ) Added ProfilingManager class, used to orchestrate profilers (#3738 ) (105da3b ) Updated RemoteMethod to handle sending pprof_data through the collector (#3734 ) (868e5bd ) Updated the profiling config properties (#3742 ) (fa55881 ) Code refactoring LangChain LLM event refactor (#3745 ) (b2612ec ) OpenAI LLM event refactor (#3726 ) (0ccad21 ) Documentation Updated compatibility report (#3743 ) (4a7cafc ) (#3739 ) (59ff976 ) (#3730 ) (dea410b ) (#3703 ) (532729a ) Miscellaneous chores Added subcomponent attribute to LangChain tool traces (#3706 ) (c5469ea ) Added subcomponent attribute to mcp-sdk invocations (#3749 ) (70b7f41 ) Enabled all OTEL signals by default when OTEL is enabled (#3712 ) (15b82c2 ) Fixed @langchain/community peer dep conflict (#3741 ) (202d2b3 ) Removed @langchain/core peer dep from LangGraph test matrix (#3737 ) (8ba2616 ) Renamed OTEL metrics config params to snake_case from camelCas… (#3711 ) (4f59108 ) Updated ai-support.json to include LangGraph (#3705 ) (aa0ba22 ) Updated eslint configuration (#3740 ) (d306374 ) Tests Updated mcp streaming tests to generate sessions to reuse transport for all streaming tests (#3729 ) (1772fd5 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-13-0","eolDate":"2027-02-17"},{"agent":"nodejs","date":"2026-02-02","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.12.0","features":["Added instrumentation support for `@langchain/langgraph`","Added compact mode for span links","Added `timestamp` to AWS Bedrock `LlmChatCompletionSummary`","Added `timestamp` to LangChain `LlmChatCompletionSummary`","Added `timestamp` to Google Gen AI `LlmChatCompletionSummary`"],"bugs":["Updated langchain tool instrumentation to properly redefine the segment name on every call"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added instrumentation support for @langchain/langgraph (#3645 ) (f339675 ) Added timestamp to LlmChatCompletionSummary messages Added timestamp to AWS Bedrock LlmChatCompletionSummary (#3702 ) (430d1dd ) Added timestamp to Google Gen AI LlmChatCompletionSummary (#3690 ) (7748e26 ) Added timestamp to LangChain LlmChatCompletionSummary (#3701 ) (7472118 ) Added compact mode for span links (#3681 ) (6ff6961 ) Bug fixes Updated langchain tool instrumentation to properly redefine the segment name on every call (#3691 ) (4df6068 ) Documentation Updated compatibility report (#3699 ) (40b6b81 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-12-0","eolDate":"2027-02-02"},{"agent":"nodejs","date":"2026-01-29","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.11.0","features":["Added timestamp to OpenAI `LlmChatCompletionSummary`","Added `timestamp` to LangChain input `LlmChatCompletionMessage`","Added `timestamp` to Google Gen AI `LlmChatCompletionMessage`","Added `timestamp` to AWS Bedrock `LlmChatCompletionMessage`","Added essential tracing mode for span links"],"bugs":["Added defensive code in `lib/subscribers/middleware-wrapper.js` to prevent crash when attempting to associate an error on an incoming http request","Updated `pg` instrumentation to properly capture the TraceSegment duration for promise based queries","Updated `Supportability/Nodejs/PartialGranularity/NrIds/Dropped` metric to only keep track of spans that got dropped when `nr.ids` execeeded 63 spans."],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added timestamp to AIM LlmChatCompletionMessage messages Added timestamp to AWS Bedrock LlmChatCompletionMessage (#3685 ) (ea297c8 ) Added timestamp to Google Gen AI LlmChatCompletionMessage (#3686 ) (f4dd09e ) Added timestamp to LangChain input LlmChatCompletionMessage (#3658 ) (0bce235 ) Added timestamp to OpenAI LlmChatCompletionSummary (#3689 ) (55b0310 ) Additional support for partial granularity traces (Not available for production use) Added essential tracing mode for span links (#3670 ) (83dfb84 ) Updated Supportability/Nodejs/PartialGranularity/NrIds/Dropped metric to only keep track of spans that got dropped when nr.ids execeeded 63 spans. (#3684 ) (9797cf3 ) Bug fixes Added defensive code in lib/subscribers/middleware-wrapper.js to prevent crash when attempting to associate an error on an incoming http request (#3697 ) (658e78b ) Updated pg instrumentation to properly capture the TraceSegment duration for promise based queries (#3695 ) (0051697 ) Code refactoring Added AIM abstract subscribers and updated all AIM subscribers to use them (#3676 ) (08cd38b ) Documentation Updated compatibility report (#3675 ) (cc898f4 ) Miscellaneous chores Added TimedEvent limit of 100 (#3683 ) (0d595d8 ) Added supportability metrics Supportability/Nodejs/SpanEvent/<Links|Events>/Dropped when limit of 100 is exceeded (#3688 ) (a247d31 ) Removed eslint disable next line for sonarjs/no-dead-store (#3692 ) (593fa15 ) Continuous Integration Fixed CI issue when sec-agent present (#3677 ) (23da654 ) Tests Assert that span events drop in partial traces (#3680 ) (25e3781 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-11-0","eolDate":"2027-01-29"},{"agent":"nodejs","date":"2026-01-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.10.0","features":["Add `timestamp` to OpenAI input `LlmChatCompletionMessage`s","Added reduced tracing mode for span links"],"bugs":["Updated OpenAI instrumentation to properly parse headers when a call fails"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Add timestamp to OpenAI input LlmChatCompletionMessages (#3657 ) (099e20e ) Added reduced tracing mode for span links (#3649 ) (2414331 ) Bug fixes Updated OpenAI instrumentation to properly parse headers when a call fails (#3665 ) (641b7a8 ) Documentation Updated compatibility report (#3669 ) (ec922ae ) (#3668 ) (85c601f ) (#3663 ) (82b3ac8 ) Miscellaneous chores Lazy load OTEL dependencies (#3667 ) (0b0c764 ) Record subscriber usage metric (#3626 ) (5796574 ) Update ai-support.json (#3666 ) (562b403 ) Updated OpenAI instrumentation to skip creating a LlmChatCompletionMessage for an outgoing tool call response (#3655 ) (572c3a1 ) Tests Updated mock response to avoid retries on OpenAI LangChain vectorstore calls (#3664 ) (bc1faf3 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-10-0","eolDate":"2027-01-20"},{"agent":"nodejs","date":"2025-08-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.1.0","features":["Disabled timers instrumentation by default in the sample configuration","Added supportability metrics when instrumentation has been disabled for a package","Added support for OTEL logs API"],"bugs":["Fixed `transaction.url` obfuscation"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for OTEL logs API (#3228 ) (19a9c78 ) Added supportability metrics when instrumentation has been disabled for a package (#3252 ) (6098a5b ) Disabled timers instrumentation by default in the sample configuration (#3253 ) (72eb8d4 ) Bug fixes Fixed transaction.url obfuscation (#3280 ) (dc09492 ) Code refactoring Updated http-outbound to parse url only once (#3270 ) (5bb0f8d ) Documentation Updated distributed tracing example target to use the correct repo (#3254 ) (1fb3859 ) Updated compatibility report (#3299 ) (8b85342 ) Updated compatibility report (#3267 ) (2712c94 ) Updated compatibility report (#3265 ) (daedadd ) Updated compatibility report (#3261 ) (bd7d3fa ) Updated compatibility report (#3246 ) (c289fb5 ) Updated compatibility report (#3241 ) (64529e1 ) Miscellaneous chores Added guardrail for OTEL bridge (#3283 ) (ff71865 ) Refactored API bootstrapping (#3281 ) (97be8f6 ) Tests Cleaned up engines and version ranges in versioned tests (#3260 ) (c7fd60e ) Fixed failing http benchmark test (#3258 ) (7e8cd48 ) Fixed a failing span-event benchmark test (#3255 ) (05b955f ) Fixed CI issues with latest 24 (#3277 ) (960d169 ) Fixed tests that assumed timers instrumentation was always enabled (#3257 ) (40cfda1 ) Forced install of peer deps on nestjs test app (#3269 ) (4e454ff ) Continuous integration Updated CI to fail if benchmark tests fail (#3256 ) (a6a7a15 ) Added sending benchmark metrics to NR One (#3285 ) (7fc8e40 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-1-0","eolDate":"2026-08-13"},{"agent":"nodejs","date":"2025-07-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"13.0.0","features":["Dropped support for Node.js 18","Updated min supported version for `fastify` to 3.0.0, `pino` to 8.0.0, and `koa-router` to 12.0.0"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes ⚠ BREAKING CHANGES This version of the Node.js agent is a SemVer MAJOR update and contains the following breaking changes. MAJOR versions may drop support for language runtimes that have reached End-of-Life according to the maintainer. Additionally, MAJOR versions may drop support for and remove certain instrumentation. For more details on these changes please see the migration guide . Dropped support for Node.js 18 Updated min supported version for fastify to 3.0.0, pino to 8.0.0, and koa-router to 12.0.0 Features Dropped support for Node.js 18 (#3097 ) (cb7c080 ) Updated min supported version for fastify, pino, and koa-router (#3108 ) (ae9e21d ) Documentation Updated AI Monitoring compatibility docs with new AWS Bedrock APIs (#3230 ) (e1ff0d3 ) Updated compatibility report (#3237 ) (dc85e4e ) Tests Fixed assertSegments to insert all expected segments (#3239 ) (de183fb ) Updated tests to mock outgoing calls to avoid issues in CI (#3234 ) (66694c6 ) Continuous integration Updated prepare release to exclude semver major copy for repos other than node-newrelic (#3242 ) (82d9689 ) Updated release prep to add copy around breaking changes (#3199 ) (ca1131c ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-13-0-0","eolDate":"2026-07-23"},{"agent":"nodejs","date":"2016-07-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.29.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Domain error handlers will now be scoped to the transaction the error occurred in. Previously, the 'error' event handlers would not be scoped to a transaction causing our API methods to not associate data correctly (e.g. using noticeError would not associate the error with the transaction and would instead be unscoped). Bug fixes Reworked the SQL parser to handle new lines in the query. Previously the agent would have difficulty classifying queries with new lines in them. Thanks to Libin Lu (@evollu) for the fix! Postgres instrumentation is now compatible with inputs with text getter attributes. Thanks again to Libin Lu (@evollu) for the fix!","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1290","eolDate":"2019-07-14"},{"agent":"nodejs","date":"2016-07-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.28.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Improved agent startup speed by 10% by simplifying environment checks. Removed prolific fs.exists and fs.stat checks, instead simply handling the error for mis-used files which greatly reduces disk access. Added slightly more trace-level logging around the creation of segments. Added examples for using the newrelic.createBackgroundTransaction method in a number of different use cases. Bug fixes Removed excessive segment creation from PG instrumentation. For queries with many results we would create a segment for each result. This would result in excessive object allocation and then cause harsh GC thrashing. Fixed a bug in agent connect that could cause an identity crisis under specific use cases. When using the agent with multiple app names, transaction information could be misattributed to other services if they share the same first app name. This resolves that by using all of the host names to uniquely identify the agent.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1283","eolDate":"2019-07-14"},{"agent":"nodejs","date":"2016-07-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.28.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements Director instrumentation that will now name the transaction correctly, as well as create segments corresponding to the handlers registered with director. Transaction naming refactor - this should clear up some inconsistent naming issues in our router instrumentations. Previously the instrumentation was tasked with the maintenance of the transaction state name, now this has been abstracted into its own class to be used by instrumentations. Express instrumentation refactored to scope transaction storage to the incoming request object. Previously the express instrumentation used a stack to track which router was expecting middleware to finish and keep track of which transaction is being executed. The new implementation has a stronger guarantee on scoping work to the correct transaction. Bug fixes The agent now uses the correct units (was seconds, now milliseconds) for slow queries - this fixes and issue where query traces in the databases tab were slower than the reported maximum.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1282","eolDate":"2019-07-07"},{"agent":"nodejs","date":"2016-06-15","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.28.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Improvements The following attributes are now sent to Insights along with transaction events: databaseDuration, databaseCallCount. Updated Redis instrumentation to work with version 2.x of the redis module. Improvements to error tracking on systems that have a lot of errors. Minor improvements in tests and logging. Bug fixes Fixed a few issues with the Express instrumentation. Middleware functions mounted with a path variable now generate the correct middleware metrics. Routers mounted using route methods now generate the correct trace segments and times. Routers mounted on root path are now not included in trace when they contain no matching routes.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1281","eolDate":"2019-06-15"},{"agent":"nodejs","date":"2016-05-25","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.28.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Express middleware metrics are now enabled by default. Improvements The following attributes are now sent to Insights along with transaction events: externalDuration, externalCallCount, and queueDuration. Custom SSL certificates (from the agent configuration) are now used even when a proxy is not explicitly defined. This is useful in some environments that use an implicit proxy for all network traffic.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1280","eolDate":"2019-05-25"},{"agent":"nodejs","date":"2016-05-05","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.27.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed duplicated external transactions for https requests in Node > 0.10. Any external transaction that used the https module to make the request would appear twice in transaction traces due to https.request internally using http.request. This has now been resolved. Updated eslint dev dependency to 2.9.0 (was 0.24.1). Fixed an issue with transaction naming precedence. Custom naming of transactions will no longer be replaced by names generated by the instrumentation. Fixed tests which broke under Node 6.0. Node 6.0.0 changed some messaging and internal functionality which our tests were asserting on. These tests have been updated to work with either the new version or the older ones. Fixed installing GCC 5 in Travis for testing native modules in Node >= 3.0. Starting in Node 3.0, native modules were compiled with C++11 features enabled. The version of GCC preinstalled on Travis was too old to support that so we now manually install GCC 5 and set it as the system compiler. Fixed metrics that were being scoped to themselves. Some metrics were scoped to themselves, causing a strange visual glitch in the New Relic UI. This self-scoping has been removed. Added tests for transaction naming with parallel requests in Express.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1272","eolDate":"2019-05-05"},{"agent":"nodejs","date":"2016-05-03","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.27.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed issue with checking listener count for uncaughtException and unhandledRejection global events. Fixed a number of issues with promise instrumentation of Bluebird.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1271","eolDate":"2019-05-03"},{"agent":"nodejs","date":"2016-04-21","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.27.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release has been unpublished from npmjs.org. Use version 1.27.1  or higher. New Features Reworked promise instrumentation to be more reliable and reusable. Promise instrumentation has been rewritten to be applicable to any A+ compliant promise library. This change brings more consistent instrumentation of Bluebird promises. This change also allows users to see the execution order of chained promises in their Transaction Traces. This is an opt-in process and can be achieved by setting feature_flag.promise_segments to true in the agent config. Bug fixes The agent now properly checks for custom SSL certificates. The check previously was falsely positive if there was an empty list of custom certificates. This caused red herrings to be admitted into the debug logs. Thanks to Seth Shober (@sethshober) for the fix! Promise error handling is now more consistent. Previously the agent would notice errors being emitted on unhandledRejection regardless of other listeners. Errors coming in on the unhandledRejection event will not be recorded if there are handlers for the event - this is more in line with our error handling practices in other instrumentations. Improvements Added a .npmignore file to exclude non-essential files. The agent will now omit tests and examples on install from npm, drastically improving download times. Thanks to Serge Havas (@Sinewyk) for the contribution! Logging has been reworked to reduce CPU overhead. The check to see if a logging call was valid happened fairly late in the logic, causing unnecessary work to be done regardless of logger state. This has been rectified, netting a large decrease in CPU overhead.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1270","eolDate":"2019-04-21"},{"agent":"nodejs","date":"2016-04-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.26.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added ioredis instrumentation. Big thanks to Guilherme Souza (@guilhermef) for the contribution! Added a new shutdown call to the public API. Thanks to @echmykhun for the contribution! The new shutdown API call will gracefully stop the agent. It can optionally harvest any pending data waiting to be sent to the New Relic servers before shutting down. To read more about this new API, please read our README, or visit our docs page . Added support for truncated segment notifiers. Segments related to work that happens after a transaction has finished will now be labeled as Truncated in the UI. Bug fixes Fixed an issue in the express instrumentation related to inactive/lost transaction state. Thanks to Jacob Page (@DullReferenceException) for submitting this fix. Previously, the agent would crash if there was no active transaction when an Express middleware would handle the request. Improvements The agent now uses MongoDB's APM API for its instrumentation. Method discovery for instrumentation is now done through MongoDB's APM API in newer versions of the MongoDB driver.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1262","eolDate":"2019-04-07"},{"agent":"nodejs","date":"2016-03-31","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.26.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added capturing errors from the unhandledRejection global event. If a promise is rejected with an error, and the error is not handled, the error will now be reported to New Relic. Bug fixes Fixed issue with attaching an event handler every time Express was required. Fixed issue with chained promises losing context. Previously the transaction state was getting lost when an error was thrown early in a promise chain. Fixed issue with the agent crashing when an http Server did not have the address() getter. Fixed issue with Express instrumentation when a wrapped layer object was missing a method. Improvements Added more logging around the CAT feature.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1261","eolDate":"2019-03-31"},{"agent":"nodejs","date":"2016-03-23","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.26.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Express instrumentation has been fundamentally reworked. This refactor includes a few bug fixes around error handling and transaction naming, as well as optional higher resolution traces. Setting feature_flag.express_segments to true in the agent config will make the agent report the amount of time spent in each individual middleware per request Fixes The agent will not report errors handled in an error handler it is monitoring - this is more in line with how the agent does error handling in other contexts. The agent will now name transactions correctly when an application responds from a middleware.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1260","eolDate":"2019-03-23"},{"agent":"nodejs","date":"2016-03-09","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.25.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Added instrumentation of Bluebird promises. Previously, the transaction state could get lost when multiple promises resolved close to each other. Fixed issue with PostgreSQL native instrumentation. Previously, calling require('pg').native more than once was causing the agent to crash. Fixed issue with hapi instrumentation not returning value from Server.connection(). Various improvements to tests to make them more stable.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1255","eolDate":"2019-03-09"},{"agent":"nodejs","date":"2016-02-24","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.25.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Added more HTTP request/response parameters to transactions. The agent now collects additional request/response HTTP headers (e.g. contentType, HTTP method, response status code). These can be used to filter and group errors in the Error analytics page, as well as events in Insights. Fixes Fixed an issue with collecting errors when an Express error handler removed message and stack properties from the error object.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1254","eolDate":"2019-02-24"},{"agent":"nodejs","date":"2016-02-18","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.25.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed crashing bug on unhandled rejections in Q. Previously, the agent would cause the process to crash in the event of an unhandled rejection. Thanks to @mdlavin for this fix!","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1253","eolDate":"2019-02-18"},{"agent":"nodejs","date":"2016-02-17","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.25.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Added Q instrumentation. The node agent now accurately records programs using Q for promises. Thanks to @mdlavin for the contribution! Added node-mysql2 support. Thanks to @jhollingworth for adding node-mysql2 support to the agent. Query streaming in node-mysql now works while using the agent. Previously, due to the way node-mysql was instrumented query streaming would be forced off when the agent was collecting data. This is no longer the case and query streaming will work and be recorded as expected.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1252","eolDate":"2019-02-17"},{"agent":"nodejs","date":"2016-01-26","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.25.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Corrected an issue where the agent would sometimes crash looking up the port of the HTTP server that a request came from. Previously, the agent assumed the HTTP server would always have an address, unfortunately this isn't the case if the HTTP server's .close() has been called.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1251","eolDate":"2019-01-26"},{"agent":"nodejs","date":"2016-01-20","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.25.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New Features Added support for the new Response Time Line  and better representation of asynchronous data. This has many implications in the UI. The first is the Application Overview , in the past we've always just shown \"node\" and maybe \"request queueing \" on the response time graph. We now show you an application breakdown like our other language agents! This means you'll be able to see how much time was in HTTP externals, your various datastores, or spent in node itself. Overlaid on this will be your response time as a blue line. Next page that has been affected is our Transaction Overview  page. Specifically when you click into a Transaction to see more detail. Previously we showed you a breakdown of the top time consumers in that transaction, both as a graph and as a table. Unfortunately that graph didn't show response time and the table would show percentages over 100%. Now, like the Application Overview, you will get a blue response time line and the breakdown table will have numbers that add up much more intuitively! Finally, our Transaction Trace  view has also been updated. The change is very similar to the changes mentioned above for the breakdown table in the Transaction Overview page. You should no longer see percentages over 100% here either. Improvements Transaction trace serialization is now 4x faster than before. This speedup will primarily affect those with large, deeply nested transactions. Though small transactions have seen some improvement as well.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1250","eolDate":"2019-01-20"},{"agent":"nodejs","date":"2015-12-30","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.24.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Error totals are now reported. The agent now reports metrics that reflect the total number of errors that have occurred in web and background transactions. Bug fixes Disabling SSL no longer requires the setting of a port. Previously, the agent required changing port in the config to 80 when disabling SSL. The agent will now default to port 80 if a port is not supplied and SSL is turned off. Logging functions have been improved. The agent will now properly log error stack traces and can rate limit logging messages. To aid in debugging we have provided more logging about the public API.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1241","eolDate":"2018-12-30"},{"agent":"nodejs","date":"2015-11-18","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.24.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"New features Advanced Analytics for APM Errors With this release, the agent reports TransactionError events . These new events power the Advanced Analytics for APM Errors  feature. The error events are also available through New Relic Insights . Advanced Analytics for APM Errors lets you see all of your errors with granular detail, filter and group by any attribute to analyze them, and take action to resolve issues through collaboration. Bug fixes NEW_RELIC_LOG_ENABLED environment variable is now treated as a boolean. Previously, this option was treated as a string, causing it to not work for some use cases. Thanks to @jakecraige for contributing this fix!","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1240","eolDate":"2018-11-18"},{"agent":"nodejs","date":"2015-11-05","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.23.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes newrelic.getBrowserTimingHeader() API now includes the full transaction name. Previously, the agent would use a fragment of the transaction name, causing Browser Monitoring transactions and APM transactions to not be cross linked. This change makes the cross linking work correctly.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1231","eolDate":"2018-11-05"},{"agent":"nodejs","date":"2015-10-29","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.23.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The New Relic Node Agent now officially supports Node v4! We are excited to announce that the New Relic Node Agent officially supports Node v4.x! We've tested the agent across all major versions of Node used by New Relic customers to ensure a quality Node APM experience. New Relic recommends upgrading to Node v4.x for best Node Agent performance. Corrected a parsing issue in the slow sql query parsing step. Previously, the agent would not be able to parse inputs to database libraries that specified sql as an option param. This was an issue with node-mysql, namely. The agent now correctly handles this case and registers the queries as expected.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1230","eolDate":"2018-10-29"},{"agent":"nodejs","date":"2015-10-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.22.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Removed client support of the RC4 stream cipher for communicating with the New Relic servers. The RC4 cipher is considered unsafe and is generally being deprecated. Fix for logging version number in Express instrumentation. Thanks @tregagnon. When an unsupported version of Express is detected, we log a message that contains the Express version number. The version is a string and was being logged as a number, resulting in NaN in the log message. Agent is now more safe when recording memory stats. Previously, the agent would crash the process as it was gathering memory usage information (i.e. when process.memoryUsage threw an error). This defect is now guarded against with a try-catch.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1222","eolDate":"2018-10-14"},{"agent":"nodejs","date":"2015-09-21","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.22.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Express and Connect instrumentation will no longer crash on Node 4 As of ES6, the Function.name attribute will track if the function is a getter/a setter/is bound to (i.e. fn.bind().name -> 'bound ' + fn.name). This new behavior caused the agent to crash on start up due to the way connect and express are instrumented. The agent is now more defensive of future implementations of ES6.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1221","eolDate":"2018-09-21"},{"agent":"nodejs","date":"2015-08-20","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.22.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Errors will now respect its transaction's ignore state. When ignoring transactions, related errors will now also be ignored. The agent can now handle immutable and frozen error objects. In rare cases the agent gets passed an immutable error object. The agent would then crash when trying to tag the error object with the current transaction. We now handle these errors properly.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1220","eolDate":"2018-08-20"},{"agent":"nodejs","date":"2015-08-06","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.21.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Corrected a defect in the handling of uncaught exceptions This defect was surfaced in versions of node that did not have process._fatalException, namely v0.8. When an uncaught exception occurs, the agent now records the error and passes it along to the other uncaught exception handlers that have been registered. This was inverted before, passing along errors when there were no other error handlers present and rethrowing otherwise.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1212","eolDate":"2018-08-06"},{"agent":"nodejs","date":"2015-07-13","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.21.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Moved concat-stream from dev dependencies to production dependencies. Last week we released v1.21.0 but forgot to move a dependency. We've removed v1.21.0 from npmjs.org and this release contains the changes from that version. Support for display host names  (originally in 1.21.0). The agent now has configuration settings to allow configuration of custom host names. Set process_host.display_name  to enable this. If this config is not set, the agent will continue to use the host name found through an os.hostname() call. Should this lookup fail somehow, process_host.ipv_preference  can now be set to 4 or 6 to configure the type of ip address displayed in place of the host name.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1211","eolDate":"2018-07-13"},{"agent":"nodejs","date":"2015-07-10","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.21.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes This release has been unpublished from npmjs.org . Use v1.21.1  or higher instead. Support for display host names . The agent now has configuration settings to allow configuration of custom host names. Set process_host.display_name  to enable this. If this config is not set, the agent will continue to use the host name found through an os.hostname() call. Should this lookup fail somehow, process_host.ipv_preference  can now be set to 4 or 6 to configure the type of ip address displayed in place of the host name.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1210-superseded","eolDate":"2018-07-10"},{"agent":"nodejs","date":"2015-06-23","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.20.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixed a bug where custom events weren't being sent. In a refactor of our data collection cycle, we omited the custom events from the list of commands, this is now fixed. Fixed a very rare bug where the custom event pool could be set to 10 instead of the user config value. This patch was contributed by shezarkhani , thanks! This case would only be hit if you disabled custom events via server sent config while there were custom events ready to be sent. Then you later reenabled it via server sent config. It would only occur for one data collection cycle then reset back to the correct size.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1202","eolDate":"2018-06-23"},{"agent":"nodejs","date":"2015-06-11","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.20.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixed a bug in custom event recording limits. Previously, the agent would use the config value for max events (default of 1000) for the first harvest of custom events, then would use an internal default for the reservoir with max of 10 events for each harvest after that, resulting in less than the expected number of events being sent. Exposed the custom_insights_events settings in the user config. You can now set custom_insights_events.enabled and custom_insights_events.max_samples_stored in your newrelic.js. Read more about these settings in our documentation .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1201","eolDate":"2018-06-11"},{"agent":"nodejs","date":"2013-12-07","downloadLink":null,"version":"1.2.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: Before, there were certain circumstances under which an application would crash without New Relic installed, but wouldn't crash with it. This has been fixed, and applications with New Relic installed now crash consistently. The error tracer is now also considerably simpler. Added a security policy. See the new section in README.md or read SECURITY.md. Future-proofed the MongoDB instrumentation and prevented the module from breaking GridFS. Made a small tweak that should reduce the amount of blocking file I/O done by the module. The module's instrumentation and harvest cycle will now not hold the process open in Node 0.9+. This should make it easier for processes to shut themselves down cleanly with New Relic running. The environment information gatherer will no longer crash if it tries to read a directory where it's expecting a file. Errors thrown during the execution of Express routes or Connect middlewares that were attached to requests that ended in HTTP status codes configured to be ignored by default will now be ignored correctly. Made the module play nicer with Node's REPL. It no longer assumes that an application necessarily has a main module. A few tweaks were made to support the CoolBeans dependency injection framework. Several log messages were demoted to a less chatty level.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-120","eolDate":"2016-12-07"},{"agent":"nodejs","date":"2024-12-18","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.9.0","features":["Added entity linking attributes to aws-sdk v3 Lambda segments","Provided ability to define newrelic config as `newrelic.mjs`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added entity linking attributes to aws-sdk v3 Lambda segments (#2845 ) (8820265 ) Provided ability to define newrelic config as newrelic.mjs (#2836 ) (972b59d ) Documentation Updated compatibility report (#2828 ) (d5fe8e3 ) Miscellaneous chores deps:  Updated @newrelic/security-agent to v2.2.0 (#2842 ) (170941e ) Updated borp configs to target tests correctly (#2835 ) (66ae59d ) Tests Removed tap and cleaned up left over tap helpers (#2804 ) (37407b6 ) Updated match to fail if you pass in an object that lacks the expected keys (#2843 ) (a3db8bd ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-9-0","eolDate":"2025-12-18"},{"agent":"nodejs","date":"2024-12-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.8.2","features":[],"bugs":["Fixed matching for Lambda events containing resource but which aren't API Gateway","Fixed `mysql2` promise instrumentation to properly handle `createPool` and `createPoolCluster`"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Fixed mysql2 promise instrumentation to properly handle createPool and createPoolCluster (#2823 ) (a679872 ) Fixed matching for Lambda events containing resource but which aren't API Gateway (#2825 ) (64d2042 ) Documentation Updated compatibility report (#2814 ) (580a27f ) Miscellaneous chores Improved documentation for assertSegments (#2819 ) (298473c ) Tests Added test/custom-assertions.js to the apollo-server external versioned tests config (#2817 ) (568525a ) Fixed flakey when versioned test (#2821 ) (54f034b ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-8-2","eolDate":"2025-12-09"},{"agent":"nodejs","date":"2024-12-04","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.8.1","features":[],"bugs":["Updated `mysql2` instrumentation to work with 3.11.5+","Fixed matching for ALB and API Gateway (v1 & v2) events for Lambda"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Fixed matching for ALB and API Gateway (v1 & v2) events for Lambda (#2780 ) (2f1a6c6 ) Updated mysql2 instrumentation to work with 3.11.5+ (#2811 ) (3ec4fee ) Documentation Fixed changelog to group the labels in logs work (#2776 ) (04271da ) Fixed links to next.js apps (#2812 ) (834440c ) Updated compatibility report (#2809 ) (fc1fbda ) Tests Migrated test/integration/api tests to node:test (#2787 ) (03b01a3 ) Migrated test/integration/core tests to node:test (#2781 ) (36bc0e7 ) Migrated test/integration/instrumentation tests to node:test (#2784 ) (963fb30 ) Migrated test/integration/transaction tests to node:test (#2783 ) (68e1a0c ) Migrated test/integration/utilization tests to node node:test (#2794 ) (db237e9 ) Migrated test/smoke/api tests to node:test (#2772 ) (af3bbcd ) Migrated CAT integration tests to node:test (#2778 ) (bd9df5f ) Migrated integration tests at root to node:test (#2803 ) (a7ef080 ) Migrated root smoke tests to node:test (#2771 ) (78f2709 ) Migrated smoke tests in test/smoke/agent, test/smoke/e2e, and test/smoke/index to node:test (#2774 ) (440a0af ) Removed t.diagnostic as they're better suited as code comments (#2786 ) (ee24027 ) Fixed flaky test on macOS (#2790 ) (eebf06b ) Removed reference to pino internals (#2805 ) (0382ee2 ) Restricted mysql2 version to get CI working (#2808 ) (ad60ed4 ) Updated agent integration tests to node:test (#2782 ) (d556512 ) Updated config integration tests to node:test (#2777 ) (fe8d2df ) Updated distributed-tracing integration tests to node:test (#2798 ) (83ad1f3 ) Updated grpc integration tests to node:test (#2789 ) (ea8f743 ) Updated index, issue-2155, and metric integration tests to node:test (#2801 ) (80b55c2 ) Updated q, superagent, and when tests to node:test (#2773 ) (ff2d8d0 ) Updated shimmer, uninstrumented, environment, flatten, and logger integration tests to node:test (#2802 ) (83fd7ee ) Added per test file timing to test reporter (#2785 ) (00d9940 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-8-1","eolDate":"2025-12-04"},{"agent":"nodejs","date":"2024-11-19","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.8.0","features":["Added new configuration options to add custom tags (labels) to logs","Moved `entity.guid`, `entity.name`, `entity.type`, and `hostname` to `common.attributes` on logs payload instead of in every log message","Added support for Bedrock Claude 3.5 invoke model user request"],"bugs":["Corrected expected shape of user input in get Prompt()"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added labels.enabled and labels.exclude to config defaults (#2727 ) (36adb13 ) Added new configuration options to add custom tags (labels) to logs (#2743 ) (d20c874 ) With custom tags on logs, platform engineers can easily filter, search, and correlate log data for faster and more efficient troubleshooting, improved performance, and optimized resource utilization. To learn more about this feature see the documentation To enable set config.application_logging.forwarding.labels.enabled to true or the environment variable NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LABELS_ENABLED to true (#2727 ) (36adb13 ) To exclude labels that were set on application from logs use config.application_logging.forwarding.labels.exclude or the environment variable NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LABELS_EXCLUDE Added support for Bedrock Claude 3.5 invoke model user request (#2721 ) (a901a24 ) Moved entity.guid, entity.name, entity.type, and hostname to common.attributes on logs payload instead of in every log message (#2736 ) (a7f14de ) Bug fixes Corrected expected shape of user input in get Prompt() (#2741 ) (a8eef8b ) Documentation Updated compatibility report (#2755 ) (459a3f1 ) Miscellaneous chores Fixed test reporter (#2751 ) (5878ef9 ) Improved unit test speed (#2728 ) (9640030 ) Tests Fixed two assertions to work against older versions of openai (#2726 ) (8996fc3 ) Migrated ioredis, prisma and undici versioned tests to node:test (#2746 ) (449ae03 ) Migrated memcached, nestjs, and restify versioned tests to node:test (#2752 ) (653f614 ) Migrated nextjs versioned tests to node:test (#2749 ) (d385af6 ) Migrated redis versioned tests to node:test (#2725 ) (9752827 ) Updated hapi tests to node:test (#2722 ) (636899b ) Updated kafkajs, langchain, & openai tests to node:test (#2723 ) (b6e4c5d ) Updated koa tests to node:test (#2744 ) (86c22a4 ) Updated mongodb tests to node:test (#2738 ) (295e7e6 ) Updated pg and pg-esm tests to node:test (#2750 ) (40aea36 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-8-0","eolDate":"2025-11-19"},{"agent":"nodejs","date":"2024-11-11","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.7.0","features":["Added `cloud.resource_id` attribute to dynamo spans","Enhance Proxy Request Handling to Display Actual External URLs"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added cloud.resource_id attribute to dynamo spans (#2701 ) (904f41b ) Enhance Proxy Request Handling to Display Actual External URLs (#2698 ) (3ef7bbe ) Thanks for the contribution @mstarzec386 Documentation Updated compatibility report (#2712 ) (82f0e98 ) (#2699 ) (4432c42 ) Miscellaneous chores Added a benchmark script for our sql parser (#2708 ) (9b6de68 ) Updated express-esm, generic-pool, grpc, & grpc-esm tests to node:test (#2702 ) (a229bbf ) Tests Migrated mysql and mysql2 versioned tests to node:test (#2711 ) (fc767e0 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-7-0","eolDate":"2025-11-11"},{"agent":"nodejs","date":"2024-11-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.6.1","features":["added `cloud.aws.account_id` to default config"],"bugs":["Fixed issue parsing docker container id"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features added cloud.aws.account_id to default config (#2691 ) (0ccee8e ) Bug fixes Fixed issue parsing docker container id (#2705 ) (0c897ab ) Documentation Updated compatibility report (#2679 ) (3c19cdf ) Miscellaneous chores Moved recorders to lib/metrics/recorders (#2666 ) (d8dfe84 ) Tests Fixed file extensions for aws-sdk v2 and v3 versioned tests to reflect they have been migrated to node:test (#2687 ) (4ec09ba ) Migrated elasticsearch and esm-package versioned tests to node:test (#2680 ) (0e0c2b2 ) Updated cls and connect tests to node:test (#2676 ) (1e74434 ) Reorganized custom assertions and improved test reporter (#2700 ) (9e98b18 ) Updated cassandra-driver tests to node:test (#2678 ) (bd4f7ff ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-6-1","eolDate":"2025-11-07"},{"agent":"nodejs","date":"2024-10-30","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.6.0","features":["Added ARN and provider to Lambda segments","Added IAST configurations for scan scheduling and restrictions"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added ARN and provider to Lambda segments (#2674 ) (a23294c ) Added IAST configurations for scan scheduling and restrictions (#2645 ) (13a627a ) Documentation Updated compatibility report (#2673 ) (e4d0503 ) Miscellaneous chores Replaced static openssl cert usage with in-process cert (#2671 ) (72872f4 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-6-0","eolDate":"2025-10-30"},{"agent":"nodejs","date":"2024-10-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.5.2","features":["Updated shim/when instrumentation to use tracer to run in context"],"bugs":["Fixed amqplib instrumentation via ESM"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Updated shim/when instrumentation to use tracer to run in context (#2642 ) (1a80ad5 ) Bug fixes Fixed amqplib instrumentation via ESM (#2668 ) (a36deba ) Documentation Remove SECURITY.md (#2633 ) (41002cd ) Updated compatibility report (#2670 ) (281c0fa ) Updated match custom-assertion jsdoc (#2636 ) (c37abe5 ) Miscellaneous chores Upgraded import-in-the-middle to work around a bug introduced in 1.11.1 (#2618 ) (9ad476a ) Tests Migrated aws-sdk-v2 and aws-sdk-v3 tests to node:test (#2620 ) (e0dc015 ) Migrated test/unit/shim to node:test (#2599 ) (8d1acff ) Migrated test/versioned/amqplib to node:test (#2612 ) (7bdada6 ) Migrated test/versioned/express to node:test (#2609 ) (bd2f1a5 ) Migrated bluebird versioned tests to node:test (#2635 ) (6e28fad ) Migrated last group of unit tests to node:test (#2624 ) (386f546 ) Migrated unit tests to node:test (#2623 ) (86231b7 ) Updated tests that relied on tspl by awating the plan.completed instead of calling end to avoid flaky tests (#2610 ) (935ac14 ) Updated tests that used the context manager directly and instead use the tracer to access the segment context (#2643 ) (b917b3e ) Updated the mininum version of pg-native in pg-esm tests to align with the pg tests (#2616 ) (16be714 ) Migrated bunyan, pino, and winston tests to node:test (#2634 ) (69c1ab8 ) Migrated fastify tests to node:test (#2632 ) (b522477 ) Migrated block of unit tests to node:test (#2607 ) (e33807b ) Migrated block of unit tests to node:test (#2604 ) (cd90ce1 ) Migrated block of unit tests to node:test (#2593 ) (6d4d49e ) Continuous integration Added delay to site extension publishing to wait for NPM (#2665 ) (e412020 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Node.js agent EOL policy for information about agent releases and support dates .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-5-2","eolDate":"2025-10-23"},{"agent":"nodejs","date":"2024-09-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.5.1","features":[],"bugs":["Fixed handling of Pino merging object"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Fixed handling of Pino merging object (#2600 ) (de3c266 ) Documentation Updated compatibility report (#2589 ) (2f45a4a ) Miscellaneous chores deps:  Udpated @newrelic/security-agent to v2.0.0 (#2594 ) (92e6978 ) Tests Converted transaction* and urltils tests to node:test (#2585 ) (d169546 ) Fixed @koa/router tests. path-to-regex differs between @koa/router and koa-router now (#2587 ) (608dd98 ) Removed transitive deps from versioned tests as they will auto-install if required as peer deps (#2580 ) (0db6599 ) Updated a missing minSupported in aws-sdk-v3 versioned tests (#2582 ) (c997af6 ) Updated fastify versioned tests to work with fastify@5.0.0 (#2584 ) (a5a1526 ) Updated how we handle the koa-router nuance of wildcard routes (#2588 ) (ddeb097 ) Updated koa-router to tests to handle bug fixes from 13.0.1 (#2578 ) (a28e2e6 ) Migrate block of unit tests to node:test (#2570 ) (5cd1d8a ) Migrate second block of unit tests to node:test (#2572 ) (943a83e ) Reduce koa-router version to enable CI (#2573 ) (f44a99b ) Removed noisy test log (#2583 ) (3766ed6 ) Continuous integration Added workflow run trigger to Azure site extension publish job (#2575 ) (e8ae942 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-5-1","eolDate":"2025-09-23"},{"agent":"nodejs","date":"2024-09-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.5.0","features":["Added utilization info for ECS"],"bugs":["Ensured README displays for Azure site extension"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added utilization info for ECS (#2565 ) (6f92073 ) Bug fixes Ensured README displays for Azure site extension (#2564 ) (a30aed5 ) Documentation Updated compatibility report (#2562 ) (8f7aebe ) Tests Convert metric and metrics-recorder tests to node:test (#2552 ) (7ae4af4 ) Updated serverless unit tests to node:test (#2549 ) (619f23c ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-5-0","eolDate":"2025-09-12"},{"agent":"nodejs","date":"2024-09-11","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.4.0","features":["Provided ability to disable instrumentation for a 3rd party package","Added support for `express@5`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for express@5 (#2555 ) (252f3b2 ). Provided ability to disable instrumentation for a 3rd-party package (#2551 ) (abfb9f0 ). To disable instrumentation, set config.instrumentation.<library>.enabled to false.  The values of <library> are the keys listed here . Be cautious when using this feature, as disabling instrumentation for a library could affect instrumentation of other libraries executed afterwards. Miscellaneous chores Added CI for publishing agent as Azure site extension (#2488 ) (468943a ). Added Azure site extension installation scripts (#2448 ) (a56c4e1 ). Tests Converted llm-events tests to use node:test (#2535 ) (ebfa2e9 ). Migrated test/unit/spans to use node:test (#2556 ) (9319071 ). Migrated test/unit/util to use node:test (#2546 ) (0b07be8 ). Migrated tests in test/unit/instrumentation to use node:test (#2531 ) (47b8398 ). Converted collector unit tests to node:test (#2510 ) (762511b ). Converted errors unit tests to node:test (#2540 ) (ae82760 ). Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Node.js agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-4-0","eolDate":"2025-09-11"},{"agent":"nodejs","date":"2024-09-04","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.3.1","features":[],"bugs":["Fixed detection of REST API type payloads in AWS Lambda"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Fixed detection of REST API type payloads in AWS Lambda (#2543 ) (adfeebc ) Documentation Cleaned up formatting of api.js to properly inject example snippets when rendering on API docs site (#2524 ) (4b34f3d ) Updated compatibility report (#2523 ) (29784ea ) Updated Next.js Otel cloud provider FAQ (#2537 ) (6553807 ) Tests Converted db unit tests to node:test (#2514 ) (bea4548 ) Converted grpc, lib, and utilization tests to node:test (#2532 ) (c207e1e ) Replaced distributed tracing tests with node:test (#2527 ) (8184c56 ) Added a match function for tests (#2541 ) (51e7f34 ) Converted config to node:test (#2517 ) (1534a73 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-3-1","eolDate":"2025-09-04"},{"agent":"nodejs","date":"2024-08-27","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.3.0","features":["Added new API method `withLlmCustomAttributes` to run a function in a LLM context"],"bugs":["Improved AWS Lambda event detection"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added new API method withLlmCustomAttributes to run a function in a LLM context (#2437 ) (57e6be9 ) The context will be used to assign custom attributes to every LLM event produced within the function Bug fixes Improved AWS Lambda event detection (#2498 ) (5e8b260 ) Documentation Updated compatibility report (#2493 ) (0448927 ) Miscellaneous chores Fixed linting scripts (#2497 ) (c395779 ) Removed examples/shim (#2484 ) (40d1f5c ) Updated test-utils dependency and added matrix-count only (#2494 ) (5e04c76 ) Tests Converted the api unit tests to node:test (#2516 ) (ab91576 ) Converted context-manager unit tests to node:test (#2508 ) (9363eb0 ) Continuous integration Updated codecov action sha to post coverage from forks.  Added flag to fail ci if it fails to upload report (#2490 ) (12fbe56 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-3-0","eolDate":"2025-08-27"},{"agent":"nodejs","date":"2026-02-10","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.25.1","features":[],"bugs":[],"security":["Bumped minimum version of security agent"],"supportedOperatingSystems":null,"description":"Notes Security Bumped minimum version of security agent (#3713 ) (88b2334 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-25-1","eolDate":"2026-07-09"},{"agent":"nodejs","date":"2025-07-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.25.0","features":["Instrument AWS Bedrock Converse API"],"bugs":["`eventSegment.addAttribute` will not crash if null","`openai` Responses API support changed to >=v4.87.0"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Instrument AWS Bedrock Converse API (#3191 ) (16ac684 ) Bug fixes eventSegment.addAttribute will not crash if null (#3215 ) (8955f37 ) openai Responses API support changed to >=v4.87.0 (#3219 ) (19c0c70 ) Documentation Updated compatibility report (#3220 ) (b4350c7 ) Miscellaneous chores Converted .proto to .json for bundling (#3212 ) (1e208d4 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-25-0","eolDate":"2026-07-09"},{"agent":"nodejs","date":"2025-07-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.24.0","features":["Implemented configurable attribute value size limit"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Implemented configurable attribute value size limit (#3206 ) (08a6eca ) Documentation Updated compatibility report (#3190 ) (72c492c ) Miscellaneous chores Rename GCP ID config flag (#3205 ) (8446f29 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-24-0","eolDate":"2026-07-07"},{"agent":"nodejs","date":"2025-06-30","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.23.0","features":["Added ability to report only on entry and exit spans","Added Node.js 24 support"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added ability to report only on entry and exit spans (#3184 ) (1f909d3 ) Added Node.js 24 support (#3080 ) (a538c2a ) Documentation Updated compatibility report (#3186 ) (5498c15 ) Miscellaneous chores Fix issues on Node 24 (#3181 ) (24832df ) Removed force labels on main CI workflow (#3183 ) (3aaee17 ) Updated undici tests to unblock CI (#3185 ) (08261eb ) Continuous integration Fixed the name of todo colum in add to board reusable workflow (#3178 ) (f216e0c ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-23-0","eolDate":"2026-06-30"},{"agent":"nodejs","date":"2025-06-24","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.22.0","features":["Added `openai` v5 streaming support","Added support for `openai.responses.create` api"],"bugs":["Fixed error logging for undefined tracestate header"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added openai v5 streaming support (#3148 ) (6e90d41 ) Added support for openai.responses.create api (#3139 ) (a1204b2 ) Bug fixes Fixed error logging for undefined tracestate header (#3170 ) (3c915f5 ) Code refactoring Updated transformation rules to remove the bespoke rule to appease @google-cloud/pubsub <5.1.0 (#3151 ) (2d9b4b4 ) Documentation Gemini compatibility (#3134 ) (bbdc531 ) Updated compatibility report (#3171 ) (f3361e4 ) Miscellaneous chores Added logging of used New Relic environment variables (#3145 ) (1a9d9f5 ) Added supportability metrics to OTEL metrics API (#3164 ) (5312db0 ) Fixed formatting in Slack PR titles (#3167 ) (847859f ) Improved output of pending prs script (#3160 ) (9bafd77 ) Improved setup of OpenTelemetry metrics API (#3138 ) (e91592d ) Pinned google/genai to <1.5.0 (#3154 ) (04b9bde ) Removed discontinued Bedrock models (#3158 ) (2c79a31 ) Removed usage of shim.argsToArray in favor of rest parameters (#3141 ) (b144d71 ) Tweaked nestjs test manifest (#3152 ) (51b82aa ) Tests Added JSDoc annotation for benchmark interface (#3127 ) (77e7e0a ) fixed test assertion for langchain openai (#3169 ) (29ec912 ) Skips running nest 11+ on node 18 due to dropping support (#3149 ) (961975b ) unpinned google genai tests (#3168 ) (cfa7114 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-22-0","eolDate":"2026-06-24"},{"agent":"nodejs","date":"2025-06-04","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.21.0","features":["Added `@google/genai` Gemini AI LLM instrumentation","Updated opentelemetry bridge to rely on configuration based transformation rules"],"bugs":["Refactored getHostnameSafe to accommodate GCP","Updated openai instrumentation to work with 5.0.0+","Updated rules to work with 1.17.0 and 1.24.0 for consumer and producer span kind"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added @google/genai Gemini AI LLM instrumentation (#3119 ) (7f28a29 ) Updated opentelemetry bridge to rely on configuration based transformation rules (#3125 ) (ad116d2 ) Bug fixes Refactored getHostnameSafe to accommodate GCP (#3132 ) (f1eea8d ) Updated openai instrumentation to work with 5.0.0+ (#3129 ) (09146a9 ) Updated rules to work with 1.17.0 and 1.24.0 for consumer and producer span kind (#3128 ) (686c747 ) Documentation Updated compatibility report (#3124 ) (c51d45f ) (#3117 ) (084e599 ) Miscellaneous chores Added preliminary otel configuration (#3121 ) (664ee4a ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-21-0","eolDate":"2026-06-04"},{"agent":"nodejs","date":"2025-05-27","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.20.0","features":["Added support for OTEL metrics API"],"bugs":["Fixed common.getKeys logic","Fixed Google Cloud Run hostname issue"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for OTEL metrics API (#3109 ) (4a57721 ) Bug fixes Fixed common.getKeys logic (#3114 ) (01d4fa5 ) Fixed Google Cloud Run hostname issue (#3111 ) (e233fb7 ) Documentation Updated compatibility report (#3106 ) (3c47406 ) Miscellaneous chores Added event source type to  txn name for Lambda APM Mode (#3110 ) (ddc2e2a ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-20-0","eolDate":"2026-05-27"},{"agent":"nodejs","date":"2024-08-19","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.2.0","features":["Added instrumentation support for Express 5 beta"],"bugs":["Updated `koa` instrumentation to properly get the matched route name and to handle changes in `@koa/router@13.0.0`"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added instrumentation support for Express 5 beta (#2476 ) (06a4c2f ) This will be experimental until express@5.0.0 is generally available Bug fixes Updated koa instrumentation to properly get the matched route name and to handle changes in @koa/router@13.0.0 (#2486 ) (0c2ee2f ) Documentation Removed reference to @newrelic/next in README (#2479 ) (8740539 ) Updated compatibility report (#2487 ) (c0a5e64 ) Miscellaneous chores Reverted to upstream require-in-the-middle (#2473 ) (9bbc41c ) Updated aggregators unit tests to node:test (#2481 ) (fd2d76f ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Node.js agent EOL policy for information about agent releases and support dates .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-2-0","eolDate":"2025-08-19"},{"agent":"nodejs","date":"2025-05-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.19.0","features":["Added Azure Function HTTP streaming support"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added Azure Function HTTP streaming support (#3070 ) (9865e1c ) Code refactoring Added check to only set a FakeSpan if transaction.agent.otelSpanKey exists (#3071 ) (b0c1ac1 ) Documentation Updated compatibility report (#3074 ) (7dc9aad ) Miscellaneous chores Fixed redis legacy test suite (#3077 ) (ec39925 ) Updated security agent (#3098 ) (48ed8cb ) Tests Added cross agent otel bridge tests (#3057 ) (1526bed ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-19-0","eolDate":"2026-05-20"},{"agent":"nodejs","date":"2025-04-30","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.18.2","features":[],"bugs":["Updated `createSegment` to stop adding segments to trace when `max_trace_segments` is exceeded"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated createSegment to stop adding segments to trace when max_trace_segments is exceeded (#3056 ) (8f3336e ) Documentation Updated compatibility report (#3065 ) (#3063 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-18-2","eolDate":"2026-04-30"},{"agent":"nodejs","date":"2025-04-29","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.18.1","features":[],"bugs":["Only add `newrelic` header to outgoing headers if has a value"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Only add newrelic header to outgoing headers if has a value (#3052 ) (6ef0a90 ) Code refactoring Added defensive code when calculating exclusive time on a segment where it cannot locate the segment in the transaction trace tree (#3051 ) (b4aa25e ) Updated how otel bridge trace propagator assigns traceparent/tracestate headers (#3046 ) (6e317b8 ) Documentation Updated compatibility report (#3054 ) (#3050 ) (#3026 ) Tests Skipped regressions in pg-native versioned tests (#3053 ) (6ce3670 ) Updated elasticsearch image for versioned tests (#3038 ) (3d73f9f ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-18-1","eolDate":"2026-04-29"},{"agent":"nodejs","date":"2025-04-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.18.0","features":["Support Azure functions background trigger types","Support Azure functions HTTP trigger type"],"bugs":["Updated span streamer to properly retry failed batches and handle flushing batch queue every 5 seconds"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Support Azure functions background trigger types (#3028 ) (3bf17b0 ) Support Azure functions HTTP trigger type (#3021 ) (90d894b ) Bug fixes Updated span streamer to properly retry failed batches and handle flushing batch queue every 5 seconds (#3033 ) (7db0e7c ) Code refactoring Update otel bridge rules synthesizer to properly handle consumer kind rules (#3003 ) (3295dd1 ) Documentation Updated compatibility report (#3020 ) (ce32b67 ) Miscellaneous chores Fixed prisma CI issues (#3031 ) (1349cae ) Improved logging within utilization detection (#3034 ) (b47bd46 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-18-0","eolDate":"2026-04-14"},{"agent":"nodejs","date":"2025-04-02","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.17.0","features":["Azure Function utilization","Support honoring W3C `traceparent` sampled flag"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Azure Function utilization (#3017 ) (80ab93e ) Support honoring W3C traceparent sampled flag (#3009 ) (d903413 ) By default the agent will not honor the traceparent sampled flag. To control how sampling works with traceparent set the following in config: distributed_tracing.sampler.remote_parent_sampled(when the traceparent sampled flag is 01) always_on: the agent will sample spans always_off: the agent will not sample spans default: the agent will rely on existing priority sampling to make its decisions distributed_tracing.sampler.remote_parent_not_sampled(when the traceparent sampled flag is 00) always_on: the agent will sample spans always_off: the agent will not sample spans default: the agent will rely on existing priority sampling to make its decisions Code refactoring Updated otel bridge to centralize mapping rules for a given span attribute to accomondate semantic convention spec updates (#3010 ) (c20c36b ) Documentation Updated compatibility report (#3013 ) (8fab715 ) Tests Pinned openai@4.90.0 to work with @langchain/openai (#3019 ) (eaa3db0 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-17-0","eolDate":"2026-04-02"},{"agent":"nodejs","date":"2025-03-24","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.16.1","features":["Assign all attributes on internal spans to segment"],"bugs":["Fixed `tracer.transactionNestProxy` to create a new transaction if there is no transaction or transaction is not active"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Assigned all attributes on internal spans to segment (#3000 ) (5403018 ) Bug fixes Fixed tracer.transactionNestProxy to create a new transaction if there is no transaction or transaction is not active (#3007 ) (ced9e22 ) Documentation Updated compatibility report (#2993 ) (cdfa042 ) Tests Fixed handling require esm for >20.19.0+ (#3002 ) (b808e00 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-16-1","eolDate":"2026-03-24"},{"agent":"nodejs","date":"2025-03-17","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.16.0","features":["Added support for response streaming Lambda functions","Added AWS entity linking segment attributes for otel bridge","Added error handling on transactions for otel spans"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for response streaming Lambda functions (#2981 ) (61dbbf9 ) Added AWS entity linking segment attributes for otel bridge (#2978 ) (6bf1ccc ) Added error handling on transactions for otel spans (#2985 ) (4e61e09 ) Code refactoring Updated span event generation to assign the appropriate span.kind based on the segment name (#2976 ) (697b17e ) Documentation Updated compatibility report (#2988 ) (ed17a6d ) Miscellaneous chores Clarified supported next.js middleware versions in docs (#2984 ) (15cb454 ) Clarified system metrics sampler naming (#2987 ) (8647d43 ) Refactored loops to be simpler (#2990 ) (79fb8e9 ) Removed unused transaction method (#2986 ) (cb4e2f7 ) Reverted restriction in NestJS versioned tests (#2979 ) (ffddcab ) Tests Fixed fastify assertions around span kind while running security agent (#2983 ) (c641645 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-16-0","eolDate":"2026-03-17"},{"agent":"nodejs","date":"2025-03-03","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.15.0","features":["Added server span transaction naming fallback to the url.path","Updated Context class to ensure bi-directional context propagation with opentelemetry bridge","Added ability to propagate traceparent and tracestate on incoming server/consumer spans and outgoing client http and producer spans","Allowed undici error reporting to be disabled with feature flag `undici_error_tracking`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Allowed undici error reporting to be disabled with feature flag undici_error_tracking (#2956 ) (6278107 ) Thanks for your contribution @Voziv :tada: Added ability to propagate traceparent and tracestate on incoming server/consumer spans and outgoing client http and producer spans (#2958 ) (258ad7d ) Added server span transaction naming fallback to the url.path (#2966 ) (770bf6f ) Updated Context class to ensure bi-directional context propagation with opentelemetry bridge (#2962 ) (dfeec5a ) Code refactoring Separated context classes for agent in standard and opentelemetry bridge mode (#2967 ) (d11c071 ) Documentation Updated compatibility report (#2973 ) (7106c81 ) Miscellaneous chores Added consumer attribute reconciliation (#2957 ) (8943672 ) Added http external span attributes (#2955 ) (ef697a5 ) Limit nestjs to enable successful CI (#2972 ) (e9699cf ) Refactored otel attribute reconciling (#2964 ) (1b5ed2c ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-15-0","eolDate":"2026-03-03"},{"agent":"nodejs","date":"2025-02-18","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.14.0","features":["Added attribute reconciliation for message producer spans","Added timeslice metrics for synthesized consumer segments","Added support for region-prefixed Bedrock models"],"bugs":["Fixed undici/fetch instrumentation to properly assign the parent-id portion of the `traceparent` header on outgoing requests to the active http external span id","Updated `api.recordLogEvent` to no longer truncate the message key in log event","Fixed queueing of logs from child loggers"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for region-prefixed Bedrock models (#2947 ) (6acf535 ) Added attribute reconciliation for message producer spans (#2942 ) (a9ba396 ) Added timeslice metrics for synthesized consumer segments (#2938 ) (acfe953 ) Bug fixes Fixed queueing of logs from child loggers (#2945 ) (888cfe8 ) Fixed undici/fetch instrumentation to properly assign the parent-id portion of the traceparent header on outgoing requests to the active http external span id (#2951 ) (bc714cf ) Updated api.recordLogEvent to no longer truncate the message key in log event (#2949 ) (8dd557b ) Thanks for your contribution @rChaoz 🎉 Documentation Updated compatibility report (#2948 ) (8e32ed7 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-14-0","eolDate":"2026-02-18"},{"agent":"nodejs","date":"2025-02-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.13.0","features":["Propagate agent root context when opentelemetry `ROOT_CONTEXT` is passed in to trace propagator.","Added timeslice metrics for synthesized producer segments","Added timeslice metrics for synthesized server segments","Added timeslice metrics for synthesized database segments","Provided ability to disable instrumentation for core Node.js libraries"],"bugs":["Fixed `api.getTraceMetadata` to handle when there is an active transaction but not active segment"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added timeslice metrics for synthesized server segments (#2924 ) (f404585 ) Added timeslice metrics for synthesized producer segments (#2939 ) (6832637 ) Added timeslice metrics for synthesized database segments (#2922 ) (8606f78 ) Propagate agent root context when opentelemetry ROOT_CONTEXT is passed in to trace propagator.(#2940 ) (b85111c ) Added logic to handle properly naming and ending transactions for server spans. Provided ability to disable instrumentation for core Node.js libraries (#2927 ) (2d232f1 ) Bug fixes Fixed api.getTraceMetadata to handle when there is an active transaction but not active segment (#2944 ) (6db3b4d ) Documentation Updated compatibility report (#2920 ) (c7ae8be ) Miscellaneous chores Localized OTEL attribute constants (#2928 ) (965c41b ) Updated import-in-the-middle version (#2923 ) (aa2781f ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-13-0","eolDate":"2026-02-12"},{"agent":"nodejs","date":"2025-02-05","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.12.0","features":["Added health check support for upcoming feature","Added opentelemetry bridge instrumentation that adds a context manager, and processor to handle synthesizing segments and time slice metrics."],"bugs":["Updated default config to accept `undefined` as default value"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added health check support for upcoming feature (#2841 ) (4c8bf13 ) Added OpenTelemetry bridge instrumentation, which includes a context manager and processor to handle synthesizing segments and time-slice metrics (#2906 ) (d2e8a9e ) Bug fixes Updated default config to accept undefined as default value (#2917 ) (e049442 ) Documentation Updated compatibility report (#2914 ) (acd0c90 ) Miscellaneous chores Added regex note to SQL obfuscator (#2911 ) (1533111 ) deps:  Updated @newrelic/security-agent to v2.3.0 (#2918 ) (ed89f38 ) Continuous integration Optimized the Lambda layers and Kubernetes init containers post-release workflow (#2915 ) (4be1099 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-12-0","eolDate":"2026-02-05"},{"agent":"nodejs","date":"2025-01-29","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.11.3","features":[],"bugs":["Fixed transaction-shim to properly create new transactions when the existing transaction is not active","Fixed issue with `bluebird` and `when` instrumentation where checking active context crashed when transaction prematurely ends"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Fixed issue with bluebird and when instrumentation where checking active context crashed when transaction prematurely ends (#2909 ) (4a30d5c ) Fixed transaction-shim to properly create new transactions when the existing transaction is not active (#2912 ) (3ad8c59 ) Documentation Updated compatibility report (#2902 ) (cb16516 ) Miscellaneous chores Updated lint rule suppression comment (#2895 ) (559dc98 ) Continuous integration Move init container release from lambda to GHA (#2848 ) (8d8608d ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-11-3","eolDate":"2026-01-29"},{"agent":"nodejs","date":"2025-01-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.11.2","features":["Added support for Claude 3+ Chat API in Bedrock"],"bugs":["Added defensive code in shim to prevent crashing when checking parent segment"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for Claude 3+ Chat API in Bedrock (#2870 ) (6a83abf ) Bug fixes Added defensive code in shim to prevent crashing when checking parent segment (#2898 ) (751eb96 ) Documentation Updated compatibility report (#2888 ) (dce9deb ) Miscellaneous chores Replaced backtracking regex with new algorithm (#2887 ) (46462d0 ) Tests Improved test coverage of normalizing claude 3 messages (#2893 ) (cc65763 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-11-2","eolDate":"2026-01-23"},{"agent":"nodejs","date":"2025-01-16","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.11.1","features":[],"bugs":["Updated undici instrumentation to fix crash with trying to calculate exclusive duration on a segment that no longer exists"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated undici instrumentation to fix crash with trying to calculate exclusive duration on a segment that no longer exists (#2884 ) (3b7e4bf ) Documentation Updated compatibility report (#2878 ) (e784f84 ) Miscellaneous chores Fixed dns integration tests (#2883 ) (dd30ad7 ) Tests Restored the branch to test apollo-server-plugin to main (#2879 ) (978faab ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-11-1","eolDate":"2026-01-16"},{"agent":"nodejs","date":"2025-01-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.11.0","features":["Added otel consumer span processing","Added segment synthesis for internal spans","Added segment synthesis for otel producer spans","Added segment and transaction synthesis for http server spans","Added segment synthesis for db client otel spans to db trace","Added segment synthesizer and provided ability to convert http client otel spans to external http trace segments","Added segment tree to transaction trace","Removed children from segments.","Removed transaction from segment. Introduced a new enterSegment and enterTransaction to make context propagation more clear"],"bugs":["Updated `shim.createSegment` and `shim.handleMqTracingHeaders` to be backwards compatible with the changes to context manager"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Removed transaction from segment. Introduced a new enterSegment and enterTransaction to make context propagation more clear (#2646 ) (d84531a ) Removed children from segments. (#2689 ) (66f140f ) Added segment tree to transaction trace (#2717 ) (8fcc239 ) Added segment synthesizer and provided ability to convert http client otel spans to external http trace segments (#2745 ) (c42f8e6 ) Added otel consumer span processing (#2854 ) (82fe9d5 ) Added segment and transaction synthesis for http server spans (#2833 ) (8fa4d05 ) Added segment synthesis for db client otel spans to db trace (#2820 ) (1ad1858 ) Added segment synthesis for internal spans (#2840 ) (436c63d ) Added segment synthesis for otel producer spans (#2839 ) (30f4995 ) Bug fixes Updated shim.createSegment and shim.handleMqTracingHeaders to be backwards compatible with the changes to context manager (#2844 ) (554b4bf ) Code refactoring Removed class construction on the segment synthesis and instrumentation (#2837 ) (4b7ec0f ) Documentation Updated compatibility report (#2869 ) (4bde427 ) Miscellaneous chores Added rules engine to match OTEL spans (#2694 ) (2c93c68 ) Updated rules engine to account for fallbacks (#2831 ) (19fbdfb ) Updated versioned tests docs (#2874 ) (73a84d7 ) Tests Updated a langchain test to be less rigid on asserting the tracking metric by @langchain/core version (#2876 ) (73985ea ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-11-0","eolDate":"2026-01-14"},{"agent":"nodejs","date":"2025-01-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.10.0","features":["Added instrumentation for `@opensearch-projects/opensearch` v2.1.0+"],"bugs":["Fixed event matcher to use properties specific to web requests (v1/ALB and v2)"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added instrumentation for @opensearch-projects/opensearch v2.1.0+ (#2850 ) (763c0e6 ) Bug fixes Fixed event matcher to use properties specific to web requests (v1/ALB and v2) (#2863 ) (a93fe6e ) Miscellaneous chores Fixed mysql2 tests for new mysql2 version (#2853 ) (30a6de0 ) Updated eslint configuration (#2851 ) (d2fba9d ) Utilize updated @newrelic/eslint-config (#2865 ) (f53d4fc ) Tests Removed t.diagnostic from tests (#2858 ) (23ca237 ) Continuous integration Updated codecov-action to latest released version sha (#2866 ) (75f8902 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-10-0","eolDate":"2026-01-09"},{"agent":"nodejs","date":"2024-08-15","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.1.1","features":[],"bugs":["Updated `amqplib` instrumentation to properly parse host/port from connect","Updated `redis` instrumentation to parse host/port when a url is not provided","Updated the `kafkajs` node metrics to remove `/Named` from the name"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated amqplib instrumentation to properly parse host/port from connect (#2461 ) (91636a8 ) Updated redis instrumentation to parse host/port when a url is not provided (#2463 ) (2b67623 ) Updated the kafkajs node metrics to remove /Named from the name (#2458 ) (37ce113 ) Code refactoring Updated pino instrumentation to separate the wrapping of asJson into its own function (#2464 ) (81fdde1 ) Documentation Updated compatibility report (#2460 ) (a4570e9 ) Miscellaneous chores Removed limit on superagent versioned testing (#2456 ) (b4b6a6b ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Node.js agent EOL policy for information about agent releases and support dates .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-1-1","eolDate":"2025-08-15"},{"agent":"nodejs","date":"2024-08-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.1.0","features":[],"bugs":["Pick log message from merging object in Pino instrumentation","Added TLS verification for Redis"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Pick log message from merging object in Pino instrumentation (#2421 ) (599072b ) Added TLS verification for Redis (#2446 ) (9a16b70 ) Documentation Updated compatibility report (#2440 ) (32abe5f ) Updated examples to properly use specs (#2422 ) (f7e8c58 ) Fixed typo in doc header (#2433 ) (9726e23 ) Miscellaneous chores Added entity relationship attributes to SQS segments (#2436 ) (578aead ) Converted agent unit tests to node:test (#2414 ) (b32f793 ) Fixed mongodb-esm tests in combination with security agent (#2444 ) (5d617de ) Limited superagent tests to avoid new breaking release (#2439 ) (f1dd8e7 ) Removed promise resolvers from callback based agent unit tests (#2450 ) (3766895 ) Tests Moved pkgVersion to collection-common to avoid a conflict with ESM tests (#2438 ) (7260fa3 ) Restored mongodb-esm tests (#2434 ) (67a12e3 ) Updated custom test reporter to only log failed tests when there are failures (#2425 ) (baa37ec ) Updated tls redis tests to work with older versions of redis v4 (#2454 ) (ffd9b17 ) Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Node.js agent EOL policy for information about agent releases and support dates .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-1-0","eolDate":"2025-08-12"},{"agent":"nodejs","date":"2024-07-31","downloadLink":"https://www.npmjs.com/package/newrelic","version":"12.0.0","features":["Added `server.address` to amqplib spans","Removed support for `redis` less than 2.6.0","Removed legacy context manager","Removed instrumentation for `director`","Updated `mongodb` instrumentation to drop support for versions 2 and 3","Dropped support for Node.js 16","Migrated instrumentation for `next` into agent"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes ⚠ BREAKING CHANGES Dropped support for Node.js 16 Removed legacy context manager Removed support for redis less than version 2.6.0 Removed instrumentation for director Updated mongodb instrumentation to drop support for versions 2 and 3 Features Dropped support for Node.js 16 (#2394 ) (1870010 ) Removed legacy context manager (#2404 ) (321244c ) Removed support for redis less than version 2.6.0 (#2405 ) (e2c0a31 ) Removed instrumentation for director (#2402 ) (1b355e7 ) Added server.address to amqplib spans (#2406 ) (09636a4 ) Updated mongodb instrumentation to drop support for versions 2 and 3 (#2398 ) (a0ae32a ) Migrated instrumentation for next into agent (#2409 ) ([b55d8e1](https://github.com/newr     elic/node-newrelic/commit/b55d8e1ca09e6055ea09f4fcd773a05245e7203f)) You no longer need to load Next.js instrumentation via @newrelic/next. Instead you must load the agent via NODE_OPTIONS='-r newrelic' next start Documentation Updated compatibility report (#2401 ) (a53085d ) Miscellaneous chores Added test configs for defined targets in the aws test suite (#2403 ) (cf514d9 ) Added producer and consumer metrics to kafkajs instrumentation (#2407 ) (41c1cc6 ) Switched to using Node built-in test runner (#2387 ) (b9f64b7 ) Updated @newrelic/native-metrics to 11.0.0 (#2412 ) (aef69e2 ) Updated dashboard links in developer-setup.md (#2397 ) (16866da ) Verified MySQL host:port metric is recorded (#2400 ) (74176f7 ) Tests Removed mongodb-esm tests as they are not atomic and conflicting with mongodb tests in CI (#2416 ) (e587b9d ) Updated minimum version of lesser used versions of 3rd party libraries (#2399 ) (ef8c006 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-0-0","eolDate":"2025-07-31"},{"agent":"nodejs","date":"2015-05-06","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.19.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Features Filesystem interactions are now recorded in metrics The time spent in filesystem functions during a transaction will now be displayed in the transaction overview  page per operation. Bugfixes Fixed a bug with error handling. Previously the agent could crash applications in certain situations where null was thrown rather than an Error object.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1190","eolDate":"2018-05-06"},{"agent":"nodejs","date":"2015-05-01","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.18.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Bug fixes Fixed a bug in environment variable based configuration. Previously the agent would parse the NEW_RELIC_APDEX environment variable as a string rather than a float this could cause data to be sent to New Relic servers in an invalid format, preventing the data from being collected. Fixed a bug with the error collector's handling of ignored status codes. Previously the agent would not properly ignore status codes if the status code was set using a string rather than a number. Fixed a bug in mysql instrumentation. Previously the mysql instrumentation could cause errors when making mysql queries using an options object rather than a SQL string. The agent now handles arguments to the query method in a more robust way.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1185","eolDate":"2018-05-01"},{"agent":"nodejs","date":"2015-04-22","downloadLink":"https://www.npmjs.com/package/newrelic","version":"1.18.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixed an inverted if in config loading. Previously, the config loader would log a warning on success, rather than failure. Configuration loading works as expected now. Fixed a bug in process.nextTick instrumentation for io.js 1.8.1. Previously the agent would only pass the callback argument to process.nextTick. This did not cause issues in Node.js and older version of io.js, since additional arguments were ignored. In a recent change to io.js, process.nextTick was changed to pass any additional arguments to the callback, the same way setImmediate does. This change ensures all arguments are handled as expected.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1184","eolDate":"2018-04-22"},{"agent":"nodejs","date":"2015-03-27","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.18.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Reduce agent CPU overhead by omitting setImmediate from traces. The change to setImmediate makes that function behave the same way as nextTick and other frequently-called functions that are already elided from Transaction Traces. Mitigate a Node.js memory leak that can occur during TLS connections. There is an outstanding Node.js Core memory leak involving TLS connections. Clients specifying certificates, such as the New Relic Agent, quickly reveal this leak. We now mitigate this issue by using the default client certificates where possible. A new log message will be printed when the TLS memory leak workaround can not be used, such as when using a custom certificate with an HTTPS proxy.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1180","eolDate":"2018-03-27"},{"agent":"nodejs","date":"2015-03-19","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.17.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixed a bug where external requests report times longer than the transactions that initiated them. External request segments are now always ended when an error occurs. Fixed a bug that produced incorrect transaction names for some routes in express2 and express3.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1173","eolDate":"2018-03-19"},{"agent":"nodejs","date":"2015-03-12","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.17.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixed a bug that interfered with listing the routes in Express apps. Fixed a bug that caused custom transaction names to appear as \"unknown\". Added more log detail when instrumentation fails to load.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1172","eolDate":"2018-03-12"},{"agent":"nodejs","date":"2015-03-05","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.17.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Added instrumentation support for Node.js PostgreSQL driver pg 4.x. Added instrumentation support for Datastax's Cassandra driver. Updated Oracle instrumentation to collect new datastore metrics.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1171","eolDate":"2018-03-05"},{"agent":"nodejs","date":"2015-02-20","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.16.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixed a bug in the logger to respect the configured log level in all cases.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1164","eolDate":"2018-02-20"},{"agent":"nodejs","date":"2015-02-20","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.16.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Fixed a bug in hapi 8 view segments. Previously, the segments weren't being ended when the view ended. Added a configuration option to completely disable logging. logger.enabled defaults to true, if set to false it won't try to create the log file.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1163","eolDate":"2018-02-20"},{"agent":"nodejs","date":"2015-02-13","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.16.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Enable http/https proxy features on all supported Node versions. Supported versions: Node.js 0.8, 0.10, 0.12 and io.js 1.x. Fixed a bug in vhost detection in Hapi 8. This bug would result in a crash for users of vhosts.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1162","eolDate":"2018-02-13"},{"agent":"nodejs","date":"2015-02-06","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.16.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Now transaction tracing with synthetic monitoring is on by default. The previous release had the synthetic transaction tracing feature turned off by default.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1161","eolDate":"2018-02-06"},{"agent":"nodejs","date":"2015-02-06","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.16.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Added support for synthetic monitoring transaction tracing. Synthetic monitoring lets you monitor your site from around the world. When you use synthetics to monitor your Node application, up to 20 detailed transaction traces will now be captured every minute when the application is probed from synthetics. To learn more about this feature, visit our documentation .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1160","eolDate":"2018-02-06"},{"agent":"nodejs","date":"2015-01-30","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.15.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Preliminary Node.js 0.12 support. HTTP proxies are not supported on 0.12 yet. We don't recommend running the Agent on Node.js 0.11.15+ in production, but if you are testing on it, please let us know of any issues you encounter.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1151","eolDate":"2018-01-30"},{"agent":"nodejs","date":"2015-01-23","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.15.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes: Added an API for recording custom Insights events. Read more about this in our documentation","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1150","eolDate":"2018-01-23"},{"agent":"nodejs","date":"2015-01-16","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.14.7","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixed a crash in express instrumentation in the handling of sub-routers. Fixed a crash in http outbound connections when CAT is enabled and another library has frozen the http request headers. Updated version checking to allow versions of the runtime >= 1.0.0. Thanks to Mark Stosberg  for this patch!","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1147","eolDate":"2018-01-16"},{"agent":"nodejs","date":"2015-01-09","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.14.6","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes The agent now logs the actual error when log file parsing fails. Thanks to knownasilya  for this patch! Fixed a crash where config serialization would fail due to circular objects if domains were enabled.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1146","eolDate":"2018-01-09"},{"agent":"nodejs","date":"2014-12-30","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.14.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes: Errors that occur in background transactions now have custom parameters copied onto them in the same manner as web transactions. Memcached instrumentation has been updated to account for additional arguments that might be passed to the command function that the agent wraps.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1145","eolDate":"2017-12-30"},{"agent":"nodejs","date":"2014-12-22","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.14.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Custom web transactions can have their names changed by nr.setTransactionName(). Thanks to Matt Lavin  for this patch! Fixed a bug where Express instrumentation could crash if transaction state was lost in a sub router.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1144","eolDate":"2017-12-22"},{"agent":"nodejs","date":"2014-12-18","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.14.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Improved the Express instrumentation to be more defensive before doing property lookups, fixing a crash that could happen in an exceptional state. Improved logging when the New Relic agent cannot connect to New Relic servers. Make Cross Application Tracer header injection less aggressive fixing interaction with other libraries such as riak-js.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1143","eolDate":"2017-12-18"},{"agent":"nodejs","date":"2014-12-11","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.14.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Added support for Hapi v8. briandela  contributed a fix for an crash that would occur when using hapi with vhosts.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1142","eolDate":"2017-12-11"},{"agent":"nodejs","date":"2014-12-05","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.14.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Fixes Fixed a bug that caused some outbound http requests to show up in the New Relic UI as requests to localhost rather than the specified domain. The agent no longer reports errors from outbound http requests if they were handled by the user's application","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1141","eolDate":"2017-12-05"},{"agent":"nodejs","date":"2014-11-25","downloadLink":null,"version":"1.14.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 node agent now instruments connections to Oracle Databases using the oracle driver. This patch was contributed by ryanwilliamquinn Fixed an issue that would break kraken apps when the node agent was enabled. This patch was contributed by Lenny Markus","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1140","eolDate":"2017-11-25"},{"agent":"nodejs","date":"2014-11-20","downloadLink":null,"version":"1.13.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Added support for the the aggregate method on mongodb collections. This patch was contributed by taxilian","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1134","eolDate":"2017-11-20"},{"agent":"nodejs","date":"2014-11-13","downloadLink":null,"version":"1.13.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 a bug in Cross Application Tracing where the agent would sometimes attempt to set a header after headers had already been sent. Replaced the logger with one that is handles file writes properly lowering overall resource usage. This is a small change with a large impact. fs.createWriteStream returns whether data was queued or not. If it is queued it is recommended to wait on a drain event but this isn't mandatory. Most loggers we've found ignore this event which leads to many writes getting buffered and a rapid increase in native heap size as well as lowering the process's ability to respond to requests.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1133","eolDate":"2017-11-13"},{"agent":"nodejs","date":"2014-11-06","downloadLink":null,"version":"1.13.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Updated support for hapi 7.2 or higher. Hapi refactored how the server is instantiated and caused the agent to not be able to get transaction names. This release accounts for the update and enables full instrumentation.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1132","eolDate":"2017-11-06"},{"agent":"nodejs","date":"2014-11-06","downloadLink":null,"version":"1.13.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 This release was unpublished from npm due to a bad merge","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1131","eolDate":"2017-11-06"},{"agent":"nodejs","date":"2014-10-31","downloadLink":null,"version":"1.13.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Added support for Custom Metrics Custom metrics provides a way to send additional metrics up to New Relic APM, which can be viewed with Custom Dashboards. We have two APIs for this, recordMetric(name, value) and incrementMetric(name[, value]). Read more about Node.js custom metrics . Fixed a bug in deeply nested transactions. Previously we allowed transactions to be nested to any depth. We've found in some cases this causes stack depth problems and are now limiting to 900 segments per transaction. We will still collect metrics on all segments, but transaction traces will only show the first 900. Fixed a bug where custom tracers would show 0 time if the transaction ended n them. This may change the times you see for other types of tracers by a small amount. The change will reflect slightly more accurate timing.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1130","eolDate":"2017-10-31"},{"agent":"nodejs","date":"2014-10-23","downloadLink":null,"version":"1.12.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixed a bug that would cause the application to crash on outbound connections when using node 0.8. Fixed a bug that could sometimes cause the application to crash while parsing MySQL queries.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1122","eolDate":"2017-10-23"},{"agent":"nodejs","date":"2014-10-16","downloadLink":null,"version":"1.12.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Added support for Label Categories The agent now supports setting Labels for your application on a per instance level, using either an environment variable, or a config file setting. https://docs.newrelic.com/docs/apm/new-relic-apm/maintenance/categories-... Improved transaction names for express 4 express 4 added the ability to mount apps and routers at specific urls. The node agent would previously use only the portion of the route that was the last router or app matched as the transaction name. Transaction names will now include the entire matched route. Added detection for uninstrumented instances of modules that should be instrumented The agent will now detect if an application has required a module before require('newrelic') .If this occurs, the agent will add a warning in the log file and display a warning banner in the UI. Added more logging to custom instrumentation APIs at debug level. The logging was improved for the benefit of people using the following APIs: createTracer, createWebTransaction, createBackgroundTransaction, and endTransaction. It will log when transactions are created and when transactions are ended. It will also log when it can't create a tracer due to there being no active transaction. Fixed a bug in PostgreSQL instrumentation where the event emitter from query could not chain .on calls. This patch was contributed by sebastianhoitz . Fixed a bug in createBackgroundTransaction where if the agent was disabled it didn't take a group argument. This patch was contributed by nullvariable . Fixed a bug in our URL parsing where in Node v0.11.14 url.parse returns a differently shaped object than expected. This patch was contributed by atomantic Note : Node v0.11.x is not officially supported, but Node v0.12 will be and this patch helps us get ready for that.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1121","eolDate":"2017-10-16"},{"agent":"nodejs","date":"2014-10-10","downloadLink":null,"version":"1.12.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Added support for Cross Application Tracing The agent now supports Cross Application Tracing , which allows the New Relic APM UI to display traces that span multiple applications. Fixed a bug that would cause application to crash on request when using the kraken framework. Loosened the restrictions on the app_name setting. Application names may now include any Unicode characters.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1120","eolDate":"2017-10-10"},{"agent":"nodejs","date":"2014-10-06","downloadLink":null,"version":"1.11.5","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Fixed a type error while checking payload size before reporting to New Relic. When this occurred the agent would fail to send the payload to New Relic. This was more likely to occur in high throughput applications.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1115","eolDate":"2017-10-06"},{"agent":"nodejs","date":"2014-10-03","downloadLink":null,"version":"1.11.4","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixed a bug where mutibyte characters would cause an error when sending data to the New Relic servers.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1114","eolDate":"2017-10-03"},{"agent":"nodejs","date":"2014-09-26","downloadLink":null,"version":"1.11.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Updated hapi instrumentation to support the recently released v6.9. Fixed a bug where an invalid package.json could cause the agent to crash while it recursed through node_modules gathering version details. Properly name other SQL queries. Previously when the agent failed to parse SQL it would create a metric stating the database type, query type, and query table were all unknown. This has been changed to keep track of database type and create an appropriate other operation metric like other agents.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1113","eolDate":"2017-09-26"},{"agent":"nodejs","date":"2014-09-19","downloadLink":null,"version":"1.11.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Custom Instrumentation functions now pass through the return value of their passed in callback. Multiple improvements to PostgreSQL instrumentation When no callback was detected in the query functions, we were inserting our own. The insertion itself caused a crash. Adding a callback also modified the behavior of the pg module. Instead, we now listen for error or end events to finish segments. We now generate metrics for statement type/table combinations. Look for these in the database tab your APM Account!","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1112","eolDate":"2017-09-19"},{"agent":"nodejs","date":"2014-09-11","downloadLink":null,"version":"1.11.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Improved MongoDB find instrumentation. The mongo driver provides many ways to invoke its API and find documents. In previous releases, some API invocations would create transaction trace segments that would not end properly, leading to inaccurately large segment times. This release ensures the agent always instruments finding and iterating through documents, ensuring segment times are accurate.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1111","eolDate":"2017-09-11"},{"agent":"nodejs","date":"2014-09-05","downloadLink":null,"version":"1.11.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Improvements PostgreSQL support via the `pg` driver. The Node.js agent now records the amount of time spent in transactions with PostgreSQL databases. This timing can be viewed in the Transactions  page within individual transactions and their traces. The agent supports all of the following `pg` usage scenarios: Using the pure javascript API exposed directly from `pg` Using the \"native\" API exposed from `pg.native` Using the \"native\" API exposed directly from `pg` when the `NODE_PG_FORCE_NATIVE` environment variable is set Using the pure javascript API from the `pg.js` module","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1110","eolDate":"2017-09-05"},{"agent":"nodejs","date":"2013-11-09","downloadLink":null,"version":"1.1.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: Added support for key transactions and New Relic's new alerting policies. The agent no longer renames transactions for requests that end in error to the gnomic and unhelpful '400/*' (or whatever the final HTTP status code ends up being). This should make the traced errors tab considerably more useful. Improved instrumentation for legacy http.createClient and http.Client client methods. A few modules still use these legacy API calls, and the old instrumentation was just plain wrong. Changed how the error tracer deals with certain kinds of errors to deal with differences between Node versions 0.8 and 0.10. It should now convert throws into fatal errors less frequently. Removed useless fs.readDir instrumentation, which generated a lot of metrics but which New Relic was unable to display in any useful form. Maybe it will come back someday in a more useful incarnation.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-111","eolDate":"2016-11-09"},{"agent":"nodejs","date":"2014-08-28","downloadLink":null,"version":"1.10.3","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Removed a preemptive DNS lookup of the New Relic servers that could cause errors when behind a proxy.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1103","eolDate":"2017-08-28"},{"agent":"nodejs","date":"2014-08-25","downloadLink":null,"version":"1.10.2","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Fixes Fix to prevent proxy credentials transmission This update prevents proxy credentials set in the agent config file from being transmitted to New Relic.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1102","eolDate":"2017-08-25"},{"agent":"nodejs","date":"2014-08-22","downloadLink":null,"version":"1.10.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 . Improvements MySQL Pooling Support Better support for mysql pooling, including connections that use createPoolCluster and createPool. Previously connections obtained through a pool could potentially be uninstrumented.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1101","eolDate":"2017-08-22"},{"agent":"nodejs","date":"2014-08-15","downloadLink":null,"version":"1.10.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Custom instrumentation The agent now allows you to annotate your application code to provide customized instrumentation. This includes the ability to time both web and background transactions, and add tracers to measure activity within transactions like querying a database. For more information, see custom instrumentation","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-1100","eolDate":"2017-08-15"},{"agent":"nodejs","date":"2013-11-06","downloadLink":null,"version":"1.1.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: Added a new call to the API, .noticeError. See the docs  for details, but unlike the other calls on the API, you can use this to pass off errors anywhere in your app, not just from within web requests. Ignoring slow (or polling) requests was only being applied to slow transaction traces. It now applies to metrics and transactions that end in errors. MongoDB, Redis and Memcached now honor the capture_params and ignored_params settings. New Relic for Node.js, like New Relic's other agents, has a sophisticated system for repeatedly trying to connect to New Relic's servers when the first attempt results in failure. This had been broken since (roughly) January. It works again now. The built-in debugging for the transaction tracer was out of date with respect to the production tracer. This is fixed, and you're welcome to satisfy your curiosity by enabling it, but it's really not going to be useful to you unless you feel like taking the time to understand what the tracer is doing at a low level. Do not ever enable it in production, as it degrades the tracer's performance and generates a huge pile of objects per transaction.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-110","eolDate":"2016-11-06"},{"agent":"nodejs","date":"2024-01-10","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.9.0","features":["Assign pkgVersion and id of all child shim instances when using shim.makeSpecializedShim with a ConglomerateShim instance"],"bugs":["Dropped support for ElasticSearch &lt; 7.16.0","remove extra / in openai framework metric name"],"security":["bump follow-redirects from 1.15.2 to 1.15.4"],"supportedOperatingSystems":null,"description":"Notes Features Assign pkgVersion and id of all child shim instances when using shim.makeSpecializedShim with a ConglomerateShim instance (#1941 ) (d3e393d ) Bug fixes Dropped support for ElasticSearch < 7.16.0 (#1940 ) (e017768 ) Previously, New Relic's Node.js agent instrumented ElasticSearch as early as v7.13.0, which was susceptible to crashing when using ElasticSearch's .helper API. ElasticSearch fixed this bug in v7.16.0 , so we now support instrumentation from that version onward, and previous versions are noops. Removed extra /  in openai framework metric name (#1938 ) (7f586c3 ) Security improvements deps:  bump follow-redirects from 1.15.2 to 1.15.4 (#1942 ) (c1b04b6 ) Miscellaneous chores Removed assigning unused metadata to LLM events (#1932 ) (2f67d49 ) Tests Fixed DNS lookup in remote-method test (#1937 ) (4da2149 ) Removed console log (#1939 ) (7d378aa ) Updated abort controller test expected error message based on undici version (#1935 ) (3e79cc7 ) Updated chat-completions tests to properly assert segments (#1931 ) (10762a7 ) Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-9-0","eolDate":"2025-01-10"},{"agent":"nodejs","date":"2024-01-03","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.8.0","features":["Removed api.setLlmMetadata","Updated SQL obfuscation tokenizer to better handle negative numbers and boolean values"],"bugs":["Ensure opts.headers is defined in http instrumentation"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Removed api.setLlmMetadata (#1918 ) (cc4a975 ) Instead, the api.addCustomAttribute will have the llm prefix. The conversation_id will be assigned from llm.conversation_id custom attribute Updated SQL obfuscation tokenizer to better handle negative numbers and boolean values. Bug fixes Ensure opts.headers is defined in http instrumentation (#1926 ) (7ea31a3 ) Code refactoring Updated lib/instrumentation/core/http.js to reduce the cognitive complexity to an allowable value (#1922 ) (4c30d97 ) Updated lib/shim/promise-shim.js to reduce the cognitive complexity (#1924 ) (bd0a5dc ) Updated lib/shim/webframework-shim.js to reduce the cognitive complexity (#1927 ) (1ce371e ) Miscellaneous chores deps:  Updated @newrelic/security-agent to v0.6.0 (#1929 ) (4e09927 ) Tests Refactored tests now use tap if they still use the tap mocha shim + chai. (#1919 ) (957529e ) Removed access to deprecated req._headers and instead use req.headers (#1923 ) (0ec2f66 ) Updated the cross agent tests, made updates to tests based on fixture changes (#1917 ) (2d666b6 ) Updated helper.randomPort to use crypto.randomInt instead of Math.random by using crypto lib (#1921 ) (9003791 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date . See the New Relic Node.js agent EOL policy  for information about agent releases and support dates.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-8-0","eolDate":"2025-01-03"},{"agent":"nodejs","date":"2023-12-14","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.7.0","features":["Added instrumentation for Restify async handlers","Added deserialized X-NewRelic-Synthetics-Info header to transaction and transaction trace intrinsic attributes"],"bugs":["Update import-in-the-middle to fix ESM on Node 18.19.0"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added deserialized X-NewRelic-Synthetics-Info header to transaction and transaction trace intrinsic attributes (#1912 ) (7ed64bd ). The attributes in transactions are: nr.syntheticsType, nr.syntheticsInitiator, and nr.synthetics<attributeKey(s)>. The attributes in transaction traces are: synthetics_type, synthetics_initiator, and synthetics_<attribute_key(s)>. It will also include the X-NewRelic-Synthetics-Info header in outgoing http requests. Added instrumentation for Restify async handlers (#1910 ) (1a3f87f ). Bug fixes Update import-in-the-middle to fix ESM on Node 18.19.0 (#1906 ) (e9c3748 ). Code refactoring Change dynamic import to work with bundlers (#1905 ) (ee81429 ). Miscellaneous chores Add AWS Bedrock feature flag (#1913 ) (91019b0 ). Continuous integration Removed step in post release process to update an internal system with the latest agent version (#1909 ) (2080b1f ). Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date here . See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-7-0","eolDate":"2024-12-14"},{"agent":"nodejs","date":"2023-12-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.6.1","features":[],"bugs":["Updated @newrelic/aws-sdk to 7.0.3","Updated shimmer to handle instrumenting named and default exports of CommonJS modules in ESM"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes deps:  Updated @newrelic/aws-sdk to 7.0.3 (#1902 ) (bf22ae5 ) Updated shimmer to handle instrumenting named and default exports of CommonJS modules in ESM (#1894 ) (9f7979c ) Code refactoring Fixed cognitive complexity violations of openai instrumentation by moving functions outside of the parent function scope (#1895 ) (31dc717 ) Updated span names of openai actions to allow AI O11y team to locate relevant spans (#1896 ) (b7a644d ) Miscellaneous chores Improve OpenAI mock server streams (#1890 ) (d12bfe4 ) Tests Fix winston-esm versioned tests (#1898 ) (6e02e57 ) pin undici versioned below 6.0.0 on Node 16 (#1900 ) (9973b24 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-6-1","eolDate":"2024-12-07"},{"agent":"nodejs","date":"2023-11-29","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.6.0","features":["Added version tracking metric on OpenAI events","Added instrumentation for chat completion streams","Added pkgVersion to shim instances to facilitate semver checking without having to re-parse the package.json","Ensure openai errors are tracked","Added ai_monitoring configuration","Added instrumentation for openai embedding creation","Added API for tracking LLM feedback","Added instrumentation for openai chat completion creation","Added setLlmMetadata API to allow users to specify metadata for LLM events","Added openai LLM events.","Added configuration for openai instrumentation"],"bugs":["Updated isSimpleObject util to only check plain objects not arrays"],"security":["Set log file permissions to read/write for Node process only"],"supportedOperatingSystems":null,"description":"Notes Features Added instrumentation for openai. This feature is in limited preview and will be off by default. Aside from creating spans for chat completions and embeddings, it will create custom events that drive the New Relic AI Monitoring . Added instrumentation for chat completion streams (#1884 ) (404e317 ) Added instrumentation for openai chat completion creation (#1862 ) (34dcd70 ) Added instrumentation for openai embedding creation (#1872 ) (1c62321 ) Added ai_monitoring.enabled configuration.(#1873 ) (52bf9f3 ) Added Nodejs/ML/OpenAI/<version> metric every time a chat completion or embedding occurs.(#1886 ) (d11d100 ) Added setLlmMetadata API to allow users to specify metadata for LLM events (#1863 ) (85979d7 ) Ensure API errors are tracked (#1880 ) (289c2a2 ) Added getLlmMessageIds and recordLlmFeedbackEvent API methods for tracking LLM feedback (#1868 ) (1681e4b ) Added openai LLM events. (#1857 ) (a7786f3 ) Added pkgVersion to shim instances to facilitate semver checking without having to re-parse the package.json (#1883 ) (4ddfd81 ) Bug fixes Updated isSimpleObject util to only check plain objects not arrays (#1865 ) (8baa5bc ) Security improvements Set log file permissions to read/write for Node process only (#1854 ) (1b93ec9 ) Code refactoring Improved custom event attributes checking when using api.recordCustomEvent (#1870 ) (20e7f1d ) Miscellaneous chores dep:  Updated @newrelic/security-agent to v0.5.0 (#1877 ) (2882236 ) dev-deps:  bump axios and @slack/bolt (#1871 ) (2d00b02 ) docs:  Updated links in documentation to https (#1888 ) (f1913ea ) Fixed bool -> boolean in jsdoc (#1853 ) (3c00e55 ) Tests Added streaming responses to mock OpenAI sever (#1881 ) (86d83f2 ) Added unit tests for LLM API methods (#1878 ) (3d8b987 ) Added a mock server for openai testing (#1858 ) (3b1f5e6 ) Fixed shadowed variable lint error in pino versioned tests (#1859 ) (e1b21eb ) Updated openai versioned tests to properly work with the legacy context manager (#1876 ) (a879700 ) Continuous integration Made release note date always in pacific time (#1855 ) (6d7dc69 ) Remove updating staging with newly release agent version (#1887 ) (9d38faa ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-6-0","eolDate":"2024-11-29"},{"agent":"nodejs","date":"2023-10-30","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.5.0","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Miscellaneous chores dep:  Updated @newrelic/security-agent to v0.4.0 (#1837 ) (fb06ac9 ) Continuous integration Disable fail-fast on nightly versioned test runs (#1836 ) (fe1b4fc ) Support statement We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-5-0","eolDate":"2024-10-30"},{"agent":"nodejs","date":"2023-10-25","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.4.0","features":["Added support for parsing container ids from docker versions using cgroups v2."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for parsing container ids from docker versions using cgroups v2. (#1830 ) (9892901 ) Miscellaneous chores [Snyk] Upgraded @grpc/grpc-js from 1.9.2 to 1.9.4. (#1823 ) (81f9450 ) deps:  Updated aws-sdk, koa, superagent (#1831 ) (8b4e963 ) Tests Increased timeout for integration tests to avoid random failures. (#1827 ) (5202048 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-4-0","eolDate":"2024-10-25"},{"agent":"nodejs","date":"2023-10-23","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.3.0","features":["Updated agent initialization to allow running in worker threads when config.worker_threads.enabled is true"],"bugs":["Updated Elasticsearch instrumentation to register only on v7.13.0+"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Updated agent initialization to allow running in worker threads when config.worker_threads.enabled is true (#1817 ) (a39f0ef ) Bug fixes Updated Elasticsearch instrumentation to register on v7.13.0+ only (#1816 ) (6437671 ) Miscellaneous chores dev-deps:  Bumped @babel/traverse (#1818 ) (d3c8d04 ) Updated release note headers to follow standard sentence caps (#1806 ) (91d3600 ) Tests Updated the grpc versioned tests utils to dynamically bind ports to avoid conflicts between cjs and esm tests (#1820 ) (95ac917 ) Continuous integration Disabled fail-fast on testing jobs to make sure all versions are run before getting canceled because of a flappy test (#1819 ) (0928ee3 ) Updated CI workflow to use larger runners on versioned tests but only when running against the main branch (#1812 ) (01eaa14 ) Updated post release script to update the nodejs_agent_version only on staging and us prod, eu will get it via replication now (#1811 ) (317a00a ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-3-0","eolDate":"2024-10-23"},{"agent":"nodejs","date":"2024-07-22","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.23.2","features":["Added support for `fs.glob` in Node 22+"],"bugs":["Updated aws-sdk v3 instrumentation to load custom middleware last to properly get the external http span to add `aws.*` attributes","Updated cassandra-driver instrumentation to properly trace promise based executions"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for fs.glob in Node 22+ (#2369 ) (1791a4e ) Bug fixes Updated aws-sdk v3 instrumentation to load custom middleware last to properly get the external http span to add aws.* attributes (#2382 ) (751801b ) Updated cassandra-driver instrumentation to properly trace promise based executions (#2351 ) (bab9a8b ) Documentation Removed examples/api/ (#2381 ) (fb964de ) Removed out of date ROADMAP_Node.md from root of project (#2367 ) (4be870c ) Updated compatibility report (#2345 ) (f08adc3 ) Miscellaneous chores Always upload status logs in compatibility report CI (#2341 ) (b3f1ee3 ) Tests Removed server.start in grpc tests as it is deprecated and no longer needed (#2372 ) (d212b15 ) Updated benchmark test results to output result files (#2350 ) (1b51a68 ) Continuous integration Added benchmark test GitHub Action (#2366 ) (afd3ab4 ) Increased the limit of installs from 2 to a bigger number for versioned tests (#2346 ) (f85a385 ) Updated bin/create-docs-pr to create an empty array if changelog.json is missing security (#2348 ) (7d5368c ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-23-2","eolDate":"2025-07-22"},{"agent":"nodejs","date":"2024-07-11","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.23.1","features":[],"bugs":["Updated redis v4 instrumentation to work with transactions(multi/exec)"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated redis v4 instrumentation to work with transactions(multi/exec) (#2343 ) (39eb842 ) Documentation Updated compatibility report (#2342 ) (5c9e3e6 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-23-1","eolDate":"2025-07-11"},{"agent":"nodejs","date":"2024-07-10","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.23.0","features":["Added support for account level governance of AI Monitoring"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for account level governance of AI monitoring (#2326 ) (7069335 ) Code refactoring Removed redundant isExpected in the Exception class (#2328 ) (38f9825 ) Reduced duplication in the error-collector (#2323 ) (10581bf ) Refactored benchmark tests to complete async functions (#2334 ) (57a4dfb ) Documentation Included commands and links for Mac setup (#2327 ) (6eddb72 ) Updated compatibility report (#2318 ) (3a910ef ) Miscellaneous chores Fixed copy paste error in post release workflow (#2329 ) (6f2da7a ) Implemented split jobs for post release docs publishing (#2319 ) (c14ec3b ) Tests Fixed recordMiddlewawre benchmark test (#2338 ) (fb55ac7 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-23-0","eolDate":"2025-07-10"},{"agent":"nodejs","date":"2024-06-28","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.22.0","features":["Added supoort for Node 22","Added AIM support for Meta Llama3 models in AWS Bedrock"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for Node 22(#2305 ) (0bf8908 ) Added AIM support for Meta Llama3 models in AWS Bedrock (#2306 ) (ff2e509 ) Documentation Updated compatibility report (#2309 ) (7bf77c6 ) Miscellaneous chores Added @amychisholm03  to list of contributors 🎉 (#2310 ) (8a890f1 ) Forced re-creation of API docs on gh-pages (#2307 ) (917110a ) Tests Updated undici versioned tests to assert an error is present and not the actual message (#2299 ) (4e38ed4 ) Continuous integration Added Node 22 to CI (#2164 ) (4b12d9e ) Added Node 22 to smoke tests and nightly versioned test runs (#2316 ) (af00666 ) Moved the docs PR job to before api docs publish (#2300 ) (2e7252e ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-22-0","eolDate":"2025-06-28"},{"agent":"nodejs","date":"2024-06-25","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.21.0","features":["Added support for getting container ids from ECS metadata API"],"bugs":["Handled assigning headers in LambdaProxyWebRequest when there are no headers present"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for getting container ids from ECS metadata API (#2292 ) (dbca830 ) Bug fixes Handled assigning headers in LambdaProxyWebRequest when there are no headers present (#2293 ) (e4d22f3 ) Documentation Updated compatibility report (#2290 ) (b5fc893 ) Tests Fixed log error stack message truncating and failing equality test (#2294 ) (8e06f0f ) Updated shimmer method in benchmark tests (#2281 ) (1528d68 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-21-0","eolDate":"2025-06-25"},{"agent":"nodejs","date":"2024-06-24","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.20.0","features":["Added support for Anthropic Claude 3 messages API"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for Anthropic Claude 3 messages API (#2278 ) (7e3cab9 ) Code refactoring Replaced instances of substr() with substring() (#2274 ) (8f96c73 ) Documentation Fixed typos in API jsdoc (#2287 ) (7b3c8d1 ) Updated compatibility report (#2285 ) (b1b5e3e ) Miscellaneous chores Added a missing library we instrument to be picked up by the compatibility report (#2261 ) (6c964b2 ) Added a script that generates Dashboard json for reporting on libraries by version (#2267 ) (d2877c1 ) Added AI support docs for automation (#2249 ) (e2efc1f ) Fixed comment about transaction_tracer.transaction_threshold (#2258 ) (7cd6aef ) Made elastic versioned tests work on Node 16 (#2284 ) (143b475 ) Updated docker compose configuration (#2268 ) (eb1cce9 ) Updated GitHub Actions versions (#2272 ) (07a841b ) Updated mysql tests to use MySQL 8.3 (#2280 ) (11e0f8c ) Updated mysql2 tests to fix CI issue (#2282 ) (5a37971 ) Updated versioned security agent workflow with simpler setup (#2259 ) (a886187 ) Continuous integration Added ability to run a build step in create release (#2273 ) (4c2f24c ) Updated security agent workflow to use large runners when available (#2271 ) (181ec1b ) Updated security agent workflow to use large runners when available (#2270 ) (761fcd5 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-20-0","eolDate":"2025-06-24"},{"agent":"nodejs","date":"2023-10-12","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.2.1","features":[],"bugs":["Updated initialization to return the api on start up to the security agent properly"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated initialization to return the API on start up to the security agent properly (#1807 ) (99e5792 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-2-1","eolDate":"2024-10-12"},{"agent":"nodejs","date":"2023-10-11","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.2.0","features":["Added instrumentation for ElasticSearch."],"bugs":["Updated agent to create a stub api when running in a worker thread to avoid Next.js early return errors.","Updated shimmer to allow registering instrumentation for different versions of the same module."],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added instrumentation for ElasticSearch (#1785 ) (a748b84 ) Bug fixes Updated agent to create a stub api when running in a worker thread to avoid Next.js early return errors (#1800 ) (636e8f0 ) Updated shimmer to allow registering instrumentation for different versions of the same module (#1799 ) (30f0b16 ) Miscellaneous chores deps:  Updated @newrelic/security-agent to v0.3.0 (#1786 ) (9ca78ae ) Separated running versioned tests between local and external (#1792 ) (6ffe2f6 ) dev-deps  Updated get-func-name to fix CVE (#1790 ) (f378c77 ) Tests Updated elasticsearch container to ignore highwatermark to function on a constrained environment (#1803 ) (8380e9d ) Updated invalid json pino test as this was fixed in 8.15.1 of the pino library. (#1782 ) (3e65fdc ) Continuous integration Added steps to zip up container logs on versioned test failure (#1804 ) (0a54729 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-2-0","eolDate":"2024-10-11"},{"agent":"nodejs","date":"2024-06-06","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.19.0","features":["Added instrumentation for `kafkajs`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added instrumentation for kafkajs (enabled through a feature flag ) (#2237 ) (#2244 ) (#2236 ) (#2236 ) (#2251 ) Miscellaneous chores Added KafkaJS instrumentation and versioned tests skeleton (#2224 ) (fc13916 ) Added KafkaJS to compatibility list (#2254 ) (f003ee7 ) Implemented DT header injection for message specs (#2250 ) (3e6bc6d ) Removed targets for Kafka versioned tests (#2235 ) (838bab2 ) Updated flaky when test (#2241 ) (4079a0a ) Updated readme to remove no longer relevant information (#2240 ) (01fb53c ) Updated versioned tests due to update in @newrelic/security-agent V1.3.0 (#2239 ) (982276c ) Tests Migrated memcached tests to versioned tests (#2231 ) (0b3a928 ) Ported when and q integration tests to versioned tests (#2233 ) (9a4dddc ) Updated ioredis tests to assert the host metric getting created on ioredis calls (#2230 ) (89df06a ) Updated unit tests that were missing constructing specs at instrumentation source (#2252 ) (54ab238 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-19-0","eolDate":"2025-06-06"},{"agent":"nodejs","date":"2024-05-29","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.18.0","features":["Added support for redis v4 legacyMode `client.v4.<command>`"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added support for redis v4 legacyMode client.v4.<command> (#2200 ) (b2284c5 ) Code refactoring Updated shim.recordConsume to use shim.record and added ability to invoke an after hook with callback args (#2207 ) (4f48fc3 ) Documentation Updated compatibility report (#2223 ) (a256ca0 ) Miscellaneous chores Removed outdated Slack reference (#2198 ) (8110d42 ) Removed package-lock.json (#2208 ) (b267695 ) Removed unused express5 feature flag (#2197 ) (366504b ) Tests Updated langchain versioned tests to separate the vectorstore and other tests. This is to avoid peer resolution of @langchain/community package that is being used to test the elasticsearch vectorstore (#2216 ) (e768955 ) Fixed aws-sdk-v3 bedrock tests (#2211 ) (050469e ) Fixed aws-sdk-v3 bedrock tests (again) (#2212 ) (330cc4b ) Continuous integration Updated the langchain vectorstore test to reference the correct version of @langchain/core getting tested (#2202 ) (ed81852 ) Added updating of docs site with compatibility table (#2205 ) (c28a938 ) Fixed CI jobs (#2215 ) (8b030fb ) Fixed should-run CI step (#2214 ) (d0a481d ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-18-0","eolDate":"2025-05-29"},{"agent":"nodejs","date":"2024-05-15","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.17.0","features":["Added otel compliant `server.address`, `server.port`, and `http.request.method` to external http spans","Added otel compliant `db.system`, `server.address`, and `server.port` attributes to database spans"],"bugs":["Added support for AWS API Gateway v2 payloads","Reverted openai instrumentation update to handle broken version of 4.40.1","Updated instrumentation to handle the different exports in 4.40.1 of `openai`"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added otel compliant server.address, server.port, and http.request.method to external http spans (#2169 ) (b0a3e6d ) Added otel compliant db.system, server.address, and server.port attributes to database spans (#2173 ) (3fdcab4 ) Bug fixes Added support for AWS API Gateway v2 payloads (#2191 ) (0ccdc6a ) Code refactoring Updated instrumentation for http, undici, grpc to use a new segment.captureExternalAttributes to centralize the necessary data needed to create segment and span attributes (#2179 ) (ddb6356 ) Documentation Updated compatibility report (#2185 ) (eb986c9 ) Miscellaneous chores Added workflow for generating compatibility doc (#2183 ) (9b1d5cb ) Fixed conditionals in CI workflow (#2188 ) (6b733c0 ) Fixed superagent versioned tests (#2190 ) (297bc01 ) Made pre-commit hook require dependency changes (#2172 ) (e7bd356 ) Updated CI to skip expensive actions when not needed (#2184 ) (8639fb9 ) Updated validate-pr workflow (#2186 ) (6ff4497 ) Continuous integration Updated minimum version of lib-dynamo to work around peer dependency resolution (#2174 ) (7ddf2c9 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-17-0","eolDate":"2025-05-15"},{"agent":"nodejs","date":"2024-04-29","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.16.0","features":["Added API `ignoreApdex` to ignore calculating apdex for the active transaction","Migrated @newrelic/superagent into agent","Migrated @newrelic/aws-sdk into agent","Migrated @newrelic/koa into mainline agent"],"bugs":["Fixed issue with CJS being imported as ESM"],"security":["bump formidable and superagent"],"supportedOperatingSystems":null,"description":"Notes Features Added API ignoreApdex to ignore calculating apdex for the active transaction (#2166 ) (cb21d2c ) Bug fixes Fixed issue with CJS being imported as ESM (#2168 ) (9a14cb0 ) Security improvements deps:  bump formidable and superagent (#2162 ) (260f16b ) Documentation Fixed images in markdown tutorials (#2153 ) (ef14948 ) Includes api.js in jsdoc generation (#2139 ) (3883348 ) Miscellaneous chores Migrated @newrelic/superagent into agent repo (#2141 ) Migrated @newrelic/aws-sdk into agent repo (#2161 ) (a9eb593 ) Migrated @newrelic/koa into mainline agent repo (#2148 ) (33af646 ) Removed repetitive cache busting (#2160 ) (5ac870e ) Updated instrumentation to use type constants instead of raw strings (#2165 ) (c5b42cd ) Updated versioned tests readme (#2159 ) (a957304 ) Updated versioned tests to support upcoming tooling (#2147 ) (38e47d9 ) Updated versioned tests to use quiet output mode (#2145 ) (63a5ddc ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-16-0","eolDate":"2025-04-29"},{"agent":"nodejs","date":"2024-04-09","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.15.0","features":[],"bugs":["Fixed instrumenting the same module installed in different locations"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Fixed instrumenting the same module installed in different locations (#2104 ) (88bdace ) Code refactoring mongodb:  Removed instrumentation that handles connecting via unix domain socket. (#2129 ) (808323f ) Updated shim classes to no longer construct specs. (#2096 ) (158c295 ) Miscellaneous chores deps-dev:  Bumped express from 4.18.2 to 4.19.2 (#2101 ) (639cb78 ) deps:  Updated @newrelic/security-agent to v1.1.1 (#2092 ) (3272aa3 ) Fixed incorrect pinning of @elastic/transport (#2120 ) (7b5bdaa ) Removed scrollbar styling in generated API docs (#2091 ) (cb0fa11 ) Removed transaction_id and legacy token count attributes from llm events for openai and langchain (#2093 ) (df2a0fd ) Tests Updated test/integration/core/dns reverse test to remove flakiness (#2121 ) (c32cb27 ) Updated elastic tests to skip broken version (#2119 ) (5d0d1bb ) Continuous integration Removed usage of use_new_release from prepare release workflow (#2124 ) (007ddb4 ) Updated prepare-release.js to not require changelog.json (#2106 ) (328a570 ) Updated prepare release to provide a drop down for release type (#2133 ) (846269b ) Updated versioned security agent workflow (#2100 ) (f787b15 ) Fixed typo in constant name for prepare release script (#2094 ) (3b887d9 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-15-0","eolDate":"2025-04-09"},{"agent":"nodejs","date":"2024-03-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.14.0","features":["Added instrumentation for `initializeUnorderedBulkOp`, and `initializeOrderedBulkOp` in mongodb 4+","Added support for Mongo v5+","Added `guid` attribute to `TransactionError` events"],"bugs":[],"security":["bump follow-redirects from 1.15.5 to 1.15.6"],"supportedOperatingSystems":null,"description":"Notes Features Added guid attribute to TransactionError events (#2079 ) (3468fb1 ) Added instrumentation for initializeUnorderedBulkOp, and initializeOrderedBulkOp in mongodb 4+ (#2086 ) (666ae6e ) Added support for Mongo v5+ (#2085 ) (00f6feb ) Security improvements deps:  bump follow-redirects from 1.15.5 to 1.15.6 (#2078 ) (aa86482 ) Documentation Changed bug bounty URL (#2081 ) (f4586d7 ) Miscellaneous chores Added instrumentation tracking class (#2084 ) (07d7e7d ) deps:  pin @newrelic/security-agent to 1.0.1 (#2089 ) (e133c76 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-14-0","eolDate":"2025-03-20"},{"agent":"nodejs","date":"2024-03-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.13.0","features":["Added setLlmTokenCountCallback API endpoint to register a callback for calculating token count when none is provided","Added tool_id to langchain error event","Added instrumentation for VectorStore.similaritySearch for langchain.js","Added token_count to LlmEmbedding and LlmChatCompletionMessage for openai"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added AI Monitoring(AIM) for OpenAI , Amazon Bedrock , and Langchain . To enable, set config.ai_monitoring.enabled or NEW_RELIC_AI_MONITORING_ENABLED to true. For a full experience, set config.span_events.max_samples_stored to 10000, config.custom_insights_events.max_samples_stored to 100000, and config.distributed_tracing.enabled should not be set to false. Note : Enabling high-security mode  will disable the AIM instrumentation and events. Added instrumentation for VectorStore.similaritySearch for langchain.js (#2049 ) (3c50606 ) Added setLlmTokenCountCallback API endpoint to register a callback for calculating token count when none is provided (#2065 ) (d2faf1a ) Added token_count to LlmEmbedding and LlmChatCompletionMessage for openai (#2061 ) (47a925e ) Added tool_id to Langchain error event (#2064 ) (793abe8 ) Miscellaneous chores Added flag for verbosity during docs publishing (#2060 ) (fe0d41a ) Added some delays to docs publishing (#2062 ) (a602fd4 ) Changed casing of OpenAI in vendor property (#2068 ) (64b4ca2 ) Changed token_count to only use tokenCountCallback (#2070 ) (66f94b0 ) Removed langchain_instrumentation feature flag as the instrumentation is feature complete (#2073 ) (925a463 ) updated @newrelic/aws-sdk and @newrelic/koa to latest (#2074 ) (0747ca4 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-13-0","eolDate":"2025-03-13"},{"agent":"nodejs","date":"2024-03-04","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.12.0","features":["Added instrumentation for `chain.stream` for langchain js."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added instrumentation for chain.stream for langchain js. (#2052 ) (03abfce ) Miscellaneous chores Added @azure/openai and @langchain/community/llms/bedrock as tracking packages so we can measure usage with angler (#2053 ) (4830ea3 ) Tests Updated aws-sdk branch to main as the necessary code was merged. (#2051 ) (1e52a5c ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-12-0","eolDate":"2025-03-04"},{"agent":"nodejs","date":"2024-02-27","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.11.0","features":["Added ability to recordLlmFeedbackEvent by traceId","Add LangChain error events capture","Add instrumentation for RunnableSequence","Added instrumentation for langchain tools.","Added `ai_monitoring.streaming.enabled`. When set to `false` this will not instrument chat completion streams, thus it will not create relevant Llm events."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added instrumentation for RunnableSequence (#1996 ) (71ffa37 ) Added LangChain error events capture (#2040 ) (4d0d839 ) Added ai_monitoring.streaming.enabled. When set to false this will not instrument chat completion streams, thus it will not create relevant Llm events. (#2021 ) (ff78b51 ) Added ability to recordLlmFeedbackEvent by traceId (#2043 ) (b0a4ed1 ) Added instrumentation for langchain tools. (#2009 ) (695d10e ) Code refactoring Updated AIM instrumentation (#2015 ) (d37d2a8 ) removed capturing last 4 of api key included all custom attributes prefixed with llm. as attributes on all Llm events changed tracking metric to start with Supportability Updated capturing conversation_id on Llm Events as llm.conversation_id (#2020 ) (5f93f65 ) Updated instrumentation to construct specs at source instead of within the shim methods (#2035 ) (ead8c25 ) Simplified the logic in shim.recordQuery and shim.recordOperation to reduce merging of spec properties and rely on the constructed spec Documentation Added note about using sudo for firewall script (#2032 ) (bf106d2 ) Fixed spec objects parameter definitions (#2024 ) (4378173 ) Miscellaneous chores Added missing is_response to LangChain completion messages (#2044 ) (20c7d47 ) Attached specs to the Shim.prototype for use in custom instrumentation and instrumentation outside of the agent (#2038 ) (2c97488 ) deps:  Updated to use @newrelic/ritm from require-in-the-middle (#2034 ) (ffb729f ) Updated DatastoreParameters to include collection (#2039 ) (b9c73ca ) Tests Cleaned up pending mocks in the log dropping test to avoid a console warning around pending mocks in after each (#2017 ) (d2f40c2 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-11-0","eolDate":"2025-02-27"},{"agent":"nodejs","date":"2024-02-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.10.4","features":[],"bugs":["Resolved application logs getting blocked when an excessive payload is encountered","Updated Shim to properly calculate the _moduleRoot on windows environments"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Resolved application logs getting blocked when encountering an excessive payload (#2013 ) (365ded4 ) Updated Shim to properly calculate the _moduleRoot on Windows environments (#2014 ) (ab0bd7f ) Code refactoring Abstracted registering of new aggregators into a Harvester class that's responsible for starting, stopping, and updating all registered aggregators. (#1994 ) (1fb85a6 ) Refactored specs into classes for easier code navigation (#2004 ) (4daedc0 ) Miscellaneous chores deps:  Updated @newrelic/security agent to v1.0.1 (#2002 ) (b460c7b ) Tests Updated smoke tests to send data to the appropriate collector method (#2005 ) (6130486 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-10-4","eolDate":"2025-02-13"},{"agent":"nodejs","date":"2024-02-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.10.3","features":["Add vectorsearch entities","Add message entities for LangChain","Add feature flag for LangChain instrumentation"],"bugs":["Updated grpc-js instrumentation to properly track errors and end transactions"],"security":[],"supportedOperatingSystems":null,"description":"Features Added feature flag for LangChain instrumentation (#1990 ) (ab04e7a ) Added message entities for LangChain (#1983 ) (6b44a3a ) Added vectorsearch entities (#1992 ) (ef74b2e ) Bug fixes Updated grpc-js instrumentation to properly track errors and end transactions (#2001 ) (fda1346 ) Documentation Removed documentation around aws_bedrock_instrumentation as feature flag has been removed (#1991 ) (f414564 ) Miscellaneous chores Fixed third-party notices and package lock as they were out of sync. (#1999 ) (a89def8 ) Tests Updated prisma versioned test range to skip 5.9.0 as it was broken (#1993 ) (d885286 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. You can read more about keeping agents up to date in our documentation . For information about agent releases and support dates, please see our New Relic Node.js agent EOL policy documentation .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-10-3","eolDate":"2025-02-07"},{"agent":"nodejs","date":"2024-01-31","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.10.2","features":[],"bugs":["Updated winston instrumentation to wrap configure to properly retain our transporter to do log forwarding"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated winston instrumentation to wrap configure to properly retain our transporter to do log forwarding (#1987 ) (b54a97f ) Documentation Fixed jsdoc generation by marking private methods as @private  (#1976 ) (f33c0cc ) Miscellaneous chores Update eslint config (#1980 ) (8991a15 ) Tests Pinned prisma instrumentation testing to <5.9.0 until we can fix issues with instrumentation (#1985 ) (5eae6ee ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-10-2","eolDate":"2025-01-31"},{"agent":"nodejs","date":"2024-01-25","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.10.1","features":[],"bugs":["Updated instrumentation registration to allow for instrumenting of a local file that does not exist within node_modules."],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Updated instrumentation registration to allow for instrumenting of a local file that does not exist within node_modules. To properly instrument a local file, you must pass in absolutePath with the absolute path to the file that is being instrumented along with the moduleName which in this case is just the file name without the extension. (#1974 ) (f545b4e ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-10-1","eolDate":"2025-01-25"},{"agent":"nodejs","date":"2024-01-22","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.10.0","features":["Added transaction ID to ErrorTrace event","Added llm attribute to all transactions that contain llm spans for openai"],"bugs":[],"security":["Redacted ingest key in trace level logs"],"supportedOperatingSystems":null,"description":"Notes Features Added llm attribute to all transactions that contain llm spans for openai (#1946 ) (6312629 ) Added transaction ID to ErrorTrace event (#1954 ) (5d0ebcd ) Security improvements remote_method:  Redacted ingest key in trace level logs (#1948 ) (04fee88 ) Code refactoring Updated lib/shim/shim.js to remove cognitive complexity violations (#1950 ) (60e57a1 ) Updated message-shim to remove cognitive complexity violations. (#1958 ) (3d1caaf ) Miscellaneous chores deps:  Updated @newrelic/aws-sdk to latest and removed aws_bedrock_instrumentation feature flag (#1956 ) (9eae28c ) deps:  Updated @newrelic/security-agent to v0.7.0 (#1955 ) (e156539 ) Migrated non-sensitive CI values to vars (#1957 ) (1739378 ) updated contributors list to include james and svetlana 🎉 (#1947 ) (33a59fd ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-10-0","eolDate":"2025-01-22"},{"agent":"nodejs","date":"2023-09-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.1.0","features":["Added instrumentation for fetch.","Removed undici feature flag. This will now instrument undici by default.","Updated undici instrumentation to create segment on request create instead of after connection and opening socket to more accurately record time it takes to make an undici request."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added instrumentation for fetch. (#1776 ) (980b4dc ) Removed undici feature flag. This will now instrument undici by default. (#1772 ) (683b254 ) Updated undici instrumentation to create segment on request create instead of after connection and opening socket to more accurately record time it takes to make an undici request. (#1770 ) (3f494f8 ) Performance Improvements Trace:  optimise getTotalTimeDurationInMillis function to push to an array instead of concat arrays. (#1774 ) (6ecde97 ) Thanks @infinity-naveen for your contribution 🎉 Miscellaneous Chores Updated Next.js plugin versioned tests to use main now that require-in-the-middle fixes have been merged. (#1768 ) (6a72d1f ) Upgraded @newrelic/test-utilities and removed unused shimmer.patchModule and shimmer.unpatchModule (#1769 ) (96620ef ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-1-0","eolDate":"2024-09-07"},{"agent":"nodejs","date":"2023-08-28","downloadLink":"https://www.npmjs.com/package/newrelic","version":"11.0.0","features":["Added support for Node 20","Removed support for Node 14","Updated the default context manager to be AsyncLocalContextManager.","Renamed shim.handleCATHeaders to shim.handleMqTracingHeaders"],"bugs":["Updated prisma instrumentation to parse prisma datamodel with internal package.","Replaced ESM loader with import-in-the-middle to fix instrumentation firing for both CommonJS and ESM."],"security":[],"supportedOperatingSystems":null,"description":"Notes ⚠ BREAKING CHANGES Removed support for Node 14. Replaced ESM loader with import-in-the-middle to fix instrumentation firing for both CommonJS and ESM. You must load both the ESM loader and agent as follows: node --experimental-loader newrelic/esm-loader.mjs -r newrelic path/to/app.js. Removed config.esm.custom_instrumentation_entrypoint to register ESM instrumentation. You can now just call the newrelic.instrument* APIs but you must pass in an object and specify isEsm: true. See example . Updated agent to use require-in-the-middle to register CommonJS instrumentation. You can no longer use an onResolved hook to register custom instrumentation. Updated the default context manager to be AsyncLocalContextManager. Renamed shim.handleCATHeaders to shim.handleMqTracingHeaders. Updated agent to only run in the main thread. This is because running in a worker thread does not completely function out of the box. This will reduce the overhead for customers that are naively trying to load this into worker threads. Features Added support for Node 20. Renamed shim.handleCATHeaders to shim.handleMqTracingHeaders (#1735 ) (6788f9e ) If you have calls to shim.handleCATHeaders, the signature is identical and a function name change is only necessary. Note : The agent will be removing CAT functionality in an upcoming release. Updated the default context manager to be AsyncLocalContextManager (#1731 ) (25f2bd8 ) To restore functionality of legacy context manager you can set config.feature_flag.legacy_context_manager to true or `NEW_RELIC_FEATURE_FLAG_LEGACY_CONTEXT_MANAGER=true Please note this legacy context manager will be removed in future major releases. If you have any issues, please raise with New Relic support or on the issues  of the agent. Bug Fixes Replaced esm loader with import-in-the-middle to fix instrumentation firing for both commonjs and esm (#1760 ) (4452354 ), closes 1646 Breaking Change : Updated ESM loader that now requires to use both a loader and -r. node --experimental-loader newrelic/esm-loader.mjs -r newrelic path/to/app.js Breaking Change : Removed config.esm.custom_instrumentation_entrypoint to register ESM instrumentation. You can now just call the newrelic.instrument* APIs but you must pass in an object and specify isEsm: true. Updated prisma instrumentation to parse prisma datamodel with internal package (#1765 ) (48079b3 ) Code Refactoring Updated agent to use require-in-the-middle to register CommonJS instrumentation (#1758 ) (d4b4f11 ) Removed onResolved hook. If you're using custom instrumentation with an onResolved hook, you must update to use onRequire You can no longer instrument files that are not within a node_module unless you provide an absolute path to the file when registering the instrumentation. You cannot instrument both the base module and a sub module. Miscellaneous Chores Remove support for Node 14 (#1756 ) (0ff9912 ) Updated the bundled packages to the latest @newrelic/superagent, @newrelic/aws-sdk, @newrelic/koa, @newrelic/native-metrics, and @newrelic/test-utilities (#1766 ) (8f6e15b ) Updated the aws-sdk external branch to be main now that the code is in there (#1761 ) (d34d0fe ) Tests update smoke tests versioned matrix in CI to 16, 18, and 20. (#1762 ) (c82b517 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-11-0-0","eolDate":"2024-08-28"},{"agent":"nodejs","date":"2013-10-30","downloadLink":null,"version":"1.0.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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: Added a new setIgnoreTransaction call to the exported API to allow explicit control over whether transactions should be ignored or not. Mark those polling routes to be ignored! Pull your crazy custom favicon.ico renderer out of the ignore list! The module will no longer pollute MongoDB queries with New Relic-only parameters. Thanks to Alon Salant for identifying this issue, and all apologies to him for the trouble it caused him. The instrumentation for MongoDB, memcached, Redis, and Express will now honor the setting of the capture_params configuration flag. Before the module always captured query parameters. Fixed a problem that would cause New Relic for Node to fail on versions of Node between 0.8.0 and 0.8.3. Upgraded to the newest version of continuation-local-storage, which has many fixes for dealing with monkeypatched EventEmitters.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-101","eolDate":"2016-10-30"},{"agent":"nodejs","date":"2013-10-24","downloadLink":null,"version":"1.0.0","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"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 Availability release of the Node.js agent. Please review the news.md at the root of the project for all prior release notes. If you are using an older BETA version of the Node.js agent, please upgrade to the current version.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-100","eolDate":"2016-10-24"},{"agent":"nodejs","date":"2023-08-07","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.6.2","features":[],"bugs":["added defensive code around JSON.parse in formatting pino log lines because pino can return invalid json"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug Fixes added defensive code around JSON.parse in formatting pino log lines because pino can return invalid json (#1750 ) (8f2e11a ) Miscellaneous Chores deps:  Updated @newrelic/security-agent to v0.2.1 (#1754 ) (0d04f14 ) Fix smoke tests node 20 (#1745 ) (8c053e0 ) fixed typos in lib/config/index.js comments (#1749 ) (9000a14 ) Tests Added a full suite of unit tests for the collector/http-agents (#1748 ) (9d4201b ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-6-2","eolDate":"2024-08-07"},{"agent":"nodejs","date":"2023-08-01","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.6.1","features":[],"bugs":[],"security":["updated ESM loader to track instrumentation by url in a map instead of in url to avoid remote code execution."],"supportedOperatingSystems":null,"description":"Notes Security Improvements updated ESM loader to track instrumentation by url in a map instead of in url to avoid remote code execution. (#1741 ) (c8dc779 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-6-1","eolDate":"2024-08-01"},{"agent":"nodejs","date":"2023-07-26","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.6.0","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Miscellaneous Chores deps:  Updated @newrelic/security-agent to v0.2.0 (#1737 ) (9bf2a01 ) restored engines to >=14 until we actually drop support for Node 14 (#1738 ) (8d66123 ) Continuous Integration Add Node.js 20.x to CI and remove 14.x (#1603 ) (c4b008c ) update support statement (#1733 ) (3013da9 ) Support statement: We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/ ) See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/ )","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-6-0","eolDate":"2024-07-26"},{"agent":"nodejs","date":"2023-07-20","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.5.0","features":["enabled code_level_metrics by default"],"bugs":["prevent ESM loader from loading instrumentation multiple times"],"security":[],"supportedOperatingSystems":null,"description":"Notes Features enabled code_level_metrics by default (#1723 ) (0b96de3 ) Bug Fixes prevent ESM loader from loading instrumentation multiple times (#1729 ) (962d172 ) Miscellaneous Chores deps-dev:  bump word-wrap from 1.2.3 to 1.2.4 (#1730 ) (500a69e ) Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-5-0","eolDate":"2024-07-20"},{"agent":"nodejs","date":"2023-07-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.4.2","features":[],"bugs":["Dropped query params from request.uri attribute when obfuscating"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug fixes Dropped query params from request.uri attribute when obfuscating (#1719 ) (76112a6 ) Miscellaneous chores Created story issue template (#1694 ) (20442c6 ) Tests Pinned prisma to < 5 when running on node 14 (#1717 ) (b000d7b ) Support statement New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-4-2","eolDate":"2024-07-13"},{"agent":"nodejs","date":"2023-07-10","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.4.1","features":[],"bugs":[],"security":["bump protobufjs from 7.2.3 to 7.2.4"],"supportedOperatingSystems":null,"description":"Notes Security Improvements deps:  bump protobufjs from 7.2.3 to 7.2.4 (#1713 ) (5fb4606 ) Miscellaneous Chores test:  Converted adaptive-sampler.test.js to tap (#1709 ) (bb42249 ) test:  converted environment.test.js to tap (#1705 ) (53b4376 ) test:  Replaced t.equals with t.equal (#1711 ) (a0b255e ) Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-4-1","eolDate":"2024-07-10"},{"agent":"nodejs","date":"2023-06-30","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.4.0","features":[],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Miscellaneous Chores test:  Converted 'errors/expected.test.js' to tap-style (#1695 ) (86025de ) test:  Converted server-config.test.js to tap-style (#1702 ) (2c6906d ) Continuous Integration skip running test suite when merging releases (#1704 ) (f78b981 ) Build System updated @newrelic/aws-sdk to latest to get the instrumentation fixes for 3.363.0 (#1707 ) (a2cca08 ) Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-4-0","eolDate":"2024-06-30"},{"agent":"nodejs","date":"2023-06-26","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.3.2","features":[],"bugs":["check for query args in string property"],"security":["Updated security agent to v0.1.3","bump fast-xml-parser and @aws-sdk/client-lambda"],"supportedOperatingSystems":null,"description":"Notes Bug Fixes prisma:  check for query args in string property (#1684 ) (8d9b176 ) Security Improvements deps:  Updated security agent to v0.1.3 (#1696 ) (0f957bd ) Miscellaneous Chores test:  Added t.end() to trace unit test (#1698 ) (254c9c0 ) test:  convert error-trace-aggregator.test.js to tap-style (#1690 ) (44b17ab ) test:  convert trace unit test to tap style (#1692 ) (727c17f ) test:  Fixed tap end/autoend calls in trace unit test (#1700 ) (b4a4948 ) Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-3-2","eolDate":"2024-06-26"},{"agent":"nodejs","date":"2023-06-22","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.3.1","features":[],"bugs":[],"security":["Updated semver dependency to 7.5.2, also updating @newrelic/native-metrics, and @newrelic/test-utilities"],"supportedOperatingSystems":null,"description":"Notes Security deps:  Updated semver to v7.5.2, also in native-metrics and test utils (#1685 ) (e207a6b ) Miscellaneous Chores Added test for getRedisParams (#1670 ) (e9f8556 ) temporarily limit prisma tests to non-breaking version (#1680 ) (76d3ade ) testing:  convert query-test-aggregator tests to tap style (#1676 ) (d2e45ad ) testing:  Converted error-event-aggregator.test.js to tap (#1683 ) (9f1d66f ) Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-3-1","eolDate":"2024-06-22"},{"agent":"nodejs","date":"2023-06-13","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.3.0","features":["Added IAST security agent capabilities when security.agent.enabled is true"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added Interactive Application Security Testing(IAST) mode of security agent when config.security.agent.enabled is true. (#1664 ) (3e926e5 ) The New Relic Security agent IAST mode is in public preview and should only be used in non-production environments. To learn about how to use IAST, check out our documentation . To enable the security agent set config.security.agent.enabled and config.security.enabled to true. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-3-0","eolDate":"2024-06-13"},{"agent":"nodejs","date":"2023-06-06","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.2.0","features":["added supportability metrics to indicate how agent was loaded and if --enable-source-maps was passed to Node.js runtime","log execArgs at the debug level"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Features Added supportability metrics to indicate how agent was loaded and if source maps were enabled (#1657 ) (6f6f7e6 ) Supportability/Features/CJS/Preload - recorded if -r newrelic was used to load agent Supportability/Features/CJS/Require - recorded if require('newrelic') was used to load agent Supportability/Features/EnableSourceMaps - recorded if node --enable-source-maps was present to start application Added logging of process.execArgs at the debug level (#1654 ) (c85c006 ) Miscellaneous chores Updated c8 to merge v8 coverage reports asynchronously to avoid OOM issues (#1652 ) (34376d7 ) Updated explorer hub link in readme (#1656 ) (c1e81a7 ) Tests Added unit tests for MySQL instrumentation (#1649 ) (b693ba0 ) Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-2-0","eolDate":"2024-06-06"},{"agent":"nodejs","date":"2023-05-24","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.1.2","features":[],"bugs":["Updated mysql instrumentation to properly wrap the connection pool.getConnection and poolCluster.of"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug Fixes Updated mysql instrumentation to properly wrap the connection pool.getConnection and poolCluster.of (#1647 ) (4caf1db ) Added instrumentation to PoolNamespace.prototype.query Continuous Integration fix minor release note generation bugs (#1643 ) (dd6ab9a ) Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-1-2","eolDate":"2024-05-24"},{"agent":"nodejs","date":"2023-05-15","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.1.1","features":[],"bugs":["updated prisma instrumentation to properly parse database connection strings that work across all versions of prisma"],"security":[],"supportedOperatingSystems":null,"description":"Notes Bug Fixes updated prisma instrumentation to properly parse database connection strings that work across all versions of prisma (#1634 ) (b2101fd ) Code Refactoring run-versioned-tests.sh:  added ability to run versioned tests and skip collecting coverage by passing in SKIP_C8 env var to the job. (#1621 ) (0ba9dcb ) Documentation update Contribution Guide with Conventional Commit info (#1635 ) (f1a00e5 ) Miscellaneous Chores pin testdobule to 3.17.2 as 3.18.0 no longer works on node 14 (#1628 ) (d68bd9f ) remove release-please workflow and scripts (#1624 ) (80f7eb8 ) Tests pin prisma to 4.14.0 until we fix instrumentation (#1631 ) (a60659d ) scripts:  fix failing changelog unit test (#1626 ) (08f48b3 ) config:  increase test coverage (#1625 ) (67f39d8 ) config:  revert changes to lib/config/index.js (#1630 ) (fea1068 ) Continuous Integration changed versioned tests script to use SKIP_C8 (#1621 ) (83e95e3 ) add --use-new-release functionality (#1633 ) (d97b421 ) add ability to generate release notes from conventional commits (#1623 ) (880a88b ) create-docs-pr:  Set username/email to machine user by default (#1627 ) (3870a1f ) fix issue with missing type in the prep-release (#1638 ) (9a906e8 ) update prep-release to fetch entire history of caller repo (#1641 ) (428174a ) update to conditionally add CLI flag to prep-release (#1640 ) (b167c93 ) Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-1-1","eolDate":"2024-05-15"},{"agent":"nodejs","date":"2023-05-04","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.1.0","features":["Added batching and compression to infinite tracing.","Added official support for Nest.js"],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes Added batching and compression to infinite tracing. These options are on by default. To restore uncompressed spans set config.infinite_tracing.compression to false. To send single spans vs batches set config.infinite_tracing.batching to false. The environment variables for these new configurations are: NEW_RELIC_INFINITE_TRACING_BATCHING and NEW_RELIC_INFINITE_TRACING_COMPRESSION. Added support to record Nest.js error stack traces. Nest.js is officially supported via underlying instrumentation of express or fastify. Added job to create a release notes PR in the post-release workflow. Removed request library and updated helper to use http/https to make requests in tests. Reduced cognitive complexity in lib/serverless/aws-lambda.js Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-1-0","eolDate":"2024-05-04"},{"agent":"nodejs","date":"2023-04-19","downloadLink":"https://www.npmjs.com/package/newrelic","version":"10.0.0","features":["Updated the default of `config.transaction_tracer.record_sql` from `off` to `obfuscated`.","Route (URL) parameters are now stored as `request.parameters.route.*` attributes on Transactions, root Segments and Spans.","Removed `captureUrlParams` from `WebFrameworkShim` class.","Added the ability to register instrumentation multiple hooks (onRequire, onResolved) for the same resolved moduleName."],"bugs":[],"security":[],"supportedOperatingSystems":null,"description":"Notes BREAKING  - Updated the default of config.transaction_tracer.record_sql from off to obfuscated. This means that sql statements will be captured but obfuscated. BREAKING  - Route (URL) parameters are now stored as request.parameters.route.* attributes on Transactions, root Segments and Spans. After this change, the following becomes true: Query parameters will be available as attributes prefixed with request.parameters.* on Transactions and Spans. Route parameters will be available as attributes prefixed with request.parameters.route.* on Transactions and Spans. Route parameters (aka url parameters) are a common feature of various web frameworks, where you can create a placeholder as part of an API route definition. For example, given the following Express route definition and request url: The route parameter is id, and has a value of abc123. This would become request.parameters.route.id: abc123 on the Transaction, root Segment, and Span attributes. This example also has a query parameter of id, which has a value of true. This would become request.parameters.id: true on the Transaction, root Segment, and Span attributes. BREAKING  - Removed captureUrlParams from WebFrameworkShim class. DEPRECATION NOTICE : shim.unwrap and shim.unwrapOnce will no longer function if you attempt to unwrap an item that has been wrapped multiple times. This is because since we now allow instrumenting the same module more than once, you cannot safely unwrap without breaking all registered instrumentation.  We plan to remove shim.unwrap and shim.unwrapOnce in the next major release. Added the ability to register instrumentation multiple hooks (onRequire, onResolved) for the same resolved moduleName. This has been a limitation of the agent from the beginning. If you used the api to instrument api.instrument, api.instrumentDatastore, api.instrumentWebframework, api.instrumentMessages, or api.instrumentConglomerate, it would override existing instrumentation hooks.  The effect was that the Node.js agent would not function as designed. Refactored lib/transaction/tracecontext.js to reduce cognitive complexity. Refactored lib/transaction/trace/index.js to reduce cognitive complexity. Upgraded devDependencies jsdoc, and lean-jsdoc-theme. Support statement: New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life .","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-10-0-0","eolDate":"2024-04-19"},{"agent":"nodejs","date":"2015-04-02","downloadLink":"https://www.npmjs.org/package/newrelic","version":"1.18.1","features":null,"bugs":null,"security":null,"supportedOperatingSystems":null,"description":"Notes Names assigned to errors via Error.name now appear in the UI. Previously, the name of an error in the UI appeared as Error.constructor.name or with a default of Error. Now the common pattern of Error.name is respected and takes precedence. Child segments of external calls will now be nested correctly. This change causes segments that make up external calls to nest under the call correctly. Previously, the child segments appeared as siblings to external calls. The request_uri attribute on errors will now only include the path without any parameters. This behavior now matches the other New Relic agents.","slug":"docs/release-notes/agent-release-notes/nodejs-release-notes/clone-node-agent-1181","eolDate":"2018-04-02"}]