What's the meaning of lpcloggerselector : .debug in the lpc.cnf?

Frederic

LPC question: what's the meaning of *lpc*logger*selector : *.debug in the lpc.cnf?

Find more posts tagged with

elektron

lpc

Accepted answers

wasin.w

Hello @Frederic

I cannot find the parameter information in the LPC package and document. However, I am assuming that it should be the same as other RTDS components (ADS, ADH, RTC).

According to the RTC (the rebranded ADS - Pop) configuration file, this *logger*selector parameter defines the logging levels which will be enabled.

! *rtc*logger*selector : *.info
!#help
!    selector:
!
!    This parameter defines the logging levels which will be enabled.
!    One of the following levels may be specified:
!     *.alert - Alerts are typically logged when communications problems are
!               encountered.
!     *.critical - These are logged when the RTC determines that it runs
!                  out of memory.
!     *.error - These are typically logged with problems on startup.
!     *.warning - These are typically logged when the RTC receives status
!                 or error messages from the host transport.
!     *.notice - These are only logged when the RTC starts and stops its
!                congestion control algorithm.
!     *.info  - Log selected information regarding normal operation.
!     *.debug - This logs information when rare item-level events occur. This
!               can trigger a lot of messages to be logged so it should only
!               be turned on when debugging.  The most common occurrence of
!               this is when gaps in the update stream are found.
!
!    Selecting a level will automatically log messages for levels above it.
!    For example selecting *.info will log *.alert, *.critical, *.error,
!    *.warning, *.notice and *.info messages.
!
!    Default value: *.info
!
!    Note, the default is probably sufficient for most purposes and
!    should not log unnecessary messages.
!#end

Additionally, you may contact the LPC support team directly via the my.refinitiv.com website. The LPC can help you verify the server configuration parameters.

All comments

wasin.w

Hello @Frederic

I cannot find the parameter information in the LPC package and document. However, I am assuming that it should be the same as other RTDS components (ADS, ADH, RTC).

According to the RTC (the rebranded ADS - Pop) configuration file, this *logger*selector parameter defines the logging levels which will be enabled.

! *rtc*logger*selector : *.info
!#help
!    selector:
!
!    This parameter defines the logging levels which will be enabled.
!    One of the following levels may be specified:
!     *.alert - Alerts are typically logged when communications problems are
!               encountered.
!     *.critical - These are logged when the RTC determines that it runs
!                  out of memory.
!     *.error - These are typically logged with problems on startup.
!     *.warning - These are typically logged when the RTC receives status
!                 or error messages from the host transport.
!     *.notice - These are only logged when the RTC starts and stops its
!                congestion control algorithm.
!     *.info  - Log selected information regarding normal operation.
!     *.debug - This logs information when rare item-level events occur. This
!               can trigger a lot of messages to be logged so it should only
!               be turned on when debugging.  The most common occurrence of
!               this is when gaps in the update stream are found.
!
!    Selecting a level will automatically log messages for levels above it.
!    For example selecting *.info will log *.alert, *.critical, *.error,
!    *.warning, *.notice and *.info messages.
!
!    Default value: *.info
!
!    Note, the default is probably sufficient for most purposes and
!    should not log unnecessary messages.
!#end

Additionally, you may contact the LPC support team directly via the my.refinitiv.com website. The LPC can help you verify the server configuration parameters.

EXPLORE OUR SITES