It would be very helpful when troubleshooting "empty reports" if support could see what path fixes are being applied (before -> after)
I understand this could be a lot of log noise for many files, if we can log the first 1-5, or even a random sample of the files for each report that would be helpful.
Eli in 2020: This is a fr-will-do. Moving the log seems straightforward and the log bloat doesn’t seem incredibly impactful. Given that it will open up more troubleshooting opportunities for support and is straightforward, I think we should do this on the next sprint.
CODE-103
It would be very helpful when troubleshooting "empty reports" if support could see what path fixes are being applied (before -> after)
I understand this could be a lot of log noise for many files, if we can log the first 1-5, or even a random sample of the files for each report that would be helpful.
Eli in 2020: This is a fr-will-do. Moving the log seems straightforward and the log bloat doesn’t seem incredibly impactful. Given that it will open up more troubleshooting opportunities for support and is straightforward, I think we should do this on the next sprint.