Wireshark-bugs: [Wireshark-bugs] [Bug 7484] New: RFE: rpc.time in caller
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 16 Jul 2012 06:39:25 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7484

           Summary: RFE: rpc.time in caller
           Product: Wireshark
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: Dissection engine (libwireshark)
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: wireshark-bugs@xxxxxxxxxxx


Build Information:
Build version n/a
--
========
Problem:
Doing some troubleshooting which involves long RPC times, rpc.time is
invaluable for identifying problematic RPC (actually NFS) calls.

This debugging consists of finding long rpc.time, finding the corresponding
call, and walking through the packets in the GUI to find the sequence of
operations which is causing the fault.

However, it's not possible to construct a filter which shows long rpc.time
calls and replies together.

========================
Request for enhancement:
What would help enormously would be if the rpc.time metadata was added to both
the call and reply packets. I assume this could live around the same part of
the code which creates rpc.reqframe / rpc.repframe.

Are there any other *.time-like protocol metadata fields which do this, or
would benefit from a similar change?

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.