I have several (50) docker containers running, and most are not needed 24x7. Those services are used only 1-2hours atmost each day. So keeping them active 24x7 isn't efficient at all.
I have used this wonderful project sablier to automatically start docker containers when their is traffic for it, and the container gets automatically stopped if no traffic flows for about 2-3 hours.
There is no way for uptime kuma to know whether the docker container is being managed by the sablier. and so it assumes it to be DOWN.
✔️ Solution
In this use case the uptime kuma should integrate this sablier project which can tell if the container is stopped by the it. and then uptime-kuma can mark it as DORMANT instead of marking it as DOWN.
📑 I have found these related issues/pull requests
https://github.com/sablierapp/sablier
🏷️ Feature Request Type
API / automation options, Other
🔖 Feature description
I have several (50) docker containers running, and most are not needed 24x7. Those services are used only 1-2hours atmost each day. So keeping them active 24x7 isn't efficient at all.
I have used this wonderful project sablier to automatically start docker containers when their is traffic for it, and the container gets automatically stopped if no traffic flows for about 2-3 hours.
There is no way for uptime kuma to know whether the docker container is being managed by the sablier. and so it assumes it to be DOWN.
✔️ Solution
In this use case the uptime kuma should integrate this sablier project which can tell if the container is stopped by the it. and then uptime-kuma can mark it as DORMANT instead of marking it as DOWN.
❓ Alternatives
No response
📝 Additional Context
No response