The Span represents an operation on the initiating side of a request/response interaction.
The Span represents an operation on the initiating side of a request/response interaction. For example, instrumentation on a HTTP client library will most likely generate a Span with kind=client that represents the outgoing HTTP requests that it sends to other parties.
The Span represents an operation that consumes messages from a message broker.
The Span represents an internal operation that doesn't imply communication communication with any external services.
The Span represents an internal operation that doesn't imply communication communication with any external services. For example, if there is an interesting block of code that affects the processing of a bigger operation, it might be useful to create an internal Span that represents it so that the time spent on it will be shown on traces and related metrics.
The Span represents an operation the produces a message placed on a message broker.
The Span represents an operation on the receiving side of a request/response interaction.
The Span represents an operation on the receiving side of a request/response interaction. For example, instrumentation on a HTTP server will most likely create a Span with kind=server that represents the operations it processes.
The Span represents an unknown operation kind.