This section explains typical project manager tasks that are required for configuring a
Performance Manager monitoring system, including the set up of monitors, rules, conditions, and custom incidents.
Overview
Client monitors, at the most basic level, simulate user actions against online systems and record the effects that those actions have on system health.
Setting up Monitors
Client monitors simulate end-user transactions to mimic real world application usage. Monitors are derived from Silk Performer projects.
GUI-Based Monitoring with Silk Test
This section introduces you to the process of integrating Silk Test GUI-based tests into Performance Manager. Both products are fully integrated and enable you to create Silk Test monitors just like creating Silk Performer monitors.
Configuring Static Boundaries for Performance Values
Using the Boundary Editor, administrators can easily change the thresholds that are used for health calculation and specify which dimension each specific result is to influence.
Project Schedules
Project schedules define when the monitors in a given project are executed.
Custom Monitor Schedules
In addition to having privileges for changing schedules project-wide, project managers can also create custom schedules for individual monitors that override project-wide schedules.
Schedule Exclusions
Exclusions are weekly scheduled periods of monitor down-time.
Definite Runs
A definite run is a specific time at which a monitor will execute, regardless of its usual schedule or any configured exclusions. Multiple definite runs can be scheduled.
Rules
Rules define how errors are raised and the actions that Performance Manager performs when incidents occur.
Custom Incidents
Incidents are automatically raised when predefined conditions are met. Custom incidents are incidents that are detected by users and manually logged into Performance Manager.
