DRAFT
On the Anomaly Impact Deatils Details page, users gain insight into why & how AGILITY triggered each anomaly notification by delineating the anomaly’s unique information we received. The Anomaly Impact Details page allows you to drill down further into an anomaly's causes & impacts to expedite network resolution processes and gather knowledge to prevent similar anomalies from reoccurring.
How to Access the Anomaly Impact Details Page
To navigate to the Anomaly Impact Details to view the specifics of a particular anomaly:
Click the AGILITY icon.
You will be redirected to the AGLILITY home page.
Click the square icon.
The Domain Insights menu will expand.
Select "Radio Access Network".
You'll be redirected to the Radio Access Network (RAN) Domain Insights Dashboard. ( To access domain insights for a different domain, click on the desired Domain name from the Continuous Assurance menu. You'll be redirected to the applicable Domain Insights Dashboard.
| Info |
|---|
Default Filters: When the Dashboard is accessed through the menu, it automatically reflects the past 3 hours and 15 minutes of activity on the selected Network. |
5. Expand the row for the anomaly that you're investigating.
6. Select the View Details icon. You’ll be redirected to the Anomaly Details page.
...
Extracting Information from the Anomaly Details Page
Under the Anomlay Information headers header located at the beginning tell you what you are looking at Duration is the top of the page, you’ll find a synopsis of the anomaly’s origin and impact.
...
The Anomaly Information includes:
Start Date & Time: provides the start date and time at which the anomaly began.
Cell: provides the cell site identifier.
Site: provides the site ID
Network Layer: provides the domain
Duration: lists the amount of time that lapsed before anomaly recovery or the duration of time that the anomaly lasted.
Class: provides the anomaly classification
Anomaly Score: is back end score we use a score that is decided by our data scientist’s models & used to determine if the anomaly should be displayed - will be removed Detected on tells them when we discovered that there is an issue - when our AD model detected it - showing the latency for how long to users.
RCA: provides the Root Cause Analysis for the anomaly.
Detected on: provides the time at which AGILITY detected the anomaly. This detail demonstrates the latency for the amount of time it takes AGILITY to detect that there was an issue. Note that there can be a delay in the receipt of data from the customer, which contributes to the latency.
The Impacted KQIS (Key Quality Indicator Scores) Chart
The Impacted Key Quality Indicator Scores (KQIS) chart provides service impact details that help users identify the severity of the anomaly.
...
KQI Name:
Impacted QoE:
Value:
Service:
Current Impact:
See Trends:
Service data is at the top based on individual user KQIs key quality index reflected by user experience
- toggle button filter data volte
...
Current impact: the model computes the impact and tells you if it is low medium high or not available . No means it is not impacted there are three no, medium, high N/A means the data is not available
Service KQIS Trends: How to view the Impacted KQIs service trends
On the Anomaly Details page, go to the Imapcted KQIS chart.
Select the graph line icon from the SEE Trends column. The Service KQIS TREND data for the selected KQI will load.
See Trends:
cLICK ON THE sEE tRENDS icon to see the Service KQIS Trend Chaart
Auxillary data togle adds secondary data the secondary axix added on the right hand side adds data that lets you visualize the cause
Performance Management:
key performance indicators are network level performance level - second two tables PM KPIS
...
Importance : the inidcagti=or that was decided to trigger the anomaly numbers greater than zero indicate that this KPI was degraded and therefor triggered an anomaly . You will see dgredation in the chart if it is higher than 0
RAN Metrics Trend
FM Alarms
if we have an alarm on site it will trigger an anomaly based on the alarms right now we don't have an alarm . In some cases we do have an alarm. Example of cases with an alarm: https://oci-ad-dev.b-yond.com/ran/anomaly/c3818f35-a987-d578-aa66-58f7bcb3569c?restoreFilters=4bdbf827-75e0-4620-99d1-4b55ce3ebcba
...
Alarm type: sometimes it is not a KPI issue . Either an issue is a PM KPI or an FM Alarm Fault. Management PM performance Management
Anomaly Correlations
Anomlay Correlation : Anomaly correlation between anomalies that are all connected together. Ex there are several towers in a stadium, Tower a had an issue tower b & c had an issue and they were triggered separately, The correlator will bring these issues into one place to advise that here is a common issue happening on an area on a group of towers whether its on the same domain or a different domain ex. a router far away fro m the stadium has an issue and at the same time there was a problem on those sites. if we ave an anomaly in PS core and we notice that it is affecting towers , we connect them
...
its telling you the anomaly at these two sites is correlated
Impacted Subscriber Group Overview
IMPACTED SUBSCRIBER GROUPS OVERVIEW: change to impacted customer insight
...