A scenario defines a test configuration. Select an existing SLA profile to verify and a list of existing populations to test from NeoLoad project. Define a load policy for each population.
| Name | Description | Accept variable | Required | Since |
|---|---|---|---|---|
| name | The name of the scenario | - | ✓ | |
| description | The description of the scenario | - | - | |
| sla_profile | The name of the SLA profile to apply to the Scenario (will not be applied to children) | - | - | |
| store_variables_for_raw_data | This option allows storing variables for raw data. The default value is "false". | - | - | 7.6 |
| monitoring | The monitoring parameters | - | - | 7.6 |
| populations | The list of name of the existing populations | - | ✓ | |
| rendezvous_policies | The list of the Rendezvous | - | - | 7.6 |
| excluded_urls | The regular expressions to ignore matching Requests from the scenario during the test playback | - | - | 7.6 |
| apm_configuration | The APM configuration for the monitoring with Dynatrace | - | - | 7.5 |
Defining a scenario with 1 SLA profile, 1 population, with Dynatrace monitoring and excluded URLs :
scenariosnameMyScenario descriptionMy scenario with 1 SLA profile and 1 population sla_profileMySlaProfile store_variables_for_raw_datatrue monitoring before30s after1m30s populationsnameMyPopulation constant_load users500 rendezvous_policiesnamerendezvous when50% timeout50s apm_configuration dynatrace_tagsmyDynatraceTag excluded_urls.*\.jpg.*\.jpeg.*\.gif.*\.png