跳到主内容
智客 ZICQ

技能库 智客分类:运维与云 otel-collector

Otel Collector

配置和部署"开口遥测"收集器专家指导. 在安装收集器管道、配置接收器、出口商或处理器、向Kubernetes或Docker部署收集器或向Dash0转发遥测器时使用。 触发涉及采集器、管道、OTLP接收器、出口商或Dash0采集器设置的请求.

717 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

配置和部署 OpenTeleometry 收集器的专家指南

何时用

设置一个收集器管道,配置接收器、出口商或处理器,向Kubernetes或Docker部署一个收集器,或向Dash0发送遥测。 触发涉及收集器、管道、OTLP接收器、出口商或Dash0收集器设置的请求

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:OpenTelemetry Collector configuration guide、Rules、Key principles、Quick start、Configuration workflow、Quick reference。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Expert guidance for configuring and deploying the OpenTelemetry Collector. Use when setting up a Collector pipeline, configuring receivers, exporters, or processors, deploying a Collector to Kubernetes or Docker, or forwarding telemetry to Dash0. Triggers on requests involving collector, pipeline, OTLP receiver, exporter, or Dash0 collector setup.

OpenTelemetry Collector configuration guideRulesKey principlesQuick startConfiguration workflowQuick referenceOfficial documentation

· 许可:Apache-2.0

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
otel-collector
description
Expert guidance for configuring and deploying the OpenTelemetry Collector. Use when setting up a Collector pipeline, configuring receivers, exporters, or processors, deploying a Collector to Kubernetes or Docker, or forwarding telemetry to Dash0. Triggers on requests involving collector, pipeline, OTLP receiver, exporter, or Dash0 collector setup.
许可
Apache-2.0
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「otel-collector」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-b149587abc186e49-%E5%A5%A5%E7%89%B9%E5%B0%94%E6%94%B6%E9%9B%86%E5%99%A8.html
请存为 .cursor/skills/otel-collector/SKILL.md 或 .claude/skills/otel-collector/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/dash0hq/agent-skills' --list

npx skills add 'https://github.com/dash0hq/agent-skills' --skill 'otel-collector'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: otel-collector description: Expert guidance for configuring and deploying the OpenTelemetry Collector. Use when setting up a Collector pipeline, configuring receivers, exporters, or processors, deploying a Collector to Kubernetes or Docker, or forwarding telemetry to Dash0. Triggers on requests involving collector, pipeline, OTLP receiver, exporter, or Dash0 collector setup. license: Apache-2.0 metadata: author: dash0 version: '1.0.0' workflow_type: 'advisory' supports-traces: "true" supports-metrics: "true" supports-logs: "true"

OpenTelemetry Collector configuration guide

Expert guidance for configuring and deploying the OpenTelemetry Collector to receive, process, and export telemetry.

Rules

| Rule | Description | |------|-------------| | receivers | Receivers — OTLP, Prometheus, filelog, hostmetrics | | exporters | Exporters — OTLP/gRPC to Dash0, debug, authentication | | processors | Processors — memory limiter, resource detection, ordering, sending queue | | pipelines | Pipelines — service section, per-signal configuration, connectors | | deployment | Deployment — agent vs gateway patterns, deployment method selection | | dash0-operator | Dash0 Kubernetes Operator — automated instrumentation, Collector management, Dash0 export | | collector-helm-chart | Collector Helm chart — presets, modes, image selection | | opentelemetry-operator | OpenTelemetry Operator — Collector CRD, auto-instrumentation, sidecar | | raw-manifests | Raw Kubernetes manifests — DaemonSet, Deployment, RBAC, Docker Compose | | sampling | Sampling — head, tail, load balancing | | red-metrics | RED metrics — span-derived request rate, error rate, duration histograms | | custom-distributions | Custom distributions — building a stripped-down Collector binary with OCB |

