mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-07-09 16:00:59 +00:00
9923e4b04f
The public demo wrote ~110K resource_changes rows/day (restart 60K/day, state_transition 45K/day), making the Changes timeline unreadable and keeping unified_resources.db churning. Four generator-level engines, all verified with before/after soaks against scratch mock backends: - Per-tick flap probabilities ran 43,200x/day on the 2s update loop (docker restart p=0.01/tick alone is ~430 restarts/day/container). Churn rates are now expressed as events per day per entity and converted per tick against the configured interval, tuned to a few fleet-wide events per day with dwell times long enough to see. - The pod scheduling reconciler fought the per-tick scenario re-pin and fabricated a fresh random StartTime on every recovery; derived uptime moved backwards, which change emission records as a restart. The reconciler is now idempotent: stable per-pod park/reschedule choices, StartTime never regenerated, and only pods it parked itself (NodeNotReady/ClusterOffline/NodeLost) get recovered, so curated Pending and ImagePullBackOff stories stay put. - Swarm cluster objects were fabricated per host under one shared cluster key, so registry dedupe alternated between the divergent candidates every poll (service renames, status flips, node re-parenting). One leader manager now reports services, tasks, secrets, configs and the node inventory, like a real control plane. - Demo docker host profiles cycled 2 hostnames across 4 online hosts, collapsing canonical identities, and scripted-offline hosts had their sighting refreshed right at the 2 minute staleness threshold, sawtoothing them online/offline. Four distinct host profiles now exist and offline hosts keep a stably stale sighting. Before/after soak with a live client: pre-fix ~110-160 rows/min sustained (restart ~45/min, matching the droplet's 60K/day); post-fix zero rows/min at steady state with the curated degraded stories (CrashLoop payments-worker, ImagePullBackOff, offline hosts) intact. |
||
|---|---|---|
| .. | ||
| alert_history.go | ||
| availability_fixtures.go | ||
| canonical_api_guardrails_test.go | ||
| config_validation.go | ||
| config_validation_test.go | ||
| demo_scenarios.go | ||
| demo_scenarios_test.go | ||
| discovery_fixtures.go | ||
| discovery_fixtures_test.go | ||
| env_dev.go | ||
| env_release.go | ||
| fixture_graph.go | ||
| generator.go | ||
| generator_helpers_coverage_test.go | ||
| generator_test.go | ||
| integration.go | ||
| integration_additional_test.go | ||
| integration_concurrency_test.go | ||
| integration_coverage_test.go | ||
| integration_release_test.go | ||
| integration_security_test.go | ||
| integration_shutdown_test.go | ||
| integration_test.go | ||
| metric_personas.go | ||
| metric_runtime.go | ||
| platform_fixtures.go | ||
| platform_fixtures_test.go | ||
| platform_support_contract_test.go | ||
| recovery_points.go | ||
| recovery_points_test.go | ||
| testhelpers_test.go | ||
| truenas_metrics_identity.go | ||