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
{{ message }}
This repository has been archived by the owner on Dec 11, 2020. It is now read-only.
This might not be enough: a bunch of big traces can consume all the available memory and make the monitor fail - this has caused us trouble with 1 user already. We should be erasing by memory consumption instead of by number. And we could probably remove really old traces (i.e. 1 week old).
The text was updated successfully, but these errors were encountered:
Deleting them by time still does not solve the issue. Only way how to do this properly is to count the memory usage. We already have internal ticket about this.
Currently we delete traces based on the number of traces alone.
This might not be enough: a bunch of big traces can consume all the available memory and make the monitor fail - this has caused us trouble with 1 user already. We should be erasing by memory consumption instead of by number. And we could probably remove really old traces (i.e. 1 week old).
The text was updated successfully, but these errors were encountered: