arunramani commented on code in PR #16905: URL: https://github.com/apache/druid/pull/16905#discussion_r1723906616
########## docs/configuration/index.md: ########## @@ -394,6 +394,9 @@ Metric monitoring is an essential part of Druid operations. The following monito |`org.apache.druid.java.util.metrics.CgroupCpuSetMonitor`|Reports CPU core/HT and memory node allocations as per the `cpuset` cgroup.| |`org.apache.druid.java.util.metrics.CgroupDiskMonitor`|Reports disk statistic as per the blkio cgroup.| |`org.apache.druid.java.util.metrics.CgroupMemoryMonitor`|Reports memory statistic as per the memory cgroup.| +|`org.apache.druid.java.util.metrics.CgroupV2CpuMonitor`|Reports CPU usage from `cpu.stat` file. Only applicable to `cgroupv2`.| Review Comment: Now that I think about it, would it make sense to have just a single monitor and use the right cgroup discoverer instead? It might be too annoying for a user to figure out which one to use depending on how they setup their container. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
