-
Notifications
You must be signed in to change notification settings - Fork 496
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
Support in-page-search in trace view on key=value pairs #1391
Conversation
a2c591f
to
345d2bc
Compare
I'm happy to add tests if this addition makes sense. |
a bit dirty (i.e. would also match on |
Overall the in-page search functionality is not very discoverable. When it was just a direct string match it was less of an issue, but if supporting a=b format it would be good to have some help tip somewhere. Q: in the backend search form we support multiple space-separated tag queries, would be nice to allow the same syntax for in-page search. I believe we even have a parser for the syntax in the UI. |
aefe32f
to
f785fec
Compare
Previously one could only filter on `key` or `value`. This wasn't useful when one needed to find spans with `result=false` in a trace view. With this change one can use `key=value` as a search term, for example: * `http.method=GET` Signed-off-by: Ivan Babrou <github@ivan.computer>
Signed-off-by: Ivan Babrou <github@ivan.computer>
f785fec
to
2ddc2b3
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #1391 +/- ##
==========================================
- Coverage 95.60% 95.58% -0.03%
==========================================
Files 244 244
Lines 7653 7657 +4
Branches 2006 2008 +2
==========================================
+ Hits 7317 7319 +2
- Misses 336 338 +2
☔ View full report in Codecov by Sentry. |
I added some tests for the Here's the tooltip I added in the second commit: Using the same syntax as the tag filter on the search page would mean that we lose |
@yurishkuro, any comments on the latest update? |
Signed-off-by: Yuri Shkuro <github@ysh.us>
To preclude certain key-value pairs from participating in the matching, prefix the key | ||
with the minus <code>'-'</code> sign, e.g., <code>-http.status_code</code>. | ||
</p> | ||
</div> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I rewrote the tooltip to make the explanation a bit more clear and to remove the styling applied to some key words which was difficult to read on the dark background.
Sorry it took a while to review, a busy month. |
…g#1391) Previously one could only filter on `key` or `value`. This wasn't useful when one needed to find spans with `result=false` in a trace view. With this change one can use `key=value` as a search term, for example: * `http.method=GET` Before (no matches): <img width="1231" alt="image" src="https://user-images.githubusercontent.com/89186/236012512-f97a67e8-8bf8-4372-b698-d0f34383b441.png"> After (a successful match): <img width="1231" alt="image" src="https://user-images.githubusercontent.com/89186/236012540-7c011a81-ca63-41d2-9051-cad4c5eab02e.png"> --------- Signed-off-by: Ivan Babrou <github@ivan.computer> Signed-off-by: Yuri Shkuro <github@ysh.us> Co-authored-by: Yuri Shkuro <github@ysh.us> Signed-off-by: RAMU MANAM <manam.ramu@uber.com>
Previously one could only filter on
key
orvalue
. This wasn't useful when one needed to find spans withresult=false
in a trace view.With this change one can use
key=value
as a search term, for example:http.method=GET
Before (no matches):
After (a successful match):