What should I know about baseline and anomaly detector creation?
Baseline best practices
When baselines are configured, NSP creates a baseline with the parameter values for each resource selected. For example, if you want to collect baseline values for 20 ports with the same telemetry type, configure the Create Baselines parameters and NSP will create 20 baselines.
Bulk creation of baselines can take significant time and resources to complete. If the bulk creation process is interrupted by a network disruption or user action, it results in failed or partial creation.
If a baseline creation process has been interrupted by a network problem or user action (such as a page refresh), incorrect entries may exist in the database. Contact Nokia support.
Keep these suggestions in mind:
-
The collection interval configured in NSP is ignored by resources that are managed by NFM-P. Instead, the collection interval of resources managed by NFM-P is determined by the corresponding NFM-P MIB entry policy.
-
Use object filters in the Create Baselines form to target the resources you need; see How do object filters work?.
-
Avoid unfiltered baseline creation requests unless the network is limited in size.
-
If you configure the Convert to Bitrate parameter for a baseline counter and want to detect anomalies, set the Evaluate What parameter in the detector rule to Bandwidth. Using a different evaluation setting results in a mismatch between the Anomalies list in Visualizations and the baseline and anomaly chart generated for the baseline.
-
Ensure that you have enough time to wait for the creation operation to complete before configuring baseline creation.
The following table shows some average time frames for bulk baseline creation.
|
Number of baselines |
Average maximum time required |
|---|---|
|
100 |
30 s |
|
1000 |
3 min |
|
5000 |
15 min |
|
10 000 |
30 min |
Note: The baseline subscriptions are created last, therefore no statistics are collected for any baseline in the group until the bulk creation is completed.