Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Feature] Log BigQuery console link at the info level (instead of debug level) #1136

Closed
3 tasks done
wircho opened this issue Mar 13, 2024 · 3 comments
Closed
3 tasks done

[Feature] Log BigQuery console link at the info level (instead of debug level) #1136

wircho opened this issue Mar 13, 2024 · 3 comments
Assignees
@dataders
Labels
enhancement New feature or request refinement Product or leadership input needed Stale

Comments

@wircho
Copy link

wircho commented Mar 13, 2024

Is this your first time submitting a feature request?

  • I have read the expectations for open source contributors
  • I have searched the existing issues, and I could not find an existing issue for this feature
  • I am requesting a straightforward extension of existing dbt-bigquery functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Change the log level of the BigQuery console job link from debug to info

Describe alternatives you've considered

N/A

Who will this benefit?

Any team that runs jobs on the cloud (e.g. Airflow).

Debug-level logs, especially with full parse, are extremely verbose and long for large projects. We set our log level to info everywhere. So it would be useful to benefit from what is basically the most relevant and actionable information about the job, at the info level.

Are you interested in contributing this feature?

Yes

Anything else?

No response
@wircho wircho added enhancement New feature or request triage labels Mar 13, 2024
@wircho wircho mentioned this issue Mar 13, 2024
Closed
4 tasks
@dataders dataders self-assigned this Mar 25, 2024
@dataders dataders added refinement Product or leadership input needed and removed triage labels Mar 25, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

@github-actions github-actions bot added the Stale label Sep 22, 2024
@github-actions GitHub Actions
Copy link
Contributor

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 29, 2024
@dschneiderch
Copy link

dschneiderch commented Sep 29, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dataders dataders

Labels
enhancement New feature or request refinement Product or leadership input needed Stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update BigQuery console job link log level from debug to info wircho/dbt-bigquery
3 participants
@dschneiderch @dataders @wircho