-
Task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Product / Portfolio Work
-
1
-
False
-
-
False
-
-
-
Tracing Sprint # 270, Tracing Sprint # 271, Tracing Sprint # 272 - Release, Tracing Sprint # 273, Tracing Sprint # 274, Tracing Sprint # 275, Tracing Sprint # 276, Tracing Sprint # 277 - 3.7, Tracing Sprint # 278
Provide some sizing recommendations for Tempo Monolithic instances. We can provide some information like:
- Number of traces per second
- Number of spans in those traces
- Some default values for resource limits
This comes from TRACING-4455, where some customers tried to use Tempo Monolithic with a big amount of traces and the Tempo container is OOMKilled.
- is triggered by
-
TRACING-4455 Tempo Monolithic throws html error
-
- Closed
-