There are various ways in how to proceed and customize the console, but I think it would really help in order to tell you the best route if you were to express the requirements that you have. Some of them may be done in some ways, others in other ways.
* you can ask for (and this is why I was asking for specific requirements) some new configuration parameters or plugins to add: not everything is configurable, nor everything is changeable via plugin, but depending on the demand/request, it may be useful to other users to open up more plugins or more configuration parameters
* you can build an entirely new console using whichever technology you want by using the REST api (of the console, as described here: http://pongasoft.github.io/glu/docs/latest/html/orchestration-engine.html#rest-api). Technically that is the way glu should be built as well: a thin UI on top of a REST api... It is not really the way it is done right now (maybe it will get there at some point). There are obviously quite a few REST api missing to be able to rebuild glu this way, but those can be added and would benefit everybody who wants to automate/program glu.
Here is attached screenshot which we want to build in glu console. We want to Start, Stop or Bounce an individual or multiple application(s) at the same time.
Please give your suggestion how to achieve this new design in glu console by developing new plugin or develop new screen and then use existing code to start, stop, and bounce application(s) in agent(s).