Alert fatigue is a significant issue that affects the job satisfaction and well-being of Site Reliability Engineers (SREs), Operations Engineers, and Developers, particularly those on an on-call rotation. It occurs when teams receive too many non-critical alerts, leading to desensitization and slower response times, ultimately threatening system reliability and eroding team happiness. The prevalence of advanced observability tools has made alert fatigue more widespread, and it can be caused by factors such as repetitive alerts, alerts delivered to mobile devices outside working hours, and cognitive biases that lead to ignoring critical alerts. To combat alert fatigue, synthetic monitoring can be optimized with best practices such as ensuring critical user flows, implementing smart retries, labeling test steps, using visual tools for faster interpretation, embracing Monitoring as Code (MaC), and setting monitoring cadence and alert thresholds based on SLA. By adopting these strategies, teams can reduce the likelihood of alert fatigue and create a more maintainable and scalable monitoring setup.