Concepts & Reference
Traces, Spans, And Logs
Understand request evidence: traces show the path of work, spans show timed operations, and logs add event context.
Concept
Understand request evidence: traces show the path of work, spans show timed operations, and logs add event context.
A trace is one request or unit of work across one or more services.
A span is one timed operation inside a trace, such as an inbound request, database call, external call, or application operation.
A log is a timestamped event that explains what the application reported around a request or service.
Examples
- Trace
- One checkout request can contain spans from the web service, API service, and payment call.
- Span
- A database query, outbound HTTP call, or controller action appears as a timed span inside the trace.
- Log
- A validation warning or retry message explains application context that span timing alone may not show.
How Vight uses it
Start with Traces when you need timing, status, route, and service path evidence. Open trace detail when you need to see which span dominated duration or failed. Use related logs when span timing does not explain why the request behaved that way. Use the Logs page when you need service-wide event history, not only one request. Keep service, environment, time range, version, and deployment filters aligned when comparing traces and logs.
Usage guidance
Use traces to prove where time or failure happened. Use logs to explain why the application made a decision. Compare several traces before treating one unusual request as the whole incident. Keep filters aligned when moving between trace detail and Logs.