chore: Include Default Engine Open Telemetry Components in OTel Engine

[blewis12]

As discussed, we will also include open telemetry components that are wrapped in the Default Engine in the OTel Engine, this means users don't lose any functionality - and clears the space for a migration path in the future. This PR adds all upstream components found in the default engine over to the builder manifest for the otel engine, minus a couple which are addressed in this comment

There are two other components added as well (the grafanacloud connector, and hostmetrics receiver), that are included in the GC "new connection" -> "OpenTelemetry collector" wizard flow, and so would make sense to also have work with our own distribution

I've also made sure the components are alphabetical, just makes it a tad easier to read

[github-actions]

🔍 Dependency Review

Below is a review of dependency changes detected in the provided diff, focused on Go module updates and replacements.

github.com/open-telemetry/opentelemetry-collector-contrib/receiver/filestatsreceiver v0.142.0 -> github.com/grafana/opentelemetry-collector-contrib/receiver/filestatsreceiver v0.0.0-20260126095124-0af81a9e8966

• Status: ⚠️ Needs Review

Summary:

• This change pins a forked module for filestatsreceiver to address a FreeBSD build tags issue. No API or behavior changes are implied for consumers; the fork is intended to be build-only fix.
• No code changes in your repository should be required. The consumer code imports and the factory registration remain the same.
• Evidence (from the diff’s comments):
  • “Fork to grafana repo to address issue with freebsd build tags. This can be removed once [filestatsreceiver]: Not able to build agent with builder with filestatsreceiver for freebsd open-telemetry/opentelemetry-collector-contrib#42645 is fixed”

Impacted files (replace directive added in multiple modules):

• collector/go.mod
• extension/alloyengine/go.mod
• go.mod (repo root)

Relevant snippet:

+ replace github.com/open-telemetry/opentelemetry-collector-contrib/receiver/filestatsreceiver => github.com/grafana/opentelemetry-collector-contrib/receiver/filestatsreceiver v0.0.0-20260126095124-0af81a9e8966

Code changes required: None.

Suggested follow-up (when upstream is fixed and released):

- replace github.com/open-telemetry/opentelemetry-collector-contrib/receiver/filestatsreceiver => github.com/grafana/opentelemetry-collector-contrib/receiver/filestatsreceiver v0.0.0-20260126095124-0af81a9e8966
+ // Remove the replace after upstream fix for FreeBSD build tags is available

Multiple OpenTelemetry Collector Contrib components v0.142.0 -> v0.142.0 (promoted from indirect to direct)

• Status: ✅ Safe

Summary:

• A large number of contrib modules were promoted from indirect to direct requirements at the same version (v0.142.0).
• This aligns with the added imports and factory registrations in collector/components.go and the enriched builder-config.yaml.
• Since the version did not change (v0.142.0 -> v0.142.0), there are no intervening releases to evaluate and no API changes to handle. The additions are to ensure the modules are retained and available for the custom distribution.

Affected modules (non-exhaustive list, all at v0.142.0):

• Connectors: countconnector, servicegraphconnector, spanmetricsconnector, grafanacloudconnector
• Exporters: awss3exporter, faroexporter, fileexporter, googlecloudexporter, googlecloudpubsubexporter, kafkaexporter, loadbalancingexporter, prometheusexporter, prometheusremotewriteexporter, splunkhecexporter, syslogexporter, zipkinexporter
• Extensions: basicauthextension, bearertokenauthextension, headerssetterextension, healthcheckextension, jaegerremotesampling, oauth2clientauthextension, pprofextension, sigv4authextension, storage/filestorage
• Processors: attributesprocessor, cumulativetodeltaprocessor, deltatocumulativeprocessor, filterprocessor, groupbyattrsprocessor, intervalprocessor, k8sattributesprocessor, metricstarttimeprocessor, probabilisticsamplerprocessor, resourceprocessor, resourcedetectionprocessor, spanprocessor, tailsamplingprocessor, transformprocessor
• Receivers: awscloudwatchreceiver, awsecscontainermetricsreceiver, awss3receiver, cloudflarereceiver, datadogreceiver, faroreceiver, filelogreceiver, filestatsreceiver (replaced via fork), fluentforwardreceiver, googlecloudpubsubreceiver, hostmetricsreceiver, influxdbreceiver, jaegerreceiver, kafkareceiver, solacereceiver, splunkhecreceiver, syslogreceiver, tcplogreceiver, vcenterreceiver, zipkinreceiver

