What should you do to manually reset baseline if a high-volume request causes alerts?

What should you do to manually reset baseline if a high-volume request causes alerts?

• A. Mute the request permanently
• B. Establish new performance baselines
• C. Remove the service from monitoring
• D. Delay the alerts further

Answer: (B)

Establishing new performance baselines is crucial after experiencing a high-volume request that has triggered alerts. Baselines serve as reference points for normal performance metrics, and when traffic or behavior changes significantly, the existing baselines may no longer reflect normal operating conditions. By setting new baselines, you can effectively recalibrate the monitoring system to accommodate the new performance data. This ensures that alerts are relevant to the current performance expectations and reduces the likelihood of false alarms caused by temporary spikes or changes in usage patterns. In this context, simply muting the request permanently would not address the underlying issue of performance evaluation, nor would it provide a solution for future incidents. Removing the service from monitoring is an extreme measure that eliminates visibility into potential problems and is typically not advisable. Delaying alerts further may postpone the notification of actual issues, potentially leading to unresolved performance problems in the application or service. Establishing new baselines represents a proactive approach to maintaining effective monitoring and ensuring that your alerting mechanisms reflect the current operational environment.

Establishing new performance baselines is crucial after experiencing a high-volume request that has triggered alerts. Baselines serve as reference points for normal performance metrics, and when traffic or behavior changes significantly, the existing baselines may no longer reflect normal operating conditions. By setting new baselines, you can effectively recalibrate the monitoring system to accommodate the new performance data. This ensures that alerts are relevant to the current performance expectations and reduces the likelihood of false alarms caused by temporary spikes or changes in usage patterns.

In this context, simply muting the request permanently would not address the underlying issue of performance evaluation, nor would it provide a solution for future incidents. Removing the service from monitoring is an extreme measure that eliminates visibility into potential problems and is typically not advisable. Delaying alerts further may postpone the notification of actual issues, potentially leading to unresolved performance problems in the application or service. Establishing new baselines represents a proactive approach to maintaining effective monitoring and ensuring that your alerting mechanisms reflect the current operational environment.