Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Design for Integrated Console

See original GitHub issue


The purpose is to have one console, that can be used to create the enmasse address spaces, iot spaces, as well as kafta, brokers, and routers. There will be a new project for the slim integrated console, that will delegate to each component, to create, delete, list instances. The integrated console will only provide the ability to view a list of each instance, and the ability to create, delete (edit)? them.


Repository Strutcture

If we used, it should be for the EnMasseConsole, not the integrated console. Therefore, suggesting Another option is being a consolidated console it could be in the repo that contains many of the AMQ projects
The integrated-console repository should contain directories: console-ui (PF4 react), console-service (go), and console-mock-service.

Console Server:


  • GET /v1/components => list all amq components
    • name
    • create-url
    • description (for first screen of create)
    • instances-count (could move the count into its own call. But the header always needs the instances & count
  • GET /v1/instances?name=xxx?component=xxx&sort_by=&order_by=asc&offset=10&limit=5 => list of instances, filter by name, paging.
    • In the markup, the ordering is confusing. Widgets appear in both the filter, and the table?
    • do we want multi-column sort?
  • GET /v1/instances/123 => specific instance
    • name
    • created by
    • component
    • type
    • status (alive / dead, not throughput)
    • component console url
    • time created
    • statistics (addresses, queues, connections / AMQP Addresses, senders, receivers / topics,senders,consumergroups / addresses, connections), ordered by priority
  • DELETE /v1/instances/123


  • Authentication: Authenticate against openshift
    • oath to get a token to be used for any communication.
    • click through to existing AMQ Online Console (and navigate back)
    • ensures users can only see resources that they have permissions to. And if you can view a resource, you can get the stats etc.
  • console server would need to be run under a service account for permissions
  • update mechanism (amqp/http), used by prometheus etc. for polling. The other option is websockets, but not as common.
  • wraps the kubernetes calls, to provide a well defined api.
  • message throughput graphs (later)
  • be able to make a stub console server (mock out kubernetes)

Each Component console (EnMasse, Kafta, …):

  • Will provide HTML and Javascript to support the create workflow.
    • THis will populate the fields of the CRD resource.
      • configuration page, that updates object: url/configure
      • review page, url/review
      • POST
    • create instance
    • delete instance
    • throughput info for graph?
  • CRD resource updated by the component.
  • When the console is instanciated in Openshift it will define its CRD with its version.
  • For each instance of its component that it creates, it will create/update

Example CRD created by Enmasse Console on deploy

kind: CustomResourceDefinition
  name: (or
  version: v1 
  scope: Cluster
    plural: addressspaceinstances
    singular: addressspaceinstance 
    kind: AddressSpaceInstance
    - asi

Example Custom Object, created on new address space.

kind: AddressSpaceInstance
  name: address-space-instances
component-create-url: "http://..."
display-name: "address space"
display-description: ...
instance-count: 2
- name: AddSpacer01
  created-by: "annoymous_test1"
  type: "standard"
  status: "alive"
  component-console-url: "http://.../objectid"
  statistics: ["addresses:192", ...] ordered by priority
- name: AddSpace02

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:12 (12 by maintainers)

github_iconTop GitHub Comments

k-wallcommented, Mar 4, 2019

I like the prometheus idea, but maybe it would be best if the design didn’t mandate it. If each component submitted a statistics plugin to the console-server its implement could find and emit the statistics in the way that suits it. For components that use prometheus, they could periodically call out to it and then periodically emit the results… They would be free to use an different implementation.

Re watchable component resources. I think it would be too inflexible to try and impose standard form. Users could be bringing their own components and plugging them in to the console.

k-wallcommented, Mar 5, 2019

We decided to defer statistics for a later phase and take an alternative approach for retrieving the resources (i.e. use the Kubernetes API directly from the UI, rather than effectively proxying it in a console server. I opened a new issue to replace this one #2408.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Using the Application Integration Design Console
The Application Integration Design Console is a graphical user interface (GUI) that offers an easy way to access, organize, and edit all the...
Read more >
Some _other_ way to get the PowerShell Integrated Console ...
However, when I do want it, I only have one option: the command palette: Show Integrated Console or probably another one is starting...
Read more >
Analysis and design of integrated task console software ...
Integrated task console is an important part of the UAV system, and its main mission is to accept combat tasks transmitted by superiors,...
Read more >
Control Room Consoles - Copp Systems
Let us help you design your ideal control room and command center with modular workstations. Our ergonomic control room consoles can be customized...
Read more >
Jetic - Integration Console - Dribbble
Jetic - Integration Console designed by Nic Jablonski for Semiflat. Connect with them on Dribbble; the global community for designers and ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found