🔭
Monitors
Monitors allow you to track specific metrics and calculate SLOs to never miss important events that need attention and run analysis to take data driven decisions
SLO, or Service Level Objective, is a key concept in the realm of observability, which is the practice of monitoring, understanding, and optimizing the performance and reliability of software systems. To break it down, let's define each term separately:
- Service: A software application or system that delivers functionality to users or other systems.
- Level: A measure of quality or performance.
- Objective: A specific, measurable target that a service aims to achieve.
In the context of observability, SLOs are typically expressed as a percentage or a ratio, representing the desired level of performance over a given time period. These targets are usually defined in terms of key performance indicators (KPIs), such as response time, error rate, or availability. By monitoring these KPIs, teams can assess whether the service is meeting its objectives or if there is a need for improvement.
To build monitors, you can leverage blocktorch's powerful query engine, which allows you to query various types of data, such as chains, blocks, transactions, and gas fees. All available faucets are listed here. By using blocktorch's query chips you can create complex queries and filters to focus on the desired aspects of your data, enabling you to build accurate and relevant monitors.
To build a new monitor navigate to the "monitor" overview page in the blocktorch app and click the "+ Add Monitor" button in the top right or navigate to the "explore" page and start building your query right away
Building monitors
- Choose one or multiple smart contracts you want to monitor with the query.
- Choose the metric to monitor
- Optionally set one or multiple conditional filters
- All query faucets can be combined and mixed as you wish. The full list of available faucets and operators can be found here.
- To finish the query choose to get the SUM, the COUNT, the AVERAGE, the MAXIMUM or MINIMUM of your metric.
want to build monitors across smart contracts and also across different blockchains? Please reach out.
Time windows for the monitors to check the query on
Example #1: not more than 2% of transactions should revert (=> 98% success rate of transactions)
Example #2: Monitoring that the gas used by a certain contract does not succeed a treshold
The title will display in the monitor chart as soon as you saved the monitor
Last modified 28d ago