---
title: "Log management that links every log line to its trace and error"
description: "LogBrew is a log management tool for developers, with 50 GB of logs a month and 30-day retention free, no card needed."
canonical: "https://logbrew.co/en/logs"
last_updated: "2026-11-11"
---

# Log management that links every log line to its trace and error
LogBrew is a log management tool for developers, with 50 GB of logs a month and 30-day retention free, no card needed.

Send logs from the logger you already use. Search them by level, text, trace, service, release, environment, time, and field. Open the error or the trace behind any line.

## 1 log store, 4 ways to read it
Your logs in LogBrew: Every line keeps its level, message, fields, service, release, environment, and trace id.

- Web dashboard: `logbrew.co`. Filter, open a line with its trace, and watch live.
- CLI: `logbrew read logs --severity error --since 1h --json`. The same filters from your terminal or a script.
- API: `GET /api/logs`. Cursor pagination and up to 4 typed field filters.
- MCP server: `https://logbrew.co/mcp`. Your coding agent reads the logs of the projects you approve.

Each tap reads the same logs with the same filters. The mugs fill when your first line arrives. The web and the iOS app also show lines live as they arrive.

## Send logs from the logger you already use
No new logger. Add the LogBrew SDK next to the one you have, and each line arrives with its level, message, and fields.

- Node.js: `console`, Pino, and Winston.
- Python: The `logging` module, with `extra={}` fields.
- Java and Kotlin: SLF4J, Logback, and JUL. Android logcat lines through the Kotlin SDK.
- .NET: `ILogger` and ASP.NET Core.
- PHP: PSR-3 and Monolog, with Symfony and Laravel.
- Rust: `tracing`, with Axum, Actix, and Rocket.
- OpenTelemetry: OTLP logs from any OpenTelemetry SDK or Collector, with no LogBrew SDK.
- Supabase: A log drain sends the platform logs.

## Search logs by what you already know
Every filter works on the web, in the CLI, and in the API, so log analysis starts from the same query everywhere. A text search matches a substring of the message. A field filter compares a typed value, so a number takes `gte` and a text value takes `contains`.

- Level: `info`, `warning`, `error`, or `critical`.
- Text: A substring of the message.
- Trace id: Every log sent inside a trace carries its trace and span ids.
- Service, release, and environment: The service name, the release, and the environment, such as `production`.
- Time: `since` and `until`, with cursor pagination for long ranges.
- Fields: Up to 4 typed filters per query. Text takes `eq`, `ne`, `contains`, and `starts_with`. Numbers take `gt`, `gte`, `lt`, and `lte`.

```bash
curl -sS -G "https://api.logbrew.co/api/logs" \
  -H "Authorization: Bearer $LOGBREW_TOKEN" \
  --data-urlencode "project_id=$LOGBREW_PROJECT" \
  --data-urlencode "since=2026-11-10T05:31:33Z" \
  --data-urlencode 'attribute_filters=[{"path":"/metadata/order_id","type":"string","operator":"eq","value":"ord_42"}]' \
  | jq -c '.logs[] | {message, order_id: .attributes.metadata.order_id}'
```

```text
{"message":"order paid","order_id":"ord_42"}
```

## From 1 log line to its cause
- Log investigation: Open 1 log with its trace and the logs around it.
- Live tail: Watch logs arrive in real time on the web and in the iOS app.
- Log rules: Change a log's severity or hide it, without deleting data.
- Export: Save a log as JSON, CSV, TXT, Markdown, or XLSX.
- Agents: The hosted MCP server and the CLI give a coding agent the same logs with the same filters.

## What each plan includes for logs
Every plan has every feature. Plans differ by volume and retention. A meter warns at 80% and at 100% pauses only logs until the monthly reset, with no overage charge.

| Plan | Price | Logs a month | Retention |
| --- | --- | --- | --- |
| Free | $0 per month | 50 GB | 30 days |
| Pro | $25 per month | 500 GB | 90 days |
| Business | $80 per month | 2 TB | 1 year |
| Enterprise | Custom by email quote | By quote | By quote |

Product actions count toward the log allowance. Logs past the retention window are deleted within 1 to 8 days.

## Questions people ask

### What is log management?

Collecting the log lines your applications write, keeping them for a set time, and searching them by level, text, time, and field. LogBrew adds the link from a line to the trace and the error it came from.

### What is logging, and how does it work?

Your code writes 1 line per event with a level, a time, and a message, through a logger such as Pino, Python `logging`, or SLF4J. A handler or appender sends each line to LogBrew, where it is stored and indexed.

### What is a log line?

One record from a logger, with a timestamp, a level, a message, and the fields you attach, such as `order_id`. In LogBrew it also carries the service, the release, the environment, and the trace id when it was sent inside a trace.

### What is log aggregation, or centralized logging?

Sending the logs of every service and host to 1 place, so 1 search covers all of them. Each line keeps its service name, so you can narrow the search to 1 service again.

### How long does LogBrew keep logs?

30 days on Free, 90 days on Pro, 1 year on Business, and as agreed on Enterprise. Logs past the window are deleted within 1 to 8 days.

### What happens at 50 GB on the Free plan?

LogBrew warns at 80%. At 100%, only logs pause until the monthly reset. Errors, traces, and metrics keep flowing, and there are no overage charges.

## Public links
- Logs: https://logbrew.co/en/logs
- Pricing: https://logbrew.co/en/pricing
- Docs Markdown: https://logbrew.co/en/docs.md
- OpenAPI: https://logbrew.co/openapi.json
- llms.txt: https://logbrew.co/llms.txt