Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[zookeeper] bytes_received and bytes_sent metrics do not represent bytes #816

Closed
eliaslevy opened this issue Oct 18, 2017 · 0 comments
Closed
Assignees

Comments

@eliaslevy
Copy link
Contributor

The zookeeper.bytes_received and zookeeper.bytes_sent metrics are misnamed.

The data for these metrics is collected from the ZK stat command, which prints Received and Sent fields. But these fields represent packets received and sent, not bytes. This in turn means that the DD ZK dashboard is wrong when it displays the data in a widget named Bytes sent/received/outstanding per second.

In addition, both metrics are being submitted as gauge types. In reality they are monotonic counts, except they are not truly monotonic as they can be reset using the ZK srst command and they will reset if the ZK server is restarted.

It appears that the developers of the ZK dashboard where aware of the wrong metric type applied to zookeeper.bytes_received and zookeeper.bytes_sent, as the dashboard uses the per_second function to convert the "gauges" into rates.

As an aside, the ZK dashboard mistakenly displays the zookeeper.bytes_outstanding metric in the same widget as the zookeeper.bytes_received and zookeeper.bytes_sent metrics. Even if those two metrics did refer to received and sent bytes displaying zookeeper.bytes_outstanding with them would be an error. As the comment in the collector notes, that metric refers to outstanding requests, not outstanding bytes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants