Major Description
For debug purposes one may create log statements originating from log source SCRAPER and these messages are copied verbatim into the scraper main output web page. This will put the debug scraper logs in temporal order along with the AMQP traffic.
Note that the SCRAPER log source does not need to be created in the router's log sources setup but can be generated on-the-fly at any time in any module.
A log statement like
qd_log(qd_log_source("SCRAPER"), QD_LOG_CRITICAL, "Crazy event 42 happened!"
will result in a scraper display like
◊ 2020-06-11 10:56:54.694247 A0#378 INT.A [A0_6] <- [C0_1] EA1 transfer [1,3] (0) settled transfer_2 - 163 bytes transfer presettled ◊ 2020-06-11 10:56:54.695489 A0#402 INT.A [A0_6] -> [C0_1] EA1 flow [1,3] (1,32) ◊ 2020-06-11 10:56:54.695575 A0#404 INT.A [A0_6] -> [C0_1] EA1 transfer [1,4] (0) settled transfer_3 - 161 bytes transfer presettled ◊ 2020-06-11 10:56:54.695658 C0#206 EA1 [C0_1] <- [A0_6] INT.A flow [1,3] (1,32) ◊ 2020-06-11 10:56:54.695697 C0#207 EA1 [C0_1] <- [A0_6] INT.A transfer [1,4] (0) settled transfer_3 - 161 bytes transfer presettled ◊ 2020-06-11 10:56:54.696249 C0#223 EA1 [] [] SCRAPER (critical) Crazy event 42 happened! ◊ 2020-06-11 10:56:54.696635 C0#237 EA1 [C0_4] -> [] peer_11 attach [0,0] receiver link_31 (source: none, target: "$management", class: client) ◊ 2020-06-11 10:56:54.696689 C0#240 EA1 [C0_4] -> [] peer_11 flow [0,0] (0,250) ◊ 2020-06-11 10:56:54.696713 C0#241 EA1 [C0_1] -> [A0_6] INT.A flow [1,4] (1,250) ◊ 2020-06-11 10:56:54.696790 A0#408 INT.A [A0_6] <- [C0_1] EA1 flow [1,4] (1,250)