You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The database for Studio can fill up and grow to so size — my database was 420mb.
In some cases I don’t need to keep all that historical data and while there is an option in the Spans UI to truncate the database, it’s not readily apparent when to do so.
Therefore the info page could provide some metrics on table row sizes and such to suggest when to truncate - and to allow truncation.
On Studio start as well , some status could be logged and a recommendation to truncate could help.
The text was updated successfully, but these errors were encountered:
The database for Studio can fill up and grow to so size — my database was 420mb.
In some cases I don’t need to keep all that historical data and while there is an option in the Spans UI to truncate the database, it’s not readily apparent when to do so.
Therefore the info page could provide some metrics on table row sizes and such to suggest when to truncate - and to allow truncation.
On Studio start as well , some status could be logged and a recommendation to truncate could help.
The text was updated successfully, but these errors were encountered: