Is your feature request related to a problem? Please describe
Users frequently write an exact field filter on a field that is actually a stream field. This is much slower than using a stream filter, but users do not see it: the stream vs non-stream distinction is an internal concept for devops and for VictoriaLogs.
The people operating VictoriaLogs are mostly devops, but the people actually reading logs are mostly engineers, and to them this distinction is pure friction. Related: #1077.
Describe the solution you'd like
In the Web UI (and the Grafana plugin for logs), while the user is typing a query and adds a filter on some field, run a background check whether that field is a stream field for the selected time range.
If so, show a non-intrusive hint (or green tip) next/below to the filter, such as "this field may be a stream field", with a clickable action that rewrites the filter into a stream filter.
Describe alternatives you've considered
No response
Additional information
No response
Is your feature request related to a problem? Please describe
Users frequently write an exact field filter on a field that is actually a stream field. This is much slower than using a stream filter, but users do not see it: the stream vs non-stream distinction is an internal concept for devops and for VictoriaLogs.
The people operating VictoriaLogs are mostly devops, but the people actually reading logs are mostly engineers, and to them this distinction is pure friction. Related: #1077.
Describe the solution you'd like
In the Web UI (and the Grafana plugin for logs), while the user is typing a query and adds a filter on some field, run a background check whether that field is a stream field for the selected time range.
If so, show a non-intrusive hint (or green tip) next/below to the filter, such as "this field may be a stream field", with a clickable action that rewrites the filter into a stream filter.
Describe alternatives you've considered
No response
Additional information
No response