Synthetic Monitoring and E2E Testing: 2 Sides of the Same Coin
summary
Argues that the same code artifact can serve as both synthetic monitor and CI end-to-end test, and demonstrates a working pipeline that uses Playwright tests, GitHub Actions for gating and pushes, and Elastic Synthetics to run scheduled monitors in production. Shows a concrete login journey converted to a monitor, pushes monitors via API keys, captures per-step durations and screenshots, surfaces core web‑vitals, and triggers alerts when failures or slow steps occur.
AI-written summary · about
chapters (9)
- 0:00Introduction and motivation
- 1:07Professional background
- 4:04Challenges in software delivery
- 7:39Bridging tools and strategies
- 11:22Technical implementation
- 16:29Automating test journeys
- 20:42CI/CD integration
- 23:21Observability and alerting
- 25:26Conclusion and Q&A
related talks
32mSynthetic Monitoring and E2E Testing: 2 Sides of the Same Coin
26mSynthetic Monitoring and E2E Testing: 2 Sides of the Same Coin
40mMonitoring as Code: E2E Testing in Production with Playwright
44mUnleash Synthetic Monitoring with Supercharged Test Automations
40mDecoding Synthetic Monitoring: A Journey from E2E UI Tests to Service-Level Probes
44mSynthesizing Sanity with, and in Spite of, Synthetic Monitoring
23mSecure by Design: Rethinking Test Credentials for Synthetic Monitoring
43mDecoding Synthetic Monitoring: A Journey from E2E UI Tests to Service-Level Probes