New in Network Monitor 3.3 and API issue

[Romany]

I have read illustration and help file of NM 3.3. In addition I watched the video on Channel 9. Still I do not recognize how to utilize those APIs. How be able to I get procedure id for an http request in a live incarcerate session. Do not locate several filters that I am able to utilize but the GUI has this potential. So I think it is probable. Can anybody share an example code to do this. Too little information in sequence obtainable in the help file. An additional question, What is New in Network Monitor 3.3.

[Visala28]

The network Monitor 3.3 is a protocol analyzer. It permits you to incarcerate network traffic, observe and analyze it. The version 3.3 is and bring up to date and reinstates Network Monitor 3.2. Network Monitor 3.x is a comprehensive overhaul of the preceding Network Monitor 2.x description. The Network Monitor core engine has been decoupled from the parser set. To inaugurate the complete Network Monitor 3.3 products: you have to work or start the setup.exe for the platform you are installing.

[teenQ]

You have to see the majority current traffic as it comes in. In a live incarcerate, hit it off the Autoscroll switch on the main toolbar to have the Frame Summary window mechanically scroll down to display the majority current frames as they come in. Hit it off Autoscroll once more to freeze the vision in its present position. In this you have to right-click-go-to-description, Right-click a field in the Frame particulars windows and choose and go to data Field Definition or go to Data Type Definition to observe where the field is distinct in the NPL parsers.

[Candace]

The API Extensions: API methods have been additional to facilitate right of entry to discussion information, properties, field display strings, and commentary. The capability to open ETL files and associate information in sequent by Network Tracing scenario. The set of core parsers to get better parsing presentation. These be able to be accessed by changing the Common and Windows set of parsers to stubs, for this you have to go to the tools menu, then you have to choose the options, after that you have to go to the Parsers Tab. After that you have to choose the folder you desire to stub out (Common or Windows). Then at the end select on the Stubs switch on the toolbar.

[Carley]

Regrettably you do not permit them to incarcerate process information in sequence with the API unswervingly. As an alternative you determine to have to do what our UI does and call the process info API unswervingly. Then take that information in sequence and map it to the IP address and TCP ports. This is something you desire to add in the prospect, but right at present it’s limited to running in the UI only. As for the HTTP Parser and not parsing "referer" be able to you give you additional information.

[addie]

The API is capable to read the process information in sequence generated from the UI, but the API cannot incarcerate that information in sequence. The UI keeps track of the entire the process tracking information in sequence and saves it as part of the incarcerate file. This is missing from the API incarcerate engine today. As for the HTTP field, in view of the fact that HTTP is self describing you be supposed to parse this field in the UI.