> 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/logger/dynamic-appenders.md).

# Dynamic Appenders

Each logger object has several methods that you can use in order to interact with the logger's appenders. You can add, remove, clear or list the appenders on a specific logger instance. Below are the methods you can use in the logger class to interact with appenders:

| Method                | Return Type | Description                                               |
| --------------------- | ----------- | --------------------------------------------------------- |
| hasAppenders()        | `Boolean`   | Checks if the logger has any appenders attached to it     |
| getAppenders()        | `Struct`    | Returns the map of registered appenders                   |
| getAppender(name)     | `Appender`  | Return a named appender if it is registered in the logger |
| appenderExists(name)  | `Boolean`   | Checks if a named appender exists in the logger           |
| addAppender(Appender) | `void`      | Register an appender with the logger at runtime           |
| removeAppender(name)  | `Boolean`   | Will un-register an appender from this logger             |
| removeAllAppenders()  | `void`      | Will try to un-register all appenders from this logger    |

So you can easily add/remove/check the appenders on any logger at any time.

```javascript
//Add your own appender at runtime
jms = createObject( "component", "com.appender.JMSAppender" ).init( "JMSAppender", properties );
logger.addAppender( jms );

//log a message to all appenders and to my jms appender:
logger.fatal( "I FAILED MAN!" );

//remove it
logger.removeAppender( "JMSAppender" );
```


---

# 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/logger/dynamic-appenders.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.