Fix index out of range error when getting AWS account name #21101
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
botelastic
bot
added
the
needs_team
kaiyan-sheng
added
bug
needs_backport
Collaborator
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
botelastic
bot
removed
the
needs_team
Collaborator
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
|
ChrsMark
approved these changes
Sep 17, 2020
ChrsMark
approved these changes
Sep 17, 2020
3 tasks
kaiyan-sheng
added
v7.10.0
and removed
needs_backport
3 tasks
v1v
added a commit
to v1v/beats
that referenced
this pull request
Sep 18, 2020
…ne-2.0 * upstream/master: Add Cloud Foundry dashboards for metricbeat (elastic#21124) [Metricbeat][Kibana] Apply backoff when errored at getting usage stats (elastic#20772) Update input-log.asciidoc (elastic#20965) (elastic#21153) Remove redirects page (elastic#19574) [Ingest Manager] Fixed input types for filebeat (elastic#21131) docs: add beat specific install widget (elastic#21050) docs: link to APM privs for API keys (elastic#20911) Fix index out of range error when getting AWS account name (elastic#21101) Agent info docs and ci test pr (elastic#19805) Handling missing counters in application_pool metricset (elastic#21071)
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…etting AWS account name (elastic#21144) * Fix index out of range error when getting AWS account name (elastic#21101) (cherry picked from commit 749e0ea)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What does this PR do?
This PR is to fix panic in aws metricbeat module for by skipping running
output.AccountAliases[0]after checking if the length ofoutput.AccountAliasesis zero.Why is it important?
This error will happen when the user is trying to collect metrics with an account that does not have an account alias.
Checklist
- [ ] 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 worksCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues