Monitors Overview
BlackTide supports 12 different monitor types to cover traditional infrastructure and Web3 use cases.
Traditional Monitors
Monitor traditional web services, APIs, databases, and infrastructure:
HTTP Monitor
Monitor HTTP/HTTPS endpoints with custom headers, validation, and SSL checking
TCP Monitor
Check if specific ports are open and accepting connections
ICMP/Ping Monitor
Verify server reachability with ICMP ping requests
TLS/SSL Monitor
Monitor SSL certificate validity and expiration dates
Heartbeat Monitor
Verify cron jobs and scheduled tasks are running on time
Web3 Monitors
Native monitoring for blockchain infrastructure and Web3 applications:
Gas Price Monitor
Track gas prices across 8 EVM chains with high/low alerts
Whale Wallet Monitor
Monitor wallet balances and transaction activity
Contract Events Monitor
Listen to smart contract events and filter by parameters
Liquidation Risk Monitor
Track DeFi position health factors (Aave, Compound)
DeFi Protocol Monitor
Monitor protocol TVL, pool health, and APY/APR
Subgraph Monitor
Monitor The Graph subgraphs for sync status and health
Bridge Monitor
Track cross-chain bridge TVL and transaction correlation
Supported Blockchains
BlackTide supports monitoring across 24+ blockchain networks:
EVM Mainnets (8)
- Ethereum, Polygon, BSC, Arbitrum, Optimism, Base, Avalanche, Fantom
Cosmos SDK Mainnets (10)
- Cosmos Hub, Osmosis, Juno, Stargaze, Akash, Evmos, Injective, Celestia, Neutron, Stride
Non-EVM Mainnets (2)
- Cardano (Blockfrost API), Midnight (Substrate JSON-RPC)
Testnets (4)
- Sepolia, Mumbai, Cardano Preprod, Midnight Testnet
Multi-Chain Support
Monitor Features
Multi-Location Checks
Run checks from 6 global locations for accurate uptime measurement:
- US East, US West, EU West, EU Central, Asia Pacific, South America
Flexible Intervals
Configure check frequency from 30 seconds to 24 hours:
| Interval | Use Case |
|---|---|
| 30-60s | Critical production services |
| 5 min | Standard web services |
| 15-30 min | Non-critical services |
| 1-24 hrs | Daily health checks |
Advanced Validation
- Response validation - Check status codes, body content, JSON schemas
- Latency thresholds - Alert on slow responses before complete failures
- SSL verification - Automatic certificate expiry alerts
- Custom assertions - Define custom validation logic
Creating Your First Monitor
Follow our Quick Start Guide to create your first monitor in 5 minutes.
Best Practices
Monitor Configuration Tips
- Use appropriate intervals - Don't over-monitor; 60s is sufficient for most services
- Enable multi-location - Always check from 2+ locations to avoid false alarms
- Set realistic timeouts - Allow enough time for legitimate slow responses
- Tag your monitors - Use tags like "production", "critical", "web3" for organization
- Monitor dependencies - Monitor third-party APIs your app depends on
Next Steps
- Create an HTTP Monitor - Monitor REST APIs and websites
- Create a Gas Price Monitor - Track blockchain gas prices
- Configure Alert Rules - Get notified when monitors fail