Generate a report of flow events

Rate this feature
Included in the June 2021 release A Reports option in the Tools menu allows you to produce a list of all events that have run through one or more flows for a specified time period.  Each report is available for download for 30 days.

Contents

• Create a report
• View a report
• What’s in the report?

Create a report

The reports are separate for integrator.io Sandbox and Production environments. To create a Sandbox report, for example, you must first be working in your Sandbox environment.

1. Select Tools > Reports from the left navigation menu.
2. In the header row of the Flow events report results list, click + Run report.
3. In the resulting Run report pane, customize the required settings for your report:
   • Integration – All captured flows must belong to the integration (tile) that you choose here. Only the integrations that you’re allowed to edit or monitor are available in the list.
     • “Child” integrations – Optionally, you can narrow the flows shown below according to member integrations, such as stores or banks.
   • Flows – Select one or more flows in this integration to include in the report.
   • Date range – Pick a convenient window ending now, or click Custom to specify up to a three-day range within the last 30 days. Be sure to click Apply after entering a range.
4. Click Run report.

Next, the new report is added to the list, with a progress animation until your report is generated and the Status switches to Completed, if successful.

View a report

You can browse and revisit all reports created in the last 30 days. To make it easier to find a report, click the Filter ( ) button where available on a column heading.

The list of reports contains summary information. To review the settings, from the Actions overflow (…) menu select View report details. The details include the integration, flow, and date range settings, as well as the completion date and status.

To view the actual report, click Download results. The CSV file will be transferred to your default browser download folder or to a selected local or network location.

What’s in the report?

Anyone with an integrator.io account can view a report, regardless of permissions level. The only flow value exposed in the report is the trace key, typically a unique record ID.

When you open the CSV report, you’ll see the following columns, corresponding to your flows’ structure:

1. traceKey – A unique value for this record.
2. time – The UNIX time in milliseconds.
3. type – The successfully processed record’s flow step, such as export, import, or lookup, or an error event, such as ignore or error.
4. timeTaken – The number of milliseconds in which the record was processed.
5. _flowJobId – An integrator.io value for an individual flow run. This value will be unique, in case you want to filter to see the number of flow runs; or it may be useful for troubleshooting with Celigo support.
6. _exportId – An integrator.io resource ID for the flow step. To resolve the ID to a human-readable name, sign into integrator.io and open the URL https://integrator.io/exports/edit/exports/<_exportId> (or https://eu.integrator.io/exports/edit/exports/<_exportId> for EU customers).
7. _importId – An integrator.io resource ID for the flow step. To resolve the ID to a human-readable name, sign into integrator.io and open the URL https://integrator.io/imports/edit/imports/<_importId> (or https://eu.integrator.io/imports/edit/imports/<_importId> for EU customers).
8. oIndex – The order of the flow step. For example if a flow contains 1 export and multiple imports, then the export will have an oIndex of 0 and imports 1, 2, and so on.
9. _connectionId – An integrator.io resource ID for the connection. To resolve the ID to a human-readable name, sign into integrator.io and open the URL https://integrator.io/connections/edit/connections/<_connectionId> (or https://eu.integrator.io/connections/edit/connections/<_connectionId> for EU customers).
10. retryDataKey – A UUID for the error retry data.
11. exportDataURI – A link to the original data in the source application. This column is populated only if the field Data URI template is set in the export.
12. importDataURI – A link to the original data in the destination application. This column is populated only if the field Data URI template is set in the import.
13. exportField – If the user-defined settings fail during import field mapping or processing transformation rules, this column will contain the “extract” details.
14. importField – If the user-defined settings fail during import field mapping or processing transformation rules, this column will contain the “generate” details.
15. source – When the type (col. C) is error, this column contains a named error generator, such as “application.”
16. code – When the type (col. C) is error, this column contains the error code returned.
17. message – The error message for the code (col. P).
18. legacyId – (Deprecated.)
19. classification – The error classification.
20. reqAndResKey – A UUID for the HTTP request and response debug logs for the error type event.