#28 Add Catalina logs to call browser

[David Suendermann-Oeft]

Dear Alex, Vikram,

Would you please work on yet another PHP script to enable call browsing in the Catalina logs? This provides a number of additional information points to be accessible including

• dialog state
• dialog name (description)
• ASR hypothesis
• semantic interpretation of ASR hypothesis
• actual branch taken
• URL of browsed VXML pages

To make all this information available, GGS will have to be adapted, too.

I am envisioning that the call browser's front page lists links to the speech logs and the Catalina logs side-by-side to allow users to chose the type of log they would like to look at at their convenience.

Thanks,

DSO

[Alexei V. Ivanov]

Done late January.

We've (Vikram was helping) propagated this capability to the production system.

[David Suendermann-Oeft]

Two questions:

1. Is there a documentation on how to set up the logging interface for a new Halef instance?
2. Are the logging processes now part of the restart.sh script as we talked about before?

[Alexei V. Ivanov]

Two questions:

1. Is there a documentation on how to set up the logging interface for a new Halef instance?

Yes, there is a README file, in the web directory. It lists commands, that need to be issued for the logging interface to get attached to the different log-files. Essentially there is a need to:

a) Launch the node web-server that pushes dynamic content to the browser;
b) Create "tail" processes that follow-up on log-file updates;

Option "b)" is a "temporary solution". In order to make it reliable we shall plan to move logging into a stand-alone database. This way besides having reliable access to the recent history we will be able to do proper time synchronization.

1. Are the logging processes now part of the restart.sh script as we talked about before?

We can't simply add those to restart script for the following reasons:

a) Restart shall be done several times until we manually make sure that Mary is up and running, while we have a need in only one tail process per log file;

b) Tailing to a local file from the log on a remote machine is a hack that needs to be launched in a separate screen to keep it active. It involves manual authentication on the remote host, unless the two interacting hosts are capable of encrypted key-based authentication. (As it is noted above, the permanent solution of all these woes is in (eventually) switching from the file-logging to the DB-logging.)