> 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/getting-started/first-start.md).

# First start

This is what happens when your server starts with Prisma Logs for the first time.

## 1. License check

After a few seconds the resource checks your license key and the IP of your server. If something is wrong, the server stops with:

```
[ERROR] Server shutting down, invalid license key or ip..
```

See [Troubleshooting](/prisma-logs/docs/en/help/troubleshooting.md#invalid-license-key-or-ip).

## 2. Creating categories

The built-in categories are created in your panel, for example `connections`, `chat`, `items` and `money`. If they already exist, they only get new fields added. Your own fields and webhooks always stay.

These categories do **not** count towards the limit of your plan.

## 3. Script scan

On the first start the resource scans all your scripts by itself. The actions it finds are sorted into themes in your panel, like **police & crime**, **job scripts** and **vehicle scripts**. See [Script scan](/prisma-logs/docs/en/configuration/script-scan.md).

Added scripts later? Press **Scan scripts** under **Categories** in the panel.

## 4. Sending logs

From now on the resource collects logs and sends them to the panel in one batch every 3 seconds. If the panel can't be reached for a moment, the resource keeps up to 2000 logs and sends them later.


---

# 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/getting-started/first-start.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.