• /
  • EnglishEspañol日本語한국어Português
  • EntrarComeçar agora

Docs release notesRSS

June 28
Docs version: June 21-27, 2024

New docs

  • Mobile monitoring's application not responding feature helps you track and analyze when and why your Android application's blocked for more than five seconds.
  • New browser monitoring log() and wrapLogger() API docs define the syntax, requirements, parameters, and examples on how to use these new endpoints.

Major changes

Minor changes

  • Added IAST validator service URL endpoints to FedRAMP compliant endpoints and networks.
  • Updated IAST troubleshooting with specific IP ranges to whitelist if you're not seeing your application.
  • Updated Ruby agent configuration with NEW_RELIC_INSTRUMENTATION_AWS_SQS auto-instrumentation configuration information.
  • Removed ApplicationExitInfo reporting configuration information from configure mobile monitoring settings, because you can do this in the UI.
  • Workflow enrichments support multiple variables so you can customize your data more specifically ot your needs.
  • Added the MobileApplicationExit attribute to our data dictionary. Our data dictionary isn't only a docs resource, but it also feeds attribute definitions directly to the UI, for example when you're writing NRQL queries in our query builder.
  • Removed docs related to the outdated alerts REST API.

Release notes and What's New posts

June 21
Docs version: June 14-20, 2024

New docs

Major changes

  • In our Python agent configuration, added STARTUP_DEBUG info.
  • In mobile monitoring configuration settings, added enable and disable info for background and ApplicationExitInfo reporting for Android.
  • A massive overhaul of the alerts navigation more clearly maps out your user journey through alerts creation, configuration, management, and use.

Minor changes

Release notes and What's New posts

June 14
Docs version: June 7-13, 2024

New docs

Major changes

  • We've moved away from using applied intelligence to refer to our Alerts capability. This creates a clearer, more cohesive experience as we introduce more AI features and functionalities. We completed a massive sweep to remove nearly all mention of "applied intelligence" from our docs.
  • Deleted several old, outdated alerts docs.
  • A rewrite of change vulnerability status makes it easier for you to enable this feature.

Minor changes

  • Removed the notifications section from CodeStream settings.
  • Added a new OpenTelemetry redis instance section to clarify that you need to manually include redis attributes for the collector.
  • Private Synthetics Job Managers now support permanent data storage via synthetic monitoring.
  • Added New Relic partner API endpoint to networks user-facing domains table.
  • Added version tracking metadata environment variables to the Ruby agent's sending handled errors.
  • Added environment variables for .NET Lambda monitoring for serverless and layerless.
  • Multiple docs updates related to hybrid mobile agent releases.
  • We've updated our docs to remove unsupported .NET Core versions. (We no longer support .NET Core versions 2.0, 2.1, 2.2, and 3.0.)
  • In response to customer feedback, updated info on how to view script logs in the synthetic monitoring UI.
  • Thanks to our Docs engineering team, we no longer hardcode v into our release notes titles.
  • Quality-of-life improvements to view slow query details removed some outdated content and brought procedural content up-to-date.

Release notes and What's New posts

June 7
Docs version: May 31-June 6, 2024

New docs

Major changes

Minor changes

  • Updated PHP agent operating system support to state that we support an OS version one year after a vendor's end-of-life date. (This saves us some maintenance overhead, because we don't need to list specific versions now.)
  • Our .NET APM agent for .NET Core and Framework now supports Microsoft.Data.SqlClient v5.2.1. Also, .NET Framework 4.6.2 or higher requires .NET APM agent version 10.0 or higher.
  • On our homepage, we've broken OpenTelemetry out into its own tile button.
  • In Forward your logs using the infrastructure agent, clarified that using ANSI encoding on winevtlog addresses empty string logs, but isn't used to convert ANSI to UTF-8. Added example use-ansi entries.
  • Updated some non-standard callouts to use our recommended format.
  • In Send your logging data with our Log API, added "msg" to the JSON message attributes table.
  • Added http.response.status_code from http span link to OpenTelemetry docs in OpenTelemetry APM errors inbox UI.
  • In APM: Monitor apps and services with OpenTelemetry, added a new section that lists things to keep in mind when you're running APM agents alongside OpenTelemetry tools.

Release notes and What's New posts

May 31
Docs version: May 24-30, 2024

New docs

Major changes

Minor changes

Release notes and What's New posts

May 24
Docs version: May 17-23, 2024

New docs

