Major Description
For 4.9, we have decided to update AMQP support to allow for monitord to publish events to AMQP Server
The AMQP url format will follow the naming scheme that online monitoring in kickstart uses
amqp://[USERNAME:PASSWORD@]amqp.isi.edu[:port]/<virtualhost>/<exchange_name>
The monitoring code will not create any exchanges or job queues automatically, as that requires admin privileges in RabbitMQ
The exchange to which we will populate as mentioned in properties, will be of type topic
type -> topic
durable -> True
auto_delete -> False
The Queue associated with the exchange has to be created by the user separately via the rabbit mq interface
Routing Keys
the routing key should be based on stampede event names. All events have workflow uuid in them
Events populated
https://pegasus.isi.edu/documentation/stampede_wf_events.php
We should add periodic events about states of workflows
SWIP integrity error events will be populated by clients
The AMQP url format will follow the naming scheme that online monitoring in kickstart uses
amqp://[USERNAME:PASSWORD@]amqp.isi.edu[:port]/<virtualhost>/<exchange_name>
The monitoring code will not create any exchanges or job queues automatically, as that requires admin privileges in RabbitMQ
The exchange to which we will populate as mentioned in properties, will be of type topic
type -> topic
durable -> True
auto_delete -> False
The Queue associated with the exchange has to be created by the user separately via the rabbit mq interface
Routing Keys
the routing key should be based on stampede event names. All events have workflow uuid in them
Events populated
https://pegasus.isi.edu/documentation/stampede_wf_events.php
We should add periodic events about states of workflows
SWIP integrity error events will be populated by clients
