Metabridge redis manager
updated 2026-07-09 · 21:04 utc verify api · read-only
fleet status — object cache pro
serving healthy · registry drifting (24)
database capacity 75/100 25 slots free · next → db 76
memory used 57% 1.72G / 3.00G · peak 73%
cache hit rate 90% 163.5M hits · 17.0M misses
wordpress sites 69 61 complete · 4 partial · 4 absent
GET /fleet/health

Capacity & memory

database slots 75 / 100
highest assigned db 75next db 76status ok
memory (allkeys-lru) 1.72G / 3.00G
used 57%peak 73% (2.20G)evicted 0
cache efficiency 90% hit rate
hits 163,535,204misses 16,950,183uptime 12d 9h
GET /fleet/drift

Reconciliation · not clean

Duplicate database
db 74 shared by windshieldsxpress.com and wsx-staging.stagingdemo.dev
1
Orphaned Redis DBs
live keys, no registry entry — db 6, 9, 11, 14, 18, 30, 35, 46, 52, 61, 66, 67, 75
13
Unregistered sites
WordPress present, never assigned a DB in the registry
6
Partial deployments
missing a drop-in or the Object Cache Pro plugin
4
Config mismatches & missing sites
registry DB numbers all agree with wp-config — nothing to fix
0
GET /fleet/scan

Deployment state

Object Cache Pro has four moving parts per site — the drop-in, the plugin, the mu-plugin loader, and the wp-config require. A site is complete only when all four are present.

61 complete
4
4
complete · all four components partial · some components absent · no cache config
DomainDBStateComponents (drop-in · plugin · mu · config)
5starwindowtint.com4complete
ae-ppf.com5complete
apexcustominnovations.compartial
elitemotorsportsla.com26partial
expertcustomstulsa.compartial
lockerhometint.com44partial
eclipsesolarcontrol.comabsent

Showing 7 representative rows of 69 sites · 71 vhosts scanned total.

GET /fleet/redis

Keyspace distribution

Each database rendered as one bar — the same twin-peaked geometry as the Metabridge mark. Tall bars are busy tenants; the short flagged bars are Redis DBs with live keys but no registry entry.

736,330 keys across 75 databases
assigned orphaned (13) duplicate (db 74)
db 1db 21 · peak 73,062db 68 · peak 86,991db 75
GET /registry

Assignment map

The source of truth for which site owns which Redis DB. Append-only by design.

DomainDBStatusAssignedSource
5starwindowtint.com4active2026-04-16wp-config
ae-ppf.com5active2026-04-16wp-config
ap3-ppf.com7active2026-04-16wp-config
asaptintppf.com8active2026-04-16wp-config
bakerswindowtint.com10active2026-04-16wp-config
capitalautobahnd.com13active2026-04-16wp-config

Showing 6 of 63 assignments · redis-wp @ 127.0.0.1:6379.

The one rule. A site's DB number is never renumbered or reused once assigned — renumbering forces that site to rebuild its entire object cache. Released numbers are quarantined, never handed out again.