quaint-telephone-89068
03/06/2026, 3:19 PM--stats-log (to feed the values into Honeycomb via buildevents). At the moment the stats are always written to stderr, at the tail end of any other logging from Pants. It'd be convenient if we could configure the stats to be written to a dedicated file.
Describe the solution you'd like
A new command-line flag / env var that can set an on-disk path for the stats outputs.
Describe alternatives you've considered
I'll be experimenting with doing something like ./pants <goal> 2>&1 | tee pants-out.log and then processing pants-out.log to drop all the output before the stats counters.
pantsbuild/pantsquaint-telephone-89068
03/06/2026, 3:19 PM