Version: 1.0 | Last Updated: 30/09/2024 ## Overview - **Feature Name:** Discard - **Audience:** End-User, Administrators, Support team - **Prerequisites:**  Basic understanding of MoovingON AI, User in MoovingON AI --- ## Table of Contents 1. [[#Introduction]] 2. [[#Getting Started]] 3. [[#Configuration/Setup]] 4. [[#Best Practices]] 5. [[#Troubleshooting]] 6. [[#FAQs]] 7. [[#Related Links]] --- ## Introduction - **What is this feature?** The Discard feature allows users to remove specific events from the user interface after a customer requests to ignore a particular instance/service, or any similar item. This ensures that only relevant alerts remain visible, helping streamline operations by reducing alert overload. - **Why is it useful?** - **Reduces Alert Fatigue:** By removing non-essential alerts, users can focus on critical issues without being overwhelmed by unnecessary notifications. - **Customizable Control:** It allows end users to customize the alert system to their specific needs, improving efficiency and reducing distractions. --- ## Getting Started - **Initial Setup:** **** **By clicking on a event, then Create Noteboard** **** **Choose the Discard option** **** **Here you’ll be prompted with the host and service from the event you clicked on, you can add the reason for the discard in the Description field** **** **Setting an automatic timer for when the this event can be monitored back** --- ## Configuration/Setup - **Detailed Configuration Steps:** Sometimes you are prompted with a request to ignore every event coming from a specific Host/region/service, you are able to do that by adding a wildcard “ % “ to the start and end of the expression, for example **** You can see the area highlighted in <font style="color:red">red</font> is between two wildcards, means that the discard searches for the content in that expression And the <font style="color:blue">blue</font> highlighted area can be deleted, because the customer informed us that they are doing maintenance on Investigation on the EU region. And when putting an empty wildcards ( double %) so everything in Host/Service is selected **** this button tests the expression and returns the corresponding events that match the specified expressions, ensuring the correct selection before applying any further actions. --- ## Best Practices - **Known Issues:** 1. **Filtering Out False Positives:** In cases where an alert is mistakenly triggered by a false positive (e.g., a sensor glitch or temporary network blip), users can discard that specific instance to prevent unnecessary follow-up or investigation. 2. **Suppressing Repetitive Alerts:** If a known issue is generating repetitive alerts that have already been addressed or logged, the Discard feature can remove them from view to avoid clutter and ensure the team only sees new or unresolved issues. 3. **Ignoring Alerts for Deprecated Services:** If a service or instance is no longer in use, the Discard feature can be employed to ignore any future alerts related to that service, ensuring that obsolete instances don’t clutter the interface. 4. In case of a whole group of alerts, we have to configure the "Host" and "Service" accordingly - **Avoiding Common Pitfalls:** 1. The attention feature configuring includes the discard feature as well; we have to make sure we're not discarding the alert 2. Not to include a whole group if alerts are not relevant to the attention --- ## Troubleshooting ## FAQs - **Q:** The discarded alerts are still in the dashboard or the discard has been added as attention **A:** 1. Go to the Noteboard section and make sure the discard has the appropriate details of the alert 2. Make sure it's on the discard option and not the Attention option - **Q:** Alerts that are not supposed to be done discarded are not received **A:** 1. Go to the Noteboard section and make sure the discard has the appropriate details of the alert 2. The whole group of Hosts/Services may have been discarded rather than specific alert - **Q:** Receiving alerts again which are supposed to be were discarded or need to extend discard that ended **A:** 1. The attention end time may have passed 2. Go to the Noteboard>Archive section and extend the end time till the relevant team --- ## Related Links - **Internal Links:** [[05.01 Attention]]