Table of Contents
See also Synthetic Scripts FAQ (Part I).
On-Premises/SaaS
What are the supported on-premises/SaaS/hybrid configurations?
Controller
|
Web Mobile/RUM
|
Synthetic
|
| SaaS |
SaaS |
SaaS |
| On-premises (v4.5.4+) |
On-premises (v4.5.4+) |
On-premises (v4.5.4+) |
Security/Passwords
Do you have an encrypted store for passwords?
Yes. The Synthetic Credential Vault securely stores credentials used for synthetic jobs. When you create a synthetic job with a synthetic script, you can retrieve a stored key/value credential pair, like a username and password, and inject the credential into the synthetic script. Then, when the synthetic job runs, the synthetic script executes and retrieves the credentials stored in the Synthetic Credential Vault.
See our documentation to learn more about the Synthetic Credential Vault.
Are scripts and test results transferred securely?
The short answer is that scripts and their results always go over encrypted channels. The scripts and results are stored in clear text in various databases, so a database breach could compromise the information, but, of course, we try very hard to prevent database breaches.
For the long answer, see the summary of the data path of a script and its results below. (Foo) denotes data at rest.
- Script -> UI -> Controller -> EUM SaaS services -> (EUM SaaS database) -> Test driver service.
- Test driver service connects to PoP machine with an encrypted channel and sends WebDriver commands to the PoP, driving the browser.
- The browser connects to a website and imitates a user. Instrumentation hook gathers data from the browser and sends it to an EUM SaaS service. Now we have a test result.
- Test result -> EUM SaaS service -> (metric store, event store, and EUM SaaS database) -> controller -> UI.
Each of the -> links uses HTTPS, with two possible exceptions which are determined by the user:
- If you use an on-premises controller, security between the browser and controller is your responsibility. In other words, don't allow non-HTTPS connections to your controller.
- Security between the test browser and your website is your responsibility. Consequently, your script should connect to your site over HTTPS.
How can I retrieve passwords from a secure server, not hard-code them in the script?
If you can write Python code to do something using the standard libraries, you can do that in your script. For example, you can use Python's requests library to make REST calls to fetch a password.
Selecting Elements
How do I click on an element in an iFrame (for instance to handle a pop-up)?
You can wait for the iFrame element to be clickable as shown in the snippet below.
from selenium.common.exceptions import TimeoutException
# Cancel an advert pop-up in an iframe
# Find the right iframe
frame = wait.until(EC.element_to_be_clickable((By.XPATH,'//xpath-to-your-iframe]')))
# Move into the iframe
driver.switch_to_frame(frame)
# Close the pop-up
wait.until(EC.element_to_be_clickable((By.XPATH,'/xpath-to-element/i'))).click()
# Move to the default content
driver.switch_to_default_content()
|
Snapshots
What is the retention period of snapshots?
Snapshots are retained for two weeks.
Can the retention period of a snapshot be extended beyond the default?
No, the snapshot retention period cannot currently be extended on SaaS.
Supported Features
Can Synthetics be used for API testing/monitoring?
Though synthetic web monitoring can be used to monitor APIs, it is not officially supported. Synthetic API monitoring is part of our roadmap: watch this space for updates.
If the customer's use case involves monitoring the API from inside their network, then Service Availability is the preferred solution. Monitoring from outside their network is not an option at this time.
Is virtual page naming (for single-page apps) supported in Synthetics?
Virtual pages are not yet supported in Synthetic (possible future feature), so virtual page naming is not supported.
Are JavaScript popups such as those created with window.alert or window.prompt supported?
Yes, JavaScript popups created with window.alert or window.prompt are fully supported.
Are multiple windows, as in multiple HTML documents loading either in different tabs or windows, supported?
Multiple windows or tabs with loaded HTML documents are only partially supported. You can create scripts to handle multiple windows, but the session results will combine the waterfall metrics and the resources from all of the windows into one page. Thus, you will not be able to view the individual results for each browser window.
Troubleshooting
How do I debug my script?
We recommend doing your initial debugging locally: that’s always the easiest place to debug. We capture the stdout and stderr streams from your script, so you can debug that way. And we show partial sessions for scripts that failed part-way through, so you can see what the browser did up until the script failed.
How do you prevent timeouts in scripts?
Timeouts in scripts can be prevented by explicitly waiting for specific element states (e.g., clickable). See also the paragraph Expected Conditions discussed in Explicit Waits.
If something breaks, how can I tell if it’s my site, my job, or your infrastructure?
If your script has an assertion failure, the session status is “Failed”, which indicates a problem with your site. If your script crashes, the session status is “Broken”, which indicates a problem with your script. If we can’t run your script, the session status is “Internal Error”. We hope you’ll never see that. For single-URL measurements, a 5xx is “Failed,” and a 4xx is “Broken”.
Why are visual metrics (Visually Complete, Speed Index) not always present?
There are currently two known issues regarding visual metrics:
- In some cases, Chrome sessions may not display visual metrics because of a bug. This typically happens on pages with JS redirects, but may happen elsewhere as well. This is a Chrome-specific problem, and we are working on a solution.
- A Windows issue will sometimes prevent these metrics to be computed for all browsers. When this happens, the agent needs to be rebooted. This is infrequent because we get alerts and react as fast as possible.
