Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOC: <Issue related to /old/tracing/faq/querying_traces> #463

Open
MaxHoecker opened this issue Oct 8, 2024 · 1 comment
Open

DOC: <Issue related to /old/tracing/faq/querying_traces> #463

MaxHoecker opened this issue Oct 8, 2024 · 1 comment

Comments

@MaxHoecker
Copy link

In the UI I have a filter so that a run's input "does not match" a given string. But I'm having a difficult time figuring out how to replicate that via the sdk/rest api filter syntax.

Any updates to the docs to indicate how to do "matches" and "does not match" for a run's input with maybe even an example provided would be greatly appreciated

Thanks!

@MaxHoecker
Copy link
Author

realized I could determine it from the UI url. Figured out it was: notlike(inputs, "input string to not match")
seems like the "inputs" field and the "like" and "notlike" comparison operators should definitely be added to the docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant