What every boundary records
The logs, traces and metrics on RPCs, component calls, the database, outbound HTTP and the browser, and how browser and API traces join.
Where the telemetry goes
The local ClickStack,
.forge/logs/<env>/, the browser console mirror, the hosted store, retention and opting out.Querying with forge obs
obs check and its exit codes, status, issue, trace and db query, the same locally and hosted.Hosted dashboards, alerts and issues
Generated dashboards, the default alert rules, how errors are grouped, source maps and session replay.
Health probes and graceful shutdown
/healthz and /readyz, what a booting process reports, and how a rollout drains a replica.Why this helps an agent
Browser errors on disk, exit codes to branch on, recon commands, shipped skills, MCP and parallel agents.
The shape of it
The app exports standard OpenTelemetry to whatever endpoint its environment provides, so the same build runs against the local ClickStack in development and your organization’s store on hosting. Read the diagram from the left: two producers, one store, and three ways to read it. Locally the third arm, plain files you cangrep, is the one agents reach for first.
Related topics
Environments & deploys covers the releases thatforge obs check judges. Troubleshooting covers what to check when a command fails. Hosting on Reliant covers what hosting runs and bills. Session timelines shows what a user did before a frontend error, and Profiling covers CPU and heap profiles. Release gates explains how forge obs check gates a promotion.