ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

what determines when an alarm alarm_unique_id changes

book

Article ID: 226015

calendar_today

Updated On:

Products

DX OI SaaS DX APM SaaS DX Application Performance Management DX Operational Intelligence

Issue/Introduction

we have observed that when an alert is sent from APM via OI to the webhook channel the same alarm_unique_id is used 

what are the rules around how the alarm_unique_id is resused or a new one created?

The below is a webhook alert generated form an alarm which came from APM - the bold section labeled EventId is the ${alarm_unique_id}
 
EventDate: 2021-04-26T06:40:15+0000
AlertGroup: SuperDomain|ibnbld004162|Infrastructure|Agent|MIKE|URLS|/myurl/donkey:g 
EventId: 764529.dxi-na1.saas.broadcom.com-bbcde611-51d4-4902-a571-2cdca3a0fd87-ibnbld004162
Severity: major
Summary: The alert COOMI06-RBS-URLS has breached the MAJOR threshold of 1

Environment

Release : SAAS

Component :

Resolution

If an alert is triggered against metric A then that gets an alarm_unique_id and that alarm_unique_id stays the same if the alert status for that metric fluctuates between caution and danger (major and critical)
 
Once either metric value drops down below the caution threshold  so that a normal alert is triggered that is the last time that alarm_unique_id is used and if the metric subsequently triggers a new caution or danger alert then it has a new alarm_unique_id as can be seen in the below sequence

 

EventDate: 2021-10-12T09:35:15+0000  
AlertGroup: SuperDomain|ibnbld004162|Infrastructure|Agent|MIKE|URLS|/myurl/donkey:g 
EventId: 764529.dxi-na1.saas.broadcom.com-0eaf2e57-964b-4f1d-9fd3-0484e998d883-ibnbld004162  
Severity: critical 
Summary: The alert COOMI06-RBS-URLS has breached the CRITICAL threshold of 75

EventDate: 2021-10-12T09:35:30+0000  
AlertGroup: SuperDomain|ibnbld004162|Infrastructure|Agent|MIKE|URLS|/myurl/donkey:f 
EventId: 764529.dxi-na1.saas.broadcom.com-111abd62-5a41-46f8-a1ca-ccb3067b70ec-ibnbld004162  
Severity: major 
Summary: The alert COOMI06-RBS-URLS has breached the MAJOR threshold of 49

EventDate: 2021-10-12T09:37:15+0000  
AlertGroup: SuperDomain|ibnbld004162|Infrastructure|Agent|MIKE|URLS|/myurl/donkey:f 
EventId: 764529.dxi-na1.saas.broadcom.com-111abd62-5a41-46f8-a1ca-ccb3067b70ec-ibnbld004162  
Severity: critical
Summary: The alert COOMI06-RBS-URLS has breached the CRITICAL threshold of 75

EventDate: 2021-10-12T09:37:30+0000  
AlertGroup: SuperDomain|ibnbld004162|Infrastructure|Agent|MIKE|URLS|/myurl/donkey:g 
EventId: 764529.dxi-na1.saas.broadcom.com-0eaf2e57-964b-4f1d-9fd3-0484e998d883-ibnbld004162  
Severity: major 
Summary: The alert COOMI06-RBS-URLS has breached the MAJOR threshold of 49
   
EventDate: 2021-10-12T09:38:15+0000  
AlertGroup: SuperDomain|ibnbld004162|Infrastructure|Agent|MIKE|URLS|/myurl/donkey:g 
EventId: 764529.dxi-na1.saas.broadcom.com-0eaf2e57-964b-4f1d-9fd3-0484e998d883-ibnbld004162  
Severity: critical 
Summary: The alert COOMI06-RBS-URLS has breached the CRITICAL threshold of 75

EventDate: 2021-10-12T09:38:30+0000  
AlertGroup: SuperDomain|ibnbld004162|Infrastructure|Agent|MIKE|URLS|/myurl/donkey:f 
EventId: 764529.dxi-na1.saas.broadcom.com-111abd62-5a41-46f8-a1ca-ccb3067b70ec-ibnbld004162  
Severity: information 
Summary: The alert COOMI06-RBS-URLS is normal

EventDate: 2021-10-12T09:39:15+0000  
AlertGroup: SuperDomain|ibnbld004162|Infrastructure|Agent|MIKE|URLS|/myurl/donkey:f 
EventId: 764529.dxi-na1.saas.broadcom.com-72ea55df-d305-408d-b535-e7aeec410345-ibnbld004162  
Severity: critical 
Summary: The alert COOMI06-RBS-URLS has breached the CRITICAL threshold of 75