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

Trim project from GCE cloud metadata #10987

Conversation

andrewkroh
Copy link
Member

@andrewkroh andrewkroh commented Feb 28, 2019

This removes the project info from the cloud.machine.type and cloud.availability_zone fields
that are added to the add_cloud_metadata processor for Google Compute Engine (GCE).

Fixes #10968, #10775 (docs)

This removes the project info from the `cloud.machine.type` and `cloud.availability_zone` fields
that are added to the add_cloud_metadata processor for Google Compute Engine (GCE).

Fixes  elastic#10968
@@ -31,6 +31,8 @@ https://github.com/elastic/beats/compare/v7.0.0-alpha2...master[Check the HEAD d
- Allow Central Management to send events back to kibana. {issue}9382[9382]
- Initialize the Paths before the keystore and save the keystore into `data/{beatname}.keystore`. {pull}10706[10706]
- Add `cleanup_timeout` option to docker autodiscover, to wait some time before removing configurations after a container is stopped. {issue]10374[10374] {pull}10905[10905]
- On Google Cloud Engine (GCE) the add_cloud_metadata will now trim the project
info from the cloud.machine.type and cloud.availability_zone. {issue}10968[10968]
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this be listed as a breaking change, to be on the safe side?

Copy link
Member Author

Choose a reason for hiding this comment

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

Being safe. If you are using GCE and have queries or aggs based on the old values, they will be broken.

Copy link
Contributor

@tsg tsg left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for the quick fix!

@tsg tsg added v7.0.0 needs_backport PR is waiting to be backported to other branches. and removed v7.0.0 labels Mar 1, 2019
@andrewkroh andrewkroh merged commit f527cd5 into elastic:master Mar 1, 2019
@tsg
Copy link
Contributor

tsg commented Mar 3, 2019

@andrewkroh I think we want this backported quickly to the 7.0 branch, to make sure we don't miss the RC1.

@andrewkroh andrewkroh added v7.0.0 and removed needs_backport PR is waiting to be backported to other branches. labels Mar 3, 2019
andrewkroh added a commit to andrewkroh/beats that referenced this pull request Mar 3, 2019
This removes the project info from the cloud.machine.type and cloud.availability_zone fields
that are added to the add_cloud_metadata processor for Google Compute Engine (GCE).

Fixes elastic#10968, elastic#10775 (docs)

(cherry picked from commit f527cd5)
andrewkroh added a commit that referenced this pull request Mar 6, 2019
This removes the project info from the cloud.machine.type and cloud.availability_zone fields
that are added to the add_cloud_metadata processor for Google Compute Engine (GCE).

Fixes #10968, #10775 (docs)

(cherry picked from commit f527cd5)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants