- 23 Oct, 2014 40 commits
-
-
Thomas Vachuska authored
-
Madan Jampani authored
-
- Added hosts to test data. - Messed with colors and icons. - Added more internal configuration values.
Simon Hunt authored -
Thomas Vachuska authored
-
Thomas Vachuska authored
-
* Use the new class EventMetric to cleanup and simplify the implementation * Replaced the single metric for Topology Events with four metrics (last event timestamp and event rate): - Device Event metrics - Host Event metrics - Link Event metrics - Topology Graph metrics Change-Id: I2acc06ab84ef3ca06d0d383983dfcff9774ff341
Pavlin Radoslavov authored -
rate and last event timestamp (ms from epoch) Change-Id: Ifce6c2ca911f3b288a0efd9061befc936d06da51
Pavlin Radoslavov authored -
- IMap#get usually returns clone of original value, but when the type is byte[], it returns the original value. - During the deserialization process, Kryo temporarily modifies the input buffer, which may cause problem when multiple threads were reading the same value. - applying clone only to value deserialization for now, since it is unlikely that caller will be modifying Map key Change-Id: I52214ba711b4060663b0e1c451f49bdd1d472ea9
Yuta HIGUCHI authored -
Madan Jampani authored
-
Madan Jampani authored
-
Thomas Vachuska authored
-
Thomas Vachuska authored
-
It can be used as an Intent-related event and event metrics collector. It can be loaded by one of the following two (new) features: onos-app-metrics, onos-app-metrics-intent After loading the module, it subscribes for intent-related events and keeps the following state: (a) The last 100 events (b) The timestamp of the last event (ms after epoch) as observed by this module for each event type: SUBMITTED, INSTALLED, WITHDRAWN. The missing event type is the equivalent of "Withdraw Requested" (c) The rate of each intent event type: count, median rate, average rate over the last 1, 5 or 15 minutes The following CLI commands are added: * onos:intents-events Shows the last 100 intent events * onos:intents-events-metrics Shows the timestamp of the last event (ms after epoch) as observed by this module for each event type, and the rate of the topology events (for each event type): see (b) and (c) above Change-Id: I9f23e9086bbd433b8f24283539abdeb97e199e2e
Pavlin Radoslavov authored -
Devices, Hosts, Links, TopologyEvent Now the semantics for updating the metrics are: * Any topology-related event (DeviceEvent, HostEvent, LinkEvent, TopologyEvent) will update the Lost Topology Event Timestamp * Only the DeviceEvent, HostEvent and LinkEvent will be counted in measuring the event rate; TopologyEvent is excluded, because it is generated as a result of some of those events Also, increased the number of saved events from 10 to 100. Change-Id: Ie759ee69869cddc617d7ad5b8b75a622e2571620
Pavlin Radoslavov authored -
Thomas Vachuska authored
-
Thomas Vachuska authored
-
Fixed the optical config json file. Fixed treatment of links added by ancillary providers. Added a trap for topology provider errors. Added CLI to recompute topology.
Thomas Vachuska authored -
AbstractEvent.toString() This method is needed so we can display the port as well (when set). Change-Id: I35af68ccb4a63602de40a904a6cee0cfe5f4985f
Pavlin Radoslavov authored
-