.NET agent release notesRSS

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

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.

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

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.

Fixes

• ASP.NET Core 6+ browser agent injection is disabled by default. (e571ac1)

Checksums

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.

Fixes

• Add defensive coding and exception handling during ASP.NET Core 6+ browser injection. (#2035) (#2038) (5ddd0ea)

Checksums

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.

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

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.

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

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.

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

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.

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

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.

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

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.