Correlation boundaries
A deployment marker near an error is a reason to investigate, not a causal conclusion. GitHub import is bounded and cannot reconstruct telemetry before instrumentation. Repositories without a verified deployment mapping are listed as gaps. Restart counters indicate observed changes, not the exact time or cause of a historical restart.
Incident identity and editing
Default workspaces group findings by system and canonical check identity, keeping original issue IDs and transitions. Verified dependencies provide context. Owner groups support private regrouping and filtering without changing the underlying findings. New, ongoing, reopened, unverified, and remediated states come from deterministic inspection. Private owner notes never enter public evidence or AI summaries.
Configuration ownership
A score threshold or provisional availability target can be proposed from the health detail page. Inputs are limited to registered checks, bounded finite thresholds, and validated availability targets. The server opens a Git PR against the deployed configuration, rejecting concurrent base changes. The standard documentation and deployment pipeline applies approved Git changes. Dashboard editing remains in owner Grafana; synchronized originals remain separate from editable copies. Anonymous users cannot submit arbitrary datasource queries, save dashboards, or start jobs.