ALTERYX INSPIRE | Join us this May for for a multi-day virtual analytics + data science experience like no other! Register Now
The Alteryx Community will be temporarily unavailable for a few hours due to scheduled maintenance starting on Thursday, April 22nd at 5pm MST. Please plan accordingly.

Alteryx Server Knowledge Base

Definitive answers from Server experts.

Alteryx Server: How to enable Engine Logs


How To Enable Engine Logs

Engine logs are useful when troubleshooting Engine related issues. Engine logs contain the output of messages created when a workflow runs, as well as the time stamps when tools run in a workflow.

Procedure for Alteryx Server


  1. Open Alteryx System Settings
  2. Navigate to Engine - General

  1. Under Logging Directory set a directory for Engine logs to be written to. This is empty by default and therefore Engine logs would be disabled.

Please note: In a multi-node environment, the above-mentioned steps will have to be performed for each Worker machine.

Procedure for Alteryx Designer
Engine logs can also be enabled within Alteryx Designer.
  1. Open Alteryx Designer
  2. Go to User settings > Edit user Settings
  3. In the Defaults Tab enable "Override System Settings" and add the path you would like to extract the workflow execution logs.
    1. Press Save.

    Additional Resources  
    8 - Asteroid


    A Workflow log question.  In a multi-node environment, is it a best practice to write Workflow logs to a network drive shared by all the worker nodes?  We just added a new worker node and we have the WF loads writing to the D:\ drive on each server.  Can you advise on what's the best set up?  Also, we scan the logs to alert on Error messages.  Is there a pattern that would pick up critical errors vs say field conversion errors?