Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
Clarify token and session history lifetime guarantees
pulse-triage[bot]ba168bea9f9c
diff --git a/docs/release-control/v6/internal/subsystems/api-contracts.md b/docs/release-control/v6/internal/subsystems/api-contracts.mdindex 9a9a192d9e..fa534ceace 100644--- a/docs/release-control/v6/internal/subsystems/api-contracts.md+++ b/docs/release-control/v6/internal/subsystems/api-contracts.md@@ -25,10 +25,12 @@The existing `/api/metrics-store/history` chart read and canonical agent`get_metric_history` read retain the admitted API token or local browser session-through the complete synchronous lookup and response. Current monitoring-read-scope, credential identity, principal and organisation authority are checked at-output, including after the agent's inventory lookup. Withdrawal before output-returns the fixed 401 rather than metric values or a successful empty series;+through the complete synchronous lookup and response. For API tokens, current+monitoring-read scope, credential identity, principal and organisation authority+are checked at output, including after the agent's inventory lookup. Local+sessions retain the admitted session instance, validity, principal and store.+Withdrawal before output returns the fixed 401 rather than metric values or a+successful empty series;after an admitted prefix it only stops further writes. Handler-specific headersremain undisclosed until an authorised write.@@ -51,7 +53,6 @@ reads and unrelated-scope removal. Existing history query/entitlement/fallbackand shared response-writer tests remain applicable. Consuming browser proof mustuse actual producer responses at desktop and narrow sizes, not a guard skip.-### Agent HTTP redirects retain their configured originManifest discovery, capability HTTP calls and agent SSE reads using standard Godiff --git a/docs/release-control/v6/internal/subsystems/security-privacy.md b/docs/release-control/v6/internal/subsystems/security-privacy.mdindex e975bfebdf..08c1f69a69 100644--- a/docs/release-control/v6/internal/subsystems/security-privacy.md+++ b/docs/release-control/v6/internal/subsystems/security-privacy.md@@ -22,10 +22,12 @@The existing `/api/metrics-store/history` chart read and canonical agent`get_metric_history` read retain the admitted API token or local browser session-through the complete synchronous lookup and response. Current monitoring-read-scope, credential identity, principal and organisation authority are checked at-output, including after the agent's inventory lookup. Withdrawal before output-returns the fixed 401 rather than metric values or a successful empty series;+through the complete synchronous lookup and response. For API tokens, current+monitoring-read scope, credential identity, principal and organisation authority+are checked at output, including after the agent's inventory lookup. Local+sessions retain the admitted session instance, validity, principal and store.+Withdrawal before output returns the fixed 401 rather than metric values or a+successful empty series;after an admitted prefix it only stops further writes. Handler-specific headersremain undisclosed until an authorised write.@@ -48,7 +50,6 @@ reads and unrelated-scope removal. Existing history query/entitlement/fallbackand shared response-writer tests remain applicable. Consuming browser proof mustuse actual producer responses at desktop and narrow sizes, not a guard skip.-### Audit viewer results cannot outlive their reader or pageAudit event details and verification outcomes in Settings are reader-owned.