Get Object Cache Status

A site can look like it has object caching switched on while nothing is actually being cached.

debugging/get-object-cache-status reports whether a persistent object cache is really connected, which backend and drop-in it uses, and its hit ratio.

At a glance

Abilitydebugging/get-object-cache-status
ToolsetDiagnostics — toolset/diagnostics
GroupDiagnostics › Query Monitor
RequiresQuery Monitor, active on the site
Capabilitymanage_options
SafetyRead-only — changes nothing
RepeatableIdempotent — running it twice leaves the same result
Ships inAcrossAI Abilities Manager 0.0.43 and later

How it works

It takes no parameters.

It reports whether an external object-cache drop-in is in place, which backend it points at, and the hit and miss counts with the resulting ratio. It changes nothing.

Input

This ability takes no parameters.

What comes back

NameTypeWhat it is
persistentbooleanWhether a persistent object cache is connected.
backendstringThe backend / drop-in in use, such as Redis or Memcached.
hit_rationumberThe cache hit ratio, with the underlying hit and miss counts.
activebooleanWhether Query Monitor is active on the site.
successbooleanWhether the call completed.
messagestringA one-line summary of what happened, suitable for showing a human.
error_codestringPresent only on failure — a stable machine-readable reason.

Example

Ask your assistant:

Is a persistent object cache connected, and what’s the hit ratio?

It resolves to one call:

{
  "ability": "debugging/get-object-cache-status",
  "parameters": {}
}

Worth knowing

  • Read-only.
  • A low hit ratio, or no backend, is the usual sign caching is switched on but not working.
  • Needs the Query Monitor plugin active; without it you get a clear “not active” message.

Related abilities


Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager

Browse the rest: Every ability, by category


Keep reading