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
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
On Kusama, we see weird behaviors around some resource consumption of our process. Specifically around resources needed for networking. To make debugging easier, we should track a few more metrics around that via prometheus:
num open connections
num of open streams
num of open sockets / connections by the system (lsof-style)
total number of open files
Any other suggestions of resources we are not tracking yet but would be useful to?
This PR refactors the metrics measuring and Prometheus exposing entity in sc-service into its own submodule and extends the parameters it exposes by:
- system load average (over one, five and 15min)
- the TCP connection state of the process (lsof), refs #5304
- number of tokio threads
- number of known forks
- counter for items in each unbounded queue (with internal unbounded channels)
- number of file descriptors opened by this process (*nix only at this point)
- number of system threads (*nix only at this point)
refs #4679
Co-authored-by: Max Inden <mail@max-inden.de>
Co-authored-by: Ashley <ashley.ruglys@gmail.com>
On Kusama, we see weird behaviors around some resource consumption of our process. Specifically around resources needed for networking. To make debugging easier, we should track a few more metrics around that via prometheus:
Any other suggestions of resources we are not tracking yet but would be useful to?
Refs #4679 .
The text was updated successfully, but these errors were encountered: