Custom God logging?

Question

God has helped us keep a few services running on a Rails box (Nginx and MySQLd, specifically) but I'm hoping to get some more details when it actually swings into action. So far, setting the watch log file using w.log = /var/log/god/mysql.log (for example) gets us a lot of stuff like this:

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
 * Starting MySQL database server mysqld
   ...done.

...which is cool enough in its way, because it tells me that the server went down and God restarted it, but I'm hoping for something like a timestamp and maybe some other details. (Server load, memory status, or something else to help me diagnose why MySQLd went down to begin with.)

Does God support adding extra information to logfiles when events like this are triggered?

I think maybe you would be better off approaching your local church with this question... — , Dec 14 '10 at 22:35
There's one in every crowd. [This question](http://stackoverflow.com/q/3877178/306084) is much more entertaining, though. — pjmorse, Dec 15 '10 at 17:42

score 2 · Accepted Answer · answered Dec 18 '10 at 09:57

2

At the very least you should be able to get a timestamp by starting god with something like:

god -Dc config/sst.god --log-level debug

but as far as I can tell there should already be timestamps preceding log messages in your w.log file. As far as logfile customization goes, it looks like it's been an issue for a few years (short answer: it's not an option).

answered Dec 18 '10 at 09:57

Andy Mikula

16,796
4
32
39

Ugh. I'm not getting timestamps, but I guess a negative answer is still an answer. – pjmorse Dec 20 '10 at 18:58

Custom God logging?

1 Answers1