Docs » Advanced test configurations

Edit this page
Learn how

---

Advanced test configurations

• Built-in variables
  • Random variables
  • Date-and-time variables
  • Location variables
  • Request variables for API Tests
  • Use a variable in a test
• Detectors and alerts
  • Types of detectors in Synthetics
  • Best practices for sending an alert when a synthetic test fails
  • Set up a detector for Splunk Synthetic Monitoring tests
    • Create a page-level detector for a Browser test
    • Create a transaction-level detector for a Browser test
    • See also
• Devices
  • Select a device type for Splunk Synthetic Monitoring tests
• Downtime
  • Schedule a downtime configuration
  • Records
• Global variables
  • How can you use a global variable?
  • What happens when you conceal a global variable?
  • Create a global variable
  • Edit a global variable
  • Use a global variable in a synthetic test
    • Use a global variable in a browser test
    • Use a global variable in an API Test
• Private locations
  • What is a runner?
  • Use cases for private locations
  • Requirements
  • Set up a new private location
    • What you can do with your private location ID
    • Manage your tokens
  • Working with Docker
    • Limit logging in Docker
    • Add certificates in Synthetics
  • Configuring Proxy Settings for Private Locations
  • Assess the health of your private location
    • Troubleshoot queue length and latency
• Public locations
  • Best practices
  • Locations
    • AU0
    • EU0
    • EU1
    • EU2
    • JP0
    • US0
    • US1
    • US2
  • JSON file of public locations
• Compare run results to Web Vitals with Splunk RUM
  • Prerequisites
  • Compare Web Vitals for your run results
  • See also
• Validate your test configuration with try now
  • When to use try now to validate your test configuration
  • Example
  • Limits

To simulate diverse types of traffic to your site or application, use a range of configuration options to customize each of your tests.

Test naming conventions

Choosing informative names for your tests and alerts helps organize content. Here are some guidelines:

• Add a category as a prefix to your test name like group, application, brand, or team names so that you can simplify searches. For example, these two Browser tests start with [ButtercupGames].

• Add a description about the purpose of the test like the workflow, process, performance, or data source.

This page was last updated on Dec 20, 2024.

---

❮

Previous

Test performance KPIs

Next

Built-in variables

❯

---

• API docs
• Blog
• Training
• Free Trial