# Alerting Alerting and notification are vital components of blocktorch's observability platform, helping teams to react promptly to potential issues. By setting the right thresholds for alerts and ensuring they are delivered through preferred channels to the relevant stakeholders, you can significantly reduce the Mean Time to Recovery (MTTR). This not only helps in minimizing downtime but also safeguards the customer experience and maintains operational efficiency. The key is to strike a balance between alert sensitivity and notification fatigue to ensure that every alert prompts a timely and effective response. ### Alert trigger The alert trigger is [the target you set when building a monitor](https://docs.blocktorch.xyz/use-cases/monitoring/pages/Twhl5L8vDcNCiEsYqKoM#id-3.-setting-the-monitor-target) The alert is getting triggered every time the target is hit ### Alert destination Alerts are currently set via email. In case you would like to receive alerts via Slack, Discord, Telegram, PagerDuty or on-chain via Push Protocol [please reach out to us](mailto:contact@blocktorch.xyz). ### Who receives the alerts Alerts to sent to all members of your project. That means everyone who [you invited to your project](/use-cases/collaborating/inviting-others.md) and has accept this invite will receive all alerts as well. In case you would like to have triaging of alerts based on e.g. role or creator of the alert [please reach out to us](mailto:contact@blocktorch.xyz). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.blocktorch.xyz/use-cases/monitoring/alerting.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.