Key principles

  • Processor ordering matters. Place memory_limiter first in every pipeline. Use the exporter's sending_queue with file_storage instead of the batch processor. Incorrect ordering causes memory exhaustion or data loss.
  • One pipeline per signal type. Define separate pipelines for traces, metrics, and logs. Mixing signals in a single pipeline breaks processing and causes runtime errors.
  • Every declared component must appear in a pipeline. The Collector rejects configurations that declare receivers, processors, or exporters not referenced by any pipeline.
  • Consistent resource enrichment across pipelines. Apply processors that enrich resource attributes like resourcedetection and k8sattributes to every signal pipeline (traces, metrics, and logs), not just one. If one pipeline enriches telemetry with k8s.namespace.name or host.name but another does not, correlation between signals is compromised by incomplete metadata.
  • Memory safety is non-negotiable. Always configure memory_limiter in production. Without it, a burst of telemetry can cause the Collector to OOM and crash.

Quick start

Minimal working configuration: OTLP receiver → memory limiter → OTLP/gRPC exporter to Dash0.

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
      http:
        endpoint: 0.0.0.0:4318

processors:
  memory_limiter:
    check_interval: 1s
    limit_mib: 400
    spike_limit_mib: 100

exporters:
  otlp:
    endpoint: ingress.eu-west-1.aws.dash0.com:4317
    headers:
      Authorization: "Bearer ${env:DASH0_TOKEN}"
    sending_queue:
      enabled: true
      storage: file_storage

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [memory_limiter]
      exporters: [otlp]
    metrics:
      receivers: [otlp]
      processors: [memory_limiter]
      exporters: [otlp]
    logs:
      receivers: [otlp]
      processors: [memory_limiter]
      exporters: [otlp]

See exporters for full authentication and queue configuration, and processors for adding resource detection.

Configuration workflow

  1. Write config — define receivers, processors, and exporters; wire them in service.pipelines.
  2. Validate locally — run otelcol validate --config=config.yaml to catch structural errors before deployment.
  3. Deploy — choose a deployment method from the deployment rule (Helm, Operator, raw manifests, or Docker Compose).
  4. Verify — add the debug exporter to a pipeline temporarily and inspect stdout to confirm telemetry is flowing; then remove it before going to production.

Quick reference

| What do you need? | Rule | |--------------------|------| | Accept OTLP telemetry from applications | receivers | | Scrape Prometheus endpoints | receivers | | Collect log files or host metrics | receivers | | Send telemetry to Dash0 | exporters | | Configure retry, queue, or compression | exporters | | Set processor ordering | processors | | Add Kubernetes or cloud metadata | processors | | Wire receivers → processors → exporters | pipelines | | Complete working configuration | pipelines | | Validate the pipeline with the debug exporter | collector-helm-chart, opentelemetry-operator, raw-manifests, or dash0-operator | | Deploy as DaemonSet or Deployment | raw-manifests | | Deploy with Helm | collector-helm-chart | | Deploy with the OTel Operator | opentelemetry-operator | | Deploy with the Dash0 Operator | dash0-operator | | Auto-instrument applications in Kubernetes | opentelemetry-operator or dash0-operator | | Local development with Docker Compose | raw-manifests | | Reduce trace volume | sampling | | Keep errors and slow traces, drop the rest | sampling | | Redact sensitive data in the pipeline | processors | | Generate RED metrics from traces | red-metrics | | Build a custom Collector binary | custom-distributions |

Official documentation

相关技能

运维与云

Docker Essentials

用于容器管理,图像操作,调试的基本道克命令和工作流程.

运维与云

Find Skills

从开放的代理技能生态系统中发现并安装技能. 使用时:(1)用户问"我如何做X",X可能拥有现有技能,(2)用户说"为X找到技能"或"是否为X有技能",(3)用户问"你能否做X",X是专门能力,(4)用户想扩展代理能力,(5)用户想搜索工具,模板,或工作流程,(6)用户提到他们希望…

运维与云

Microsoft Foundry

构建,部署,评价,优化,微调,管理微软创始代理,模型,资源最终结束. 用法:铸造、azd ai代理、azd 提供/部署、托管代理脚手架/开发/运行/部署/拖放、即时代理创建、创建代理、更新代理、添加代理工具、援引代理、代理.yaml、评估代理、批量活化、连续活化、持续监测、代理C…

运维与云

Azure Deploy

执行已有.azure/部署计划.md和基础设施文件的ALREADY-PREPARED应用程序的Azure部署。 当用户向 CREATE 请求新应用程序时, 请不要使用此技能 。 这种技能运行了 azd上行, azd 部署, trarraform 应用, 和 az 部署命令带有内置…