In 22.1.3 and later versions, there has been significant changes done to the Events processing on Avi. One of the major change is the Events API 3.0 which includes the consolidation of events for many processes and better file name formatting for easy log rotation and file management to help reduce disk usage.
In prior versions, each process will generate its own event file based on timestamp and pid. When certain processes (such as portal) restart frequently, a huge amount of event files will be generated and each one has a quite small size. This will cause log manager spending longer time to process all the files state and cause log query timeouts for loading events/logs.
The events created across the system for the processes are stored as event log files in /var/lib/avi/logs/ALL-EVENTS folder in the fileformat such as, log_event_adf_ALL-EVENTS_XXX_portal_<pid>.XXX. The new fileformat in 22.1.3-2p3 and later would look like log_event_adf_ALL-EVENTS_XXX_portal_idx1.XXX. This new naming strategy is done for 4 major processes that are frequently restarted [‘portal’, ‘analyticsportal’, ‘maintenanceportal’, ‘systemportal’]
Some of the symptoms are:
Controller version prior to 22.1.3 or upgraded from version prior to 22.1.3 may carry over the old format event-files
All events files with names portal_<pid>, analyticsportal_<pid>, maintenanceportal_<pid>, systemportal_<pid> needs to be deleted from /var/lib/avi/logs/ALL-EVENTS/controller-xxx folder on all controller nodes
Steps to follow:
Dry run: find /path/to/folder -type f -name '*portal*' -not -name '*portal_idx*'
Delete: find /path/to/folder -type f -name '*portal*' -not -name '*portal_idx*' -delete