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
Assume a scenario where the docker containers are running behind something like containernursery / sablier, which will start / stop containers based on whether there is traffic or not, primarily useful in self-hosted situations where not all containers need to be running all the time.
What is the best practice for monitoring the up / down (start / stop) status of each container ?
Currently I am thinking about setting up a tcp based check for each container based on the export port. But wondering if there is a better suggestion for monitoring the up/down status for containers without having to write a config file with each container listed with the corresponding ports.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Assume a scenario where the docker containers are running behind something like containernursery / sablier, which will start / stop containers based on whether there is traffic or not, primarily useful in self-hosted situations where not all containers need to be running all the time.
What is the best practice for monitoring the up / down (start / stop) status of each container ?
Currently I am thinking about setting up a tcp based check for each container based on the export port. But wondering if there is a better suggestion for monitoring the up/down status for containers without having to write a config file with each container listed with the corresponding ports.
Beta Was this translation helpful? Give feedback.
All reactions