# APIs: requests, logs, errors and performance

> Find your way around the APIs pages: every request, your warning and error logs, grouped errors, slow endpoints and the map of your services.

Section: Each part of Relia · Page: https://tryrelia.com/docs/apis · Last checked against the product: 2026-11-01
Video walkthrough: https://youtu.be/W_SUfdKLns0

The **APIs** part of Relia shows what your server does: what came in, what broke, what's slow, and how your services connect. It fills in once a server SDK sends traces (Node.js, Next.js, Python, PHP / Laravel, or any language through OpenTelemetry).

Open **APIs** in the sidebar. Its pages are **Requests**, **Logs**, **Performance**, **Errors** and **Anomalies**. **Map** is its own item higher in the sidebar.

## Requests

**Requests** opens the **Logs & Requests** page. Every row is one request to your server: when, which endpoint, the status, how long it took and which service answered. Search (for example `products`) to see only matching requests, filter by service, status or time, and open a row to see the request's trace.

The page has three tabs:

- **HTTP / API Requests**: the request list.
- **Process Logs**: the same requests as a log, with service, time, severity and trace id.
- **Endpoint Analytics**: one row per endpoint with calls, average time and error rate. Open an endpoint for its calls, latency (p95, p99) and errors over time.

Quick ranges go up to 7 days.

## Logs

**Logs** shows the warning and error lines your services send, grouped into patterns: one row per kind of message, with how many lines, a trend, when it was last seen and a link to a request that logged it. Switch to **Lines** to read them one by one, newest first.

Info and debug lines are not stored. The SDKs send warnings and errors by default; set `RELIA_LOGS=0` to stop sending logs.

## Errors

**Errors** opens the **Issues** page. Each kind of error becomes one row, however often it happens, with when it was last seen and how many times. Open one for its events and the stack trace, pointing at the line in your code.

Not every row is a fire. For example, about 3 in every 100 product requests asking for a product that doesn't exist (404) is worth a look, not an emergency. Relia's own incidents tell you which problems need you.

> **Tip:** watch [Fix pages and APIs returning 404 not found in production](https://youtu.be/ed4I6yqAPXc) (2 min).

## Performance

**Performance** ranks your slowest endpoints and shows latency over time. Open a request and the waterfall shows where the time goes: each step (your code, a database query, a call to another service) as a bar. Often one slow query explains a slow endpoint.

> **Tip:** watch [Why is my API slow? Find the slow database query behind it](https://youtu.be/W8ONSladzPk) (2 min).

## Anomalies

**Anomalies** lists slow calls, error bursts and traffic spikes. Most of these also show up as incidents on Home.

## Map

**Map** shows how everything connects, in columns: users, your services, what they depend on (databases, queues, outside APIs, AI agents) and the servers they run on. Lines are coloured by health, and cards show open incidents. Click a card to see only its connections, its incidents and example failed requests.

## What Relia does with this

You don't have to watch these pages. Relia reads the same data every few minutes and raises an incident when an endpoint fails or slows down more than usual for it. Look here when you want the detail behind an incident, or when your server acts up.

## Next

- [Database](https://tryrelia.com/docs/database.md)
- [Read an incident](https://tryrelia.com/docs/incidents.md)
- [Why is my API slow?](https://tryrelia.com/docs/slow-api.md)
- [Did my deploy break anything?](https://tryrelia.com/docs/did-my-deploy-break.md)

---
All Relia docs for AI assistants: https://tryrelia.com/llms.txt (index) · https://tryrelia.com/llms-full.txt (everything in one file)
