DX OI - incidents are created but DOI console still shows the “Open ticket” option rather than the incident number

book

Article ID: 193262

calendar_today

Updated On:

Products

DX Operational Intelligence

Issue/Introduction

For some alarms, incidents are created but DOI console still shows the “Open ticket” option rather than the incident number, here is an example:

 

1.In OI UI:

 

2.In Kibana:

 

3.Incident is also found when querying the Alarm in Elastic:

{ES-Endpoint}/*alarms_all*/_search?pretty&size=100&sort=timestamp:desc&q=alarm_unique_id:<alarm-id>

 

4.Open Chrome Dev Tools (press F12), click “Open ticket” below error is observed: " Incident is already created for this alarm”

Cause

The issue is related to defect DE457521

Environment

DIGITAL OPERATIONAL INTELLIGENCE - 1.3.2

Resolution

Contact Broadcom Support to obtain a copy of the fix.


Installation instructions :

1. Scale down doi-readserver and doi-adminui only. DOI UI will not be accessible during that time ( 500 internal server error will appear if users try to connect), there will be NO data loss
2. tar -xvf readserver-doionprem.tar.gz
3. cd readserver-doionprem/
4. docker load --input readserver-doionprem.tar
5. docker images | grep isl-dsdc.ca.com:5001
6.  docker tag isl-dsdc.ca.com:5001/doi/1.3.2.1/readserver-doionprem:release <private-registry-hostname>:5000/1.3.2/readserver-doionprem:release
7. docker push <private-registry-hostname>/1.3.2/readserver-doionprem:release
8. oc import-image readserver-doionprem:release
9. Scale up doi-readserver and doi-adminui 

 

Additional Information

DX OI - Troubleshooting, Common Issues and Best Practices
https://knowledge.broadcom.com/external/article/190815/dx-oi-troubleshooting-common-issues-and.html

Attachments