We've enabled the new transaction logs feature and sending it to our AWS S3.
We have came across something which we wanted to point out which is the directory structure is in hours/days/month/year this is not how standard logging folders are created and is different from your old approach too. This can be an issue during manual searching or programatic querying in tools like AWS Athena. I suggest changing this to a normal directory structure to avoid these pains.
Question
New transaction logs feature and sending to AWS S3 Structure issue
+5We are running into issues with this format when ingesting logs into Cribl.
+12
+5
We are using direct to cloud log streaming.
+12Can you share an example of the directory structure you are seeing so I can provide a tactical solution and file an enhancement request?
+5Can you share an example of the directory structure you are seeing so I can provide a tactical solution and file an enhancement request?
I dont have access to the S3 bucket to show the structure, but it is in H/D/M/Y format. We opened case # 00592950 and PM informed us that they will not fix the issue. I don't feel that is a reasonable response.
Sign up
Already have an account? Login
Sign in or register securely using Single Sign-On (SSO)
Employee Continue as Customer / Partner (Login or Create Account)Login to the community
Sign in or register securely using Single Sign-On (SSO)
Employee Continue as Customer / Partner (Login or Create Account)Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.