Apache HTTP Server mod_manager module offers a clean and simple "Mod_cluster Manager Console" where an administrator could:

• observe all worker nodes and their
  • deployed contexts
  • status
  • load
  • elected numberProxyHandler
  • and more metrics
• see load balancing groups and their members
• carry out management operations on
  • contexts
  • nodes
  • whole load balancing groups

...and more. It is offered as a plain HTML page, with a possibility to request an XML variant for automated processing.

The standalone Undertow mod_cluster proxy implementation contains a class called MCMPWebManager.java that appears to be offering some management UI.

What I consider being a Blocker though is the absence of any WildFly CLI / Web console implementation.

At first, I though one could simply update WildFly/Undertow mod_cluster filter integration with something like

MCMPConfig.WebBuilder webBuilder = MCMPConfig.webBuilder();
webBuilder.setCheckNonce(false);
webBuilder.setAllowCmd(true);
webBuilder.setReduceDisplay(false);
webBuilder.setManagementHost(managementSocketBinding.getValue().getSocketAddress().getHostName());
webBuilder.setManagementPort(managementSocketBinding.getValue().getSocketAddress().getPort());
webManagerConfig = webBuilder.build();

having it registered as HttpHandler just after unhandled ProxyHandler, before MCMPHandler. Giving it a second thought, I believe that producing any wild HTML pages accessible on some arbitrary "management" contexts is not the way to go with Wildfly.

Call to action

IMHO, we need to implement the management console operations for Undertow mod_cluster proxy in Wildfly CLI console; subsequently exposing the operations to the Wildfly web console.

WDYT?