You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.next.asciidoc
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -348,6 +348,7 @@ https://github.com/elastic/beats/compare/v7.0.0-alpha2...master[Check the HEAD d
348
348
- Reference kubernetes manifests mount data directory from the host when running metricbeat as daemonset, so data persist between executions in the same node. {pull}17429[17429]
349
349
- Add more detailed error messages, system tests and small refactoring to the service metricset in windows. {pull}17725[17725]
350
350
- Stack Monitoring modules now auto-configure required metricsets when `xpack.enabled: true` is set. {issue}16471[[16471] {pull}17609[17609]
351
+
- Allow partial region and zone name in googlecloud module config. {pull}17913[17913]
351
352
- Add aggregation aligner as a config parameter for googlecloud stackdriver metricset. {issue}17141[[17141] {pull}17719[17719]
352
353
- Move the perfmon metricset to GA. {issue}16608[16608] {pull}17879[17879]
Copy file name to clipboardExpand all lines: metricbeat/docs/modules/googlecloud.asciidoc
+73-3Lines changed: 73 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,20 @@ Note: extra GCP charges on Stackdriver Monitoring API requests will be generated
16
16
== Module config and parameters
17
17
This is a list of the possible module parameters you can tune:
18
18
19
-
* *zone*: A single string with the zone you want to monitor like "us-central1-a". If you need to fetch from multiple regions, you have to setup a different configuration for each (but you don't need a new instance of Metricbeat running)
20
-
21
-
* *region*: A single string with the region you want to monitor like "us-central1". This will enable monitoring for all zones under this region.
19
+
* *zone*: A single string with the zone you want to monitor like `us-central1-a`.
20
+
Or you can specific a partial zone name like `us-central1-`, which will monitor
21
+
all zones start with `us-central1-`: `us-central1-a`, `us-central1-b`,
22
+
`us-central1-c` and `us-central1-f`.
23
+
Please see https://cloud.google.com/compute/docs/regions-zones#available[GCP zones]
24
+
for zones that are available in GCP.
25
+
26
+
* *region*: A single string with the region you want to monitor like `us-central1`.
27
+
This will enable monitoring for all zones under this region. Or you can specific
28
+
a partial region name like `us-east`, which will monitor all regions start with
29
+
`us-east`: `us-east1` and `us-east4`. If both region and zone are configured,
30
+
only region will be used.
31
+
Please see https://cloud.google.com/compute/docs/regions-zones#available[GCP regions]
32
+
for regions that are available in GCP.
22
33
23
34
* *project_id*: A single string with your GCP Project ID
24
35
@@ -28,6 +39,56 @@ This is a list of the possible module parameters you can tune:
28
39
29
40
* *period*: A single time duration specified for this module collection frequency.
30
41
42
+
[float]
43
+
== Example configuration
44
+
* `compute` metricset is enabled to collect metrics from `us-central1-a` zone
Authentication and authorization in Google Cloud Platform can be achieved in many ways. For the current version of the Google Cloud Platform module for Metricbeat, the only supported method is using Service Account JSON files. A typical JSON with a private key looks like this:
Copy file name to clipboardExpand all lines: x-pack/metricbeat/module/googlecloud/_meta/docs.asciidoc
+69-5Lines changed: 69 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,18 +6,82 @@ Note: extra GCP charges on Stackdriver Monitoring API requests will be generated
6
6
== Module config and parameters
7
7
This is a list of the possible module parameters you can tune:
8
8
9
-
* *zone*: A single string with the zone you want to monitor like "us-central1-a". If you need to fetch from multiple regions, you have to setup a different configuration for each (but you don't need a new instance of Metricbeat running)
10
-
11
-
* *region*: A single string with the region you want to monitor like "us-central1". This will enable monitoring for all zones under this region.
9
+
* *zone*: A single string with the zone you want to monitor like `us-central1-a`.
10
+
Or you can specific a partial zone name like `us-central1-` or `us-central1-*`,
11
+
which will monitor all zones start with `us-central1-`: `us-central1-a`,
12
+
`us-central1-b`, `us-central1-c` and `us-central1-f`.
13
+
Please see https://cloud.google.com/compute/docs/regions-zones#available[GCP zones]
14
+
for zones that are available in GCP.
15
+
16
+
* *region*: A single string with the region you want to monitor like `us-central1`.
17
+
This will enable monitoring for all zones under this region. Or you can specific
18
+
a partial region name like `us-east` or `us-east*`, which will monitor all regions start with
19
+
`us-east`: `us-east1` and `us-east4`. If both region and zone are configured,
20
+
only region will be used.
21
+
Please see https://cloud.google.com/compute/docs/regions-zones#available[GCP regions]
22
+
for regions that are available in GCP.
12
23
13
24
* *project_id*: A single string with your GCP Project ID
14
25
15
-
* *credentials_file_path*: A single string pointing to the JSON file path reachable by Metricbeat that you have created using IAM.
26
+
* *credentials_file_path*: A single string pointing to the JSON file path
27
+
reachable by Metricbeat that you have created using IAM.
16
28
17
-
* *exclude_labels*: (`true`/`false` default `false`) Do not extract extra labels and metadata information from Metricsets and fetch metrics onlly. At the moment, *labels and metadata extraction is only supported* in Compute Metricset.
29
+
* *exclude_labels*: (`true`/`false` default `false`) Do not extract extra labels
30
+
and metadata information from metricsets and fetch metrics only. At the moment,
31
+
*labels and metadata extraction is only supported* in `compute` metricset.
18
32
19
33
* *period*: A single time duration specified for this module collection frequency.
20
34
35
+
[float]
36
+
== Example configuration
37
+
* `compute` metricset is enabled to collect metrics from `us-central1-a` zone
Authentication and authorization in Google Cloud Platform can be achieved in many ways. For the current version of the Google Cloud Platform module for Metricbeat, the only supported method is using Service Account JSON files. A typical JSON with a private key looks like this:
0 commit comments