-
Notifications
You must be signed in to change notification settings - Fork 421
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
[aws] Fix event.created in CloudTrail data stream #2325
[aws] Fix event.created in CloudTrail data stream #2325
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
Pinging @elastic/integrations (Team:Integrations) |
05fc437
to
96f4a70
Compare
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
@@ -79,20 +78,6 @@ | |||
}, | |||
"version": "1.16.310" | |||
} | |||
}, | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The source file had extra newlines in it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That seems like something that shouldn't result in an output.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I raised elastic/elastic-package#616 to catch these in elastic-package lint
and format
.
event.created was being set to the CloudTrail eventTime rather than the time that Filebeat created the document. Fixes elastic#2324
96f4a70
to
a77a340
Compare
event.created was being set to the CloudTrail eventTime rather than the time that Filebeat created the document. Fixes elastic#2324
What does this PR do?
event.created was being set to the CloudTrail eventTime rather than the time that Filebeat created the document.
Fixes #2324
Checklist
changelog.yml
file.- [ ] I have verified that Kibana version constraints are current according to guidelines.Related issues