[HDX-4029] Support all OTel Collector Contrib components in builder-config.yaml

[wrn14897]

Summary

Update packages/otel-collector/builder-config.yaml to include all components from the upstream opentelemetry-collector-contrib distribution.

Previously, only the HyperDX-specific subset of components was included in the OCB builder manifest. If a user provided a custom OTel config referencing a component not in our list (e.g. kafkareceiver, elasticsearchexporter, k8sattributesprocessor), the collector binary would fail to load.

This change adds the full set of:

• Receivers (~100 contrib components)
• Processors (~28 contrib components)
• Exporters (~48 contrib components)
• Extensions (~43 contrib components, including encoding and observer sub-packages)
• Connectors (~12 contrib components)
• Configuration Providers (~4 contrib providers)

All existing HyperDX-required components remain included. The version placeholder pattern (__OTEL_COLLECTOR_VERSION__ / __OTEL_COLLECTOR_CORE_VERSION__) is preserved for Docker build-time substitution. Components are sorted alphabetically within each section for maintainability.

How to test locally or on Vercel

1. Build the OTel Collector Docker image — the builder-config.yaml should be valid and OCB should resolve all listed modules
2. Provide a custom OTel config that references a previously-unsupported component (e.g. kafkareceiver) and verify it loads successfully
3. Verify existing HyperDX OTel pipeline still functions (otlp receiver, batch processor, clickhouse exporter, etc.)

References

• Linear Issue: https://linear.app/clickhouse/issue/HDX-4029
• Related PRs: 28f374e (HDX-3929 OCB migration)
• Upstream contrib builder-config: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/cmd/otelcontribcol/builder-config.yaml

[changeset-bot]

🦋 Changeset detected

Latest commit: b104ba3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@hyperdx/otel-collector	Minor
@hyperdx/api	Minor
@hyperdx/app	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hyperdx-oss	Ready	Preview, Comment	Apr 15, 2026 3:51am

[github-actions]

🔴 Tier 4 — Critical

Touches auth, data models, config, tasks, OTel pipeline, ClickHouse, or CI/CD.

Why this tier:

• Critical-path files (1):
  • packages/otel-collector/builder-config.yaml

Review process: Deep review from a domain expert. Synchronous walkthrough may be required.
SLA: Schedule synchronous review within 2 business days.

Stats

• Files changed: 2
• Lines changed: 355
• Branch: warren/HDX-4029-otel-contrib-all-components
• Author: wrn14897

To override this classification, remove the review/tier-4 label and apply a different review/tier-* label. Manual overrides are preserved on subsequent pushes.

[github-actions]

E2E Test Results

✅ All tests passed • 133 passed • 3 skipped • 970s

Status	Count
✅ Passed	133
❌ Failed	0
⚠️ Flaky	2
⏭️ Skipped	3

Tests ran across 4 shards in parallel.

View full report →

[github-actions]

PR Review

• ⚠️ Binary size and CI build time will increase significantly (from ~15 to 200+ components) → Acceptable tradeoff per the PR intent, but worth verifying the Docker image size regression doesn't exceed deployment limits and CI timeout budgets before merging
• ⚠️ No auto-sync mechanism — this manifest was hand-copied from upstream and will drift as contrib adds/removes components → Consider adding a comment or script reference noting how to regenerate (e.g., a link to the upstream manifest + a note to run a diff periodically)
• ✅ Version placeholder usage is consistent: __OTEL_COLLECTOR_VERSION__ for all core+contrib components, __OTEL_COLLECTOR_CORE_VERSION__ for confmap providers only — matches the sed substitution in the Dockerfile
• ✅ Changeset correctly marks this as a minor bump for @hyperdx/otel-collector
• ✅ All previously included HyperDX-required components (clickhouseexporter, otlpreceiver, fluentforwardreceiver, resourcedetectionprocessor, etc.) are still present