Summary: | ASTERISK-25728: Better tracking of calls within Asterisk Logs needed (UNIQUEID) | ||
Reporter: | Sherwood McGowan (smcgowan) | Labels: | |
Date Opened: | 2016-01-26 13:31:53.000-0600 | Date Closed: | 2016-01-26 13:46:32.000-0600 |
Priority: | Minor | Regression? | |
Status: | Closed/Complete | Components: | |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | All | Attachments: | |
Description: | When trying to track a single call through massive Asterisk full logs, it would be extremely handy to have the option to add the UNIQUEID to all log entries in logger.conf.
| ||
Comments: | By: Asterisk Team (asteriskteam) 2016-01-26 13:31:55.371-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Joshua C. Colp (jcolp) 2016-01-26 13:46:32.831-0600 Feature requests such as this are not allowed on the issue tracker. On the specific subject you raise though Asterisk 11 added call-id logging[1] which gives each call (this includes resulting outbound channels) an identifier that can be used to follow it. [1] https://wiki.asterisk.org/wiki/display/AST/Call+Identifier+Logging |