> 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/extending-logbox/creating-custom-appenders/instance-members.md).

# Instance Members

Every Appender has access to the following public variables and injected references.

## Log Levels Enum

| Property         | Description                                                                                                                                        |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| `this.logLevels` | A reference to the `logbox.system.logging.LogLevels` class. Use this to access level constants (`this.logLevels.DEBUG`, etc.) and utility methods. |

## Injected References

These variables are automatically set by LogBox when the appender is registered. They are available as `variables.*` inside your appender and are empty strings (`""`) when LogBox is running in standalone mode (outside a ColdBox application).

| Property  | Description                                                                  |
| --------- | ---------------------------------------------------------------------------- |
| `logBox`  | A reference to the running `LogBox` instance.                                |
| `coldbox` | A reference to the ColdBox application controller. Empty in standalone mode. |
| `wirebox` | A reference to the WireBox injector. Empty in standalone mode.               |

## Configuration Properties

| Property      | Default                        | Description                                                                                                                                                                                                                                                                                      |
| ------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `lockTimeout` | `25`                           | Timeout in seconds used by the base `lock()` helper when acquiring named locks during concurrent appender operations.                                                                                                                                                                            |
| `logListener` | `{ active: false, queue: [] }` | Internal state for the async queue system. `active` indicates whether the log-listener scheduled task is currently running; `queue` is the array of pending log payloads awaiting processing. See [Async Appenders](/extending-logbox/creating-custom-appenders/async-appenders.md) for details. |


---

# 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/extending-logbox/creating-custom-appenders/instance-members.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.