Alteryx Promote Ideas

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

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

Submission Guidelines
Don't forget to submit your entry for the Excellence Awards by October 30! | Need more information about the program? Check out the blog here

Save detailed prediction data in Promote

Some customers would like to log all inputs & outputs that go into each model. The goal is to save every JSON request and response with minimal (or no) impact to latency. 

16 - Nebula
16 - Nebula

Hey @RossK


I agree that this would be helpful - and if this could be a switched capability then this would be very useful for testing or logging.


Reason why I mention the switching is that the return from an API can contain client-sensitive data which then will fall foul of data retention requirements such as GDPR so we'd need to turn this off on our prod environments for the responses.


Prediction analytics exists in 18.3+

Status changed to: Implemented

This feature has been implemented as of 2018.3

16 - Nebula
16 - Nebula

Hey @RossK and @DavidCo 


Would you be able to provide more detail about how to enable this - i.e. on a standard workflow, enable full verbose logging of the inputs that go into a predictive tool for each run?

Where would this data be logged - I presume it would be in Mongo - which collection would these inputs be logged in?


Many thanks



Hi Sean,


Thanks for asking, I'm happy to add more detailhere.


As of 2018.3, Promote has implemented both monitoring and prediction logging.


For monitoring, Promote tracks and reports total requests, requests by response code (200, 400, etc), and average latency for the past 28 days. Users are able select varying time windows to see the reporting period of most interest to them. That data is stored on the Promote cluster in an InfluxDB database.



Analytics Tab


For request logging, Promote tracks the inputs and outputs of every request for up to 14 days and offers an interface for searching for specific requests, by Id, time, or response code.



History Tab


In both cases, data can be extracted from Promote using a batch ETL job and stored indefinitely.


Happy to discuss any additional questions you might have!




16 - Nebula
16 - Nebula

🙂 David - that is very encouraging and very helpful.


It would be very useful if some of this technology could be ported across to the server product - since there's a similar situation for regular Alteryx Canvasses (where it would be useful for a canvas in some situations to turn on detailed logging of inputs to an API)


Thank you for taking the time to reply - learned something new and useful today!