Abiquo 5.2

Skip to end of metadata
Go to start of metadata

The Events view allows users to see what is happening in Abiquo


To open the Events view, click on the Events icon  in the main menu bar. To add new events as they arrive, select the Update automatically checkbox. Otherwise, you must refresh the list manually. To display the event details in a separate panel, double-click on an event. 

Privilege: Display all events for current enterprise, Display all events, Allow user to switch enterprises

Event viewing can be restricted using privileges assigned to user roles. Users can have: no event privileges; the Display all events for current enterprise privilege; and/or the Display all events privilege. Users with no event privileges will not see the Events icon or the Events window in the Home view. 

The default cloud User and the default Enterprise Admin role have the Display all events for current enterprise. The default Cloud Admin role has the Display all events privilege.

Event attributes

An event has the following attributes:




The system object that is the source of the event or error. For example, it could be a VIRTUAL_APPLIANCE for a group of virtual machines.

Entity name

The name of the system object that is the source of the event or error, for example, myVirtualAppliance.

ActionThe action that generated the event, for example, DELETE. See Events Table

Performed by

The user who performed the Action, for example, admin.

SeverityThe severity of the event. Can be INFO, WARN or ERROR


The date and time when the event was generated.


Additional information about the event. See Events Table for more details. The traces displayed in Events view are also found in the Logs, which are documented in the Troubleshooting section of the Abiquo Administrator's Guide. See Abiquo Logs, especially catalina.out 

ContextThe identifier of a group of related events. This attribute is in the event detail but not in the event list.

Event context

When you view the event detail, the platform will display the context of the event. The context is an ID that the platform assigns to each event in a group of related events. For example, if you undeploy a virtual appliance, the platform will create events for the undeploy of each VM, the destruction of the related hard disks, and the release of the NICs. And the platform will assign the context ID to each of these events. You can filter by context to display this group of events.

Filtering events

To make it easier to find a specific event, use the filter tool. Click the funnel filter button at the top right of Events view. Enter your filter criteria and click Accept. To remove the filter, click Clear atthe bottom of the popup.

When events are filtered, the text (events filtered)  will be displayed next to the filter button.

Event fieldDescription
EntityPull-down list of Entities
ActionPull-down list of Actions
Entity nameThe name of the entity. The Name field may contain the UUID or the friendly name of the entity
SeverityPull-down list of event severity. See Severity table
UserThe name of the user who performed the action
EnterpriseThe tenant that the event occurred in
Date fromCalendar selection for start date in format YYYY/MM/DD
Date toCalendar selection for end date in format YYYY/MM/DD
MessageThe message field will contain the details of the event, including the friendly name. See Events Table

Examples of events filter

To filter alarm events by name, enter the friendly name of the alarm in the "Message" field of the filter. Note that the Name field contains the UUID of the alarm.

To display all events related to an event, select the event, copy the context ID and filter by context.

Severity table

Events on the Abiquo platform are classified into three severity categories: info, warning and error. 




General information events for the user as part of the normal use of the platform


Warning about an abnormal situation that does not block normal use of the platform


Error that blocks the normal use of the platform

Events table

The Events Table describes all the actions that can be performed on each entity and the event that they can generate on the platform. For example, for the Action plan entity, you can perform the Create, Modify and Delete actions, and events will also be generated when you run an action plan.

Outbound API

Abiquo streams events using the Outbound API or M module. See Abiquo Outbound API

  • No labels