Skip to content

Commit 4976ba8

Browse files
committed
add debug page to docs
1 parent 737f592 commit 4976ba8

1 file changed

Lines changed: 33 additions & 0 deletions

File tree

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
title: Debugging
3+
slug: en/docs/tutorials/debugging
4+
sidebar:
5+
order: 2
6+
---
7+
8+
When debugging, it’s important to distinguish between **client-side errors** (errors in the user’s browser) and **server-side errors** (errors from your backend services). Client-side issues appear in the browser console, while server-side issues are recorded by your running containers.
9+
10+
### Client Logs
11+
12+
To inspect client-side errors and warnings, open your browser’s developer tools and check the **Console** tab.
13+
14+
### Server Logs
15+
16+
Server logs are available through Docker. For example, you can view logs for a specific service with:
17+
18+
```bash
19+
docker compose logs api
20+
```
21+
22+
The API and Gateway logs are in JSON format, so you can filter and inspect them using jq. For example, to show only error-level logs from the last 24 hours:
23+
24+
```bash
25+
docker compose logs api --no-log-prefix --since 24h | jq 'select(.level == "ERROR")'
26+
```
27+
28+
### Reporting Issues
29+
30+
If you encounter **500 Internal Server Errors** or unclear failures, please open an issue on our GitHub repository and include:
31+
32+
- Relevant server logs (redacted if necessary)
33+
- Steps to reproduce the problem

0 commit comments

Comments
 (0)