> ## Documentation Index
> Fetch the complete documentation index at: https://docs.logbrew.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> LogBrew is agent-first observability for developers: logs, traces, issues, actions, and releases through a native CLI and API.

LogBrew helps developers and AI coding agents understand production from the
terminal. Send first-party telemetry from your app, then read logs, traces,
issues, actions, and releases through the native `logbrew` CLI or API.

Telemetry means structured records about what your app did and what happened
around it: log messages, trace spans, grouped issues, product actions, releases,
and environments.

The goal is simple: authenticate once, keep coding, and let agents inspect
production context without opening a dashboard.

<CardGroup cols={2}>
  <Card title="Start with the CLI" icon="square-terminal" href="/quickstart">
    Log in, set up a project, and read your first telemetry in JSON.
  </Card>

  <Card title="Understand telemetry" icon="activity" href="/concepts/telemetry">
    Learn how logs, traces, issues, and actions connect.
  </Card>

  <Card title="Track releases" icon="tag" href="/concepts/releases">
    Tie every signal to a release and environment.
  </Card>

  <Card title="Use the API" icon="braces" href="/reference/telemetry-api">
    See the native JSON envelope and read endpoints.
  </Card>
</CardGroup>

## What LogBrew tracks

<CardGroup cols={2}>
  <Card title="Logs" icon="file-text">
    Structured log lines with severity, message, source, attributes, trace ID,
    release, and environment.
  </Card>

  <Card title="Traces" icon="route">
    Trace spans that let you follow one request across services.
  </Card>

  <Card title="Issues" icon="bug">
    Grouped errors and crashes with stable fingerprints, status, stack traces,
    occurrence counts, release, and environment.
  </Card>

  <Card title="Actions" icon="mouse-pointer-click">
    Product events such as `checkout_failed`, tied to actors, sessions,
    releases, and traces.
  </Card>
</CardGroup>

## Why agents like it

* Commands use popular words: `logs`, `issues`, `traces`, `actions`,
  `releases`, and `environments`.
* Every read command supports `--json` for stable machine-readable output.
* Release and environment filters work across telemetry streams.
* Issues can be read, explained, resolved, ignored, or reopened from the CLI.
* The mobile app stays useful for live awareness, while the CLI remains the
  fastest path for agents.

<Tip>
  Start with `logbrew examples`, then check status with `logbrew --json status`.
  For telemetry, read releases first with `logbrew read releases --json`, then
  narrow into one release with `logbrew read issues --release api@1.2.3 --json`.
</Tip>