perl code to test 2.0.6 data on 3.0 ra

carter at qosient.com carter at qosient.com
Tue Jun 27 09:26:58 EDT 2006


Hey Peter,
So, this is great!!  It will, however require that we figure out what to do with the inconsistencies!  And there should be some rules, I suspect.  Here is a first shot.

Metrics must conform, unless there is/was an error in the original code.
So we should focus on getting those right.

Flow key values must conform, although the names can vary.  Values like 'rtp' becoming 'udp' is ok, although not preferable.

Status fields can change, however, what it changes to should be rational.

I will try to make them look the same, but there will eventually be changes!!  Let's not lose the opportunity to fix some things, if we can!!!

OK, can't fix it without an argus-2.0 file as the reference.  Care to share the data (if you didn't include it earlier).

Carter
Carter Bullard
QoSient LLC
150 E. 57th Street Suite 12D
New York, New York 10022
+1 212 588-9133 Phone
+1 212 588-9134 Fax  



More information about the argus mailing list