.NET agent release notesRSS

Fixes

• Fix syntax error in setenv.sh (#2864) (a629138), closes #2863

Checksums

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. See the New Relic .NET agent EOL policy doc for information about agent releases and support dates.

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

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. See the New Relic .NET agent EOL policy doc for information about agent releases and support dates.

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

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. See the New Relic .NET agent EOL policy doc for information about agent releases and support dates.

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

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. See the New Relic .NET agent EOL policy doc for information about agent releases and support dates.

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

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. See the New Relic .NET agent EOL policy doc for information about agent releases and support dates.

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

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. See the New Relic .NET agent EOL policy doc for information about agent releases and support dates.

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

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. See the New Relic .NET agent EOL policy doc for information about agent releases and support dates.

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

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. See the New Relic .NET agent EOL policy doc for information about agent releases and support dates.

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

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. See the New Relic .NET agent EOL policy doc for information about agent releases and support dates.