User Tools
Writing /app/www/public/data/meta/watchdogs/remoteticketfailedtocreate_-_rabbitmq.meta failed
watchdogs:remoteticketfailedtocreate_-_rabbitmq
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| watchdogs:remoteticketfailedtocreate_-_rabbitmq [2020/05/07 15:29] – pmurphy | watchdogs:remoteticketfailedtocreate_-_rabbitmq [2023/03/06 09:31] (current) – 10.91.110.100 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== RabbitMQ - RemoteTicketFailedToCreate ====== | ||
| + | |||
| + | Author: Eoin Hearne | ||
| + | |||
| + | A prometheus alert will come in similar to [FIRING:1] RemoteTicketFailedToCreate prodext (extlb1: | ||
| + | |||
| + | The interface for the RabbitMQ email queues can be found at loadbalancer: | ||
| + | Once logged in you will be presented with this interface. Click on the **Queues** tab. | ||
| + | {{ : | ||
| + | |||
| + | Then navigate to the **remote.ticket.dead.letter.queue**. The queue might be at the bottom of the multi page list, use the search bar if necessary. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | Scroll down the page and click on the **Get Messages** tab, then click the **Get Message(s)** button.** Make sure to use the 'Nack message requeue' | ||
| + | |||
| + | {{: | ||
| + | |||
| + | Please see example fail below.In this case the payload was missing the WORKFLOW parameter under ticketValues, | ||
| + | < | ||