Actions
Task #2450
closedMake log messages more uniform across all face types
Start date:
Due date:
% Done:
100%
Estimated time:
Description
I noticed that the various faces are quite inconsistent in what they log and which log level they use. I propose the following (draft) guidelines for current and future faces.
- Any abnormal condition that is not fatal (i.e. the face can continue working, usually discarding the packet that triggered this condition) must be logged at WARN level. Depending on the face implementation, this can include both non-fatal system call failures (e.g. read/write), and recoverable packet parsing errors.
- When closing a face under normal circumstances (e.g. EOF or explicit
close()
invocation) use INFO level. - When sending or receiving a packet, log the event at TRACE level.
- All log messages must include at least the face id within square brackets at the beginning of the message (example:
"[id:300] Something happened"
)
Updated by Davide Pesavento almost 10 years ago
- % Done changed from 0 to 30
Updated by Davide Pesavento almost 10 years ago
- Status changed from In Progress to Resolved
- Target version set to v0.3
- % Done changed from 50 to 100
Updated by Junxiao Shi almost 10 years ago
Change is merged. Please add these guidelines into NFD Developer Guide before closing this issue.
Updated by Davide Pesavento almost 10 years ago
- Status changed from Resolved to In Progress
- % Done changed from 100 to 80
In which section/subsection?
Updated by Junxiao Shi almost 10 years ago
In which section/subsection?
Face System - Extending NFD Face System
Updated by Junxiao Shi over 9 years ago
- Related to Feature #3173: Developer Guide: Face=LinkService+Transport and GenericLinkService added
Updated by Junxiao Shi over 9 years ago
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
This is no longer relevant after #3172 because Face is non-inheritable.
Actions