Observability

Tenklo'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 Tenklo's logs based on three principles:

Comprehensive: Everything that happens in Tenklo 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

Logs are structured into:

Operations: High-level actions happening in your Tenklo 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)

Tenklo provides detailed filtering and searching of log messages by integration, connection, operation type, status, etc.

We recommend exploring the logs in your own Tenklo account under Logs.

Logs are retained for 15 days, then permanently deleted.

The Management MCP server provides tools for listing and filtering log operations and retrieving their messages from an MCP-compatible client.

This helps LLMs investigate and fix integration issues automatically.

Tenklo supports exporting OpenTelemetry traces so you can monitor and analyze integration activity in your own observability stack.

Use this for:

Advanced custom metrics
Advanced alerting and escalation paths (e.g., segment sync errors by customer account for customized escalation paths)

The following operations are exported as traces:

If you need support for other operations please reach out. We can enable support for them.

Log into the Tenklo dashboard and navigate to the Environment settings page.

In the Environment Settings, provide the following information:

OpenTelemetry endpoint: The endpoint URL of your OpenTelemetry collector. Ex: https://my.otlp.collector:4318
Headers (Optional): Any authorization headers or additional headers required to access your collector.