Skip to content

Commit 4c9b6e8

Browse files
authored
prep rel1.5 (#124)
1 parent e4bcf43 commit 4c9b6e8

File tree

3 files changed

+19
-10
lines changed

3 files changed

+19
-10
lines changed

CHANGELOG.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,10 @@
11
# Changelog
2+
## 1.5.0 (2025-05-29)
3+
* Update plugin to support access token auth
4+
* Add datasource syncer
5+
* Fix message from jsonPayload doesn't show up in Grafana
6+
* Update a few dependencies
7+
28
## 1.4.1 (2024-03-22)
39
* Fix an encoding issue for parentheses
410
* Fix cloud logging link scope issue

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ You can follow the steps to enable it:
1919

2020
### Generate a JWT file & Assign IAM Permissions
2121

22-
1. If you don't have a GCP project, add a new GCP project. [link](https://cloud.google.com/resource-manager/docs/creating-managing-projects#console)
22+
1. If you don't have a GCP project, add a new GCP project [here](https://cloud.google.com/resource-manager/docs/creating-managing-projects#console)
2323
2. Open the [Credentials](https://console.developers.google.com/apis/credentials) page in the Google API Console
2424
3. Click **Create Credentials** then click **Service account**
2525
4. On the Create service account page, enter the Service account details
@@ -32,7 +32,7 @@ If you want to access logs in multiple cloud projects, you need to ensure the se
3232

3333
If you host Grafana on a GCE VM, you can also use the [Compute Engine service account](https://cloud.google.com/compute/docs/access/service-accounts#serviceaccount). You need to make sure the service account has sufficient permissions to access the scopes and logs in all projects.
3434

35-
Similar to [Prometheus data sources on Google Cloud](https://cloud.google.com/stackdriver/docs/managed-prometheus/query#use-serverless), you can also configure a scheduled job to use an OAuth2 access token to view the logs. Please follow the steps in the [data source syncer README](./datasource-syncer/README.md) to configure it.
35+
Similar to [Prometheus data sources on Google Cloud](https://cloud.google.com/stackdriver/docs/managed-prometheus/query#use-serverless), you can also configure a scheduled job to use an OAuth2 access token to view the logs. Please follow the steps in the [data source syncer README](https://github.com/GoogleCloudPlatform/cloud-logging-data-source-plugin/blob/main/datasource-syncer/README.md) to configure it.
3636

3737
### Service account impersonation
3838
You can also configure the plugin to use [service account impersonation](https://cloud.google.com/iam/docs/service-account-impersonation).
@@ -43,8 +43,8 @@ by this plugin needs logging read and project list permissions.
4343
1. With Grafana restarted, navigate to `Configuration -> Data sources` (or the route `/datasources`)
4444
2. Click "Add data source"
4545
3. Select "Google Cloud Logging"
46-
4. Provide credentials in a JWT file, either by using the file selector or pasting the contents of the file.
47-
5. Click "Save & test" to test that logs can be queried from Cloud Logging.
46+
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
47+
5. Click "Save & test" to test that logs can be queried from Cloud Logging
4848

4949
![image info](https://github.com/GoogleCloudPlatform/cloud-logging-data-source-plugin/blob/main/src/img/cloud_logging_config.png?raw=true)
5050

datasource-syncer/README.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -141,9 +141,9 @@ and [Cloud Scheduler](https://cloud.google.com/scheduler), do the following:
141141
142142
```bash
143143
# These values are required.
144-
export GRAFANA_INSTANCE_URL=YOUR_GRAFANA_INSTANCE_URL # The Grafana instance URL from step 2. This is a URL. Include "http://" or "https://".
145-
export GRAFANA_DATASOURCE_UID=YOUR_GRAFANA_DATASOURCE_UID # The Grafana data source UID from step 3. This is not a URL.
146-
export GRAFANA_SERVICE_ACCOUNT_TOKEN=YOUR_GRAFANA_SERVICE_ACCOUNT_TOKEN # The Grafana service account token from step 4.
144+
export GRAFANA_INSTANCE_URL=YOUR_GRAFANA_INSTANCE_URL # The Grafana instance URL from step 3. This is a URL. Include "http://" or "https://".
145+
export GRAFANA_DATASOURCE_UID=YOUR_GRAFANA_DATASOURCE_UID # The Grafana data source UID from step 4. This is not a URL.
146+
export GRAFANA_SERVICE_ACCOUNT_TOKEN=YOUR_GRAFANA_SERVICE_ACCOUNT_TOKEN # The Grafana service account token from step 5.
147147
```
148148
149149
1. Create a secret in Secret Manager:
@@ -212,8 +212,11 @@ and [Cloud Scheduler](https://cloud.google.com/scheduler), do the following:
212212
213213
It can take up to 15 seconds for the data source to be updated.
214214
215-
1. Go to your newly configured Grafana data source and verify the **Access Token
216-
** field has the value `configured` and the **Project ID** field has your cloud project id. You might have to refresh the page. Once verified, go to the bottom
215+
1. Go to your newly configured Grafana data source and verify the **Access Token**
216+
field has the value `configured` and the **Project ID** field displays the Google
217+
Cloud Project ID you configured (e.g., the value of your ${PROJECT_ID} variable).
218+
219+
You might have to refresh the page. Once verified, go to the bottom
217220
of the page, select **Save & test**, and ensure you see a green checkmark saying that
218221
the datasource is properly configured. You need to select **Save & test** at
219-
least once to ensure that label autocompletion in Grafana works.
222+
least once to ensure that label autocompletion in Grafana works.

0 commit comments

Comments
 (0)