ReadonlyabsentSuccessful has calls answering false.
ReadonlyageMonotonic ms since the last settled call.
ReadonlyaliasThe configured source alias (always equal to the snapshot's alias).
ReadonlycountSettled calls observed.
ReadonlyfailedRejected (or synchronously throwing) calls.
ReadonlyhitsSuccessful get calls answering a non-null value.
ReadonlylastInteger ms of the most recent timed call; null when none was timed.
ReadonlymissesSuccessful get calls answering null.
ReadonlynotSuccessful delete calls answering false.
ReadonlyoperationThe backend operation these counters describe.
ReadonlypresentSuccessful has calls answering true.
ReadonlyremovedSuccessful delete calls answering true.
ReadonlysucceededFulfilled calls.
Cumulative counters for one (source alias, operation) pair (M98i).
Every settled backend call increments
countand exactly one ofsucceeded(fulfilled) orfailed(rejected, or threw synchronously). The detail counters increment only on a SUCCESSFUL call of their matching operation:hits/missesforget(non-null /nullresult),present/absentforhas,removed/notRemovedfordelete.setandclearcarry only the outcome counters; every non-applicable counter is0. Every counter saturates independently atNumber.MAX_SAFE_INTEGER. No eviction count exists: a miss is never reported as an eviction.lastDurationMsis the integer duration, on the runtime's monotonic clock, of the most recently settled TIMED call — a source may time only a sample of calls (the built-in cache source times the first call per operation and one in every eight after it) — and isnullwhen no call in the current retention window was timed.ageMsis the elapsed time since the most recent settled call, timed or not. Keys, prefixes, values, factory results and errors are never carried.Since
0.8.0