EASA contains several tools for monitoring the usage of an EASA system.

These tools will allow an Administrator to keep track of the following:

• All failed login attempts, including IP logging
• User submissions of runs
• EASAP run times
• Delay times waiting for an available Compute Server or an application software license
• Amount of disk space an EASA Server uses
• Status of the EASAP run queue

This page provides feedback on the state of Compute Servers, Excel Servers and EASA Server Disk Space.

A comma-separated list of email addresses may be supplied such that if a Compute Server or Excel Server goes inactive, or if the disk space goes below a preset amount, then these people are notified.

Configure email capability in Administrator-mode via: EASA > Configure > Email

The tests are done every 10 minutes. On the disk space check, an email will only be sent if the system goes from having 2*minimum disk space to below minimum disk space. This is to avoid too many emails being sent if the disk space usage is hovering around the minimum.

'Log4j' provides this same info via: <EASAROOT>/webapps/easa/WEB-INF/classes/log4j.properties (category - backend.EventNotification)

The log4j.properties may be modified to send the information to other locations.

Failed log in attempts and other events are monitored and logged in Administrator-mode at: EASA > System > Security Log

There are three types of failed attempts that will be recorded and displayed:

• Incorrect password entered
• Unrecognized user name
• Single or multiple login attempts from another client computer

Other logged events include:

• Added or deleted users
• Added or deleted privileges (Author or Administrator)
• Changed user's details (name, email or phone)
• Change user's password

For each failed attempt, a row will be displayed in the table showing the time and date of the attempt, the User ID used during the attempt, and a message pointing towards one of the three issues listed above. The message for all failed login attempt issues will also display the IP address of the computer used in the attempt.

The data in the 'Security Log' is found in: <SERVERDATA>/admin/logs/security.txt

This file contains comma-separated data values (CSV) and therefore is suitable for importing into spreadsheet tools for further analysis.

Check the history of license availability in Administrator-mode via: EASA > System > Availability

For each failed attempt, a row is placed in the table showing the time and date of the attempt and the user ID used in the attempt.

The data on the Availability page is found in: <SERVERDATA>/admin/logs folder/availability.txt

This file contains comma-separated data values and therefore is suitable for importing into spreadsheet tools, such as Microsoft Excel, for further analysis.

To view EASAP use statistics, in Administrator-mode select: EASA > System > Activity

The table provides monthly information since EASA was installed, each row provides:

• A User ID for each submitted EASAP run during the month
• Each EASAP that has been submitted to run during the month
• Number of submissions and runs performed during the month
• Total EASAP run time accumulated during the month

By using the two search fields, filters for for Users and for Applications may distill EASAP usage information down to specific user IDs and/or specific EASAPs. Once filtered, the submissions, runs and run time information corresponds to just the Users and Applications currently displayed in the table. See the figure below for an example of the Activity page.

A submission is recorded every time a user clicks on the 'Submit' EASAP button on an EASAP, while a run is recorded only if it runs to 'Completion'. Also, submissions of parametric and optimization studies may produce multiple runs per submission.

Data at 'EASA > System > Activity' is stored in two text files:

• <SERVERDATA>/admin/logs
  submitted_runs.txt
  runs.txt

These files contain comma-separated data values and therefore is suitable for importing into spreadsheet tools, such as Microsoft Excel, for further analysis.

The default User session timeout is 120 minutes.

• To change this, open: <EASAROOT>\webapps\jsf-easa\WEB-INF\web.xml

• Modify the following property:
  <session-config>
  <session-timeout> 120 </session-timeout>
  </session-config>

To view the efficiency with EASAP runs, select: EASA > Administrator > System > Efficiency

A table listing all the EASAPs currently published in the Application Library will appear.

This table contains statistics for each published EASAP:

• Average wait time for an available Compute Server in seconds for an EASAP run
• Average wait time for an available application software license in seconds for an EASAP run
• Average overall turnaround time in seconds for an EASAP run

When wait times for either compute servers or licenses become a large portion of the overall turnaround times, it may be worth considering making more Compute Servers or licenses available, whichever is needed.

To see current disk usagein Administrator-mode, select: EASA > System > Disk Space

A table shows per-User disk usage. An aggregate total for both Authors and Users is provided above the table. Add these two numbers to find the total disk space being used by the EASA system beyond the initial 100 MB or so taken up during installation.

A User may reduce disk footprint by deleting unwanted entries in: EASA > Results

An Author may reduce disk space usage by deleting results from testing runs and deleting old, unneeded versions of EASAPs. An Author also has some control over how much disk space an EASAP run will use when finished.

Remind Authors to use CLEAR FILSPACE to help keep the use of disk space to a reasonable level.

To view and manage the use of software and computer resources by User's EASAP runs select: EASA > Administrator > System > Queue

A table listing all current EASAP runs present within the EASAP queue will appear showing a information each run and its status in the queue.

Administrator-mode allows may 'stop' or 'change priority' control of a running EASAP via: EASA > System > Queue

• Stop an EASAP run by clicking: Stop EASAP ()

• Change an EASAP run’s place in the queue by clicking: Change Priority ()
  Click on the 'Highest' button to elevate the run to top of the queue
  Click 'Lowest' button to drop the run to the bottom of the queue