Starting a Solace Broker Container pre-configured

Solace Event Broker
,
1

Hello everyone,

I’m looking to run a Solace Broker container with a modified configuration right from the start.

Specifically, I need to ensure that the container is launched with a specific syslog endpoint already configured. This would save a manual configuration step after the broker is running. is this possible?

Thanks in advance, Pascal

2

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

Let me analyze how to configure a Solace software event broker container with a pre-configured syslog endpoint.

The documentation shows that syslog configuration can be done in two ways:

  1. Using configuration keys during container initialization
  2. Using the Solace Event Broker CLI after the container is running

For pre-configuring syslog during container initialization, you can use the following configuration keys:

# Configure the logging output destination
logging_<facility>_output=<destination>

# Configure the logging format 
logging_<facility>_format=<format>

Where:

  • <facility> can be: debug, command, system, event, or kernel
  • <destination> can be: file (default), stdout, all, or none
  • <format> can be: graylog, rfc5424, raw, or legacy (default)

For example, to configure a container with syslog forwarding to stdout in RFC5424 format:

docker run -d \
  --env logging_system_output=stdout \
  --env logging_system_format=rfc5424 \
  --env logging_event_output=stdout \
  --env logging_event_format=rfc5424 \
  solace/solace-pubsub-standard

Key points:

  • The logging configuration must be done during container creation
  • Multiple facilities can be configured independently
  • When directing logs to stdout, you can use container runtime logging drivers to forward to external syslog servers
  • The format only affects logs sent to stdout - logs written to files always use legacy format

For more details on:

3

Hi Pascal,
As Solly-AI already told you:

Please have a close look at configuration keys (Configuration Keys) - that should solve your question.

Uli