#7428 added the capability to store supervisor errors and expose them via the supervisor status endpoint. The original PR sets the config druid.supervisor.stream.storingStackTraces to false, which means that only the error's message is stored instead of the full stack trace. I think setting the default storingStackTraces config to true would improve the Druid out-of-the-box experience by allowing quickstart users to debug supervisor issues more easily without having to pore through logs or figure out how to change configs.
Does anyone see any issues with this? Also, would making this change affect anything on the web console side?
#7428 added the capability to store supervisor errors and expose them via the supervisor status endpoint. The original PR sets the config
druid.supervisor.stream.storingStackTracestofalse, which means that only the error's message is stored instead of the full stack trace. I think setting the defaultstoringStackTracesconfig totruewould improve the Druid out-of-the-box experience by allowing quickstart users to debug supervisor issues more easily without having to pore through logs or figure out how to change configs.Does anyone see any issues with this? Also, would making this change affect anything on the web console side?