Audit logs maintain a record of specific activities in your flows, including the fields that were changed, the type of change, and who’s responsible for the change. You can view your audit logs at a flow or integration level.
Important: In audit logs, pageProcessors and pageGenerators represent imports and exports, respectively. It’s just a system naming convention that doesn’t affect your integrations or flows.
- Download audit logs
- Practical uses for audit logs
integrator.io keeps audit logs for the last year. If you download logs as CSV files or use the audit API endpoint, you can download up to 1,000 records simultaneously. If, for example, you’ve generated 3,000 records in the last 24 hours, you can download the records in parts by adjusting the Custom date and time. You can filter the logs by resource type, user, and source; however, the filters won’t be applied to your CSV download.
It’s easy to review audit logs in a vacuum. However, you can use your audit logs to troubleshoot flow errors and pinpoint changes that created issues with your integration or flow. You can also determine who changed account permissions. For example, if someone changed an import field and caused an error, you can use audit logs to review the changes. Then, use Integration Lifecycle Management to revert your changes.
Audit logs record every action or change you’ve made to your flow or integration. The logs record nine (9) parameters for each change:
You can configure your account profile to display timestamps in any date/time format. If you’ve set your account to relative time, the timestamp is displayed as the length of time between the started date and time and the current date and time (1 day ago, 3 hours ago).
The user responsible for the changes. In cases where the account is shared by multiple people with the same password, the only username is something similar to “Account Owner” or your company name.
Tip: If you’re an account owner or administrator you can invite new users (or remove old users) to your account.
Determines how the change was made. This could be:
- UI – Changes were made from the user interface.
- API – Changes were made in the API.
- Stack – Changes were made from the stack.
- System – Any change made to a resource by integrator.io backend logic or a system process.
- Integration app – Changes were made by the integration app.
Shows you the resource that was updated. There are nine resources monitored for changes:
|Integration||Logs your integration-level updates. This includes name changes.|
|Flow||Logs your flow-level updates. In integration-level audit logs, this is displayed as an update to the flow, with a specific field name (pageProcessors/Imports or pageGenerators/Exports) and changes available to view.|
|Export||Logs your export-level updates. This includes name, operation, and other export settings changes.|
|Import||Logs your import-level updates. This includes name, operation, and other import settings changes.|
|Connection||Logs your connection-level updates. This includes name and authentication changes.|
|Stack||Logs your changes to a stack.|
|Async helper||If certain data is unavailable, an async helper has the app’s API ping integrator.io when the info is available. The flow will be paused until the data is received. This logs all modifications to your async helpers.|
|File definitions||Logs all modifications to the rules that define how integrator.io should parse or generate EDI or fixed-width files.|
|Revision||Logs all your version management revisions, including clones, pulls, merges, and snapshots.|
|Scripts||Logs all modifications to your scripts.|
|Notification||Logs all notifications when a resource is created or deleted.|
There are also account-specific resources, including user status changes, deletions by each user and IP address, agent changes, and single sign-on logs.
To find these resources, click your profile at the top, right-hand side of the screen → click My Account → and click Audit log.
|Account-specific Resource type||Description|
|User||Logs account, permission, IP address, notification, and updates by user.|
|Agent||Logs modifications to your secure on-premise or cloud tunnels to integrator.io.|
|SSO client||Logs all changes to your single sign-on configurations. integrator.io does not display your client secret. Multiple layers of protection are in place, including AES 256 encryption, to keep your client secret safe. When editing this form later, you must enter this value again.|
|API tokens||Logs all API token modifications. integrator.io does not display your API tokens. Multiple layers of protection are in place, including AES 256 encryption, to keep your API token safe. When editing this form later, you must enter this value again.|
|My APIs||Logs all modifications to your custom My APIs.|
The name or identifier of your updated resource. Resources with IDs instead of names have been deleted, which is why they’re only available by the ID they were given when they were created.
The action that was taken. Actions include:
- Sign in
- Sign out
The most common action is Update, while Create and Delete are reserved for creating/deleting a flow or another significant event. The Sign in and Sign out actions are reserved for the User resource.
The Field column gives you an idea of what’s been changed. It can display things like pageProcessors, connections, and names.
The field values before and after the change.
In the Old and New value fields, you have options including Click to view edits, dates and times a token was updated, and secure connection details. You should know that we won’t display your secure connection details, like keys, tokens, or passwords, in audit logs under any circumstances, as those details are encoded.
When you use Click to view, old and new edits are displayed side-by-side in a popup diff screen. This is a feature of the flow audit log that’s also available in the integration logs. It drills down and shows you the exact changes you made, including any mapping changes.