Changes between Version 1 and Version 2 of UnifiedLogger

Timestamp:

07/12/2019 08:13:18 AM (7 years ago)

Author:

jdalbey

Comment:

draft

UnifiedLogger

@@ -15 +15 @@
 The output is a CSV file, unifiedlog.csv, which merges all the previous logs and orders them by simulation time.
 
-A separate web app, unifiedlogmonitor.html, runs in a web browser to display a nicely formatted version of the CSV file.
+A separate web app, `unifiedlogmonitor.html`, runs in a web browser to display a nicely formatted version of the CSV file.
 
 === Configuration ===
@@ -39 +39 @@
 
 The application will echo logs to the console for diagnostic purposes.The expected output file is `unifiedlog_expected.csv` (attached).
+
+While the application is running you may append further entries to either data file, save it, and observe the output csv file is updated with the new entry.
+
+''(TBD: explain time interval.)''
+
+Open `webapps/unifiedlogmonitor.html` in a web browser and observe the csv file listed in reverse chronological order, formatted like this:
+
+{{{
+example
+}}}
+=== Usage ===
+Start the CAD server and Simulation Manager.  Load the practice script and start it running.  Start a CAD client. In a browser, start CPTMS.  In a browser, start `unifiedlogmonitor.html`.
+
+Wait for an incident to appear in the CAD client.  Open the incident viewer and in the upper comments field, enter a note "hello world" and press Exit/Send.Wait ten seconds and observe an entry for CAD Log appear in the monitor.  
+
+In CPTMS, display the CMS layer, open a CMS dialog and enter a message "SLOW TRAFFIC".  Click "Send" and wait ten seconds.  Observe an entry for CMS Activated to appear in the monitor.   Update the CMS message results in a "CMS Updated" entry in the unified log.  Clearing a CMS message results in a "CMS Deactivated" entry in the unified log.
+
+=== Running as a background service ===
+''TBD: Explain how to start the service as a unix daemon.  Explain start, stop, restart.  Explain which files are reset, etc.''