Now allowing extractions without measure selections in MDX mode. Selections can now be parameterized with lists of strings
L - Low: Install only if advised by the support team. M - Medium: Install within your usual update interval. defines the recommended priority for updating:. C is incremented when a bug is fixed, or a small feature is added, modified, or removed. B is incremented when an important feature is added, modified, or removed. Additional steps might be necessary when upgrading to this version. If there is at least one newer release available with medium or high update priority, please download the latest version from the customer portal and deploy it to your test environment. We recommend to check for updates at least every three months. Scan for events after the error occurred to identify potential consequences.See the Xtract Kernel Version History for changes related to core extraction logic. Scan for events before the error occurred to identify potential causes. Starting from the error, locate the point in the log where Server started ("AlteryxService starting"). Search log entries for words such as Error, Alert, and Critical. Locate and open the log in a text editor or Microsoft Excel. There are several steps you can take to investigate logs and diagnose issues in Server. Service and Gallery logs are most-commonly used for investigating issues. You can specify a location to store engine log files on the System Settings > Engine > General page in the Logging Directory. Configure Engine LoggingĮngine logs are not stored by default. Customize the location, if necessary, on the System Settings > Gallery > General page. The storage location for Gallery log files is set to C:\ProgramData\Alteryx\Gallery\Logs by default. This prevents the creation of large log files that are difficult to consume in standard log readers. Select Enable log file rotation to place log files that exceed the max size in an archive file. 
Specify the maximum File size in MB for log files. Normal: Log low, warning, and notice messages. 
Low: Only log emergency, alert, critical, and error messages.You can increase the log level when debugging aberrant Server behavior. This minimizes disk write operations and input/output contention. We recommend setting the log level to Low or None.
0 kommentar(er)
