You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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?
Beta Was this translation helpful? Give feedback.
All reactions