
8lz1q (8lz1q) asked a question.
I have found myself in multiple situation when querying logs, where I know what I did not want to see but there was no visible way to get this. Additionally if you do not have an exact case match, you will not get any hits on queries.
I need to find all the request in an IP chain but currently you can only get if you already know what is present.
request.ipChain.geographicalContext.country eq "Russia"
This above log queury should be case insensitive and I should be able to perform request.ipChain.geographicalContext.country neq "Russia" or "not eq" so I can exclude what is not needed. I realize this would be a performance issue for Okta, however functionality should also be a high consideration for the administrators.
Am I not using the filter correctly? Is this a non-obvious features or one that is coming. It is sorely needed.
https://developer.okta.com/docs/api/getting_started/design_principles*filtering

Can confirm "not equals" is not an available operator. Looks like there's an existing post in the "Ideas" section of the Help Center:
https://support.okta.com/help/s/idea/0872A000000XbCaQAK/detail
I just voted on it. You should do the same! Cheers!