Monitoring AMQ Interconnect sites using the console

Red Hat AMQ 2021.Q2

For Use with AMQ Interconnect 2.0 TECHNOLOGY PREVIEW


This guide describes how to monitor AMQ Interconnect sites and a service network.


Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.


AMQ Interconnect 2.0 Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production.

These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see

Chapter 1. Monitoring AMQ Interconnect sites using the console

The Skupper console provides useful information about the service network, for example, traffic levels between sites.

skupper console

1.1. Accessing the Skupper console

By default, the Skupper console is available whenever you create a service network router and is protected by credentials available in the skupper-console-users secret.


  1. Determine the Skupper console URL using the skupper CLI, for example:

    $ skupper status
    Skupper is enabled for namespace "west" in interior mode. It is not connected to any other sites. It has no exposed services.
    The site console url is:  https://skupper-west.apps-crc.testing
  2. Browse to the Skupper console URL. The credential prompt depends on how the site was created using skupper init:

    • using the --console-auth unsecured option, you are not prompted for credentials.
    • using the --console-auth openshift option, you are prompted to enter OpenShift cluster credentials.
    • using the default or --console-user <user> --console-password <password> options, you are prompted to enter AMQ Interconnect credentials.
  3. If you created the site using default settings, that is skupper init, a random password is generated for the admin user. To retrieve the password:

    1. Retrieve the encoded password for the admin user:

      $ oc get secret skupper-console-users -o yaml| grep admin
      admin: Sk5aV3pNSHR5Zw==
    2. Decode the password for the admin user:

      $ echo -n "Sk5aV3pNSHR5Zw==" | base64 --decode

1.2. Exploring the Skupper console

The Skupper console provides an overview of the following:

  • Services - services that are exposed on the service network, both local and remote.
  • Sites - AMQ Interconnect installations on the current service network.
  • Deployments - deployments relating to exposed services.

    1. Perform the Creating a service network with OpenShift tutorial.
    2. Navigate to the Skupper console.
    3. Click the Sites menu item. Both the east and west sites should be displayed in circles.
    4. Drag and drop the west circle to be on the left of the east circle.
    5. Click the Table tab to display the sites as text items. This view allows you drill down into details relating to the selected site.
    6. Click the Deployments menu item. This view shows you any deployments that are exposed as services on the service network. In this case, the console displays the hello-world-backend (east) deployment.
    7. Click the Services menu item to display details for all services exposed on the service network.


      Although two services are involved in the tutorial, only one service, hello-world-backend is exposed on the service network.

    8. Click the Sites menu again and expand the panel on the right hand side of the console. This panel shows the traffic flows from the backend to the frontend.

Revised on 2021-08-16 14:22:55 UTC

Legal Notice

Copyright © 2021 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.