Summary

Due to a change in .NET versions 6.0.12 and 7.0.1, Model View Controller (MVC) applications using HTTP naming for Business Transactions may not register the root path of the application as a Business Transaction. Because of this, WebAPI applications using HTTP naming may register a Business Transaction with a different name, in older versions of .NET. 

Affected Software

This change is known to impact all .NET Agents, specifically when instrumenting applications running on .NET 6.0.12 and 7.0.1 runtimes.

Impact

MVC applications may not register the root URL as Business Transactions, and it may impact visibility. In the case of WebAPI applications, existing Business Transactions may stop reporting, and new Business Transactions may get registered. If there are alerts configured against specific Business Transactions, false alerts may be triggered. Also, custom transaction detections, or exclusion rules defined using URLs, might not work.

Resolution

We are evaluating options for the fix required to accommodate the change in the .NET Framework. Until a fix is released, we recommend using .NET version 6.0.11. 

If you have any questions or concerns, please contact customer support or use our support portal.