bug(dire): not de-duplicating agents #982

New issue

Closed

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

mfreeman451 commented

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

Owner

Imported from GitHub.

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

Describe the bug

Our agents are getting turned into new device records everytime their k8s pod IP address changes. We should be able to easily reconcile device records from agents since they provide a strong identifier, the unique agent name or ID. I'm not sure if the agent ID stuff actually exists but we may want to consider setting one when we onboard an agent or first see an agent, not sure how it would persist on the agent side, we could embed it in the onboarding token but what about agents that have already been onboarded? Not sure where the agent would keep this either and what would happen if the end-user re-installed the agent or wiped the server?

We only have two agents in the system, one running in k8s in the cluster. (k8s-agent) and another agent-dusk running on 192.168.2.22

Instead we're showing 3 agents running in here, two with 10 net addressing obviously indicating they are coming from our k8s cluster.

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

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):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Imported from GitHub. Original GitHub issue: #2758 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2758 Original created: 2026-02-10T00:06:57Z --- **Describe the bug** Our agents are getting turned into new device records everytime their k8s pod IP address changes. We should be able to easily reconcile device records from agents since they provide a strong identifier, the unique agent name or ID. I'm not sure if the agent ID stuff actually exists but we may want to consider setting one when we onboard an agent or first see an agent, not sure how it would persist on the agent side, we could embed it in the onboarding token but what about agents that have already been onboarded? Not sure where the agent would keep this either and what would happen if the end-user re-installed the agent or wiped the server? <img width="1175" height="373" alt="Image" src="https://github.com/user-attachments/assets/c1cd7bd9-e844-4a00-998f-f4d4f220a4c4" /> We only have two agents in the system, one running in k8s in the cluster. (k8s-agent) and another agent-dusk running on 192.168.2.22 Instead we're showing 3 agents running in here, two with 10 net addressing obviously indicating they are coming from our k8s cluster. **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **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):** - OS: [e.g. iOS] - Browser [e.g. chrome, safari] - Version [e.g. 22] **Smartphone (please complete the following information):** - Device: [e.g. iPhone6] - OS: [e.g. iOS8.1] - Browser [e.g. stock browser, safari] - Version [e.g. 22] **Additional context** Add any other context about the problem here.

mfreeman451 commented

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

Author

Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2758#issuecomment-3875227293
Original created: 2026-02-10T04:18:16Z

closing, fixed

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2758#issuecomment-3875227293 Original created: 2026-02-10T04:18:16Z --- closing, fixed