On Wed, Oct 16, 2013 at 2:10 PM, Brad Watkins <bwatkins at thinkingphones.com>wrote: > > I don't personally see a need for logging functionality within ARI. > There are so many ways in any language you can think of to log to > files/database/etc. that complicating the ARI in order to pollute > asterisk's logs more seems unnecessary. > > - Brad > > Actually, a few people (/me looks at Alistair and Lenz) at AstriDevCon expressed an interest in this functionality. The idea is that an Asterisk application - whether or not that's a dialplan application or an application that is written and controlled via ARI - still interacts with Asterisk. There may be times when you want log messages from that application to also emit log messages in Asterisk, so that the context of what happens to a call is still in the same log file with the rest of the Asterisk messages. Say for example your application hits an error condition and hangs up the channel - from the Asterisk log file perspective, it just got a DELETE channel and it hangs up the channel. It doesn't know why it hung it up - for all it knows, the hangup was completely nominal. Having the ability to send a: [Oct 16 17:20:23] ERROR[20023] my_first_queue.py:1234: Oh snap! There aren't any agents! Bail - bail - bail Tells you why the caller just got hung up from the Asterisk log without having to look at your ARI application log file. At the very least, it correlates when the activity happens from Asterisk's perspective, giving you a starting point in your application log file as well. Matt -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20131016/4b8c4d98/attachment.html>
