[//]: # (werk v2)
# Don't log unparsable SNMP traps per default
key | value
---------- | ---
date | 2024-08-08T09:11:31+00:00
version | 2.4.0b1
class | fix
edition | cre
component | ec
level | 1
compatible | yes
When an SNMP trap arrives at the event console which can't be parsed for
various reasons (unknown SNMP engine ID, some deserialization error, ...),
we previously logged a full Python backtrace to the EC log. This could lead
to the incorrect conclusion that there is something wrong with the EC
itself, which is not what has actually happened: Actually, some device was
probably misconfigured and/or misbehaving. To avoid such log spam, such a
trap is now silently dropped at the standard "informational" log level, and
more details can be logged at higher levels when needed.
Show replies by date