I would like to request that the column structure of CSV log exports in F5XC be fixed and made consistent.

In F5XC, the columns included in CSV log downloads can change depending on the timing of the export. When exporting logs to CSV and opening them in Excel, the column layout may differ between files. For example, the column named “signature” may appear in column G in one CSV file, but move to column BM in another file generated at a different time.

According to F5 Support, this behavior is by design, as certain security events may or may not include specific keys (such as signature). While I understand this design rationale, having log fields dynamically change their positions causes significant issues for log aggregation, analysis, and reporting.

This problem becomes even more serious for logs forwarded via the Global Log Receiver, where field positions vary widely, making it impossible to effectively use Excel’s filtering functionality.

For operational log analysis and data processing, a stable and fixed column definition is essential. I strongly request that the CSV log output format be improved so that column order and field positions remain consistent across exports.