Adding Apache Ignite

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

  1. Log into the eG administrative interface.
  2. Click on the Add Component button in the right corner of the Components at a Glance page that appeared or follow the Infrastructure -> Components -> Add/Modify menu sequence.

  3. The Components page will then appear. In the Components page, select Apache Ignite as the Component type and click the Add New Component button.

  4. Figure 1 will then appear.

    Figure 1 : Adding Apache Ignite

  5. Specify the Host IP/Name and the Nick name for the Apache Ignite component.

  6. The Agentless flag is enabled by default, as 'agentless' is the default monitoring approach for the Apache Ignite.

  7. Do not disturb the default settings of the OS and Mode drop-down lists.

  8. Pick a remote agent from the Remote agent list box.

  9. Pick an external agent from the External agents list box and click the Add button to add the component for monitoring.

  10. Once the Apache Ignite component is added successfully, you will be again redirected to the Components page (see Figure 2). Using the options provided in the Components page, 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 Ignite component

  11. To collect the performance metrics, you may need to manually configure the tests that are mapped to the Apache Ignite. 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 Ignite will be listed in the Unconfigured Tests list box.

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

  12. Now, click on the Ignite Always Failover SPI test to configure it. To know how to configure this test, refer to Ignite Always Failover SPI Test.

  13. The remaining tests will be automatically configured once the Ignite Always Failover SPI test is configured.

  14. To configure Windows ServiceTest, refer to Monitoring Unix-and-Windows-Servers/Windows.

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