Is your feature request related to a problem? Please describe.
The server-side function when they run there's an automatic history log attach to each run. It would be nice to keep only the last 15 days or something to prevent growing this history log too large per function.
When inspecting the function run via backend function info fn-name it can get verbose quickly, especially for function that run on a daily or worst hourly schedule.
Describe the solution you'd like
I think we could have an automatic cleanup each time we're creating a history entry, we could have a go routine cleaning up old entries, say older than 15 days in there etc. Maybe this could be 15 days by default and controllable via an env variable in the config. Like the number of days to retain logs, in fact even 7 days could be the default.
Describe alternatives you've considered
There's not much alternative, since the system tables are not accessible outside of the core, they cannot be cleanse from the CLI for instance, since it's a system table.
Additional context
Is your feature request related to a problem? Please describe.
The server-side function when they run there's an automatic history log attach to each run. It would be nice to keep only the last 15 days or something to prevent growing this history log too large per function.
When inspecting the function run via
backend function info fn-nameit can get verbose quickly, especially for function that run on a daily or worst hourly schedule.Describe the solution you'd like
I think we could have an automatic cleanup each time we're creating a history entry, we could have a go routine cleaning up old entries, say older than 15 days in there etc. Maybe this could be 15 days by default and controllable via an env variable in the config. Like the number of days to retain logs, in fact even 7 days could be the default.
Describe alternatives you've considered
There's not much alternative, since the system tables are not accessible outside of the
core, they cannot be cleanse from the CLI for instance, since it's a system table.Additional context