Today the only way to search for a support id is it you know which LB its associated to, you drill down into the LB and set a filter for the req_id. In many cases, we're provided with "support IDs" for WAF blocks and asked to research to determine the issue. Our first task is to figure out which LB its associated with, which often means going back to the "customer" and asking them for more details such as the URL or which application they were working in so that we have enough context to determine the LB. Being able to search all LBs specifically for req_id would alleviate this step and allow our process to be a better experience for the end user that is being blocked.
Agree with the OP - It would be great to have a single pane of glass for global WAF blocks that can be filtered down as needed like with Silverline. A "workaround" at the moment is utilizing log-forwarding (for those that have that option) to identify and correlate the events, then jump to the portal for further detail.
Same situation as above. Users provide the Support ID, but not the specific site. Have to look in all namespaces, and all Load Balancers to find out which LB the Support ID is for!?