LocalAI version:
4.1.1
Environment, CPU architecture, OS, and Version:
Not relevant
Describe the bug
Traces are lost when restarting the service (i.e. systemctl restart local-ai). This suggests that traces are not persisted. This could be a design decision, however from my point of view they should be made persistent - or at least give the administrator the choice and a cleanup method. As there is a db in the app since version 4.0.0, it makes sense to store them there?
To Reproduce
Restart local-ai.
Expected behavior
Traces are not lost when restarting local-ai
Logs
Additional context
LocalAI version:
4.1.1
Environment, CPU architecture, OS, and Version:
Not relevant
Describe the bug
Traces are lost when restarting the service (i.e.
systemctl restart local-ai). This suggests that traces are not persisted. This could be a design decision, however from my point of view they should be made persistent - or at least give the administrator the choice and a cleanup method. As there is a db in the app since version 4.0.0, it makes sense to store them there?To Reproduce
Restart local-ai.
Expected behavior
Traces are not lost when restarting local-ai
Logs
Additional context