opentelemetry

Deploy OpenTelemetry Collector via Helm and configure telemetry pipelines in Kubernetes.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/tense-i/tslink --skill opentelemetry-tense-i
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opentelemetry
Source: https://github.com/tense-i/tslink/tree/main/skills/opentelemetry
Command: npx skills add https://github.com/tense-i/tslink --skill opentelemetry-tense-i

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill simplifies the complex task of setting up and managing OpenTelemetry (OTEL) for comprehensive observability in Kubernetes environments.

Core Features & Use Cases

  • Collector Deployment: Guides you through deploying the OTEL Collector using Helm.
  • Pipeline Configuration: Provides examples for configuring traces, metrics, and logs pipelines.
  • Kubernetes Integration: Details how to enrich telemetry data with Kubernetes metadata.
  • Use Case: You need to collect traces, metrics, and logs from your microservices running on Kubernetes and send them to Prometheus, Loki, and Tempo. This Skill will show you how to deploy the OTEL Collector and configure it to achieve this.

Quick Start

Deploy the OpenTelemetry Collector on Kubernetes using the provided Helm commands.

Frequently Asked Questions about opentelemetry

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

FAQPage Schema
How do I deploy the OpenTelemetry Collector on Kubernetes using Helm?

Deploy the OpenTelemetry Collector on Kubernetes by using the provided Helm commands to install the collector, which establishes a centralized, vendor-neutral pipeline for telemetry data collection across your cluster.

What is the best way to collect traces, metrics, and logs in Kubernetes?

The best way to collect traces, metrics, and logs in Kubernetes is configuring OpenTelemetry pipelines, which centralize telemetry data processing and route it to observability backends like Prometheus, Loki, and Tempo.

How do I configure OpenTelemetry pipelines to send data to Prometheus, Loki, and Tempo?

Configure OpenTelemetry pipelines by defining receivers, processors, and exporters in the collector configuration to route traces, metrics, and logs directly to backends like Prometheus, Loki, and Tempo.

Can I enrich telemetry data with Kubernetes metadata using OpenTelemetry?

Yes, you can enrich telemetry data with Kubernetes metadata using the OpenTelemetry Collector, which adds resource attributes to traces, metrics, and logs for better context in observability backends.

Why use a vendor-neutral telemetry collector in cloud-native environments?

Use a vendor-neutral telemetry collector like OpenTelemetry to avoid lock-in, standardizing how you collect and process traces, metrics, and logs before exporting them to backends like Prometheus, Loki, and Tempo.

Does the OpenTelemetry Collector support centralized logging and metrics collection for microservices?

Yes, the OpenTelemetry Collector supports centralized logging and metrics collection for microservices, processing telemetry data through configurable pipelines before exporting to backends like Loki and Prometheus.