feature: threshold rule form: hysteresis and sustained breach fields #48
No reviewers
Labels
No labels
breaking
bug
ci
dependencies
documentation
feature
security
skip-changelog
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
argus/frontend!48
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/threshold-hysteresis"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #46
Needs argus/backend#56 (
recover/for_countparams) deployed first -- without it the backend's param cleaner silently drops both fields.EventRulesManager: two optional fields on metric-threshold rules, "Seuil de retour à ok" →recover, "Rapports consécutifs avant de changer de niveau" →for_count(1-100); both appear in the rule summary line when set ("retour 85", "2 rapports de suite").ReportCard(custom reports): a metric carryingpendinggets a "dépassement en cours (n/N)" chip in the pending level's colour.Tests: new cases in
RuleTriggers.spec.tsandReportCard.spec.ts; vitest (132), vue-tsc and build pass locally.🤖 Generated with Claude Code
https://claude.ai/code/session_01AUcAVt7dKqdZsFwQdwZkxW
📊 Rapports Argus pour cette PR