Tenderly Alerting Setup: Smart Contract Monitoring and Alerts

A production contract without monitoring is risky. You learn about issues from Twitter, not from an alert. One DeFi protocol lost $50k due to an unnoticed flash loan attack — after setting up Tenderly Alerting, they receive a Telegram notification within 2 seconds. Our team of 5 Web3 engineers h

Blockchain Development Services

Frequently Asked Questions

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1450
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1308
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    1003
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1269
  • image_logo-advance_0.webp
    B2B Advance company logo design
    719
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    1009

A production contract without monitoring is risky. You learn about issues from Twitter, not from an alert.

One DeFi protocol lost $50k due to an unnoticed flash loan attack — after setting up Tenderly Alerting, they receive a Telegram notification within 2 seconds. Our team of 5 Web3 engineers helps you configure Tenderly Alerting in 1.5 hours on average. We have 5+ years in Web3 and have completed over 20 contract monitoring projects. We guarantee that no anomalous withdrawal or owner change goes unnoticed.

Tenderly solves the key challenge: informing your team about on-chain changes without building your own indexer. The setup cost is $500, which is less than one hour of a DevOps engineer's time. Infrastructure savings compared to a custom indexer can reach 70%. You pay only for configuration — the Tenderly service itself is billed separately, but its cost is offset by the first prevented incident.

How Tenderly simplifies smart contract monitoring

You receive alerts for specific contract events, storage variable changes, transactions above a threshold, calls to specific functions, and failed transactions. No need to write your own indexer. The main trigger types are:

Trigger Example use case Criticality level
Successful Transaction Large withdrawal from vault High
Failed Transaction Errors in production Critical
Event Emitted Transfer above $10k threshold Medium
State Change Owner/admin change Critical
Function Called Call to pause() or emergencyWithdraw() Critical
Balance Change Treasury balance change >1% High

Consider a real-world case: for a vault contract (ERC-4626), we configured alerts on the Withdraw event with amount > $10k, on setAdmin calls, on vault balance changes exceeding 1% per block, and on gas spikes above 200 gwei. As a result, the team learns about risks instantly — for example, an attempted oracle manipulation or unauthorized access. Such a configuration takes no more than 2 hours, including testing.

Tenderly Alerting can be set up 10 times faster than writing a custom indexer on The Graph. For critical events, we use Telegram or PagerDuty with immediate delivery; for informational ones, a Slack channel.

What's included in the setup

  • Adding contracts (ABI + address + network) to Tenderly
  • Configuring triggers according to your business logic: thresholds, functions, events
  • Integrating notification channels: Telegram, Slack, PagerDuty, email, webhook
  • Setting up webhooks for custom processing (auto-pause, database logging)
  • Testing and documentation for your team
  • Recommendations for optimizing alerts and avoiding false positives (we filter out up to 95% of noise)

Setup steps

  1. Add your contract to Tenderly (ABI + address + network)
  2. Go to Alerts → Add Alert → select trigger type
  3. Configure filters (e.g., value > 100000e6 for USDC)
  4. Choose destination: Slack, Telegram, PagerDuty, webhook, email

For critical events (pause, owner change, anomalous withdrawals) — Telegram/PagerDuty with immediate delivery. For informational ones (regular transactions, protocol events) — a Slack channel for the team.

Comparison of notification channels

Channel Latency Reliability Application
Telegram <1 sec High Critical alerts
Slack 1-2 sec Medium Team notifications
PagerDuty <30 sec High Incidents
Webhook Depends on handler Depends on implementation Custom automation

Webhook integration

Tenderly can send a webhook POST request with transaction details. This enables custom logic: auto-pause the contract on anomaly, log to database, send enriched notifications.

{ "id": "alert_id", "contract": "0x...", "network": "1", "transaction": { "hash": "0x...", "from": "0x...", "value": "1000000000000000000" }, "trigger": "successful_transaction" } 

Limitations

Tenderly is a managed service. For full control and data privacy, consider alternatives: a custom indexer on The Graph, Goldsky, or OpenZeppelin Defender Sentinel (more flexible trigger engine). For most projects, Tenderly Alerting offers the best balance of setup speed and functionality. Basic monitoring setup takes 1 business day, including team documentation.

Contact us to discuss your project — we will assess the complexity and propose the optimal solution. Order Tenderly Alerting setup and eliminate the risk of missing a critical event. With 5+ years of Web3 experience and over 20 projects, we ensure reliable monitoring. Get a free consultation on monitoring.