| Summary: | ASTERISK-00103: Feature Request: Console Timestamp | ||
| Reporter: | denon (denon) | Labels: | |
| Date Opened: | 2003-08-15 11:15:01 | Date Closed: | 2004-09-25 02:49:15 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Would it be possible to have a (possibly optional) timestamp on the console events? It'd be nice to see, at a glance, what time events happened from the console when trying to troubleshoot a problem. | ||
| Comments: | By: Mark Spencer (markster) 2003-08-15 13:31:17 Are you talking about LOG_FOO or ast_verbose messages? By: fhedberg (fhedberg) 2003-08-18 03:45:12 I'd be talking about ast_verbose By: John Todd (jtodd) 2003-09-08 21:10:00 I would agree with this, and I think that this may be part of a larger future feature request which is a configurable CLI interface as well. The big fat dumping ground that is the CLI STDOUT is very unweildy, and almost useless for tracking down problems when multiple calls are happening at the same time. By: zoa (zoa) 2003-10-27 13:12:54.000-0600 would this also improve the mixing of the monitoring script that now sometimes sounds completely fucked up because something went wrong with the mixing ? By: Brian West (bkw918) 2003-12-16 19:06:03.000-0600 bug 665 has this | ||