Source code compiled into executable software artifacts, tracked by build number.
A build refers to source code that has been compiled or packaged into software artifacts that can be executed on a computer. Because a project produces many builds over time, each build is identified by a unique build number for traceability.
In the context of observability, builds are significant change events: a new deployment often triggers latency regressions, error rate spikes, or memory leaks. Correlating telemetry data (traces, metrics, logs) with build numbers or deployment markers allows engineers to quickly attribute performance changes to specific code changes. obseria.io supports deployment markers that overlay build events on metrics dashboards, making it easy to answer 'did this metric degrade after the last deploy?'
See Build in action
obseria.io gives you full-stack observability — logs, metrics, traces, and AI-powered root cause analysis.