// product · available now
OpenTelemetry Collector Recipes
tested configs for sampling, PII redaction & Kubernetes
Production OpenTelemetry Collector configs, validated and tested end-to-end in Docker. Tail sampling, PII redaction, Kubernetes, GenAI.
● instant download · secure checkout by Gumroad
// tested
Tested, not just written
Every release runs its full test suite against real tooling before it ships.
Every config passes otelcol-contrib validate on the pinned 0.161.0 collector
Every recipe runs in Docker (non-root, read-only FS) with assertions on its output
PII redaction proven: emails, card numbers, auth headers, API keys and IPs removed
Tail sampling keeps all error and slow traces; load balancing never splits a trace
Persistent queue survives a backend outage and a collector restart without data loss
Zero deprecation warnings, enforced by the test suite; Helm & Operator schema-checked
// pricing
One-time purchase, three tiers
Pay once, keep the files. Each tier includes everything in the tier before it.
Starter
Teams starting with OpenTelemetry
$19USD
- 5 core recipes: production agent, host metrics, logs to Loki, traces to Tempo/Jaeger, Prometheus scrape
- 5-minute Docker Compose quickstart
- 30 days of updates
Pro
Platform and SRE teams running a gateway tier
$49USD
- 16 recipes incl. load-balanced gateway with tail sampling
- PII & secret redaction, cost reduction, Kubernetes attributes
- Span metrics + service graph, multi-tenant routing, GenAI/LLM telemetry
- Persistent queue, mTLS, collector self-monitoring + alert rules
- 1 year of updates
Studio
Consultants, agencies, Kubernetes platform teams
$99USD
- Helm values for the official chart: DaemonSet agent + Deployment gateway
- OpenTelemetry Operator resources with auto-instrumentation
- One-command lab: collector + Prometheus + Loki + Tempo + Grafana
- Sizing & tuning guide, client-use license
- 1 year of updates
// contents
16 recipes
- Production agentStarter+
- Host metrics → PrometheusStarter+
- File logs → Loki (OTLP)Starter+
- Traces → Tempo / JaegerStarter+
- Prometheus scrape → OTLPStarter+
- Agent with trace-ID load balancingPro+
- Gateway tail samplingPro+
- PII & secret redactionPro+
- Cost reductionPro+
- Kubernetes attributesPro+
- Span metrics + service graphPro+
- Multi-tenant routingPro+
- GenAI / LLM telemetryPro+
- Persistent queuePro+
- mTLS agent → gatewayPro+
- Collector self-telemetryPro+
// compatibility
Works with your stack
- OpenTelemetry Collector Contrib 0.161.0
- Prometheus, Grafana Mimir, Loki, Tempo, Jaeger v2
- Any OTLP-compatible vendor backend
- Docker Compose or plain binary
- Kubernetes, Helm & OpenTelemetry Operator (Studio)
// faq
Questions
+Which collector version?
All recipes are pinned to otel/opentelemetry-collector-contrib 0.161.0 and use the current snake_case component names. The compatibility matrix lists component stability and tested backend versions.
+Do I need Kubernetes?
No. Every recipe except Kubernetes attributes runs with Docker Compose or as a plain binary. Studio adds Helm and Operator deployments.
+Will it work with my vendor?
The recipes export standard OTLP. Point the endpoint variable at your vendor's OTLP endpoint and add its auth header.
+Is the PII redaction compliance-grade?
It is a tested, strong layer of defence for traces and logs, not a legal guarantee. The README shows how to test it against your own data formats.
+Can I use it for client work?
Starter and Pro are licensed for your own organization. Client and agency use requires Studio.
+Refunds?
If a recipe doesn't work with the pinned collector version and the troubleshooting guide doesn't fix it, contact us within 14 days for a refund.
Stop debugging collector YAML in production.
Questions first? Email hello@fractaltechware.com