Docs / Capability guide
Private deployments and cell health
Deploy serving cells and check their health before sending traffic.
All capabilities · Related guide · Agent prompt for this capability
When to use this example
After bringing up a private deployment or adding a region, check that the tenant and cell configuration matches where traffic should run. Configuration inspection complements service health, serving and event-pipeline tests before a rollout.
What the example gives you
The inspector reads tenant health and, with operator permission, tenant settings and cells. It provides JSON records for a readiness review; the licensed checkout contains the infrastructure and migration tools that perform deployment.
Before you start
A licensed platform checkout for deployment, infrastructure access, configured secrets/storage and the repository's maintained deployment instructions.
Run the example
Extract the archive and follow README.md for setup, commands, and expected results. Start with workspace_inspect.py. Local tests use sample data.
Python tools accept --help. To connect to your workspace, supply the deployment URLs, credentials and resource IDs required by the tool.
Connect it to your application
Follow the private-deployment guide and maintained manifests for database, plan distribution, serve, events and reporting. Use separate control/data/agent endpoints and run migrations with the migration role.
Inspect tenant health, cells and doctor diagnostics after startup. Confirm compiled-plan freshness, storage/event connectivity and credentials before enabling serving traffic.
Run the existing smoke and benchmark harnesses for the relevant media profile and record the environment. Keep rollback artifacts and verify each region; use the public inspector to check configuration alongside the deployment tools.
Check the result
Verify health, serving responses, and recorded events in each cell. Measure capacity with your own traffic profile and infrastructure.