Fill gaps from assistant conversations: Insights filter scopes - #247
mintlify[bot] wants to merge 1 commit into
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
|
|
||
| Insights supports two filter scopes, and where you click determines which one you get: | ||
|
|
||
| - **Inline filter (per metric):** Click the event or behavior inside a specific metric card, then add the filter there. The filter applies only to that metric, so you can filter one metric while leaving other metrics in the same report unfiltered. |
There was a problem hiding this comment.
The existing Filters documentation says inline filters are added through the … menu beside a query item. Directing readers to click the event or behavior may open its selector instead, leaving them unable to find the per-metric filter control.
| - **Inline filter (per metric):** Click the event or behavior inside a specific metric card, then add the filter there. The filter applies only to that metric, so you can filter one metric while leaving other metrics in the same report unfiltered. | |
| - **Inline filter (per metric):** Click the **…** icon beside the event or behavior inside a specific metric card, then add the filter there. The filter applies only to that metric, so you can filter one metric while leaving other metrics in the same report unfiltered. |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
There was a problem hiding this comment.
I agree, we could phrase it as "click on the options menu next to the event/metric (the ... icon beside it)" and then add the filter there".
There was a problem hiding this comment.
Agreed — that wording is clearer and points readers to the actual control. I’d use:
- Inline filter (per metric): Click the options menu next to the event or metric (the ... icon beside it), then add the filter there. The filter applies only to that metric, so you can filter one metric while leaving other metrics in the same report unfiltered.
Tip: You can customize Greptile's behavior for this repo with .greptile/rules.md and .greptile/config.json.
|
|
||
| Insights supports two filter scopes, and where you click determines which one you get: | ||
|
|
||
| - **Inline filter (per metric):** Click the event or behavior inside a specific metric card, then add the filter there. The filter applies only to that metric, so you can filter one metric while leaving other metrics in the same report unfiltered. |
There was a problem hiding this comment.
I agree, we could phrase it as "click on the options menu next to the event/metric (the ... icon beside it)" and then add the filter there".
|
2 participants
Summary
Clarify in the Insights doc that filters can be scoped per metric (inline) or applied to the whole report (global), so readers can filter one metric without affecting others.
Changes
docs/reports/insights.mdx: In Step 3 (Choose Filters), added a short breakdown of inline vs global filter scopes and a link to the general Filters section.Context
Assistant conversations show users trying to apply a filter to only one metric in an Insights report and mistaking the report-level Filter button for a per-metric control. The distinction was already documented on the general Reports page but not surfaced from the Insights walkthrough.