-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Derived iostat metrics #30
Comments
Oops, sorry this was a |
jmangs
pushed a commit
to jmangs/opentsdb
that referenced
this issue
Aug 8, 2014
jzeeck
added a commit
to jzeeck/opentsdb
that referenced
this issue
Aug 26, 2014
Consolidate basetime calculation into one place
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
iostat
derives a few values from the counters we already collect iniostat.py
such as (from theiostat
manual):await
: The average time (in milliseconds) for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them.svctm
: The average service time (in milliseconds) for I/O requests that were issued to the device.%util
: Percentage of CPU time during which I/O requests were issued to the device (bandwidth utilization for the device). Device saturation occurs when this value is close to 100%.These are to be taken with a grain of salt (a lot of people really believe that
%util
accurately reflect the percentage of utilization of the I/O subsystem) but they would be useful to have anyway.For reference, the code of
iostat
is here.The text was updated successfully, but these errors were encountered: