Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!
The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Better Log Structure on Alteryx Designer/Server

In order to make it easier to find workflow logs and be able to analyze them we would suggest some changes:

  • In the log name instead something like "alteryx_log_1634921961_1.log" the log name should be the queue_id for example: "6164518183170000540ac1c5.log"

This would facilitate when trying to find the job logs.

 

 To facilitate reading the log we would suggest the following changes: 

  1. Add the timestamp 
  2. Add error level 

 

For the example of current and suggested log: 

 Please consult the document in attachment.

 

 

In the suggested format the log would be [TIMESTAMP] [ERRORLEVEL] [ELAPSEDTIME] [MESSAGE] 

3 Comments
TheCoffeeDude
11 - Bolide

I thought I was reading a Unix log in the PDF. This would be a great enhancement for readability and integration with log monitors.

CristonS
Alteryx Alumni (Retired)

Again @joanatpsantos, thanks for your thoroughness!

AlteryxCommunityTeam
Alteryx Community Team
Alteryx Community Team
Status changed to: Accepting Votes