Page History
...
| Note |
|---|
The Trace SQL Store either stores trace messages in the database, or consumes trace events from the queue. When the configuration below is enabled, only trace events are consumed, no trace messages are saved to the database directly. So if you enable this configuration, be sure to also enable the Trace Event Publisher Component, otherwise no trace information is saved anywhere. |
| Code Block |
|---|
# RabbitMQ configuration |
...
blueriq.trace.event.listener.amqp.rabbitmq.host=localhost |
...
blueriq.trace.event.listener.amqp.rabbitmq.port=5672 |
...
blueriq.trace.event.listener.amqp.rabbitmq.virtualHost=/ |
...
blueriq.trace.event.listener.amqp.rabbitmq.username=guest |
...
blueriq.trace.event.listener.amqp.rabbitmq.password=guest |
...
blueriq.trace.event.listener.amqp.rabbitmq.queueNames=trace |
...
# Enable consumer functionality |
...
blueriq.trace.event.listener.amqp.enabled=true |
Enable TLS connection
To enable a secure (TLS) AMQP connection to the queue, set the property "blueriq.trace.event.listener.amqp.rabbitmq.ssl.enabled" to "true".The default for AQMP port with TLS on RabbitMQ is '5671', it needs to be explicitly enabled though, see https://www.rabbitmq.com/ssl.html for more information.
...
Overview
Content Tools