mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-07-10 00:14:38 +00:00
6bb147c1bb
The alert engine fired powered-off alerts for every stopped VM and container regardless of whether the guest was configured to autostart. This meant intentionally-stopped guests (onboot=0) generated alarm fatigue — in the live lab, 7 of 12 alerts were noise from stopped VMs that are deliberately off. Now the alert engine checks the Proxmox onboot setting before firing: - onboot=true → stopped is unexpected, alert (preserved behavior) - onboot=false → stopped is expected, suppress - onboot=nil → unknown, alert (preserved behavior) For containers, onboot is parsed from the already-fetched container config in enrichContainerMetadata (no new API call). For VMs, the config is fetched only for stopped VMs via GetVMConfig (one extra call per stopped VM, running VMs are unaffected). Models: add OnBoot *bool to VM and Container. Alerts: add onboot-aware suppression branch in CheckGuest. Monitoring: add parseProxmoxOnBoot helper and fetchVMOnBoot. |
||
|---|---|---|
| .. | ||
| account_roles.go | ||
| ceph_cluster_identity.go | ||
| ceph_pool_storage_test.go | ||
| concurrency_test.go | ||
| converters.go | ||
| converters_additional_test.go | ||
| converters_test.go | ||
| deepcopy.go | ||
| deepcopy_test.go | ||
| disk_summary.go | ||
| disk_summary_test.go | ||
| metrics_types.go | ||
| metrics_types_test.go | ||
| models.go | ||
| models_frontend.go | ||
| models_frontend_test.go | ||
| models_helpers_test.go | ||
| node_aliases_test.go | ||
| organization.go | ||
| organization_additional_test.go | ||
| profile_validation.go | ||
| profile_validation_additional_test.go | ||
| profile_validation_test.go | ||
| profiles.go | ||
| snapshot_provider.go | ||
| state_additional_test.go | ||
| state_docker_test.go | ||
| state_host_test.go | ||
| state_snapshot.go | ||
| state_snapshot_additional_test.go | ||
| state_snapshot_concurrency_test.go | ||
| state_snapshot_frontend_test.go | ||
| state_snapshot_merge_test.go | ||