@girish Like I said, it happened to me only once between updates so the system is pretty stable. I outlined a theoretical situation where it would be needed. Then another user mentioned an important use case for simply adding a single endpoint to reaction to a Not Responding status
But you yourself said Docker supports this, and multiple people have expressed that customizable actions based on "status changes" of apps are beneficial. I even outlined how to make @nebulon's and your main issue with this work even better while still increasing uptime. Increasing uptime for users was important enough for Docker to implement it themselves with their heathchecks. Even supervisor.
The notifications can literally say "We restarted your app
x, if you notice this happening often with this app - click this to send the log directly to the developers."
Only @mehdi appears opposed to this though I couldn't tell, I'd say it's almost unanimous and why wouldn't we compromise to make everyone happy app devs,
Cloudron developers (you and @nebulon), and especially users.
But the point you guys made (yourself and @nebulon) is valid, it's just overruled by using the notification system you already have in place to make this situation so much easier for the users to repot more to mitigate your concerns while simultaneously increasing user reporting and increasing app uptimes. Win-win - does anyone disagree with that?
Note: I agree with @girish that we should hear from more users and their opinions btw.