Given the maturity of the project, a lot of the issues cri-o hits in production are obscure deadlocks. It could be useful to have an internal goroutine monitor to raise an alert if the number of active goroutines get high (500 or so maybe? not clear what high is).