Repository navigation
Make configuration examples use v1 parameters instead of v0.12 ones - #706
Merged
Merged
Conversation
These examples still use v0.12 parameters. Most work only because of compat_parameters, so readers copy an outdated style. retry_limit in a <buffer> section is not converted at all and is silently ignored. - Move flush_interval into a <buffer> section - Replace format apache2 with a <parse> section - Rename retry_limit to retry_max_times in a <buffer> section - Drop out_s3's time_slice_format and let timekey set the time format - Refer to the <buffer> section instead of buffer_path and buffer_type Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Shizuo Fujita <fujita@clear-code.com>
✅ Deploy Preview for fluentd-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
kenhys
approved these changes
Oct 7, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Several examples still used v0.12 parameters such as a top-level
flush_interval,format apache2and out_s3'stime_slice_format. They work only through compat_parameters, so readers keep copying the old style. One example hadretry_limitinside<buffer>, which is not converted and is silently ignored.This moves them to the v1
<buffer>and<parse>sections, renamesretry_limittoretry_max_times, and letstimekeyset the S3 time format. The v0.12 examples inoutput/README.mdand the migration pages are kept on purpose, since they show the old format for comparison.🤖 Generated with Claude Code