DOCS-1755 - Document Search Assist Filter - #6933
Conversation
Add a "Filter results from a column" section to the results-table doc covering the column filter icon, string/number operators, and limitations, with a screenshot. Add a service release note announcing the feature. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Applying a filter updates the query with a where clause but does not refresh results automatically; you click search to run the updated query. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
kimsauce
left a comment
kimsauce
left a comment
There was a problem hiding this comment.
Nice addition — clear steps and consistent with the existing doc structure. Left a few inline notes: the screenshot doesn't currently show the filter panel described in the text (and has internal host/cluster names visible, which you already flagged), the operator list needs SME confirmation, and one terminology tweak for consistency with the rest of the file. None of these block merging in my view once the image is swapped for a masked/polished capture — approving.
|
|
||
| To filter results from a column: | ||
|
|
||
| 1. Run a search. In the **Messages** tab, click the filter icon in the header of the column you want to filter.<br/><img src={useBaseUrl('img/search/get-started-search/search-page/search-assist-filter.png')} alt="Filter icon and filter panel on a search results column" style={{border: '1px solid gray'}} width="800" /> |
There was a problem hiding this comment.
I pulled this image from the branch to check it — it's an annotated demo capture with red boxes/arrows labeling "String fields" and "Number fields" over the filter icons. It doesn't actually show the filter panel, operator dropdown, or Top 10 values list that the next two steps describe, so the alt text ("Filter icon and filter panel on a search results column") overstates what's shown. It also has internal host/cluster identifiers visible (e.g. epd_dev1_cluster, org-service-5fc5b766b6-697nz) — matches what you flagged in the PR description. Worth replacing with a masked capture that shows the actual filter panel before publish.
| - **String fields**. Select an operator such as **Text contains**, **Text does not contain**, or **Text starts with**, then enter a value. You can also select a value from the **Top 10 values** list, which shows the most common values in the column with their approximate counts. | ||
| - **Number fields**. Select an operator such as **Greater than**, **Less than**, or **Equal to**, then enter a value. |
There was a problem hiding this comment.
Per the PR notes, these operator lists are phrased "such as" because they reflect only what the demo showed.
| - **String fields**. Select an operator such as **Text contains**, **Text does not contain**, or **Text starts with**, then enter a value. You can also select a value from the **Top 10 values** list, which shows the most common values in the column with their approximate counts. | ||
| - **Number fields**. Select an operator such as **Greater than**, **Less than**, or **Equal to**, then enter a value. | ||
| 1. Click **Apply**. Sumo Logic adds the filter to your query as a `where` clause (for example, `| where _size > 1000`). | ||
| 1. Click the search button to run the updated query. |
There was a problem hiding this comment.
This file uses Start everywhere else for running/re-running a query (e.g. two lines up in this same doc: "click Start (or press Enter/Return) to run the appended search"). Suggest matching that here for consistency:
| 1. Click the search button to run the updated query. | |
| 1. Click **Start** (or press Enter/Return) to run the updated query. |
3 participants
Purpose of this pull request
This pull request documents the new Search Assist Filter, which lets you filter search results directly from a results-table column instead of manually typing a filter clause. It adds a "Filter results from a column" section to the results-table doc (covering the filter icon, string/number operators, the Top 10 values picker, and current limitations), a supporting screenshot, and a service release note.
Notes for reviewers:
Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-1755