[streetcat1]

Thanks for the info, so can you please elaborate more on how are you access the prediction logs? Is there a specific log format? How do you know the model input schema?

[elenasamuylova]

Right now we ask the user to prepare the logs on their side (or schedule a job to push the logs to the tool). We learnt that most teams store the prediction logs anyways - since they are usually used for retraining. So we thought that is the simplest and most universal interface for integration for now.

The tool now works with tabular data. Depending on the report type you can include only the input features (e.g. for data drift report), or also add the prediction and target column to the table (e.g. for model performance report). So you might need to perform some basic transformations (e.g. to add the target column if this data comes later) to prepare the input.

To specify the schema, you need to configure a simple column mapping (basically show where the target or prediction columns are, and optionally specify which features are categorical and numerical).

You can check the requirements for each report in the documentation https://docs.evidentlyai.com/

[emelidral]

To add to this, if the column_mapping is not provided we try to parse data automatically assuming that the schema is standard (e.g. you use the column names like "target" and "prediction") We also process the features based on pandas data type. In future to want to make it super easy to avoid writing extra configuration so we will try to parse as much as possible, but of course give the user the opportunity to override.