From 57683d7a94e7a191d1b9e5ae926ff78f6fa29cc6 Mon Sep 17 00:00:00 2001 From: sangupta01 Date: Tue, 21 Mar 2017 09:26:12 -0700 Subject: [PATCH] Update alarms-history.md Fixed typo in #3. It should be contrail-stats. --- specs/alarms-history.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specs/alarms-history.md b/specs/alarms-history.md index c8720988c76..42af9184b27 100644 --- a/specs/alarms-history.md +++ b/specs/alarms-history.md @@ -6,7 +6,7 @@ Contrail solution sends alarms and UVEs for monitoring and analytics. This provi If an alarm gets created and then it is reset after mitigation steps, the system is back to original good state. But the history of alarm triggers/reset over time is lost. Same issue with UVEs. #3. Proposed solution -During alarm and UVE processing, increment set/reset or add/update/remove counters and save it in database. Later this database can be queried using contrail-status script. +During alarm and UVE processing, increment set/reset or add/update/remove counters and save it in database. Later this database can be queried using contrail-stats script. ##3.1 Alternatives considered None