Skip to content

Add freely configurable exporters for generic CF service bindings - #426

Merged
KarstenSchnitter merged 3 commits into
mainfrom
cf-exporter
Sep 3, 2026
Merged

Add freely configurable exporters for generic CF service bindings#426
KarstenSchnitter merged 3 commits into
mainfrom
cf-exporter

Conversation

@KarstenSchnitter

Copy link
Copy Markdown
Contributor

This change introduces new exporters for logs, metrics and traces that are freely
configurable to read the connection credentials from any CF binding in VCAP_SERVICES.
The binding can be specified by name, label, tags or a combination of those.
The exporters needs configuration of the properties within the credentials of the
binding to know where to find the endpoint and auth properties. The exporter require
either client key and cert for mTLS and will trust any server cert if not provided. Without
mTLS an authorisation header is required.

This changes supports clear separation of configuration with secrets provided by the service binding and everything else from the app manifest.

@dkhsap dkhsap left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Parsing the PEM representation of certs and keys is universal. This refactoring
can be used for other more generic exporters.

Signed-off-by: Karsten Schnitter <k.schnitter@sap.com>
Add the option to filter CF Services by their name, not only tag and label.

Signed-off-by: Karsten Schnitter <k.schnitter@sap.com>
This change introduces new exporters for logs, metrics and traces that are freely
configurable to read the connection credentials from any CF binding in VCAP_SERVICES.
The binding can be specified by name, label, tags or a combination of those.
The exporters needs configuration of the properties within the credentials of the
binding to know where to find the endpoint and auth properties. The exporter require
either client key and cert for mTLS and will trust any server cert if not provided. Without
mTLS an authorisation header is required.

@dkhsap dkhsap left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@KarstenSchnitter
KarstenSchnitter merged commit 9f4337a into main Sep 3, 2026
3 checks passed
@KarstenSchnitter
KarstenSchnitter deleted the cf-exporter branch September 3, 2026 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants