...
...
| Table of Contents |
|---|
User documentation
Performance Monitoring values measured by the devices are necessary to analyze and optimize the network. Therefore, the application automatically retrieves all historical performance values from the devices and stores them in a database.
The “Performance History” Web Application displays the historical performance values of the device.
Specification
“Performance History” User Interface should be implemented to show the historical performance values of the devices stored in the database.
The model of the data is described in ONF-TR-532 - see xyz-historical-performances.
Below are the UI elements to be implemented.
- Drop-down Table to select a device from all the devices available in PM history database
connected device/networkElement. - Once the connected device is selected from the above drop-downtable, it should display the below two Dropdowns.
- Drop-down to ‘select the LTP’ associated with the selected device.
- Drop-down to ‘select the time period’ to show the performance values of the selected device (based on the time period 15min/24hrs)
After the selection of a connected device and LTP, the first LTP is automatically populated, the application collects the received and centralized stored performance values for the selected device from the database and displays them in the table views based on the time period selected. (15min/24hours). Time-period is 15min by default.
To differentiate the performance values of the devices based on different aspects of performance, below seven different accordions/panels tabs should be created with the respected data in its table view and in a chart.1)
- Performance Data
...
- Receive Level
...
- Transmission Power
...
- Adaptive Modulation
...
- Temperature
...
- Signal-to-interference-plus-noise ratio
...
- Cross Polar Discrimination
The table view implements the common ux-framework-table supporting sorting, filtering and pagination on the server. The chart is visualizing the data of the actual table page.The following panels shows the tables with its respective data
Visualization
Main window
Once the network element is selected, the below page is displayed.
The 'Performance Data' tab is selected as a default as well as the chart view.
The chart view offers a filter to quickly limit the displayed data.
The filter can be dis- or enabled via the 
button. As a default, the filter is always shown.
By clicking on the 
toggle button, the data is shown as a table and the filter toggle button is disabled, as the table itself has its own filter.
The filter in the chart view and the filter in the table are linked. Both views always show the same data.
Summary of functions:
- Each data is provided by its own section
- Each section contains a toggle view to switch between chart and table
- The data in the chart is the same as the data in the table
- For big amounts of data, both the chart and table are providing a filter function
- The number of table entries can be configured and/or filtered to show specific information
- The pagination provides a configuration of selecting the number of entries in the range of 5 to 50 in four steps
Data in the database
The performance values are stored on an ElasticSearch database.
The index is “historicalperformance15min” the doctype is
- “historicalperformance15min”- when time-period is selected as 15min (has past 15min performance data of the device)
The datta provider is provided by the REST.
Entity name to read the device list for 15min performance data is read-pmdata-15m-device-list,
Entity name to read the ltp list for 15min performance data is read-pmdata-15m-ltp-list
2.“historicalperformance24h”- when time-period is selected as 24hours (has past 24hours performance data of the device)
Entity name to read the device list for 15min performance data is read-pmdata-24h-device-list,
Entity name to read the ltp list for 15min performance data is read-pmdata-24h-ltp-list
Sections/ Tabs
The data in the tables varies based on the selected tab.
1) Performance Data
The “Performance Data” panel tab shows the table with the following columns:
...
2) Receive Level
The “Receive Level” panel tab shows the table with the following columns:
...
3) Transmission Power
The “Transmission Power” panel tab shows the table with the following columns:
...
The “Adaptive Modulation” panel tab shows the table with the following columns:
...
5) Temperature
The “Temperature” panel tab shows the table with the following columns:
...
The “Signal-to-interference-plus-noise ratio” panel tab shows the table with the following columns:
...
The “Cross Polar Discrimination” panel tab shows the table with the following columns:
- Radio Signal Id
- Scanner Id
- End Time
- Suspect Interval flag
- CPD min [db]
- CPD avg [db]
- CPD max [db]
The performance values are stored on an ElasticSearch database. The REST-API is provided by the ApiGateway.
The index is “sdnperformance” the doctype is
- “historicalperformance15min”- when time-period is selected as 15min (has past 15min performance data of the device)
- “historicalperformance24h”- when time-period is selected as 24hours (has past 24hours performance data of the device)
Charts
The charts should be introduced to show the performance values in as a line graph.
X axis: TimeStamp
Y axis: performance values
Example:
Data provider
The data is stored in an ElasticSearch database. The Data-Provider provides a REST-API to read the data.
- To get all devices
- having 15 minutes performance data: read-pmdata-15m-device-list
- having 24 hours performance data: read-pmdata-24h-device-list
- To get all ltps, which have
Implementation
...
- 15 minutes performance data: read-pmdata-15m-ltp-list
- 24 hours performance data: read-pmdata-24h-ltp-list
- To get all 15 minutes performance data: read-pmdata-15m-list
- to get all 24 hours performance data: read-pmdata-24h-list
Implementation
- GUI Framework: ONAP SDNR React framework
- Used components: react-chartjs-2
- Accessor for getting data from sdnr database / Elasticsearch→ via Elasticsearch: Rest API