This topic introduces Cursor observability, an LLM observability log application available in TLS application marketplace.

Overview

The Cursor observability log application from TLS offers services including the Cursor observability dashboard, Trace analysis, and session analysis.

Once you connect to the TLS Cursor observability log application, it listens to Cursor Hooks and incrementally reads agent-transcripts, collecting user inputs, model outputs, tool invocation details, model names, token usage, as well as session and workspace context, and organizes them as Trace logs to upload to the configured Volcano Engine TLS.

By integrating the Cursor Observability log application, a dedicated Cursor trace log topic is automatically created in TLS, visual charts are generated, and session and trace data are displayed, enabling trace tracking and observability.

Prerequisites

Category	Description
Software limits	The server deploying Cursor must have NPM and Node.js 22 or later version installed.
Region restriction	The server deploying Cursor and the TLS service must be in the same region to ensure network connectivity
Authentication method	Depending on the authentication method, obtain the user's Access Key ID, Secret Access Key, or API Key. AK/SK: AccessKey ID and AccessKey Secret for Volcano Engine accounts. Obtain them from the Volcano Engine console Key Management page. We recommend using IAM user keys. Ensure this user has the required permissions. For details, see IAM overview. Supports automatic creation of TLS resources (project/app/topic) and auto-generates log topic IDs. API Key: A key credential for requesting Volcano TLS. It is used only for reporting Log, Metric, and Trace data. Enforces strict permissions and does not support auto creation of TLS resources. It is suitable for multi-data center environments and strict permission management scenarios. Notice API Key is in closed beta. If needed, contact your account manager for access to the allowlist.

1. Integrate the Cursor log application

Log in to TLS console.

Select the region where log service is located from the top navigation bar.

In the left navigation bar, select AgentLoop > AI observability.

On the AI observability page, click Integrate AI observability.

On the Integrate AI observability page, create an application.

Click the Cursor icon and select the Cursor application.

Configure the integration parameters, then click Create application.

Parameters	Description
Region	The region where the log application data is stored.
Log project	Select the project where the log application data is stored. Notice After the log application is successfully created, a log topic with the CURSOR tag will be automatically created in the project to store trace data. The relevant information about this log topic is as follows: Log topic name: application_name_trace Number of shards: 2 Log storage period: Standard storage for 90 days Index: Key-value index is automatically configured.
Application name	Enter the name of the Aiden log application. Length must be between 3 and 64 characters. Only supports Chinese, lowercase letters, numbers, underscores (_), and hyphens (-). Can not start or end with a hyphen (-) or underscore (_). Cannot start with tls_, tos_, or certain reserved fields.
Description	Description information for the log application. Length limit is 0–128 characters.

After creating the application, proceed to the next step to obtain the usage guide and integrate the log application.

2. Integrate Cursor application data

Obtain the usage guide for integrating Cursor application data.

Go to the Integration configuration page.

When integrating a log application
After integrating a log application
When creating a Cursor log application in AgentLoop, you can obtain the corresponding usage guide based on the interface prompts.
Refer to 1. Integrate the Cursor log application to integrate the Cursor log application.
On the Integrate AI Observability page, in Integration Configuration, configure the following information to obtain the usage guide.
Log in to TLS console.
Select the region where log service is located from the top navigation bar.
In the left navigation bar, select AgentLoop > AI Observability.
On the AI Monitoring page, access the usage guide page using the following methods.
Click the access configuration icon in the Actions column of the target log application.
Click the target log application name, then click Access Management.

On the Integration configuration page, select the authentication method, configure the following information, and obtain the usage guide.

AK/SK access
API Key access
For Access Method, select AK SK Access.
For Connection Method, select Public Network or Volcano Engine Internal Network as appropriate.
In Usage Guide, copy the auto-generated usage guide.
For Access Method, select API Key Access.
For Connection Method, select Public Network or Volcano Engine Internal Network as appropriate.
For API Key, select the API Key that has been created.
In Usage Guide, copy the auto-generated usage guide.

Usage guide example (AK/SK integration method):

Public network
Volcano Engine internal network

