otel-collector

Name: otel-collector
Author: ollygarden

37installs6forks

How to install otel-collector?

ollygarden/opentelemetry-agent-skills/otel-collector

$npx -y skills add ollygarden/opentelemetry-agent-skills --skill otel-collector

Installs into the current project.

Summary

OpenTelemetry Collector component configuration. Use when authoring, reviewing, or debugging Collector YAML for a specific receiver, processor, exporter, connector, or extension — config keys, defaults, validation rules, signal support, stability levels, and component-level gotch

Files · 1

View on GitHub

SKILL.md

1	# OpenTelemetry Collector
2
3	This skill covers the configuration surface of individual OpenTelemetry Collector components. It targets [opentelemetry-collector](https://github.com/open-telemetry/opentelemetry-collector) and [opentelemetry-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib).
4
5	It does not cover OTTL expressions (see `otel-ottl`), declarative SDK configuration (`otel-declarative-config`), or end-to-end pipeline design choices. Reach for those skills when the question is about transformation language, SDK setup, or pipeline composition.
6
7	## Workflow
8
9	1. Identify the component. Find the `type` in the user's config or question (`log_dedup`, `interval`, `otlp`, …). Note that several components were renamed to snake_case across v0.146.0–v0.154.0 with deprecated aliases preserved — see [Recent renames](#recent-renames).
10	2. Load the component page. If the component is in the [Component index](#component-index), read `components/<type>/README.md` first — it carries the metadata, description, main use-cases, and a Details index. Open the linked detail files (`configuration.md`, `verification.md`, `advanced.md`, `quirks.md`, …) only as the question requires; don't load files you don't need.
11	3. If the component is not indexed, say so explicitly and fall back to the upstream README under `processor/<name>/`, `receiver/<name>/`, `exporter/<name>/`, `connector/<name>/`, or `extension/<name>/` in [opentelemetry-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib). Don't invent config keys from memory — Collector components evolve quickly.
12	4. Apply Collector-wide conventions. Named instances (`type/name`), stability levels, and pipeline placement rules in [Collector-wide conventions](#collector-wide-conventions) apply to every component.
13	5. Verify. Run the component page's Verification recipe — `telemetrygen` (see the `otel-telemetrygen` skill) plus a `debug` or `file` exporter — to confirm the component behaves as the docs claim. Alpha- and Development-stability components are common here, and behavior changes between releases. See [Verification harness](#verification-harness) for how to run a recipe end-to-end.
14
15	## Component index
16
17	Each component is a directory under `components/<type>/`. The `File` column points at the lean `README.md` (metadata, description, main use-cases, and a Details index); the full config reference, verification recipe, advanced use-cases, and quirks live in on-demand detail files linked from that README.
18
19	Coverage is intentionally selective. If a component is not indexed here, fall back to the upstream component README for the user's Collector version.
20
21	\| Type \| File \| Kind \| Signals \| Stability \| Summary \|
22	\|------\|------\|------\|---------\|-----------\|---------\|
23	\| `log_dedup` \| `components/log_dedup/README.md` \| processor \| logs \| Alpha \| Deduplicates identical log records over a time window; emits one aggregated log with a count. Renamed from `logdedup` in v0.151.0; alias preserved. \|
24	\| `interval` \| `components/interval/README.md` \| processor \| metrics \| Alpha \| Buffers cumulative monotonic metrics (and optionally gauges/summaries) and emits the latest value once per interval. Delta and non-monotonic sums pass through unchanged. \|
25	\| `tail_sampling` \| `components/tail_sampling/README.md` \| processor \| traces \| Beta \| Buffers whole traces and makes a single keep/drop decision after a wait window via policies. Requires a `load_balancing` layer to scale across instances. \|
26	\| `drain` \| `components/drain/README.md` \| processor \| logs \| Alpha \| Clusters log bodies with the Drain algorithm and annotates each record with a derived template string. \|
27	\| `redaction` \| `components/redaction/README.md` \| processor \| traces, logs, metrics \| Beta (traces), Alpha (logs/metrics) \| Allow/block-list masking or removal of sensitive attribute keys and values, with hashing and URL/DB sanitizers. \|
28	\| `filter` \| `components/filter/README.md` \| processor \| traces, metrics, logs, profiles \| Alpha (traces/metrics/logs), Development (profiles) \| Drops spans, metric data points, log records, and profiles that match OTTL conditions (or legacy metric-name / severity filters). The most direct telemetry-volume lever. \|
29	\| `transform` \| `components/transform/README.md` \| processor \| traces, metrics, logs, profiles \| Beta (traces/metrics/logs), Development (profiles) \| Applies OTTL statements to mutate spans, metric data points, log rec

People who liked this also viewed

6 picks

Type

otel-collector

37installs6forks

View on GitHub

How to install otel-collector?

ollygarden/opentelemetry-agent-skills/otel-collector

$npx -y skills add ollygarden/opentelemetry-agent-skills --skill otel-collector

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# OpenTelemetry Collector
2
3	This skill covers the configuration surface of individual OpenTelemetry Collector components. It targets [opentelemetry-collector](https://github.com/open-telemetry/opentelemetry-collector) and [opentelemetry-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib).
4
5	It does not cover OTTL expressions (see `otel-ottl`), declarative SDK configuration (`otel-declarative-config`), or end-to-end pipeline design choices. Reach for those skills when the question is about transformation language, SDK setup, or pipeline composition.
6
7	## Workflow
8
9	1. Identify the component. Find the `type` in the user's config or question (`log_dedup`, `interval`, `otlp`, …). Note that several components were renamed to snake_case across v0.146.0–v0.154.0 with deprecated aliases preserved — see [Recent renames](#recent-renames).
10	2. Load the component page. If the component is in the [Component index](#component-index), read `components/<type>/README.md` first — it carries the metadata, description, main use-cases, and a Details index. Open the linked detail files (`configuration.md`, `verification.md`, `advanced.md`, `quirks.md`, …) only as the question requires; don't load files you don't need.
11	3. If the component is not indexed, say so explicitly and fall back to the upstream README under `processor/<name>/`, `receiver/<name>/`, `exporter/<name>/`, `connector/<name>/`, or `extension/<name>/` in [opentelemetry-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib). Don't invent config keys from memory — Collector components evolve quickly.
12	4. Apply Collector-wide conventions. Named instances (`type/name`), stability levels, and pipeline placement rules in [Collector-wide conventions](#collector-wide-conventions) apply to every component.
13	5. Verify. Run the component page's Verification recipe — `telemetrygen` (see the `otel-telemetrygen` skill) plus a `debug` or `file` exporter — to confirm the component behaves as the docs claim. Alpha- and Development-stability components are common here, and behavior changes between releases. See [Verification harness](#verification-harness) for how to run a recipe end-to-end.
14
15	## Component index
16
17	Each component is a directory under `components/<type>/`. The `File` column points at the lean `README.md` (metadata, description, main use-cases, and a Details index); the full config reference, verification recipe, advanced use-cases, and quirks live in on-demand detail files linked from that README.
18
19	Coverage is intentionally selective. If a component is not indexed here, fall back to the upstream component README for the user's Collector version.
20
21	\| Type \| File \| Kind \| Signals \| Stability \| Summary \|
22	\|------\|------\|------\|---------\|-----------\|---------\|
23	\| `log_dedup` \| `components/log_dedup/README.md` \| processor \| logs \| Alpha \| Deduplicates identical log records over a time window; emits one aggregated log with a count. Renamed from `logdedup` in v0.151.0; alias preserved. \|
24	\| `interval` \| `components/interval/README.md` \| processor \| metrics \| Alpha \| Buffers cumulative monotonic metrics (and optionally gauges/summaries) and emits the latest value once per interval. Delta and non-monotonic sums pass through unchanged. \|
25	\| `tail_sampling` \| `components/tail_sampling/README.md` \| processor \| traces \| Beta \| Buffers whole traces and makes a single keep/drop decision after a wait window via policies. Requires a `load_balancing` layer to scale across instances. \|
26	\| `drain` \| `components/drain/README.md` \| processor \| logs \| Alpha \| Clusters log bodies with the Drain algorithm and annotates each record with a derived template string. \|
27	\| `redaction` \| `components/redaction/README.md` \| processor \| traces, logs, metrics \| Beta (traces), Alpha (logs/metrics) \| Allow/block-list masking or removal of sensitive attribute keys and values, with hashing and URL/DB sanitizers. \|
28	\| `filter` \| `components/filter/README.md` \| processor \| traces, metrics, logs, profiles \| Alpha (traces/metrics/logs), Development (profiles) \| Drops spans, metric data points, log records, and profiles that match OTTL conditions (or legacy metric-name / severity filters). The most direct telemetry-volume lever. \|
29	\| `transform` \| `components/transform/README.md` \| processor \| traces, metrics, logs, profiles \| Beta (traces/metrics/logs), Development (profiles) \| Applies OTTL statements to mutate spans, metric data points, log rec

People who liked this also viewed

6 picks

Type