Citrix Systems 4.2 manual Event Log Queries, Deleting and Archiving Events and Alerts

Event Log Queries

•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.5. Event Log Queries

Database logs can be queried from the user interface. The list of events captured by the system includes:

•Virtual machine creation, deletion, and on-going management operations

•Virtual router creation, deletion, and on-going management operations

•Template creation and deletion

•Network/load balancer rules creation and deletion

•Storage volume creation and deletion

•User login and logout

22.1.6. Deleting and Archiving Events and Alerts

CloudPlatform provides you the ability to delete or archive the existing alerts and events that you no longer want to implement. You can regularly delete or archive any alerts or events that you cannot, or do not want to resolve from the database.

You can delete or archive individual alerts or events either directly by using the Quickview or by using the Details page. If you want to delete multiple alerts or events at the same time, you can use the respective context menu. You can delete alerts or events by category for a time period. For example, you can select categories such as USER.LOGOUT, VM.DESTROY, VM.AG.UPDATE, CONFIGURATION.VALUE.EDI, and so on. You can also view the number of events or alerts archived or deleted.

In order to support the delete or archive alerts, the following global parameters have been added:

•alert.purge.delay: The alerts older than specified number of days are purged. Set the value to 0 to never purge alerts automatically.

•alert.purge.interval: The interval in seconds to wait before running the alert purge thread. The default is 86400 seconds (one day).

Note

Archived alerts or events cannot be viewed in the UI or by using the API. They are maintained in the database for auditing or compliance purposes.

253