# How can I disable debug logs?

**URL:** https://discourse.getdbt.com/t/how-can-i-disable-debug-logs/6261
**Category:** Help
**Created:** [January 20, 2023, 9:05am UTC](https://discourse.getdbt.com/t/how-can-i-disable-debug-logs/6261 "2023-01-20T09:05:01Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![spacecowboy](https://avatars.discourse-cdn.com/v4/letter/s/6a8cbe/32.png) [@spacecowboy](https://discourse.getdbt.com/u/spacecowboy)
#### Post date: [January 20, 2023, 9:05am UTC](https://discourse.getdbt.com/t/how-can-i-disable-debug-logs/6261/1 "2023-01-20T09:05:01Z")

</div>

## The problem I’m having

After upgrading from 1.3.0 to 1.3.2, I’m getting debug logs all of a sudden and I don’t know why.

```auto
$ DBT_DEBUG=false dbt build --select models/staging/yobify/+
INFO:configured_file:

============================== 2023-01-20 08:57:13.991556 | 7f36c610-b7a7-4282-ab93-80cfd435a872 ==============================
08:57:13.991591 [info] [MainThread]: Running with dbt=1.3.2
08:57:13 Running with dbt=1.3.2
INFO:configured_std_out:08:57:13 Running with dbt=1.3.2
DEBUG:configured_file:08:57:13.992240 [debug] [MainThread]: running dbt with arguments {'write_json': True, 'use_colors': True, 'printer_width': 80, 'version_check': True, 'partial_parse': True, 'static_parser': True, 'profiles_dir': '/workspaces/elt/transform', 'send_anonymous_usage_stats': False, 'event_buffer_size': 100000, 'quiet': False, 'no_print': False, 'cache_selected_only': False, 'indirect_selection': 'eager', 'resource_types': [], 'select': ['models/staging/yobify/+'], 'which': 'build', 'rpc_method': 'build'}
DEBUG:configured_file:08:57:13.992439 [debug] [MainThread]: Tracking: do not track
DEBUG:configured_file:08:57:14.241083 [debug] [MainThread]: Partial parsing enabled: 0 files deleted, 0 files added, 0 files changed.
DEBUG:configured_file:08:57:14.241355 [debug] [MainThread]: Partial parsing enabled, no changes found, skipping parsing
INFO:configured_file:08:57:14.405057 [info] [MainThread]: Found 148 models, 304 tests, 0 snapshots, 0 analyses, 670 macros, 0 operations, 2 seed files, 68 sources, 0 exposures, 3 metrics
08:57:14 Found 148 models, 304 tests, 0 snapshots, 0 analyses, 670 macros, 0 operations, 2 seed files, 68 sources, 0 exposures, 3 metrics
INFO:configured_std_out:08:57:14 Found 148 models, 304 tests, 0 snapshots, 0 analyses, 670 macros, 0 operations, 2 seed files, 68 sources, 0 exposures, 3 metrics
INFO:configured_file:08:57:14.450782 [info] [MainThread]: 
08:57:14  
INFO:configured_std_out:08:57:14  

```

## The context of why I’m trying to do this

## What I’ve already tried

I’ve tried running with `DBT_DEBUG=false` as above but there is no change.

I have searched and searched but have not found any ENV var set or anything that could explain this.

Any suggestions on what to try next??

---

<div class="post-metadata">

### Author: ![spacecowboy](https://avatars.discourse-cdn.com/v4/letter/s/6a8cbe/32.png) [@spacecowboy](https://discourse.getdbt.com/u/spacecowboy)
#### Post date: [January 20, 2023, 10:45am UTC](https://discourse.getdbt.com/t/how-can-i-disable-debug-logs/6261/2 "2023-01-20T10:45:20Z")

</div>

I nailed it down to something weird in my vs code devcontaner. I rebuilt it and the problem went away.

---

<div class="post-metadata">

### Author: ![joellabes](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/joellabes/32/3980_2.png) [@joellabes](https://discourse.getdbt.com/u/joellabes)
#### Post date: [January 20, 2023, 7:04pm UTC](https://discourse.getdbt.com/t/how-can-i-disable-debug-logs/6261/3 "2023-01-20T19:04:30Z")

</div>

Thanks for closing the loop!

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex020/uploads/getdbt/original/1X/a7a7ca1fe379aaf90952b0e13118a817babcd14f.png) [@system](https://discourse.getdbt.com/u/system)
#### Post date: [January 27, 2023, 7:05pm UTC](https://discourse.getdbt.com/t/how-can-i-disable-debug-logs/6261/4 "2023-01-27T19:05:20Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
