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

Resolution for mqtt.message.pub_to_sub.latency.* #12

Open
KrlosWd opened this issue Jun 14, 2017 · 0 comments
Open

Resolution for mqtt.message.pub_to_sub.latency.* #12

KrlosWd opened this issue Jun 14, 2017 · 0 comments

Comments

@KrlosWd
Copy link

KrlosWd commented Jun 14, 2017

Hello,

After working with mzbench + vmq_mzbench for a while, I noticed that the resolution for mqtt.message.pub_to_sub.latency.50, mqtt.message.pub_to_sub.latency.90, mqtt.message.pub_to_sub.latency.99, mqtt.message.pub_to_sub.latency.999 and mqtt.message.pub_to_sub.latency.mean is reduced due to the fact of using an exponential notation to save the data (e.g. 1.23e4). Is that something that we can configure? otherwise I think it would be a good improvement to save those values with as much resolution as possible.

Thanks in advance for your attention/help!

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

1 participant