Closed naj-h closed 10 months ago
Pinging @elastic/integrations (Team:Platforms)
This is a known issue. The GCP integration can only handle metadata of Compute services and Beats need to develop the proper workarounds on lightweight modules to extract the labels data.
The code to achieve this must be stored in the metrics
Metricset. An example of how to do this can be found in the compute folder here https://github.com/elastic/beats/tree/main/x-pack/metricbeat/module/gcp/metrics/compute
Hi! We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
.
Thank you for your contribution!
Describe the enhancement: Add labels to the Metricbeat GCP module pubsub
Describe a specific use case for the enhancement or feature:
In GCP projects, one can have multiple topics and subscriptions which each serve a certain functional scope. One way to categorise them is to use labels. If metricbeat does not report labels, then one cannot use them to build specific visualisations by functional domain. Example below to give an idea :