Abiquo 4.7 introduces changes to how events are managed on the platform and some improvements to the display of events in the user interface.
This feature includes changes to the Abiquo database, so the database upgrade may take a little longer than usual while it converts the events to the new format.
Abiquo 4.7.0 introduces changes to the data structure of the events streamed by the Outbound API (M module).
Update integrations that use the outbound event streaming API. For the new event format, see Trace entity.
The new version of the M module does not require a user in the database or Abiquo Configuration Properties to configure this user.
Previously the platform applied filters to the names of the entities but now the general filters will apply to all details of all entities.
In the Events view, the filter now has separate pull down menus for entities and actions, which makes it easier for users to find specific events.
Related events are tagged with a context ID. When you click on an Event, the platform will display the Context ID in the event details. To display all the related events, you can filter by Context ID.
Abiquo 4.7 enables customers to create custom VM tracers using a post request to the VM: POST “action/notification”, endpoint, which accepts a single message. A new event is published with EntityType: VIRTUAL_MACHINE EntityAction: NOTIFICATION Severity: INFO and Message: request message
Abiquo 4.7 introduces a new Events tab for virtual machines. Users can display the tab when they edit the VM.
To display the detail of an event, click on the event. To sort events on a column, click on the column header.