It all depends on what a neater solution means. I would try to understand the functional complaint before seeking technical alternatives.

In this case, the issue is likely to be the lack of modularity of your solution, in the sense that you should be writing a logging subroutine that meets your manager's needs. Try to complete the list of requirements first, such as whether it needs a logfile naming convention (also creating required separation) to include timestamping, process identity, stage identity, file identity or whatever is functionally required. Design your own logging subroutine accordingly and get your manager to agree to it before coding it - you might find there are also site-specific requirements for how the logging routine is installed in a (site-specific) module as well as other project standards that need to be maintained.