# How Does LogBox Work?

![](/files/XqxjrRe9IM0ikO9l2xei)

LogBox has five main components:

1. **LogBox**
   1. The central library that stores your loggers, appenders, categories, and configuration
2. **Logger**
   1. The class in charge of sending messages to the appropriate destinations according to the category it has been defined with.
3. **Categories**
   1. Each Logger is created with a unique category that usually maps to the classpath of the CFC that uses the logger.
4. **Appenders**
   1. Components that receive log events and send them for storage in their implementations: files, consoles, etc.
5. **Layouts**
   1. The appenders will send the messages to their destinations using a specified format.  This is called the layout of the message. LogBox comes with default layouts, but you can build your own.

These components work in unison to deliver messages' logging and tracing and control how they are logged. You will primarily interact with the **Logger** component as it will send your statements to the **Appenders** you have configured. Users can extend LogBox and build custom appenders and layouts.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://logbox.ortusbooks.com/getting-started/how-does-logbox-work.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.