Skip to main content
Every telemetry envelope in LogBrew must include a non-empty release and environment. A release is the code version that emitted telemetry, such as api@1.2.3, ios@2026.06.01, or a git SHA. Release tracking makes production questions precise:
  • What changed in this version?
  • Which issues first appeared after deploy?
  • Did action failures increase in production?
  • Which traces and logs belong to the same release?

​
Release summary

LogBrew keeps an append-friendly release summary with counts for each stream.

​
Naming releases

Use a release name that a human and an agent can map back to code.

Good

api@1.2.3, web@b7f4d91, ios@2026.06.01, worker@2026-06-01.1

Avoid

latest, prod, new, build, empty strings, or values that change meaning after deploy.

​
Environment filters

Use environment to separate production from staging or local development. Release names can repeat across environments.
Keep release and environment on every SDK envelope. It is cheaper than trying to reconstruct deploy context after an incident.