Quick Start (5 minutes)
Get BlackTide up and running in 5 minutes. This guide walks you through creating your first monitor and configuring alerts.
Prerequisites
- A BlackTide account (free tier works fine)
- A service or API endpoint to monitor
Getting Started
Follow these steps to set up your first monitor and start receiving alerts when your services go down.
Create Your First Monitor
Let's start by monitoring a simple HTTP endpoint. This will check if your service is accessible and responding correctly.
- Navigate to Monitors in the sidebar
- Click New Monitor
- Select HTTP Monitor
- Configure your endpoint:
Example Configuration
For this tutorial, you can use a public API like https://api.github.com/statusor your own service endpoint.
{
"name": "My API Health Check",
"url": "https://api.example.com/health",
"method": "GET",
"interval": 60,
"timeout": 30,
"expectedStatus": 200,
"locations": ["US East", "EU West"]
}Configure Alert Channels
Set up where you want to receive notifications when your service goes down.
- Go to Alerts → Alert Channels
- Click New Channel
- Select your preferred channel (Email, Slack, Discord, etc.)
- Enter the required credentials
- Click Test Connection to verify
Email Channel (Quickest)
Email is the fastest to set up - just enter your email address and you're done. You can add more sophisticated channels like Slack or PagerDuty later.
Create an Alert Rule
Alert rules define when you should be notified. Let's create a rule that alerts you when your monitor fails.
- Go to Alerts → Alert Rules
- Click New Rule
- Configure the conditions
- Select your alert channel(s)
- Save the rule
{
"name": "API Down Alert",
"monitorIds": ["<your-monitor-id>"],
"conditions": {
"consecutiveFailures": 3,
"notifyOnRecovery": true,
"latencyThresholdMs": 2000
},
"channels": ["<your-channel-id>"]
}Consecutive Failures
Setting consecutiveFailures: 3 prevents false alarms. Your service must fail 3 checks in a row before an alert is sent.
View Your Dashboard
Return to the Dashboard to see your monitor in action. You'll see:
- Real-time status - Up/down indicator with current state
- Response time chart - Historical latency data
- Recent checks - Log of the last 50 checks with results
- Uptime percentage - 7-day and 30-day uptime metrics
You're All Set!
Your monitor is now running. You'll receive an alert if your service becomes unavailable. First results will appear within a minute.
Testing Your Setup
Want to verify your alerts are working? You can temporarily point your monitor to an invalid URL (like https://invalid-domain-that-does-not-exist.com) and wait for 3 failed checks.
Don't Forget to Revert
Remember to change the URL back to your real endpoint after testing!
Next Steps
Now that you have your first monitor running, explore these advanced features:
Advanced HTTP Monitoring
Custom headers, request bodies, SSL validation, and more
Public Status Pages
Create a branded status page for your users
Slack Integration
Get alerts directly in your Slack channels
Web3 Monitoring
Monitor gas prices, wallets, and smart contracts
Need Help?
If you run into any issues, check out our Troubleshooting Guide or visit the FAQ for common questions.