Make AI Logs Entity Bundleble and Fieldable

Created on 9 October 2024, about 2 months ago

Problem/Motivation

The current logs entity was very much developed for chat, embeddings and other textual AI calls, making it unusable or having flawed logic in other cases. The current solution was to put everything that was none-textual or parameter data in an extra data blob, but that will not work in the long run.

Outside of that logging file input and output can become pretty complex, pretty fast. Having specific solutions for garbage collection and how to store this, would make it easier to handle.

Steps to reproduce

Proposed resolution

* Move the (or create a new) entity to a bundle.
* Move the (or create a new) entity to be fieldable, but keep certain base fields that every log needs.
* Create a bundle for each operation type.
* Make a boolean where the bundle can decide if it is filled in on the eventsubscriber. The other option is that its a manual process from a third party app.
* Create a base logic on how to fill in the logs when the bundle has this enabled.
* Make this inheritable per bundle, so they can set how they log this themselves for special cases.

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Active

Version

1.0

Component

Other Submodules

Created by

🇩🇪Germany marcus_johansson

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024