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
Distinguish agent identity from connection names in triage
pulse-triage[bot]91b9bb69e47d
diff --git a/docs/ISSUE_TRIAGE.md b/docs/ISSUE_TRIAGE.mdindex 049c9f4362..8b2164f5ea 100644--- a/docs/ISSUE_TRIAGE.md+++ b/docs/ISSUE_TRIAGE.md@@ -75,6 +75,18 @@ context. Existing reports need no refile. Retain every affected surface (forexample, node errors, backup status and Docker monitoring); recovery in one doesnot establish recovery in the others.+Keep the connection Host/URL, Pulse display name, native node/guest name and+agent-reported hostname separate. A full connection hostname does not establish+that guest or agent names are fully qualified. If the supplied evidence leaves+that distinction consequential, ask only for the remembered short/full form+and whether full domain suffixes differ, not the literal names; unknown is valid.+Retain which guest has an agent and whether it remained connected when its+Docker inventory disappeared. Only one guest having an agent does not make a+shared guest name unique across the platform inventory. An ambiguous automatic+link is not proof that agent reporting stopped. Do not install another agent,+change a link or recreate the addition just to diagnose it; a repair for distinct+full hostnames alone does not establish a fix for repeated short names.+Missing readings and an unresponsive workload need different investigation andrecovery paths. Use the reporter's existing observations of the workload's usualUI, not Pulse's displayed connection status, to distinguish them where possible.diff --git a/frontend-modern/public/docs/ISSUE_TRIAGE.md b/frontend-modern/public/docs/ISSUE_TRIAGE.mdindex 049c9f4362..8b2164f5ea 100644--- a/frontend-modern/public/docs/ISSUE_TRIAGE.md+++ b/frontend-modern/public/docs/ISSUE_TRIAGE.md@@ -75,6 +75,18 @@ context. Existing reports need no refile. Retain every affected surface (forexample, node errors, backup status and Docker monitoring); recovery in one doesnot establish recovery in the others.+Keep the connection Host/URL, Pulse display name, native node/guest name and+agent-reported hostname separate. A full connection hostname does not establish+that guest or agent names are fully qualified. If the supplied evidence leaves+that distinction consequential, ask only for the remembered short/full form+and whether full domain suffixes differ, not the literal names; unknown is valid.+Retain which guest has an agent and whether it remained connected when its+Docker inventory disappeared. Only one guest having an agent does not make a+shared guest name unique across the platform inventory. An ambiguous automatic+link is not proof that agent reporting stopped. Do not install another agent,+change a link or recreate the addition just to diagnose it; a repair for distinct+full hostnames alone does not establish a fix for repeated short names.+Missing readings and an unresponsive workload need different investigation andrecovery paths. Use the reporter's existing observations of the workload's usualUI, not Pulse's displayed connection status, to distinguish them where possible.diff --git a/scripts/release_control/release_promotion_policy_test.py b/scripts/release_control/release_promotion_policy_test.pyindex c5335f2e9e..2afec0233c 100644--- a/scripts/release_control/release_promotion_policy_test.py+++ b/scripts/release_control/release_promotion_policy_test.py@@ -2014,6 +2014,17 @@ class ReleasePromotionPolicyTest(unittest.TestCase):"add, rename, remove or re-enrol anything", "Existing reports need no refile","node errors, backup status and Docker monitoring","recovery in one does not establish recovery in the others",+ "connection Host/URL, Pulse display name, native node/guest name",+ "agent-reported hostname separate",+ "full connection hostname does not establish",+ "guest or agent names are fully qualified",+ "ask only for the remembered short/full form",+ "whether full domain suffixes differ, not the literal names",+ "which guest has an agent", "whether it remained connected",+ "shared guest name unique across the platform inventory",+ "link is not proof that agent reporting stopped",+ "Do not install another agent, change a link or recreate the addition",+ "does not establish a fix for repeated short names",):self.assertIn(distinction, prose)