| demx8as6 | aca16f7 | 2021-05-08 15:58:54 +0200 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 International License. |
| 2 | .. SPDX-License-Identifier: CC-BY-4.0 |
| 3 | .. Copyright (C) 2020 highstreet technologies and others |
| 4 | |
| demx8as6 | 53c4f57 | 2020-06-14 10:22:57 +0200 | [diff] [blame] | 5 | .. contents:: |
| 6 | :depth: 3 |
| 7 | .. |
| 8 | |
| 9 | Performance |
| 10 | =========== |
| 11 | |
| 12 | Performance Monitoring values measured by the devices are necessary to |
| 13 | analyze and optimize the network. Therefore the application |
| 14 | automatically retrieves all historical performance values from the |
| 15 | devices and stores them in a database. The client retrieves the values |
| 16 | from the database and displays them in a graphical user interface. |
| 17 | |
| 18 | Performance history values |
| 19 | -------------------------- |
| 20 | |
| 21 | After selecting a connected PNF supporting ONF-TR-532 and a physical |
| 22 | interface, the application collects the received and centralized stored |
| 23 | performance values for this interface. |
| 24 | |
| 25 | The values are visualized using two views: a line chart and a table, |
| 26 | with the chart always shown first. To switch between them, toggle |
| 27 | buttons can be used. The chart view offers a filter to quickly limit the |
| 28 | shown values. To keep both views in sync, the filters of the chart and |
| 29 | the table are connected. If one view is filtered, the other one gets |
| 30 | updated in the background. |