Skip to content

docs: document behavior changes for s3 log_key and HTTP server - #2649

Open
eschabell wants to merge 1 commit into
fluent:masterfrom
eschabell:erics_behavior_change_updates
Open

docs: document behavior changes for s3 log_key and HTTP server#2649
eschabell wants to merge 1 commit into
fluent:masterfrom
eschabell:erics_behavior_change_updates

Conversation

@eschabell

Copy link
Copy Markdown
Collaborator

Two merged source changes alter existing behavior in ways users can hit on upgrade.

  • pipeline/outputs/s3.md: note in the log_key row that the record key name must match exactly, linking to the new section below.
  • pipeline/outputs/s3.md: add a "Key matching for log_key" section describing the prefix matching used before 5.1, where a record key that was a prefix of the configured value matched (log_key log_level selecting a log field instead), and the "Could not find log_key" error that identifies an affected configuration after upgrading.
  • administration/monitoring.md: document that a monitoring HTTP server that cannot bind now fails startup with "could not start HTTP server", where earlier versions continued running without the endpoint.

Note, update for code changes without corresponding docs PR.

Two merged source changes alter existing behavior in ways users can hit
on upgrade.

- pipeline/outputs/s3.md: note in the log_key row that the record key
  name must match exactly, linking to the new section below.
- pipeline/outputs/s3.md: add a "Key matching for log_key" section
  describing the prefix matching used before 5.1, where a record key
  that was a prefix of the configured value matched (log_key log_level
  selecting a log field instead), and the "Could not find log_key"
  error that identifies an affected configuration after upgrading.
- administration/monitoring.md: document that a monitoring HTTP server
  that cannot bind now fails startup with "could not start HTTP
  server", where earlier versions continued running without the
  endpoint.

Note, update for code changes without corresponding docs PR.

Signed-off-by: Eric D. Schabell <eric@schabell.org>
@eschabell eschabell self-assigned this Aug 1, 2026
@eschabell
eschabell requested a review from a team as a code owner August 1, 2026 12:19
@eschabell eschabell added waiting-on-review Waiting on a review from mainteners 5.0.9 labels Aug 1, 2026
@coderabbitai

coderabbitai Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

Next review available in: 20 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 28362a12-1479-45ac-82de-72c51fc8ed68

📥 Commits

Reviewing files that changed from the base of the PR and between 0eb06a6 and 206b8eb.

📒 Files selected for processing (2)
  • administration/monitoring.md
  • pipeline/outputs/s3.md

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.

@eschabell

Copy link
Copy Markdown
Collaborator Author

@patrick-stephens ready for review!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

5.0.9 waiting-on-review Waiting on a review from mainteners

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant