...
The Cockpit tab gives an overview of the key data for the installation.
...
Section | Meaning |
|---|---|
Current front end load | The current load on the front end server. For multi-core servers, the load per core is indicated (indicated load value = measured load / number of cores). On a server with up-to-date hardware, the load should be below 3. |
Front end | The name of the front end server. |
Date of last mail dispatch | E-mails posted for dispatch will not be immediately retrieved and sent, but automatically at 10-minute intervals. |
Date of last database maintenance | Time and frequence of the database maintenance are configured by our support for the specific installation. |
EFS version | The major and minor EFS versions which are currently installed. |
Initial EFS version | The EFS version which was originally used when setting up the installation. |
Name of installation | The domain at which you will find the EFS installation on the Internet. |
Database name | The name of the database. |
MySQL query cache effectivity | The results of requests sent to the database by a participant during the completion of the questionnaire will be cached to the so-called query cache. If a request has already been executed by the database once (e.g. a request about a question text), it will not be executed again the second time. Instead the cached result will be delivered. This use of the cache brings significant advantages in terms of speed. The specified effectivity value indicates how often a cached result has been delivered. It is calculated from the number of requests executed by the database / number of requests answered from the cache. Thus, a value of 100% indicates that each request has also been retrieved from the cache once. Usually, values are above 100%. |
Database report
On the Database report tab, you will find general information on the state of the database as well as on completed and scheduled maintenance operations.
Database report of the previous day
Section | Meaning |
|---|---|
Number of tables | The total number of database tables in the EFSinstallation. |
Number of projects | The total number of projects in the EFS installation. |
Size of sample_data | The “sample_data” table holds all sample data drawn in the installation. This means that the table includes both the data of all respondents who are authorized to participate in personalized surveys and the data of all respondents who have participated in anonymous surveys. |
Number of started interviews (yesterday) | The number of interviews started on the previous day. |
Number of finished interviews | The number of interviews finished on the previous day. |
Participants denied access (load limit) | Number of participants denied access due to the load limit being exceeded |
Participants denied access (participant limit) | Number of participants denied access due to maximum permissible number of participants being exceeded for the entire installation. |
Watchdog mean (yesterday) | The mean execution time for loading a questionnaire page on the previous day. |
Number of delivered pages (yesterday) | The number of questionnaire pages delivered to survey participants on the previous day. |
Admin_log mean (yesterday) | The mean execution time for loading a page in the installation’s admin area on the previous day. |
Number of delivered admin pages (yesterday) | The number of pages in the installation’s admin area that was delivered to users on the previous day. |
Database maintenance
Section | Meaning |
|---|---|
Number of deleted and backed-up watchdog entries | If entries archived in watchdog are deleted after the specified deadline has expired, this is displayed here. If the installation is hosted at TIVIAN, deleted entries will automatically be backed up. |
Addresses for sendingthe status report on automatic database maintenance | If you wish to continuously monitor the status of your installation, you can subscribe to a database report that will be e-mailed on a daily basis:
|
Maximum number of days to retain log | In the text fields, you can set for how long the data displayed in the OSPE watchdog, in the login log and admin log are to be archived. For performance reasons, the archiving duration you can set for the Watchdog is limited to a maximum of 30 days. |
The tables listed here will be automatically optimized... | The tables in the list are optimized automatically during low traffic times.
|
Login Log
The archived login data informs you on which user logged in when, including rejected login attempts. If you click on the column titles of the table, the information will be sorted by the respective column. This makes it easier to search for, e.g., a specific user.
Search
Field | Meaning |
|---|---|
Date from ... to | In this area, you can specify which period of time you wish to search. Clicking on the Calendar icon to the right of the date will open a dialog containing a calendar, and clicking on the Cancel icon will delete all entries. |
Account | In the text field, you can enter the user account whose logins you want to search for. |
Access | In the drop-down list, you can set which accesses are to be displayed: all accesses, only accesses granted or only accesses denied. |
Number of rows per page | In this field, you can increase or reduce the number of records that will be displayed on one page of the login log. |
Login
Column title | Meaning |
|---|---|
Account | The user account |
IP address | The IP address from which the staff member logged in. Please note: Certain network constellations may allow only restricted determination and storage of hostnames and IP addresses. |
Access | This field indicates whether access was granted or denied. |
Error message | If the access was denied, the corresponding rejection message from the system will be displayed in this field. |
Date | The date and time of the login attempt. |
Functions | Detailed view of the respective entry with all identification data including request parameters. |
Admin Log
The Admin log tab not only provides a detailed log of the actions executed by users in the system, but also allows an insight into the performance in the installation’s admin area. Similar to the login log, you can click on a column title in the “Matching log entries” area to sort the entries by the respective column. This function makes it easier to search, e.g. for actions in a specific module. If you click on the icon in the “Functions” column, you can also display a detail view of the respective entry with all identification data, including request parameters.
Search for log entries
Field | Meaning |
|---|---|
Log date from... to Execution time from... to | In this area, you can specify exactly which period of time you wish to search. |
Account | In the text field, you can enter the user account whose log entries you want to search for. |
Module name | If you only want to observe the actions in a specific module, enter the module name in this field. |
Action | If you want to view the existing logs for a specific action, enter the name of the action in this field. |
Request parameters | The request parameters characterize a certain action of a specific user in a user session. |
Matching log entries
Column title | Meaning |
|---|---|
Entry ID | Every single action executed in the installation receives an entry ID by which it can be uniquely identified. |
Account | The account of the respective user. |
Log date | The date and time of the log entry. |
Module name | The name of the module in which the action was executed. |
Action | The name of the executed action. |
Execution time | The time needed to execute the respective action. |
Functions | A detail view of the respective entry with all identification data, including request parameters. |
OSPE Watchdog
The OSPE watchdog tab provides details on overall system performance as well as on the performance of each project and each questionnaire page.
Restricting performance data
Field | Meaning |
|---|---|
Start date; End date | In this area, you can specify exactly over which time interval you want to calculate the performance data. Clicking on the Calendar icon to the right of the date will open a dialog containing a calendar. Please note that the time interval over which you can request evaluations must not include more than seven days for performance reasons. Furthermore, the permissible evaluation period is limited by the maximum period for which data can remain in watchdog, which is limited to a maximum of 30 days. You can change the archiving deadline in the “Maximum of days in watchdog” field on the Database report tab. However, the maximum of 30 days cannot be exceeded. |
Overall performance
Overall performance | Meaning |
|---|---|
Current front end load | The current load on the front end server, divided by the number of available cores. |
# Requests | The total number of questionnaire requests in the specified period. |
Ø Front end load | The average front end server load in the specified period. |
Ø Exec. time | The average overall execution time for building and delivering a questionnaire page for all projects in the specified period. (Overall execution time - DB time - PHP incl. time - Memcache time = time needed by PHP for other processes.) |
Max. exec. time | The highest overall execution time registered in the specified period. |
Median | The median of the overall execution time in the specified period. |
Std. dev. | The standard deviation of the overall execution time in the specified period. |
Ø DB time | The average time needed for all queries on the questionnaire page to-bebuilt |
Ø PHP incl. time | The average time needed for loading the EFS PHP code via the EFS autoloader. Smarty templates are not loaded via the autoloader and are therefore not included. |
Ø Memcache time | The average time needed for read and write memcache requests. |
Participants denied access (load limit) | Number of participants denied access due to the load limit being exceeded per installation, project and questionnaire page. |
Participants denied access (participant limit) | Number of participants denied access due to maximum number of participants being exceeded per installation, project and questionnaire page. |
Actions | By clicking on the envelope icon, you can send an e-mail to the support team. |
Performance by project
Column | Meaning |
|---|---|
Project | The project whose average performance values are described in the respective row. By clicking on the project title, you can display a detail view of the individual pages in the project. |
# Requests | The number of requests to questionnaire pages of the respective project |
Ø Front end load | The average server front end load during execution of the respective project. |
Ø Exec. time | The average overall execution time for building and delivering a questionnaire page in the project and in the period specified. Sum of the average values for “DB time”, “PHP incl. time” and “Memcache time”. |
Max. exec. time | The highest overall execution time registered in the project and the period specified. |
Median | The median of the execution time for this project in the specified period. |
Std. dev. | The standard deviation of the execution time for this project in the specified period. |
Ø DB time | The average time needed for all queries on the questionnaire page to-bebuilt in the project specified. |
Ø PHP incl. time | The average time needed for loading the EFS PHP code via the EFS autoloader in the project specified. Smarty templates are not loaded via the autoloader and are therefore not included. |
Ø Memcache time | The average time needed for read and write memcache requests in the project specified. |
Actions | By clicking on the envelope icon, you can send an e-mail to the support team. |
You can check the performance of the individual questionnaire pages of your project by clicking on a certain project in the “Performance by project” area.
...
The Options → System settings menu is only accessible to members of the administrator team or the system administrator team.
Mail queue
Mail Report
System → Options → Mail queue leads you to the global Mail Report, where you can find information on all installation-wide mail processes. For more details on the topic “Mail report”, click here.
Do-Not-Email list
Navigate to the Do-not-Email list using the following path:
...
The following table explains the contents of the overview list in detail:
Column heading | Meaning |
|---|---|
Date | Date when file was stored on server |
Title | User-defined file identification within the exchange platform |
Comment | Explanatory comment |
File name | Actual file identification, such as example.doc. |
Size | File size. If the file is smaller than 1.024 KB, the size is stated in kilobytes, otherwise in megabytes. If the file is smaller than 1.024 bytes, the size is stated in bytes. |
Author | The staff member who uploaded the file. |
Security | If a password has been set when uploading the file, this field contains an input field where you have to enter the password before downloading the file. |
Status | Indication of status. Possible values: “Active”, “Obsolete”, “Locked”. |
Team name | Name of staff team possessing full rights to the file. |
Uploading a new file
You may upload files of any format, except for PHP and HTML. The maximum possible file size of the respective installation is displayed in the import dialog. Please note that the name of the file you want to upload has to be unique; i.e. if test.doc already exists, you cannot upload a second file named test.doc.
...
If the uploaded files are frequently revised and replaced with new versions, assigning a file status will help you keep track. There are three possible file statuses to describe the degree of currentness and accessibility of a file: “Active”, “Obsolete”, “Locked”.
File statuses
Status | Meaning |
|---|---|
Active | The file is up-to-date and may be downloaded by every team member. Its status may be changed by members holding special rights and by the author of this file. |
Obsolete | The file is no longer up-to-date but may still be downloaded by every team member. Its status may be changed by members holding special rights and by the author of this file. |
Locked | The file has been locked. The file cannot be downloaded until the status has been changed to “Active” or “Obsolete” by the user who initiated the lock. |
In order to change the status of a file, proceed as follows:
...