Cherry-pick #9784 to 6.5: Vsphere nil pointers access in Metricbeat module #9823
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #9784 to 6.5 branch. Original message:
It seems that some fields within the vsphere module on Metricbeat are pointers where the
nil
check access is not being done. This can cause panics that are not easy to reproduce.This PR checks every pointer that acces a pointer from the
gvmomi
library which is used to access vsphere data.Initially, we only know about panics in the
virtualmachine
metricset but I have seen that thehost
metricset could potentially have the same problem