Filter
Top Products
Chapter 22. Troubleshooting
252
Configuration
As a CloudPlatform administrator, perform the following one-time configuration to enable event
notification framework. At run time no changes can control the behaviour.
1. Open 'componentContext.xml.
2. Define a bean named eventNotificationBus as follows:
• name : Specify a name for the bean.
• server : The name or the IP address of the RabbitMQ AMQP server.
• port : The port on which RabbitMQ server is running.
• username : The username associated with the account to access the RabbitMQ server.
• password : The password associated with the username of the account to access the RabbitMQ
server.
• exchange : The exchange name on the RabbitMQ server where CloudPlatform events are
published.
A sample bean is given below:
<bean id="eventNotificationBus"
class="org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus">
<property name="name" value="eventNotificationBus"/>
<property name="server" value="127.0.0.1"/>
<property name="port" value="5672"/>
<property name="username" value="guest"/>
<property name="password" value="guest"/>
<property name="exchange" value="cloudstack-events"/>
</bean>
The eventNotificationBus bean represents the
org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus class.
3. Restart the Management Server.
22.1.3. Standard Events
The events log records three types of standard events.
• INFO. This event is generated when an operation has been successfully performed.
• WARN. This event is generated in the following circumstances.
• When a network is disconnected while monitoring a template download.
• When a template download is abandoned.
• When an issue on the storage server causes the volumes to fail over to the mirror storage server.
• ERROR. This event is generated when an operation has not been successfully performed
22.1.4. Long Running Job Events
The events log records three types of standard events.