Skip to content

armgit / Pulse

Public Imported from GitHub
0

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.

Reconcile published contracts and alert-first drawers with reviewed maintenance

pulse-triage[bot]db2615f4dad8
diff --cc docs/release-control/v6/internal/subsystems/agent-lifecycle.md
index 5266071948,6b97e33194..50e9dc861d
--- a/docs/release-control/v6/internal/subsystems/agent-lifecycle.md
+++ b/docs/release-control/v6/internal/subsystems/agent-lifecycle.md
@@@ -15,55 -15,14 +15,63 @@@
## Purpose
+### Unraid/QNAP removal retires exact boot entries and confirms watchdog quiescence
+
+The Unix uninstall caller selects these platforms from their vendor/installed
+footprints, not from an ordinary recovered Linux state directory or QNAP state
+finder alone. Existing exact state-removal authority must select the wrapper's
+state directory. Regular root-owned files and parents are required; FAT boot
+volumes cannot be assumed to implement Unix chmod semantics. Unknown wrapper
+ownership and missing observation tools refuse before mutation.
+
+One complete bounded boot-file parse admits only the exact generated Unraid
+launch or canonical QNAP deferred block/legacy direct launch for that wrapper.
+All duplicates retire; unrelated entries (including co-installed names and
+legacy Telegraf) remain. Foreign/indirect targets, partial or changed blocks,
+linked/non-regular files, binary/incomplete content and over-1-MiB files refuse
+without evaluating or disclosing their text. The original remains in a private
+`.pulse-removal.*` recovery directory outside the active boot namespace through
+remote confirmation. A changed source during staging or a concurrently created
+file, directory or symlink refuses without clobbering it; interrupted staging
+retains the actual original and never restores automatic activation. New boot
+content uses no-clobber file creation, compatible with FAT without hard links;
+this is not an atomic whole-content swap or a lock against external root writers.
+
+Complete bounded kernel evidence returns only numeric IDs and roles. Only exact
+selected watchdog/collector processes receive checked TERM, watchdog first,
+with independent absence observations. Editor sessions, backup wrappers and
+co-installed names are not targets. Relative/foreign same-name processes or
+unattributable QNAP deferred autorun or live Unraid go shells refuse instead
+of signalling another boot owner. A live go shell may already hold later boot
+commands in memory; editing its file cannot establish quiescence. Failed/diagnostic/duplicate/empty reads and ignored/refused signals
+retain identity, credentials, trust and recoverable files. QNAP mount and
+unmount each have checked bounded results, including cleanup after partial mount.
+
+Whole boot/process and applicable init-manager quiescence closes again before
+same-instance server removal and before local erasure; late activation refuses,
+even after remote removal succeeded. NAS paths do not subsequently run the
+unchecked global pkill or delete arbitrary discovered QNAP state/whole legacy
+Unraid directories. Successful/absent/repeated removal still requires complete
+fresh observations. No automatic restart, credential churn or transport-policy
+change follows a partial operation.
+
+`TestInstallSHNASBootOwnersQuiesceBeforeRecoveryErasure` requires all eighteen
+actual-function/full-uninstall caller controls in `agent_nas_teardown.py`. The
+boot filesystem transformations are real private user operations; flash/kernel
+faults are closed models. Two generated watchdog/child controls use real private
+ordinary-user processes, not appliance mounts or root services. Native signed
+Unraid/QNAP/Linux/PowerShell, TLS/identity/repetition/cleanup and containing
+publication remain separate obligations; this source proof does not resolve
+#1099 or claim installed restoration.
+
+ ### Patrol maintenance coverage adds no agent authority
+
+ The Patrol operator-state projection in `internal/api/router.go` now reads the
+ active maintenance occurrence (one-shot or recurring) and inherits ancestor
+ windows scoped `resource_and_descendants`, as alert intent does. It only
+ auto-dismisses new findings; it adds no agent route, command or execution
+ authority, and remediation locks stay exact-resource state.
+
### Pro Patrol default adds no agent authority
The Patrol autonomy handler change only reports whether the Pro Ask first
diff --cc docs/release-control/v6/internal/subsystems/deployment-installability.md
index 5057eedde5,40c3c1f2ff..6d6d67c114
--- a/docs/release-control/v6/internal/subsystems/deployment-installability.md
+++ b/docs/release-control/v6/internal/subsystems/deployment-installability.md
@@@ -16,98 -16,12 +16,61 @@@
## Purpose
+### Unraid/QNAP removal retires exact boot entries and confirms watchdog quiescence
+
+The Unix uninstall caller selects these platforms from their vendor/installed
+footprints, not from an ordinary recovered Linux state directory or QNAP state
+finder alone. Existing exact state-removal authority must select the wrapper's
+state directory. Regular root-owned files and parents are required; FAT boot
+volumes cannot be assumed to implement Unix chmod semantics. Unknown wrapper
+ownership and missing observation tools refuse before mutation.
+
+One complete bounded boot-file parse admits only the exact generated Unraid
+launch or canonical QNAP deferred block/legacy direct launch for that wrapper.
+All duplicates retire; unrelated entries (including co-installed names and
+legacy Telegraf) remain. Foreign/indirect targets, partial or changed blocks,
+linked/non-regular files, binary/incomplete content and over-1-MiB files refuse
+without evaluating or disclosing their text. The original remains in a private
+`.pulse-removal.*` recovery directory outside the active boot namespace through
+remote confirmation. A changed source during staging or a concurrently created
+file, directory or symlink refuses without clobbering it; interrupted staging
+retains the actual original and never restores automatic activation. New boot
+content uses no-clobber file creation, compatible with FAT without hard links;
+this is not an atomic whole-content swap or a lock against external root writers.
+
+Complete bounded kernel evidence returns only numeric IDs and roles. Only exact
+selected watchdog/collector processes receive checked TERM, watchdog first,
+with independent absence observations. Editor sessions, backup wrappers and
+co-installed names are not targets. Relative/foreign same-name processes or
+unattributable QNAP deferred autorun or live Unraid go shells refuse instead
+of signalling another boot owner. A live go shell may already hold later boot
+commands in memory; editing its file cannot establish quiescence. Failed/diagnostic/duplicate/empty reads and ignored/refused signals
+retain identity, credentials, trust and recoverable files. QNAP mount and
+unmount each have checked bounded results, including cleanup after partial mount.
+
+Whole boot/process and applicable init-manager quiescence closes again before
+same-instance server removal and before local erasure; late activation refuses,
+even after remote removal succeeded. NAS paths do not subsequently run the
+unchecked global pkill or delete arbitrary discovered QNAP state/whole legacy
+Unraid directories. Successful/absent/repeated removal still requires complete
+fresh observations. No automatic restart, credential churn or transport-policy
+change follows a partial operation.
+
+`TestInstallSHNASBootOwnersQuiesceBeforeRecoveryErasure` requires all eighteen
+actual-function/full-uninstall caller controls in `agent_nas_teardown.py`. The
+boot filesystem transformations are real private user operations; flash/kernel
+faults are closed models. Two generated watchdog/child controls use real private
+ordinary-user processes, not appliance mounts or root services. Native signed
+Unraid/QNAP/Linux/PowerShell, TLS/identity/repetition/cleanup and containing
+publication remain separate obligations; this source proof does not resolve
+#1099 or claim installed restoration.
+
### TrueNAS SCALE removal retires every owned middleware boot task before recovery erasure
- TrueNAS SCALE has an independent activation owner: its Init/Shutdown bootstrap
- can recreate and enable the systemd unit after a normal disable. A recovered
- state directory or an unrelated `/etc/version` alone is not appliance identity.
- The uninstall caller selects SCALE only from a bootstrap footprint or vendor
- marker. The existing protected/explicit state-removal authority must select the
- same state directory and exact bootstrap path; linked, writable or non-regular
- bootstrap files refuse before task/service mutation.
-
- One complete, bounded middleware inventory must identify every exact generated
- SCRIPT/POSTINIT task, including duplicates. Unknown ownership, indirect command
- activation or another-install bootstrap refuses without deleting unrelated
- tasks. The JSON reader rejects duplicate keys/IDs, invalid types, failed/empty/
- diagnostic/incomplete reads, over 512 tasks or over 1 MiB; it returns only owned
- numeric IDs and enablement, never task commands, names or credentials. A
- missing/empty SCRIPT path or COMMAND target is unknown activation, not an
- unrelated task or evidence that the owned task is absent. All owned
- tasks are disabled with checked calls and independent exact-set readback before
- systemd stop. A partial stop/disable stays stopped/disabled: do not re-enable or
- automatically restart after a refusal.
-
- The complete systemd target set and independent kernel collector/bootstrap
- process inventory and a final exact disabled-task readback must be quiescent
- before same-instance server removal, including task changes during systemd stop.
- After remote confirmation, the exact disabled task set is re-read before the first
- task deletion. Every owned deletion is checked; final whole-unit/process
- quiescence and complete task absence precede credential, stored binary,
- bootstrap and state erasure. A changed set, refusal, ignored deletion, new task
- or reactivation retains local recovery, even if earlier task/server operations
- succeeded. No favourable replacement observation, task recreation or credential
- churn is performed. Unrelated tasks survive unchanged.
-
- `TestInstallSHTrueNASScaleBootTasksRetireBeforeRecoveryErasure` requires all
- sixteen `agent_truenas_teardown.py` actual-function/full-caller controls,
- including multiple tasks, partial/refused/unknown operations, post-remote
- changes, ignored/recreated deletion, process privacy and a real timeout child.
- These run against closed middleware/systemd/process models and private ordinary-
- user files, not a native appliance. Existing systemd/OpenRC/DSM/rc.d/SysV gates,
- transport trust and identity remain. TrueNAS CORE retains its linked rc.d/
- appliance refusal; Unraid/QNAP boot ownership, Windows and signed installed
- Linux/PowerShell/native/TLS/cleanup acceptance remain separate. This does not
- expand the original removal job into macOS or introduce another dispatcher.
+ The [agent lifecycle removal contract](agent-lifecycle.md#truenas-scale-removal-retires-every-owned-middleware-boot-task-before-recovery-erasure)
+ owns this manager's activation, quiescence, recovery-retention and erasure
+ requirements, including the registered source controls and native-qualification
+ boundary. The deployment entrypoint must preserve that contract.
### DSM Upstart removal retains recovery until automatic activation and the job are absent
diff --cc docs/release-control/v6/internal/subsystems/security-privacy.md
index c114f61a7b,1b78e8953e..f8413e46a7
--- a/docs/release-control/v6/internal/subsystems/security-privacy.md
+++ b/docs/release-control/v6/internal/subsystems/security-privacy.md
@@@ -18,26 -18,13 +18,33 @@@
## Purpose
+### Rejected infrastructure URLs stay out of diagnostics
+
+PVE/PBS constructors validate a host before logging it. URL syntax errors omit
+`url.Parse`'s copy of the supplied input; ordinary validation reasons remain.
+Cluster logs, health snapshots, recovery summaries and aggregate errors use
+display-only labels:
+a valid base URL or `[invalid endpoint]`. Health snapshots preserve each entry
+even when rejected endpoints share that label, and are built only for enabled
+log events. These labels never supply routing,
+alias membership, saved configuration or TLS-pin identity. HTTP/HTTPS defaults,
+base paths, authentication, CA/pin/opt-out choices and guest fences are unchanged.
+
+`TestClientRejectedHostDiagnosticsContainNoCredentials` and
+`TestClusterRejectedEndpointDiagnosticsContainNoCredentials` exercise actual
+constructors, single/multiple endpoint routing and recovery with synthetic
+userinfo/query/fragment and malformed URLs. Accepted-host and
+`TestInfrastructureURLValidationPolicyUnchanged` controls preserve ordinary
+routing and diagnostics. This bounds client diagnostics, not arbitrary provider
+error text, previously saved logs, native trust recovery or an installed service.
+
+ ### Patrol maintenance coverage widens no authority
+
+ Patrol inherits only maintenance from an ancestor window scoped
+ `resource_and_descendants`. Monitoring mode, lifecycle and the
+ `NeverAutoRemediate` lock are never inherited, so descendant scope can quiet
+ findings but cannot unlock or grant automated action on any resource.
+
### Startup provisioning cannot replace retained access
`pkg/server/server.go` admits environment-selected startup import only into an
diff --cc frontend-modern/src/components/Workloads/GuestDrawerOverview.tsx
index 2b9d0a3b3e,af688764de..311fbd050e
--- a/frontend-modern/src/components/Workloads/GuestDrawerOverview.tsx
+++ b/frontend-modern/src/components/Workloads/GuestDrawerOverview.tsx
@@@ -114,12 -142,9 +142,12 @@@ export function GuestDrawerOverview(pro
const overviewSections = () =>
compactDetailSections([
{
- label: 'Operator context',
+ label: 'Summary',
rows: compactDetailRows([
- // OS and primary IP lead the facts strip; they are not repeated here.
+ makeDetailRow('System', props.hasOsInfo ? props.guestOsSummary : null, {
+ // The full OS name/version must be readable without a hover title.
+ wrap: true,
+ }),
makeDetailRow('Pulse coverage', coverageLabel(), {
title: props.hasWorkloadActionAgent
? props.workloadActionAgentTitle
diff --cc frontend-modern/src/components/Workloads/NodeDrawerOverview.tsx
index 8971dce852,57467f8f0c..3b17d149ac
--- a/frontend-modern/src/components/Workloads/NodeDrawerOverview.tsx
+++ b/frontend-modern/src/components/Workloads/NodeDrawerOverview.tsx
@@@ -1,7 -1,12 +1,13 @@@
- import { Show } from 'solid-js';
+ import { For, Show, Suspense, createMemo, lazy } from 'solid-js';
+
+ import { ALERTS_EMPTY_STATE } from '@/utils/alertOverviewPresentation';
import { useRelativeTimeNow } from '@/utils/relativeTimeClock';
+ import {
+ TechnicalDetailsDisclosure,
+ TechnicalDetailsSection,
+ } from '@/components/shared/TechnicalDetailsDisclosure';
+ import { HOST_METRICS_HISTORY_GROUPS } from '@/components/shared/hostMetricsHistoryModel';
+import { HelpIcon } from '@/components/shared/HelpIcon';
- import { TechnicalDetailsSection } from '@/components/shared/TechnicalDetailsDisclosure';
import { DrawerAttentionSection } from '@/components/shared/DrawerAttentionSection';
import {
compactDetailRows,
@@@ -336,63 -389,157 +386,178 @@@ export function NodeDrawerOverview(prop
},
]);
- const overviewSections = () => {
- const primaryTemperature = getCpuTemperature(props.node.temperature);
- const updates = updateEvidence();
- const temperatureClass =
- typeof primaryTemperature === 'number'
- ? getTemperatureTextClass(primaryTemperature, props.temperatureThresholds)
- : '';
- return compactDetailSections([
- {
- label: 'Summary',
- rows: compactDetailRows([
- makeDetailRow('Platform', versionLabel() ? `PVE ${versionLabel()}` : null),
- makeDetailRow(
- 'Pulse coverage',
- linkedAgentId() ? `Agent ${stripAgentPrefix(linkedAgentId())}` : 'PVE API only',
- ),
- updates
- ? makeDetailRow('Updates', updates.value, {
- tone: updates.tone,
- title: updates.title,
- })
- : null,
- typeof primaryTemperature === 'number' &&
- (temperatureClass.includes('yellow') || temperatureClass.includes('red'))
- ? makeDetailRow('Temperature', formatTemperature(primaryTemperature), {
- tone: temperatureClass.includes('red') ? 'danger' : 'warning',
- })
- : null,
- ]),
- },
- ]);
+ const updateAccessGuidance = (
+ <Show when={updateEvidence()?.helpContentId}>
+ <div class="space-y-1 text-left text-[11px] font-normal text-muted">
+ <p class="whitespace-normal wrap-anywhere">
+ Update checks use separate Proxmox access. Other monitoring can still work.
+ </p>
+ <HelpIcon
+ contentId="updates.proxmox.access"
+ triggerLabel="Why update checks are unavailable"
+ size="xs"
+ class="-ml-2"
+ />
+ </div>
+ </Show>
+ );
+
+ // Keep the interactive guidance owned by the drawer, rather than rebuilding
+ // its section and help state whenever node readings or relative ages change.
+ const operatorContextSection: DetailSection = {
- label: 'Operator context',
++ label: 'Summary',
+ get rows() {
+ const primaryTemperature = getCpuTemperature(props.node.temperature);
+ const updates = updateEvidence();
+ const temperatureClass =
+ typeof primaryTemperature === 'number'
+ ? getTemperatureTextClass(primaryTemperature, props.temperatureThresholds)
+ : '';
+ return compactDetailRows([
+ makeDetailRow('Platform', versionLabel() ? `PVE ${versionLabel()}` : null),
+ makeDetailRow(
+ 'Pulse coverage',
+ linkedAgentId() ? `Agent ${stripAgentPrefix(linkedAgentId())}` : 'PVE API only',
+ ),
+ updates
+ ? makeDetailRow('Updates', updates.value, {
+ tone: updates.tone,
+ title: updates.title,
+ wrap: true,
+ })
+ : null,
+ typeof primaryTemperature === 'number' &&
+ (temperatureClass.includes('yellow') || temperatureClass.includes('red'))
+ ? makeDetailRow('Temperature', formatTemperature(primaryTemperature), {
+ tone: temperatureClass.includes('red') ? 'danger' : 'warning',
+ })
+ : null,
+ ]);
+ },
+ get footerContent() {
+ return updateEvidence()?.helpContentId ? updateAccessGuidance : undefined;
+ },
};
+ const overviewSections = () => [operatorContextSection];
+ const exceptionRows = createMemo(() =>
+ collectDrawerExceptionRows([...overviewSections(), ...technicalSections()]),
+ );
+
+ // The table withholds readings from an offline or stale node; the trend
+ // cards do the same instead of presenting the last numbers as live.
+ const liveReadingsWithheld = (): string | null => {
+ const health = (props.node.connectionHealth || '').trim().toLowerCase();
+ if (props.node.status === 'offline') return 'Node is offline. Showing its history only.';
+ if (
+ props.node.status === 'unknown' ||
+ health === 'error' ||
+ health === 'degraded' ||
+ health === 'stale'
+ ) {
+ return 'Proxmox readings for this node are stale. Showing its history only.';
+ }
+ return null;
+ };
+
+ const trendCards = (): DrawerTrendCardConfig[] => {
+ const card = (
+ metric: string,
+ label: string,
+ unit: DrawerTrendCardConfig['unit'],
+ current: number | undefined,
+ detail?: string,
+ deferred?: GuestDrawerHistoryDeferredMetric,
+ ): DrawerTrendCardConfig => {
+ const alert = getDrawerMetricAlert(props.metricAlerts, metric);
+ const withheld = liveReadingsWithheld();
+ return {
+ metric,
+ label,
+ unit,
+ color: hostSeriesColor(metric),
+ current: withheld ? undefined : current,
+ deferred: withheld ? { message: withheld } : deferred,
+ detail: withheld ? undefined : detail,
+ alertSeverity: alert?.severity,
+ alertThreshold: alert?.threshold,
+ };
+ };
+ const memory = props.node.memory;
+ const disk = props.node.disk;
+ // The adapter fills missing usage with zero; a known total is the
+ // evidence that a percentage was measured at all.
+ const memoryValue =
+ memory?.usageUnavailable || !((memory?.total ?? 0) > 0)
+ ? undefined
+ : finitePercent(memory?.usage);
+ // A retained or undated reading is shown as last known, the same rule the
+ // guest cards follow, rather than as a live value.
+ const memoryReading = getMemoryObservationPresentation(memoryValue, memory?.observation);
+ const memoryDeferred: GuestDrawerHistoryDeferredMetric | undefined =
+ memoryReading && memoryReading.state !== 'current'
+ ? {
+ lastKnownValue: memoryReading.state === 'unavailable' ? undefined : memoryValue,
+ ...(memoryReading.state === 'unknown'
+ ? { valueLabel: 'freshness unknown' as const }
+ : {}),
+ message: memoryReading.message,
+ }
+ : undefined;
+ const memoryCurrent = memoryDeferred ? undefined : memoryValue;
+ const diskMeasured = (disk?.total ?? 0) > 0;
+ const temperature = getCpuTemperature(props.node.temperature);
+ return [
+ card(
+ 'cpu',
+ 'CPU',
+ '%',
+ finitePercent(props.node.cpu),
+ loadAverageLabel() !== '-' ? `load ${props.node.loadAverage?.[0]?.toFixed(2)}` : undefined,
+ ),
+ card(
+ 'memory',
+ 'Memory',
+ '%',
+ memoryCurrent,
+ (memoryCurrent ?? memoryDeferred?.lastKnownValue) !== undefined
+ ? `${formatBytes(memory.used ?? 0)} of ${formatBytes(memory.total)}`
+ : undefined,
+ memoryDeferred,
+ ),
+ ...(typeof temperature === 'number'
+ ? [card('temperature', 'CPU temperature', 'C', temperature)]
+ : []),
+ card(
+ 'disk',
+ 'Root disk',
+ '%',
+ diskMeasured ? finitePercent(disk?.usage) : undefined,
+ diskMeasured
+ ? `${formatBytes(disk?.used ?? 0)} of ${formatBytes(disk?.total ?? 0)}`
+ : undefined,
+ ),
+ ];
+ };
+
+ const facts = () => {
+ const model = cleanText(props.node.cpuInfo?.model);
+ const cores = props.node.cpuInfo?.cores;
+ const firstAddress = (props.node.networkInterfaces || [])
+ .flatMap((networkInterface) => networkInterface.addresses || [])
+ .map((address) => cleanText(address))
+ .find(Boolean);
+ return [
+ versionLabel() ? `Proxmox VE ${versionLabel()}` : '',
+ [model, hasPositiveNumber(cores) ? `${cores} logical CPUs` : ''].filter(Boolean).join(' · '),
+ (props.node.memory?.total ?? 0) > 0 ? `${formatBytes(props.node.memory.total)} RAM` : '',
+ firstAddress ?? '',
+ clusterLabel() && clusterLabel() !== 'Standalone' ? `Cluster ${clusterLabel()}` : '',
+ ].filter((fact) => fact.trim().length > 0);
+ };
return (
- <div class="space-y-3">
+ <div class="space-y-3" data-testid="node-drawer-overview">
<DrawerAttentionSection
items={(props.alerts ?? []).map((alert) => ({
id: alert.id,