Skip to content

Reliability · Editable reference architecture

Synthetic monitoring architecture

An editable synthetic monitoring architecture reference showing Probe locations → Scripted journey → Public endpoint. Use safe test identities and bounded operations.

Open & Edit in DrawArc (Free, No Login Required)

Your changes stay in a separate draft on this browser. Download an editable project to keep a portable copy.

LinkedInTelegramReddit

Synthetic monitoring architecture diagram: Probe locations, Scripted journey, Public endpoint, Journey results and their connections
Synthetic monitoring architecture — follow the component relationships, then open the editor to adapt the design. View diagram image.

6 components · 4 connections · Open the editor to zoom, move nodes and edit source.

Architectural overview

Synthetic monitoring architecture addresses the responsibilities and boundaries shown in this reference rather than prescribing an entire production deployment. The primary flow starts at Probe locations and reaches Public endpoint through Scripted journey. Use this view to explain which component initiates work, which component owns a decision, and where a dependency can affect the caller. Use safe test identities and bounded operations.

The diagram contains 6 distinct components and 4 directed relationships. A separate path connects Journey results → Metrics store → Alert evaluation. These arrows describe logical interactions; they do not establish authentication, network access, atomic transactions or delivery guarantees. Label the actual protocol, payload contract and owner when adapting the drawing to your system. Keep synchronous and asynchronous boundaries explicit so that a reviewer can identify where a request ends and a later operation begins.

Before implementing this architecture, define expected load, data classification, latency budgets and recovery objectives. Give Probe locations a bounded dependency timeout and a documented failure response. For Metrics store, specify ownership, retention, access control and a tested recovery procedure. Validate the decision above against your workload instead of treating the presence of a component as proof of reliability. Open the editable canvas, replace generic labels with real deployment units, and document the decisions that differ from this reference.

The real-world problem

Design or explain synthetic monitoring architecture with explicit ownership and dependency paths. Use safe test identities and bounded operations.

Data flow

Connections from this diagram. Branches and control signals are not a single chronological sequence.

  • Probe locations → Scripted journey. Define the interaction contract and trace the resulting response or state change.
  • Scripted journey → Public endpoint. Define the interaction contract and trace the resulting response or state change.
  • Journey results → Metrics store. Define the interaction contract and trace the resulting response or state change.
  • Metrics store → Alert evaluation. Define the interaction contract and trace the resulting response or state change.

Security boundaries

  • Authenticate callers at the boundary before Scripted journey accepts protected work; authorize the specific operation rather than trusting network placement.
  • Use separate service identities and least-privilege permissions for Scripted journey, Public endpoint, Journey results. Encrypt sensitive traffic, protect credentials and avoid placing confidential payloads in logs.
  • Restrict and audit access to Metrics store; define retention and deletion requirements for the actual data.

Failure handling

Probe locations is unavailable or slow

Response: Apply bounded timeouts and controlled backoff only where retrying is safe. Return an explicit failure or durable acceptance; do not report success before required work is committed.

Verify: Interrupt Probe locations in an isolated test and measure errors, recovery and any repeated side effects.

Metrics store loses or returns stale state

Response: Use workload-specific durability, reconciliation and tested recovery. Specify how stale reads or a failed write affect callers.

Verify: Exercise the failure path with representative records and verify both the visible response and the resulting state.

An invalid or incompatible input reaches Scripted journey

Response: Validate the input contract before effects are committed. Preserve rejected input identifiers without exposing secrets, and document a safe replay or correction procedure.

Verify: Send malformed and older-version inputs through Probe locations and verify rejection, observability and unchanged valid state.

Trade-offs and alternatives

Use safe test identities and bounded operations.

Benefit
Makes the ownership and interaction boundaries visible for a focused design review.
Cost
The 6 illustrated components still require contracts, monitoring and operational ownership; extra boundaries can add latency and failure modes.
Alternative
Use a simpler deployment when it meets the same requirements, or split a boundary only after measuring a specific need.

Logical boundaries versus deployment units in Synthetic monitoring architecture

Benefit
Keeps the responsibilities of Probe locations, Scripted journey, Public endpoint visible without requiring a separate server for each box.
Cost
A logical view does not establish isolation, independent scaling or high availability; those require a separate deployment design and operational tests.
Alternative
Co-locate components in a simpler deployment first when ownership and workload requirements permit it.

When to use this architecture

  • Explain synthetic monitoring architecture to engineers or stakeholders using a concrete visual flow.
  • Review this decision before deployment: Use safe test identities and bounded operations.
  • Adapt a starting diagram for your own requirements, then record and validate every changed boundary.

Key components

Probe locations
Probe locations participates in synthetic monitoring architecture. Probe locations → Scripted journey. Define its contract, owner and access permissions in your implementation.
Scripted journey
Scripted journey participates in synthetic monitoring architecture. Probe locations → Scripted journey; Scripted journey → Public endpoint. Define its contract, owner and access permissions in your implementation.
Public endpoint
Public endpoint participates in synthetic monitoring architecture. Scripted journey → Public endpoint. Define its contract, owner and access permissions in your implementation.
Journey results
Journey results participates in synthetic monitoring architecture. Journey results → Metrics store. Define its contract, owner and access permissions in your implementation.
Metrics store
Metrics store participates in synthetic monitoring architecture. Journey results → Metrics store; Metrics store → Alert evaluation. Define its contract, owner and access permissions in your implementation.
Alert evaluation
Alert evaluation participates in synthetic monitoring architecture. Metrics store → Alert evaluation. Define its contract, owner and access permissions in your implementation.

Questions about this template

What does this synthetic monitoring architecture diagram show?

It shows 6 components with the core flow Probe locations → Scripted journey → Public endpoint. Use safe test identities and bounded operations.

Can I edit this diagram without signing in?

Yes. Open the template in the browser-local canvas to change nodes, connections and source. AI generation and cloud account storage require sign-in.

Is this a complete production implementation?

No. It is an editable reference. Validate the security controls, dependency behavior, capacity and recovery plan against your own requirements before implementation.

Validate your implementation

Use the relevant platform documentation to verify service limits, supported features and configuration. This diagram is an original reference rather than a reproduction of a provider deployment.