Yury Molodov

> @Loori-R Can comfirm that with the Select component everything works. @archef2000 Would you mind replacing `Combobox` with `Select`?

> Already on it It looks like there are still some `Combobox` components in the code: https://github.com/VictoriaMetrics/victorialogs-datasource/pull/329/files#diff-35151418f87b2fad4cd2f8e9b4515cd9685e1c922d771a348463efc8672b15ecR12-R22

> This query should give me the value types of `ClientPort` right? `/select/logsql/field_values?query=_msg%3A*+%7C+uniq+by+ClientPort+%7C+block_stats+%7C+uniq+type&start=1751839200000&end=1752011999999&field=type` > > query: `_msg:* | uniq by ClientPort | block_stats | uniq type` field: `type` Not sure,...

Seems like the query won’t return `ClientPort` types — it just gets unique `type` values from logs matching the full `query` as a text filter, because `/field_values` doesn’t run the...

I don't quite understand what you're trying to achieve. For the expression: `_msg:* | uniq by ClientPort | block_stats | uniq type` `/fields_values` can only be used for `_msg` (I'm...

Maybe we could just hardcode the supported value types (like `const`, `dict`, `string`, `int64`, `float64`, etc.) and allow users to enter a custom type if needed - that might be...

> I described just an example and asked to move all the handlers from the component to the handlers. I would suggest extracting only complex logic - for example, if...

> So looks like we can hide fields in other tabs, and as for me it doesn't make sense to do the same thing here. And you are right about...

FYI: This doesn't completely resolve the issue but can help improve the behavior. Source: [paul.ren/note/2024-288](https://paul.ren/note/view/2024-288) ``` ... ```

@jicki Click the ‘Group by query…’ header to expand the accordion. When a group contains more than 20 items, the accordion is collapsed by default.