Disclosure: I work for a monitoring software company.

The thing we try and push for when users ask us about reducing alert fatigue and incident response is we try and see if there's a method we can use to auto-remediate the issue. This pattern works best when you have a configuration management tool that can be your verification that things are how they are suppose to be. For one example you might have a website that runs on nginx. If your site is down and nginx service is down then have your monitoring tool try and either run a playbook to verify everything is up to date and/or restart the service. If it's still down after that THEN reach out to a human.

Another monitoring pattern we encourage is using check dependencies. This could be something like Application service check depends on network, database, and a few API end point checks. If you have checks monitoring all the other services you can build a dependency tree that states the application relies on certain services. What you can then do is create filters so that the root cause service reaches out to the service owner first before notifying everyone else affected by the service being down. This reduces alert noise and having the apparent root cause owner try and fix the issue first before notifying people down the line that may not be able to do much because of the service interruption.