bearrundr / bots

Automatically exported from code.google.com/p/bots
0 stars 0 forks source link

contextual engine log #305

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
The idea : Have more contextual engine log.

Keep network traces only for a specific channel :
  - Add debug bool or log_level field in channel model

Debug a specific translation.
  - Add readrecorddebug bool in translate model
  - Add mappingdebug bool in translate model

And make the engine write his log according to it.

Original issue reported on code.google.com by lucky...@gmail.com on 18 Apr 2014 at 10:39

GoogleCodeExporter commented 8 years ago
think that would be possible.
for channels there is the problem that at the moment there are no more 'spare 
field' in the database.
(try to avoid changes in database because migration is less easy)

(for myself: I use these extended log settings only in development. And 
nowadays I mostly use the 'checklevel' setting. )

Original comment by hjebb...@gmail.com on 20 Apr 2014 at 12:13

GoogleCodeExporter commented 8 years ago
I also only do this in a development environment

Original comment by mjg1964 on 28 Apr 2014 at 10:36

GoogleCodeExporter commented 8 years ago
if only used in development, it probably would be overkill?

Original comment by hjebb...@gmail.com on 1 May 2014 at 1:07

GoogleCodeExporter commented 8 years ago
Yes I agree for mapping, but for networks, dev and prod could have different 
rules for each part, and it could help in some cases if errortext is not enough 
: server certificate change, proxy, imap, ftp, server down, ... 
I don't know if errortext is enough to investigate all case.

Original comment by lucky...@gmail.com on 1 May 2014 at 3:55