The Synthetic Test Dashboard in Acumen Logs provides a detailed breakdown of your synthetic monitoring tests, allowing you to:
This guide will help you navigate the dashboard efficiently.
At the top-left of the dashboard, youβll find the Run button.
Clicking Run executes the test immediately.
π Tip: If a test is failing repeatedly, run a one-off test to check whether the issue is persistent or intermittent.
At the top-right of the dashboard, you have key control options:
π Tip: If you frequently adjust alert settings, group alerts by priority levels to avoid unnecessary notifications.
Below the test controls, the Response Breakdown Graph visualizes all test responses over time.
π Tip: If the graph shows too many 300 redirects, check if your test is interacting with unnecessary redirect chains that slow performance.
Below the Response Breakdown Graph, this section provides a quick summary of the most recent test execution, including:
On the left side, youβll see a pie chart representing overall test status:
Watch Recording Button β Replay the test execution video.
π Best Practice: If a test fails, watch the recording first to identify issues like missing elements or slow page loads.
The Synthetic Test Dashboard provides a comprehensive overview of website functionality and performance.
β Monitor performance trends over time
β Diagnose failures with detailed breakdowns
β Compare test results to find issues
β Fine-tune alerts for better monitoring
Question | Answer |
---|---|
What is synthetic monitoring? | Synthetic monitoring simulates user interactions with a website by running scheduled tests from different locations. It helps detect performance and availability issues before real users are affected. |
Does running synthetic tests impact website performance? | No, synthetic tests are designed to simulate user interactions without affecting real visitors. However, very frequent tests (e.g., every minute) may create minor spikes in server requests. Best Practice: Adjust test intervals to balance monitoring without overloading the server. |
Can synthetic monitoring detect real-time user issues? | No, synthetic monitoring simulates user actions but does not track real users. If you need real visitor data, combine it with Real User Monitoring (RUM) to capture live user performance. |
What should I do if my test fails inconsistently? | Inconsistent failures may indicate: (1) Third-party dependencies (CDN, API) having downtime, (2) Dynamic elements (captchas, one-time codes) interfering, or (3) Issues occurring at peak traffic hours. Solution: Run tests at different times or compare failure logs for patterns. |
Can I run synthetic tests from different locations? | Yes! You can select multiple locations when setting up your test to simulate how users experience your site globally. Tip: If your site has region restrictions, check for firewall settings or geo-blocking. |
Why do I see different results when testing manually vs. automated tests? | This happens because: (1) Synthetic tests use controlled environments without cached resources, (2) Your browser loads elements differently due to cookies, stored data, or login sessions, and (3) Some dynamic content (personalized elements) may not be present in synthetic tests. Solution: If your test needs authentication, use session handling or API tokens. |
Why are my tests failing on mobile but passing on desktop? | Possible reasons: (1) A responsive design bug, (2) A JavaScript issue in mobile browsers, or (3) Blocked mobile user agents. Solution: Switch device emulation settings to different phone models or check for mobile-specific errors in console logs. |
Can synthetic tests monitor API endpoints? | Yes! If you need to monitor API uptime or response validation, use API Monitoring instead of synthetic tests. API monitoring is better for checking status codes, validating response payloads, and ensuring third-party integrations work. |
How can I prevent synthetic tests from being blocked by my websiteβs security? | Some security systems may block automated tests as bots. To prevent this: (1) Whitelist Acumen Logsβ testing IPs, (2) Use a static test user for login-based monitoring, and (3) Avoid running tests too frequently on high-security pages like checkout flows. |
How do I set up alerts for test failures? | Go to the Alerts section in the dashboard and configure notifications via: (1) Email, (2) Slack or Microsoft Teams, (3) Webhooks, and (4) Desktop notifications. |
How do I integrate synthetic monitoring alerts with third-party tools? | You can integrate alerts with: (1) Email Alerts & Slack / Microsoft Teams for real-time notifications, (2) Webhooks** to trigger workflows in tools like Zapier, and (3). |