Monitor with Synthetic Probes from Multiple Regions
Run a synthetic check every minute from three regions so a regional outage is detected before users report it.
Task
Instrument synthetics: { regions: ['us-east', 'eu-west', 'ap-south'], interval: 60s, steps: [...] } so on-call engineers can diagnose an incident without guessing at log lines.
When to use this
An outage lasts 47 minutes because the team cannot correlate synthetics: { regions: ['us-east', 'eu-west', 'ap-south'], interval: 60s, steps: [...] } across services without structured traces.
Prerequisites
- An application with structured logging available
- A metrics or tracing backend configured
Steps
1. Configure synthetics: { regions: ['us-east', 'eu-west', 'ap-south'], interval: 60s, steps: [...] } in the project configuration file with the recommended defaults.
synthetics: { regions: ['us-east', 'eu-west', 'ap-south'], interval: 60s, steps: [...] }
Expected output: The configuration is accepted and synthetics: { regions: ['us-east', 'eu-west', 'ap-south'], interval: 60s, steps: [...] } runs without errors on the first invocation.
2. Run the check locally to verify synthetics: { regions: ['us-east', 'eu-west', 'ap-south'], interval: 60s, steps: [...] } produces the expected result before pushing.
act -j build # or: pnpm test
Expected output: Local run matches CI behavior; no surprises after push.
3. Add the gate to the CI pipeline so synthetics: { regions: ['us-east', 'eu-west', 'ap-south'], interval: 60s, steps: [...] } blocks merge on failure.
- name: Run add synthetic probe monitoring
run: pnpm test
Expected output: Pull requests with failing synthetics: { regions: ['us-east', 'eu-west', 'ap-south'], interval: 60s, steps: [...] } are blocked from merging.
Troubleshooting
Problem
The check passes locally but fails in CI
Solution
Pin dependency versions and the runtime to match CI exactly; reproduce with the same Docker image or act.
Problem
Configuration is rejected with a schema error
Solution
Check the tool version matches the config schema; older versions may not support newer fields.
Limitations
- The gate only runs on events that trigger the workflow; locally pushed commits bypass it.
- Configuration drift is possible if someone edits settings outside version control.
Make the system observable
Start by measuring the problem. Run a synthetic check every minute from three regions so a regional outage is detected before users report it. The most common mistake is adding the gate without first confirming it catches the issue you care about. Run synthetics: { regions: [‘us-east’, ‘eu-west’, ‘ap-south’], interval: 60s, steps: […] } against the current codebase and inspect the output before wiring it into CI.
synthetics: { regions: ['us-east', 'eu-west', 'ap-south'], interval: 60s, steps: [...] }Correlate across services
Once the gate is in place, make failures actionable. A failing synthetics: { regions: [‘us-east’, ‘eu-west’, ‘ap-south’], interval: 60s, steps: […] } should point to the exact file and line, not a generic error. Pin the tool version in the lockfile so a upstream release does not silently change behavior. Review the gate output in every pull request just like a test result.