bug: OTEL traces are broken #1086
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#1086
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: #2968
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2968
Original created: 2026-03-01T07:40:06Z
Describe the bug
In the stats cards we're showing 0 traces, in the observability/traces page, stats cards say same thing, in the list of traces though we see the last one showing up on 2/21 (today is 3/1), so it seems like they stopped coming in, not sure how/why.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
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: @marvin-hansen
Original URL: https://github.com/carverauto/serviceradar/issues/2968#issuecomment-3979515479
Original created: 2026-03-01T08:50:23Z
is that related to the Rust / otel crate?
I am working on refactoring this one in the rust-fix branch
Imported GitHub comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2968#issuecomment-3979559464
Original created: 2026-03-01T09:19:52Z
Not sure yet need to triage still
Imported GitHub comment.
Original author: @marvin-hansen
Original URL: https://github.com/carverauto/serviceradar/issues/2968#issuecomment-3979603576
Original created: 2026-03-01T09:53:57Z
Okay, let me wrap up the current Rust fix , build & test and then I fill a
PR later tonight which you can review and merge. That way, I can keep
working on the non OTEL crates without meddling with your but fixing
On Sun, Mar 1, 2026 at 17:20 Michael Freeman @.***>
wrote:
Imported GitHub comment.
Original author: @marvin-hansen
Original URL: https://github.com/carverauto/serviceradar/issues/2968#issuecomment-3979605535
Original created: 2026-03-01T09:55:28Z
I mean bug fixing... The only thing that seems never to happen to iphone
autocorrect..
On Sun, Mar 1, 2026 at 17:53 Marvin Hansen @.***> wrote:
Imported GitHub comment.
Original author: @marvin-hansen
Original URL: https://github.com/carverauto/serviceradar/issues/2968#issuecomment-3979900808
Original created: 2026-03-01T12:49:14Z
The merger of the otel crate is blocked by the fact that I cannot get the target build with Bazel because of some wonky target in the Bazel config that only exists for a Docker image file... Details in the Bazel Discord channel. The TLDR is that I try to get this resolved tomorrow and then I hope I can get a full build and test run so that I can fill the PR.
Imported GitHub comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2968#issuecomment-4145507596
Original created: 2026-03-27T21:45:12Z
i believe this is fixed, closing.. we can re-open if necessary