Currently, Synthetic Browser Tests in Splunk APM don’t provide a built-in way to clear the browser cache, cookies, or session data between individual Steps within the same monitor. Your workaround of creating separate monitors for each step is a common approach but, as you mentioned, it can be tedious and harder to maintain. Here are a couple of alternative suggestions you might consider: Use JavaScript in the Step to clear cookies and local storage: You can try running JavaScript at the start of each step to clear cookies and local storage, like this: document.cookie.split(";").forEach(function(c) {
document.cookie = c.trim().split("=")[0] + "=;expires=Thu, 01 Jan 1970 00:00:00 UTC;path=/;";
});
localStorage.clear();
sessionStorage.clear(); This might help clear session data, but it doesn’t fully clear browser cache for static assets. Separate Monitors with Scheduled Runs: While more maintenance-heavy, scheduling multiple monitors with one step each allows each browser instance to start fresh, ensuring accurate Lighthouse scores. Feature Request / Support: Consider submitting a feature request to Splunk support or your customer success team for native support of cache clearing between steps. This could be a valuable enhancement for Synthetic testing workflows. Hope this helps! If you find a better solution or workaround, sharing it here would be appreciated. If this helped you, some karma would be appreciated!
... View more