Skip to content
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

feature request: logstash friendly S3 log files #15

Open
sarkortrantor opened this issue Jul 1, 2022 · 1 comment
Open

feature request: logstash friendly S3 log files #15

sarkortrantor opened this issue Jul 1, 2022 · 1 comment

Comments

@sarkortrantor
Copy link

Hello guys,

I'm trying to read the S3 files written by the AWS Serverless Application from logstash, and I'm facing issues spanning from the fact that the files

  • are containing a JSON list as the root object
  • the JSON events are spanning multiple lines (indent=2)

So in order to read them from logstash I would have to do one of :

  • create a custom logstash input/codec or retrieve and preprocess the files before logstash using some other tool / jq etc.
  • try to leverage the multiline codec to split on some well chosen separator pattern and postprocess to reconstruct valid JSON before decode
  • try to leverage the multiline codec to read the entire files in single event and decode then split later in the pipeline

This is definitely possible but maybe not the best user experience.

Would you consider providing a second serverless app that emmits line delimited JSON (logstash friendly) in the files written in S3 ?

(so flat, no JSON list, and one event per line)

Best regards,

@kmaranionjc
Copy link
Contributor

Hello, you can edit the code and make your desired changes to the json format then manually publish the serverless app to your AWS org instead of going through the AWS Serverless App Repo.

https://github.com/TheJumpCloud/JumpCloud-Serverless/tree/master/AWS/DirectoryInsights#readme

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

No branches or pull requests

2 participants