Adding Apache Flume

eG Enterprise cannot auto-discover an Apache Flume. This implies that you need to manually add the component for monitoring. The steps for manually adding the Apache Flume component are detailed below:

  1. Login to the eG admin interface as user with administrative privileges.
  2. Follow the Infrastructure -> Components -> Add/Modify Component menu sequence in the Admin tile menu.
  3. From the page that appears, select Apache Flume as the Component type and click the Add New Component button.

  4. Figure 1 will then appear.

    Figure 1 : Adding Apache Flume component

  5. In Figure 1, provide the Host IP/Name of the Apache Flume to be monitored. Then, provide a Nick name for the server.

  6. By default, the Auto option will be selected against the Internal agent assignment field. This indicates that by default, eG Enterprise maps every configured IP/nick name with a separate internal agent. To manually define the IP-internal agent association, select the Manual option.
  7. Pick an external agent from the External agents list box and click the Add button to add the component for monitoring.

  8. Once the Apache Flume component is added successfully, you will be again redirected to Figure 2. Using the options provided in the page that appeared, you can modify, unmanage or delete the newly added component. In addition, you can also configure the tests, set thresholds and maintenance policies, and change the IP address.

    Figure 2 : Configuring the Apache Flume component

  9. To collect the performance metrics, you may need to manually configure the tests that are mapped to the Apache Flume. To configure the tests that need manual configuration, click on the icon in Figure 2. This will lead you to the Specific Test Configuration page where the unconfigured tests for the Apache Flume will be listed in the Unconfigured Tests list box.

    Figure 3 : The list of unconfigured tests for the Apache Flume component

  10. Now, click on the Flume Sink test to configure it. To know how to configure this test, refer to Flume Sink Test

  11. The remaining tests will be automatically configured once the Flume Sink test is configured.

  12. To configure File Descriptors and JVM G C tests, refer to Monitoring Oracle Web Logic Application Server:

  13. To configure JVM Leak Suspects test, refer to Monitoring IBM WebSphere LibertyServer.

  14. To configure Processes and Windows Services tests, refer to Monitoring Unix and Windows Servers.

  15. Once all the tests are configured, switch to the Monitor tab to view the performance metrics reported by the tests.