Feature #1685
osmo-sip-connector: Review and define log statements and which info to include
Start date:
03/31/2016
Due date:
% Done:
0%
Resolution:
Description
Define how to handle logging and which fields to include. It should be call + leg. Right now it is only leg.
History
#1 Updated by laforge over 3 years ago
- Category set to osmo-sip-connector
#2 Updated by laforge over 2 years ago
- Project changed from OsmoNITB to osmo-sip-connector
- Category deleted (
osmo-sip-connector)
#3 Updated by laforge over 1 year ago
- Assignee changed from zecke to sysmocom
#4 Updated by laforge about 1 year ago
- Assignee changed from sysmocom to osmith
#5 Updated by laforge about 1 year ago
#6 Updated by osmith 12 months ago
- Status changed from New to In Progress
laforge, keith:Define how to handle logging and which fields to include.
- Which additional log messages would be useful and which fields should they have?
- Are there missing fields in existing messages?
- Is there unhelpful information that we should not display at all or only output when increasing the log level?
It should be call + leg. Right now it is only leg.
- Do you guys want an additional log message when a call has been initiated?
- Which other call related log messages would be helpful?
#7 Updated by laforge about 1 month ago
- Tracker changed from Bug to Feature
- Parent task deleted (
#1604)
