Need Help: Issues with Log Format While Integrating application logs via S3 bucket into SecOps

Hello,

I recently integrated an S3 bucket for one of our application logs. The logs are in JSON format, and the files in the S3 bucket are named in the format FileName.json.gz.

SecOps is successfully pulling the logs, but I'm encountering an issue with the log format. The logs are breaking improperly—either after each line, comma, or curly brace { } —resulting in an incorrect format when ingested.

I’ve double-checked the basics but haven’t been able to pinpoint the root cause of this issue.

Has anyone faced a similar problem? If so, how did you resolve it? Any guidance or troubleshooting steps would be greatly appreciated.

Thanks in advance for your help!

0 9 568
9 REPLIES 9