it seems that in some use cases - and that seems to become more frequent (linked to widgets maybe ?) - where containers run for much longer than expected
I suspect that some long-haul traffic is happening, that makes the last_activity report unreliable; just a wild guess at this point
but typically there should be a means for operations to state we don't want any container older that 2 days
so in addition to the current settings, monitor should accept a third parameter that would describe in hours a maximal age no matter what else
it seems that in some use cases - and that seems to become more frequent (linked to widgets maybe ?) - where containers run for much longer than expected
I suspect that some long-haul traffic is happening, that makes the last_activity report unreliable; just a wild guess at this point
but typically there should be a means for operations to state we don't want any container older that 2 days
so in addition to the current settings, monitor should accept a third parameter that would describe in hours a maximal age no matter what else