In this post I explore the source generators shipped in Microsoft.Extensions.Telemetry.Abstractions, explore the code, and discuss whether I would use them

Andrew Lock's blog focuses on ASP.NET Core development, web APIs, and software architecture. Readers can find tutorials, code samples, and explanations covering topics such as RESTful API design, authentication, and authorization in ASP.NET Core. Additionally, they can learn about dependency injection, middleware, and performance optimization techniques.

.NET Escapades

The Microsoft.Extensions.Telemetry.Abstractions source generator for System.Diagnostics.Metrics APIs generates boilerplate code for creating strongly-typed metrics and tag objects. However, the generated code offers minimal advantages over manual implementation—it doesn't improve performance, limits API flexibility (missing Description support, experimental Unit parameter), and supports niche scenarios like registering instruments with multiple meters. The strongly-typed tags feature helps prevent parameter-ordering bugs but can be implemented manually with better optimization opportunities. The underlying System.Diagnostics.Metrics APIs are already well-designed with minimal boilerplate, making the source generator's value proposition questionable for most use cases.

Exploring the (underwhelming) System.Diagnostics.Metrics source generators

Background: System.Diagnostics.Metrics APIs

Background: sample app with manual boilerplate

Replacing boiler plate with a source generator