ndt-users list created

["Seth Peery" <>]

Fellow NDT-users,

I'm hoping to resurrect an archived discussion on the parsing of
web100srv.log.  The messages below, from 2006, were the most recent that
I could find that addressed a method of figuring out which log entries
corresponded to what NDT variables.  I'm wondering if there has been any
additional development in this area.

I developed the "Community Broadband Map" tool at Virginia Tech
(http://www.ecorridors.vt.edu/maps/broadbandmap.php), and I've merged
NDT with a number of other web-based maps since the original project.
At the time, I did not pull all the variables from the applet into the
PHP that does the DB insert when a user runs a speed test - just
timestamp, c2sspd and s2cspd.  Now I'm hoping to retroactively parse
web100srv.log into a format that can be imported into a database and
then associated with the existing entries by making a key out of the IP
address and timestamp, which should give me a unique identifier. 

We've got the development resources here to construct a parser for this
log file if need be (which could then of course be shared with the
community), but before I embarked on this, I wanted to see if anyone has
  a) some documentation of the order of the variable names in the log
file beyond the comments in web100srv.c 
  b) an active effort to develop a parser with which we might
collaborate

I don't want to step on anyone else's toes in the community if this is
an ongoing project; furthermore I want to make sure that I am correctly
interpreting which variable is which.

I will appreciate any insight the community might have into this matter.

______________________________________________________
Seth Peery
Senior GIS Architect
Enterprise GIS Research and Development Administration
Virginia Tech

(540) 231-2178

-----Original Message-----
From: Richard Carlson 
[mailto:]
 
Sent: Thursday, November 02, 2006 10:52 AM
To: Kidwell, Michael Mr NISO/APPTIS; 'Clarke Morledge';

Subject: RE: Parsing web100srv.log in sync with client output?
(UNCLASSIFI ED)

Gang;

One other option you can think about is to turn the syslog logging
function 
on.  This outputs "name=value" tags to the syslog file.  At one point I
had 
this going to a database, but haven't continued that code development.

Anyone looking for a class project? .-)

Rich

At 07:05 AM 11/2/2006, Kidwell, Michael Mr NISO/APPTIS wrote:
>Classification:  UNCLASSIFIED
>Caveats: NONE
>
>There is a utility called "analyze" that is included in the
distribution.
>The way I use it (and I'm sure that others may have a more efficient
method)
>is to search the log for the transaction of interest, cut and paste it
into
>a blank document and save it. Caveat, the paste mechanism may take a
single
>line of data and make it multiple lines; you'll have to use an editor
to get
>this corrected. Then you can call "analyze -l <the file_name of your
log
>snippet>." The option to analyze is "el". If you get a segment fault,
review
>the caveat. Hope this helps. -- Mike
>
>-----Original Message-----
>From: Clarke Morledge 
>[mailto:]
>Sent: Wednesday, November 01, 2006 3:40 PM
>To: 
>
>Subject: Parsing web100srv.log in sync with client output?
>
>Aside from actually peering into the source code, is there a document
>available that can help me to parse through the output found in the
>web100srv.log?
>
>I am assuming that the web100srv.log file keeps a copy of each of the
test
>results and so I'd like to be able to correlate that to the client
output
>from the "Report Problem" button, but I'm having some trouble trying to
sync
>everything up.
>
>Thanks.
>
>Clarke Morledge
>College of William and Mary
>Information Technology - Network Engineering Jones Hall (Room 18)
>Williamsburg VA 23187
>Classification:  UNCLASSIFIED
>Caveats: NONE

------------------------------------



Richard A. Carlson                              e-mail:

Network Engineer                                phone:  (734) 352-7043
Internet2                                       fax:    (734) 913-4255
1000 Oakbrook Dr; Suite 300
Ann Arbor,  MI  48104