Monitoring AMQ Interconnect sites using the console
For Use with AMQ Interconnect 2.0 TECHNOLOGY PREVIEW
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 https://access.redhat.com/support/offerings/techpreview.
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.
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
Determine the Skupper console URL using the
skupperCLI, 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
Browse to the Skupper console URL. The credential prompt depends on how the site was created using
--console-auth unsecuredoption, you are not prompted for credentials.
--console-auth openshiftoption, 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.
- using the
If you created the site using default settings, that is
skupper init, a random password is generated for the
adminuser. To retrieve the password:
Retrieve the encoded password for the
$ oc get secret skupper-console-users -o yaml| grep admin admin: Sk5aV3pNSHR5Zw==
Decode the password for the
$ echo -n "Sk5aV3pNSHR5Zw==" | base64 --decode JNZWzMHtyg
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.
- Perform the Creating a service network with OpenShift tutorial.
- Navigate to the Skupper console.
- Click the Sites menu item. Both the east and west sites should be displayed in circles.
- Drag and drop the west circle to be on the left of the east circle.
- Click the Table tab to display the sites as text items. This view allows you drill down into details relating to the selected site.
- 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.
Click the Services menu item to display details for all services exposed on the service network.Note
Although two services are involved in the tutorial, only one service,
hello-world-backendis exposed on the service network.
- 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