Logging Mode

Syntax:
<URL>/?log=<value>
Parameters:
<URL>: host name or IP address to the installed EMU hardware
<value>: is a number between 1 and 3 as follow:

  • 1: log only to browser’s local console
  • 2: log only to remote socket server
  • 3: log to the local console and to the socket listener simultaneously

Default:
By default a minimum logging to local console is active

Examples:
http://emu.ansari.de/?log=1
http://emu.ansari.de/?log=3
http://emu.ansari.de/?dbg&log=2
(accessing the on-line EMU-emulator)

Description

This command leads the web server to generate additional logging information not only to the browser’s local console (using developer tools with F12 function key), but also to a remote socket server, which can display the logs remotely.

When the debugging command (dbg) is used, logging data is automatically provided to the browser’s local console. Without the dbg command, if one wants to get all available logging data turned on, the command log=1 must be added to the end of URL string in combination with a ‘/?’ or ‘&’ if ‘/?’ is already there (see examples). 

Sending only debugging data to a remote socket listener can be activated by using the command log=2. Finally if the command log=3 is used, then the local console and the remote socket server will be provided with the logging information simultaneously. 

See more setting options for remote socket listener here: emuapi-socket

log – Example

Since all tests are done with Chrome, it is recommended to use also the Chrome browser when you follow the log-example below:

Try this:
http://emu.ansari.de/?dbg&log=3

  1. Open the link above in Chrome
  2. Hit the F12-key to start developer mode
  3. Hit the eacape-key, so that the console window pops up (if not already)
  4. Hit the F5-key to reload the page
  5. Watch the logs getting generated, while the page loads

emuapi-dbg