Monitoring Integration Logs in Noca AI

Integration Logs serve as your central hub for tracking, analyzing, and debugging all integration events across your flows. Whether you’re monitoring daily operations or investigating issues, this tool offers the visibility you need to keep your automations running smoothly and efficiently.

Where to Access Integration Logs

You can access integration logs via:
Left Drawer Menu > Logs & Monitoring > Integration Logs

Integration Logs Table

The Integration Logs screen provides:

  • A breadcrumb for navigation at the top
  • A search box with built-in filters directly above the table:
    • Keyword search (e.g., by flow name or trigger type)
    • Status filter with options:
      • Success
      • Paused
      • Processing
      • Terminated
      • Error – Resolved
      • Error – Unresolved
  • A refresh icon on the right to reload the most up-to-date log entries

Table Header Controls

Each column header offers powerful built-in options:

  • Hovering over a column displays:
    • An arrow icon to quickly sort data (ascending/descending)
    • A kebab menu (⋮) with additional options:
      • Sort by column
      • Filter – Apply filters based on conditions (e.g., contains, equals)
      • Hide column
      • Manage columns – Open a checklist to show/hide specific columns

Table Columns Explained

Started At

Date and time when the flow run began

Duration

Total runtime in seconds

Trace

Link to open a detailed task list modal, showing:

  • Event Name
  • Status
  • Date
  • Duration (in seconds)
  • Credits – Usage units, important for cost and performance monitoring

Status

Whether the run is processing, or was a Success, Error or Terminated

Rate Limit

Indicates if the flow is during execution

Resolved / Unresolved

Flags if the error was marked as resolved

Message

Error or status message for deeper context

Actions

Direct link to open this flow run in debug mode

Noc Name

Name of the flow (a.k.a. Noc) related to the event

IP Address

IP from which the run was triggered

Triggered By

What triggered the flow — e.g., Scheduler, Gmail, Salesforce Event, Debug.
This is important for distinguishing between manual runs and automated triggers.

Applications

Apps involved in the integration

Actions Menu (⋮)

Additional quick actions:

  • Play – Re-run the flow
  • Set as Resolved – Mark the error as handled

 

Back to top