Interesting Thanks. I did some quick testing on mysql processes and you are right, the `scalr-server-manage` restarts it after I kill the PID. I'll test the rest of the processes and say thank you for building something smart.
On Wednesday, March 23, 2016 at 11:26:25 AM UTC-6, DicsyDel wrote: > > scalr-server-manage is actually a supervisor that monitors and manages > scalr components, so no need to monitor this separately. The only > thing that can be monitored is supervisor itself. > > Regards, > Igor > > On 23 March 2016 at 10:20, Vitaliy Demidov <[email protected] <javascript:>> > wrote: > > 1 Next version of Scalr CE includes Scalr Health Dashboard which is > useful > > for monitoring service-xxx workers. I think we will improve it with > every > > day. > > 2 The only way to restart service is with `scalr-server-manage` > > > > I think we could do next release in mid-April. > > > > > > Cheers > > Vitaliy Demidov > > > > On Wed, Mar 23, 2016 at 7:00 PM, Jay Farschman <[email protected] > <javascript:>> wrote: > >> > >> I'm looking for advice from anyone who is monitoring the services > inside > >> Scalr. > >> > >> I know there is a tool `scalr-server-manage` that allows us to see the > >> running systems. > >> > >> # scalr-server-manage > >> crond RUNNING pid 4359, uptime 24 days, > >> 14:15:40 > >> httpd RUNNING pid 3772, uptime 24 days, > >> 14:15:44 > >> memcached RUNNING pid 4317, uptime 24 days, > >> 14:15:40 > >> mysql RUNNING pid 3955, uptime 24 days, > >> 14:15:40 > >> rrd RUNNING pid 3775, uptime 24 days, > >> 14:15:44 > >> service-analytics_poller RUNNING pid 5197, uptime 15 days, > >> 16:54:10 > >> service-analytics_processor RUNNING pid 5231, uptime 15 days, > >> 16:54:06 > >> service-dbqueue RUNNING pid 4859, uptime 15 days, > >> 16:54:21 > >> service-msgsender RUNNING pid 4826, uptime 15 days, > >> 16:54:24 > >> service-plotter RUNNING pid 4893, uptime 15 days, > >> 16:54:18 > >> service-poller RUNNING pid 5023, uptime 15 days, > >> 16:54:15 > >> service-szrupdater RUNNING pid 5160, uptime 15 days, > >> 16:54:13 > >> zmq_service RUNNING pid 5485, uptime 15 days, > >> 16:54:01 > >> > >> But I don't believe the system has any thing built in to monitor > >> processes, repair and alert. Am I missing something? Should I use > Chef or > >> MonitD? I'm a long time and recovering puppet user with little chef > >> experience. > >> > >> QUESTIONS > >> > >> What should I use to monitor services in Scalr? > >> If a service reports down should I simple call for it to start back up > >> again with `scalr-server-manage` > >> > >> Really looking for best practices before I just make something that > work > >> and seems to be really easy. Thanks. > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "scalr-discuss" group. > >> To unsubscribe from this group and stop receiving emails from it, send > an > >> email to [email protected] <javascript:>. > >> For more options, visit https://groups.google.com/d/optout. > > > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "scalr-discuss" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
