Manage your 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’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.

All audit logs

Integration audit logs

These logs show high-level data for all your logs. To narrow down the information to integration audit logs, use Select resource type, user, and source.

Contents

• Download audit logs
• Practical uses for audit logs
• Parameters
  • Time
  • Source
  • User
  • Resource
  • Name/ID
  • Action
  • Field
  • Old and new values

Download 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 get up to 1,000 files from the last year. You can filter the logs by resource type, user, and source; however, the filters won’t be applied to your CSV download.

Practical uses for audit logs

It’s easy to review audit logs in a vacuum. However, if you use the power of your audit logs to troubleshoot flow errors you’ll be able to pinpoint changes that created issues with your integration or flow. 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.

Parameters

Audit logs record every action or change you’ve made to your flow or integration. The logs record nine (9) parameters for each change:

Time

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).

Source

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.

User

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.

Resource

Shows you the resource that was updated. There are eight resources monitored for changes:

• Integration – Your integration-level updates. This includes name changes.
• Flow – 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 – Your export-level updates. This includes name, operation, and other export settings changes.
• Import – Your import-level updates. This includes name, operation, and other import settings changes.
• Connection – Your connection-level updates. This includes name and authentication changes. Stack – Your changes to a stack.
• Async helper – In the event that 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.
• File definitions – Changes to the rules that define how integrator.io should parse or generate EDI or fixed-width files.
• Revision – Your recently created version management revisions including clones, pulls, merges, and snapshots.

Name/ID

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.

Action

The action that was taken. Actions include Create, Update, and Delete. The most common action is Update, while Create and Delete are reserved for creating/deleting a flow or another major event.

Field

The Field column gives you an idea of what’s been changed. It can display things like pageProcessors, connections, and names.

Old and new values

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.