December 6, 2025
Build-a-Collector, some assembly required
OpenTelemetry Distribution Builder
Build-your-own telemetry gets a cheat code — early users exhale
TLDR: OpenTelemetry Distribution Builder lets you pick parts in a simple file and auto-create installers and releases for your own monitoring tool. Early reaction: it finally eases the pain, with predictable side-eye over “another builder,” YAML fatigue, and trusting automated GitHub releases—still a big quality-of-life win.
Developers are buzzing over the OpenTelemetry Distribution Builder, a new “build-your-own” kit for monitoring tools that promises to turn a simple checklist (a manifest file) into ready-to-install packages and auto-made releases. If OpenTelemetry is the open standard for app health data, this is the Lego box to snap your own set together. The first public vibe check is glowing: pveierland says custom builds used to be a slog, but this tool “made it much easier,” especially when you need a special mix of parts. That’s the energy—relief and a big “finally.”
But the sidelines are already crackling with familiar debates. Some cheer the one-click GitHub Actions setup as “press tag, get release,” while skeptics mutter about trusting robots with production builds. Others roll their eyes at yet another YAML (that manifest file) but admit the payoff—multi-platform installers for popular Linux flavors—hits real pain points. A few wonder if this is “another builder” on top of the official one (it is—built on the OpenTelemetry Collector Builder), and whether that’s smart layering or tool sprawl. Meanwhile, meme lords are calling it “manifesto-driven telemetry,” and ops folks are bookmarking the repo like it’s Friday. Drama light, usefulness heavy—so far.
Key Points
- •The tool builds custom OpenTelemetry Collector distributions from a manifest.yaml, automating packaging and releases.
- •It leverages OpenTelemetry Collector Builder (OCB) to produce multi-platform binaries (amd64, arm64).
- •Generated packages include APK, DEB, RPM, and TAR.GZ, following OpenTelemetry community best practices.
- •CI/CD integration is provided via GitHub Actions, with automated versioned releases and artifacts published to GitHub Releases.
- •Builds can be run locally, via Docker, or using Google Cloud Build; development prerequisites include Python 3, Docker, and Make.