[HECnet] HECnet mapper -- request to backbone node operators

ok so you got me curious about this and i worked it out. i'm not using any of the yaml/json config files for logging, so the default logging goes to the console. by adding "logging console" to the config i get all the events as expected into my log file as specified on the startup command line. but i have one query for paul: is it valid to have both "logging monitor" and the "logging console" enabled together in the configuration file? i want to make sure that i'm pushing data to your sink-node and that by enabling "logging console" i'm not reverting/overriding that part of the config. otherwise i need to implement this other logging config. cheers, Wiz!! ________________________________ From: owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> on behalf of Robert Armstrong <bob at jfcl.com> Sent: Monday, 17 August 2020 11:18:27 AM To: hecnet at Update.UU.SE Subject: RE: [HECnet] HECnet mapper -- request to backbone node operators I have a whole yaml file for logging, which is mostly taken verbatim from Paul?s example. I get tons of logged events ? starting circuits, starting datalinks, nodes up, areas up, routers discovered, etc. It doesn?t seem like it?s changed with this release. You might try that. For example, an hour ago I just got 2020-08-16 17:06:07.775: A2RTR: Event type 4.7, Circuit down, circuit fault From node 2.1023 (A2RTR), occurred 16-Aug-2020 17:06:07.775 Circuit = MUL-35 Reason = Circuit synchronization lost Adjacent node = 35.1023 (A35RTR) 2020-08-16 17:06:28.432: A2RTR: Event type 4.10, Circuit up From node 2.1023 (A2RTR), occurred 16-Aug-2020 17:06:28.432 Circuit = MUL-35 Adjacent node = 35.1023 (A35RTR) Bob