What is Analytics?

Overview

Analytics generates reports and dashboard views of network conditions using raw and aggregated data collected in the NFM-P. Raw data is used for evaluating current conditions; aggregated data helps to identify patterns and trends. The available aggregation levels vary by report type, and are selectable using the Granularity drop-down menu in the input prompt panel; for example, Hourly, Daily, or Monthly.

Analytics also generates reports from data collected using NSP telemetry. The NSP reports differ from the NFM-P reports by including data from the NFM-P and MDM (model-driven Nokia or multivendor NEs).

Before you can create a report or dashboard based on aggregated data, you must enable and configure aggregation for the required statistics using the NFM-P Aggregation Manager; see How do I configure analytics aggregation?.

For NSP reports for MDM-mediated NEs, you must enable aggregation. Aggregation rules are configured on the NSP component, and can be viewed and edited in the Data Collection and Analysis Management, Aggregation view; see the NSP Data Collection and Analysis Guide and the Telemetry information on the Network Developer Portal.

Before you can create a report or dashboard based on data stored in the auxiliary database, you must use the samconfig utility, as described in the NSP Installation and Upgrade Guide, to enable and configure the following:

Caution 1: Some reports use a variety of statistics or data types. All data must be collected using the same collection interval; otherwise, the report generation fails or produces erroneous results.

Caution 2: Due to a security limitation, if a user is created in the NFM-P to access Analytics, the user name cannot be samuser.

Object limits in Analytics reports

You can select the 1000 objects that you want by entering comma-separated names for report input prompts with % searches in their text boxes. For example, you can specify the 1000 objects that you want by entering comma-separated names, such as “%135.250%,%MSS%,%40.71%”, in the Name or name pattern for NEs report input prompt, or any other text box with % searches, including NE names, Port-LAG, port names, interface, service, SAP, and customer.

When reporting is required for more than 1000 objects, you can filter using report prompts to generate multiple reports. Reports in the Comprehensive chapter (see Chapter 11, Comprehensive reports), do not implement the 1000 object limit, and permit reporting limited only by the available system resources. These reports may take longer to render, or may fail due to insufficient resources. In such cases, use the report prompts to reduce the number of selected objects. Alternatively, you can create an ad hoc report without the 1000 object limit, or contact Nokia professional services to create a custom report.

Analytics Data Dictionary

To ensure optimal reporting performance, a subset of network and service objects (for example, subscribers, services, ports) is copied from the main NSP database to the auxiliary database. This data is also kept in sync by the Analytics framework for all object create, update, and delete operations. To ensure that no such operations are missed, the data dictionary is periodically resynchronized and is entirely rebuilt every 30 days. This data is used to populate prompts in reports and are available for use in ad hoc reports. Since deleted objects are retained for up to 30 days, they may still appear in reports, depending upon the report design. If deleted objects are not desired in the report output, they can be omitted by excluding them using the report prompts.

Analytics API support

NSP Analytics functions are available for OSS using programmable APIs. For general information about developer support, see the Network Developer Portal. For API documentation, see the API documentation page.

Server requirements

To accommodate the significant NFM-P Analytics data throughput, storage, and analysis requirements, an NFM-P system requires the following components:

See the NSP Planning Guide for specific information about the NFM-P system requirements for Analytics, based on the managed network size, functional requirements, and deployment scope.

Browser requirements

If an adBlocker extension is in use, it may block some files in Analytics. To use Analytics with an adBlocker extension, add the NSP component and analytics server IP addresses to the whitelist.

Network domains for Application Assurance reports

Analytics supports Application Assurance reports for residential, business, Wi-Fi, and fixed wireless access subscribers. If needed, the network domain can be selected from the Domain drop-down menu in the input prompt panel.

Note: The use of “mobile” in this document implies fixed wireless access.

The domains are defined by the value of the Subscriber Type parameter in the AA Subscriber form, the Subscriber Scale parameter in the ISA AA group policy, or both:

The following table describes the reports available for each domain.

Table 1-1: Application Assurance reports available by domain

Report type

Residential/Wi-Fi (ESM)

Business

Wi-Fi (DSM)

Mobile

Business Subscribers

None

All

None

None

Devices and Domains

