-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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] Change log.file.path field in awscloudwatch input to nested object #41099
Conversation
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
|
Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services) |
We talked about this on slack and decide to merge it for both 8.x and 9.0 since it's a small change that shows no impact on es query or mapping. |
/test |
…tch input to nested object (#41164) * [aws] Change log.file.path field in awscloudwatch input to nested object (#41099) Change log.file.path field in awscloudwatch input to nested object (cherry picked from commit 904d14b) --------- Co-authored-by: kaiyan-sheng <[email protected]>
…atch input to nested object (#41163) * [aws] Change log.file.path field in awscloudwatch input to nested object (#41099) Change log.file.path field in awscloudwatch input to nested object (cherry picked from commit 904d14b) --------- Co-authored-by: kaiyan-sheng <[email protected]>
Hello, The field I've opened this issue about it last year: elastic/integrations#5156 Is it possible to apply the same fix on this field? |
Proposed commit message
This PR changes
log.file.path
field in awscloudwatch input from dotted field to nested object.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
The concern we have with this PR is when users have ingest pipelines or logstash filters configured down the line, this might break what they have. For example in ingest pipeline, ctx[‘log.file.path’] needs to be changed to
ctx.log?.file?.path
.