Understanding `status json` output

Could someone help with an explanation of the distinctions among the following details found in the exposed status JSON?

  1. Difference between transactions allowed per minute vs transactions released per minute?
    cluster.qos.transactions_per_second_limit vs cluster.qos.released_transactions_per_second
  2. How do ‘operation read requests’ and ‘operations read’ differ? Does it point to read failures/ read not able to keep up cluster and/or cache hits vs disk read?
    cluster.workload.operations.read_requests.counter vs cluster.workload.operations.reads.counter
  3. Differences in latency probe between transaction start seconds, transactions commit seconds and transactions read second?
    cluster.latency_probe.start_seconds vs cluster.latency_probe.commit_seconds vs cluster.latency_probe.read_seconds

Not sure of the answers to some of your specific questions, but if you haven’t already read it, the Monitored Metrics page in the docs is helpful for some of these.

1 Like