What you will learn in this TP
- Access the Dynatrace SaaS environment
- Understand how Synthetic Monitoring works overall
- Differentiate an HTTP Monitor from a Browser Monitor
- Choose the monitor type suited to the use case
- Understand the value of public and private locations
- Analyze an existing monitor's configuration
- Identify the key metrics (frequency, locations, type, steps)
- Display the list of existing locations
- Understand the process to add a private location
- Master the Credential Vault to secure credentials
- Create a multi-step HTTP monitor
- Configure status code and content validations
- Set specific execution parameters (location and frequency)
- Install and configure the Dynatrace Synthetic Recorder
- Record a full user journey
- Validate that a clickpath works correctly
Prerequisites and connection #
What you will learn in this section
- Access the Dynatrace SaaS environment
- Understand how Synthetic Monitoring works overall
Critical prerequisite: before starting this lab, you must have read this article.For this lab, we'll use the dedicated SaaS platform. Connect to the following address: https://playground.dynatrace.rousseltm.fr.
Please reach out to your instructor for the login credentials.
Introducing Synthetic Monitoring
What is Synthetic Monitoring and what's its main purpose?
HTTP Monitor versus Browser Monitor #
What you will learn in this section
- Differentiate an HTTP Monitor from a Browser Monitor
- Choose the monitor type suited to the use case
Dynatrace offers two main types of synthetic monitors. It's crucial to pick the right tool depending on your need.
Key differences
What's the fundamental difference between an HTTP Monitor and a Browser Monitor?
Billing (Synthetic actions)
How is billing calculated for these two monitor types in Dynatrace?
Remote Locations #
What you will learn in this section
- Understand the value of public and private locations
One strength of Synthetic Monitoring is being able to test the application from different geographic areas to check the impact of network latency.
Why use remote locations?
In the monitor creation interface (Synthetic > Create a synthetic monitor), you're asked to choose 'Locations'. What's the point?
Analyzing a scenario #
What you will learn in this section
- Analyze an existing monitor's configuration
- Identify the key metrics (frequency, locations, type, steps)
Now that you understand the concepts, let's put them into practice by analyzing existing synthetic monitors in the demo environment. The following two scenarios exist in the console; you need to find them:
Dynatrace website
For this scenario, identify:
- The scenario type
- The availability rate
- The execution frequency
- The number of steps
- The number of locations
- The location of the ActiveGates running the testsAstroshop Core API Endpoints
Now look for the monitor named Astroshop Core API Endpoints. As before, identify:
- The scenario type
- The availability rate
- The execution frequency
- The number of steps
- The number of locations
Managing locations #
What you will learn in this section
- Display the list of existing locations
- Understand the process to add a private location
In this section, we'll see how to manage locations in Dynatrace, which will then serve as starting points for your synthetic monitors.
Viewing locations
How do you view the list of public and private locations configured on your Dynatrace cluster?
Adding a location
How do you add a new private location so you can run tests from your own internal network?Note: the targeted ActiveGate must have been installed with the 'Synthetic' capability enabled. Once the ActiveGate is assigned and recognized by the system, this new location will appear in the list of choices when creating a scenario.

