User Tools

Site Tools


Writing /app/www/public/data/meta/resolution_area/prometheus_resolutions/res-p1103.meta failed
resolution_area:prometheus_resolutions:res-p1103

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
resolution_area:prometheus_resolutions:res-p1103 [2021/06/24 11:35] btobinresolution_area:prometheus_resolutions:res-p1103 [2021/07/05 11:25] (current) 10.91.120.28
Line 1: Line 1:
 +===== RemoteTicketFailedToCreate =====
  
 +**Level:** __Critical__ FIXME
 +
 +
 +**Purpose:**
 +Reports if a remote ticket creation has failed on RabbitMQ. If the ticket fails to create, it will be found in the remote.ticket.dead.letter.queue on RMQ. 
 +
 +**Scenario:** A remote ticket has failed to create. This can happen for a number of reasons. The exception can be found when getting the message from the dead letter queue. Steps can be found in the below link. The most common reason is that the ticket is being created on an orphan element and the remote ticket failed due to having no visibility.
 +
 +**Resolution:**
 +There are many different resolutions. If it's related to the orphan element, the queue will need to be purged and the customer notified that an orphan element is sending alarms to our system
 + 
 +**Manual Action Steps:** See http://wiki.err/doku.php?id=watchdogs:remoteticketfailedtocreate_-_rabbitmq
 +
 +
 +**Auto Clear:**
 +When the dead letter queue is purged