Changed
- Option to ignore logs from selected gRPC methods now supports ignoring logs for selected errors on method.
Examples:--grpc.log-ignore-methods="/ttn.lorawan.v3.GsNs/HandleUplink"
: log is skipped when no error occurs.--grpc.log-ignore-methods="/ttn.lorawan.v3.GsNs/HandleUplink:pkg/networkserver:duplicate_uplink;pkg/networkserver:device_not_found"
: log is skipped when eitherpkg/networkserver:duplicate_uplink
orpkg/networkserver:device_not_found
error occurs (but not on success).--grpc.log-ignore-methods="/ttn.lorawan.v3.GsNs/HandleUplink:;pkg/networkserver:duplicate_uplink"
: log is skipped on success or whenpkg/networkserver:duplicate_uplink
error occurs.
- The Gateway Server now takes into consideration the extra duty cycle checks present in the LoRa Basics Station forwarder. Previously the Gateway Server may accept the scheduling of downlinks which the packet forwarder would silently drop.
- Note that in some rare cases in which the LoRa Basics Station duty cycle is stricter than the windowed approach used by The Things Stack, the scheduling will fail and this will be visible via
ns.down.data.schedule.fail
events. Note that this is actually a positive outcome - it allows the Network Server to schedule the downlink via another gateway, while previously the downlink would be scheduled but get silently dropped on the gateway.
- Note that in some rare cases in which the LoRa Basics Station duty cycle is stricter than the windowed approach used by The Things Stack, the scheduling will fail and this will be visible via