Skip to main content
Nango’s logs are comprehensive and give you a detailed picture of what happens in your integrations.

​
Our approach

Since integrations rely on third-party APIs, production issues are bound to happen. When you encounter a problem, great observability is the difference between a week-long needle-in-a-haystack hunt and a timely resolution. We built Nango’s logs based on three principles:
  • Comprehensive: Everything that happens in Nango for your integrations produces an “operation” in the logs
  • Detailed: Every operation and every log message contains detailed information about the integration, connection, and function. Error messages are as detailed as the external APIs allow.
  • Customizable: You can easily log your own messages from functions you write (learn more). To consume logs, you can either use our built-in interface or export them with our OpenTelemetry exporter

​
Overview of Nango logs

Nango Logs screen on a demo account (click to enlarge)

Logs are structured into:
  • Operations: High-level actions happening in your Nango account (e.g., sync executed, connection created, webhook processed)
  • Log messages: Nested in operations, these provide details on what happened (e.g., HTTP request executed, data validation warning, custom log message)
Nango provides detailed filtering and searching of log messages by integration, connection, operation type, status, etc. We recommend exploring the logs in your own Nango account under Logs.

​
OpenTelemetry export

Nango supports exporting OpenTelemetry traces. We recommend this for:
  • Advanced custom metrics
  • Advanced alerting and escalation paths (e.g., segment sync errors by customer account for customized escalation paths)
To set up OpenTelemetry export, follow our OpenTelemetry export setup guide.