-
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] Add storage metricset to Google Cloud Platform module #15598
Conversation
}, | ||
"storage": { | ||
"storage": { | ||
"object_count": 1 |
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.
Just a suggestion, since this is being included in the docs it would be nice if we could have more metrics-fields as a more complete sample for our users. I would try to include as many as possible of them https://github.com/elastic/beats/pull/15598/files#diff-71e43a13b3f822a4956f547a646aced4R10.
wdyt?
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.
Overall lgtm @sayden already! I just left some minor concerns.
Also do you plan to add a dashboard too in this or in followup PR? It would be nice to update the PR's description with this info too.
return nil, nil | ||
case googlecloud.ServiceLoadBalancing: | ||
return nil, nil | ||
case googlecloud.ServiceStorage: |
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.
It seems that ServicePubsub
and ServiceLoadBalancing
are not strictly related to this patch and related to different upcoming metricsets, right?
Also ServiceStorage
returns nil metadata too?
If we plan to keep it like this for now could you please provide some content here for reference so as to be more clear?
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.
Yeah, main thing here is that I'm trying to avoid too many potential conflicts because there are 3 different follow-up PR's touching the same function and I have to wait until only one is left to see overall final look.
About the question of storage: This file, metadata_services.go
"controls / knows" which metricsets / gcp-services have an specific implementation to retrieve extra metadata (call it labels or properties) using their specific API's, instead of taking just the labels that are returned in the Stackdriver API. Only one metricset has such implementation: compute
.
This is caused by a direct limitation on lightweight modules. Being so generic is a con in this case.
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.
Fair enough! Thanks for elaborating!
Need a rebase and a changelog entry please 😬 |
zone: "us-central1-a" | ||
region: "us-central1" |
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.
Should compute and storage be in separate config section? Because one is taking zone and the other is taking region as config.
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 would say that yes 🤔
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.
@sayden ^^ WDYT? 😄
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 overlooked at this the first time but yeap, I think it's better to separate them too. Thanks! 😬
@sayden @kaiyan-sheng could you please update the status of this after the changes/rebase? |
It was blocked by the loadbalancing metricset and now it needs rebase. |
9541366
to
a635414
Compare
a635414
to
9e87030
Compare
e9b87d1
to
cdcca53
Compare
@kaiyan-sheng whenever you can take a look at this, I'm not sure if the final "merge" is correct, for example the function |
@sayden Sorry for the late response. I believe |
0d22a64
to
0c3ba1c
Compare
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.
We can create a separate PR to address the leftover comments 👍 Let's get this in first! Thanks!
67894b4
to
4406e09
Compare
…lastic#15598) (cherry picked from commit 52b9330) # Conflicts: # metricbeat/docs/modules/googlecloud.asciidoc # metricbeat/docs/modules_list.asciidoc # x-pack/metricbeat/metricbeat.reference.yml # x-pack/metricbeat/module/googlecloud/_meta/config.yml # x-pack/metricbeat/module/googlecloud/fields.go # x-pack/metricbeat/modules.d/googlecloud.yml.disabled
…le Cloud Platform module (#17219)
Add the storage metricset and the field
region
to the input configcf. #15810