Hi devs,
I see on http://localhost:8080/xwiki/bin/admin/XWiki/XWikiPreferences?editor=globaladmin§ion=Likes that we exposed a technical management option which is the cache capacity for Likes. I don’t recall if we do that elsewhere already but anyway this raises the question of what we want to do about JMX options.
Note: Technically, I hope that the Like cache capacity is exposed as a JMX MBean since this is what we decided to do (https://xwiki.markmail.org/search/?q=jmx#query:jmx+page:1+mid:akxlzdvlfvwxgpxb+state:results) .
I see 3 options:
-
provide our own UI for JMX actions and configuration options
-
bundle one of the numerous existing generic UIs for JMX
-
don’t bundle any but document how to use existing JMX management app (such as visualJVM, jconsole, etc). Nore that this is currently what we do at https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Monitoring#HJMXConsole
-
is the most costly by far and not complete (we’ll miss actions and features, like the ones exposed by the Servlet container or Hibernate or Infinispan, etc). It’s also the most usable probably. However it also makes our admin UI more complex to use since it may litter it with lots of quite technical management options. So if we were to do 1) we could also offer a Management category separate from the configuration category for each feature/extension.
For 2) we would need to look for it that we can integrate. I remember MX4J but it seems dead-ish now.
I would go for 3) and look at stuff like https://hawt.io/
WDYT?