All

All

All

All

Firewall

None

All

None

All

Location and Congestion

None

None

All

All

Mobile Subscribers

None

None

None

All

Nodes

All

All

All

All

Performance

All

All

All

All

Subscribers

All

None

None

None

Baselining in Analytics reports

Some reports support the use of baselining. Baselining highlights deviations for the current period from the baseline data collected in the configured baseline period.

Note: Baselining in Analytics reports is different from baselines as seen in the Data Collection and Analysis Management, Baselines view.

In an analytics report, NSP computes a baseline for data configured for reporting, for example, utilization and throughput for a port in a Port LAG Details report, or bandwidth and data for an application group in a Router Level Usage Summary report with Baseline.

A baseline configured in Data Collection and Analysis Management, Baselines provides near-real-time trend and anomaly detection from telemetry counters, for example, received-octets for the /telemetry:base/interfaces/interface telemetry type.

For more information about baselines in Data Collection and Analysis Management, see the NSP User Guide and the NSP Data Collection and Analysis Guide .

The following table describes how baseline data is presented.

Report granularity

Baseline definition

Baseline composition

Raw

Raw + Hour of Day

Baseline is composed of all data points in the Baseline Report Range for matching intervals to the hour and minute for any day of the week.

For example if May 15 14:05 is in the Report Range, and the Baseline Report Range is April 1 00:00 - April 30 11:59, the baseline minimum, maximum, and average values are based on the 30 samples from 14:05 for every day of April. The same baseline calculation is made for other data points in the Report Range.

Raw + Hour of Day + Day of Week

Baseline is composed of all data points in the Baseline Report Range for matching intervals to the hour and minute for the corresponding day of the week.

In the above example, the baseline has 4 or 5 samples depending on the day of the week (as each day occurs 4 or 5 times per month).

Hourly

Hour of Day

Baseline is composed of all data points in the Baseline Report Range for matching hours for any day of the week.

For example, if May 15 14:00 is in the Report Range, and the Baseline Report Range is April 1 00:00 - April 30 11:59, then the baseline minimum, maximum, and average values are based on the 30 samples from 14:00 for every day of April. The same baseline calculation is made for other data points in the Report Range.

Hour of Day + Day of Week

Baseline is composed of all data points in the Baseline Report Range for matching hours for the corresponding day of the week.

In the above example, the baseline has 4 or 5 samples depending on the day of the week (as each day occurs 4 or 5 times per month).

Hour of Day + Day of Month

Baseline is composed of all data points in the Baseline Report Range for matching hours for the corresponding day of the month.

In the above example, the baseline has 1 sample (note: a longer Baseline Report Range is recommended).

Daily

Day of Week

Baseline is composed of all data points in the Baseline Report Range for matching days of the week.

For example, if May 15 is in the Report Range, and the Baseline Report Range is January 1 00:00 - April 30 11:59, the baseline minimum, maximum, and average values are based on the 17 or 18 samples for every day in those 4 months.

Day of Week + Month of Year

Baseline is composed of all data points in the Baseline Report Range for matching hours for the corresponding day of the week for the matching months.

In the above example, the baseline has 4 or 5 samples for each of the months of January-April.

Day of Month

Baseline is composed of all data points in the Baseline Report Range for matching days of the month.

In the above example, the baseline has 4 samples for the 15th day of January-April.

Day of Month + Month of Year

Baseline is composed of all data points in the Baseline Report Range for the matching days and months of the year.

In the above example, the baseline is empty as May 15th does not occur (a different Baseline Report Range is required).

Monthly

Month of Year

Baseline is composed of all data points in the Baseline Report Range for matching months.

For example, if May is in the Report Range, and the Baseline Report Range is January 1 2020 - December 31 2022, the baseline minimum, maximum, and average values are based on the 3 samples for every month of May between 2020-2022.

Analytics report branding

Some reports support the inclusion of logos. If a logo image is added to the report it appears at the top of each report page, in an 80 x 80 pixel square. Images can be saved to the application client computer or to the analytics server. See How do I upload images for report branding? for information about managing image files from Analytics, or “To manage images on an analytics server” in the NSP System Administrator Guide for information about managing image files on an analytics server.