grafana / grafana/google-bigquery-datasource

Feature: GCE for Alerting

Open
#533 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
40
Forks
24
Avg merge
3d 21h
Merged PRs (30d)
8

Description

When the data source is configured with Forward OAuth Identity, queries authenticate by forwarding the signed-in user's OAuth token to BigQuery. Alert rules evaluate in the background with no user session, so there is no token to forward and the query reaches BigQuery with no credentials:

googleapi: Error 401: Request is missing required authentication credential.
Expected OAuth 2 access token... reason: CREDENTIALS_MISSING

This makes alerting unusable on instances that rely on OAuth identity forwarding.

The solution is to give the users the ability to use a different authentication mechanism for alerts in case they need it or just keep it same as the main authentication.

I've made a PR already for my proposed solution, which is already tested and Fully backward compatible.

https://github.com/grafana/google-bigquery-datasource/pull/532

@zoltanbedi

Contributor guide

Open the contributing guide

Research direction

Start by reviewing linked pull request #532, which contains the proposed and tested solution. Check how alert-rule queries authenticate when Forward OAuth Identity is enabled, and verify that alerts can use a separate mechanism or retain the main authentication while remaining backward compatible.

Written by the indexing model from the issue text.

Assessment

Tech stack
google-cloud, typescript
Domain
authentication, cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.