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.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,19 @@
1
1
## master / unreleased
2
2
3
+
## 0.18.0 / 2025-01-16
4
+
5
+
-[FEATURE] Support more specific prefixes in ?collect parameter #387
6
+
-[FEATURE] Enabling monitoring metrics, aggregate deltas, and descriptor cache with ?collect #389
7
+
8
+
## 0.17.0 / 2024-11-04
9
+
10
+
Deprecation notice: The comma delimited flags `google.project-id` and `monitoring.metrics-type-prefixes` are being replaced by repeatable flags `google.project-ids` and `monitoring.metrics-prefixes`. The comma delimited flags will be supported for at least one more release.
11
+
12
+
-[CHANGE] Migrate logging to promslog #378
13
+
-[ENHANCEMENT] Sanitize metric type prefixes to prevent duplicate metrics #319
14
+
-[ENHANCEMENT] Add project ID to all logs from the collector #362
15
+
-[FEATURE] Add support for specifying comma-delimited string flags as repeatable flags #355
|`google.project-id`| No | GCloud SDK auto-discovery |Comma seperated list of Google Project IDs |
81
+
|`google.project-ids`| No | GCloud SDK auto-discovery |Repeatable flag of Google Project IDs |
82
82
|`google.projects.filter`| No || GCloud projects filter expression. See more [here](https://cloud.google.com/sdk/gcloud/reference/projects/list). |
83
83
|`monitoring.metrics-ingest-delay`| No || Offsets metric collection by a delay appropriate for each metric type, e.g. because bigquery metrics are slow to appear |
84
84
|`monitoring.drop-delegated-projects`| No | No | Drop metrics from attached projects and fetch `project_id` only. |
85
-
|`monitoring.metrics-type-prefixes`| Yes ||Comma separated Google Stackdriver Monitoring Metric Type prefixes (see [example][metrics-prefix-example] and [available metrics][metrics-list]) |
85
+
|`monitoring.metrics-prefixes`| Yes ||Repeatable flag of Google Stackdriver Monitoring Metric Type prefixes (see [example][metrics-prefix-example] and [available metrics][metrics-list]) |
86
86
|`monitoring.metrics-interval`| No |`5m`| Metric's timestamp interval to request from the Google Stackdriver Monitoring Metrics API. Only the most recent data point is used |
87
87
|`monitoring.metrics-offset`| No |`0s`| Offset (into the past) for the metric's timestamp interval to request from the Google Stackdriver Monitoring Metrics API, to handle latency in published metrics |
88
88
|`monitoring.filters`| No || Additonal filters to be sent on the Monitoring API call. Add multiple filters by providing this parameter multiple times. See [monitoring.filters](#using-filters) for more info. |
@@ -143,8 +143,9 @@ If we want to get all `CPU` (`compute.googleapis.com/instance/cpu`) and `Disk` (
pubsub.googleapis.com/subscription/num_undelivered_messages (apply to only the specific subscription metric) \
164
165
165
166
The `filter_query` will be applied to a final metrics API query when querying for metric data. You can read more about the metric API filter options in GCPs documentation https://cloud.google.com/monitoring/api/v3/filters
166
-
167
+
167
168
The final query sent to the metrics API already includes filters for project and metric type. Each applicable `filter_query` will be appended to the query with an AND
0 commit comments