...
...
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.
| Table of Contents |
|---|
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.
...
The table view implements the common ux-framework-table supporting sorting, filtering and pagination on the server. The chart is visualing the data of the actual table page.
Visualization
Main window
One section with table and chart
...
Overview for one data entry, showing the table and the chart.
Data in the database
The performance values are stored on an ElasticSearch database. The REST-API is provided by the ApiGateway.
...
- “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)
Sections/ Panels
The following panels shows the tables with its respective data.
...
- Radio Signal Id
- Scanner Id
- End Time
- Suspect Interval flag
- CPD min [db]
- CPD avg [db]
- CPD max [db]
Charts
The charts should be introduced to show the performance values in a line graph.
...
Y axis: performance values
Example:
Implementation
- GUI Framework: ONAP SDNR React framework
- Used components: react-chartjs-2
- Accessor for getting data from sdnr database via Elasticsearch-Rest API