From 0255d960351a1e55c7fd2f881198e70cbaddc7f8 Mon Sep 17 00:00:00 2001 From: Chris Grindstaff Date: Wed, 18 Oct 2023 07:47:50 -0400 Subject: [PATCH] doc: fix typo in ems docs --- docs/configure-ems.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/configure-ems.md b/docs/configure-ems.md index 04d524edb..d63e5e28f 100644 --- a/docs/configure-ems.md +++ b/docs/configure-ems.md @@ -27,12 +27,12 @@ with `ems_events`. Harvest supports two types of ONTAP EMS events: -1. **Normal EMS events** +- **Normal EMS events** Single shot events. When ONTAP detects a problem, an event is raised. When the issue is addressed, ONTAP does **not** raise another event reflecting that the problem was resolved. -2. **Bookend EMS events** +- **Bookend EMS events** ONTAP creates bookend events in matching pairs. ONTAP creates an event when an issue is detected and another paired event when the event is resolved. @@ -112,7 +112,7 @@ The EMS event template parameters are explained below along with an example for - `resolve_after` (optional, Go duration, default = 28 days) resolve the issuing EMS after the specified duration has elapsed (`672h` = `28d`). If the bookend pair is not received within the `resolve_after` duration, the Issuing EMS event expires. When that - happens, Harvest will mark the event as auto resolved by adding the `autoresolve=true` label to the Issuing EMS event. + happens, Harvest will mark the event as auto resolved by adding the `autoresolved=true` label to the issuing EMS event. - `resolve_key` (optional) bookend key used to match bookend EMS events. Defaults to prefixed (`^^`) labels in `exports` section. `resolve_key` allows you to override what is defined in the `exports` section.