On Wed, 6 Jul 2022 03:52:30 GMT, xpbob <d...@openjdk.org> wrote: >> Container configuration information is useful for troubleshooting >> problems,Exposing information in MBeans is ideal for monitoring, jConsole, >> and other scenarios. >> Results the following >>  > > xpbob has updated the pull request incrementally with one additional commit > since the last revision: > > update header
It's not clear that introducing this as a standard API is the right thing to do. Are you 100% confident that the concepts of "CPU quota", "CPU shares", "CPU period", "soft limit" etc. will last the test of time and that we don't be back here next year with another PR to deprecate or replace this API? I don't disagree that exposing a MXBean could be useful for monitoring/management purposes but I think we have to be cautious getting locked in. A possible standard point for prototyping purposes and getting feedback is a JDK-specific MXBean (module jdk.management). ------------- PR: https://git.openjdk.org/jdk/pull/9372
