Skip to content

out_es: custom http headers#1390

Open
AndrewChubatiuk wants to merge 3 commits into
fluent:masterfrom
AndrewChubatiuk:out-es-custom-http-headers
Open

out_es: custom http headers#1390
AndrewChubatiuk wants to merge 3 commits into
fluent:masterfrom
AndrewChubatiuk:out-es-custom-http-headers

Conversation

@AndrewChubatiuk
Copy link
Copy Markdown
Contributor

Added docs for custom Elasticsearch output custom HTTP headers

@AndrewChubatiuk AndrewChubatiuk requested review from a team as code owners June 11, 2024 07:01
Signed-off-by: AndrewChubatiuk <andrew.chubatiuk@gmail.com>
Signed-off-by: esmerel <6818907+esmerel@users.noreply.github.com>
@esmerel
Copy link
Copy Markdown
Contributor

esmerel commented Oct 22, 2024

I fixed the merge conflict, this should be ok to go if/when the appropriate code merges.

@eschabell
Copy link
Copy Markdown
Collaborator

@AndrewChubatiuk just fyi I've nudged the corresponding code PR fluent/fluent-bit#9416 for a review to hopefully move both the docs and code changes forward.

@eschabell eschabell self-assigned this Oct 22, 2025
Copy link
Copy Markdown
Contributor

@patrick-stephens patrick-stephens left a comment

Choose a reason for hiding this comment

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

Can we add some examples particularly with multiple headers so people can see - what types of headers would be common here?

@eschabell eschabell added the waiting-for-user Waiting for user/contributors feedback or requested changes label Dec 3, 2025
Signed-off-by: Eric D. Schabell <eric@schabell.org>
@eschabell eschabell self-requested a review as a code owner May 27, 2026 15:27
@eschabell
Copy link
Copy Markdown
Collaborator

@AndrewChubatiuk resolved your conflicts.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 27, 2026

Warning

Review limit reached

@eschabell, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 11 minutes and 15 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fb17ea8b-19f7-4a54-91cb-d40911b41e00

📥 Commits

Reviewing files that changed from the base of the PR and between 5231934 and 4d69981.

📒 Files selected for processing (1)
  • pipeline/outputs/elasticsearch.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Collaborator

@eschabell eschabell left a comment

Choose a reason for hiding this comment

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

@AndrewChubatiuk just waiting on code PR merging.

@eschabell eschabell removed the waiting-for-user Waiting for user/contributors feedback or requested changes label May 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants