OpenTelemetry Instrumentation FAQs

Question 1

Which operations should I instrument using this skill?

Accepted Answer

The skill focuses on system boundaries such as network calls, I/O, and queue operations rather than instrumenting every internal function, which helps reduce noise in your traces.

Question 2

Can I use this for testing my tracing implementation?

Accepted Answer

Yes, the skill provides patterns for testing instrumentation using in-memory exporters and SimpleSpanProcessor to assert on span names, attributes, and status.

Question 3

What is the OpenTelemetry skill for Claude Code?

Accepted Answer

It is a specialized capability that helps Claude implement standardized instrumentation conventions for distributed tracing, ensuring your code follows global observability best practices.

Question 4

Does this skill support custom attribute names?

Accepted Answer

This skill prioritizes official OpenTelemetry semantic conventions to ensure data compatibility and consistency, discouraging the invention of non-standard attribute names.

Question 5

How does it handle error reporting in spans?

Accepted Answer

It follows the OTel convention of setting status to 'Error' only when necessary (treating 'Unset' as success) and uses RecordError to add span events without redundant status changes.

OpenTelemetry Instrumentation

Key Features

Use Cases

OpenTelemetry Instrumentation

Key Features

Use Cases