feat(core): keep track of discovery/sweep events #602

New issue

Closed

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

mfreeman451 commented

2026-03-28 04:26:17 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #1862
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1862
Original created: 2025-10-23T02:43:15Z

Is your feature request related to a problem?

We currently don't have visibility outside of OTEL or by manually reviewing application logs, when a discovery or network sweep event has occured. We would know if we read the configs as well, as to when they SHOULD be occuring.

Describe the solution you'd like

When a network discovery / sweep occurs, the core learns about it as it receives the results of those operations. It should also be able to create an event like we do if a poller goes down/recovers, that would be visible in the UI. This also would allow us to show a history of previous discovery events and a summary of their findings.

For sync operations that perform an update to armis/netbox/other integration, we should create an event for that as well, with the success/fail status and a summary of the update.

Since the sweep.json config lives in the KV, and soon the rest of all of the configs will live in the KV as well, we should be able to check in the KV to also enrich the event with the current desired configuration state, for example:

The sync.json is configured to run the 'armis' integration every 3 hours, and do a discovery every 2 hours. We should be able to record in the event that the discovery occured as planned, or if a scheduled discovery didn't run for some reason.

The event should be enriched with all of the related intervals related to the discovery/sweep/scanner service by reading them from the KV if available. This is contingent on #1861 but we can still implement it before that is finished.

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: #1862 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/1862 Original created: 2025-10-23T02:43:15Z --- **Is your feature request related to a problem?** We currently don't have visibility outside of OTEL or by manually reviewing application logs, when a discovery or network sweep event has occured. We would know if we read the configs as well, as to when they SHOULD be occuring. **Describe the solution you'd like** When a network discovery / sweep occurs, the core learns about it as it receives the results of those operations. It should also be able to create an event like we do if a poller goes down/recovers, that would be visible in the UI. This also would allow us to show a history of previous discovery events and a summary of their findings. For sync operations that perform an update to armis/netbox/other integration, we should create an event for that as well, with the success/fail status and a summary of the update. Since the `sweep.json` config lives in the KV, and soon the rest of all of the configs will live in the KV as well, we should be able to check in the KV to also enrich the event with the current desired configuration state, for example: The sync.json is configured to run the 'armis' integration every 3 hours, and do a discovery every 2 hours. We should be able to record in the event that the discovery occured as planned, or if a scheduled discovery didn't run for some reason. The event should be enriched with all of the related intervals related to the discovery/sweep/scanner service by reading them from the KV if available. This is contingent on #1861 but we can still implement it before that is finished. **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 commented

2026-03-28 04:26:17 +00:00

Author

Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1862#issuecomment-3813920884
Original created: 2026-01-28T21:03:17Z

closing, completed

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/1862#issuecomment-3813920884 Original created: 2026-01-28T21:03:17Z --- closing, completed