Add host inventory metrics to googlecloud compute metricset

[kaiyan-sheng]

What does this PR do?

Why is it important?

This PR is to add proposed host common fields into compute metricset:

• host.id
• host.name
• host.cpu.pct
• host.network.in.bytes
• host.network.in.packets
• host.network.out.bytes
• host.network.out.packets
• host.disk.read.bytes
• host.disk.write.bytes

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

How to test this PR locally

1. Start Metricbeat googlecloud module: ./metricbeat modules enable googlecloud
2. Edit modules.d/googlecloud.yml to only include compute metricset:

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

3.Change add_host_metadata processor config in metricbeat.yml file:

processors:
  - add_host_metadata:
      replace_fields: false

4. Start metricbeat
5. You should see metrics from compute metricset and includes fields listed above.

[elasticmachine]

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

[elasticmachine]

💚 Build Succeeded

Expand to view the summary

Build stats

• Build Cause: [Pull request #20391 updated]

• Start Time: 2020-08-19T22:33:23.418+0000

• Duration: 49 min 18 sec

Test stats 🧪

Test	Results
Failed	0
Passed	843
Skipped	72
Total	915

[jsoriano]

Nothing to change here, just thinking loud. It might be interesting to have cloud-agnostic common values for regions. So a user can more easily group metrics coming from asia-northeast1 in GCP, and ap-northeast-1 in AWS.

Imagine for example being able to ingest with something like this metadata:

"cloud.region": {
    "name": "asia-northeast1",
    "area": "asia-pacific",
    "country": "japan",
    "city": "tokyo",
}

And if it were ingested from AWS:

"cloud.region": {
    "name": "ap-northeast-1",
    "area": "asia-pacific",
    "country": "japan",
    "city": "tokyo",
}

Not sure if cloud providers have APIs for this information.

Though maybe for that we can add geodata through an ingest pipeline in the future.

[kaiyan-sheng]

@jsoriano Yeah good point! Different cloud has different names for regions. I don't see a specific API for GCP though but I think the geoip processor should be sufficient if we see good use cases in the future!