> For the complete documentation index, see [llms.txt](https://logbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://logbox.ortusbooks.com/usage/logbox-in-a-coldbox-application.md).

# LogBox in a ColdBox Application

Every ColdBox application can use LogBox by default since the main engine already uses it. By default ANY ColdBox application will be configured with a LogBox instance with the following appenders:

{% tabs %}
{% tab title="BoxLang" %}

```js
class{

    function configure(){
        logBox = {};

        // Define Appenders
        logBox.appenders = {
            console = { class="coldbox.system.logging.appenders.DummyAppender" }
        };

        // Root Logger
        logBox.root = {
            levelmax="OFF",
            levelMin="OFF",
            appenders="*"
        };
    }

}
```

{% endtab %}

{% tab title="CFML" %}

```cfscript
component{

    function configure(){
        logBox = {};

        // Define Appenders
        logBox.appenders = {
            console = { class="coldbox.system.logging.appenders.DummyAppender" }
        };

        // Root Logger
        logBox.root = {
            levelmax="OFF",
            levelMin="OFF",
            appenders="*"
        };
    }

}
```

{% endtab %}
{% endtabs %}

Also, the app will log on **ANY** severity by default up to `INFO` for the root logger and the ColdBox package. You can customize this default behavior by creating or modifying the `LogBox` element in your ColdBox configuration file and follow the same configuration approach as any normal LogBox configuration file.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://logbox.ortusbooks.com/usage/logbox-in-a-coldbox-application.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.