Skip to content

[Metricbeat] gcp: fields do not respect naming best practices #27231

@endorama

Description

@endorama

While working at #26824 I noticed that the current implementation of the gcp module for Metricbeat does not seem to align to naming conventions.

Examples:

  • gcp.compute.instance.uptime.value is a value in seconds, for which sec suffix should be used
  • gcp.compute.instance.firewall.dropped_bytes_count.value is a bytes value, for which bytes suffix should be used

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions