The number of failed requests per update intervalĬurrent number of active HTTP requests that have started but not yet completed or failedĬurrent HTTP 1.1 Connections ( http11-connections-current-total) Requests Failed Rate ( requests-failed-rate) The number of failed requests since the process started The number of requests started per update interval Requests Started Rate ( requests-started-rate) The number of requests started since the process started The following counters are published by the HTTP stack. The total number of TLS handshakes with the web server Total TLS Handshakes ( total-tls-handshakes) The total number of connections to the web server The number of TLS handshakes per update interval TLS Handshake Rate ( tls-handshakes-per-second) Request Queue Length ( request-queue-length) The total number of failed TLS handshakes The current number of upgraded requests (WebSockets)įailed TLS Handshakes ( failed-tls-handshakes) The current number of active connections to the web serverĬurrent TLS Handshakes ( current-tls-handshakes)Ĭurrent Upgraded Requests (WebSockets) ( current-upgraded-requests) The number of connections per update interval to the web server The current length of the connection queueĬonnection Rate ( connections-per-second) CounterĬonnection Queue Length ( connection-queue-length) The following counters are published as part of the ASP.NET Core Kestrel web server and are maintained in KestrelEventSource.cs. Microsoft-AspNetCore-Server-Kestrel counters The total number of connections that have timed out Total Connections Timed Out ( connections-timed-out) The total number of connections that have stopped Total Connections Stopped ( connections-stopped) The total number of connections that have started Total Connections Started ( connections-started) The number of active connections that have started, but not yet stopped The average duration of a connection in millisecondsĬurrent Connections ( current-connections) CounterĪverage Connection Duration ( connections-duration) The following counters are published as part of ASP.NET Core SignalR and are maintained in HttpConnectionsEventSource.cs.
The total number of requests that have occurred for the life of the app The number of requests that occur per update interval The total number of failed requests that have occurred for the life of the app
/facebook-friend-request-scams-what-they-are-and-how-to-protect-yourself-from-them-4771675-9-c5e4dc5a8d9d4214803e3bc6ee31b949.png "maptiler request count")
The total number of requests that have started, but not yet stopped The following counters are published as part of ASP.NET Core and are maintained in HostingEventSource.cs. The number of methods that are JIT-compiled Method Jitted Count ( method-jitted-count) The total size of ILs that are JIT-compiled, in bytes The amount of physical memory mapped to the process context at a point in time base on Environment.WorkingSet The number of thread pool threads that currently exist in the ThreadPool, based on ThreadPool.ThreadCount ThreadPool Thread Count ( threadpool-thread-count) The number of work items that are currently queued to be processed in the ThreadPool ThreadPool Queue Length ( threadpool-queue-length) The number of work items that have been processed so far in the ThreadPool ThreadPool Completed Work Item Count ( threadpool-completed-items-count) The number of Assembly instances loaded into a process at a point in time Number of Assemblies Loaded ( assembly-count) The number of Timer instances that are currently active, based on Timer.ActiveCount Number of Active Timers ( active-timer-count) The number of times there was contention when trying to take the monitor's lock, based on Monitor.LockContentionCount Monitor Lock Contention Count ( monitor-lock-contention-count) The number of bytes for the pinned object heap (available on. The number of bytes for the large object heap The number of times GC has occurred for Gen 2 per update interval The number of times GC has occurred for Gen 1 per update interval The number of times GC has occurred for Gen 0 per update interval The number of bytes thought to be allocated based on GC.GetTotalMemory(Boolean) The number of exceptions that have occurred The percent of the process's CPU usage relative to all of the system CPU resources The number of bytes allocated per update interval The percent of time in GC since the last GC NET runtime (CoreCLR) and are maintained in the RuntimeEventSource.cs. The following counters are published as part of. This article is a reference on the providers that can be used to monitor these counters and their descriptions. NET runtime and libraries implement and publish several EventCounters that can be used to identify and diagnose various performance issues.
0 kommentar(er)
