Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesHello all,
This may be a little controversial. As of today, when you buy an Alteryx Server, the basic package covers up to 4 cores :
https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/How-Alteryx-defines-cores-for-licensing-our-products/ta-p/158030
I have always known that. But these last years, the technology, the world has evolved. Especially the number of cores in a server. As an example, AMD Epyc CPU for server begin at 8 cores :
https://www.amd.com/en/processors/epyc-7002-series
So the idea is to update the number of cores in initial package for 8 or even 16 cores. It would :
-make Alteryx more competitive
-cost only very few money
-end some user frustration
Moreover, Alteryx Server Additional Capacity license should be 4 cores.
Best regards,
Simon
Alteryx Server does a pretty good job of tracking all the information you need in order to find out who ran a workflow at a given time, even if that workflow has been deleted from the Gallery.
However, if I need to identify what that workflow actually did on a specific date, and that version is no longer available on the Gallery, it gets really hard to track down.
There are some posts throughout the community on leveraging the MongoDB to try and reconstruct this, but in some cases the workflow is "Chunked" and becomes impossible for an end user to reconstruct.
I spoke to support about this recently and they suggested that by using the Scheduler, I could schedule the historical instance of the workflow and then "Really quickly" grab it when it was reconstructed from the temporary staging folder used by our Alteryx Server. This has a few concerns, among them, finding a way to run this workflow so that the files can be created but it has no impact on tables, for instance if the given workflow drops a table as part of its execution. Additionally, the only way to schedule with a different set of permissions in a 1-Worker environment is to change the default "Run Workflows As" to a different user, who also needs permission to access all files on the Alteryx Server. This can also impact any other Scheduled or Gallery job that is executed while this recovery is underway, effectively causing downtime to do file recovery.
These restrictions are specific enough as to be impractical for most organizations using Alteryx Gallery/Server.
I think this could be solved by adding to the Scheduler an option along the lines of "Download a copy of the workflow", available to administrators. Ideally this copy could include some important metadata, like when that version of the workflow was uploaded, who uploaded it, and its ID/Version Number from the Gallery.
This would go a long way towards making it easier to Audit and respond to requests for historical information about Alteryx Workflows on the Server, and since the Alteryx Engine can already recreate these workflows, I think that a basic version of this feature could simply save out that temporary file, rather than executing it.
Use Cases:
Currently, we use Task Manager to control Alteryx Service (or command line). An administrative function within Alteryx should support graceful stopping and starting of the service as user jobs are interrupted (or can be) by our activities. While I currently post messages to users alerting them to admin activities, I am asked why Tableau can restart jobs (admin) and we can't. Other admins have asked what is "hanging" alteryx service up for a STOP command. I have explained that all jobs must be stopped in order for a quick restart of the service.
We're using a single server today (this client) and plan to add workers to the configuration. It would be helpful to know where work is running and be able to use admin functions across the servers.
Cheers,
Mark
The job timeout function is a perinate issue on the the Alteryx server because scheduling workflows on the server that overlap with another workflow can cause bottleneck issues. Depending on the number of workers and the other workflows, the workflow in question could fail to run or not complete running at the desired date and time. I recommend a view option of the Schedule Forecast feature for all users, so as to allow all users to effectively schedule workflows on the Alteryx server that do no conflict with other workflows.
From a security standpoint, it is important that all users are authenticated when accesing the Gallery on Alteryx Server and using local accounts. There shgould be an option available to force user to the login page rather than the public Gallery. Users going to the Alteryx server URL should be presented with the login page by default before being taken to the Gallery, rather than seeing the public Gallery and needing to click Sign-in in the upper right corner.
We spent almost a full day on Friday internally, and also about 3 or 4 hours of time for 3 Alteryx Server engineers (thank you all - MattH; ZachH; WayeW) and Ben Burkholder trying to get our gallery server to start.
Error message was "
Failed to construct Gallery daemon process, process exited code <9002>
This was all that was provided in the server log files; the gallery log files; and the Windows Event Viewer.
In the end, it turned out that the issue was very simple - the MongoDB had open locks in place that needed to be deleted; and then the service came up immediately.
Several man-days of our effort; as well as the precious time of the Alteryx Engineers who gave up their Friday afternoon to help could have all been avoided if the error-message on the server failure said "Login failure on server due to open locks - please clean out locks on db.locks collection" with a link to the solution or a lookup code that be researched on the Alteryx support site.
Please could we go through the server service and eliminate all the exit codes and replace with human-friendly error messages - that way we could allow this kind of issue to be self-diagnosed, and allow the Alteryx Engineers to spend their time building the next generation of Alteryx Server rather than diagnosing a table lock.
cc: @avinashbonu @revathi @Deeksha @BenBu @WayneWooldridge @MattH @SteveA @ZachH
For scheduled jobs, there should be an option to include performance profiling in output logs globally. Basically we are looking at how we can understand which custom macros are in use, and in which workflows, and one way to do this would be to get the output logs into another tool (i.e., splunk), and then set up some queries there. It would work, but I would have to tell N developers to go set performance profiling on, re-upload their workflows, ect.
But why not have a switch on server / gallery that just turns this feature on globally for every scheduled workflow?
Thank you for attending my TED talk on why performance profiling should have an option to be set globally.
On the workflow results window, I'd like to see a column for "Start Time". If I have a workflow that is running, I'd like to know what time it started running so I have an idea on when it might finish.
I've been writing applications and regularly need to REQUIRE fields for data entry. When I do, I include ERROR MESSAGES at minimum. Often I label the field as something like: Name (Required). Wouldn't it be nice to have a red star or have the data field in another color for background? Taking this a step further, the validation rules being activated within the screen (rather than during run) would be awesome.
As long as I'm posting ideas, it would be nice to have an Alteryx supported function to identify the user within the application global variables. For users, it would make my apps more friendly if they could save their configuration (*.yxwv) in the gallery. Extending that thought, within my application I would like to be able to have easy access to their responses as well.
My use case for access to the .yxwv file data is that I will repeat some of the fields back to the user within my output. When needed I will write the responses to a text input tool and format it for display in the output. That requires an additional action and maintenance within the application.
Just a few application thoughts.
Thanks,
Mark
When rerunning a failed manual job, the same Priority is used, but the Optional Job Name is not and cannot be re-entered on submit. User has to go to Workflow results page and Edit to add the Optional Job Name for a rerun.
I suggest the Optional Job Name text box be added to the rerun submit page.
Prefill using the original job's value if one exists.
Thanks,
MJ
With Alteryx Server 2019.4, new users cannot create Collections by default.
As Alteryx Server admin this causes much manual effort on my side, because I need to configure new users manually.
Alteryx claims to be a tool for automatization and I do not see how this new feature fits into Alteryx's vision.
I wish that there were tools, which allow me to automatize the management of users on the Alteryx Server.
With a growing number of users on the Alteryx Gallery, manual user management is not an option!
I wish there was a way to create custom roles on the Gallery and assign them to AD groups, similar to "Permissions".
Those custom roles could include the privilege to create Collections, schedule Jobs, etc.
I would also love, if there was a way to give granular access to the Data Connection menu to users.
I have already addressed this topic to the Alteryx product manager in Q1 2019 and I hope this feature will be implemented in the future.
As we look at upgrading Alteryx Server - one of the challenges is that it's an all-or-nothing approach; and there doesn't seem to be a guided wizard approach to upgrading.
The upgrade process would be much less intimidating if we could create a Migration tool which can work across versions - similar to Microsoft SQL Server which has the. This would allow us to:
- Migrate a subset of assets up or down versions
- Migrate across servers to do consolidation or to split loads into different servers for the purpose of segregation
- Progressively migrate over time to limit the risk.
cc: @JohnPelletier
Please support SAML 2.0 for gallery
As an enhancement to the gallery, I'd like to be able to save my application parameters in the gallery in a similar fashion to when I run an app locally. Users can view the results of an application run, but can't save the parameters that created the run. I'll go a step further than this and ask for another enhancement. I'd like to be able to access the questions & responses within the execution of the app to display them during reporting.t
Use case:
For a list generation application, I need to present to the user the criteria applied during the selection process.
Input Address: 49015
Type of Vehicle: Chevy
Minimum Year: 2010
Maximum Year: 2015
I've got a working solution that is okay, but not very "Alteryx-easy". I need to have a second update attached to the interface tool to update the user response.
Thanks for your consideration,
Mark
Hello,
We use external corporate scheduler and we would like to start scheduling Alteryx workflows in this way. However, collections don't have API which would simplify our way of running workflows which we are shared by the users. Are you planning to enable such feature?
Best,
Piotr Zawistowski
Hello, Alteryx users,
My idea is simple but would make things way easier for the analytical app users on the Gallery.
Currently, the order is ascending and we can see all the files from all the applications we have run before.
It would help a million to see the most recent files first and only see the files related to this workflow.
Thank you,
Fernando Vizcaino
It would be really useful to be able to obtain the user name of some one running an app in the Gallery. This could be used for instance in row level security for people running an app that produces a report and that data is considered sensitive
Although the connectivity to the eMail infrastructure is set up on the controller and worker nodes - there is no ability to set up automated alerting for errors on workflows from the server.
We would like to be able to set up the gallery as follows:
- Every job is owned by a user or a distribution list
- If that workflow throws an error or warning (this should be configurable on the server, whether warnings are included), then the author should be e-mailed with a link to the specific workflow and the error log.
This can be done in a round-about way, by running an error-reporting alteryx job after the fact - but this kind of alert needs to go out almost immediately given our dependance on Alteryx for specific SLAs.
cc: @avinashbonu ; @Deeksha ; @revathi
Some of our artisans are unable to publish straight from designer and it would be great if there was an "Upload workflow" button in the private studio just like there is for curators in the admin panel.
Currently the Gallery's Admin API is a bit light on functionality. It only works with data connections & workflows and not regular server admin functions. Endpoints I'd love to see, but not limited to, are:
I have been trying to scan all of the workflows that are stored in the gallery and wrote this community post about it. Some Alteryx employees reached out to me directly to see if they could help solve my problem. We ended up with a somewhat wonky roundabout solution (that I haven't implemented yet) by downloading yxzp files through the Gallery API, unzipping them, then scanning the workflows as xml. I think the process could be greatly simplified if Alteryx had a set of Introspective tools.
The introspective tools would use similar, if not the same, processes that Alteryx already has in place to pull data from the gallery/server itself. The set of tools would be most useful for Server admins or people that are trying to build meta-workflows for Alteryx to make things easier for their users. Similar to the solution to my problem above, most of this functionality can be worked around by querying the Mongo and/or scanning engine logs. The Introspective tools would simplify this process greatly, especially when it comes to joining records from the Mongo and collecting workflow-internal data.
Since the tools will have direct access to the gallery/server it would make sense that they would only be available to machines with server licensing or could be made available if the user has a high enough permission level in the gallery they are trying to obtain data from.
User | Likes Count |
---|---|
2 | |
2 | |
1 | |
1 | |
1 |