[Metricbeat] Allow to specify more than one regions in googlecloud module

[kaiyan-sheng]

Right now googlecloud module only accept region parameter for one specific region, not a list of regions, which means if you want to collect metrics from more than one region, you need to repeat the config like below:

- module: googlecloud
  metricsets:
    - compute
  region: "europe-west1"
  project_id: elastic-observability
  credentials_file_path: "/Users/kaiyansheng/Downloads/elastic-observability-d17781618202.json"
  exclude_labels: false
  period: 300s
- module: googlecloud
  metricsets:
    - compute
  region: "europe-west3"
  project_id: elastic-observability
  credentials_file_path: "/Users/kaiyansheng/Downloads/elastic-observability-d17781618202.json"
  exclude_labels: false
  period: 300s
- module: googlecloud
  metricsets:
    - compute
  region: "us-central1"
  project_id: elastic-observability
  credentials_file_path: "/Users/kaiyansheng/Downloads/elastic-observability-d17781618202.json"
  exclude_labels: false
  period: 300s

It will be nice introduce a config parameter called regions to accept a list of strings:

- module: googlecloud
  metricsets:
    - compute
  regions:
    - us-central1
    - europe-west3
    - europe-west1
  project_id: elastic-observability
  credentials_file_path: "/Users/kaiyansheng/Downloads/elastic-observability-d17781618202.json"
  exclude_labels: false
  period: 300s

[elasticmachine]

Pinging @elastic/integrations-platforms (Team:Platforms)

[exekias]

can this one be closed now?

[kaiyan-sheng]

Not yet I think. Right now we accept partial region/zone as input parameter but not a list of strings.

[exekias]

sorry, my bad, I misread this!

[endorama]

@kaiyan-sheng do you think we can close this? Is 2 years old, is an enhancement but the functionality can already be used today.

[endorama]

@kaiyan-sheng and I discussed this, and there is still a consolidation benefit from implementing this. AWS does it, Azure does not need it (as it leverages subscriptions) and GCP leverage globs, which are not the most expressive way. Would be nice to introduce a region list, like in AWS.

We need to check if the reason why GCP is using glob is related to internal SDK usage and the feasibility of migrating to a list.