Skip to content

Cache alert evaluation state #459

@cwbriones

Description

@cwbriones

Right now we go to the database for every enumeration of alerts. We should instead have some sort of repository wrapper that caches these evaluations as they are written to avoid so many individual reads.

Similarly, we could fetch the evaluation state in a batch instead of per-alert - although this could also be done separately from the caching.

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