Setting up an HTTP scenario #
What you will learn in this sectionThis section guides you through creating a complex HTTP monitor on the SaaS platform https://demo.dynatrace.rousseltm.fr/.
- Master the Credential Vault to secure credentials
- Create a multi-step HTTP monitor
- Configure status code and content validations
- Set specific execution parameters (location and frequency)
Note: remember to use your name when creating each component (e.g. name_credential, name_monitor) so participants can tell their resources apart on the shared environment.
Warning: thereqres.inAPI enforces call-rate limits. You may see the error"rate_limit_exceeded"in your JSON output if you run too many tests in a short time.
Creating a secure account
Secure the credentials in the vault. Create a token with the valuereqres_8d849a2d1091451e8cec7154abc5a97cfor our scenario.Note: if this token has expired, feel free to generate a new one to continue the lab.
Initializing the scenario
Start configuring the monitor.
Adding the 'User list' step
Configure the first API request. The step must point to the URLhttps://reqres.in/api/userswith the GET method, use the previous token via thex-api-keyheader, and trigger an error if the response body contains"error"or its status code is >= 400.Setting frequency and locations
Time-based settings (every 5 minutes) and geographic settings from Paris (Azure) and Sydney (GCP).
Extracting data via JavaScript
Chaining steps lets you pass along dynamic data. Without it, the value of multi-step monitors is limited. Add a JavaScript script (Post-execution script) to extract the ID of the second element of the 'data' array:// 1. Check the HTTP status code if (response.getStatusCode() != 200) { api.fail("HTTP error: " + response.getStatusCode()); } var responseBody = response.getResponseBody(); var jsonData = JSON.parse(responseBody); // 2. Safety check: make sure "data" exists, is an array and has at least 2 elements if (jsonData && jsonData.data && Array.isArray(jsonData.data) && jsonData.data.length > 1) { var userIdValue = jsonData.data[1].id; // 3. Must convert to String to inject it into the Dynatrace context api.setValue("userid", userIdValue.toString()); // 4. Log it in Dynatrace's execution logs api.info("Extracted user ID: " + userIdValue); } else { api.fail("Parsing error: the JSON doesn't contain the expected second element in 'data'."); }Open in Notebooks
To debug your scripts or see the detail of the HTTP exchanges, Dynatrace lets you send a monitor's execution to a Notebook. Create and send your request to a new Notebook namedformation-synthetic-YOUR_NAMEto see the detailed step outputs. Very useful when troubleshooting.Final step: using the variable
A dynamic call based on the previous extraction. Add a test of the URLhttps://reqres.in/api/users/[user id retrieved in the previous step]and check that the output contains the text 'Become a better CTO'.
Setting up a Browser scenario #
What you will learn in this section
- Install and configure the Dynatrace Synthetic Recorder
- Record a full user journey
- Validate that a clickpath works correctly
This section guides you through creating a complex user scenario (Clickpath) using the Dynatrace browser extension.
Installing the extension
To easily record your clicks and navigation, install the Dynatrace Synthetic Recorder extension, available on the Chrome Web Store or Microsoft Edge Add-ons.Incognito mode
It's strongly recommended to allow the extension to run in Incognito mode. This lets you record your tests in a clean environment, with no cookies or pre-existing sessions that could skew the robot's behavior.
Recording the steps
Start recording with the extension and perform the following actions:- Open the URL: https://elearning.rousseltm.fr
- Click the Categories menu
- Click the View button on the Observability category
- In the course list, click View on the Dynatrace course
- In the section list, click Dynatrace Architecture
- Start playing the video
Difficulty level : ●●●○○ (3/5)
My progress
Sign in to track your progress and take notes. Sign in
💬 Recent discussions about this course
- Dynatrace : mes pods Kubernetes ne sont pas instrumentés malgré le DynaKube✓ solved · 1 reply(ies)
Ask a question about this lesson →See all discussions about this course
Course Glossary
AIOps (Artificial Intelligence for IT Operations)
The use of artificial intelligence and machine learning to automate and improve IT operations (e.g., anomaly detection, reducing alert noise).
OpenTelemetry
An open source framework providing standards, APIs, and SDKs to collect and export observability data (traces, metrics, logs) in an agnostic way.
Core Web Vitals
Set of three metrics defined by Google to measure the real experience of a web page: loading (LCP (Largest Contentful Paint)), responsiveness (INP (In...
LCP (Largest Contentful Paint)
Time until the largest visible element of the page (image, video or text block) is rendered: it shows when the main content appears. Loading metric of...
INP (Interaction to Next Paint)
Latency of interactions (click, tap, key press) observed over the whole visit: the delay between the user's action and the next paint. The reported va...
CLS (Cumulative Layout Shift)
Measure of visual stability: the sum of unexpected layout shifts (a button moving just as you click, text pushed down by an ad). Unitless, computed ov...
FCP (First Contentful Paint)
Time until the first content (text, image, SVG) is rendered: the moment the user sees the page start loading. It is not a Core Web Vital, but it helps...
TTFB (Time to First Byte)
Time between the start of navigation and the arrival of the first byte of the response: it adds up redirects, DNS, TCP/TLS connection and server proce...
FID (First Input Delay)
Former responsiveness metric of the Core Web Vitals: the delay before the browser starts handling the first interaction (good ≤ 100 ms). It ignored la...
TBT (Total Blocking Time)
Lab metric (Lighthouse): the sum, between FCP (First Contentful Paint) and the end of loading, of the blocking part of each long task (over 50 ms) on ...
CrUX (Chrome UX Report)
Google's public dataset aggregating the Core Web Vitals measured from real Chrome users (at the 75th percentile, per origin and URL, over a rolling 28...
Lighthouse
Google's free audit tool, built into Chrome DevTools and PageSpeed Insights: it loads the page in a simulated environment and scores performance, acce...
Apdex
Application Performance Index: a satisfaction score between 0 and 1 based on a time threshold T. Requests under T are “satisfied”, between T and 4T “t...
Recommended Articles
Dynatrace Synthetic Monitoring: complete guide and best practices
Learn how to use Dynatrace Synthetic Monitoring to proactively monitor your applications, from th...
Synthetic monitoring as code: industrializing synthetic scenario management
Learn how to integrate synthetic monitoring into your CI/CD pipelines for automated, resilient pe...
RUM and Synthetic Monitoring with Datadog: synthetic transaction monitoring and user experience
Measure user experience with Datadog: browser and mobile RUM, Core Web Vitals, Session Replay, li...
Dynatrace Credential Vault: securing and managing your secrets
Discover how the Dynatrace Credential Vault app lets you securely manage passwords, tokens and ce...
Website monitoring: availability, HTTPS monitoring, certificates and performance
Set up website monitoring: availability and HTTPS checks, certificate expiry, response time, Core...
Dynatrace Real User Monitoring: injection, web applications and verification
Set up real user monitoring in Dynatrace: automatic injection by OneAgent, agentless monitoring, ...
ActiveGate and network zones: architecture, routing and high availability
Understand and deploy ActiveGate in Dynatrace: roles (routing, API, cloud integrations, extension...
DQL in practice: exploring logs and events, notebooks, dashboards and performance
Use the Dynatrace Query Language day to day: explore logs and events, chain commands, parse field...
Synthetic Monitoring in Grafana Cloud
Synthetic Monitoring in Grafana Cloud: HTTP, DNS, TCP, Ping, Traceroute, multi-step, k6 script an...