https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/OPNFLWPLUG-644 OpenFlowPlugin <p>In a real prod environment its imperative to extract an audit trail of connection and disconnection events. Other events might also be important.</p> <p>Some options to consider are</p> <p>1. Have a keyword in the logs to identify its a connection event.<br/> 2. Put JMX metrics for this events (keeping a history will be difficult here)<br/> 3. Store these events in Datastore - this might be an overkill, and there are other better systems than our in-mem datastore for this purpose.</p> <p>For now option 1 seems to be a low hanging fruit, for now.</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-644

Audit data collection for various events of OpenFlow plugin.

Improvement Medium Resolved Done Somashekhar Javalagi Kamal Rameshan neon-release Thu, 17 Mar 2016 19:36:18 +0000 Mon, 27 Sep 2021 09:01:45 +0000 Fri, 12 Jul 2019 06:19:51 +0000 Neon Sodium General 0 3 <p>Connection and disconnections statistics is possible to get through SessionStatistics (karaf console command show-session-stats). In all logs on the DEBUG level is used alwas the same pattern to identify device as "Device:'device name'". Session statistics or MessageSpy, can be enhanced. But need to know what information are needed. MessageSpy is also available in karaf console and in LOG by using DEBUG.</p> <p>This story is a good enhancement for the plugin, but it requires more grooming on what can be improved here and how to expose these statistics data.</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=Arunprakash" class="user-hover" rel="Arunprakash">Arunprakash</a> Can you please update the ticket with the details?</p> <ol> <li>Planning to define logger with a specified name (Ex: OfEventLogger) for openflowplugin, so that we can use this logger to log openflowplugin important events.</li> <li>We can develop a script which will modify karaf log configuration file(etc/org.ops4j.pax.logging.cfg) for configuring logger and appender for this.</li> <li>This script should make sure that these event logs are written into a separate file (ex: data\events\openflow), so that main events can be referred here.</li> <li>These main events can be following:<br/> (1) Openflow device connection/disconnection<br/> (2) OF Resync Start/Finish<br/> (3) Flow Count after Reconciliation<br/> (4) Node connector addition/deletion<br/> (5) Master Role Acquisition, etc</li> </ol> <p> </p> <p>Main events of openflowplugin can be logged using a separate common logger, which will be using log4j logging framework. This can be configured as a log appender in etc/org.ops4j.pax.logging file, through which we can redirect main openflowplugin event logs to a separate file. This can be helpful in debugging the problems with different phases of device connection to the SDN controller. The log appender can be configured as below in <span class="nobr"><a href="https://jira.opendaylight.org/secure/attachment/15018/15018_log_configuration.txt" title="log_configuration.txt attached to OPNFLWPLUG-644">log_configuration.txt^{<img class="rendericon" src="https://jira.opendaylight.org/images/icons/link_attachment_7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span></p> <p> </p> <p> </p> Development External issue ID 5551 External issue URL Issue Type Rank 0|i032fb: