Skip to content

out_stdout: add use_logger option #593

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 30, 2025

Conversation

daipom
Copy link
Contributor

@daipom daipom commented Jul 29, 2025

Copy link
Contributor

@Watson1978 Watson1978 left a comment

Choose a reason for hiding this comment

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

👍🏻

daipom added a commit to fluent/fluentd that referenced this pull request Jul 30, 2025
**Which issue(s) this PR fixes**: 
* Fixes #5029

**What this PR does / why we need it**: 
Add `use_logger` option to `out_stdout` plugin.

* Type: `bool`
* Default: `true`

If you set `false` to this option, `out_stdout` outputs events to
`$stdout`, instead of `$logger`.
This feature enables events to be output to STDOUT in containerized
environments, such as K8s.

This does not change the default behavior.

Note: Although it's preferable for the default value of a `bool` option
to be `false` (because it can be used as a flag), I couldn't think of a
suitable name for it.

**Docs Changes**:
fluent/fluentd-docs-gitbook#593

**Release Note**: 
out_stdout: support output to STDOUT independently of Fluentd logger by
setting `use_logger` to `false`.

---------

Signed-off-by: Daijiro Fukuda <[email protected]>
Co-authored-by: Takuro Ashie <[email protected]>
Co-authored-by: Kentaro Hayashi <[email protected]>
Co-authored-by: Shizuo Fujita <[email protected]>
Co-authored-by: Kentaro Hayashi <[email protected]>
@daipom daipom merged commit 39a9a9a into fluent:1.0 Jul 30, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants