Telemetry

API usage and tool execution history for your workspace API keys.

Source: https://runstack.engineer/docs/telemetry

Telemetry gives you execution visibility for MCP requests authenticated with your API keys. Open Settings → Workspace → Logs to inspect request history, summary metrics, and a 14-day activity chart.

Summary cards

Card	What it counts
Total requests	All logged MCP requests
Executions	Requests where `execute_tool` ran (`counted: true`)
Errors	Requests with `status: error`
Success rate	`(total - errors) / total` as a percentage

Activity chart

A 14-day line chart with three series:

Requests — all MCP calls
Executions — execute_tool calls only
Errors — failed requests

Recent activity table

Each row in the activity log includes:

Column	Description
Time	When the request occurred
Method	MCP JSON-RPC method (e.g. `tools/call`)
Tool	MCP tool name (`execute_tool`, `search_tools`, etc.) or —
API key	The key name used for the request
Status	`success` or `error`
Counted	Whether the request counted toward your key's execution limit

What counts as an execution

Only MCP tools/call where the tool name is execute_tool increments the key's usage count and appears as Counted in the log.

These methods are logged but not counted:

search_tools
check_authentication
initiate_connection

Log retention

The server retains up to 50 log entries per user (older entries are pruned). The Logs UI loads up to 500 entries via the API.

API

GET /api/usage-logs?limit=500&apiKeyId=<optional>
Authorization: Clerk session

Filter by apiKeyId to see activity for a specific key.

Related settings

Create and manage keys in API Keys
Workspace Guardrails apply to counted executions
Toolkit connections for execution come from the active workspace — see Orgs and Workspaces