Operational Health
The Pavri dashboard exposes operator-facing health indicators directly in the shell so teams can separate product issues from agent issues more quickly.
Support status
| Area | Status | Notes |
|---|---|---|
| Dashboard/API query metrics | Available | Query latency and freshness signals are part of the dashboard experience. |
| Dependency posture summary | Available | The shell exposes high-level dependency health for the core operator path. |
| Full observability control plane | Not available | Use your platform observability tooling for service and infrastructure analytics. |
What these panels represent
- browser-facing query latency and freshness signals for active dashboard APIs
- dependency posture for the core Pavri data path
- a compact operational summary for the current tenant context
What these panels are not
Operational Health is not a full SRE or platform-ops console. It is meant to answer:
- Is the dashboard getting fresh enough data to trust what I am seeing?
- Is there an obvious dependency or control-plane issue affecting my workflow?
For deeper operational review, use the backoffice service-health surfaces and platform observability tooling.