[Zookeeper] TSDB Enablement

[agithomas]

TSDB Enablement

• PR link - Zookeeper TSDB Enablement #8104

Test Environment Setup

• Creation of Test Environment

Datastream : connection

• Add dimension fields - [Zookeeper] Added dimensions mapping to Zookeeper connection datastream #8059
• Add metric_type mappings - [Zookeeper] Added metric type mapping for connection datastream #7765
• TSDB Package test completion

Datastream : mntr

• Add dimension fields - Added dimension mapping to zookeeper mntr datastream #8069
• Add metric_type mappings - [Zookeeper] Add metric type mapping for mntr datastream #7779
• TSDB Package test completion

Datastream : server

• Add dimension fields - [Zookeeper] Added dimensions mapping to server datastream #8081
• Add metric_type mappings - [Zookeeper] Add metric type mapping for server datastream #7885
• TSDB Package test completion

[lalit-satapathy]

Hi @agithomas,

Can we cross-check and explain the metric type mapping of the following fields currently marked as gauge (but seemingly counters)?

• num_alive_connections
• packets.received (already fixed)
• packets.sent(already fixed)
• znode_count
• node_count

[agithomas]

• num_alive_connections

[agithomas]

• znode_count
  Explanation i found :
  zk_znode_count is the total count of znodes stored in the ZooKeeper ensemble. Every time a client creates a new znode, this counter will increment. Every time a client deletes a new znode (either explicitly or by dropping its ephemeral znodes after disconnection), this counter will decrement.

So, this field must be gauge.

[agithomas]

• node_count

This is the explanation i found. node count is the number of znodes in the ZooKeeper namespace (the data). On basis of the comment, it is hence treated as a Gauge field. Also, during the testing, i never witnessed a monotonically incrementing value for this field.