> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/guides/deploy/server-configuration/monitoring/browser-console-log.md).

# Browser Console Log

From Servoy 8.4 on, all client side messages from the browser's Console loggers (log (is send as info),error,info,warn,debug) will be send to the server and logged through the logger: org.sablo.BrowserConsole. By default this is not configured in the log4j.xml file so it logs WARN and ERROR messages from the browser. This could be adjusted by adding a logger:

```xml
<Logger name="org.sablo.BrowserConsole" level="INFO" />
```

by making it INFO you will see also Console.log and Console.info

You can also redirect this to a another file, see [Websocket Message logging (for debug purposes)](/guides/deploy/server-configuration/monitoring/websocket-log.md#websocket-log) for another sample how to do that.

Besides the [Console object](https://developer.mozilla.org/en-US/docs/Web/API/Console) of the browser, also the global [Window.onerror](https://developer.mozilla.org/en-US/docs/Web/API/Window/error_event) is catched and logged as error to the browser.


---

# 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://docs.servoy.com/guides/deploy/server-configuration/monitoring/browser-console-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.