Central logging tooling

[SeanAdams]

It would be helpful to have a central Logging tool for large & complex environments.

This would be useful to allow teams to have a central way of logging data transformation errors by error-type; severity; alteryx Canvas; etc.

Right now, there's a message tool, but this doesn't provide a way to create well structured central logging across a team; especially once deployed to a server environment.

CC: @rijuthav @jithinmony @HengHe @RajK @ydmuley @revathi @Deeksha @MPistone @Ari_Fuller @Arianna_Fuller @JoshKushner @samnelson @avinashbonu @Sunder_Sriram @Rahul_Thakur @Rahul_Singh

[Deeksha]

@SeanAdams Would really  help  identify   "real issues"  e.g.   some exceptions   may show an error in execution still  generate the expected output file - categorization of error type and severity  would help   in debugging and identifying any potential patterns in  issue types.

[adrianloong]

+1 total agree on this one. A lot of requests from IT and business teams to log/monitor this

[fharper]

I posted info on capturing the output log.  I think you will find it useful

https://community.alteryx.com/t5/Setup-Configuration/Log-File-Location-and-Variables/m-p/80884/highl...

[fharper]

Basically once you capture the log data you can parse and transform the content into any form that is meaningful to you and do analysis on it.

[KylieF]

Thank you for your post! We are really interested in this idea, however we cannot fit an idea of this undertaking on the near future road map. We would keep this idea in mind however for when making future large scale choices for the product and update the status once we’re better able to speak on when and if we can implement it.