Logging Requirements
From N4C
Contents |
Work In progress
Motivation
All the field trials have to produce quantitative data that is
- Useful: for analysis do that it can be fed into results and improve future work
- Appropriate: Tells just what we need to know and no more
- Accurate: so far as we can manage it
The first set of field trials in summer 2008 need to log as much useful data about the DTN systems and usage as possible using as far as possible existing capabilities form the previous summer's systems
What should we be aiming to get
General
- Information about the number of times applications were used and where
- Information about how the messages traveled across the DTN
- Information about expected and actual routes followed (people, helicopters, etc)
- Information about how the Prophet routing protocol performed, including evolution of parameters
- Information about storage volumes used on relay nodes
- Debugging information as necessary if things don't work.
- Information about used capacities of the system or computer (particularly about RAM requirements
of each application to detect memory leakages)
DTN
- Establishment of connection with another node
- Loss of connection with another node
- The number of successfully exchanged bundles
- Name and index of the bundle that has been removed from the storage because of expired time to live
- Transfer rate of each exchanged bundle
- Status of successful reading of configuration files, report errors in details
- Additional change of settings during the execution of the application
Environmental applications
- Time of startup and shutdown of application
- Shutdown status or exit code (normal or quick shutdown, in the case that application has been terminated from outside this status gets lost)
- Status of successful reading of configuration files, report errors in details
- Additional change of settings during the execution of the application
- Information about additional requirements, settings or inputs from the user interface
- Successful connection to configured ports and devices (meteorological station, radiological probe, ultrasonic wind sensor, etc), report errors in details
- Report lost connections to ports and devices
- Information about data exchanged with external devices for debugging purpose
- Information about generated data messages that contain measured data
- All successful and unsuccessful connections to local database of archived measured data
- Success on archiving measured data in the local database in detail for each measured environmental parameter
Hikers App
Example from first winter test: Norut N4C Wiki First winter test MAX, MIN and AVG of Transference Time (s), Transference Rate (KBps), Distance (m), File size (KBytes) and Temperature (C).
How to log and collect the data
General
- The clocks on all nodes and devices in the system must be synchronized and set to correct time zone
DTN
Environmental applications
- Log data should be written in as possible simple human readable ASCII files that can be viewed with any available text editor
- Each event/log in the file should have its own human readable time stamp of it’s occurance
- The log data for each application should be stored in separate file(s)
- Each application should have one or more log files containing the latest logs
- The size of log file(s) should not exceed the size of 1Mb (for viewing also on less powerful computers)
- Older log files should be deleted to free disk space for new logs
- Log files should be transferred once a day to the central unit where required
Hikers App
- Log data is written in SQLite database
How to Analyze the data
General
Environmental applications
- When some failures occur (usually are detected on the central unit when the environmental data is invalid or missing) the log files are used by maintainers of system to determine the problem and to prepare tools and equipment for the repairs
- Statistics on the quality of operation of the system is made periodically at the end of each month in the form of QA/QC report. Log files are used for detail explanation of failures that are detected.
Hikers App
Example of log-database exported into Open Office spreadsheet: SummerTest2009/hikerpda-sync-log--2009-07-22.ods
Revision History
- 0.0 20080605 EBD Initial Creation.
- 0.1 20100601 Boštjan Grašič, MEIS d.o.o. begin_of_the_skype_highlighting end_of_the_skype_highlighting, Requirements for environmental applications
--Karl 10:26, 2 June 2010 (BST)
