Alerts
Tenderly Alerting listens for events on the blockchain and sends real-time notifications to your desired destination when the event occurs. This can be email, your favorite messaging app, an incident monitoring system, or webhooks and Web3 Actions.
With Tenderly Alerting, you can stay informed about desired or undesired events related to transitions, wallets, smart contracts, or any other activity on the network. This enables you to identify and resolve smart contract transaction issues faster. Alerts can also aid in the early detection of operational, code, or security issues.
With Alerts API, you can create complex triggering conditions.
Follow these quick links to skip ahead and get started with Tenderly Alerting:
- Quickstart guide
- How to set up webhooks for alerting
- Using Alerting API.
- Alert triggers and targets
- Alert destinations
Anatomy of an Alert
Each Alert requires three elements to be configured before it can be enabled:
- Alert Type: On-chain event that triggers Tenderly to send you a notification. There are 12 alert trigger types to choose from.
- Alert Target: Addresses you want Tenderly to monitor, as well as other settings such as the network, project, and tags.
- Alert Destination: Service for receiving notifications about a specific event. One Alert can send notifications to multiple destinations. There are 8 destination types where you can send and receive notifications.
Alert trigger types overview
Below is a list of all the Alert Types and a brief example of a common use case. Click the link to explore each trigger type in more detail.
| Trigger type | Explanation |
|---|---|
| Successful Transaction | Notifies you when a successful transaction happens. This is useful when you want to observe transactions from a wallet, dapp, or smart contract getting added to the blockchain. |
| Failed Transaction | Send a notification when a transition fails, allowing you to keep track of all the unsuccessful transitions and detect issues, as well as catch malfunctions with your dapp or smart contract early. |
| Function Call | Fires when a specific function is called from a contract, which is useful for monitoring the execution of smart contracts for potential issues. |
| Event Emitted | Triggers when a specific event is emitted from a contract. For example, this trigger can be used to monitor every time a spender is approved to transfer tokens on behalf of the owner. |
| Event Parameter | Alerts you when an event parameter has a particular value. You can use this Alert trigger to monitor when a particular address is approved to transfer tokens on behalf of the owner. |
| ERC20 Token Transfer | Triggers when an ERC20 transfer event is emitted from a contract, allowing you to track when you or someone moves tokens. This can be useful for monitoring suspicious wallets during or after an exploit. |
| Allowlisted Callers | Notifies you when an address that is not on this list calls your smart contract. This Alert can be used for monitoring if an address outside the “allowed” list attempts to call a function that’s reserved only for specific addresses. |
| Blocklisted Callers | Notifies you whenever an address from this list calls your contracts. |
| Balance Change | Triggers when the network's native currency balance of an address matches conditions. If you are a member of a DAO that is governed by a smart contract, you can set up this alert to notify you when the DAO's balance falls below a certain threshold. |
| Transaction Value | Notifies you when a transaction value matches set conditions. This alert is useful in situations when a transaction with more than a certain amount of ETH calls a contract. |
| State Change | Fires when a state variable in a contract changes. This alert is ideal for monitoring when the number of required confirmations for a multisig wallet goes below a certain number. |
| View Function | Alerts you when a view function's return value matches certain criteria, passes a threshold, or changes by a certain percentage. For instance, this Alert can be used if you want to check the ERC20 balance threshold. |
Alert Destinations overview
All these alert triggers can be configured to send real-time notifications to a place where it’s convenient for your team.
Receive notifications in your favorite messaging app:
Send alert data to other Tenderly systems:
Send alert data to third-party incident and error monitoring platforms like:
Learn how to set up each Alert Destination here.
What can you do with Tenderly Alerting?
Tenderly Alerting offers value in a variety of circumstances. Whenever you require a dependable alerting system for on-chain activities that can notify you of potential risks or threats, you can rely on Tenderly Alerting.
- Monitor on-chain activity: Alerts can be used as a monitoring tool to track user activity on smart contracts, such as failed or successful transactions or state changes. This is useful in scenarios when you need to keep track of specific events or changes in the blockchain environment.
- Detect suspicious behavior: Alerts can inform you about suspicious behavior on your smart contracts or wallets, such as security breaches or fraudulent activity. This helps you to take appropriate action to protect your assets and prevent losses.
- Respond faster in emergency situations: Alerts also help you detect errors, security issues, or failed transactions. This is useful in situations when you need to take action to resolve a problem immediately after it happens.
- Ensure greater visibility for your team: You can configure each Alert to your specifications, including setting the location for notifications convenient for your team.
- Enable automated processes: Use Alerts as triggers for Web3 Actions to build custom automated processes that allow you to react automatically to on-chain events with custom code.