Skip to content

Conversation

@mths1
Copy link
Contributor

@mths1 mths1 commented May 9, 2023

No description provided.

All available labels can be show using `vmq-admin metrics show --help`.

{% hint style="warning" %}
VerneMQ is a implemented in Erlang, which is a highly concurrent system, and follows a fail fast machanism. It might happen that in some scenarios the metrics do not seem to "match". One typcial example is sockets_open and sockets_close. In case of failure, the sockets_close metric might not be increased and thus there is a difference between opened sockets and closed sockets. The metric is nonetheless useful when inspecting the the running system.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to suggest that the metrics are somehow allowed to be wrong. For a Verne lifecycle (boot to boot) we expect metrics to be correct, though. Even socket close and open. If not, we missed a code flow to trigger counters.
After a reboot, those metrics are reset. So, I guess it depends what we mean by "In case of failure" in the snippet.
Just don't want to confuse readers, that's the main thing.

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

Successfully merging this pull request may close these issues.

2 participants