> ## Documentation Index
> Fetch the complete documentation index at: https://docs.entire.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Logging and Diagnostics

> Configure log verbosity, inspect active settings, and collect diagnostics.

Use this page when you need more detail about what Entire is doing locally or need to confirm which settings are active.

Most diagnostic output is local to your machine. Turn on debug logging temporarily unless the whole team needs the same verbosity.

## Start here if

Use this page to:

* turn on debug logging while investigating an issue
* confirm which settings Entire is using
* run a repository health check
* view logs or create a diagnostic bundle

## Log level

`log_level` controls how much detail Entire writes to operational logs. The default is `info`; use `debug` while investigating.

<Tabs>
  <Tab title="Temporary override">
    Use `ENTIRE_LOG_LEVEL` when you need debug output for one command or one shell session.

    ```bash theme={null}
    ENTIRE_LOG_LEVEL=debug entire status
    ```

    `ENTIRE_LOG_LEVEL` takes precedence over settings files.
  </Tab>

  <Tab title="Local settings">
    Use local settings for temporary debug logging or machine-specific troubleshooting.

    ```json .entire/settings.local.json theme={null}
    {
      "log_level": "debug"
    }
    ```
  </Tab>

  <Tab title="Project settings">
    Use project settings only when the whole repository should use the same log level.

    ```json .entire/settings.json theme={null}
    {
      "log_level": "debug"
    }
    ```
  </Tab>
</Tabs>

Supported values are `debug`, `info`, `warn`, and `error`.

## Inspect active settings

Run:

```bash theme={null}
entire status --detailed
```

Use this after editing settings to confirm Entire is reading the value you changed and to see which settings file supplied it.

## Check repository health

Run:

```bash theme={null}
entire doctor
```

Use `entire doctor` when sessions look stuck, Git hooks are not firing, checkpoint data is not syncing, or `entire status` shows warnings. It checks repository setup, hook state, checkpoint metadata, and common session problems.

## View or share diagnostics

Entire writes local diagnostic logs under `.entire/logs/`. Keep logs local unless someone asks for a specific file or bundle while troubleshooting.

<Tabs>
  <Tab title="View logs">
    Show recent operational logs with:

    ```bash theme={null}
    entire doctor logs
    ```

    To stream new log lines while you reproduce an issue, run:

    ```bash theme={null}
    entire doctor logs --follow
    ```
  </Tab>

  <Tab title="Create bundle">
    Create a diagnostic bundle for an issue report with:

    ```bash theme={null}
    entire doctor bundle
    ```

    Diagnostic bundles are redacted by default. Use `--raw` only when support has asked for an unredacted bundle.
  </Tab>
</Tabs>

For other local runtime files under `.entire/`, see [Entire-Generated Files](/guides/configuration/entire-files).

## Trace slow hooks

Hook performance traces are only available at debug log level.

Turn on debug logging, reproduce the slow Git command, then run:

```bash theme={null}
entire doctor trace
```

Use this when `git commit` or `git push` works but feels slower than expected.

## Verify logging changes

After changing logging settings, rerun the command you were investigating and check the logs:

```bash theme={null}
entire doctor logs
```