Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Switch iterator-duration metric to nanoseconds

...

NameRecording LevelMetric TypeDescription
num-open-iteratorsINFOGaugeThe current number of Iterators on the store that have been created, but not yet closed.
iterator-duration-avgDEBUGAverageThe average time spent between creating an Iterator and closing it, in millisecondsnanoseconds.
iterator-duration-maxDEBUGMaximumThe maximum time spent between creating an Iterator and closing it, in millisecondsnanoseconds.
oldest-iterator-open-since-msDEBUGGaugeThe UNIX timestamp the oldest still open iterator was created, in milliseconds.

...

The iterator-duration metrics will be updated whenever an Iterator's close() method is called, recording the time since the Iterator was created. The measurement will be conducted using SystemTime.nanoTimenanoseconds() and reported in milliseconds, with a fractional component approximating the sub-millisecond precisionnanoseconds. e.g. 2.337583 2337583, would be approximately 2 milliseconds, 337 microseconds and 583 nanoseconds. Users would want to monitor this metric and take action if:

...

The oldest-iterator-open-since-ms metric will be updated by tracking all currently open Iterators and taking the min(startTime), where startTime is recorded in the constructor by calling SystemTime.currentTimeMillismilliseconds(). Users will want to take action if:

...