Closed rijkvanzanten closed 6 years ago
I can create the logs to be one-liner and separated by day, which can make each file smaller, but the API shouldn't be looking at those files sizes and take actions based on it.
This should be separate job outside the API workflow.
Why not create a new Log file for each day? Then we can set in the app how many days to store and prune (delete) the older ones based on the Settings.
Thoughts @WellingGuzman @rijkvanzanten ?
The logger levels and names are flipped in the array.
@WellingGuzman – soooo... what do we have completed here? Log files per day and a directus_settings
option for how many days to keep before deleting?
I don't know what "levels" and "flips" means.
Doc doc doc doc doc documentation!
There's no configuration yet as we need to implement a cronjob manager for Directus. (Created a ticket for this https://github.com/directus/api/issues/200)
I don't know what "levels" and "flips" means.
It was a bug creating the files name. creating 400.<date>
instead of error.<date>
Doc doc doc doc doc documentation!
https://github.com/directus/api/wiki/Directus-CLI#log-module
Right now, there is no limit on the filesize of the logs. This can potentially result in huge huge file. We need to implement either a max filesize for the logs, or an "expiry date". (Either delete old records when filesize > threshold, or when logs.date < threshold)