-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Metricbeat + AWS Module: runtime error: index out of range [0] with length 0 #21095
Comments
Pinging @elastic/integrations-platforms (Team:Platforms) |
@dudumiquim Thanks for reporting this issue. I see in your config file, there are no credential related parameters specified. Do you have a ~/.aws/credentials shared the credential file with a default profile on your Amazon Linux 2 VM? I just want to make sure I get everything before trying to reproduce it. |
Hi @kaiyan-sheng . I'm using IAM role attached a t the ec2 instance. To discard the permission problem, I'm using an administrator role. To check if all this are working correctly, I installed the filebeat and set the sqs read to aws module. Works correctly. If you want, I can try configuring the credentials file. |
Hi @dudumiquim, thanks for the quick response! I think I found the problem. I just pushed a PR up and please feel free to verify it/review the PR. |
There is some workaround for this issue? I'm experiencing the same. |
Hello! Sorry about this bug! Could you try adding an account alias to your aws account? That would be the temporary workaround for now. |
I created an alias. But, when I run the metricbeat binary the Kibana dashboard isn't receiving metrics :( However, Kibana is confirming that the agent is sending data from the AWS module and group the metrics on AWS provider. I'm testing it on the localhost before deploying it on AWS. This is my aws.yml fil, the system module is disabled.
|
@nan140114 Any new error message in Metricbeat log? Could you check in AWS CloudWatch to see if there are metrics there first also? Thank you for the feedback! If you see anything suspicious, please open a discuss forum ticket and you can @ me there too. Let's keep this github issue for this specific bug only 🙂 |
I'm trying to configure the AWS module but when I try to start the metricbeat, I receive this error:
This error are not "too clear" and I started my metricbeat with debug logging level. The log level are not clear about what are happening.
I checked all the configs that I know, but the problem persist.
I removed all the modules (was only aws and system) and test only with aws. If I disable aws module, the metricbeat works.
Can someone help me?
I stated a thread on discuss, but someone recommended post here because look like a issue.
metricbeat.yml
Metricbeat version:
Complete output of debug:
Install the Metricbeat following the documentation on the Amazon Linux 2. After that, I only enable the AWS module and disable System module.
The text was updated successfully, but these errors were encountered: