Skip to content

Use a better OTel attribute structure for evals case data #2708

@dmontagu

Description

@dmontagu

Description

Right now we store all of the evals cases data in a single attribute on the root span related to the evaluation run, we probably want to drop those and make use of the attributes on the per-case spans for this, because the attribute will be truncated if there are too many cases.

References

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions