[Nfd-dev] How to obtain statistical information

[Lan Wang (lanwang)]

I suppose you can just look at the nfdc code to learn how it obtains these statistics.

Lan

On Apr 7, 2019, at 8:23 PM, mengxue <mengxue_1224 at 126.com<mailto:mengxue_1224 at 126.com>> wrote:

Hi, Lan

    Thank you very much for your reply!
     I am sorry that I didnot explain the problem clearly. I would like to realize an application running on a NFD, and am wondering how this application can obtain the statistics of the NFD on its each interface, such as InInterests and TimedOutInterests.
    Thank you very much. Looking forward to your reply.

Best regards,
Xue Meng






At 2019-04-08 06:20:24, "Lan Wang (lanwang)" <lanwang at memphis.edu<mailto:lanwang at memphis.edu>> wrote:
I think the nfdc command can print some statistics.

Lan

On Apr 3, 2019, at 10:31 PM, mengxue via Nfd-dev <nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>> wrote:

Hi, all,

    Thank you very much for your reading.
    Recently, I am trying to implement some functions based ndn-cxx and NFD, and meet with some problems. I am wondering how to obtain statistical information of the router on its each interface (such as, InInterests, outData, and TimedOutInterests in ndnSIM tracer, http://ndnsim.net/1.0/metric.html  ). I find a similar function in nfd::Forwarder::getCounters(), but it seems to be the total number at the granularity of a router , not each interface. I am wondering how to obtain these metrics on each interface, where I should to realize this function, in the forwarding strategy like ndnSIM or somewhere else.
   Looking forward to your reply. Thank you very much.

Best regards,
Xue Meng



_______________________________________________
Nfd-dev mailing list
Nfd-dev at lists.cs.ucla.edu<mailto:Nfd-dev at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20190408/21e89f2b/attachment-0001.html>