eG Monitoring
 

Measures reported by AWSMSKZooKeeTest

In a distributed application cluster, clients are the nodes that access information from the Zookeeper servers grouped within a Zookeeper ensemble. At frequent intervals, every client sends a message to the server to let the sever know that the client is alive. Likewise, the server too sends an acknowledgement when a client connects. If there is no response from the connected server, the client automatically redirects the message to another server. If the clients are overloaded with requests or if the client takes too long to connect to the target AWS Managed Service Kafka, the requests could not be processed swiftly leading to time delays. To avoid such time delays and to ensure that the requests are processed faster, it is essential to keep track on the clients connecting to the target server. The AWSMSKZooKeeTest helps administrators in this regard!

This test also helps administrators determine which client is taking too long to process the requests and the client on which too many connections are currently active.

Outputs of the test: One set of results for each client connecting to the Zookeeper in the target AWS Managed Service Kafka server.

Descriptor: Client connecting to the Zookeeper

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
volumeQueueLength Indicates the status of the client’s connection to Zookeeper.  

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
No connection 0
Closed 3
Authentication failed 5
Not connected 10
Associating 70
Connecting 80
Connected read only 90
Connected 100

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the status of the broker’s connection to Zookeeper.
zooKeeperRequestLatencyM Indicates the average time taken to process the requests received from this client. Millisecs