hiddink-harness:monitoring-setup

Configure OpenTelemetry environment variables for Claude Code usage metrics and event logging.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/hiddink-ai/hiddink-harness --skill hiddink-harness-monitoring-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hiddink-harness:monitoring-setup
Source: https://github.com/hiddink-ai/hiddink-harness/tree/main/templates/skills/monitoring-setup
Command: npx skills add https://github.com/hiddink-ai/hiddink-harness --skill hiddink-harness-monitoring-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the lack of visibility into AI agent performance and cost by providing a standardized way to toggle OpenTelemetry metrics and logs for Claude Code.

Core Features & Use Cases

  • Usage Tracking: Monitor session costs, token usage, and active time directly in your terminal.
  • Event Logging: Capture tool decisions, API requests, and errors for debugging agent behavior.
  • Trajectory Export: Enable advanced span-based analysis for agent evaluation frameworks.
  • Use Case: A developer needs to track the cost of a long-running refactoring task to ensure it stays within budget, or a team lead needs to debug why a specific tool call is failing during a complex workflow.

Quick Start

Use the monitoring-setup skill to enable OpenTelemetry console monitoring for your current session.

Frequently Asked Questions about hiddink-harness:monitoring-setup

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

FAQPage Schema
How do I enable OpenTelemetry metrics for Claude Code?

To enable OpenTelemetry metrics for Claude Code, you configure specific environment variables within your local .claude/settings.local.json file, which injects telemetry export settings to track usage and log events.

What is OpenTelemetry trajectory analysis used for in AI agent development?

OpenTelemetry trajectory analysis is used to capture tool decisions, API requests, and errors for debugging agent behavior, enabling advanced span-based evaluation of AI performance across development sessions.

Can I track token usage and session costs directly in my terminal?

Yes, you can track token usage and session costs directly in your terminal by enabling OpenTelemetry console monitoring, which provides standardized visibility into active time and expenses.

Does enabling OpenTelemetry telemetry require modifying settings.local.json?

Yes, enabling telemetry requires local configuration of the .claude/settings.local.json file to properly inject the OpenTelemetry environment variables needed for exporting usage metrics and event logs.

What is the best way to debug failing tool calls during a complex workflow?

The best way to debug failing tool calls is to enable OpenTelemetry event logging, which captures tool decisions and API requests to provide visibility into why specific operations fail during complex workflows.