Syslog format that is supported by syslog and log aggregators such as Logstash and Fluentd via plugins. JSON format that is supported by Graylog, Logstash, and Fluentd.
Docker syslog name software#
To configure the software event broker Docker container logging facility output format, include the logging//format configuration key during container initialization and specify one of the following values: Log Output Format To extract the facilities from the output, use a log aggregator (Logstash, Fluentd) and filter on the logging facility field you are interested in. If you direct multiple logging facilities to stdout, all facilities are combined into a single stream. In this example, output for all logging facilities is directed to both a log file on the local host and the software event broker Docker container's stdout I/O stream. Solace recommends against this setting because logs generated for the corresponding facility are effectively lost.
Directs the logging facility to the appropriate log file in /usr/sw/jail/logs on the local host.ĭirects the logging facility to both a log file on the local host and stdout.ĭirects the logging facility to neither a log file or to stdout, (effectively NULL).īe aware that setting the logging facility output destination to none is equivalent to disabling the logging facility. To configure the software event broker logging facility output destination, include the logging//output configuration key during container initialization and specify one of the following values: Output Destinationĭefault output destination. In this example, output for the command facility is directed to stdout and output for the system facility is directed to both a file on the local host and stdout. Incidents or errors encountered by event broker processes, for example event broker events related to publishers and subscribers.Īction performed or errors encountered by low level processes used for internal debugging.įor example: logging_command_output=stdout The system facility is a subset of the event facility. Incidents or errors encountered by event broker processes that relate to the health of the event broker. You can configure the output destination, and format (if stdout is specified as the destination) for each of the following logging facilities: Logging FacilityĪctions performed or errors encountered by debug processes used for internal debugging.Īctions performed or errors encountered by commands issued at the Solace Command Line Interface (CLI) prompt, by CLI script files, or by SEMP. This allows you to control the output destination and format of each facility independently. When you use configuration keys to format or direct log output, you must include the logging facility name in the configuration key name.
Docker syslog name drivers#
If you direct the logging facilities to stdout, you can modify the output format and use the Docker logging drivers to forward the output to an alternate location, for example an external log aggregator, for additional storage, analysis, and reporting.įor more information about event broker logging, including a detailed description of the default syslog message format, see Monitoring Reference Guide.įor more information about using Docker create options to control software event broker behavior, see Docker Create Options. With the Solace PubSub+ software event broker Docker container package, you can also configure the event broker to direct the logging facilities to stdout using configuration keys when you create the software event broker Docker container.
In addition, you can use the Solace CLI to direct each of the logging facilities to a remote syslog receiver. By default, the Solace PubSub+ software event broker generates log messages, based on the format defined in RFC 3164, and directs them to log files for each logging facility in /var/lib/solace/jail/logs.
0 kommentar(er)