Evidence:

• components.go now imports and registers factories for the above modules.
• go.mod moves these dependencies from indirect to direct at the same version (v0.142.0).
• No version change, no API changes required.

Code changes required: None.

Notes

• Net-new modules used by the code (e.g., github.com/open-telemetry/opentelemetry-collector-contrib/connector/grafanacloudconnector) were added at v0.142.0; since these are additions rather than upgrades, there is no upgrade-related breakage to review here.
• The comment regarding the Datadog exporter in builder-config.yaml indicates it is intentionally disabled for now:
  • “TODO: Address this as part of https://github.com/grafana/alloy/issues/5348”
• The existing replaces for controller-runtime (sigs.k8s.io/controller-runtime v0.20.4) and runc are unchanged in behavior from a dependency-upgrade perspective.

[blewis12]

making a link to #5247 -> since this is a stepping stone for that proposal

[blewis12]

hmm, looks like the file stat receiver is not compatible with FreeBSD, I can see we've also got build restrictions in our own component. I see two options:

1. Modify our generation logic to somehow exclude this component from the build(?)
2. Not include this component in our first iteration -> i'm tempted to do this and track the issue for the sake of itera
   ting. Maybe there's a change that can be made upstream to help in this situation, but we can investigate that separately

edit: actually - it might not be this component that's causing an issue, looking into it more

[blewis12]

OK - had a further look into this, the reason we saw failures is because Alloy wraps upstream components which are not compatible with FreeBSD (which is not listed as a supported platform upstream). There were two components brought in from the default engine with this problem:

• Filestatreceiver: I created a branch in our fork of the collector-contrib to address this since the fix is simple enough, and there is an upstream issue tracking it with recent comments and interest in getting it fixed
• Datadogexporter: I have removed this for now since I couldn't find any upstream issue for it. We could create a fork to address this (even if the fork just implements a noop component for FreeBSD), but I want to track this as well as discussion of this subject in this issue

[Copilot]

Pull request overview

Expands the OTel Engine’s embedded OpenTelemetry Collector distribution to include the upstream components already wrapped by the Default Engine (plus grafanacloud connector and hostmetrics receiver), preserving functionality and enabling a smoother migration path.

Changes:

• Adds a broad set of OTel Contrib receivers/processors/exporters/extensions/connectors to the OTel Engine builder manifest and generated factories list.
• Introduces a replace to a Grafana fork of filestatsreceiver to address FreeBSD build tag issues (tracked via upstream issue).
• Updates Go module metadata (go.mod/go.sum) across the root, extension module, and collector module to reflect the new dependency set.

Reviewed changes

Copilot reviewed 6 out of 9 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
go.mod	Adds generated replace for filestatsreceiver fork to address FreeBSD build tags.
go.sum	Updates module checksums reflecting the filestatsreceiver fork.
extension/alloyengine/go.mod	Mirrors the generated replace for filestatsreceiver fork.
extension/alloyengine/go.sum	Updates checksums reflecting the filestatsreceiver fork.
dependency-replacements.yaml	Adds the new replacement rule so it propagates through the generation pipeline.
collector/go.mod	Adds direct requirements for newly included OTel Contrib components; includes filestatsreceiver replace.
collector/go.sum	Updates checksums for newly included components (e.g., grafanacloud connector, hostmetrics receiver, forked filestatsreceiver).
collector/components.go	Updates generated factory registration to include the expanded component set.
collector/builder-config.yaml	Updates the OTel Collector Builder manifest to include the expanded component set and the new replace.

[thampiotr]

Seems like we are adding:

• hostmetricsreceiver - but I don't see it in Alloy's otelcol.* ?
• grafanacloudconnector - I guess this is fine :)

Seems like we are not adding:

• otelcol.receiver.opencensus - because it's been deprecated: open-telemetry/opentelemetry-collector-contrib#36791
• otelcol.exporter.datadog - blocked on FreeBSD issue
• otelcol.connector.host_info - is this replaced by grafanacloudconnector?

[thampiotr]

Discussed the concerns on Slack. LGTM!

[blewis12]

@thampiotr exactly yeah, I didn't catch otelcol.receiver.opencensus though - but since it's deprecated I will leave it out