metrics: set ems in metrics_capture object #19522
Merged
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.
Fixes issue with azure build failure due to metrics collection.
Details
Each provider's metrics_collection handles the
ems
differently.I had changed the metrics_capture to have an optional
ems
in #19511, to make sure vmware worked: ManageIQ/manageiq-providers-vmware#475 - but this caused issues with azure. Now we're passing inems
(in the second branch of theif
) so azure and all ems will be happy.Enhancement
The first branch of the
if
enablesEms.perf_capture_object
- which is the main purpose of our changes to metrics_collection. This is so metrics can be collected for an ems (rather than for only targets).