feat(web-ng): add search bars in observability views #989

New issue

Open

opened 2026-03-28 04:30:35 +00:00 by mfreeman451 · 0 comments

mfreeman451 commented

2026-03-28 04:30:35 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #2767
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2767
Original created: 2026-02-10T06:57:32Z

Is your feature request related to a problem?

We should put a search bar in each logs/traces/metrics/netflow view so users can easily filter by IP addresses or CIDR Blocks. This search bar would be tied to the SRQL query builder as well, so if you changed something in there, it should update your query in SRQL.

There is plenty of room to add it into the 'Log Stream' card header, same with traces tab, metrics, events, alerts, netflow there is less room, but we could still put it in there on a new line

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

Imported from GitHub. Original GitHub issue: #2767 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2767 Original created: 2026-02-10T06:57:32Z --- **Is your feature request related to a problem?** We should put a search bar in each logs/traces/metrics/netflow view so users can easily filter by IP addresses or CIDR Blocks. This search bar would be tied to the SRQL query builder as well, so if you changed something in there, it should update your query in SRQL. <img width="1181" height="77" alt="Image" src="https://github.com/user-attachments/assets/97754e4f-6f18-41c3-b27c-289b9d057b7d" /> There is plenty of room to add it into the 'Log Stream' card header, same with traces tab, metrics, events, alerts, netflow there is less room, but we could still put it in there on a new line **Describe the solution you'd like** A clear and concise description of what you want to happen. **Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered. **Additional context** Add any other context or screenshots about the feature request here.