npm exec -y
--registry=https://registry.npmjs.org/
--package=@volcengine/tls-observer-cursor-install@latest --
tls-observer-cursor-install
--non-interactive
--force
--region The system autopopulates the current region.
--trace-topic-id The system autopopulates the trace-topic-id
--ak <Requires manual replace of the actual tls-ak>
--sk <Requires manual replace of the actual tls-sk>

(AK/SK method only) Modify the authentication information in the usage guide.

Enter the obtained Access Key ID and Secret Access Key into the AK and SK fields in the usage guide, respectively.

Integrate Cursor observability logs into the log application.

Log in to the server where Cursor is deployed.

Use the information obtained from the usage guide to install the TLS plugin.

Restart the Cursor service after the plugin is installed.

Return to the TLS console to view the observability chart data.

Monitoring chart details

The monitoring chart details for the TLS Cursor observability application are as follows:

Type	Chart
Cursor observability	Request overview: Session count, conversation count, model request count, tool invocation count, request trends Tool overview Successful invocation count, failed invocation count, tool invocation latency P90, tool invocation Top 10, tool invocation failure Top 10, and tool invocation trend
Trace analysis	Trace call chain analysis Displays the Input, Output, Trace ID, total Tokens, InputTokens, OutputTokens, latency (s), start time, end time, and more for the specified call chain.
Session analysis	Session analysis Displays the First Input, Last Output, Session ID, total Tokens, number of call chains, latency (s), model, start time, end time, and more for the specified session.
Topic list	Displays the log types, projects, log topics, description information, and more generated by the current log application.

Manage my applications

After the log application is successfully connected, you can manage connected log applications as follows:

AgentLoop

Application marketplace

Log in to TLS console.

Select the region where log service is located from the top navigation bar.

In the left navigation bar, select AgentLoop > AI Monitoring.

On the AI Monitoring page, in the Actions column of the corresponding log application, the following management operations are supported:

Edit application information: Click the edit icon to modify the application name and description.

Obtain usage guide: Click the access configuration icon to open the access configuration pop-up window, where you can obtain example usage guide information.

Delete my application: Click the delete icon to delete the log application.

Application name_trace (log topic) log fields

Field	Type	Description
Attributes	json	Custom key-value pairs attached to the Span, recording business-related information.
Duration	long	The duration of the Span (End - Start), measuring the time consumed by the operation.
End	long	Span end time.
Events	text	Events that occur during the Span lifecycle.
Host	text	The host running the service.
Kind	text	The type of the Span.
Links	text	References to other Spans (used for cross-Trace associations, such as asynchronous task scenarios).
Name	text	The name of the Span, usually a description of the operation.
OTLPName	text	The original name reported via the OTLP protocol (OTLP = OpenTelemetry Protocol).
OTLPVersion	text	The version number of the OTLP protocol used.
ParentSpanID	text	The ID of the parent Span, indicating which operation triggered the current operation. This field is empty for the root node.
Resource	json	A set of attributes describing the service itself (more comprehensive than ServiceName), such as service name, version, runtime environment, and so on.
ServiceName	text	The name of the service that generated this Span.
SpanID	text	The unique ID of the current Span.
Start	long	Span start time.
StatusCode	text	The execution result of the Span.
StatusDescription	text	Supplementary description of the Span execution result.
TracelD	text	The TraceID of the entire call chain. All Spans from the same request share the same TraceID.
TraceState	text	Custom trace context metadata.

Attributes

Field	Type	Description
gen_ai.input.messages	text	The complete list of input messages sent to the model.
gen_ai.provider.name	text	The name of the model provider.
gen_ai.request.model	text	The specified model name for the request.
gen_ai.tool.name	text	The name of the tool involved in this invocation.
gen_ai.usage.cache_read.input_tokens	long	The number of input tokens that hit the KV Cache.
gen_ai.usage.input_tokens	long	The number of input tokens consumed by this request.
gen_ai.usage.output_tokens	long	The number of output tokens consumed by this request.
gen_ai.usage.reasoning.output_tokens	long	The number of output tokens consumed by Reasoning.
gen_ai.usage.total_tokens	long	Total number of tokens.
session.id	text	The Session ID of the current session.
session.name	text	The Session name of the current session.
tls.app.type	text	Application type identifier, indicating which log application form this Span belongs to.
tls.plugin.version	text	The version number of the observability plugin.
tool.error	text	Error message when tool execution fails.

Torch Log Service