feat: set default value for SpanLimit to 32k (#1768)

VinozzZ · web-flow · commit 088125fe5e7d · 2025-12-17T14:17:21.000-05:00
## Which problem is this PR solving?

Currently, Refinery has no default hard limit on the number of spans it
will buffer per trace. This means that giant traces can overload a
single Refinery node.

## Short description of the changes

- set 32k as the default value
diff --git a/config/file_config.go b/config/file_config.go
@@ -200,7 +200,7 @@ type TracesConfig struct {
 	TraceTimeout     Duration `yaml:"TraceTimeout" default:"60s"`
 	MaxBatchSize     uint     `yaml:"MaxBatchSize" default:"500"`
 	SendTicker       Duration `yaml:"SendTicker" default:"100ms"`
-	SpanLimit        uint     `yaml:"SpanLimit"`
+	SpanLimit        uint     `yaml:"SpanLimit" default:"32000"` // Set the default span limit to be the same as the limit for trace view in Honeycomb
 	MaxExpiredTraces uint     `yaml:"MaxExpiredTraces" default:"3000"`
 }
 
diff --git a/config/metadata/configMeta.yaml b/config/metadata/configMeta.yaml
@@ -397,7 +397,7 @@ groups:
         type: int
         valuetype: nondefault
         firstversion: v2.8
-        default: 0
+        default: 32000
         reload: true
         summary: is the number of spans after which a trace becomes eligible for a trace decision.
         description: >

Original file line number	Diff line number	Diff line change
`@@ -200,7 +200,7 @@ type TracesConfig struct {`
`200`	`200`	TraceTimeout Duration `yaml:"TraceTimeout" default:"60s"`
`201`	`201`	MaxBatchSize uint `yaml:"MaxBatchSize" default:"500"`
`202`	`202`	SendTicker Duration `yaml:"SendTicker" default:"100ms"`
`203`		- SpanLimit uint `yaml:"SpanLimit"`
	`203`	+ SpanLimit uint `yaml:"SpanLimit" default:"32000"` // Set the default span limit to be the same as the limit for trace view in Honeycomb
`204`	`204`	MaxExpiredTraces uint `yaml:"MaxExpiredTraces" default:"3000"`
`205`	`205`	`}`
`206`	`206`