Project

General

Profile

Actions

Feature #5262

closed

Change forwarder logging to add interest nonce field

Added by Alexander Lane over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Category:
Forwarding
Target version:
Start date:
05/24/2023
Due date:
% Done:

100%

Estimated time:
Tags:

Description

Currently, DEBUG/TRACE level forwarder logging in NFD provides very little in the way of actual information on the actual incoming/outgoing traffic; while knowing the name of an interest is helpful, lacking the nonce can make tracing packets through multiple nodes and applications difficult. Adding a nonce field to the logging provides more information with relatively little cost.


Related issues 1 (0 open1 closed)

Related to NFD - Feature #5267: Add logging for originating interest for ASF probesClosedAlexander Lane05/24/2023

Actions
Actions #1

Updated by Alexander Lane over 1 year ago

  • Status changed from New to In Progress
  • Assignee set to Alexander Lane
Actions #2

Updated by Alexander Lane over 1 year ago

  • Subtask #5267 added
Actions #3

Updated by Davide Pesavento over 1 year ago

  • Target version set to 24.07

Alexander Lane wrote:

Currently, TRACE level forwarder logging in NFD provides very little in the way of actual information on the actual incoming/outgoing traffic

Well, it's not supposed to be a full packet trace...

I want to make sure there are not design reasons for not including it I'm missing before I finalize and submit this to Gerrit.

I don't think there are, but a few minor considerations for completeness:

  1. Generating the full URI as opposed to just the name requires more CPU cycles.
  2. The URI also shows the hop limit (if present in the interest), which changes over time, so if you're mining the logs and naively comparing whatever comes after "interest=" as a plain string, the same interest with a different hop limit will no longer match.
  3. The "interest URI" is not a well-defined concept, its format is purely an implementation choice of ndn-cxx and was mainly intended for quick debugging, I guess we didn't want to "expose" it too much in NFD (using it in the forwarder logs means that anyone analyzing the logs will have to implement some sort of parser for that vaguely-defined format).
Actions #4

Updated by Alexander Lane over 1 year ago

  • Subject changed from Change forwarder logging to use interest URI rather than name to Change forwarder logging to add interest nonce field

Currently, TRACE level forwarder logging in NFD provides very little in the way of actual information on the actual incoming/outgoing traffic; while knowing the name of an interest is helpful, lacking the nonce can make tracing packets through multiple nodes and applications difficult. Adding a nonce field to the logging provides more information with relatively little cost.

Actions #5

Updated by Alexander Lane over 1 year ago

  • Subtask deleted (#5267)
Actions #6

Updated by Alexander Lane over 1 year ago

  • Subtask #5267 added
Actions #7

Updated by Alexander Lane over 1 year ago

  • Subtask deleted (#5267)
Actions #8

Updated by Davide Pesavento over 1 year ago

  • Description updated (diff)
  • Status changed from In Progress to Code review
Actions #9

Updated by Davide Pesavento over 1 year ago

  • Related to Feature #5267: Add logging for originating interest for ASF probes added
Actions #10

Updated by Davide Pesavento over 1 year ago

  • Status changed from Code review to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF