Tracing Fields
editTracing Fields
editDistributed tracing makes it possible to analyze performance throughout a microservice architecture all in one view. This is accomplished by tracing all of the requests - from the initial web request in the front-end service - to queries made through multiple back-end services.
Unlike most field sets in ECS, the tracing fields are not nested under the field set name. In other words, the correct field name is trace.id
, not tracing.trace.id
, and so on.
Tracing Field Details
editField | Description | Level |
---|---|---|
Unique identifier of the span within the scope of its trace. A span represents an operation within a transaction, such as a request to another service, or a database query. type: keyword example: |
extended |
|
Unique identifier of the trace. A trace groups multiple events like transactions that belong together. For example, a user request handled by multiple inter-connected services. type: keyword example: |
extended |
|
Unique identifier of the transaction within the scope of its trace. A transaction is the highest level of work measured within a service, such as a request to a server. type: keyword example: |
extended |