Repository navigation
Conversation
pbusko
reviewed
Sep 1, 2026
pbusko
reviewed
Sep 1, 2026
jorbaum
force-pushed
the
add-otel-collector
branch
from
September 1, 2026 15:41
4b25285 to
8ce1101
Compare
jorbaum
force-pushed
the
add-otel-collector
branch
from
September 25, 2026 11:36
8ce1101 to
f0a11c0
Compare
Contributor
Author
|
With this next try I am now using the upstream image from otel/opentelemetry-collector-contrib . However, I also adapted the loggregator-agent release helm chart so it includes the otel-collector. This is necessary as the forwarder-agent currently only forwards to localhost. Alternatively one could adapt the forwarder agent to send OTLP to other locations as well. However, when we think about going that route we could also add a proper cloudfoundry loggregator envelope receiver to the otel-collector as well. I consider this out of scope for now. |
jorbaum
changed the title
Contributor
Author
Does it make sense to add a test for that? |
5 of 10 tasks
Uses upstream helm chart but our own otel distro * Also configures healthcheck for otel collector
otel-collector is still experimental and should not be deployed by default
Re-use the upstream otel/opentelemetry-collector-contrib image instead of the CF-maintained distro. Drops the cross-repo deps on cf-k8s-releases#230 and otel-collector-release#263 — the contrib image already bundles health_check. - Replace CF distro image + custom command with otel/opentelemetry-collector-contrib - Add mTLS OTLP receiver (otlp/cf-internal-local, grpc 0.0.0.0:4317, TLS 1.3) mirroring the BOSH otel-collector-release job, using all-in-one-tls secret - Mount all-in-one-tls at /etc/otel/certs (extraVolumes/extraVolumeMounts) - Add otlp exporter targeting configurable exportEndpoint (default: host.docker.internal:4317) - Document config lineage in comment pointing to upstream chart values.yaml - Drop imageTag from versions.yaml; add exportEndpoint value Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
forwarder-agent only sends to localhost right now
Moved enabled and exportEndpoint under otelCollector in values.yaml.gotmpl
...now that we have enabled forwarding to external endpoints in forwarder agent.
jorbaum
force-pushed
the
add-otel-collector
branch
from
October 13, 2026 15:49
712d8b7 to
aac58b4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the otel-collector to kind deployment as its commonly used in cloudfoundry already. Deployment of otel-collector is opt-in for now.
Requires cloudfoundry/cf-k8s-releases#230 and cloudfoundry/loggregator-agent-release#734 (CI currently failing due to that).
I verified locally that I am able to send otlp traffic to
otelCollector.exportEndpoint.Drafted by an AI coding harness, carefully reviewed.