feat: refactor external checkers #801

New issue

Closed

opened 2026-03-28 04:28:41 +00:00 by mfreeman451 · 1 comment

mfreeman451 commented

2026-03-28 04:28:41 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #2402
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2402
Original created: 2026-01-20T05:02:37Z

Is your feature request related to a problem?

Historically, serviceradar-poller called down to serviceradar-agent and the agent would call out (this is all over GRPC) to an external checker for some information (status, results, etc). The agent collects the information and sends it back to the poller, the poller forwarded it to the core. Our new architecture is much different, the agent lives in the edge typically and talks to nothing, all of the old external GRPC checkers written in golang have been consolidated/merged into serviceradar-agent proper, and only a few of the original external GRPC checkers remain. Instead of making some complicated interaction between these external checkers and the agent and the agent-gateway, we should just refactor these external GRPC checkers to communicate directly to the agent-gateway, emulating the behavior of the agent with GRPC Hello calls and getting config, pushing status/results, etc directly to the gateway.

remove dusk checker from serviceradar-agent, make standalone again

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: #2402 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2402 Original created: 2026-01-20T05:02:37Z --- **Is your feature request related to a problem?** Historically, `serviceradar-poller` called down to `serviceradar-agent` and the agent would call out (this is all over GRPC) to an external checker for some information (status, results, etc). The agent collects the information and sends it back to the poller, the poller forwarded it to the core. Our new architecture is much different, the agent lives in the edge typically and talks to nothing, all of the old external GRPC checkers written in golang have been consolidated/merged into `serviceradar-agent` proper, and only a few of the original external GRPC checkers remain. Instead of making some complicated interaction between these external checkers and the agent and the agent-gateway, we should just refactor these external GRPC checkers to communicate directly to the agent-gateway, emulating the behavior of the agent with GRPC Hello calls and getting config, pushing status/results, etc directly to the gateway. - [ ] remove dusk checker from serviceradar-agent, make standalone again **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.

mfreeman451 added this to the 1.1.1 milestone

2026-03-28 04:28:41 +00:00

mfreeman451 commented

2026-03-28 04:28:41 +00:00

Author

Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2402#issuecomment-3971506345
Original created: 2026-02-27T08:24:11Z

closing, completed

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2402#issuecomment-3971506345 Original created: 2026-02-27T08:24:11Z --- closing, completed

mfreeman451 closed this issue

2026-03-28 04:28:42 +00:00