Skip to content
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

Migrate sqs metricset to use cloudwatch input as light weight module #26117

Merged
merged 2 commits into from
Jun 3, 2021
Merged

Migrate sqs metricset to use cloudwatch input as light weight module #26117

merged 2 commits into from
Jun 3, 2021

Conversation

kaiyan-sheng
Copy link
Contributor

@kaiyan-sheng kaiyan-sheng commented Jun 2, 2021

What does this PR do?

This PR is to migrate sqs metricset to use cloudwatch input as light weight module. Two main parts in this PR:

In the original sqs metricset, we are also making SQS ListQueues API call to get metadata for each SQS instance. This is added as a part of cloudwatch metricset now.
You can see under sqs metricset, there is only a manifest.yml file which defines cloudwatch as the input.

We need to keep backward compatibility with metric names so the dashboard can still be used.
You can see rename processor is used in manifest.yml file under rds metricset to make sure with this PR we are not introducing breaking changes. Also please check the updated data.json file in sqs 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 sqs metricset and cloudwatch metricset.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 2, 2021
@kaiyan-sheng kaiyan-sheng self-assigned this Jun 2, 2021
@kaiyan-sheng kaiyan-sheng added needs_backport PR is waiting to be backported to other branches. Team:Integrations Label for the Integrations team labels Jun 2, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jun 2, 2021
@elasticmachine
Copy link
Collaborator

elasticmachine commented Jun 2, 2021

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: Started by user kaiyan-sheng

  • Start Time: 2021-06-02T20:40:03.538+0000

  • Duration: 104 min 12 sec

  • Commit: a872981

Test stats 🧪

Test Results
Failed 0
Passed 8690
Skipped 2483
Total 11173

Trends 🧪

Image of Build Times

Image of Tests

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 8690
Skipped 2483
Total 11173

Copy link
Member

@ChrsMark ChrsMark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏼 nice!

@kaiyan-sheng kaiyan-sheng merged commit adbb1a3 into elastic:master Jun 3, 2021
@kaiyan-sheng kaiyan-sheng deleted the migrate_sqs branch June 3, 2021 14:54
@kaiyan-sheng kaiyan-sheng added v7.14.0 and removed needs_backport PR is waiting to be backported to other branches. labels Jun 3, 2021
kaiyan-sheng added a commit that referenced this pull request Jun 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Integrations Label for the Integrations team v7.14.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants