Skip to content

Conversation

AndrewChubatiuk
Copy link

@AndrewChubatiuk AndrewChubatiuk commented Jul 2, 2025

Description

Add ability to set custom headers for Elasticsearch protocols, which are supported by Vector to allow to customize ingested logs from Openshift into VictoriaLogs

/cc @Clee2691 @cahartma
/assign @cahartma

@openshift-ci openshift-ci bot requested review from cahartma and Clee2691 July 2, 2025 09:58
@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jul 2, 2025
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

Hi @AndrewChubatiuk. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@vrutkovs
Copy link
Member

vrutkovs commented Jul 2, 2025

/retitle NO-JIRA: support custom headers for Loki and Elasticsearch outputs
/ok-to-test

Not sure if this needs a JIRA ticket (probably it does, as there should be a release note and we'll want to backport this too)

@openshift-ci openshift-ci bot changed the title support custom headers for Loki and Elasticsearch outputs NO-JIRA: support custom headers for Loki and Elasticsearch outputs Jul 2, 2025
@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 2, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 2, 2025
@openshift-ci-robot
Copy link

@AndrewChubatiuk: This pull request explicitly references no jira issue.

In response to this:

Description

Add ability to set custom headers for Loki and Elasticsearch protocols, which are supported by Vector to allow to customize ingested logs from Openshift into VictoriaLogs

/cc @Clee2691 @cahartma
/assign @cahartma

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

codec = "json"
except_fields = ["_internal"]

[sinks.loki_receiver.request]
Copy link
Contributor

Choose a reason for hiding this comment

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

@AndrewChubatiuk Thanks for your contribution! Just a heads-up: according to the official docs, the Loki sink’s request block doesn’t support a headers field. https://vector.dev/docs/reference/configuration/sinks/loki/#request

Copy link
Author

Choose a reason for hiding this comment

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

right, thanks, removed them for loki output

@AndrewChubatiuk AndrewChubatiuk changed the title NO-JIRA: support custom headers for Loki and Elasticsearch outputs NO-JIRA: support custom headers for Elasticsearch output Jul 2, 2025
Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AndrewChubatiuk
Once this PR has been reviewed and has the lgtm label, please ask for approval from cahartma. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Contributor

openshift-ci bot commented Jul 2, 2025

@AndrewChubatiuk: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jcantrill
Copy link
Contributor

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 7, 2025
@jcantrill
Copy link
Contributor

@AndrewChubatiuk if the intent is to use this to write to VictoriaLogs then is there a functional test we can provide to confirm functionallity. The larger question is what happens when RH logging to VictoriaLogs doesn't work and we are on the hook to support it with no backing tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants