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

Push events even when there's no cloudwatch data #11023

Merged
merged 4 commits into from
Mar 7, 2019
Merged

Push events even when there's no cloudwatch data #11023

merged 4 commits into from
Mar 7, 2019

Conversation

kaiyan-sheng
Copy link
Contributor

@kaiyan-sheng kaiyan-sheng commented Mar 1, 2019

When an instance is not in running state, there will not be metrics in Cloudwatch. But it's till valuable to push an event about this instance. So users can see there are instances hanging around that's not working.
With this PR, instances in stopped state are reported as well. Please see kibana picture below:
stopped_instance

This PR also updated the documentations for ec2, please see #11009 for more details.

@kaiyan-sheng kaiyan-sheng requested a review from a team as a code owner March 1, 2019 16:53
@kaiyan-sheng kaiyan-sheng self-assigned this Mar 1, 2019
@kaiyan-sheng kaiyan-sheng added Metricbeat Metricbeat needs_backport PR is waiting to be backported to other branches. v7.0.0 Team:Integrations Label for the Integrations team labels Mar 1, 2019
@kaiyan-sheng kaiyan-sheng requested a review from a team as a code owner March 1, 2019 18:04
@kaiyan-sheng kaiyan-sheng mentioned this pull request Mar 4, 2019
3 tasks
Copy link
Contributor

@ruflin ruflin left a comment

Choose a reason for hiding this comment

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

LGTM. We can directly get this in and do follow up PR's with the comments as they are not critical.

@@ -32,8 +31,14 @@ see https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html[Te
aws> sts get-session-token --serial-number arn:aws:iam::1234:mfa/your-email@example.com --token-code 456789 --duration-seconds 129600
----

Specific permissions needs to be added into the IAM user's policy to authorize Metricbeat to collect AWS monitoring metrics. Please
see documentation under each metricset for required permissions.
Since temporary security credentials are short term, after they expire, the user needs to generate new ones and modify
Copy link
Contributor

Choose a reason for hiding this comment

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

This paragraph sounds like someone could just replace the credentials and it would reload. This is true if reload is enabled, but by default it's off.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

x-pack/metricbeat/module/aws/ec2/ec2.go Show resolved Hide resolved
x-pack/metricbeat/module/aws/ec2/ec2.go Show resolved Hide resolved
@kaiyan-sheng kaiyan-sheng merged commit 6eab0bd into elastic:master Mar 7, 2019
@kaiyan-sheng kaiyan-sheng deleted the fix_bug_ec2 branch March 7, 2019 15:19
kaiyan-sheng added a commit that referenced this pull request Mar 11, 2019
* Push events even when there's no cloudwatch data
* Change cloud.provider from ec2 to aws
(cherry picked from commit 6eab0bd)
@kaiyan-sheng kaiyan-sheng removed needs_backport PR is waiting to be backported to other branches. v7.0.0 labels Mar 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Metricbeat Metricbeat review Team:Integrations Label for the Integrations team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants