hbase-protobuf-python | ||
.gitignore | ||
Dockerfile | ||
env-hbase-exporter.j2 | ||
hbase-exporter | ||
hbase-exporter.service | ||
hbase-hbck.service | ||
hbase-hbck.timer | ||
hbase-write | ||
Makefile | ||
README.md | ||
requirements.txt |
hbase-exporter
An HBase Prometheus Exporter
Relays JMX metrics for consumption by Prometheus
The exporter parses the (Hortonworks) Hadoop config and uses (Hortonworks) Hadoop internal tooling to determine e.g. the currently active master so that it can run in different environments without requiring any configuration
Those tools are not yet included when building the app as a container
Since some important metrics are missing or empty in JMX, we additionally parse the HBase Master UI for e.g. 'Stale regions in transition'
The hbase hbck log is parsed to check for inconsistencies in HBase. The log is created independently from the exporter with the help of a systemd-timer unit and a systemd-hbck-service unit
Unfortunately querying the active namenode requires superuser privileges
For python module requirements see requirements.txt
$ sudo dnf/pkg install python36
# As the user executing the exporter:
$ pip3[.6] install --user -r requirements.txt
To generate the necessary HBase Python Protobuf bindings, run the Makefile The protobuf compiler is necessary to build them
Install the protobuf compiler
$ sudo dnf/pkg install protobuf-c
Run make
$ make
Issues
Import paths do not work in generated protobufs when used from a subdir https://github.com/protocolbuffers/protobuf/issues/1491 The solution used here is mentioned in the comments: https://github.com/protocolbuffers/protobuf/issues/1491#issuecomment-547504972