Skip to content

📝 docs(blog): replace memorylimitter typo example with tail_smapling #190

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nitinstp23 merged 2 commits into from
Apr 9, 2026
Merged

📝 docs(blog): replace memorylimitter typo example with tail_smapling #190

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
031a75a
📝 docs(blog): replace memorylimitter typo example with tail_smapling
nitinstp23 Apr 9, 2026
89d598b
Merge branch 'main' into fix/blog-otel-typo-example
nitinstp23 Apr 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions blog/2026-04-08-stop-deploying-broken-otel-configs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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

Expand Down
Loading