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
If you like, I do PR with the changes to your repo, unless you don't think this would be useful for you
Also, is there a concern with dropping the UUID, for the same container I do not believe flb ships logs more than once the same milli second and this should be safe, no?
The text was updated successfully, but these errors were encountered:
This is great! Please make a PR! I've been meaning to revisit this and update things for the newer version of fluent-bit. I added you as a collaborator to make that easier. I'm not sure about the implications of dropping the UUID, but that might be fine. One of my primary goals was to facilitate easily taking the S3 files, sending them back into fluent-bit and have them be delivered properly.
This allows disaster recovery for log pipelines that ship logs to kafka and elasticsearch.
I modified code a bit to store objects by Fluent TAG (using fluentbit 1.0.4)
See README for fluentbit config:
https://github.com/so0k/go-s3-logsink#fluent-bit-config
changes in http-server:
FLUENT-TAG
HTTP header from request:https://github.com/so0k/go-s3-logsink/blob/073d7e1043da72da2ad1c7d81411418d57dca186/server/http_server.go#L47
https://github.com/so0k/go-s3-logsink/blob/073d7e1043da72da2ad1c7d81411418d57dca186/server/http_server.go#L86
https://github.com/so0k/go-s3-logsink/blob/073d7e1043da72da2ad1c7d81411418d57dca186/server/http_server.go#L97
If you like, I do PR with the changes to your repo, unless you don't think this would be useful for you
Also, is there a concern with dropping the UUID, for the same container I do not believe flb ships logs more than once the same milli second and this should be safe, no?
The text was updated successfully, but these errors were encountered: