Synthetic Monitoring Explained: Best Practices, Examples, and Tools

Modernistic covering are look to be up 24/7, and that puts certain pressure on the performance essay team. One of their goals is to continuously monitor real exploiter ’ interaction with the site and develop a performance benchmark base on that information. & nbsp;& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;

However, there ’ s a catch: sometimes real user monitoring perform n't allow you to find the scheme 's behavior in utmost scenario (such as sudden capitulum in traffic or abnormal user behaviors). After all, those are extreme scenarios, and they don ’ t happen that often. That ’ s why & nbsp;semisynthetic monitoring & nbsp;is created to occupy in the gap that & nbsp;existent user monitoringcan ’ t provide. & nbsp;& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
 

In this article, we will dive deep into the concept of synthetic monitoring, present the key components of this approach, as well as best practices you should follow to better implement it. You can evensaltation straight to our comprehensive usher on how to do synthetic monitoring.

What is Synthetical Monitoring?

Man-made monitoring is a procedure where testers create automated scripts simulating real users ’ interactions with the coating or site to proactively detect performance subject and evaluate overall system health. These automated scripts are called & nbsp;man-made transactions, and they facilitate testers guess the scheme ’ s performance when real user data is not yet available, or too challenging to capture.

Benefits of Synthetic Monitoring

Real user datum does n't always say us the total ikon for the software ’ s execution. It is admittedly outstanding to have data captured directly from real users to provide actual user experience metrics, but & nbsp;what ifthe feature is however under ontogeny and not yet released for real users? How can you proactively capture the data to establish a execution benchmark for it?& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
 

Even if the feature is already released, user activeness tends to be quite restrict in the other stage. Performance testing teams get no pick but to passively wait until enough datum has be collect so their test resultant can be statistically significant.& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
 

Similarly, to ensure the highest level of coverage, testers also want to appear at more extreme event, such as sudden traffic spikes or host outage, and you don ’ t usually have datum for such outlier scenario. To know how the scheme behaves under such pressures, testers can create & nbsp;synthetic transactions & nbsp;to mime large volume user and send them to the website and document the results.& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
 

When it comes to dependence, the need for synthetic monitoring becomes even more marked. There are so many variable at drama that can mess with the final trial result. Having a controlled environment exclusively built for the examination of that specific feature is a must if you want the test results to be more reliable. It also reduces the risk of unintentionally breaking former features. & nbsp;& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
 

In little, you need synthetic monitoring for two primary ground:

1. Existent exploiter information is not yet available, or difficult to acquire.
2. Testers desire to have great control and less risk over the testing process.& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
    

There are so many early benefits of man-made testing, not because of its & nbsp;semisynthetic nature, but rather because of its & nbsp;automatize nature:

1. Scheduled testing: & nbsp;You can schedule your synthetic proceedings to run at specific times, preferably during peak usage period, upkeep windows, or any time periods suitable for your test scheme.
2. Improved analytics: & nbsp;Historical datum generated by man-made monitoring allows you to dive deep into the testing effort and uncover underlying patterns which you can turn into worthful insights for succeeding decision-making.
3. Customization: & nbsp;Synthetic monitoring can be tailored to your specific testing necessary, allowing you to send traffic on specific journeys through the site to address your unique testing needs.

Man-made Monitoring vs. Real User Monitoring

Have a look at the table below to better translate the deviation between synthetic monitoring and real user monitoring:& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
 

Examples of Semisynthetic Monitoring

Have a expression at some examples for synthetic monitoring below. You should notice a pattern: all of them receive a fairly specific set of requirements that would be rather gainsay to capture if you go with real user monitoring:

1. Regularly examination the load time of your website 's homepage from different geographic locations.
2. Simulate exploiter searches for products on your e-commerce site to corroborate that search results load quickly and accurately.
3. Automate the registration operation by creating test accounts to control that exploiter can successfully file and log in.
4. Test the compliance of form on your website to ensure that data is processed correctly and validation messages appear when necessary.
5. Simulate the entire e-commerce checkout process from adding items to the cart, selecting transportation pick, to dispatch a purchase.
6. Create synthetical tests that send HTTP requests to specific API endpoints to measure response times and identify potential subject.
7. Automate user logins, providing certificate and ascertain that the authentication process is secure and efficient.
8. Automate the launch of your mobile app and simulate various user interactions like screen transitions, selections, and form inputs to guarantee a smooth user experience.
9. Generate specific error conditions to control that mistake pages are correctly displayed and render utilitarian info to users.
10. Monitor images/videos to ensure they are available and load quickly for exploiter.

A Comprehensive Guide to Do Synthetic Monitoring

Before you begin, make sure you take the right attack:

• Write a test script with an automation testing model (Seleniumis a full representative. You besides need to instal Node.js and WebDriver for the specific browser you want to run the tryout script, such as ChromeDriver).
• Write test handwriting with the help of an mechanization testing creature. Installing such a tool is more straightforward, and you can & nbsp;.& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
   

Each creature comes with their own advantages that you should take into consideration. Writing your own test hand grants a great level of customization, but the downside is that you have to update all of them when updates are rolled out. Automation examination tools, on the other hand, frequently get with full-bodied lineament that support you throughout the & nbsp;entire testing life rhythm, but you ask some initial investing to get entree to the creature.

1. Synthetical Monitoring With Selenium

