From 031a75a79a3e9ca36b85970034f6247ffbabad21 Mon Sep 17 00:00:00 2001 From: Nitin Misra Date: Thu, 9 Apr 2026 11:51:51 +0530 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20docs(blog):=20replace=20memoryli?= =?UTF-8?q?mitter=20typo=20example=20with=20tail=5Fsmapling?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The previous example used memorylimitter (double 't') but was confusing because the paragraph explains underscore normalization, making readers think the typo was the missing underscore (which is actually valid). Replaced with tail_smapling (transposed letters) for a more obvious and unambiguous typo example. --- .../index.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/blog/2026-04-08-stop-deploying-broken-otel-configs/index.md b/blog/2026-04-08-stop-deploying-broken-otel-configs/index.md index 5e4c4b7..55834e3 100644 --- a/blog/2026-04-08-stop-deploying-broken-otel-configs/index.md +++ b/blog/2026-04-08-stop-deploying-broken-otel-configs/index.md @@ -30,7 +30,7 @@ passed `kubectl apply` without complaint. OpenTelemetry Collector configurations are YAML files. There's no schema, no type system, and no IDE that will tell you that -`memorylimitter` isn't a real processor. You find out when your pipeline +`tail_smapling` isn't a real processor. You find out when your pipeline goes dark and someone starts paging the on-call. The collector ships with `otelcol validate`, which catches syntax errors @@ -107,18 +107,18 @@ and 70+ exporters. The match is underscore-insensitive, so ```yaml showLineNumbers title="otel-collector-config.yaml" processors: # warning-line - memorylimitter: # typo - check_interval: 1s - limit_mib: 512 + tail_smapling: # typo + decision_wait: 10s + num_traces: 100 ``` ```text -[WARN] processors: "memorylimitter" is not a known otelcol-contrib component +[WARN] processors: "tail_smapling" is not a known otelcol-contrib component ``` This is one of the most common config mistakes. The collector loads the config without complaint, the processor does nothing, and your pipeline -runs without memory protection. +runs without tail-based sampling. ### Stage 4: Cross-references