You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The OpenTelemetry input documentation describes processor execution when multiple HTTP workers are enabled. It also documents deferred ingress queue limits, rejection responses, and retry guidance for HTTP and gRPC clients.
Changes: OpenTelemetry HTTP worker behavior
Layer / File(s)
Summary
Worker processing and queue responses pipeline/inputs/opentelemetry.md
Documents when the processor chain runs in an HTTP worker or after queueing. Describes queue limits, HTTP 503 and gRPC UNAVAILABLE responses, and when clients should retry.
fluent/fluent-bit-docs#2801: Documents related Fluent Bit 5.2 ingestion and HTTP-worker changes in release and upgrade documentation.
Merge Risk: Low · up to 4175f
The documentation accurately distinguishes oversized events from temporary queue saturation, but clients cannot distinguish those causes from the documented responses. Clarify retry guidance; the remaining risk is limited to documentation.
Pre-merge checks: 4
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title names the documentation change for the OpenTelemetry input: worker log processing and busy responses. The summary confirms the added text covers which processors run in HTTP workers, the fal…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Title check
Explanation
The title names the documentation change for the OpenTelemetry input: worker log processing and busy responses. The summary confirms the added text covers which processors run in HTTP workers, the fallback to the full chain, and the 503 and UNAVAILABLE responses when the queue is full. The title is specific to the main change and matches the objectives.
Finishing Touches
Generate unit tests (beta)
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: defaults
Review profile: CHILL
Plan: Advanced
Run ID: fdb38a72-7280-499b-b621-00919c5d8aca
Commits
Reviewing files that changed from the base of the PR and between 96b1d22 and 4175f8a.
Files selected for processing: 1
pipeline/inputs/opentelemetry.md
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 0 remain after this review.
Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.
… and busy responses
- Add HTTP workers section describing the deferred ingress queue
- Document which log processors run inside HTTP workers and the fallback
- Document 503 / gRPC status 14 responses when the ingress queue is full
- clarify retry guidance for ingress queue rejections
- Explain that mem_buf_limit can lower the effective ingress queue byte limit
- Separate the temporary queue-full rejection from the oversized-request rejection
- Recommend retrying only when the queue is full; oversized requests need smaller requests or a higher limit
- Compare the effective byte limit against each queued event instead of the whole request
- Note that one request can add several events to the ingress queue
- Align the retry guidance with the per-event limit
- Note that clients can't distinguish a full queue from an oversized event in the response
- Recommend retrying with backoff and explain that repeated failures point to an event exceeding the effective byte limit
Signed-off-by: Eric D. Schabell <eric@schabell.org>
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
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.
eschabell
added
waiting-on-review
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Signed-off-by: Eric D. Schabell eric@schabell.org