> For the complete documentation index, see [llms.txt](https://prisma-logs.gitbook.io/prisma-logs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prisma-logs.gitbook.io/prisma-logs/docs/en/configuration/built-in-logs.md).

# Built-in logs

These logs come by themselves, no scan needed. Switch them on or off in the panel under **Categories → Built-in logs** (resource 2.8.1+) or in [config.lua](/prisma-logs/docs/en/configuration/configuration.md).

Every log has an `event` field. You can filter on it in the panel, for example only `left` or only `put in trunk`.

| Category        | Events                                                                                                                     | Fields                                                       | Source                 |
| --------------- | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ---------------------- |
| **connections** | `connecting`, `joined`, `left`, `character loaded`, `character unloaded`                                                   | name, identifier, discord, steam, reason                     | FiveM, ESX, QBCore     |
| **chat**        | `message`                                                                                                                  | name, identifier, message                                    | default chat resource  |
| **deaths**      | `killed`, `died`                                                                                                           | name, identifier, killer, killer\_identifier, weapon, coords | baseevents             |
| **damage**      | `hit`, `fatal hit`                                                                                                         | attacker, victim, weapon, damage                             | FiveM (off by default) |
| **explosions**  | `explosion`                                                                                                                | name, identifier, explosion\_type, coords                    | FiveM                  |
| **entities**    | `spawned`                                                                                                                  | name, identifier, entity\_type, model, coords                | FiveM                  |
| **vehicles**    | `entered`, `left`                                                                                                          | name, identifier, vehicle, plate, seat                       | baseevents             |
| **resources**   | `started`, `stopped`                                                                                                       | resource                                                     | FiveM                  |
| **admin**       | `kick`, `warn`, `ban`, `heal`, `direct message`, `announcement`, `restart warning`, `server shutdown`                      | admin, target, reason                                        | txAdmin                |
| **money**       | `add`, `remove`, `set`                                                                                                     | name, identifier, account, amount, reason                    | ESX, QBCore            |
| **jobs**        | `job changed`                                                                                                              | name, identifier, job, grade, previous\_job                  | ESX, QBCore            |
| **items**       | `added`, `removed`, `put in trunk`, `taken from glovebox`, `put in stash`, `given to player`, `bought`, `crafted`, `given` | name, identifier, item, count, details                       | ESX, ox\_inventory     |

## Trunks, gloveboxes and stashes

With ox\_inventory you see exactly where an item went:

| event                 | details                                      |
| --------------------- | -------------------------------------------- |
| `put in trunk`        | `player Lars de Vries -> trunk (ABC 123)`    |
| `taken from glovebox` | `glovebox (ABC 123) -> player Lars de Vries` |
| `put in stash`        | `player Lars de Vries -> stash police`       |
| `given to player`     | `player Lars de Vries -> player Kim Jansen`  |

Type `trunk` in the search box of the panel to see everything around trunks.

{% hint style="info" %}
Resources that start with the server are not logged under `resources`. Only starts and stops after the server has booted.
{% endhint %}


---

# 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://prisma-logs.gitbook.io/prisma-logs/docs/en/configuration/built-in-logs.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.