| Summary: | ASTERISK-00429: [request] Call monitoring/trapping from console | ||
| Reporter: | collinr (collinr) | Labels: | |
| Date Opened: | 2003-10-25 15:48:44 | Date Closed: | 2011-06-07 14:05:02 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | I think it would be good to be able to trap all debug,info,warning,etc messages calls based on a src#,dst#, technology type or channel and route it to the console. When you have a lot of calls going through, the console is very hard to follow. | ||
| Comments: | By: zoa (zoa) 2003-10-27 10:23:36.000-0600 i'd really like such a function too, as on a high loaded server debugging will flood you away on a putty adsl connection. Its nearly impossible to detect codec issues etc when several people are calling and only one is having problems. By: John Todd (jtodd) 2003-10-27 12:20:36.000-0600 While it is unrelated to the exact feature request we're talking about, those interested in this note may also be interested in the timestamp request: http://bugs.digium.com/bug_view_page.php?bug_id=0000107 By: Brian West (bkw918) 2004-05-02 01:14:44 You can tail -f | grep the logs the info is there if you need it that bad. This isn't practical or even a good idea on a loaded server... you're talking about filtering all console output. That takes memory and processor and could cause blocking issues while your busy filtering thru the output. | ||