Expanded Browser Test settings are now available in Splunk Synthetic Monitoring within Splunk Observability Cloud. Whether you want to masquerade as a specific device or prevent a marketing modal from appearing randomly during a test, Synthetics users often have specific requirements for browser instrumentation for testing. With this release, Synthetics within Observability Cloud users can customize how they instrument browsers for browser tests to more accurately replicate the user experience and business-critical workflows they hope to measure.
Advanced Settings Available in the New UI
Advanced Settings for Browser Tests
Users can now configure the following settings via the API or UI for browser tests.
Cookies - Set cookies by adding the name, value, domain/host, and optional path to prevent popup modals from randomly appearing so tests can run to completion without interruption.
Custom Headers - For the custom headers setting, you can select from a list of available headers or define a unique custom header to add to test workflows.
SSL/TLS Validation - Enforce TLS/SSL validation is applied by default, which can cause tests to fail if host certificates are invalid or expired. With this configuration, you can deselect this option.
Host Overrides - Users can add Host Override rules to reroute requests from one host to another. This is helpful when testing an existing production site against page resources loaded from a development site or a specific CDN edge node.
User Agent - With this configuration, you can specify the device type for your browser tests by selecting the default option or adding a custom User-Agent string so you can measure how different device types impact page rendering.
Authentication - You can add username and password information to the browser to test workflows that require authentication.
Splunk Synthetic Monitoring Within Splunk Observability Cloud
Splunk Synthetic Monitoring within Splunk Observability Cloud offers customers a comprehensive solution for their observability practice allowing IT and engineering teams to proactively detect issues impacting web and API performance and end-user experience, and troubleshoot and remediate issues in the web browser, server, or third-party dependencies—all within a single UI.
Splunk’s standalone Synthetic Monitoring offering, formerly known as Rigor, is still available. We will continue to migrate all the features and capabilities to the new UI.
Interested in testing out advanced settings for browser tests? Sign up for a free trial today!
— Teneil Lawrence, Digital Experience Monitoring (DEM) Product Marketing