Managing Fuse

1. Add hawtio-springboot to your Fuse application’s pom.xml file dependencies.

   <dependency>
     <groupId>io.hawt</groupId>
     <artifactId>hawtio-springboot</artifactId>
   </dependency>

   Copy to Clipboard Toggle word wrap

   Note that you do not need to specify the version because it is provided by the Maven BOM.

2. Edit the src/main/resources/application.properties file:

   1. Set the following properties to false:

      • endpoints.jolokia.sensitive
      • endpoints.hawtio.sensitive
      • hawtio.authenticationEnabled

   2. Set the following properties to true:

      • endpoints.hawtio.enabled

      • endpoints.jolokia.enabled

        Your application.properties settings should look similar to the following example:

        # ports
        
        server.port=8080
        
        management.port=10001
        
        
        # enable management endpoints for healthchecks and hawtio
        
        endpoints.enabled = false
        
        endpoints.hawtio.enabled = true
        
        endpoints.jolokia.enabled = true
        
        endpoints.health.enabled = true
        
        management.health.defaults.enabled=false
        
        camel.health.enabled=false
        
        camel.health.indicator.enabled=true
        
        endpoints.jolokia.sensitive=false
        
        endpoints.hawtio.sensitive=false
        
        hawtio.authenticationEnabled=false

        Copy to Clipboard Toggle word wrap
        Note

        By default, authentication for the Fuse Console on Spring Boot is disabled. Optionally, you can enable authentication by writing code specific to your Fuse Console distribution. Here is an example that you can use for guidance:

        https://github.com/hawtio/hawtio/tree/master/examples/springboot-authentication

3. Run the Fuse application:

   mvn spring-boot:run

   Copy to Clipboard Toggle word wrap

4. To determine the port number for the Fuse Console URL, obtain the management.port value by looking at the value set in the src/main/resources/application.properties file. For example:

   management.port   = 10001

   Copy to Clipboard Toggle word wrap

5. To open the Fuse Console in a browser, use the following URL syntax where nnnnn is the value of the management.port property:

   http://localhost:nnnnn/hawtio/index.html

   For example: http://localhost:10001/hawtio/index.html

1. Start Red Hat Fuse standalone with the following command:

   On Linux/Mac OS: ./bin/standalone.sh

   On Windows: ./bin/standalone.bat

2. In a web browser, enter the URL to connect to the Fuse Console. For example: http://localhost:8080/hawtio
3. In the login page, enter your user name and password and then click Log In.

1. Install Fuse on the Karaf container. For step-by-step instructions, see Installing on Apache Karaf.

2. In the command line, navigate to the directory in which you installed Red Hat Fuse and run the following command to start Fuse standalone:

   ./bin/fuse

   Copy to Clipboard Toggle word wrap

   The Karaf console starts and shows version information, the default Fuse Console URL, and a list of common commands.

3. In a browser, enter the URL to connect to the Fuse Console. For example: http://localhost:8181/hawtio
4. In the login page, enter your user name and password and then click Log In.

1. Open the Red Hat Fuse etc/users.properties file in an editor.

2. Add an entry for the user name, password, and role.

   For example, the following entry in the etc/users.properties file defines the admin user and grants the admin role.

   admin = secretpass,admin

   Copy to Clipboard Toggle word wrap
3. Save the file.

1. To determine the hawtio-web bundle ID, use the following command to list the Fuse bundles that the Fuse Console uses:

   osgi:list | grep hawtio

2. To stop the bundle, use the osgi:stop command. For example, if the hawtio :: Web console bundle has an ID of 246, type this command:

   osgi:stop 246

1. In the tree view, select an MBean.
2. Click the Attributes tab.
3. Click an attribute to see its details.

1. In the tree view, select an MBean.
2. Click the Operations tab, expand one of the listed operations.
3. Click Execute to run the operation.

1. In the tree view, select an item.
2. Click the Chart tab.

1. Click the Runtime tab and then the Threads subtab. The Threads page lists active threads and stack trace details for each thread. By default, the thread list shows all threads in descending ID order.
2. To sort the list by increasing ID, click the ID column label.
3. Optionally, filter the list by thread state (for example, Blocked) or by thread name.
4. To drill down to detailed information for a specific thread, such as the lock class name and full stack trace for that thread, in the Actions column, click More.

1. In the upper right corner of the Fuse Console, click the user icon and then click Preferences.

   

   View larger image

   
2. Increase the value of the Maximum collection size option (the default is 50,000).
3. Click Close.

Procedure

1. Login to OpenShift with administrator permissions:

   $ oc login -u system:admin

   Copy to Clipboard Toggle word wrap

2. Install the custom resource definitions necessary for running the Prometheus operator, where {$templates-base-url} is the location of the Fuse on OpenShift template files:

   $ oc create -f {$templates-base-url}\fuse-prometheus-crd.yml

   Copy to Clipboard Toggle word wrap

   The Prometheus operator is now available to any namespace on the cluster.

3. Install the Prometheus operator to your namespace by using the following command syntax:

   $ oc process -f {$templates-base-url}/fuse-prometheus-operator.yml -p NAMESPACE=<YOUR NAMESPACE> | oc create -f -

   Copy to Clipboard Toggle word wrap

   For example, use this command for a project (namespace) named myproject:

   oc process -f {$templates-base-url}/fuse-prometheus-operator.yml -p NAMESPACE=myproject | oc create -f -

   Copy to Clipboard Toggle word wrap
   Note

   The first time that you install the Prometheus operator into a namespace, it might take a few minutes for the Prometheus resource pods to start. Subsequently, if you install it to other namespaces on your cluster, the Prometheus resource pods start much faster.

4. Instruct the Prometheus operator to monitor the Fuse application in the project by using the following command syntax::

   $ oc process -f {$templates-base-url}/fuse-servicemonitor.yml -p NAMESPACE=<YOUR NAMESPACE> FUSE_SERVICE_NAME=<YOUR FUSE SERVICE> | oc apply -f -

   Copy to Clipboard Toggle word wrap

   For example, use this command for an OpenShift project (namespace) named myproject that includes a Fuse application named myfuseapp:

   oc process -f {$templates-base-url}/fuse-servicemonitor.yml -p NAMESPACE=myproject FUSE_SERVICE_NAME=myfuseapp | oc apply -f -

   Copy to Clipboard Toggle word wrap

5. To open the Prometheus dashboard:

   1. Login to the OpenShift console.
   2. Open the project to which you added Prometheus.

   3. In the left pane, select Applications → Routes.

      

      View larger image

      

   4. Click the Prometheus Hostname URL to open the Prometheus dashboard in a new browser tab or window.

      

      View larger image

      
   5. For information about getting started with Prometheus, go to: https://prometheus.io/docs/prometheus/latest/getting_started/