Cherry-pick #18757 to 7.x: [Metricbeat] Fix getting compute instance metadata with partial zone/region config #18839
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 #18757 to 7.x branch. Original message:
What does this PR do?
This PR fixes getting compute instance metadata when zone/region in googlecloud.yml is partial. For example:
This bug is introduced from #17913
Why is it important?
Instances.Get
API does not accept partial zone name andRegions.Get
API does not accept partial region name. So instead of using the region/zone information from the config, use the zone label from time series metric.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.