settings for background_task_completedtask table

[q121212]

my app used this background_task sheduller for repeated tasks, and repeat interval is very short (a few secodns). Over a long period the table (background_task_completedtask table) will become very large and since there are many indexes there, it will be problematic to delete these logs. I want to advance in a more optimal way to solve this problem.

I think - good idea - add configuration for completed tasks logging, for example - logging only failed tasks..

As another solution - truncate table sometimes, but interesting events\tasks also would be lost(

[philippeowagner]

I suggest to implement a clean up routine that is called by a repetitive background task as well. Remove the unused entries and keep the interesting events.

[philippeowagner]

"I think - good idea - add configuration for completed tasks logging, for example - logging only failed tasks."

We should accept such a PR.

[michaelwiles]

Where would that kind of config go? ideally I think I'd want to put it on the @background decorator...