@@ -149,9 +149,20 @@ For example, if Compute Metricset fetches 14 metrics (which is the number of met
149149
150150[float]
151151== Metricsets
152- Currently, we have `compute`, `loadbalancing`, `pubsub`, `metrics` and
152+ Currently, we have `billing`, ` compute`, `loadbalancing`, `pubsub`, `metrics` and
153153`storage` metricset in `googlecloud` module.
154154
155+ [float]
156+ === `billing`
157+ This metricset fetches billing metrics from https://cloud.google.com/bigquery[GCP BigQuery]
158+ Cloud Billing allows users to export billing data into BigQuery automatically
159+ throughout the day. This metricset gets access to the daily cost detail table
160+ periodically to export billing metrics for further analysis.
161+
162+ The `billing` metricset comes with a predefined dashboard:
163+
164+ image::./images/metricbeat-googlecloud-billing-overview.png[]
165+
155166[float]
156167=== `compute`
157168This metricset fetches metrics from https://cloud.google.com/compute/[Compute Engine]
@@ -274,13 +285,25 @@ metricbeat.modules:
274285 - "instance/cpu/usage_time"
275286 - "instance/cpu/utilization"
276287 - "instance/uptime"
288+
289+ - module: googlecloud
290+ metricsets:
291+ - billing
292+ period: 24h
293+ project_id: "your project id"
294+ credentials_file_path: "your JSON credentials file path"
295+ dataset_id: "dataset id"
296+ table_pattern: "table pattern"
297+ cost_type: "regular"
277298----
278299
279300[float]
280301=== Metricsets
281302
282303The following metricsets are available:
283304
305+ * <<metricbeat-metricset-googlecloud-billing,billing>>
306+
284307* <<metricbeat-metricset-googlecloud-compute,compute>>
285308
286309* <<metricbeat-metricset-googlecloud-loadbalancing,loadbalancing>>
@@ -291,6 +314,8 @@ The following metricsets are available:
291314
292315* <<metricbeat-metricset-googlecloud-storage,storage>>
293316
317+ include::googlecloud/billing.asciidoc[]
318+
294319include::googlecloud/compute.asciidoc[]
295320
296321include::googlecloud/loadbalancing.asciidoc[]
0 commit comments