Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

contextual engine log #305

Open
GoogleCodeExporter opened this issue Mar 29, 2016 · 4 comments
Open

contextual engine log #305

GoogleCodeExporter opened this issue Mar 29, 2016 · 4 comments

Comments

@GoogleCodeExporter
Copy link

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 [email protected] on 18 Apr 2014 at 10:39

@GoogleCodeExporter
Copy link
Author

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 [email protected] on 20 Apr 2014 at 12:13

  • Added labels: Bots-engine, version3.2

@GoogleCodeExporter
Copy link
Author

I also only do this in a development environment

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

@GoogleCodeExporter
Copy link
Author

if only used in development, it probably would be overkill?

Original comment by [email protected] on 1 May 2014 at 1:07

@GoogleCodeExporter
Copy link
Author

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 [email protected] on 1 May 2014 at 3:55

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant