Is this a new bug in dbt-common?
Current Behavior
When Sentry integration is enabled in Airflow, it sends events for all exceptions and logs with level ERROR.
In a default Cosmos setup where dbt is run using Local + Programmatic invocation, Sentry gets flooded with errors that aren’t actually errors — just debug info.
This happens because of this piece of logic in dbt-common:
# We send PrintEvent to logger as error so it goes to stdout
# when --quiet flag is set.
# --quiet flag will filter out all events lower than ERROR.
Not sure if this is a bug or intentional, but it's definitely not obvious and was a pain to debug.
Leaving this here for future generations — hope it shows up on Google.
If I find a way to filter this out, I’ll drop it in the comments.
Expected Behavior
.
Steps To Reproduce
.
Relevant log output
Additional Context
Is this a new bug in dbt-common?
Current Behavior
When Sentry integration is enabled in Airflow, it sends events for all exceptions and logs with level ERROR.
In a default Cosmos setup where dbt is run using Local + Programmatic invocation, Sentry gets flooded with errors that aren’t actually errors — just debug info.
This happens because of this piece of logic in dbt-common:
Not sure if this is a bug or intentional, but it's definitely not obvious and was a pain to debug.
Leaving this here for future generations — hope it shows up on Google.
If I find a way to filter this out, I’ll drop it in the comments.
Expected Behavior
.
Steps To Reproduce
.
Relevant log output
Additional Context