Decoding Synthetic Monitoring: A Journey from E2E UI Tests to Service-Level Probes
summary
Team replaces flaky, minutes‑long E2E UI checks (30s to minutes, flaking maybe once every 100 runs) with API‑level probes built from Bruno or Postman collections that run in ~3 seconds every 30 minutes. Probes emit success/failure and per‑step latency via the multi-target exporter pattern into Honeycom and OpenTelemetry, enabling faster root cause work (traced exceptions in PDF generator), more reliable alerts (majority or repeated failures) and far lower monitoring noise.
AI-written summary · about
chapters (12)
- 0:00Synthetic monitoring journey
- 3:01Low-traffic system monitoring
- 7:00What is synthetic monitoring
- 12:19UI tests drawbacks
- 17:15Prometheus probes intro
- 24:19Bruno probes from APIs
- 26:05Live probe setup demo
- 31:44Probe data in Honeycomb
- 33:08Probe and backend correlation
- 35:55Unified observability benefits
- 38:46New approach advantages
- 40:00Q&A
related talks
43mDecoding Synthetic Monitoring: A Journey from E2E UI Tests to Service-Level Probes
30mSynthetic Monitoring and E2E Testing: 2 Sides of the Same Coin
32mSynthetic Monitoring and E2E Testing: 2 Sides of the Same Coin
44mUnleash Synthetic Monitoring with Supercharged Test Automations
16mMonitoring your platform from multiple locations
34mReliability Monitoring: Tips and Tools
44mSynthesizing Sanity with, and in Spite of, Synthetic Monitoring
24mBeyond Regression Testing: Observability for QA