> For the complete documentation index, see [llms.txt](https://boxlang.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boxlang.ortusbooks.com/boxlang-language/reference/components/system/log.md).

# Log

Logs information to the specified log file

## Component Signature

```
<bx:Log text=[string]
file=[string]
log=[string]
type=[string]
application=[boolean] />
```

### Attributes

| Atrribute     | Type      | Required | Description                                                                                                                                                                                                                                                                        | Default |
| ------------- | --------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
| `text`        | `string`  | `false`  | The text to log                                                                                                                                                                                                                                                                    |         |
| `file`        | `string`  | `false`  | (COMPAT ONLY) Do not use anymore, use log instead. If defined, we will use this instead of log.                                                                                                                                                                                    |         |
| `log`         | `string`  | `false`  | <p>The destination logger to use. If not passed, we use the default logger (application.log).<br>If the logger is a file appender and it doesn't exist it will create it for you.<br>If the value is an absolue path, it will create a file appender for you at that location.</p> |         |
| `type`        | `string`  | `false`  | The log level of the entry. One of "Information", "Warning", "Error", "Debug", "Trace"                                                                                                                                                                                             | `info`  |
| `application` | `boolean` | `false`  |                                                                                                                                                                                                                                                                                    | `true`  |

## Examples

### Write an informational log entry

```java
<bx:log text="Application started successfully" type="Information">

```

### Write a warning to the log

```java
<bx:log text="Cache miss rate exceeding threshold" type="Warning">

```

### Write an error log entry

```java
<bx:log text="Database connection failed" type="Error">

```

### Log to a custom logger/file

```java
<bx:log text="Payment processed" log="payments" type="Information">

```

### Log with application name disabled

```java
<bx:log text="Debug trace" application="false" type="Debug">

```


---

# 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://boxlang.ortusbooks.com/boxlang-language/reference/components/system/log.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.