[go-nuts] Re: Best way to launch/monitor several go process in production

2017-09-04 Thread Miki Tebeka
I've used http://supervisord.org/ in the past, very easy to set up and you can get notified when a process exits. On Monday, September 4, 2017 at 12:35:30 AM UTC+3, emarti...@gmail.com wrote: > > Hello, > > I am looking for the 'best' way to launch and monitor several go > processes. Doing it w

[go-nuts] Re: Best way to launch/monitor several go process in production

2017-09-04 Thread Gernot Reisinger
For the monitoring part I can recommend https://www.dynatrace.com/technologies/golang-monitoring (https://www.dynatrace.com/blog/introducing-fully-automated-support-for-go-based-application-monitoring/). Am Sonntag, 3. September 2017 23:35:30 UTC+2 schrieb emarti...@gmail.com: > > Hello, > > I a

[go-nuts] Re: Best way to launch/monitor several go process in production

2017-09-04 Thread Diego Medina
This https://github.com/jpillora/overseer may do what you need or at least give you an idea of what you can do. The way oveerseer works is, you start your app, when you send a particular kill signal, it keeps the running app running and it spawns a duplicate, it passes new http requests to the

[go-nuts] Re: Best way to launch/monitor several go process in production

2017-09-04 Thread Christian Joergensen
On Sunday, September 3, 2017 at 11:35:30 PM UTC+2, emarti...@gmail.com wrote: > > I am looking for the 'best' way to launch and monitor several go > processes. Doing it with just 1 is easy enough, using monit or systemctl > should do the trick, however since our app takes a while to start, we wa