sqlite database growing large

[justafish]

The onepassword_connect_data docker volume has an ACTIVITY_EVENTS table in the sqlite database that never gets pruned - in our case it has grown to 14GB in the space of 3 weeks (and has previously filled up a disk where the volume had to be destroyed and re-made).

How should this be handled? I see there's a OP_LOG_LEVEL environment variable but it's not really documented what this does and what values it can be set to

[Marton6]

Thank you for reporting this issue. We will look into reproducing and fixing it.

OP_LOG_LEVEL only configures the amount of messages that get logged to stdout, so changing that would not have any impact on the number of activity events logged by Connect.