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
If we drop events, especially exit events, that process will never be pruned from the cache.
To fix this we need to add a failsafe that triggers when we miss events but is also bound by time, say you lost X events, so somewhere in the next seconds/minutes we manually check if every process is still alive, probably by scraping proc.
Not labeling this as a bug as losing events is very very very hard.
The text was updated successfully, but these errors were encountered:
If we drop events, especially exit events, that process will never be pruned from the cache.
To fix this we need to add a failsafe that triggers when we miss events but is also bound by time, say you lost X events, so somewhere in the next seconds/minutes we manually check if every process is still alive, probably by scraping proc.
Not labeling this as a bug as losing events is very very very hard.
The text was updated successfully, but these errors were encountered: