Syslog and Process Logs
Logging events is a critical part of diagnosing misconfigurations and optimizing operations. Enterprise SBCs can send both syslog and process log data to appropriate hosts for storage and analysis.
The Enterprise SBC generates two types of logs, syslogs and process logs. Syslogs conform to the standard used for logging servers and processes as defined in RFC 3164. You can encrypt syslog messages to the logging server by setting the transport-protocol attribute to TLS and configuring a TLS profile for that connection.
Process logs are Oracle proprietary logs. Process logs are generated on a per-task basis and are used mainly for debugging purposes. Because process logs are more data inclusive than syslogs, their contents usually encompass syslog log data.
Important:
Because process logs are not encrypted in transit, Oracle recommends only sending process logs to a logging server when debugging an active problem over a trusted network.Overview
The Oracle® Enterprise Session Border Controller generates two types of logs, syslogs and process logs. Syslogs conform to the standard used for logging servers and processes as defined in RFC 3164.
Process logs are Oracle proprietary logs. Process logs are generated on a per-task basis and are used mainly for debugging purposes. Because process logs are more data inclusive than syslogs, their contents usually encompass syslog log data.
Syslog and process log servers are both identified by an IPv4 address and port pair.