-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
-
Kiali+Tempo performance
-
False
-
None
-
False
-
Not Selected
-
To Do
-
100% To Do, 0% In Progress, 0% Done
It's been reported that Tempo query is slower than Jaeger when tested by Kiali team:
- https://github.com/kiali/kiali/issues/6844#issuecomment-1833599117
- https://issues.redhat.com/browse/OSSM-5995
This has already shown that the Kiali interface is slower when having Tempo as a backend.
This has 2 main implications:
- Users migrating from Jaeger to Tempo will experience a quality of service drop
- As the tests provided in the previous links come from limited setups not really demanding, this symptom may get even worse at scale.
This epic is created to ensure that both implictaions described are not an issue and Tempo+Kiali interoperability is better (or at least at the same level) than Jaeger+Kiali.
- is related to
-
TRACING-4038 [QE] Test performance and scalability of Distributed Tracing operators.
- Closed