Statics (managed sessions)
Statics are long-lived, platform-managed analytics surfaces shown in the dashboard navigation (for example Resource Monitor). Each static runs a dedicated session from a session template on a schedule. Those backing sessions are kept in a system project and do not appear in normal trainee session lists.
What operators see
- Entries in the Next dashboard navigation (via v2 statics APIs) with title, icon, and section.
- Refreshed KPIs and charts on an interval defined for that static (see below).
- Access controlled by role and minimum view privilege on the definition.
Use Cluster Manager to inspect environment health. Use the dashboard statics entries for day-to-day cluster resource monitoring.
Shipped example: Resource Monitor
Current HEAT installs ship Resource Monitor (system-resource-monitor):
| Aspect | Typical value |
|---|---|
| Purpose | Kubernetes resource usage over time |
| Refresh | About 1 minute |
| Dashboard | Next (ui/dashboard), template heat-system-resource-monitor-next |
| Chart | Timeline-style panel fed by cluster-report rollup outputs |
High-frequency refresh creates many node outputs per day. The platform can rotate backing sessions (for example every 24h) so each window gets a fresh session graph, and can archive older outputs inside a session using session retention on the template.
Scope
Statics can be scoped per deployment design:
| Scope | Meaning |
|---|---|
| GlobalSingleton | One instance for the whole environment |
| PerProject | One instance per project |
| PerUser | One instance per user |
Your deployment team configures which statics exist and who can view them.
Related
- Sessions and Session templates
- Session retention
- Next dashboard components
- v2 API statics endpoints (dimensions catalog and navigation)
- Cluster Manager
Platform rotation hour: system.statics.global_singleton_session_rotate_hour_utc in Platform configuration. Implementation detail (presets, Core API) is internal-only.