-
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
Avoid mapping issues in kubernetes module #8487
Conversation
This contains 2 changes: * Do not report `start_time` when it's empty, as that will throw a mapping exception * Fix `fields.yml`, as some fields were out of place for `event` metricset
0c4f702
to
94ae4dc
Compare
Changes LGTM but it will need a Is there a reason these two changes are connected together? Will this need a backport? |
Thanks for the review, they are not that connected 😇 but both could potentially cause mapping issues so I addressed them together. I think this should be backported to 6.x & 6.4 branches |
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.
WFG
* Avoid mapping issues in kubernetes module This contains 2 changes: * Do not report `start_time` when it's empty, as that will throw a mapping exception * Fix `fields.yml`, as some fields were out of place for `event` metricset (cherry picked from commit 3c363a0)
* Avoid mapping issues in kubernetes module This contains 2 changes: * Do not report `start_time` when it's empty, as that will throw a mapping exception * Fix `fields.yml`, as some fields were out of place for `event` metricset (cherry picked from commit 3c363a0)
…8506) * Avoid mapping issues in kubernetes module (#8487) * Avoid mapping issues in kubernetes module This contains 2 changes: * Do not report `start_time` when it's empty, as that will throw a mapping exception * Fix `fields.yml`, as some fields were out of place for `event` metricset (cherry picked from commit 3c363a0) * Update CHANGELOG.asciidoc
…8507) * Avoid mapping issues in kubernetes module (#8487) * Avoid mapping issues in kubernetes module This contains 2 changes: * Do not report `start_time` when it's empty, as that will throw a mapping exception * Fix `fields.yml`, as some fields were out of place for `event` metricset (cherry picked from commit 3c363a0) * Update CHANGELOG.asciidoc
…odule (elastic#8507) * Avoid mapping issues in kubernetes module (elastic#8487) * Avoid mapping issues in kubernetes module This contains 2 changes: * Do not report `start_time` when it's empty, as that will throw a mapping exception * Fix `fields.yml`, as some fields were out of place for `event` metricset (cherry picked from commit 8d72865) * Update CHANGELOG.asciidoc
This contains 2 changes:
start_time
when it's empty, as that will throw amapping exception
fields.yml
, as some fields were out of place forevent
metricset
closes #7736