Imported from previous forum
Some time ago I swear our log files had a naming convention with the date in the name of the file. Unfortunately I cannot find an example.
Within the past year we upgraded our version of QuickFIX (10.0.0 I believe) and now the log files do not use the date in the name of the file (e.g. FIX.4.2-4F5800N-CME.messages.current.log). This makes it more difficult to prune our log files as they grow.
I could not find a setting on the quickfixengine.org website on how to toggle the logging naming convention. Any thoughts on how we can change it back to use the date in the filename?
Some time ago I swear our log files had a naming convention with the
date in the name of the file. Unfortunately I cannot find an example.Within the past year we upgraded our version of QuickFIX (10.0.0 I
believe) and now the log files do not use the date in the name of the
file (e.g. FIX.4.2-4F5800N-CME.messages.current.log). This makes it more
difficult to prune our log files as they grow.I could not find a setting on the quickfixengine.org website on how to
toggle the logging naming convention. Any thoughts on how we can change
it back to use the date in the filename?
We hit exactly the same issue moving to quickfix from a vendor provided engine. We modified the source code (for example, if you use the C++ engine, look in FileLog.cpp) to include the date when creating the file. A few thoughts:
-
If you do modify the code to embed dates, make sure you take into account the GMT offset (if any).
-
You could consider having an external process that rolls logfiles for multiple applications at a specified point in the day.
-
I raised a product update request on the quickfix website. I should have done this a while back, thanks for reminding me

Dave