Correct Access & Security Log inconsistencies

We are having issues with parsing access and security logs in our SIEM because of the inconsistent fields included in log messages. If a field in the log has no value, it is not included at all. Please create consistent log messages for access and security types with null or blank value instead of forgoing field inclusion.


Sample access & security requests highlighting this can be provided on request.

  • Guest
  • Feb 9 2024
Console / API
  • Attach files
  • Guest commented
    9 Feb 01:24am

    Related internal f5 support request #406496