otel-queries

Analyzes Copilot and agentic workflow OpenTelemetry token and execution metrics from JSONL exports.

23.3k|2.0k|Updated May 8, 2020
One-click install
npx skills add https://github.com/dotnet/maui --skill otel-queries
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: otel-queries
Source: https://github.com/dotnet/maui/tree/main/.github/skills/otel-queries
Command: npx skills add https://github.com/dotnet/maui --skill otel-queries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigating Copilot and agentic workflow telemetry is difficult when token usage, model usage, and execution timing data are scattered across OpenTelemetry exports. This Skill provides guidance for querying and interpreting that telemetry so you can understand where tokens and time are spent.

Core Features & Use Cases

  • Local JSONL Inspection: Prefer direct inspection of exported COPILOT_OTEL_FILE_EXPORTER_PATH JSONL files when an OTEL export is available.
  • Token Summarization: Summarize token counts by model, agent step, and request type to identify cost and usage patterns.
  • Diagnostic Interpretation: Treat missing or malformed OTEL records as diagnostic data rather than workflow failures.
  • Use Case: After running an agentic workflow, point the AI at the exported OTEL JSONL file to get a breakdown of token consumption per model and per agent step, plus execution timing anomalies.

Quick Start

Analyze the Copilot OTEL export file and summarize token usage by model and agent step.

Frequently Asked Questions about otel-queries

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze Copilot OpenTelemetry token usage?

Inspect the exported OTEL JSONL file locally and summarize token counts grouped by model, agent step, and request type. This reveals which steps and models consume the most tokens in an agentic workflow.

How to read COPILOT_OTEL_FILE_EXPORTER_PATH JSONL files?

Read the JSONL export line by line, where each line is a separate telemetry record. Parse each record to extract token counts, model identifiers, request types, and execution timing fields for aggregation.

What should I do with missing or malformed OTEL records?

Treat missing or malformed OTEL records as diagnostic data rather than workflow failures. Gaps in telemetry can themselves indicate instrumentation or export issues worth investigating.

Does OTEL telemetry analysis require Android or product validation?

No, workflow-only telemetry analysis changes do not require Android or product validation. The analysis operates purely on exported telemetry data, independent of platform-specific builds.

How do I find slow steps in an agentic workflow?

Examine the execution timing fields in the OTEL export and compare durations across agent steps and request types. Outliers in timing highlight steps that dominate overall workflow latency.