Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Release Notes for HawtIO Diagnostic Console Guide

Red Hat build of Apache Camel 4.4

What's new in HawtIO Diagnostic Console Guide provided by Red Hat

Red Hat build of Apache Camel Documentation Team Red Hat build of Apache Camel Support Team http://access.redhat.com/support

Abstract

The latest details on what's new in this release of HawtIO Diagnostic Console Guide.

Preface
Copy link

HawtIO provides enterprise monitoring tools for viewing and managing Red Hat HawtIO-enabled applications. It is a web-based console accessed from a browser to monitor and manage a running HawtIO-enabled container. HawtIO is based on the open source HawtIO software (https://hawt.io/). HawtIO Diagnostic Console Guide describes how to manage applications with HawtIO.

The audience for this guide are Apache Camel eco-system developers and administrators. This guide assumes familiarity with Apache Camel and the processing requirements for your organization.

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.

Chapter 1. HawtIO release notes
Copy link

This chapter provides release information about HawtIO Diagnostic Console Guide.

1.1. HawtIO features
Copy link

HawtIO Diagnostic Console is available for general release in the HawtIO Diagnostic Console Guide 4.0.0.

HawtIO includes the following main features:

  • Runtime management of JVM via JMX, especially that of Camel applications and AMQ broker, with specialised views
  • Visualisation and debugging/tracing of Camel routes
  • Simple managing and monitoring of application metrics

1.1.1. Release features
Copy link

  1. UI plugins

    1. Connect
    2. JMX
    3. Camel
    4. Runtime
    5. Logs
    6. Quartz
    7. Spring Boot
  2. UI extension with custom plugins

  3. Authentication

    1. RBAC
    2. BASIC Authentication
    3. Spring Security
    4. Keycloak

  4. HawtIO Operator

    1. Managing HawtIO Online instances via HawtIO Custom Resources (CR)

      1. Addition of CR through the OpenShift Console;
      2. Addition of CR using CLI tools, eg. oc;
      3. Deletion of CR through OpenShift Console or CLI results in removal of all owned HawtIO resources, inc. ConfigMaps, Deployments, ReplicationController etc.;
      4. Removal of operator-managed pod or other resource results in replacement being generated;
      5. Addition of property or modification of existing property, eg. CPU, Memory or custom configmap, results in new pod being deployed comprising the updated values

    2. Installation via Operator Hub

      1. Upgrade of operator will take place if the Tech Preview version has been previously installed. The 1.0.0 GA operator will report itself in the catalog as 1.0.1, purely to differentiate itself from the Tech Preview version;
      2. Successful installs via either the numbered (2.x) or the latest channels will result in the same operator version and operand being installed;
      3. Successful install of the operator through the catalog;
      4. Searching for HawtIO in the catalog will return both the product and community versions of the operator. Correct identification of the versions should be obvious.

  5. HawtIO Online

    1. With no credentials supplied, the application should redirect to the OpenShift authentication page

      1. The entering of correct OpenShift-supplied credentials should redirect back to the Discovery page of the application;
      2. The entering of incorrect OpenShift-supplied credentials should result in the user being instructed that logging-in cannot be completed;

  6. Discovery

    1. Only jolokia-enabled pods should be visible either in the same namespace (Namespace mode) or across the cluster (Cluster mode);
    2. Pods should display the correct status (up or down) through their status icons;
    3. Only those pods that have a working status should be capable of connection (connect button visible);
    4. The OpenShift console URL should have been populated by the startup scripts of HawtIO. Therefore, all labels relating to a feature accessible in the OpenShift console should have hyperlinks that open to the respective console target;
    5. The OpenShift console should be accessible from a link in the dropdown menu in the head bar of the application;
    6. All jolokia-enabled apps should have links listed in the dropdown menu in the head bar of the application;

  7. Connection to HawtIO-enabled applications

    1. Clicking the Connect button next to a pod in the Discovery page should open a new window/tab and ‘connect’ to the destination app. This should manifest as the HawtIO Online UI showing plugin names vertically down the left sidebar, eg. JMX, and details of the respective focused plugin displayed in the remainder of the page;
    2. Failure to connect to a pod should present the user with some kind of error message;
    3. Once connected, all features listed in the ‘UI Plugins’ (above) should be available for testing where applicable to the target application.

1.1.2. HawtIO known issues
Copy link

The following issue remain with HawtIO for this release:

HAWNG-147 Fuse web console - support both RH-SSO and Properties login

When Keycloak/RH-SSO is configured for web console authentication, the user is automatically redirected to the Keycloak login page. There is no option for the user to attempt local/properties authentication, even if that JAAS module is also configured.

HAWNG-698 Camel 4 application’s Fuse Console is not loading properly and throwing 'No Selected Container'

Camel 4 application’s Fuse Console is not loading properly and throwing 'No Selected Container'. Errors returned are (502) Bad Gateway and (504) ERR_INSUFIENT_RESOURCE.

Legal Notice
Copy link

Copyright © 2024 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 http://creativecommons.org/licenses/by-sa/3.0/. 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.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top