Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Telemetry Logs

The Telemetry Logs module provides real-time insights into how users and systems interact with your APIs. It automatically collects and transmits data related to application performance, usage behavior, and errors, offering a detailed view of the runtime environment. This module plays a vital role in system observability, helping teams monitor and maintain the health and reliability of their services.

Telemetry logging is built on three core pillars, Tracing, Logging, and Metrics, each contributing to effective monitoring and issue resolution.

How It Works

Telemetry data is collected passively and automatically during system operation, without requiring user intervention. When an API call is made or a system action is triggered, the following happens:

  • Tracing captures the journey of a request as it moves through different services or components, visualizing dependencies and timing.
  • Logging captures contextual details about events, errors, and activities, aiding in diagnosing issues and understanding the runtime behavior of the application.
  • Metrics measure the performance of the APIs.

This collected data is stored and displayed in the Telemetry Logs User Interface (UI), where you can filter, search, analyze, and export log records.

Benefits

Telemetry Logs offer several key advantages that support proactive monitoring, operational efficiency, and improved system reliability. The following are some of the primary benefits (but not limited to):

  • Performance Monitoring: Gain real-time visibility into API performance by tracking critical metrics such as response times, throughput, and resource consumption.
  • Usage Analysis: Understand how users interact with APIs by capturing and analyzing usage patterns, frequency of calls, and common request flows. This insight supports product improvement, scaling decisions, and user behavior analysis.
  • Error Detection and Troubleshooting: Capture detailed error information, including error codes, messages, and stack traces. These logs are essential for quickly identifying, diagnosing, and resolving issues within the application or API.

Overview of the Telemetry Logs UI

The Telemetry Logs page is designed to provide an intuitive experience for viewing, filtering, and exporting system-generated logs. It enables quick access to relevant log data while offering advanced filtering and export options to support detailed troubleshooting and analysis.

The primary component of the UI is the Telemetry Logs list, which presents all system-generated log entries in a structured format. You can switch between List View and Grid View.

Each log entry in the list includes key attributes such as Trace ID1, Span ID2, Log Time, Duration, Severity, Product, Service Name, and Message.

Note:

When there are more than 1,000 telemetry log entries, the application displays the following message on the list screen: "Please note that the actual count of records could be higher. Export the logs to get the full list."

Clicking a Trace ID within the logs list opens the Log Details panel as a slide-out panel on the right side of the screen. The Log Details provides complete visibility into the log message associated with the selected Trace ID, giving you deeper insight into the event for root-cause analysis or debugging. For more information, see Log Details.

To handle large volumes of log entries, the interface includes pagination controls at the bottom of the logs list. This enables you to navigate through multiple pages of logs while maintaining interface performance and usability.

The Search Bar, located at the top of the logs list, allows you to perform quick searches based on Trace ID, Span ID, Severity, Products, keywords, or phrases found in the log messages. For more targeted filtering, the interface provides Time filter in dropdown menu, enables you to narrow logs predefined time ranges such as Last 1 hour, 6 hours, 12 hours, 24 hours, or 7 days, and custom date and time range. For custom date and time, select the Custom Range option from the Time dropdown, choose the start and end date & time, and click Apply. You can also use the filters, advanced filters, manage visible columns, column-level actions and filters, and filter visibility & management to further narrow down your result.

Note:

The application retains and displays telemetry logs for up to 30 days, with a maximum range of 7 days per request.

The Export Logs button enables you to download the currently filtered log data for offline analysis, internal reviews, or sharing with support teams. Additionally, the Export Historybutton helps you track past export actions, view their status, and download exported logs.

1 A unique 32-character hexadecimal identifier that represents the entire distributed trace, meaning the end-to-end request flow to which this log belongs.
2 A unique identifier for the specific span, or unit of work, within the trace that generated this log entry.