πŸ“„ File detail

utils/telemetry/logger.ts

🧩 .tsπŸ“ 27 linesπŸ’Ύ 742 bytesπŸ“ text
← Back to All Files

🎯 Use case

This file lives under β€œutils/”, which covers cross-cutting helpers (shell, tempfiles, settings, messages, process input, …). On the API surface it exposes ClaudeCodeDiagLogger β€” mainly types, interfaces, or factory objects. Dependencies touch @opentelemetry. It composes internal code from debug and log (relative imports).

Generated from folder role, exports, dependency roots, and inline comments β€” not hand-reviewed for every path.

🧠 Inline summary

import type { DiagLogger } from '@opentelemetry/api' import { logForDebugging } from '../debug.js' import { logError } from '../log.js' export class ClaudeCodeDiagLogger implements DiagLogger { error(message: string, ..._: unknown[]) {

πŸ“€ Exports (heuristic)

  • ClaudeCodeDiagLogger

πŸ“š External import roots

Package roots from from "…" (relative paths omitted).

  • @opentelemetry

πŸ–₯️ Source preview

import type { DiagLogger } from '@opentelemetry/api'
import { logForDebugging } from '../debug.js'
import { logError } from '../log.js'
export class ClaudeCodeDiagLogger implements DiagLogger {
  error(message: string, ..._: unknown[]) {
    logError(new Error(message))
    logForDebugging(`[3P telemetry] OTEL diag error: ${message}`, {
      level: 'error',
    })
  }
  warn(message: string, ..._: unknown[]) {
    logError(new Error(message))
    logForDebugging(`[3P telemetry] OTEL diag warn: ${message}`, {
      level: 'warn',
    })
  }
  info(_message: string, ..._args: unknown[]) {
    return
  }
  debug(_message: string, ..._args: unknown[]) {
    return
  }
  verbose(_message: string, ..._args: unknown[]) {
    return
  }
}