The Events view allows users to find out what is happening on the platform. 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 the panel below the Event list, double-click on an Event.
Depending on user privileges, you may not be allowed to view events, or you may be able to view events for your tenant. If the events you expected to display do not appear in Events view, check with your System Administrator. Event attributesAn event has the following attributes: Attribute | Description |
|---|
Entity | The system object that is the source of the event or error. For example, it could be a VIRTUAL_APPLIANCEfor 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. | | Action | The action that generated the event, for example, DELETE. See Events Table | Performed by | The user who performed the Action, for example, admin. | | Severity | The severity of the event. Can be INFO, WARN or ERROR | Date/time | The date and time when the event was generated. | Message | 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 | | Context | The identifier of a group of related events. This attribute is in the event detail but not in the event list. |
Event contextWhen 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 eventsTo make it easier to find a specific event, use the filter tool. Click the filter button  at the top right of Events view. Enter your filter criteria and click Accept. To remove the filter, click Clear at the bottom of the popup. When events are filtered, the text (events filtered) will be displayed next to the filter button. | Event field | Description |
|---|
| Entity | Pull-down list of Entities | | Action | Pull-down list of Actions | | Entity name | The name of the entity. The Name field may contain the UUID or the friendly name of the entity | | Severity | Pull-down list of event severity. See Events View#Severity table | | User | The name of the user who performed the action | | Enterprise | The tenant that the event occurred in | | Date from | Calendar selection for start date in format YYYY/MM/DD | | Date to | Calendar selection for end date in format YYYY/MM/DD | | Message | The message field will contain the details of the event, including the friendly name. See Events Table |
Examples of events filterTo 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 the events related to an event, select the Event from the list, copy the Context ID and filter by Context.
Severity tableEvents on the Abiquo platform are classified into three severity categories: info, warning and error. Severity | Description |
|---|
INFO | General information events for the user as part of the normal use of the platform | WARNING | Warning about an abnormal situation that does not block normal use of the platform | ERROR | Error that blocks the normal use of the platform |
Events tableThe 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.
|