Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Configuration
    • There is one global configuration parameter:
      • alert.purge.delay - alerts older than specified number of days will be purged. Value set to 0 to never purge alerts automatically.
      • alert.purge.interval - interval  interval (in seconds) to wait before running the alert purge thread.

...

ApiName

Request parameters

Response parameters

Available to regular user

deleteAlert deleteAlerts

  • idids(can pass one or more IDs seperated by comma)
  • type
  • timeolderthan
  • true/false

No

archiveAlert archiveAlerts

  • idids(can pass one or more IDs seperated by comma)
  • type
  • timeolderthan
  • true/false

No

In the above mentioned APIs, id, type and time are olderthan are optional parameters but while calling the APIs atleast one APIs atleast one of them is required. Admin can pass one or multiple ids of alert to delete/archive them as per the requirement or if admin wants to delete/archive all the alerts of a particular category then he admin needs to pass only * type* parameter type parameter along with type value. If admin wants to delete/archive alerts older then some time then admin needs to pass time olderthan parameter. If admin passes any combination of parameters (two or all three) then CloudStack will fetch the alerts from database depends on the parameters and delete/archive only those alerts which satisfy this criteria.

New classes for client APIs

  • DeleteAlertCmdDeleteAlertsCmd.java
  • ArchiveAlertCmdArchiveAlertsCmd.java

Changes to Existing Files: 

...

ApiName

Request parameters

Response parameters

Available to regular user

deleteEvent deleteEvents

  •  id ids(can pass one or more IDs seperated by comma)
  • type
  • timeolderthan
  •  true/false

No yes

archiveEvent archiveEvents

  •  id ids(can pass one or more IDs seperated by comma)
  • type
  • timeolderthan
  • true/false

No yes

The APIs deleteEvent deleteEvents and archiveEvent archiveEvents will perform in the similar manner as of deleteAlert deleteAlerts and archiveAlertarchiveAlerts.

New classes for client APIs

  • DeleteEventCmdDeleteEventsCmd.java
  • ArchiveEventCmdArchiveEventsCmd.java

Changes to Existing Files:

  • Add new New methods in ManagementServerImpl.java to delete and archive alertsevents.
  • Add new New components in ManagementService.
  • New methods in EventDaoImpl to search and archive/delete events.

Logging and Debugging

All logs will go to management-server.log

...