Nothing is more frustrating than being woken up at 3am for a false alert. The site was perfectly functional, but a network problem between the monitoring point and your server triggered an alert. Double verification solves this problem by confirming incidents from multiple locations before alerting.
When MoniTao detects an anomaly, it doesn't immediately trigger the alert. It launches a verification from another geographic location. If both verifications confirm the problem, the alert is legitimate. Otherwise, it was probably a local routing issue.
This feature drastically reduces false positives while maintaining quick detection of real incidents. You maintain confidence in your alerts: when a notification arrives, you know the problem is real.
How Double Verification Works
The double verification process works as follows:
- Primary verification: MoniTao performs the check from the configured primary location. If the check succeeds, all is well. If the check fails, we move to the next step.
- Secondary verification: Immediately after primary failure, MoniTao launches a verification from another location. This second location is geographically distinct.
- Confirmation: If both verifications fail, the problem is confirmed and the alert is triggered. If only the first fails, it's probably a local routing issue.
- Escalation: Once the problem is confirmed, notifications are sent according to your criticality and escalation rules.
Why Double Verification is Essential
False positives have real consequences:
- Alert fatigue: After a few false alerts at 3am, the team starts ignoring notifications. A real incident will be handled too late.
- Loss of trust: If alerts are often false, monitoring loses credibility. The team considers it a noisy tool rather than an ally.
- Cost of interruptions: Each false alert interrupts work or sleep. This cost accumulates and impacts productivity and morale.
- Lost diagnostic time: Investigating a false positive takes time. Time that could have been spent on improvements or real problems.
Configuration in MoniTao
Enable double verification in a few clicks:
- Access monitor settings: Open the configuration of the monitor you want to protect against false positives.
- Enable confirmation: In advanced options, enable "Confirm from multiple locations before alerting".
- Choose locations: Select verification locations. Ideally, choose geographically distant locations.
- Configure delay: Define the delay between primary and secondary verification. A short delay (5-10 seconds) is usually sufficient.
- Test: Force a temporary failure (firewall, maintenance) to verify double verification works correctly.
Verification Locations
MoniTao verifies from multiple geographic points:
- Europe (Paris, Frankfurt): Western and Central Europe coverage. Low latency to European hosts.
- North America (New York, San Francisco): East and West coast coverage. Verifies accessibility from the United States.
- Asia-Pacific (Singapore, Tokyo): Asia and Oceania coverage. Detects peering issues to these regions.
- Network diversity: Each location uses a different network provider, eliminating carrier-specific routing issues.
Configuration Options
Customize double verification to your needs:
- Number of confirmations: By default, 2 verifications (primary + secondary). For ultra-critical services, configure 3 verifications.
- Confirmation delay: Time between verifications. Short (5s) for quick confirmation, longer (30s) if your service has fluctuations.
- Preferred locations: Define which locations to use. Choose those where your main users are located.
- Bypass mode: For ultra-critical P1 monitors, you can disable double verification to alert on first failure.
Best Practices
Maximize double verification effectiveness:
- Distant locations: Choose locations on different continents. Paris + Frankfurt doesn't bring as much as Paris + New York.
- Adapted delay: If your service has normal micro-outages (deployments), increase the delay. Otherwise, keep it short.
- Analyze near-alerts: MoniTao logs failed primary verifications that weren't confirmed. Analyze them to detect routing issues.
- Variable criticality: P1 monitors can bypass double verification to alert immediately. P3-P4 can have triple verification.
Double Verification Checklist
- Enable double verification on all monitors
- Choose geographically distant locations
- Configure appropriate confirmation delay
- Test configuration with simulated failure
- Analyze verification logs to optimize
Frequently Asked Questions
Does double verification slow down alerts?
Slightly. With a 5-second delay, the alert arrives 5-10 seconds later. An acceptable tradeoff to eliminate 90% of false positives.
What if both locations have network issues?
This is extremely rare with locations on different continents and carriers. If it happens, it's probably a real problem on the server or DNS side.
Can I disable double verification for certain monitors?
Yes, each monitor has its own settings. P1 monitors can alert on first failure to maximize speed.
How many locations does MoniTao use?
MoniTao has monitoring points on multiple continents. The exact number and locations are visible in monitor settings.
Does double verification work for SSL and DNS checks?
Yes, all monitor types support double verification: HTTP, SSL, DNS, TCP, heartbeat.
How to see filtered verifications?
In monitor history, failed primary verifications that weren't confirmed are marked. You can analyze these "near-alerts".
Conclusion
Double verification is your shield against false positives. By confirming problems from multiple locations before alerting, you maintain confidence in your monitoring system.
Enable this feature on all your MoniTao monitors. Your nights will be quieter, and when an alert arrives, you'll know it deserves your attention.
Ready to Sleep Soundly?
Start free, no credit card required.