![]() |
Server Logs |
||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
You should have the "Can Monitor" Server Access Right to view the Logs.
The options on the top of the page allow you to specify when the Logs files are created and deleted:
The Log files are created in the SystemLogs subdirectory of the Server base directory.
You should have the "CanTuneLoggerSettings" Monitor Access Right to modify the Logs Engine settings.
You can select one or several Logs in the list and then remove them using the Delete Marked Logs button. The active (current) Log file cannot be deleted.
You should have the "CanTuneLoggerSettings" Monitor Access Right to delete Logs.
If there are too many Log files on the Server, you can enter a string in the Filter field and click the Display button: only the Logs with names matching the Filter string will be displayed:
Click the Log file name to open it.
Only the records with time stamps in the specified interval are displayed.
If you are viewing the current Log and specify "*" in the second field, all records placed in the Log by this moment are displayed.
If you are viewing the current Log and specify some future time in the second field, the Server will keep the browser channel open, sending new Log records as they are placed in the Log. The channel is closed either at the end of the specified Time Interval, or when the Server starts a new Log.
|
Then the Log is scanned again (within the specified Time Interval), and the Server displays all records that have Prefix Keys matching one of the remembered Prefix Keys.
Some protocols (such as SIP) do not use connections. A SIP session ("dialog") consists
of several packets (each packet is recorded with its own SIPDATA-NNNNNN Prefix Key),
but all packets contain the same Call-ID line.
Use the
|
Use the Print command of your Web browser to print the filtered Log.
If the Server OS uses the time zone with daylight saving time, the time stamps used in the Log will not change when the local time ("GMT shift") changes. The new local time will be used when the new Log file is created.
If a new record cannot be placed into the Log due to a Log Manager performance problem, the Log Manager stores a short Overflow Marker instead. The Overflow Marker is a line with three asterisk signs (***).
If you filter the Log, the displayed part of the Log will always contain the OverFlow Markers if they exist in the selected part of the Log. If several sequential Overflow Markers have to be displayed, only the first one is displayed.
Use the Preferences link to open the Monitor Preferences.
Use the following settings to configure remote logging:
If the Log Manager fails to open a UDP socket or fails to send a datagram to the selected remote syslog server, the Log Manager switches the Records to Send option to Nothing and it stops sending Log records to the remote syslog server.