# Error Logs

Not the favourite place to be, but we all know errors are an inevitable part of developers' work. 

Luckily, GPTBoost segregates the error completions of your LLM app and displays them in an individual space. That empowers you to easily spot some of the most common patterns and potential bottlenecks.

<figure><img src="/files/7C7GKoSmxYROGTxgni8z" alt=""><figcaption><p>Error logs in GPTBoost</p></figcaption></figure>

Again as in the Request Log you have various filtering and ordering options- by time of occurrence or type of error. Let's say you want to check all client errors for the past 3 months. Nothing is easier than that - simply select 3m for filtering and order by 4xx.


---

# Agent Instructions: 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:

```
GET https://docs.gptboost.io/features/error-logs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.