#RUBY PROCESS MONITOR HOW TO#
I'm completely clueless how to use it, links in the wiki are either non-existant or lead to Chinese/Japanese sites. :~$ eye load ~/eye/puma.eye working_dir '/home/deploy/eye/processes' is invalid
#RUBY PROCESS MONITOR INSTALL#
I'm using Puma on my production machine, when trying to install the gem as standalone gem on the server, copying the puma.eye from examples, I get following error: What is the folder #/deployment/? Is it supposed to be in my app? There is no such folder. Do I need a separate folder for an eye-project? (/home/deploy/projects/eye) Here what are variable values for the word 'project/s'? You use 'project1' and 'projects'. Would it be possible to create some sort of starter guide on how to use it?ĭo I install the gem as standalone gem on the production server?ĭo I include it in my application in the Gemfile?ĭo the configs live in a separate folder on the production server or in a folder relative to my app? I'd really love to use your gem, however I'm struggling with the basics. Thanks Bluepill for the nice config ideas. How to write Eye extensions, plugins, gems:Įye-http Eye-rotate Eye-hipchat Plugin example Process statuses history: $ eye hi(story) $ eye q - s # stop all processes and quit I'm using distributed Ruby processes with foreman, the processes commu. Log tracing (tail and grep): $ eye t(race) $ eye t test $ eye t sample What is the best way to monitore Ruby process ( Not Rails ), I tried to use Newrelic but it seems it is designed for Rails. eyeĬonfig explain (for debug): $ eye e(xplain) examples/test. With SolarWinds AppOptics, Ruby performance monitoring means you can understand the performance impact of database queries, remote calls, frameworks. $ eye i -j # show info in JSON format Commands: start, stop, restart, delete, monitor, unmonitorĬommand params (with restart for example): $ eye r(estart) all $ eye r test $ eye r samples $ eye r sample1 $ eye r sample* $ eye r test:samples $ eye r test:samples:sample1 $ eye r test:samples:sample* $ eye r test:*sample*Ĭheck config syntax: $ eye c(heck) examples/test. Two global configs loaded by default, if they exist (with the first eye load): /etc/eye. Processes removed from the config will be removed (and stopped if the process has stop_on_delete true). New objects(applications, groups, processes) will be added and monitored. If the eye daemon has already started and you call the load command, the config will be updated (into eye daemon). Load folder with configs: $ eye l examples/
Config exampleĮxamples/test.eye (more examples) Start eye daemon and/or load config: $ eye l(oad) examples/test. I hope we've succeeded, we're using eye in production and are quite happy. We wanted the features of bluepill and god, with a few extras like chains, nested configuring, mask matching, easy debug configs We wanted something more robust and production stable. We have used god and bluepill in production and always ran into bugs (segfaults, crashes, lost processes, kill not-related processes, load problems, deploy problems. Little demo, shows general commands and how chain works:
0 kommentar(er)
