Monitor and analyze your Apache Zookeeper with this JMX-based extension
Apache Zookeeper automatically detects all applications and microservices deployed in your application server and provides automatic end-to-end tracing, application server metrics and log insights.
Dynatrace visualizes your web application and its dependencies from website to application to container, infrastructure and cloud. It diagnoses anomalies in real-time with AI and pinpoints the root-cause down to the broken code before your customers are even affected. Deep code-level insights combined with market-leading profiling capabilities like method hotspots, error/exception analysis, memory profiling, and thread analysis will help you leverage the robustness of your production environment.
Because of how MBeans are populated in zookeeper, they will look different depending on the architecture of your zookeeper.
Select Add to environment to get started. Easily create configurations for the hosts where your zookeeper is running, and the available JMX metrics will start coming through. Use feature sets to further select the metrics you're interested in.
If your Apache Zookeeper is running on a virtual machine directly, install OneAgent on it to get started.
Activate the JMX extensions for Apache Zookeeper to get full metric insight by selecting Add to environment.
Activate log monitoring to get full log insight.
The Apache Zookeeper Overview dashboard will be included in the extension, where you can see an overview of the Zookeeper JMX metrics ingested by this extension.
The extension also includes three generic types: server, replica and client. Each of these types will be populated automatically and will include out-of-the-box screens and visualizations for their data. To access the lists of these entities or each entity individually, you can use the Apache Zookeeper Overview dashboard as an entry point.
Additionally, all metrics collected by the extension will appear on the unified analysis screens for both the process group instance and the host. Make sure you are viewing the new unified analysis screens to see these metrics.
All metrics can also be viewed with the data explorer, all of them include the zookeeper prefix.
The extension consumes DDU Units. However, they are elgible for the free tier included with every host. The amount of DDUs units depends on the number of processes monitored, their architecture and usage.
When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
| Metric name | Metric key | Description |
|---|---|---|
| Zookeeper - Max latency | zookeeper.server.maxLatency | — |
| Zookeeper - Min latency | zookeeper.server.minLatency | — |
| Zookeeper - Average latency | zookeeper.server.avgLatency | — |
| Metric name | Metric key | Description |
|---|---|---|
| Zookeeper - Max request latency | zookeeper.replica.maxRequestLatency | — |
| Zookeeper - Min request latency | zookeeper.replica.minRequestLatency | — |
| Zookeeper - Average request latency | zookeeper.replica.avgRequestLatency | — |
| Metric name | Metric key | Description |
|---|---|---|
| Zookeeper - Election time taken | zookeeper.replica.electionTimeTaken | — |
| Zookeeper - Leader status | zookeeper.replica.leaderStatus | Equals 1 when the replica is a leader, 0 if it's a follower. |
| Metric name | Metric key | Description |
|---|---|---|
| Zookeeper - Client packets received | zookeeper.client.packetsReceived.count | — |
| Zookeeper - Client packets sent | zookeeper.client.packetsSent.count | — |
| Zookeeper - Client outstanding requests | zookeeper.client.outstandingRequests | — |
| Metric name | Metric key | Description |
|---|---|---|
| Zookeeper - Client average latency | zookeeper.client.avgLatency | — |
| Zookeeper - Client max latency | zookeeper.client.maxLatency | — |
| Zookeeper - Client min latency | zookeeper.client.minLatency | — |
| Metric name | Metric key | Description |
|---|---|---|
| — | zookeeper.server.aliveConnections | — |
| Zookeeper - Packets received | zookeeper.server.packetsReceived.count | — |
| Zookeeper - Packets sent | zookeeper.server.packetsSent.count | — |
| Zookeeper - Outstanding requests | zookeeper.server.outstandingRequests | — |
| Metric name | Metric key | Description |
|---|---|---|
| Zookeeper - Alive connections | zookeeper.replica.aliveConnections | — |
| Zookeeper - Packets received | zookeeper.replica.packetsReceived.count | — |
| Zookeeper - Packets sent | zookeeper.replica.packetsSent.count | — |
| Zookeeper - Outstanding requests | zookeeper.replica.outstandingRequests | — |
| Zookeeper - Pending revalidations | zookeeper.replica.pendingRevalidation.count | — |
| Zookeeper - Auths failed | zookeeper.replica.authFailed.count | — |