bmr-cymru
commented
3 years ago There's some subtlety here as there are cases where the merged output is more useful as well as the reverse. Especially for commands that produce structured output (JSON, XML etc.) I think there is value in allowing plugin authors to optionally redirect the error stream. On the other hand there are commands where it's useful to have stderr and stdout merged because it allows the errors to be correlated with some previous logged output.
pmoravec
Backstory: I was parsing the output
ceph reportin Python. The command produces a json output but also prints a line to stderr. Since both stdout & stderr are redirected to the same file, it couldn't be loaded as a json directly (had to remove the last line to make it a valid json).I wonder whether stderr of the commands need to be handled in a different way. For example, redirect to
<cmd_options>.stderrand the stdout would go to<cmd_options>.stdoutor similar. A number of commands, Ceph in particular, produce json output. So doing any post-processing would be difficult when mixing stdout and stderr. I'd imagine more commands producing a formatted output going forward than a plain text, especially for printing out configs, perf counters, etc.Just wanted to start a discussion and check whether this could be addressed in some way.