...
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 Questback 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%. |
...
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 QuestbackTIVIAN, 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.
|
...
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. |
...
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 Questback Support departmentsupport 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 Questback Support departmentsupport 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.
...
If errors are detected that you dare not fix yourself, please contact Questback Supportsupport.
Optionally, you can have the results e-mailed to you.
...
| Info |
|---|
EFS always retains a backup copy of deleted files. If you wish to restore an accidentally deleted file, please contact QuestBack support. |
ACL rights
...
There are usually a number of staff working in EFS installations, often in larger staff groups.
In addition to the project management, large numbers of additional users are often involved in large survey projects or the administration of panels. There are, for example, users that specialize in questionnaire programming, while other users are responsible for the evaluation of questionnaires.
In collective installations, users from different QuestBack clients work completely separately on their respective projects.
Some users may not be granted access to the admin area. Instead, separate logins such as EFS Survey Status and EFS Translator Interface provide restricted access to the information and functions their work requires.
...
Project manager: The project manager is responsible for conducting survey projects. However, he generally requires no access to panel administration functions and often has no access to staff administration, either.
Panel administrator: In EFS Panel installations, the panel administrator is mainly responsible for panel administration. He may also be in charge of the CMS and the panel community.
System administrator: This role is reserved for support operations by QuestbackTIVIAN. It contains special functions which, if applied incorrectly, can cause damage to the system.
...