You can enable or disable the logging of alerts. See Enable and disable logging for the general instructions. The key to add to the <add key="Db.LogEvents" line in the appSettings.xml file is Alerts.

Important

If you modify the APPSETTINGS.XML on an already installed GN4 system, remember to close Ted4, Fred4 and browser and then recycle the application pool to apply changes.

Enable alerts logging

1.Locate the APPSETTINGS.XML file on your system. See Place APPSETTINGS.XML on a GN4 server to know the file location.

2.Open the file in any ASCII editor, and then locate the line that starts with <add key="Db.LogEvents".

3.If the line already contains the key Alerts in the value, as <add key="Db.LogEvents" value="Errors,Main,Triggers,Alerts" />, then you do not need to do anything - the alerts logging is already enabled.

Where is the log?

The log file is in the folder described in the <add key="Db.LogDir" value="C:\Tera\GN4" /> line in the APPSETTINGS.XML file. The log file name as specified by the <add key="Db.LogFileName" value="GN4" /> line in the APPSETTINGS.XML file.

How to read the Alerts log

Every time a client start getting alerts, a line is inserted in the log:

  . . . 

  /*

    Alerts: begin get for client login fc484d80-d974-4b81-9fa9-9e6b920f2b28

    2010-11-27T21:07:01.494+01:00

  */  

  . . .

 

... and when the client stops getting alerts:

  . . .

  /*

    Alerts: terminated get for login fc484d80-d974-4b81-9fa9-9e6b920f2b28

    2010-11-27T21:07:02.488+01:00

  */

  . . .

 

... and also when alert messages are sent to a client:

  . . .

  /*

    Alerts: sending 2 msgs to login f13ef173-92d2-4ecc-ac74-a89cb9293f66

    2010-11-27T17:07:10.717+01:00

  */

  . . .

 

... and also when expired messages are deleted:

  . . .

  /*

    Alerts: deleted 1 messages older that 15 seconds

    2010-11-27T17:53:20.190+01:00

  */

  . .