In the Edge "New Custom Report" GUI I am able to create a compound filter statement that appears like this:
(proxy_pathsuffix like '%delivery-windows') and (apiproxy eq 'Customers')
I am trying to do the same thing through an API call. I can set the "filter" argument to either of the conditions above and the call returns results, but if I use the full string above I receive a 500 - Internal Server Error. I'm not sure if the syntax is wrong or if there is something else going on, such as a timeout threshold being reached (I've noticed that the execution time in these cases tends to be very close to 30 seconds).
I haven't found anything in the online documentation that talks about compound filters, but I'm assuming it's possible since I can do it in the UI.
Hey @Mike Overholt -
This may be a bug. I've been able to reproduce the 500 with your compound filter, but I've also gotten successful calls with it. For example, I was able to get a successful API call when I changed
like in the second expression. Then, when I switched it back to
eq, which failed at first, it worked. I'll file a ticket. (UAP-609)