The Qlik Sense Engine Service (QES) is the application service that handles all application calculations and logic.
The Engines overview lists all the available engines. The following table presents the available fields and buttons. By default, only some of the fields are displayed. You can use the column selector (
) to add fields.
| Property | Description |
|---|---|
| Node | The name of the engine node. |
| Status |
One of the following statuses is displayed:
Tip noteClick
 in the Status column for more detailed information on the status. |
| Tags | The tags that are connected to the engine. |
| App autosave interval (seconds) | The number of seconds between autosaving of the apps. Autosave is always performed when a session ends. Everything except data is saved. To persist data, perform a reload in Data load editor. |
| App cache time (seconds) | The number of seconds that a Qlik Sense app is allowed to remain in memory, after the last session that used the app has ended. |
| Working folder | A scheduled reload will search for files in this directory when relative paths are used to define file location. Information noteThis setting is used to support legacy features in QlikView scripts for relative paths to files during reload. You cannot use this setting to change the directory where the apps are stored. |
| Max number of undos | The maximum number of undos when editing app content, such as sheets, objects, bookmarks, and stories: min = 0, max = 999. |
| Performance log interval (minutes) | The number of minutes in-between performance logging entries. |
| Audit activity log level |
Levels: Off or Basic (a limited set of entries) |
| Service log level |
Each level from Error to Info includes more information than the previous level. |
| System log level |
All the standard engine messages are saved to this logger. Each level from Fatal to Debug includes more information than the previous level. |
| Performance log level | All the performance messages are saved to this logger ( by default updated default every five minutes). The log contains, for example, the number of active users, the number of open sessions, and the CPU load.Each level from Fatal to Debug includes more information than the previous level. |
| QIX performance log level |
All the QIX protocol performance messages are saved to this logger. Each level from Fatal to Debug includes more information than the previous level. |
| Audit log level | More detailed, user-based messages are saved to this logger, for example, when the user makes a selection in an app. Each level from Fatal to Debug includes more information than the previous level. |
| Session log level | All the session messages are saved to this logger when a client session is terminated, for example, user information, machine ID, IP address and port number.Each level from Fatal to Debug includes more information than the previous level. |
| Traffic log level | All the traffic messages are saved to this logger, for example, all JSON-messages to and from the engine.Each level from Fatal to Debug includes more information than the previous level. |
| Analytic connections log level | All the analytic connections messages are saved to this logger. Each level from Fatal to Debug includes more information than the previous level. |
| Allow data lineage | Status values: Yes or No. The data lineage is the origin of the data that is loaded into Qlik Sense). |
| Min memory usage (%) | The minimum memory capacity used by Qlik Sense. |
| Max memory usage (%) | The maximum memory capacity used by Qlik Sense. |
| CPU throttle (%) | The amount of CPU capacity used by Qlik Sense. Range: 0 - 100% |
| Standard mode |
Status values: Yes: standard mode. No: legacy mode. For security reasons, Qlik Sense in standard mode does not support absolute or relative paths in the data load script or functions and variables that expose the file system. Warning noteDisabling standard mode can create a security risk by exposing the file system.
|
| HTTP callback port |
The callback port used by the Qlik Sense Repository Service for sending HTTP events to engine. |
| Hypercube memory limit (bytes) |
Limit for how much memory a hypercube evaluation can allocate during a request. If multiple hypercubes are calculated during the request, the limit is applied to each hypercube calculation separately . Note that the limit is not enforced on every allocation. If the setting has the value 0, the engine applies a global heuristic to limit the amount of simultaneously executing requests that allocate a lot of memory to calculations. A negative value disables the limit. For performance reasons, memory usage and limits are checked periodically rather than on every allocation, therefore it is possible to briefly exceed the limit in some cases. |
| Reload memory limit (bytes) |
Limit for how much memory a reload request can allocate. A negative value or 0 disables the limit. For performance reasons, memory usage and limits are checked periodically rather than on every allocation, therefore it is possible to briefly exceed the limit in some cases. |
|
Export memory limit (bytes) |
Limit for how much memory the export part of an export data request can allocate. Allocations made due to calculations are not counted against this limit. A negative value or 0 disables the limit. For performance reasons, memory usage and limits are checked periodically rather than on every allocation, therefore it is possible to briefly exceed the limit in some cases. |
| Hypercube time limit (seconds) |
Limits the single core CPU time equivalent that a hypercube calculation can use. The single core CPU time equivalent is a heuristic that approximates the CPU time spent, divided by the number of cores used during the calculation. This is not a hard limit and it is dependent on the complexity of processed calculation. A negative value or 0 disables the limit. For performance reasons, the CPU time is not tracked exactly. |
| Export time limit (seconds) |
Limits the CPU time that the export part of an export data request can use. A negative value or 0 disables the limit. |
| Reload time limit (seconds) |
Limits the CPU time that a reload request can use. A negative value or 0 disables the limit. |
| Create search index during reload |
Status values: Yes or No. When selected, all apps on the server are indexed during reload so that performance during the first search session is improved. |
| ID | The ID of the engine. |
| Created | The date and time when the engine was created. |
| Last modified | The date and time when the engine was last modified. |
| Modified by | By whom the engine was modified. |
| <Custom properties> | Custom properties, if any, are listed here. |
|
Sort the list ascending or descending. Some columns do not support sorting. |
|
Type a string to filter on, or, when available, select a predefined value. All rows that match your filter criteria are displayed. You can filter on multiple columns simultaneously to narrow your search. If a filter is applied to a column, To remove your criteria, click Actions in the table header bar and select Clear filters and search. You can combine filtering with searching. |
| Actions |
Options for clearing filter and search, selecting and deselecting all rows, and toggling wrapping. Information noteThe option Select all rows is applied to the rows that are currently displayed. Any rows that have been filtered out before selecting all rows are disregarded, even if they were selected. The option Deselect all rows is applied to all rows, including those that were filtered out.
|
|
|
Column selector: Select which columns to display in the overview. Click  to reset to the default columns. |
|
Search – both basic and more advanced searches. |
|
Refresh the page. |
| Edit | Edit the selected engines. |
| Show more | The overview shows a set number of items, by default. To show more items, scroll to the end of the list and click Show more. Searching, sorting, and filtering of items is always done on the full database list of items, not only the items that are displayed. |