Monitoring Apache HBase

Edit online

The Apache HBase sensor is automatically deployed and installed after you install the Instana agent.

Support information

Edit online

To make sure that the Apache HBase 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
Apache Hbase On demand 2.6.2 2.6.1

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 Apache HBase, and configuration is optional.

Configuring the polling rate

Edit online
Note: Instana Apache HBase sensor 1.1.3 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 Apache HBase 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.hbase:
  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.

Metrics collection

Edit online

To view the metrics, select Infrastructure in the sidebar of the Instana User interface, click a specific monitored host, and then you can see a host dashboard with all the collected metrics and monitored processes.

Configuration data

Edit online
  • Process ID
  • Version
  • Started at
  • Sinks
  • Sources
  • Region Servers
  • Dead Region Servers
  • Cluster ID
  • Active Master
  • Server Name
  • Region Server
  • Zookeeper

Performance metrics

Edit online
  • Master Server
  • Statistics
  • Publish
  • Snapshot
  • Region Server
    • Split
    • Compaction
    • Flush
    • Store File
    • Block Cache

Health Signatures

Edit online

For each sensor, there is a curated knowledgebase 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 information about built-events for the Apache HBase sensor, see Built-in events reference.