8000 Add JSON array serialization format to S3 output plugin · Issue #9888 · fluent/fluent-bit · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add JSON array serialization format to S3 output plugin #9888

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.

Sign up for GitHub

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

Jump to bottom
Closed
vcschapp opened this issue Jan 29, 2025 · 2 comments
Closed

Add JSON array serialization format to S3 output plugin #9888

vcschapp opened this issue Jan 29, 2025 · 2 comments
Labels
Stale

Comments

@vcschapp
Copy link
vcschapp commented Jan 29, 2025 •
edited
Loading

Is your feature request related to a problem? Please describe.

I need to deliver log events to Amazon S3 as a JSON array rather than newline-delimited JSON.

Describe the solution you'd like

  1. Add a new format configuration parameter to the Amazon S3 output plugin with supported values: jsonl (default) and json_array.
  2. The default /jsonl behavior continues to be writing newline-delimited JSON.
  3. In the json_array variant, the plugin writes a leading [ as the first character of the object, uses , as the delimiter instead of newline, and writes a final ] when the object is finished.

Describe alternatives you've considered

I need my objects to contain JSON arrays for compatibility with an existing web service I do not control. My only options are:

  1. Don't use FB.
  2. Write a new custom plugin specifically for my use case that does what I want.
  3. Make the existing Amazon S3 plugin more versatile.

Additional context

  • I am trying to send usage logs to an existing web service whose "public interface" is an S3 bucket that MUST receive objects containing JSON arrays.
@github-actions GitHub Actions
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

@github-actions github-actions bot added the Stale label Apr 30, 2025
@github-actions GitHub Actions
Copy link
Contributor
github-actions bot commented May 5, 2025

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vcschapp
0