Cherry-pick #25924 to 7.x: Migrate ec2 metricset to use cloudwatch input as light weight module #26050
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 #25924 to 7.x branch. Original message:
What does this PR do?
This PR is to migrate
ec2
metricset to use cloudwatch input as light weight module. Two main parts in this PR:In the original
ec2
metricset, we are also making EC2DescribeInstances
API call to get metadata for each EC2 instance. This is added as a part ofcloudwatch
metricset now.You can see under
ec2
metricset, there is only amanifest.yml
file which definescloudwatch
as the input.We need to keep backwards compatibility with metric names so dashboard can still be used.
You can see rename processor is used in
manifest.yml
file underec2
metricset to make sure with this PR we are not introducing breaking changes. Also please check the updateddata.json
file inec2
metricset to see the renaming is effective.Why is it important?
With this change, we no longer need to maintain the common code in both
ec2
metricset andcloudwatch
metricset.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.