MongoDB actual run time of workflow

I am trying to get the actual running time of workflows from the Mongo database but so far all I can find is the CreationDateTime and CompletionDateTime in the AS_Queue. However CreationDateTime is the time the server started to queue the workflow and not the actual start of the workflow running.

Can anyone help in where I can find this level of information?

Thanks

After searching around some more I have found the data in the __ServiceData Blob

MongoDB

Accepted answers

All comments

Kmaclean

I don't think there is one directly, maybe in the audit tables,.... but currently I macgyver it using the column like 'execution time' as in how many seconds it took the workflow to execute, and you can use this to find the actual time of execution by subtracting it from the Completion time,

I also use it in a similar fashion to get 'queue time' by taking the remainder of subtracting the execution time from the difference between CompletionDateTime and CreationDateTime

raychase

You are correct about the JOB_CREATION_DATETIME and JOB_COMPLETION_DATETIME from the AS_Queue collection. The timestamp that you're after is the RESULT_EXECUTION_STARTTIME within the AS_Results collection. It refers to the exact moment when the AlteryxEngineCmd.exe was spawned to run the workflow.

The time difference between JOB_CREATION_DATETIME and the RESULT_EXECUTION_STARTTIME is referred to as the 'queue time'.

Marcel_Gavrila

Hello,

Sorry, what was here, because it doesn't show me?

rhipp87

I can't find anything related to AlteryxPlugin_SdPrint either, which makes this useless.

rhipp87

Thanks, Tim. It looks like it actually might run even though it has the question mark icon, which usually indicates a missing macro or plugin. I'm trying to see if this parses the ServiceData better than my manual tokenization and then hex->ascii. I'll follow-up.

TimN

In this case, the Question mark is actually a tool that does a debug print of a field that is formatted as Binary JSON. I'm not sure how that tool was actually created (i copied from a WF) but it's great for reading __ServiceData field. I believe future Alteryx releases won't require you to jump thru these hoops to get details.

rhipp87

I can only find the engine run timestamp in the physical log files on the Alteryx server's hard disk, outside of the mongoDB instance. What I did do, however, is a formula with datetimeadd([CompletionDateTime],-[ExecutionTime],"seconds") to get the engine's start runtime.

The ServiceDataParser Macro TimN provided is available within the AlteryxServerUsageReport in the Alteryx Server 2022.1 downloads in the license portal. It works even though it displays the missing dependency large question mark icon, appearing as if a plugin or macro is missing. This also appears to have solved my issue with random unicode trash appearing with blob -> hex -> (..) tokenize -> CharFromInt(HexToNumber([OutputLog])) and concatenating the results.

Cheers, Tim.

Quick Links

This months top contributors

atcodedog05 19598

Qiu 15880

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703