bug(agent): checker requests #760
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#760
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: #2331
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2331
Original created: 2026-01-18T05:31:27Z
Describe the bug
Not sure why we are seeing these, this is what we would have expected to see if the poller (which is now completely removed/deprecated) were reaching down and out to the agent for status from these external checkers. The new model is the agent pushes everything up to it, and any external checker that the agent used to reach out to, now has to also push up to the agent. We are moving as much as we can into the
serviceradar-agentservice itself (anything written in golang that gets deployed in the edge) but there still might be some edge cases, either way, these messages in the logs don't make sense and I'm not sure where they are coming from. We also see something reporting statuses for a bunch of services to the core-elx, it presumably also comes from this.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: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2331#issuecomment-3765123067
Original created: 2026-01-18T09:59:37Z
closing as completed