-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
False
-
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
With opentracing, APICast generates multiple spans with the shared traceID:
- Span 1: Operation name: "apicast"
- Span 1.1: Operation name: /
- Span 1.2: Operation name: "@upstream"
- Span 1.3: Operation name: "@out_of_band_authrep_action"
See image as example
Whereas opentelemetry, APICast only generates 1 span
- Span 1: Operation name: "apicast"
See image as example
The main purpose is provide details about time taken to perform upstream and backend actions