circle-info
📢 The Ask AI can now translate any part of the docs to your preferred language!
Read the guidechevron-right
search
sportradar.comSportradar Support Portal

Common Logs Explained

The following are the examples of logs you'll find for some common scenarios

  1. Most of the validation problems are because of the mismatch between market-associated specifiers and which specifiers are expected based on the market description. This is just a log entry and the message is processed and dispatched to the user code normally.

15:04:55,184 [WARN ] [uf-sdk-22020-22] [uf-sdk-22020-22-amqp-t-2] [c.s.u.s.i.r.OddsFeedSessionImpl] - Problems were detected while validating message odds_change, but the message is still eligible for further processing. ProducerId:5, EventId:'sr:match:40932447'

  1. Indicates a timeframe the client system took to process a message. Feed messages are time-sensitive and slow processing delays the delivery of the subsequent odds feed messages. If the accumulative delay is higher than a configured threshold - the producer will be marked down to protect the bookmaker from operating stale data and therefore - the punter getting an edge against him.

2023-05-30 15:01:19,790 [WARN ] [uf-sdk-22020-22] [uf-sdk-22020-22-amqp-t-2] [c.s.u.s.i.r.RecoveryManagerImpl] - The client took more than 1 second to process a message for producer 3 and event sr:season:105945 (4.018 seconds)

  1. Indicates that producer will not be producing messages. This might be happening due to multiple reasons like producer maintenance windows. 

2023-05-30 15:01:36,748 [WARN ] [uf-sdk-22020-22] [uf-sdk-22020-22-amqp-t-4] [c.s.u.s.i.r.RecoveryManagerImpl] - Received alive with subscribed=0 from [Producer[14 C-Odds]], initiating recovery

  1. The accumulative delay of processing messages on the customer end is higher than a configured threshold - producer is marked down to protect the bookmaker from operating stale data and therefore - punter getting an edge against him. 

2023-05-30 15:04:29,487 [WARN ] [uf-sdk-22020-22] [uf-sdk-22020-22-rm-t-0] [c.s.u.s.i.r.RecoveryManagerImpl] - ProducerDown:ProcessingQueueDelayViolation -> The max processing queue delay(20s) was exceeded, flagging producer as DOWN [Producer[3 Ctrl]]

  1. Indicates producer going down and an associated reason which in this case is too slow processing of messages on the customer end causing the bookmaker to operate with relatively out-dated (delayed) data. 

2023-05-30 15:04:29,489 [WARN ] [uf-sdk-22020-22] [uf-sdk-22020-22-rm-t-0] [c.s.u.s.i.r.RecoveryManagerImpl] - ProducerStatusChange[Producer[3 Ctrl]], reason: ProcessingQueueDelayViolation, isFlaggedDown: true, isDelayed: true

  1. Indicates producer is coming back up again and an associated reason for that, which in this case is due to finishing the initial recovery after SDK start up. 

2023-05-30 15:04:28,779 [INFO ] [uf-sdk-22020-22] [uf-sdk-22020-22-amqp-t-2] [c.s.u.s.i.r.RecoveryManagerImpl] - ProducerStatusChange[Producer[3 Ctrl]], reason: FirstRecoveryCompleted, isFlaggedDown: false, isDelayed: true

  1. Indicates that certain endpoint is about to be invoked. 

2023-05-30 15:01:28,232 [INFO ] [] [pool-12-thread-1] [c.s.u.s.i.LogFastHttpDataFetcher] - Fetching data from: 
https://global.stgapi.betradar.com/v1/descriptions/en/markets/534/variants/pre:markettext:192371?include_mappings=true

  1. A periodic check scheduled to run several times a minute which provides the status of the producers. String Literal "Producer" is followed by:

  • Producer id (which is 1, 3 and 14 in this case)

  • Producer abbreviation (LO for live odds, Ctrl for pre-match and C-Odds in this case)

  • number of seconds lapsed since last receival of feed message by the SDK (excluding processing impact on the customer end completely) 8, 5 and 2 in this case

  • number of seconds lapsed since last processing of feed message by the SKD (including processing impact on the customer end) 9, 5, and 2 in this case

  • producer state (whether it is up or down) - all 3 UP in this case.

  1. Similar to the previous one, just with additional information provided during the recovery. The producer 3 additionally is indicated to be in the process of performing its recovery.

  1. Provides information about the message received from the SDK right after it arrives from the server to the SDK. In this case it was received on a user session configured to receive only Prematch messages only, it contains a rabbitMQ routing key, and an xml message content.

  1. Indicates amount of time it took for the SDK (including customer processing impact) to process the feed message.

  1. Indicates the information about failed request providing status code.

  1. Sessions tracks the time frame they do not receive Odds Feed message from the server and after 3 minutes of inactivity close the rabbit connection which is usually represented by the following pattern in the log file, namely channels and connection getting disconnected as well and recoveries being issued.

  1. In 5 seconds after closing the connection, it is attempted to be recreated which usually is represented with the following pattern in the log file, namely creating the connection, stargin channels and continuing issueing recoveries.

PreviousExamplesNext.Net

Last updated

Was this helpful?