Jump To Close Expand all Collapse all Table of contents Managing Fuse Preface Making open source more inclusive 1. Monitoring and managing Red Hat Fuse applications on OpenShift Expand section "1. Monitoring and managing Red Hat Fuse applications on OpenShift" Collapse section "1. Monitoring and managing Red Hat Fuse applications on OpenShift" 1.1. About the Fuse Console 1.2. Setting up the Fuse Console on OpenShift 4.x Expand section "1.2. Setting up the Fuse Console on OpenShift 4.x" Collapse section "1.2. Setting up the Fuse Console on OpenShift 4.x" 1.2.1. Installing and deploying the Fuse Console on OpenShift 4.x by using the OperatorHub 1.2.2. Installing and deploying the Fuse Console on OpenShift 4.x by using the command line Expand section "1.2.2. Installing and deploying the Fuse Console on OpenShift 4.x by using the command line" Collapse section "1.2.2. Installing and deploying the Fuse Console on OpenShift 4.x by using the command line" 1.2.2.1. Generating a certificate to secure the Fuse Console on OpenShift 4.x 1.2.3. Role-based access control for the Fuse Console on OpenShift 4.x Expand section "1.2.3. Role-based access control for the Fuse Console on OpenShift 4.x" Collapse section "1.2.3. Role-based access control for the Fuse Console on OpenShift 4.x" 1.2.3.1. Determining access roles for the Fuse Console on OpenShift 4.x 1.2.3.2. Customizing role-based access to the Fuse Console on OpenShift 4.x 1.2.3.3. Disabling role-based access control for the Fuse Console on OpenShift 4.x 1.2.4. Upgrading the Fuse Console on OpenShift 4.x 1.3. Setting up the Fuse Console on OpenShift 3.11 Expand section "1.3. Setting up the Fuse Console on OpenShift 3.11" Collapse section "1.3. Setting up the Fuse Console on OpenShift 3.11" 1.3.1. Deploying the Fuse Console on OpenShift 3.11 1.3.2. Monitoring a single Fuse pod from the Fuse Console on OpenShift 3.11 1.4. Viewing containers and applications 1.5. Viewing and managing Apache Camel applications Expand section "1.5. Viewing and managing Apache Camel applications" Collapse section "1.5. Viewing and managing Apache Camel applications" 1.5.1. Starting, suspending, or deleting a context 1.5.2. Viewing Camel application details 1.5.3. Viewing a list of the Camel routes and interacting with them 1.5.4. Debugging a route 1.6. Viewing AMQ Brokers 1.7. Viewing and managing JMX domains and MBeans 1.8. Viewing and managing Quartz Schedules 1.9. Viewing diagnostics 1.10. Viewing threads 1.11. Ensuring that data displays correctly in the Fuse Console 2. Monitoring and managing Red Hat Fuse applications on Spring Boot standalone Expand section "2. Monitoring and managing Red Hat Fuse applications on Spring Boot standalone" Collapse section "2. Monitoring and managing Red Hat Fuse applications on Spring Boot standalone" 2.1. About the Fuse Console 2.2. Accessing the Fuse Console for Spring Boot 2.x 2.3. Customizing the Fuse Console branding 2.4. Securing the Fuse Console 2.5. Ensuring that data displays correctly in the Fuse Console 2.6. Connecting to remote Fuse applications Expand section "2.6. Connecting to remote Fuse applications" Collapse section "2.6. Connecting to remote Fuse applications" 2.6.1. Connecting to a remote Jolokia agent 2.6.2. Setting data moving preferences 2.6.3. Viewing JVM runtime information 2.7. Viewing and managing Apache Camel applications Expand section "2.7. Viewing and managing Apache Camel applications" Collapse section "2.7. Viewing and managing Apache Camel applications" 2.7.1. Starting, suspending, or deleting a context 2.7.2. Viewing Camel application details 2.7.3. Viewing a list of the Camel routes and interacting with them 2.7.4. Debugging a route 2.8. Viewing and managing JMX domains and MBeans 2.9. Viewing and managing Quartz Schedules 2.10. Viewing diagnostics 2.11. Viewing threads 3. Monitoring and managing Red Hat Fuse applications on Karaf standalone Expand section "3. Monitoring and managing Red Hat Fuse applications on Karaf standalone" Collapse section "3. Monitoring and managing Red Hat Fuse applications on Karaf standalone" 3.1. About the Fuse Console 3.2. Accessing the Fuse Console 3.3. Securing the Fuse Console 3.4. Role-based access reference 3.5. Customizing the Fuse Console branding 3.6. Ensuring that data displays correctly in the Fuse Console 3.7. Disabling the Fuse Console 3.8. Connecting to remote Fuse applications Expand section "3.8. Connecting to remote Fuse applications" Collapse section "3.8. Connecting to remote Fuse applications" 3.8.1. Unlocking the Fuse Console 3.8.2. Restricting remote access 3.8.3. Allowing connections to remote Fuse instances 3.8.4. Connecting to a remote Jolokia agent 3.8.5. Setting data moving preferences 3.8.6. Viewing JVM runtime information 3.9. Viewing and managing Apache Camel applications Expand section "3.9. Viewing and managing Apache Camel applications" Collapse section "3.9. Viewing and managing Apache Camel applications" 3.9.1. Starting, suspending, or deleting a context 3.9.2. Viewing Camel application details 3.9.3. Viewing a list of the Camel routes and interacting with them 3.9.4. Debugging a route 3.10. Viewing and managing JMX domains and MBeans 3.11. Viewing and managing Quartz Schedules 3.12. Viewing and managing your OSGI environment 3.13. Viewing diagnostics 3.14. Viewing threads 3.15. Viewing log entries 3.16. Enabling Prometheus metrics Expand section "3.16. Enabling Prometheus metrics" Collapse section "3.16. Enabling Prometheus metrics" 3.16.1. Enabling the export of metrics from a standalone Apache Karaf container 3.16.2. Configuring the Prometheus server to scrape exposed metrics from the Apache Karaf container 4. Monitoring and managing Red Hat Fuse applications on EAP standalone Expand section "4. Monitoring and managing Red Hat Fuse applications on EAP standalone" Collapse section "4. Monitoring and managing Red Hat Fuse applications on EAP standalone" 4.1. About the Fuse Console 4.2. Accessing the Fuse Console 4.3. Customizing the Fuse Console branding 4.4. Securing the Fuse Console 4.5. Ensuring that data displays correctly in the Fuse Console 4.6. Disabling the Fuse Console 4.7. Connecting to remote Fuse applications Expand section "4.7. Connecting to remote Fuse applications" Collapse section "4.7. Connecting to remote Fuse applications" 4.7.1. Unlocking the Fuse Console 4.7.2. Restricting remote access 4.7.3. Allowing connections to remote Fuse instances 4.7.4. Connecting to a remote Jolokia agent 4.7.5. Setting data moving preferences 4.7.6. Viewing JVM runtime information 4.8. Viewing and managing Apache Camel applications Expand section "4.8. Viewing and managing Apache Camel applications" Collapse section "4.8. Viewing and managing Apache Camel applications" 4.8.1. Starting, suspending, or deleting a context 4.8.2. Viewing Camel application details 4.8.3. Viewing a list of the Camel routes and interacting with them 4.8.4. Debugging a route 4.9. Viewing and managing JMX domains and MBeans 4.10. Viewing and managing Quartz Schedules 4.11. Viewing diagnostics 4.12. Viewing threads 4.13. Viewing log entries A. Fuse Console Configuration Properties Legal Notice Settings Close Language: 한국어 简体中文 日本語 English Language: 한국어 简体中文 日本語 English Format: Multi-page Single-page PDF Format: Multi-page Single-page PDF Language and Page Formatting Options Language: 한국어 简体中文 日本語 English Language: 한국어 简体中文 日本語 English Format: Multi-page Single-page PDF Format: Multi-page Single-page PDF Managing Fuse Red Hat Fuse 7.9Manage Fuse applications with the Fuse Console Red Hat Fuse Documentation Team Legal NoticeAbstract When you deploy a Fuse application, you can use the Fuse Console to monitor and interact with Red Hat Fuse integrations. Next