Additional Libuv Metrics

[anthonyalayo]

Additional Libuv Metrics

[bnoordhuis]

Loop lag metrics

I'm not too keen on adding that. For one, it's not clear to me how meaningful it would be in UV_RUN_NOWAIT mode.

Worker Pool utilization metrics

We currently use file operations such as uv_fs_open. These operations as far as I know will be serviced with libuv's internal thread pool

Sometimes. They can also be serviced by io_uring. I'm inclined to say thread pool metrics aren't that useful for that reason alone.

I mean, tracking per-request latency (i.e., the time a uv_fs_t operation takes from start to finish) is useful but that's something embedders can implement themselves. We're unlikely to bake that into libuv itself because it's a) not necessary, and b) adds overhead.

[anthonyalayo]

Both sound fair, I hadn't thought about those cases.