Monitoring Hazelcast

Edit online

After you install the Instana host agent, the Hazelcast sensor is automatically installed and enabled. You can view metrics that are related to Hazelcast in the Instana UI.

Support information

Edit online

To make sure that the Hazelcast sensor is compatible with your current setup, check the following support information sections:

Supported versions and support policy

Edit online

The following table shows the latest supported version and support policy:

Technology Support policy Latest technology version Latest supported version
Hazelcast IMDG 45 days 4.2.8 4.2.8

For more information about the support policy, see Support strategy for sensors.

Supported client-side tracing

Edit online

For this technology, Instana supports client-side tracing for the following language:

Configuration

Edit online

The agent natively monitors the Hazelcast, and configuration is optional.

Configuring the polling rate

Edit online
Note: Instana Hazelcast sensor 1.3.6 and later support configuring the polling rate to reduce data ingestion. This feature is supported on self-hosted Instana backend 311 and later.

You can configure how often Instana polls Hazelcast to collect data and metrics by using the poll_rate parameter in the agent configuration.yaml file as shown in the following example:

com.instana.plugin.hazelcast:
  poll_rate: 1 # values are in seconds. Default value is 1 second.
Note: If no specific polling interval is provided, the default polling interval is 1 second.

Viewing metrics

Edit online

To view the metrics, complete the following steps:

  1. In the sidebar of the Instana UI, select Infrastructure.
  2. Click the specific monitored host.

Then, you can see a host dashboard with all the collected metrics and monitored processes.

Node-level

Edit online

Configuration data

Edit online
  • Node name (returned by HazelcastInstance::getName()).
  • Node address
  • Node UUID
  • Group name
  • Cluster ID (starting with Hazelcast 3.5)
  • Version (starting with Hazelcast 3.2)
  • OpenSource/ Enterprise version (starting with Hazelcast 3.2)
  • Lite Member Status (starting with Hazelcast 3.6)

Instana extracts the labels for the Hazelcast instances by using the node address and the cluster name, for example [127.0.0.1:5701]@my-cluster-5c07d2.

Performance metrics

Edit online
  • Operation Count (starting with Hazelcast 3.2)
  • MigrationQueue Size
  • EventQueue Size (starting with Hazelcast 3.2)
  • Distributed Objects (starting with Hazelcast 3.5)
  • ExecutionService Queue Size (starting with Hazelcast 3.2)
  • Connected Client Count (starting with Hazelcast 3.2)

Health Signatures

Edit online

Each sensor has a curated knowledge base of health signatures that are evaluated continuously against the incoming metrics and are used to raise issues or incidents depending on user impact.

Built-in events trigger issues or incidents based on failing health signatures on entities, and custom events trigger issues or incidents based on the thresholds of an individual metric of any entity.

For more information about built-events for the Hazelcast node, see the Built-in events reference.

Cluster-level

Edit online

Configuration data

Edit online
  • Cluster ID
  • Group name

Starting with Hazelcast 3.5, the cluster name is a combination of the configured group name and the first characters of the cluster Id, for example, my-cluster-5c07d2. In older Hazelcast versions, only the group name is used, for example, my-cluster.