During one of our recent request analyses, we encountered latency issues affecting our onboarded applications. These applications rely on APIs that invoke backend services based on parameters such as policy number, claims, and trace ID from the ASW load balancer.

We observed that F5 XC currently does not provide a feature to filter logs using specific identifiers like policy number or trace ID. This limitation makes it challenging for us to pinpoint the exact API calls experiencing latency issues, thereby impacting our troubleshooting efficiency.

Due to the absence of such filtering capabilities, extracting precise logs for problematic API requests has become difficult and time-consuming.

We kindly request you to consider enhancing F5 XC’s logging functionality by introducing filters that allow searching based on:

• Policy number

• Trace ID

• Request payload or other custom parameters

This feature would significantly improve our ability to diagnose and resolve performance issues more effectively.

We appreciate your support and look forward to your response.