Search the documentation
5 pages for otel_log_tool_details.
Titles and paths first, then pages whose text carries it. Each row opens that page as this site last read it.
Observability with OpenTelemetry
Claude Code CLI · in the page
agent-sdk/observability
…| | `OTEL_LOG_TOOL_DETAILS=1` | Tool input arguments (file paths, shell commands, search patterns) on `claude_code.tool_result` events…
Claude Code changelog
Claude Code CLI · in the page
changelog
…now include `tool_parameters` (bash commands, MCP/skill names) when `OTEL_LOG_TOOL_DETAILS=1` * Worktrees managed by Claude are now left unlocked when the agent finishes, so `git worktree remove`/`…
Set up Claude Code in a monorepo or large codebase
Claude Code CLI · in the page
large-codebases
…the OpenTelemetry [logs exporter](/docs/en/monitoring-usage) and set `OTEL_LOG_TOOL_DETAILS=1` so skill names are recorded verbatim instead of redacted. The [`skill_activated` event](/docs/en/monitori…
Control MCP server access for your organization
Claude Code CLI · in the page
managed-mcp
…Claude Code can record which MCP servers and tools users invoke. Set `OTEL_LOG_TOOL_DETAILS=1` to include MCP server and tool names in tool events, then aggregate them in your collector to see which s…
Monitoring
Claude Code CLI · in the page
monitoring-usage
…| | `OTEL_LOG_TOOL_DETAILS` | Enable logging of tool parameters and input arguments in tool events and trac…