Collector panics on startup for non-nilable config options with unset environment variable #10949
Labels
area:confmap
bug
Something isn't working
release:blocker
The issue must be resolved before cutting the next release
Milestone
Describe the bug
When the collector is started with a configuration that has a non-nilable config option (e.g.
int
oruint64
) set to an environment variable that hasn't been set, the collector panics without any information other than the stack.Steps to reproduce
Config:
Start the collector with an
int
configuration option, in this case the debug exporter'ssampling_initial
option, set to the environment variableUNSET_VARIABLE
, which isn't set.What did you expect to see?
No panic. I'm not sure if intended behavior here is to error and force the user to set the value of the variable, or to start with a default value, such as
0
for number types.What did you see instead?
What version did you use?
v0.107.0
andv0.106.1
Environment
This has been hit on barebones
macos/amd64
and in k8s as well.The text was updated successfully, but these errors were encountered: