Cloud concept · Updated

Synthetic Transactions - Synthetic transactions are scripted interactions that simulate user or client activity to measure whether an application works correctly and responds within expected times.

In short

Synthetic transactions actively exercise application endpoints and workflows on a schedule, providing repeatable measurements even when real users are absent. They help detect broken journeys, regional connectivity problems, and performance regressions that infrastructure health checks alone can miss.

Cloud Concepts Hub →

6 key aspects of Synthetic Transactions

Effective synthetic transactions combine meaningful assertions, representative execution paths, safe automation, and actionable telemetry to continuously validate critical application journeys.

01
Outcome-based validation

Assert that the expected application result occurred, not just that an endpoint returned a successful status. Check response fields, rendered elements, or workflow state to detect functional failures.

02
Repeatable, proactive execution

Run controlled interactions on a schedule, including during periods with no real traffic. Choose intervals and timeouts according to the required detection time and execution cost.

03
Representative execution locations

Place runners where they exercise the access paths that matter, including public regions and private networks. Interpret results according to the DNS, network, and application components each path actually traverses.

04
End-to-end and step-level visibility

Measure complete user journeys while retaining individual step timings and failure details. Combine these observations with logs and traces to distinguish an authentication failure from a slow downstream dependency.

05
Safe production automation

Use restricted test identities, protected credentials, controlled data, and reliable cleanup. Prevent checks from triggering real payments, fulfillment, notifications, or duplicate writes.

06
Complementary user-experience evidence

Use synthetic results for consistent baseline checks and real user monitoring for actual session experience. Neither a passing synthetic journey nor healthy infrastructure metrics alone establishes that every user can complete every task.

What is Synthetic Transactions

3 min read

Synthetic transactions simulate meaningful interactions with an application, such as signing in, searching a catalog, adding an item to a cart, or submitting an API request. A monitoring runner executes a script, checks the results, and records success, failure, and timing information. Here, transaction means a logical interaction or workflow; it does not necessarily mean a database transaction or require a financial operation.

Useful checks validate outcomes rather than merely confirming that a server responds. An HTTP 200 response can contain an error page, an empty search result caused by a broken dependency, or an authentication redirect. A synthetic check should assert the expected status, response content, page element, or business result. For a multistep journey, capture individual step durations as well as total execution time so that failures are easier to locate.

In cloud environments, runners can operate from external locations to exercise public DNS, TLS, content delivery, ingress, authentication, and application dependencies. Runners inside private networks can test internal APIs and private applications. Placement determines what a result proves: a check originating inside a virtual network does not demonstrate that public users can reach the application. Multiple locations help distinguish a localized network issue from a widespread application failure, although cloud-hosted runners do not reproduce every user's access network.

For example, an online retailer might run a browser-based journey every five minutes that signs in with a dedicated account, searches for a known product, and adds it to a cart. A separate API check could verify inventory lookup more frequently. The browser journey can reveal rendering or JavaScript problems that the API check misses, while the API check usually runs faster and costs less. Neither should place real orders unless the workflow explicitly prevents fulfillment and payment side effects.

Production checks require operational safeguards. Use dedicated accounts with minimal permissions, retrieve credentials from a secrets manager, and remove sensitive values from logs, screenshots, and traces. Give generated records unique identifiers and clean them up reliably. Bound execution time, limit concurrency, and design retry behavior carefully so monitoring does not create duplicate actions or overload a struggling application. Maintain scripts alongside application changes, using stable selectors and controlled test data to reduce failures caused by brittle automation.

Alert on failed assertions and latency thresholds that reflect the monitored journey. Requiring repeated failures or corroboration from multiple locations can reduce noise, but also delays detection. Detection time depends on the execution interval, timeout, and alert evaluation policy. Preserve failure artifacts and correlate execution timestamps or request identifiers with application logs and distributed traces. Treat missing executions as a monitoring problem rather than assuming they represent successful checks.

Synthetic transactions provide controlled, proactive observations, not a complete measurement of actual customer experience. Real user monitoring complements them by observing real sessions across actual devices, networks, and usage patterns. Synthetic success rates describe the selected scripts and locations, not automatically the availability experienced by all users. These checks also differ from load testing: their usual purpose is continuous validation with limited traffic, not measuring maximum capacity.