Skip to content
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] GoogleCloud Dashboards using wrong fields #18962

Closed
LucaWintergerst opened this issue Jun 4, 2020 · 1 comment · Fixed by #18980
Closed

[Metricbeat] GoogleCloud Dashboards using wrong fields #18962

LucaWintergerst opened this issue Jun 4, 2020 · 1 comment · Fixed by #18980
Assignees
Labels
bug Metricbeat Metricbeat Team:Platforms Label for the Integrations - Platforms team

Comments

@LucaWintergerst
Copy link

The GoogleCloud Dashboards are using field names like googlecloud.compute.instance.cpu.utilization, while Metricbeat is sending fields like googlecloud.compute.instance.cpu.utilization.value. Note the .value at the end. This causes all visualizations to break.

For confirmed bugs, please report:

  • Version: 7.8.0-0dba676b
  • Operating System: MacOs
  • Discuss Forum URL:
  • Steps to Reproduce:

Setup Metricbeat with the GoogleCloud module

- module: googlecloud
  metricsets:
    - compute
  region: "us-central1"
  project_id: "elastic-foobar"
  credentials_file_path: "foobar.json"
  exclude_labels: false
  period: 1m

setup Dashboards ./metricbeat setup --dashboards
start Metricbeat ./metricbeat -e
try to load Dashboard
Kibana will error with Error fetching fields for index pattern metricbeat-*

@LucaWintergerst LucaWintergerst added Metricbeat Metricbeat Team:Platforms Label for the Integrations - Platforms team labels Jun 4, 2020
@elasticmachine
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Metricbeat Metricbeat Team:Platforms Label for the Integrations - Platforms team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants