Issue description

Possible causes

• Exporting reports containing too many entries without filters.
• Inefficient report configuration, such as including inappropriately long time periods or irrelevant log types.
• Direct bulk exports from the browser consume significant memory and I/O resources.
• Report data stored in Java memory takes time to transfer to file storage, especially for large batches.

Prerequisites  

• You have access to the EventLog Analyzer web interface.
• You possess the necessary permissions to generate, schedule, or modify reports as a technician.
• System resources (CPU, RAM, Disk I/O) are not already under heavy usage by the EventLog Analyzer server.

Resolution

Step 1: Limit export scope

• Select a specific time period and include only the necessary columns in the report.
• Fine-tune the filter criteria and choose only the relevant log types to reduce report size.
  

Step 2: Schedule reports instead of direct export

• For large or recurring exports, use the Report Scheduler to automate data exports.
• Schedule exports during non-business hours to avoid performance degradation.

Step 3: Avoid browser-based bulk exports

• Exporting a high volume of reports through a browser can consume large memory chunks (up to 20,000 records per batch), leading to processing delays.
• Use scheduled or segmented exports for better performance and reduced load.

Validation and testing

• Measure the time taken for export before and after applying optimizations.
• Monitor system resource usage during the export to confirm improvement.
• Check the exported file to ensure completeness and accuracy.

Tips

• Use filters proactively to restrict report size.
• Avoid exporting reports containing all available fields unless necessary.
• Consider archiving and exporting older logs separately from active data.