bug(ui): observability/logs no longer lets you select a service #593
Labels
No labels
1week
2weeks
Failed compliance check
IP cameras
NATS
Possible security concern
Review effort 1/5
Review effort 2/5
Review effort 3/5
Review effort 4/5
Review effort 5/5
UI
aardvark
accessibility
amd64
api
arm64
auth
back-end
bgp
blog
bug
build
checkers
ci-cd
cleanup
cnpg
codex
core
dependencies
device-management
documentation
duplicate
dusk
ebpf
enhancement
eta 1d
eta 1hr
eta 3d
eta 3hr
feature
fieldsurvey
github_actions
go
good first issue
help wanted
invalid
javascript
k8s
log-collector
mapper
mtr
needs-triage
netflow
network-sweep
observability
oracle
otel
plug-in
proton
python
question
reddit
redhat
research
rperf
rperf-checker
rust
sdk
security
serviceradar-agent
serviceradar-agent-gateway
serviceradar-web
serviceradar-web-ng
siem
snmp
sysmon
topology
ubiquiti
wasm
wontfix
zen-engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
carverauto/serviceradar#593
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Imported from GitHub.
Original GitHub issue: #1844
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1844
Original created: 2025-10-22T04:57:30Z
Describe the bug
After we replaced SRQL this functionality stopped working, you should see a list of known services that you can select and filter by when viewing logs.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Since the
serviceradar-coreis already basically collecting a list of services that have reported into it (flush.go / flushServices), we should be able to read from that list and then populate the web ui drop-down, then users can filter by services and we don't have to parse raw data to figure that all out.We need to do this through /api/query, this should already be supported since we have "in:services" defined in the SRQL system.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
Imported GitHub comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1844#issuecomment-3441014898
Original created: 2025-10-24T04:34:07Z
Restored the Observability › Logs service picker by querying via /api/query, added a parser util + vitest coverage, and redeployed ghcr.io/carverauto/serviceradar-web:sha-18e47406ac39 to demo.
Imported GitHub comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1844#issuecomment-3441015543
Original created: 2025-10-24T04:34:16Z
Restored the Observability Logs service picker by querying in:services via /api/query, added a parser utility with vitest coverage, and redeployed ghcr.io/carverauto/serviceradar-web:sha-18e47406ac39 to the demo namespace.
Imported GitHub comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1844#issuecomment-3441087960
Original created: 2025-10-24T05:11:30Z
Added shared service selector component, canonical service mapping/aliases, and wired the picker into Observability → Logs and Traces; deployed ghcr.io/carverauto/serviceradar-web:sha-ce492b7935fd to demo.