What exactly are traces? Watch this brief video and learn that:

• Tracing data shows the detailed, chronological flow of a specific request as it travels and communicates between different components of an application or system. This is in contrast to logs which reflect discrete events generated by different components or services within a system.
• Normal tracing, also known as single-threaded or local tracing, focuses on monitoring the execution of a single thread or process within an application or system. Distributed tracing, on the other hand, is designed to track and monitor the flow of operations across multiple interconnected services or components within a distributed system. 
• Traces are typically made up of multiple spans. Each span represents a specific operation or “conversation” within a trace that occurs as part of a request’s journey though an application or distributed system. 
• Traces provide visibility into the duration and latency for each span as well as HTTP statuses where relevant. This empowers you to understand how your system is performing and identify interdependencies and drill into bottlenecks when they occur. 
• Traces also enable you to understand which systems depend on each other, providing for single communication and leaving you with a centralized picture of everything.
• With Coralogix you can correlate your traces with logs and metrics for a fuller view and finally, Coralogix provides its own open-source friendly tracing solution.