Difference between revisions of "Syslog (AlphaCom)"
From Zenitel Wiki
(→Facility value) |
(→Statistics log) |
||
Line 25: | Line 25: | ||
==Statistics log== | ==Statistics log== | ||
− | The [[AlphaCom call statistics log]] reports on one priority level: Local2:Info | + | The [[AlphaCom call statistics log|Call Statistics Log]] reports on one priority level: Local2:Info |
[[Category:AlphaCom E Software]] | [[Category:AlphaCom E Software]] | ||
[[Category:Logging]] | [[Category:Logging]] |
Revision as of 07:00, 29 March 2012
Syslog is a standard for forwarding log messages in an IP network. The term "syslog" is often used for both the actual syslogprotocol, as well as the application or library sending syslog messages.
The syslog is configured from AlphaWeb.
Facility value
The Facility value is a way of determining which process of the AlphaCom created the message. Since the Syslog protocol was originally written on BSD Unix, the Facilities reflect the names of Unix processes and Daemons:
- Local0: Debug log
- Local1: System log
- Local2: Call Statistics Log
Debug log
The Debug log contains the same information as transmitted on the TST console. On AMC systems the information was stored in a small error buffer which could be read by the "err" command from the TST console.
The Debug Log reports on three priority levels:
- Local0:Warning
- Warning – Information to the user. Often identical to texts sent to the log port
- Local0:Error
- Error – The software handles a problem by e.g. aborting an operation and returning to idle, but logs a message
- Local0:Crit
- Disaster – Exchange reset. The state of the exchange is so bad that the software does a controlled reset to restore normal operation.
System log
The System Log reports on one priority level: Local1:Notice
Statistics log
The Call Statistics Log reports on one priority level: Local2:Info