Major changes

  • Added and updated synthetic and browser scripted monitor code examples to synthetic monitoring best practices and synthetic scripted browser reference. Code examples are one of the things that are readers ask for the most, so we're always happy to see more of these.
  • In our network performance monitoring docs, a lot of little updates led to a major change: Updated supported environments for Podman across 17 docs.
  • Clarified how logs live archives works and when that log data is available.
  • Added a diagram and environment variables to Lambda monitoring instrument your containerized image layer.
  • New Relic's REST API v1 has been fully EOLed and we deleted several docs related to it.
  • A massive sweep of our infrastructure monitoring docs to:
    • Align it our style guide.
    • Remove unnecessary content.
    • Make the installation doc more visible in the left nav.
    • Improve the flow of the installation doc.
  • Our Developer-to-Docs site migration continues, with another 30+ docs migrated this week.
  • As of May 23, 2024, AI monitoring supports Java. We've updated several AI monitoring docs to reflect this important update.

Minor changes

Release notes and What's New posts

May 17
Docs version: May 10-16, 2024

New docs

  • A new doc on our NVIDIA Management Library (NVML) integration describes how to use the infrastructure agent and NRI-Flex to monitor GPU usage and performance metrics.
  • When Vulnerability Management is working too well, a recent update gives you the power to ignore vulnerabilities you're not concerned about.
  • A massive rework of the OpenTelemetry docs category, including a new APM: Monitor apps and services with OpenTelemetry to give you a solid place to start. Other changes:
    • Reorganized the OpenTelemetry > Get started category to add consistent Overview docs to its subcategories.
    • Renamed docs titles to clarify what's in them.
    • Consolidated related docs to make it easier to find related info.
  • For people who'd rather not write regular expressions or Grok patterns to parse their logs, query time parsing is a powerful tool for parsing logs directly in the UI. (A lot of great screenshots in this one.)

Major changes

  • Continued to rewrite the on-host integration docs to make it easier to install and ensure the docs are accurate and up to date. Up this week: Port and Unix monitoring integrations.
  • Clarified how to manage and use data retention rules for single- and multiple-account organizations.
  • We've moved version tracking info from error tracking to version tracking and made some quality-of-life improvements along the way.
  • In October, 2024, we're EOLing the containerized private minion (CPM) and legacy synthetics runtime versions. In June, we're blocking the creation of new monitors using these legacy runtimes. We've added notes to this effect, like this EOL notice.

Minor changes

Release notes and What's New posts

May 10
Docs version: May 3-9, 2024

New docs

Major changes

  • Added several new images to session traces, as well as updates to prerequisites, configuration, and use cases. Session trace data is billable starting June 10, 2024.
  • As part of our Developer-to-Docs site migration project, we've migrated some content related to the SDK component library.
  • Updated global technical support offerings to relect our current support policies and SLAs.

Minor changes

Release notes and What's New posts

May 3
Docs version: April 26–May 2, 2024

New docs

  • We've got a new Atlassian integration so people can sync issues and incidents created in New Relic with Atlassian Jira.
  • Our new best practices for integration users doc gives advice to New Relic administrators when integrating third-party systems with our platform, specifically as it relates to security.
  • A new doc on the Amazon S3 Storage Lens integration describes how to connect this service to New Relic.

Major changes

  • We've overhauled our Micrometer doc with clear, procedural steps to ingest data via the OpenTelemetry Micrometer bridge.
  • As part of our Developer-to-Docs site migration project, we've migrated content related to custom visualizations, NerdGraph, and the CLI, among others.
  • Updated .NET agent compatibility requirements for several supported frameworks.

Minor changes

Release notes and What's New posts

April 26
Docs version: April 19–25, 2024

New docs

Major changes

  • We just rolled-out a completely redesigned docs homepage! Check it out! We wanted to:
    • Put search front and center.
    • Show a more linear, clear onboarding path for new users.
    • Remove the left nav to reduce overwhelm for newbies.
    • Create a clear path into docs for each of our capabilities.
    • Add more animation and color for a more attractive, dynamic, and modern look-and-feel.
    • Improve consistency between docs, newrelic.com, and the product UI.
  • Continued to rewrite the on-host integration docs to make it easier to install and ensure the docs are accurate and up to date. Up this week:
  • Thresholds are a new chart customization to add useful context to your charts.

Minor changes

Release notes and What's New posts

Copyright © 2024 New Relic Inc.

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