Configuration

Monitoring Configuration

Read-Only Settings

The Configuration of a monitoring project is very similar to the basic project configuration, but there are a few special settings for this project type. The following settings are for your information only and can be changed by XTC administrators only:

• Data Persistence (how long certain data, like Execution History, will be persisted), and
• Execution Environment (IP addresses of the machines where monitoring scenarios are running).

Dynamic Repository Branch

Another specialty for Repository Configuration is that you can define the branch to use by either specifying its name (static branch) or by defining a URL of a resource from which the branch name can be extracted dynamically using a regular expression. (This may be useful if you want to make the used test scenario code dependent on your currently deployed app version.)

Defining Scenario Defaults

On the Scenario Defaults tab in Configuration you can define default settings and manage notification settings to be used for all monitoring scenarios. These defaults can be overwritten for each individual scenario. To view or edit scenario defaults, use the toggle on the right to expand the default section, where you will find one or more editing buttons next to the settings:

The scenario defaults tab with expand toggle and editing button.

Quiet Periods

You can define Quiet Periods for your monitoring projects. These are time spans in which no notifications will be sent (and, if you configure this, no scenarios will run).

To add a new quiet period, click the + symbol at the top of the Quiet Periods list. You may then define a label, a start time and an end time, and configure whether or not scenarios should be executed in this period. The newly created quiet period will then show up in the list. All periods in the list can be edited, disabled or removed, no matter whether they are in the future, in the past or currently active.