otlp/cf-internal-local is the stable, release-managed receiver reference. Its
definition comes from ingress.grpc.* and overrides any operator definition.
The otlp/cf-internal-local receiver definition is always supplied by this
BOSH release.
ingress.pipelines
Other receiver definitions
Pipeline receiver lists
Unset (default)
Discarded
All replaced with [otlp/cf-internal-local]
[]
Preserved
Unchanged (manual wiring)
Nonempty list
Preserved
Only selected lists replaced
For manual or mixed receivers, use [] and wire lists such as
[otlp/cf-internal-local, otlp/custom] yourself.
Define custom receivers under config.receivers in the otel configuration supplied to
this release and reference them in the relevant pipeline’s receivers list.
Configure ingress.pipelines to contain only those pipelines in which
otlp/cf-internal-local shall be the only receiver (can also be []).
This way custom receiver references are preserved.
Only unset/null selection adds nop pipelines for missing CF signals, for backward
compatibility. Explicit lists and [] add no fallbacks; operators own signal handling.
FAQ
How do I configure mTLS per exporter?
Put each exporter’s PEMs under config and reference CredHub-stored values
via BOSH ((var)) placeholders:
If config must be a YAML string instead of a map, BOSH ((var))
substitution cannot indent multi-line PEMs into the block scalar and
template rendering fails. In that case use the secrets property — see the
secrets description in the job spec.
otel-collector-release
BOSH release for Cloud Foundry’s distribution of the OpenTelemetry Collector.
If you have any questions, or want to get attention for a PR or issue please reach out in the #logging-and-metrics channel within Cloud Foundry Slack.
See Configuring the OpenTelemetry Collector in the Cloud Foundry documentation for more information.
CF ingress receivers
otlp/cf-internal-localis the stable, release-managed receiver reference. Its definition comes fromingress.grpc.*and overrides any operator definition. Theotlp/cf-internal-localreceiver definition is always supplied by this BOSH release.ingress.pipelines[otlp/cf-internal-local][]For manual or mixed receivers, use
[]and wire lists such as[otlp/cf-internal-local, otlp/custom]yourself.Define custom receivers under
config.receiversin the otel configuration supplied to this release and reference them in the relevant pipeline’sreceiverslist. Configureingress.pipelinesto contain only those pipelines in whichotlp/cf-internal-localshall be the only receiver (can also be[]). This way custom receiver references are preserved.Only unset/null selection adds
noppipelines for missing CF signals, for backward compatibility. Explicit lists and[]add no fallbacks; operators own signal handling.FAQ
How do I configure mTLS per exporter?
Put each exporter’s PEMs under
configand reference CredHub-stored values via BOSH((var))placeholders:If
configmust be a YAML string instead of a map, BOSH((var))substitution cannot indent multi-line PEMs into the block scalar and template rendering fails. In that case use thesecretsproperty — see thesecretsdescription in the job spec.