otel-collector

Name: otel-collector
Availability: InStock
Author: Tsuga

Write and debug OpenTelemetry Collector configurations for traces, metrics, and logs.

2|Updated May 28, 2026

Search Tags:#opentelemetry #sampling #collector yaml #kubernetes deployment #processor ordering #otlp exporters #helm chart

Ready to run

npx skills add https://github.com/tsuga-dev/agent-plugins --skill otel-collector-tsuga-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: otel-collector
Source: https://github.com/tsuga-dev/agent-plugins/tree/main/plugins/telemetry/skills/otel-collector
Command: npx skills add https://github.com/tsuga-dev/agent-plugins --skill otel-collector-tsuga-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you author, verify, and troubleshoot OpenTelemetry Collector configuration when you need correct pipelines, processors, exporters, and deployment patterns.

Core Features & Use Cases

Collector YAML generation & review: Build minimal-to-production configurations for receivers, processors, exporters, and service pipelines across traces/metrics/logs.
Pipeline correctness guidance: Apply ordering constraints such as memory_limiter first, and ensure components are actually wired into pipelines.
Kubernetes deployment path selection: Use the Tsuga Helm chart reference for Kubernetes (and fall back to raw YAML patterns only when Helm is unavailable).

Quick Start

Use the otel-collector skill to produce a working OTel Collector config for Kubernetes by following its Helm-first references and minimal YAML template.

Frequently Asked Questions about otel-collector

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

FAQPage Schema

How do I configure OpenTelemetry Collector pipelines for traces, metrics, and logs?▼

Configuring OpenTelemetry Collector pipelines requires wiring receivers, processors, and exporters together in the service section for traces, metrics, and logs. This ensures data flows properly through the defined components.

What is the correct processor ordering for memory_limiter in an otelcol-contrib configuration?▼

The correct processor ordering places memory_limiter first in the OpenTelemetry Collector pipeline. This ensures memory limits are enforced before any other processing occurs, preventing crashes during traffic spikes.

How do I deploy the OpenTelemetry Collector on Kubernetes using a Helm chart?▼

To deploy the OpenTelemetry Collector on Kubernetes, use the Helm chart reference for deployment topology selection. This Helm-first approach is preferred over raw YAML patterns unless Helm is unavailable in your environment.

How do I configure persistent exporter buffering and sampling in OpenTelemetry Collector?▼

Configure persistent exporter buffering and sampling behavior by defining the respective processor and exporter fields in your OpenTelemetry Collector YAML. This includes setting tail sampling rules and retry queues for OTLP exporters.

What are common operational pitfalls when writing OpenTelemetry Collector YAML?▼

Common OpenTelemetry Collector YAML pitfalls include incorrect processor ordering and leaving components unwired in service pipelines. Ignoring version-specific constraints for otelcol-contrib can also cause configuration failures.