otel

Configure an OpenTelemetry collector to route OTLP traces with PII redaction and batching.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/edupazogle/agentic_cockpit --skill otel-edupazogle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: otel
Source: https://github.com/edupazogle/agentic_cockpit/tree/main/.agents/skills/otel
Command: npx skills add https://github.com/edupazogle/agentic_cockpit --skill otel-edupazogle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you configure an OpenTelemetry collector to reliably route traces to your backends while preventing sensitive data from being exported and avoiding common OTLP wiring issues.

Core Features & Use Cases

  • PII redaction before export: Redacts known PII keys from spans and scrubs sensitive patterns (emails, IBANs, DNI/NIE, plate numbers) so exporters never receive raw sensitive values.
  • Dual export pipeline: Configures OTLP/HTTP receivers and routes traces through processors into one or more exporters (e.g., Langfuse OTLP today, Dynatrace OTLP later).
  • Trace pipeline troubleshooting: Provides a concrete end-to-end verification flow to confirm the collector is alive, a test span is accepted, and traces appear in Langfuse.

Quick Start

Apply the otel collector PII redaction and Langfuse OTLP export pipeline, then verify by sending a test span to the collector and confirming it appears in Langfuse.

Frequently Asked Questions about otel

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

FAQPage Schema
How do I configure an OpenTelemetry collector to redact PII before exporting traces?

Configure an OpenTelemetry collector with ordered processors using OTTL to redact known PII keys and scrub sensitive patterns like emails and IBANs. This ensures exporters never receive raw sensitive values from your OTLP traces.

How do I send OTLP traces to Langfuse using an OpenTelemetry collector?

To send OTLP traces to Langfuse, configure an OTLP receiver on ports 4318 or 4317, route traces through memory limiting and batch processors, and set up an authenticated OTLP/HTTP exporter targeting your Langfuse endpoint.

Why are my OTLP traces missing in Langfuse when using an OpenTelemetry collector?

Missing OTLP traces in Langfuse often result from incorrect OTLP wiring. Verify the collector is alive, confirm a test span is accepted by the receiver, and check that your authenticated OTLP/HTTP exporter and batch flushing processors are correctly ordered.

Can I route OTLP traces to multiple backends like Langfuse and Dynatrace with one collector?

Yes, you can configure a dual export pipeline in your OpenTelemetry collector to route OTLP traces through processors into multiple OTLP/HTTP exporters, allowing you to send data to Langfuse today and Dynatrace later.

What patterns can OTTL scrub from OpenTelemetry spans during PII redaction?

OTTL can scrub sensitive patterns from OpenTelemetry spans including emails, IBANs, DNI/NIE, and plate numbers. This regex scrubbing occurs after attribute redaction and before batch flushing to sanitize trace data prior to export.