otel-instrumentation

Instrument applications with OpenTelemetry and validate telemetry using Kopai CLI.

1|Updated Feb 5, 2026

Search Tags:#logs #metrics #instrumentation #telemetry #traces #OpenTelemetry #Kopai

Ready to run

npx skills add https://github.com/allthingslinux/atl.services --skill otel-instrumentation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: otel-instrumentation
Source: https://github.com/allthingslinux/atl.services/tree/main/.agents/skills/otel-instrumentation
Command: npx skills add https://github.com/allthingslinux/atl.services --skill otel-instrumentation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Applications often lack standardized telemetry, making it hard to diagnose performance issues and understand behavior. This Skill provides a guided approach to instrumenting apps with OpenTelemetry and validating telemetry with Kopai so you can observe traces, logs, and metrics end-to-end.

Core Features & Use Cases

Instrument multiple signals (traces, logs, metrics) across runtimes (Node, Python, Go, .NET, etc.)
Validate telemetry locally with Kopai to ensure data appears in your observability backend
Use in development and CI workflows to verify instrumentation before production

Quick Start

Instrument your app with the OpenTelemetry SDK according to language.
Start Kopai backend and export OTLP to Kopai collector.
Validate traces/logs/metrics with Kopai CLI: npx @kopai/cli traces search --service my-service --json npx @kopai/cli logs search --service my-service --json npx @kopai/cli metrics discover --json

Frequently Asked Questions about otel-instrumentation

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

FAQPage Schema

How do I instrument an application with OpenTelemetry for traces, logs, and metrics?▼

Instrumenting an application with OpenTelemetry involves adding the SDK to your codebase to capture traces, logs, and metrics, then configuring exporters and environment variables to send telemetry signals to your observability backend.

What is the best way to validate OpenTelemetry telemetry locally before production?▼

Validating OpenTelemetry telemetry locally requires exporting OTLP data to a local collector like Kopai, then using its CLI to search and verify that traces, logs, and metrics appear correctly in your observability backend.

Does OpenTelemetry instrumentation work across multiple runtimes like Node, Python, and Go?▼

Yes, OpenTelemetry instrumentation works across multiple runtimes including Node, Python, Go, and .NET. You configure the language-specific SDK to capture traces, logs, and metrics for end-to-end observability validation.

How do I use Kopai CLI to search for traces and logs?▼

Use the Kopai CLI to search for telemetry by running commands like `npx @kopai/cli traces search --service my-service --json` or `npx @kopai/cli logs search --service my-service --json` to validate exported data.

Can I verify OpenTelemetry instrumentation in CI workflows?▼

Yes, you can verify OpenTelemetry instrumentation in CI workflows by exporting telemetry to a Kopai collector and using the Kopai CLI to programmatically validate that traces, logs, and metrics are generated correctly before production.