Scenario: & nbsp;In this example, we 'll create a Selenium test script in JavaScript to automate the process of assure a website 's homepage for its availableness and response clip.& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
 

Dependencies:

1. Node.js: & nbsp;Download here
2. Selenium WebDriver: You 'll necessitate the Selenium WebDriver library for Node.js, which you can install using npm (Node Package Manager). Open your terminal or command prompt and run the following bid:

npm install selenium-webdriver

For ChromeDriver, also run the undermentioned command in your terminal:

npm install chromedriver

Test steps:

1. Open a web browser.
2. Navigate to the site 's homepage.
3. Measure the reaction clip of the homepage.
4. Verify that the page loads successfully (HTTP status code 200).
5. Close the browser.& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
    

Test script:

The following script performs the tryout steps we note above. Make sure to change the URL from & nbsp;https: //www.example.comto the website you need to examine.& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
 

const {Builder, By, Key, until} = require ('selenium-webdriver '); const assert = require ('assert '); (async function () {// Set up the Selenium WebDriver const driver = wait new Builder () .forBrowser ('chrome ') .build (); try {// Navigate to the website 's homepage await driver.get ('https: //www.example.com '); // Replace with the URL you want to supervise // Measure the response time const startTime = Date.now (); // Wait for the page to load (e.g., by insure for an element on the page) await driver.wait (until.elementLocated (By.id ('someElement ')), 10000); // Adjust the element and timeout as involve const endTime = Date.now (); const responseTime = endTime - startTime; // Verify the page loads successfully (HTTP status code 200) const statusCode = await driver.executeScript ('return window.performance.timing.responseStart '); assert.equal (statusCode, 200, 'Expected HTTP status codification 200 '); // Log the response time console.log (` Response time: $ {responseTime} ms `);} catch (error) {console.error (` Test miscarry: $ {error.message} `);} finally {// Close the browser await driver.quit ();}}) ();

That was precisely a basic example of how to use Selenium WebDriver to measure the response time of a web page and ascertain if it loads successfully. Make sure that you understand the pros and cons of synthetic monitoring with Selenium: & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
 

2. Synthetical Monitoring With Katalon

For automation testing instrument, the summons of synthetic monitoring is much more straightforward. You don ’ t get to script much thanks to all of the low-code test authoring characteristic (such as & nbsp;Record-and-Playback, which essentially records your on-screen action and turns that succession into a codification snippet that you can freely execute on environments of your choice. & nbsp;& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
 

take this to an even high level when centralizing all point of the testing life round, so that you can plan your synthetic monitoring, write scripts based on that program, schedule them to be executed topically or on-cloud for web, desktop, mobile, and even API, then generate detailed reports to help you interpret your testing strength, & nbsp;all in one spot.

& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
 

Here ’ s how you can do synthetic monitoring with- a comprehensive software testing platform for web, background, API, mobile:

1. Create a new examination case or test retinue in.
2. Use the built-in WebUI mechanization capabilities to make scripts that model user interactions with your web application.
3. Set up the tests to run at scheduled intervals, such as every hour or every day.
4. Use Katalon Analytics to catch the results of your tests and place performance issues.
5. Integrate Katalon Studio with APM vendors.& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
    

Step 1:Sign up and download Katalon Studio. This will primarily be where you create your test event.

& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
 

Step 2:  Once you have downloaded Katalon Studio, launch it. You should see the Katalon Studio interface as below. You can then click the “ Create new Test Case ” push.

& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;

 

Let ’ s call this test case “ synthetic_monitoring ”. After you name it and write some description, click OK.

You are now ready to create your test case. Katalon proffer a wide assortment of keywords (which are essentially automation code snippets for specific actions) that you can use to craft a total on test case. & nbsp;

Below is a snapshot of our keyword list—quite plenty for all of your man-made monitoring needs, and there are C to choose from. You can yet & nbsp;or leverage the & nbsp;to record your on-screen activeness and turn that successiveness into a full hand that can be fulfill across environments. & nbsp;

But it 's not just about quickly create test cases for web (and also desktop, mobile, or API), without having to compose any code, & nbsp;but alsoabout programing, executing, and regard story for them in one place. Here you can see how to schedule a specific trial lawsuit and exam entourage to run on specific elements, at what time, and even what intervals.

After that, you can check the results in Katalon Analytics, with detailed information on passed/failed exam, before diving deep into the granularity. & nbsp;

& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
 

Read More: & nbsp;

Challenges of Synthetic Monitoring

• Limited visibility: & nbsp;Be aware of your assumptions for user behavior. Synthetical monitoring is commonly found on & nbsp;speculationson what your users do, especially in earlier stages of testing where usage datum is not yet available. Can you be sure that they are representative enough for real-world usage? Is it too simplistic? Also, you should note that user behavior is not static: it germinate over time. That is why you necessitate to complement synthetic monitoring with some real-user monitoring to add some realism.
• Adjustment for growth: & nbsp;As your website grow over time, it is indispensable to besides set your execution benchmark accordingly. What was seen as “ traffic spikes ” in your out-of-date test script can actually become “ normal traffic ” after a long enough period of time. If the assertions in your test scripts are not oftentimes updated, you will see false positives be reported. These script maintenance tasks can hap alongside infrastructure raise.
• Scalability: & nbsp;As your organization grows, your synthetical monitoring substructure likewise needs to evolve consequently. This introduces additional price and proficient challenge.