| | 4 | |
| | 5 | The GENI monitoring alerts system is based on the detection of events based on metric data that polled from remote systems. As part of the polling process raw data is both recorded in a database and pushed to a queue. The queue serves as a fanout interface for a one-to-many raw metric subscription service. |
| | 6 | |
| | 7 | [[Image(https://www.rabbitmq.com/img/tutorials/python-three-overall.png)]] |
| | 8 | |
| | 9 | In the previous figure ''P'' represents our polling agent, which publishes data to a queue exchange represented by ''X''. Clients, designated as ''C1'' and ''C2'', subscribe to exchanges by binding their own queues to exchanges. In the example, data published by ''P'' is replicated by ''X'' to client queues ''amq.gen-RQ6..'' for client ''C1'' and ''amq.gen-As8...'' for client ''C2''. |
| | 10 | |
| | 11 | |
| | 12 | Alert data is obtained are based on a publish/subscribe queuing system that allows for pattern-based (matching) subscriptions. State transition and utilization will be emitted on this queue. |
| | 13 | |
| | 14 | |
| | 15 | |
| | 16 | |
| | 17 | *Queue images are from RabbitMQ tutorials [https://www.rabbitmq.com/tutorials/tutorial-three-python.html] |
