-
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
Change cloud.provider from ec2 to aws and from gce to gcp in add_cloud_metadata #11687
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andrewkroh Could you have a look at this as you initially introduced this if I remember correctly?
@@ -82,7 +82,7 @@ func TestRetrieveAWSMetadata(t *testing.T) { | |||
|
|||
expected := common.MapStr{ | |||
"cloud": common.MapStr{ | |||
"provider": "ec2", | |||
"provider": "aws", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if this is also going to break some of our dashboards?
As I would consider this a bug in 7 I'm good with getting this in even though it's a breaking change.
@ruflin @exekias Thanks for the review. Quick question, similar to this https://www.elastic.co/guide/en/ecs/current/ecs-cloud.html, GCE probably should be GCP instead? hmm |
jenkins, test this |
+1 to changing GCE to GCP too, hopefully in the same version |
@kaiyan-sheng Could you double check that this does not break any dashboards / visualisatins? |
@ruflin Sorry I forgot to respond to you on this earlier. I did a search in metricbeat dashboards and filebeat dashboards to see if there's anywhere needed cloud.provider=ec2/gce and I didn't see any. So I assume it's safe here. And to be more sure about this, I'm trying to setup metricbeat/kibana/es on GCP to actually test it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. This will also need backports I assume?
Yes! Sorry I forgot to add the labels. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with the changes. It's unfortunate that this didn't make it into 7.0.0 because now we have a breaking change in a minor.
@@ -27,6 +27,7 @@ https://github.com/elastic/beats/compare/v7.0.0-alpha2...master[Check the HEAD d | |||
*Metricbeat* | |||
|
|||
- Add new option `OpMultiplyBuckets` to scale histogram buckets to avoid decimal points in final events {pull}10994[10994] | |||
- Change cloud.provider from ec2 to aws and from gce to gcp in add_cloud_metadata to align with ECS. {issue}10775[10775] {pull}11687[11687] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a breaking change affect all Beats.
@andrewkroh Yeah my bad... I didn't quite realize the timing there... |
With the change elastic/ecs#348 in ECS, add_cloud_metadata should change
cloud.provider
fromec2
toaws
and fromgce
togcp
to match the example in https://www.elastic.co/guide/en/ecs/current/ecs-cloud.html