Platform logs are easy to “set and forget”, especially as you are getting started with other high-priority implementations. But if you're building in integrator.io, they are actually your best troubleshooting friend. To ensure you are using your logging features to their fullest potential, we have highlighted the key ways your teams should be utilizing the logging options included in your Celigo subscription:
-
Audit Logs - Audit logs maintain a record of specific activities in your flows, including the fields that were changed, the type of change, and who is responsible for the change. This is helpful as you look for root causes of issues and want a deeper dive into who has been making changes in the platform. You can view your audit logs at a flow or integration level. Depending on your subscription tier, you are able to keep these logs for anywhere from 1 to 3 years, to fully ensure your teams are able to review what changes have been made in your account. For your records, you are able to download these logs.
-
TIP: You can utilize 1. * Celigo APIs to streamline your Audit Log download process when you need the audit data outside the UI—for automation, reporting, compliance, or correlation with other systems. 1. * This article walks you through the process of connecting to integrator.io APIs, while you use GET /v1/audit to connect to the Audit Log API.
-
-
Integration Logs - Here you can find information regarding your specific flow runs within a given timeframe. Depending on your subscription tier, you can review this data for 30 or more days, and can be configured in your Data Retention tab within Account Settings. These logs will include flows that have run in a given period, the number of errors, successes, ignored stats, and the number of errors auto-resolved by Celigo AI. While this doesn’t tell you who made changes to integrations like the Audit Log, this provides more insight into how your flows are running, and helps you determine which flows may need more attention. This gives you a great overview of all the activity in your integrations based on your 1. pre-determined data retention period. Much like Audit Logs, you are able to download these logs for your team to review if there are any challenges with your flows.
-
Debug Logs - Ever wanted to learn more about where a flow step might fail? Enabling 1. Debug Logs before you run a flow will give you just that information! These logs can assist you when troubleshooting by enabling you to view errors that caused a particular record to fail. You can also access information that may help you determine what you need to fix in your flow to avoid errors or optimize your integration's performance. All you need to do is click the Debug icon in the top right corner of your flow actions, choose how long you would like the debugger to capture flow run information, and from there, you are able to get more insight into why a flow may have failed or caused an error.
The logs the Celigo platform provides don’t end there, but this will give you a great overview of how to utilize the logs you have to their full potential. As the integrator.io platform evolves, so do our offerings, and this includes more logging options that you will soon learn about. Keep your eyes peeled for a post walking through the new Execution Logs our team has been working on!