Conversation
src/Hosting/Abstractions/src/Microsoft.AspNetCore.Hosting.Abstractions.csproj
Show resolved
Hide resolved
src/Middleware/RateLimiting/src/RateLimiterApplicationBuilderExtensions.cs
Show resolved
Hide resolved
src/Hosting/Abstractions/src/Microsoft.AspNetCore.Hosting.Abstractions.csproj
Show resolved
Hide resolved
src/Middleware/RateLimiting/src/RateLimiterApplicationBuilderExtensions.cs
Show resolved
Hide resolved
|
Blocked on API review of #47745 |
There was a problem hiding this comment.
Are we going to update Kestrel, Hosting and SignalR current- metrics to use a MetricsContext like this in a follow up PR?
As an aside, could we wait until after a transport is selected to start SignalR's "current-connections" counter and remove "current-transports"? Do we really need to know how many current connections are in a pre-transport state? If so, maybe we could add a "current-negotiating-connections" or "current-pending-connections" counter. I know this went through API review, but this is my first time looking closely at it. @BrennanConroy
src/Middleware/RateLimiting/src/RateLimiterApplicationBuilderExtensions.cs
Show resolved
Hide resolved
Co-authored-by: Stephen Halter <halter73@gmail.com>
|
Breaking change announcement: aspnet/Announcements#506 |
We decided to start the SignalR connection counter at its current point because that's when memory is allocated for it on the server. Splitting it up into multiple counters didn't feel that valuable. |
Adds metrics counters to rate limiting. See #47745 for details about the counters.