-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(DENG-4577): add monitoring bigeye_usage view to allow us to get more insight into bq usage and costs from bigeye #6260
base: main
Are you sure you want to change the base?
Conversation
…t into bq usage and costs from bigeye
@@ -48,6 +48,7 @@ jobs_by_project AS ( | |||
user_email, | |||
REGEXP_EXTRACT(query, r'Username: (.*?),') AS username, | |||
REGEXP_EXTRACT(query, r'Query ID: (\w+), ') AS query_id, | |||
REGEXP_EXTRACT(query, r'\'metric_id:(\d+)\'') AS bigeye_metric_id, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Marlene-M-Hirose @wwyc was there a specific reason why we didn't just pass the query through here? There is another bit of information I could extract here for BigEye, but wasn't sure if I should be polluting this query with BigEye specific details? If I had query available here I could just do it downstream in my bigeye monitoring view.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kik-kik , I do not think adding this specific information here is good. This table is supposed to be focused on BigQuery usage, not for monitoring bigeye. I would prefer to keep bigeye separate from this table.
We didn't add the query because we didn't need the query. We only needed the query_id and the username from the query.
This comment has been minimized.
This comment has been minimized.
Integration report for "feat: add extract of bigeye table id checked in the bq information_schema"
|
feat(DENG-4577): add monitoring bigeye_usage view to allow us to get more insight into bq usage and costs from bigeye
Description
This aims to provide a data structure to enable us to build a dashboard in Looker to allow us to monitor BigEye related spending and usage in BigQuery.
┆Issue is synchronized with this Jira Task