topic Re: Logger Mechanism in Workato Pros Discussion Board

Logger Mechanism

bhavesh-patel — Mon, 05 Sep 2022 16:47:02 GMT

Hey Everyone,

Can anyone guide me on how to implement the logger mechanism in Workato?

I have used Logger By Workato. Now my end goal is to maintain all these logs with every job execution so that I can identify errors for par jobs.

Re: Logger Mechanism

lykee11199 — Mon, 05 Sep 2022 16:50:46 GMT

It is better to use Handle Errors than logger for error inspection.

Re: Logger Mechanism

bhavesh-patel — Mon, 05 Sep 2022 17:00:59 GMT

I have used Handle Errors to catch unexpected errors but I need a logger as well.

Re: Logger Mechanism

steven-marissen — Mon, 05 Sep 2022 17:12:13 GMT

If I understood correctly you would want to identify and count what errors occur and how many times they do?

On error, you could call the same function and pass parameters into it from the recipe itself. Within the function you could use a lookup table of Workato (although limited in rows and columns) or use a connected SQL server to put your logging details.

Also there is the Autonomous Operations Framework by Workato that has more or less the same goal, monitoring issues in every recipe and taking actions where needed. https://academy.workato.com/autonomous-operations-framework

I hope my interpretation was correct and helps you out 🙂

Re: Logger Mechanism

pratik-maskar — Mon, 05 Sep 2022 17:22:14 GMT

Try using Notes for each step where it will be useful to pick up the errors in the steps

Re: Logger Mechanism

shruti-2-sharma — Tue, 06 Sep 2022 16:24:30 GMT

Hello Bhavesh ,

You can use lookup table to Store logs for every execution .

You can use the following approach

1)Create one lookup table and provide Column name relevant to your logs data

2)Create one functional recipe to add item in Look up table

3)Call functional recipe in your parent recipe where ever you want to log data .

Shruti Sharma

Mobile: +91 9643919302

Email: shruti.2.sharma@coforge.com

Coforge Limited

(Erstwhile NIIT Technologies Limited)

www.coforgetech.com

DISCLAIMER: The information transmitted, including any attachments, is intended only for the person or entity to which it is addressed and contains confidential and/or privileged material. Sharing this message or its contents with a third party without prior written consent is strictly prohibited. If you receive this email by mistake, please advise the sender and delete it immediately. Email transmission cannot be guaranteed to be secure or virus-free as information could be intercepted, corrupted, lost or destroyed as a result of the transmission process. Therefore, you should check the email for threats with proper software, as the Company does not accept liability for any damage inflicted by viewing the content of this email. Views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Company. Through this email, no employee or agent is authorized to conclude/commit any new or incidental terms, which are not part of the original contract with any client or vendor, other than by way of duly executed and signed amendment contract between the parties in accordance with the agreed protocol of the contract. Coforge Limited and its related entities consider the privacy of its clients to be of utmost importance and work to protect it. Please be aware that the Company monitors email communications through our networks for compliance purposes. The Privacy Policy of the Company can be accessed from our website www.coforge.com.

Re: Logger Mechanism

gwilkinson — Tue, 06 Sep 2022 19:20:16 GMT

One use case where I think Logger is useful is to capture the results of the steps within a loop where the job report would only show the results from the last iteration. I have not yet tried it but someday soon. It isn't necessarily just errors, I think results from steps that succeeded are also valuable for troubleshooting.

Re: Logger Mechanism

mppowe — Tue, 06 Sep 2022 21:01:36 GMT

Be careful of using your valuable Tasks b/c the Logger step counts as a Task. And using Lookup tables can work but remember they cap out at 10,000, so make sure you're not going to exceed that. But another thought here is that Workato has a way to feed your job history log to an enterprise logging solution of yours, called "Audit Log Streaming" (https://docs.workato.com/job-history-replication.html#audit-log-streaming). We do that with Splunk right now, though we're still working through the kinks b/c it dumps everything into 1 line as JSON, which is currently getting truncated and makes it hard to read 🙂 So we still need to work through that, but it sure SEEMS useful...!

Re: Logger Mechanism

jayesh — Tue, 06 Sep 2022 23:00:55 GMT

Bhavesh - every job execution of a recipe by deault includes a full trace or input/output and errors at triiger and every action step in the recipe. So you get a log by default. As others have suggested you can catch errors and do automated recovery using try catch - including sending alerts/notifications (email, Slack, etc.) or even opening tickets in the appropriate ticketing system (ServiceNow, Jira, etc.).

We also have best practice guidance around error handling - this is available as the Autonomous Operations Framework (AOF): https://www.workato.com/the-connector/introducing-automation-accelerators/

Please take a look at AOF and then let us know if that addresses your requirements.

Re: Logger Mechanism

bhavesh-patel — Wed, 07 Sep 2022 16:51:36 GMT

That exactly what we faced, workato don't maintain logs of multiple records in for each loop so that's why we are asking here. RIght now we are mainting a list of logs using variables by workato list functionality. But we are exploring for more and better ideas for logging.

Re: Logger Mechanism

steven-marissen — Wed, 07 Sep 2022 17:03:53 GMT

Troubleshooting loops is really difficult in terms of visibility.

Which is also why we've frequently opted to call a function within a loop and treat every loop item, one by one via that function for full visibility.

It's not perfect but has saved us a lot of time on troubleshooting.

Re: Logger Mechanism

mppowe — Wed, 07 Sep 2022 20:50:49 GMT

Steven Marissens yes totally, we do the same. It makes life much easier. But flies in the face of bulk actions, and calling a recipe function consumes a task, and returning a value from a function consumes a task. So unfortunately there are "cons" with this approach too, but I agree that it makes troubleshooting/monitoring much easier and is what I have opted for myself.

Re: Logger Mechanism

steven-marissen — Wed, 07 Sep 2022 21:02:17 GMT

Mike Power Yeah we swapped task-based for recipe-based billing around 2 years ago because it was demanding compromises in 'build quality' as you try to keep the amount of tasks down.

Also made it impossible predict how much it was going to consume because it can differ so much per month.

It's defintely more expensive but less time in troubleshooting and other quality enhancers reduce costs.

Re: Logger Mechanism

mppowe — Wed, 07 Sep 2022 21:21:27 GMT

Steven Marissens I wish we had that input before we just signed a renewal for 3 years that switched from connection-based to task-based. I had advocated some for Recipe-Based b/c it seemed better to me, but I think Workato prefers customers on task-based. At least that's the vibe I got and the pricing seemed to favor it.