mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
rcourtman
d2ac0c5112
Removes `GET /api/charts/workloads-summary` and `GET
/api/charts/storage-summary`, their frontend clients
(`ChartsAPI.getWorkloadsSummaryCharts`,
`ChartsAPI.getStorageSummaryTrend` and their types), and the backend
code that existed only for them.
**Why they are dead**
- `getWorkloadsSummaryCharts` arrived with the v6 import and was never
called: `git log -S getWorkloadsSummaryCharts -- frontend-modern/src
':!*test*'` lists only that commit, and no other source file ever
referenced the route.
- `getStorageSummaryTrend` lost its last reader when
`storageSummaryTrendCache.ts` was deleted in b91dc8dd4c (2026-05-26).
**Why the backend routes go too**
- No stable release ever requested either route from the browser. v6.0.0
and later carry no caller, and the storage trend reader shipped only in
v6.0.0-rc.1 to rc.5.
- Neither route is in `docs/API.md`, which lists only `/api/charts` and
`/api/storage-charts` under Metrics & Charts. That page covers common
endpoints, not all of them, so this is supporting evidence rather than
proof. Any `monitoring:read` token could reach these routes, so a
private script may notice; nothing known depends on them.
- pulse-pro, pulse-mobile and pulse-dev-infra never reference them.
pulse-enterprise names `TestSLO_WorkloadsSummaryCharts` only as fixture
data, and `release_latency_gate.py` passes a test that is absent from
the candidate as `removed`.
- They still cost something: a payload cache, an SLO test in the latency
gate and a benchmark for the workloads route, and in mock mode a 24-hour
storage aggregate rebuilt on every sampler tick for a cache nothing
read.
- Requests to either path now get 404.
**Second-order orphans removed:** `buildMockWorkloadMetricHistorySeries`
and its test-only wrapper, `filterMetricPointMap`,
`oldestMetricSeriesTimestamp`, and the summary-only constants.
**Evidence**
- TypeScript reference graph from `src/index.tsx`: zero production
references to the removed methods or types. The live controls
`getInfrastructureSummaryCharts` and `getStorageSummaryCharts` are
found.
- Production build before/after: only the ChartsAPI chunk changes,
losing exactly the two static methods (326 B raw, 49 B gzip). `index.js`
and `index.html` differ only by chunk hashes and SRI values.
- `deadcode ./cmd/pulse` and golangci `unused` (with and without tests)
report nothing newly unreachable.
- Private mock stacks: the removed routes go from 200 to 404, and
`/api/charts/workloads`, `/api/charts/infrastructure` and
`/api/storage-charts` are unchanged. The Proxmox overview in Trends, a
guest History drawer and `/proxmox/storage` make identical chart
requests before and after at 1440 and 390 px, with no console errors.
Neither build requested the removed routes.
**Contracts:** prose that described either route as live now records the
retirement, with a rule under api-contracts item 39.
`TestContract_WorkloadChartMetricBudgetGuardrailsRemainCanonical` now
pins the per-type metric sets the surviving `/api/charts/workloads`
route requests, in place of the summary-only pins.
Pulse documentation
Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.
Start here
- Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
- Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- Releases and update channels: choosing Stable or Preview, beta and RC expectations, and how releases are tested and promoted.
- Configure Pulse — authentication, notifications, discovery, retention, and system settings.
- Deployment models — data locations, lifecycle, and differences between supported deployment paths.
- Troubleshooting and FAQ — common failures, diagnostics, and operator questions.
Localized getting started guides: Deutsch · Español
Platforms and agents
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.
Monitoring and operations
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.
Security, privacy, and access
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.
Development and reference
Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.
Previous versions and migrations
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.