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.

  1. Table to select a device from all the devices available in PM history database connected device/networkElement.
  2. Once the device is selected from the above table, it should display the below two Dropdowns.
    1. Drop-down to ‘select the LTP’ associated with the selected device.
    2. 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, 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, seven different tabs should be created with the respected data in its table view and in a chart.

  1. Performance Data
  2. Receive Level
  3. Transmission Power
  4. Adaptive Modulation
  5. Temperature
  6. Signal-to-interference-plus-noise ratio
  7. 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.

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

  1. “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” tab shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. ES
  6. SES
  7. UAS

2)  Receive Level

The “Receive Level” tab shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. Rx min
  6. Rx avg
  7. Rx max

3) Transmission Power

The “Transmission Power” tab shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. Tx min
  6. Tx avg
  7. Tx max

4) Adaptive Modulation

The “Adaptive Modulation” tab shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. col5-col36 – QAM2S,QAM2,QAM2L, QAM4S,QAM4,QAM4L, QAM16S,QAM16,QAM16L, QAM32S,QAM32,QAM32L, QAM64S,QAM64,QAM64L, QAM128S,QAM128,QAM128L, QAM256S,QAM256,QAM256L, QAM512S,QAM512,QAM512L, QAM1024S,QAM1024,QAM1024L, QAM2048S,QAM2048,QAM2048L, QAM4096S,QAM4096,QAM4096L, QAM8192S,QAM8192,QAM8192L,

5) Temperature

The “Temperature” tab shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. Rf Temp min [deg; C]
  6. Rf Temp avg [deg; C]
  7. Rf Temp max [deg; C]

6) Signal-to-interference-plus-noise ratio (SINR)

The “Signal-to-interference-plus-noise ratio” tab shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. SINR min [db]
  6. SINR avg [db]
  7. SINR max [db]

7) Cross Polar Discrimination

The “Cross Polar Discrimination” tab shows the table with the following columns:

  1. Radio Signal Id
  2. Scanner Id
  3. End Time
  4. Suspect Interval flag
  5. CPD min [db]
  6. CPD avg [db]
  7. CPD max [db]

Charts

The charts should be introduced to show the performance values 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
    • 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 via Elasticsearch: Rest API


  • No labels

2 Comments

  1. Rani Borusu

    Hi Aijana S / Sai Neetha Phulmali 

    Could you please help how to save data in historicalperformance15min-v6 or historicalperformance24h-v6 indexes. I am sending measurements(./oam/solution/dev/client-scripts-ves-v7/send15minPm.sh) to ves-collector and ves collector successfully sent event to onap-dmaap but I am not seeing any data in SDNR db for performance measurement events.

    could you please help me how to save data in sndr for performance measurement data.


    Thanks,

    Rani

  2. Herbert Eiselt

    Hi Rani Borusu ,

    SDNR is not supporting PM over VES. The visualized PM data are requested by devicemanagers via NETCONF and pushed by this component to the SDNR database. 

    Martin Skorupski is there a plan to add this functionality?

    Thanks for asking,
    Herbert