blocktorch
  • Overview
    • Introduction
    • Install/Setup
    • Quickstart
  • Concepts
    • Data Sources
      • EVM Chains
      • Roll-ups
      • Local forks
        • Setup Hardhat fork
        • Setup managed Hardhat Fork
        • Hardhat forking API
      • Smart Contracts
        • Adding smart contracts
      • Custom Event Data
      • Oracles
      • Account Abstraction modules
        • Navigating the AA Explorer
      • Decentralized Datastorage
      • React Frontends
    • Querying data
    • Telemetry
  • Use cases
    • Searching
      • Logs
        • Log Details
      • Sharing search results
    • Monitoring
      • Building monitors
      • Alerting
    • Tracing
      • Stack traces
      • End-2-End Traces
    • Dashboarding
      • Pre-made dashboards
      • Custom graphs
    • Collaborating
      • Inviting others
      • Sharing data
    • Debugging
      • Step debugger
    • Benchmarking
    • Managing incidents
      • Troubelshooting
      • Post mortem
    • Predicting
  • Ressources
    • Demo videos
    • FAQs
  • Contribute
    • Open Source projects
Powered by GitBook
On this page
  • Alert trigger
  • Alert destination
  • Who receives the alerts
  1. Use cases
  2. Monitoring

Alerting

PreviousBuilding monitorsNextTracing

Last updated 1 year ago

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 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 .

Who receives the alerts

Alerts to sent to all members of your project. That means everyone who 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
you invited to your project
please reach out to us
the target you set when building a monitor