What is the recommended way to capture per-route latency/error metrics?

[petro2050]

For an ASP.NET Web API app running as a lambda, how should we go about capturing per-route metrics? Lambda monitoring tab shows metrics at lambda level which are not that useful. I can think of enabling route metrics at API Gateway level, but I like the convenience of using a greedy proxy route.

What does the team recommend?

[ashishdhingra]

@petro2050 Good afternoon. Please advise if you tried using Enhancing Observability in the AWS SDK for .NET with OpenTelemetry. Also refer Announcing the general availability of AWS .NET OpenTelemetry libraries.