NetRule 7.1 Release Notes
July 19, 2005. Analytical Engines announced the release of NetRule
7.1. This release includes additional steps in fine-tuning application analysis and automatically constructing
models using import of .cap packet capture files and model refinement features.
Following are brief descriptions of the major new or enhanced features in NetRule 7.1:
- IP address field added as optional fields on computers and nodes.
- simplified import dialogues resulting from increased data extraction during imports
- client/server roles identified automatically by
- registered port look up
- inclusion of an applications file
- default: first port encountered is the client
- automatic population of the optional IP address field during import
- device names default to their IP address unless an alias is included
- device profiles can be included in the import
- the generalization option simplified to include all clients over all server ports
- choice boxes for transport protocol and CPU and Disk time are defaults for use when the data is not in the import file
- changes in the format files for input and output (traffic file and flow files).
- enhanced application data extraction from packet captures.
Job profiles and jobs generated during the import of packet captures will reflect
- turns rather than packets
- include only payload from Layers 5,6, and 7 in the message and reply byte counts
- exclude ACK-only packets
- use network and transport protocols as identified in the packet headers
- calculate server response time based on start time and duration (these will be used in the future also in defining multitier jobs)
- more accurate ACK rate including ACK piggy-backing, based on byte counts, number of turns, and protocols.
Analytical Engines is also proud to announce its release of TraceMark, a freeware application for use in marking captures of multi-turn transactions. TraceMark is a small Java utility that generates special UDP packets with transaction names. These packets also are captured in the trace. NetRule recognizes the marker packets as delineations between transactions. This enables jobs with multi-flows and multi-turns to be easily identified. NetRule automatically creates jobs representing the transaction with the observed flows and number of turns.
Contact us for additional information about NetRule 7.1 and TraceMark.
NetRule | About Us | Other Products | Services | Contact Us