| Live Search | ||||
|---|---|---|---|---|
|
...
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 Questback 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 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. |
...
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. |
...
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. |
...
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 Questback Support department. |
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 department. |
...
Read rights for platform_cockpit are required to view and open the Options → Platform cockpit menu.
...
Interview check
The check mechanisms on the Installation check tab allow you to check the data consistency in your installation.
If errors are detected that you dare not fix yourself, please contact Questback Support.
Optionally, you can have the results e-mailed to you.
...
You can use the Interview check tab to examine how many interviews your organization has conducted. The following analyzes can be carried out with the statistics tool:
Interview numbers for specific projects
Interview numbers from a certain period
Interview numbers for disposition codes > 30 in detail
The following rules apply to the calculation:
All interviews are charged with disposition codes > 30 (31, 32, 35, 36, 37, 41).
If you reset a participant and he participates again, this is counted as two interviews.
If the external survey start is used and the start and target project are both EFS projects, the interviews are counted twice: The participants reach the end page in both projects.
Interviews that were uploaded via data import are not counted.
Installation check
The check mechanisms on the Installation check tab allow you to check the data consistency in your installation.
If errors are detected that you dare not fix yourself, please contact Questback Support.
Optionally, you can have the results e-mailed to you.
| Info |
|---|
Please keep in mind that the running of installation checks may affect your installation’s performance. Especially in the case of large installations, these checks should therefore be run during weak-load periods, if possible. |
...
The Options → System settings menu is only accessible to members of the administrator team or the system administrator team.
Mail queue
Konfiguration der Keine-Mails Liste
Navigieren Sie zur Keine-Mails Liste über folgenden PfadDo-Not-Email list
Navigate to the Do-not-Email list using the following path:
System → OptionenOptions → Mail -Admin → Keine-Mails Liste
...
queue → Do-not-Email list
General and project-based Do-Not-Email lists are managed here. To add emails to the blacklist, download the import template (Import → Download import template), add the email list to the rctp column and use pid 0 to create a general blacklist or a specific pid to create a project based blacklist. The efs.mailblacklist.add, efsmailblacklist.delete, efsmailblacklist.get-List, efsmailblacklist.isBlacklisted können dazu verwendet werden, die Verwaltung von Sperrlisten zu automatisieren. Wenn neue E-Mails aus EFS heraus verschickt werden, dann werden die Adressen aus der Keine-Mails Liste automatisch aus der Liste der
Empfänger entfernt. EMails, die bereits in der Warteschlange abgelegt waren, werden als „abgebrochen“ markiert.
Teilnehmer, deren E-Mail-Adressen auf der Keine-Mails Liste stehen, können trotzdem an der Befragung teilnehmen.
Um Self-Service-Sperrlisten in die E-Mail-Templates zu implementieren („unsubscribe“ Funktionsweise), fügen Sie #unsubscribe_survey# oder #unsubscribe_global# Ihrem E-Mail-Template hinzu.
...
#unsubscribe_survey# generiert einen Sperrlistenlink für das aktuelle EFS-Projekt.
...
web services can be used to automate the management of blacklists. When new e-mails are sent from EFS, the addresses from the Do-Not-Email list are automatically removed from the list of recipients. Emails that have already been placed in the queue are marked as "canceled".
Participants whose e-mail addresses are on the Do-not-Email list can still take part in the survey.
To implement self-service blacklists in the e-mail templates (“unsubscribe” functionality), add #unsubscribe_survey# or #unsubscribe_global# to your e-mail template.
#unsubscribe_survey# generates a blacklist link for the current EFS project.
#unsubscribe_global# generates a global blacklist link.
SMS admin
On installations with the SMS module enabled, you‘ll find SMS Report under Options → SMS admin. This functionality gives you a detailed list of all SMS sent by EFS to the provider along with the initial response received from the SMS provider.
...