Skip to main content
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.

Start with the CLI

Log in, set up a project, and read your first telemetry in JSON.

Understand telemetry

Learn how logs, traces, issues, and actions connect.

Track releases

Tie every signal to a release and environment.

Use the API

See the native JSON envelope and read endpoints.

​
What LogBrew tracks

Logs

Structured log lines with severity, message, source, attributes, trace ID, release, and environment.

Traces

Trace spans that let you follow one request across services.

Issues

Grouped errors and crashes with stable fingerprints, status, stack traces, occurrence counts, release, and environment.

Actions

Product events such as checkout_failed, tied to actors, sessions, releases, and traces.

​
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.
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.