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
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,9 @@
1
1
# Changelog
2
+
## 1.6.3 (2026-04-05)
3
+
* Add Project List Filter to restrict which projects appear in dropdowns using regex patterns
4
+
* Add Log Bucket Filter with include/exclude support — prefix patterns with `!` to exclude matching buckets (e.g., `!.*/_Default` to hide Default buckets)
5
+
* Fix race condition in variable query where default project could be unresolved before bucket/view queries run
6
+
2
7
## 1.6.2 (2026-03-18)
3
8
* Fix project dropdown search failing with "contains global restriction" error
4
9
* Fix `useEffect` dependency causing excessive API calls for log buckets and views
Copy file name to clipboardExpand all lines: README.md
+57-2Lines changed: 57 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,19 +49,65 @@ Once Grafana is configured with Google authentication for signing in, ensure tha
49
49
50
50
You can then configure the data source with the `OAuth Passthrough` authentication method. Ensure that you provide a default project ID otherwise the health-check will fail.
51
51
52
+
### Universe Domain
53
+
54
+
If you are using a Google Cloud environment that uses a custom universe domain (e.g., a sovereign or isolated cloud), you can configure the **Universe Domain** in the data source settings. This tells the plugin to use a different API endpoint instead of the default `googleapis.com`.
55
+
56
+
Leave this field empty to use the default `googleapis.com` domain.
57
+
52
58
### Grafana Configuration
53
59
54
60
1. With Grafana restarted, navigate to `Configuration -> Data sources` (or the route `/datasources`)
55
61
2. Click "Add data source"
56
62
3. Select "Google Cloud Logging"
57
63
4. Provide credentials from your JWT file, either by uploading it using the file selector or by pasting its contents directly into the designated field
58
-
5. Click "Save & test" to test that logs can be queried from Cloud Logging
64
+
5. Optionally, configure the **Universe Domain** if you are using a non-default GCP environment
65
+
6. Optionally, configure the **Project List Filter** to restrict which projects appear in the project dropdown (see [Project List Filter](#project-list-filter) below)
66
+
7. Optionally, configure the **Log Bucket Filter** to include or exclude specific log buckets from the bucket dropdown (see [Log Bucket Filter](#log-bucket-filter) below)
67
+
8. Click "Save & test" to test that logs can be queried from Cloud Logging
If you have access to many GCP projects, you can restrict which projects appear in the project dropdown by configuring a **Project List Filter** in the data source settings.
74
+
75
+
Enter project IDs or regex patterns in the text area, one per line. Only projects matching at least one pattern will appear in the dropdown. Leave the field empty to show all projects (the default behavior).
76
+
77
+
Each line is treated as a [regular expression](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions) anchored to the full project ID. For example:
78
+
79
+
| Pattern | Matches |
80
+
| --- | --- |
81
+
|`my-project-123`| Only the exact project `my-project-123`|
82
+
|`team-alpha-.*`| All projects starting with `team-alpha-`|
83
+
|`prod-.*-logging`| Projects like `prod-us-logging`, `prod-eu-logging`, etc. |
84
+
85
+
You can combine multiple patterns (one per line) to match the union of all patterns. If a pattern contains invalid regex syntax, it is treated as a literal string match.
86
+
87
+
### Log Bucket Filter
88
+
89
+
You can control which log buckets appear in the bucket dropdown by configuring a **Log Bucket Filter** in the data source settings. This supports both **include** and **exclude** patterns, which is especially useful for excluding default system buckets from initiative projects.
90
+
91
+
Enter patterns in the text area, one per line:
92
+
-**Include patterns** (no prefix): Only buckets matching at least one include pattern are shown.
93
+
-**Exclude patterns** (prefixed with `!`): Buckets matching any exclude pattern are removed.
94
+
95
+
When both include and exclude patterns are present, include patterns are applied first, then exclude patterns remove from the result. Leave the field empty to show all buckets (the default behavior).
96
+
97
+
Patterns are [regular expressions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions) anchored to the **full bucket path** as returned by the API (e.g., `global/buckets/_Default` or `locations/us-central1/buckets/my-bucket`).
98
+
99
+
| Pattern | Effect |
100
+
| --- | --- |
101
+
|`!.*/_Default`| Exclude all `_Default` buckets across all locations |
102
+
|`!.*/_Default`<br>`!.*/_Required`| Exclude both `_Default` and `_Required` buckets |
103
+
|`.*my-app-logs`| Include only buckets ending with `my-app-logs`|
104
+
|`global/buckets/.*`<br>`!.*/_Default`| Include only `global/buckets/*` buckets, but exclude `_Default`|
105
+
106
+
If a pattern contains invalid regex syntax, it is treated as a literal string match.
107
+
62
108
### An alternative way to provision the data source
63
109
64
-
After the plugin is installed, you can define and configure the data source in YAML files as part of Grafana’s provisioning system, similar to [the Google Cloud Monitoring plugin](https://grafana.com/docs/grafana/latest/datasources/google-cloud-monitoring/#provision-the-data-source). For more information about provisioning, and for available configuration options, refer to [Provisioning Grafana](https://grafana.com/docs/grafana/latest/administration/provisioning/#data-sources).
110
+
After the plugin is installed, you can define and configure the data source in YAML files as part of Grafana's provisioning system, similar to [the Google Cloud Monitoring plugin](https://grafana.com/docs/grafana/latest/datasources/google-cloud-monitoring/#provision-the-data-source). For more information about provisioning, and for available configuration options, refer to [Provisioning Grafana](https://grafana.com/docs/grafana/latest/administration/provisioning/#data-sources).
65
111
66
112
The following YAML is an example.
67
113
@@ -74,6 +120,15 @@ datasources:
74
120
access: proxy
75
121
jsonData:
76
122
authenticationType: gce
123
+
# Optional: restrict the project dropdown to matching projects (regex supported)
124
+
# projectListFilter: |
125
+
# my-project-123
126
+
# team-alpha-.*
127
+
# Optional: filter log buckets (prefix with ! to exclude)
128
+
# logBucketFilter: |
129
+
# !.*/_Default
130
+
# Optional: custom universe domain for sovereign cloud environments
description="Enter project IDs or regex patterns, one per line. Only matching projects will appear in the project dropdown. Leave empty to show all projects."
description="Filter log buckets in dropdowns. Enter patterns one per line. Prefix a line with ! to exclude matching buckets. Without !, only matching buckets are included. Patterns are regex matched against the full bucket path. Leave empty to show all buckets."
0 commit comments