> For the complete documentation index, see [llms.txt](https://docs.polarity.io/integrations/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.polarity.io/integrations/build-an-integration/debugging/using-integration-logs.md).

# Using Integration Logs

One method for debugging your integrations is to make use of the [Logger object](/integrations/build-an-integration/main/startup.md#logger) passed in through the `startup` method of the main module to log what your integration is doing.

You can then navigate to the log directory for your integration which defaults to `logs/integration.log` to tail and follow the file.

```bash
tail -f integration.log
```

You'll notice that the logs produced are in JSON making them difficult to read. You can use the `Bunyan` logger module to format them for you.

```bash
tail -f integration.log | /app/polarity-server/node_modules/bunyan/bin/bunyan -o short
```

If this is your first time using bunyan you will need to make it executable with the following command:

```bash
chmod a+x /app/polarity-server/node_modules/bunyan/bin/bunyan
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.polarity.io/integrations/build-an-integration/debugging/using-integration-logs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.