Reference7:Configuration/General/Logging
Logging
External logging is disabled by default (Off). You can still view log messages in real time (see Logging), but messages are not stored or sent to an external destination.
Available Types:
Off: | Logging is disabled. | ||||||||||||||||
TCP: | The device transmits the syslog entries using a TCP connection.
| ||||||||||||||||
SYSLOG: | The syslog entries are transmitted to a syslog recipient (also referred to as syslogd, syslog server or syslog daemon).
| ||||||||||||||||
HTTP: | The syslog entries are transferred to a web server. Each individual syslog entry is transferred to the server as an individual request.
For more information on HTTP request formatting, see Reference7:HTTP Request Message Format. If the addressed Web server requires authentication, an Authenticated URL has to be configured on the HTTP-Client Page. The URL constructed by the logger is shown right next to the Path field. It must be entered in exactly this format on the HTTP-Client Page. The device has to be restarted after the Autenticated URL has been set. | ||||||||||||||||
LOCAL: | The syslog entries are saved to the local CF card into the /log directory, e.g. \\ipaddr\drive\CF0\log. Log files named LOG0.n are created, where n goes from 0 to 3. The next log file is created when either the Max File Size is reached or the Backup Time has passed. LOG0.0 is the newest log file always.
To concentrate all syslog messages to a single CF card, you would use the HTTP Log Server Type in all but one boxes with Method set to Standard. Address must be set to the IP-address of the single box that has the CF card used for log message storage. Port must be set to the port configured for the HTTP-Server of this box. |
Alarm and Event Handling
Alarm and event forwarding is configured independantly from the handling of log messages.
If no Forward Server is configured, alarms and events are stored locally as specified in the Local Alarm and Event Queues area below.