Make logs more fine grained and use python's native logger
Right now the logs are extrem.ely noisy… entire xml cdr’s are being dumped, its very hard to follow. A coarse grained approach might be:
* General—debug statements that happen in views.py for example
* Curl—all xml curl communication (request/response) between wikipbx and freeswitch
* ESL —all ESL (both directions) between wikipbx and freeswitch
And in the settings there would be the ability to OR these together so I could say Curl | ESL and it would only print those two types of logs. Finer grain approach might be to futher subdivide Curl into Curl-Config, Curl-Dialplan, Curl-XmlCdr, Curl-Directory.
Blueprint information
Whiteboard
Right now the logs are extrem.ely noisy… entire xml cdr’s are being dumped, its very hard to follow. A coarse grained approach might be:
* General—debug statements that happen in views.py for example
* Curl—all xml curl communication (request/response) between wikipbx and freeswitch
* ESL —all ESL (both directions) between wikipbx and freeswitch
And in the settings there would be the ability to OR these together so I could say Curl | ESL and it would only print those two types of logs.
Finer grain approach might be to futher subdivide Curl into Curl-Config, Curl-Dialplan, Curl-XmlCdr, Curl-Directory.
This would really help reduce time spent debugging wikipbx/freeswitch issues.
Also, we use log4py that is obsolete for many years while python's logging module would suffice.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
