From eb995a74312567d613871f3a354ed067322749fa Mon Sep 17 00:00:00 2001 From: Gabriel Pop Date: Tue, 24 Oct 2023 22:25:15 +0300 Subject: [PATCH] improve docs --- .../module/gcp/billing/_meta/docs.asciidoc | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/x-pack/metricbeat/module/gcp/billing/_meta/docs.asciidoc b/x-pack/metricbeat/module/gcp/billing/_meta/docs.asciidoc index d1d3ac691a11..90a2766a2f45 100644 --- a/x-pack/metricbeat/module/gcp/billing/_meta/docs.asciidoc +++ b/x-pack/metricbeat/module/gcp/billing/_meta/docs.asciidoc @@ -15,14 +15,13 @@ understanding of these formats, consult the https://cloud.google.com/billing/doc standard] and https://cloud.google.com/billing/docs/how-to/export-data-bigquery-tables/detailed-usage#detailed-usage-cost-data-schema[ detailed] data schema documentation. -For regular cost monitoring and analysis, standard tables utilize the -`gcp_billing_export_v1_` format, presenting a comprehensive -view of Google Cloud expenses. - -Alternatively, detailed tables, identifiable by the `gcp_billing_export_resource_v1_` -format, offer richer data. They include additional fields, such as `effective_price`, -enabling a more granular view of expenses. +For standard usage cost data, set the table pattern format to +`gcp_billing_export_v1`. This table pattern is set as the default when no other +is specified. +For detailed usage cost data, set the table pattern to `gcp_billing_export_resource_v1`. +Detailed tables include the standard fields and additional fields, such as +`effective_price`, enabling a more granular view of expenses. [float] === Metricset-specific configuration notes