Versions Compared

Old Version 26

changes.mady.by.user Robin Collard

Saved on

compared with

New Version 27

changes.mady.by.user Robin Collard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The trace can be used in different settings, to configure how the trace will behave, and how the timeline will behave. In the table below, different combinations of

Include Page
_PropertiesBootstrap
_PropertiesBootstrap
are explained:

Active bootstrap profilesEffect

Include Page
_ProfileTrace
_ProfileTrace

Both timeline and trace will be stored in the external datasource configured as "trace-sql-store"
 Include Page
_ProfileTimeline
_ProfileTimeline
Timeline is stored in external datasource "timeline-sql-store", trace is ignored
 Include Page
_ProfileTraceWithoutTimeline
_ProfileTraceWithoutTimeline
, 
 Include Page
_ProfileTimeline
_ProfileTimeline
Timeline is stored in external datasource "timeline-sql-store", trace in "trace-sql-store"
 Include Page
_ProfileTimeline
_ProfileTimeline
, 
 Include Page
_ProfileTracePublisher
_ProfileTracePublisher
Timeline is stored in external datasource "timeline-sql-store", trace is pushed to the exchange configured at the properties and will be consumed by the consumer functionality

Configuration

Database

Scripts to create the required database content are provided for the following databases:

...

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.

# RabbitMQ configuration
blueriq.trace.event.listener.amqp.version=2.0
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.

...