> 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/getting-started/how-does-logbox-work.md).

# How Does LogBox Work?

![](https://content.gitbook.com/content/IqREipubq1Esn3UHHN0K/blobs/MCMq76M8hCwdjZwMjAUk/image.png)

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 class 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
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/getting-started/how-does-logbox-work.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.