Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Setting Up Test and Monitor Templates

Templates for test and monitor types need to be set up manually through the Paragon Active Assurance front-end user interface. A walk-through of how to do this is provided below. Templates for other test and monitor types than the ones appearing in the example are created similarly.

You can also consult the in-app help under Working with tests and monitors > Creating templates.

Setting Up Test Templates

  • On the left-side bar, click the Tests button and select New Test Sequence:

You are taken to the setup screen for tests.

  • Click the Create template button.

The procedure of creating a template is very similar to creating a test. The difference is that for each parameter setting, you can choose whether to hard-code the setting into the template or leave it to be defined at runtime.

At the top level, a test consists of a number of steps which are executed in sequence. A step in turn can contain multiple tasks that are executed in parallel.

Example: Test Template for HTTP

In the example that follows, we will create a test template for HTTP. The template consists of a single step:

Do as follows:

  • Name the template, and optionally enter a description of it.

  • Click the Add Step button.
  • In the left-hand column with task categories, select HTTP & DNS.
  • Add an HTTP task.
  • Enter values for the parameters you want to hard-code as constants into the template.
  • For parameters that you want to leave to be defined from the orchestrator at runtime, check the Template input box. Then, for each parameter, select "Create new" in the Input box and accept the default names. The field Variable name is what is used to refer to the parameter in orchestration. In the screenshot below, Clients and URL are treated in this way.

  • You are now done defining the template. Click the Save button at the top. The new template will appear in the My Templates section when you start defining a new test.

Example: Test Template for TWAMP

Below is another example of a test template, this time for TWAMP testing. Unlike the HTTP template above, the TWAMP template does not recur in the orchestration examples, but is provided simply for purposes of additional illustration.

  • Follow the same steps as in the section Example: Test Template for HTTP, up to and including clicking the Add Step button (but alter the Name and Description fields as appropriate).
  • In the left-hand column with task categories, select Reflector-based.
  • Add a TWAMP/TWAMP Light task. Again, enter values for the parameters you want to hard-code as constants into the template. For parameters that should be defined from the orchestrator at runtime, check the Template input box. Below, Senders and Reflector are treated in this way, that is, the Test Agent interfaces and the TWAMP reflector involved in the TWAMP transmissions.

  • When you are done defining the template parameters, click the Save button at the top. The new template will appear in the My Templates section when you start defining a new test.

Setting Up Monitor Templates

Monitors are different from tests in that they execute a single task or a set of parallel tasks indefinitely. Monitors cannot therefore consist of multiple steps. Rather, they are structurally similar to one step of a test.

The monitor template is built accordingly. Since only a subset of task types can execute in parallel, only those task types are available for selection when composing the monitor template. Like test templates, monitor templates offer the Template input option for each parameter.

  • On the left-side bar, click the Monitoring button and select New Monitor:

You are taken to the setup screen for monitors.

  • Click the Create template button.

From here onward, the procedure is similar to building a template for tests, as described in the section Setting Up Test Templates. In the example that follows, we will build an HTTP monitor template.

  • First, name the template, and optionally enter a description of it.

  • In the left-hand column with task categories, select HTTP & DNS.
  • Click the HTTP puzzle piece to add an HTTP task.

  • Enter values for the parameters you want to hard-code as constants into the template.
  • For parameters that you want to leave to be defined from the orchestrator at runtime, check the Template input box. Then, for each parameter, select "Create new" in the Input box and accept the default names. The field Variable name is what is used to refer to the parameter in orchestration. In the screenshot below, Clients and URL are treated in this way.

  • When you are done setting up the template, click the Save button at the top. The new template now appears in the My Templates section when you start defining a new monitor.