size_s, size_m, size_l, and size_xl) map collector resources and scaling headroom to telemetry volume. Use this page to assist you in picking a preset.
Total span throughput
Span throughput is the metric we use for benchmarking and estimating the resources needed to operate Odigos. To calculate the total span throughput (bytes/second), you can either:- Estimate your monthly span volume in bytes, which can often be inferred from your existing observability tools. If you only know the number of spans, multiply it by the average span size in bytes to estimate the total volume. Then convert the monthly volume to bytes per second.
- View the span throughput in the Odigos UI under “collectors pipeline”.
Collector pipeline UI requires enabling the Odigos Own Metrics feature.
- Number of instrumented pods - each instrumented pod consumes a small amount of additional static resources in the node collector.
- Pipeline features - actions and destinations consume additional collector CPU and memory resources.
Cluster preset vs. total span throughput
Maximal single collector capacity
Cluster gateway (1 pod) (see maximum capacity here)
The cluster gateway is a Deployment that receives telemetry from node collectors, processes it, and exports it to your destinations.Node collector
The node collector is a DaemonSet (one pod per node) that receives telemetry from apps on that node and forwards it to the cluster gateway.Maximum scaled cluster gateway capacity
* Calculated with a span size of 1.9KB
Troubleshooting
If you experience any of the following symptoms consistently:- Memory limit hits or OOMKills
- CPU throttling under steady load
- Gateway HPA scaling to max replicas frequently
- Export backlogs or dropped spans
collectorGateway / collectorNode values on the Configuration page.