Story:
NETCONF Servers increased the precision of seconds for netconf events to nano-seconds.
Please see related commit: https://github.com/sysrepo/sysrepo/commit/7ba762fcd8ca707a56b872f28ffce0f586a45b7e
As a consequence of this change ODL logs are flooded with "WARNINGs" and the logs are less readable.
2024-02-07T17:19:40,519 | TRACE | globalWorkerGroup-3-15 | NetconfDeviceCommunicator | 324 - org.opendaylight.netconf.sal-netconf-connector - 5.0.7 | - | RemoteDeviceId[name=CommScope-Era-Adapter-03, address=/172.60.0.36:830]: Notification received: <notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2024-02-07T17:19:40.508223593+00:00</eventTime>
<supervision-notification xmlns="urn:o-ran:supervision:1.0"/>
</notification>
2024-02-07T17:19:40,520 | WARN | globalWorkerGroup-3-15 | NetconfNotification | 319 - org.opendaylight.netconf.notifications-api - 5.0.7 | - | Fraction of second is cut to three digits. Value that was cut 223593
Request:
It is ok cutting fractions of seconds within ODL-NetConf. But the debug level for the Log should be changed from "WARNING" to "DEBUG".
Please change the "Log.warn(" in class: org.opendaylight.netconf.notifications.NetconfNotification, line 55ff
to "Log.debug(..."
avoiding a flood of warnings in the logs under normal conditions.
Note:
In addition, there is a request to Netopeer to make the precision of seconds configurable, but this does not help in case of other NETCONF Server implementations.
- relates to
-
NETCONF-270 2 digits milliseconds can not be parsed in notification eventTime
- Resolved
-
NETCONF-1000 Clean up NetconfMessage
- Resolved