Question

Overview/metrics on jobs?

Distributed Computing Cluster

Updated November 8, 2018

asked on November 7, 2018

We have two OCR engines running every night. Our files are a mixture of documents, images, plans and some take almost no time at all, and some chug away for much longer time periods.

I can log into the DCC in the morning and get a quick overview of the jobs that went through (we have each file as an individual job to ease tracking).

Does anyone have a way to build up some reporting on the efficiency of the jobs? I would love to tease out in a .csv file if possible but I have not found any way in my system.

we are running DCC 10

Thanks in advance!

0 0

Replies

replied on November 7, 2018

Hi Rob,

I think the PowerShell modules might be the best option. In theory, you could set up a scheduled task that would dump the data into CSV files that could then be used for reporting.

We have to run OCR in real-time, so after the Schedule OCR activity in Workflow I add the job number to an external database, then run a scheduled workflow that kicks off the PowerShell script and updates the database with the job status information so I can detect when each job is complete.

Obviously your needs are a bit different, but based on what I've been able to achieve, I think you could get what you need if you figure out an ideal configuration.

The PowerShell module is described in this part of the admin guide.

The only catch is that the DCC only keeps track of jobs for a limited amount of time, so you would need to schedule it to run often enough that you're not missing anything.

1 0

replied on November 8, 2018

Wow, I cannot imagine that I am the only person to have asked this...I searched a bunch in Answers and found nothing.

Would your recommendation of using PowerShell be in a workflow or as a scheduled script in PS?

I am new to the LF world and have a bunch to learn, PowerShell is next I guess ;)

Thank you!

0 0

replied on November 8, 2018

I don't know that doing it in Workflow is necessary for your needs. It is actually a little more complicated to do it from within in Workflow than as a scheduled task in Windows because you need to install the DCC PowerShell modules on the Workflow server than add a Workflow Script activity that creates and runs the PowerShell instance; in pure PowerShell it would be a little more direct.

The main reason I have it in Workflow is because it is part of a larger set of Workflow processes, so doing it that way keeps everything together and ensures the processes are all synchronized.

In your case, it sounds like the process could run on its own, so a standalone script would probably be less complicated.

0 0

You are not allowed to follow up in this post.

Question

Question

Overview/metrics on jobs?

Replies

Sign in to reply to this post.