PureAgent Web Interface
April 2008
support@minq.se
PureAgent Web Interface
|
|
| PureTest
3.5 April 2008 |
http://www.minq.se support@minq.se |
When you start up PureAgent for the first time, you must use the
user
name admin and password pureagent to log in:
You should change the
password using the Server Admin page as soon as possible to restrict
access.
It is recommended that you look at the license information page when
you start up PureAgent for the first time. If any of the license
constraints have been violated, PureAgent will default to a
demonstration mode with limited capabilities. The license information
can be found under the Server Admin menu selection. Please refer to the
troubleshooting section if you encounter any problems during startup.
The User Interface has a menu at the top where you can access the
different parts:
An activity in PureAgent is the same as a scenario in the Pure Performance
suite, with a unique name, an execution schedule and a specified alarm
level.
In order to design scenarios suitable for PureAgent, you can use the
PureTest tool which
includes utilities such as the HTTP Recorder for rapid scenario
development. Please refer to the PureTest documentation for details
regarding creating a scenario.
Simple activities defined by a single URL can be installed directly
in PureAgent without the use of the PureTest tool to define a scenario.
There are two ways of creating a new Activity in PureAgent:
For example, creating an Activity representing a search in
www.google.com ca be done by using HttpRecorder utility in the PureTest
tool to record a scenario. The scenario is saved to a file
C:/google.plc and can look something like:
Once you have created the activity you can upload it as an activity
in PureAgent. This is done by pressing the Create button on the
Activities page to bring up the Activity Installation form which is
shown in the following figure:
The Activity Name that you
specify must be unique within this instance of PureAgent. The name will
also be used as the identifier when reporting alarms and presenting
result information for this activity.
The Scenario File must be
the path to a valid PureLoad scenario file in your local file system.
As a simple alternative to upload a scenario file the create scenario form contains a part where a scenario defined by a single URL may be created:
The Activity Name that you
specify must be unique within this instance of PureAgent. The name will
also be used as the identifier when reporting alarms and presenting
result information for this activity.
The URL must be a valid url
to a page to access.
After an activity has been created, you will be directed to the
Activity Settings page where you can specify time interval and alarm
levels for the activity. The Activity Settings page can be seen in the
following figure:
The schedule Interval is
the time in seconds between activity executions. If the interval is set
to less than the actual execution time of an activity, it will be
executed again and again at the fastest possible rate. The default
value is 300 seconds (five minutes).
Maximum time is the alarm
level. If the activity execution time exceeds this level it will be
considered to have violated the alarm level and an alarm may be
generated depending on how many violations that are allowed (see
below). A negative alarm level (<0) is used to indicate that the
execution times should not be compared to any level, which is also the
default value.
Grace Count specifies the
number of consecutive times the alarm level is allowed to be violated
before an alarm is generated. For example, if the grace count is set to
2 and the alarm level was violated during the last execution, violating
the level again next time will cause an alarm to be generated whereas a
successful execution below the level would clear the grace counter.
This mechanism can prevent unwanted alarms if you have a monitored
system that is expected and allowed to have temporary peaks.
Persistent Count is then
umber of consecutive times an alarm is sent before the activity is
considered to be in a state of persistent failure. When this state has
been reached there will be no more alarms sent until the activity
detects successful behavior again. The same count is used to determine
that the failure has ceased. Example: Persistent Count is set to 2. The
activity generates an alarm two times in a row. The second alarm that
is sent will then inform that there is a persistent failure. The
activity will now keep on running, but the failures are not reported as
alarms. When the activity has been successful two times in a row, an
alarm will be sent that informs that the failure has ceased.
Alarm Recipients shows a list of defined recipients. Select the
recipients that should receive alarms from this activity. Managing
alarm recipients is described in the Alarms chapter.
Once you have set the properties after creation of an activity you
are redirected to a page showing a list of installed activities. This
page can be seen as the main page of PureAgent:
The list consist of the following columns:
The different status columns:
- last execution resulted in a alarm
(non persistent), and
- last execution resulted in a alarm
(persistent).
- last execution succeed, and
- lLast execution failed.To view the Activity Report for an activity, select the activity in
the ativity list. The Activity Report allows you to change settings for
the activity as well as see various reports for the activity.
The various views are:
As activities are executed PureAgent will store the results
persistently. The result history page can be reached in three ways:
The following figure shows the viewing of history for two activities simultaneously:
The Interval end fields represents the end date and time of the
displayed graphs and statistics. The left pair of input fields
represents the start date end time of the interval.
Changing these values and pressing the refresh icon will update the
page to show the graphs and statistics for the selected interval.
The combination of zoom and zoom selection controls the zooming that
is performed when clicking in image graph.
Note: Displayed graphs are
always shown using a fixed number of displayed points. This means that
a single point in a graph represents a calculated average for all the
measurements performed during the interval of the point and the
previous point. This also implies that the ok counter in the activity
statistics part may show a higher value than the visible number of
points in the graph for the activity.
Zooming in the graph will eventually make the graph show a single
point for every performed measurement.
This part displays different statistics for the chosen activities.
All values is shown for the displayed interval.
Note: Counter may not correspond to the shown number of points in
the
graphs. See the Note in the previous section about zoom and zoom
selection.
Aside from storing results persistently when running activities
PureAgent will keep information about the last execution details
available for viewing. The is information is in a more detailed format
and contains timing information for all tasks and task sequences
included in the activity.
To see the last execution result, select the link in the Activity
Report page:
The figure above shows metrics about the last successful execution
of the activity named 'Google Search'. In case of the last execution
was a failure some additional metrics is shown.
The first part (Execution Result) describes the status of the last
execution. In this case the execution was successful. For successful
executions and for some failure cases the page also shows statistics
for individual Tasks included in the activity.
Note that if several Tasks are given the same name under the same
level the average time indeed indicates an average. If the Task is a
single Task the average time is actually the exact execution time for
the Task.
In order to receive alarms when failures are detected in a monitored
system, one or more Alarm Recipients must be created as described in
this section.
The Alarm Recipients page shows an overview of the defined
recipients as shown in the figure below:
Clicking on a name will bring up a configuration form where the
details can be changed. Press the Remove button to remove a recipient
that is no longer needed.
An Alarm Recipient is created by pressing the create button on the Alarm Recipients page. This brings up the following form:
Here you specify the name, e-mail and phone of the new alarm
recipient. You may also select which activities that this recipient
should receive alarms for. If no activities have been installed it will
simply say 'N/A'.
When the execution of an activity fails, or the execution time of the activity exceeds the maximum time setting for the activity, an alarm is generated.
Alarms that are generated are stored in a back-log that can be
viewed by pressing the Alarms menu selection. The alarm back log shows
alarms generated since the PureAgent was started. The number of entries
in the backlog is limited.
The alarm are also logged in a file located at <install_home>/log/alarm.log
An example alarm back-log is shown below:
The table shows the time when the alarm occurred, which activity it originated from and the alarm message. The messages are shown in different colors depending on the type of alarm: yellow for execution time exceeding the alarm level, orange for failures, red for failures considered persistent and green when failures cease to be persistent.
Alarms may be forwarded using different modules. One such module is
the mail alarm module which sends alarms using standard Internet mail.
Enabling forwarding of alarms is done by setting up Alarm recipients
(see Creating an Alarm Recipient).
PureAgent will report alarms to the set of installed alarm modules.
See Agent Configuration for
details.
Server Admin allows you to view license information, change password
and shutdown the agent:
Shutting down PureAgent should be done in a controlled way in order
to ensure the integrity of the persistent storage. A controlled
shutdown is done by selecting Shutdown PureAgent under the Server Admin
menu selection. This will prompt you again to make sure that you do
indeed want to shutdown. After bringing down PureAgent, the web server
will exit and you must use the launcher as described above to bring
PureAgent up again.
In the case of an uncontrolled shutdown due to power failure or other
reasons, there should in most cases be no problem.