Features/netflow V10 bpg support #2925
No reviewers
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!2925
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/2925/head"
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 pull request.
Original GitHub pull request: #2841
Original author: @mikemiles-dev
Original URL: https://github.com/carverauto/serviceradar/pull/2841
Original created: 2026-02-15T19:03:06Z
Original updated: 2026-03-16T04:11:03Z
Original head: mikemiles-dev/serviceradar:features/netflow-bpg
Original base: staging
Original merged: 2026-03-16T04:11:03Z by @mfreeman451
IMPORTANT: Please sign the Developer Certificate of Origin
Describe your changes
Extending Netflow Collector to Ingest V10 BGP Fields, Pipeline, Testing, and UI changes.
Issue ticket number and link
Code checklist before requesting a review
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2810067539
Original created: 2026-02-15T22:59:19Z
Original path: cmd/consumers/netflow-ingestor/main.go
Original line: 1
check out the Broadway (elixir) stuff there, there is an EventWriter.Producer that is sending messages to NATS JetStream should be a similiar pattern for Consumers
https://github.com/carverauto/serviceradar/blob/staging/packaging/zen/rules/netflow_to_ocsf.json
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2810068532
Original created: 2026-02-15T23:00:09Z
Original path: pkg/api/netflow_bgp_handler.go
Original line: 1
this seems like it was built around the old golang API, need to re-do this in web-ng where the new API is
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2810068962
Original created: 2026-02-15T23:00:33Z
Original path: pkg/consumers/netflow-ingestor/service.go
Original line: 1
should be able to replace this with an elixir
Broadwaybased consumerImported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2810069818
Original created: 2026-02-15T23:01:14Z
Original path: pkg/db/cnpg_netflow.go
Original line: 26
I think all of these changes in
pkg/dbcan be dropped and we just move this all into Elixir/Broadway and re-use existing Elixir models/schemaImported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2810070504
Original created: 2026-02-15T23:01:52Z
Original path: pkg/models/netflow.go
Original line: 37
need to find the Elixir model and update that instead I think
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2810071175
Original created: 2026-02-15T23:02:29Z
Original path: rust/netflow-collector/src/converter.rs
Original line: 729
should these tests be in their own file?
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2810074295
Original created: 2026-02-15T23:05:02Z
Original path: go.sum
Original line: 203
I'm guessing we can remove this as well
Imported GitHub PR review comment.
Original author: @mikemiles-dev
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2810114486
Original created: 2026-02-15T23:37:06Z
Original path: rust/netflow-collector/src/converter.rs
Original line: 729
I can, not uncommon for rust to put tests on bottom of files as well.
Imported GitHub PR review comment.
Original author: @mikemiles-dev
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2810116948
Original created: 2026-02-15T23:38:40Z
Original path: rust/netflow-collector/src/converter.rs
Original line: 729
The #[cfg(test)] pattern is specifically designed for this use
case. Rust developers expect to find unit tests at the bottom of the source file.
The only reason to move them would be if:
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2848728987
Original created: 2026-02-24T17:57:17Z
Original path: elixir/serviceradar_core/lib/serviceradar/bgp/as_lookup.ex
Original line: 14
i wonder if we could tie this into our ipinfo/geoip databases to lookup against their data instead of this table
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2848809651
Original created: 2026-02-24T18:15:05Z
Original path: elixir/serviceradar_core/lib/serviceradar/bgp/as_lookup.ex
Original line: 129
do we need this if we already have an ASN lookup database from ipinfo?
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2848817963
Original created: 2026-02-24T18:16:53Z
Original path: elixir/serviceradar_core/lib/serviceradar/application.ex
Original line: 81
see previous comment about ASN lookups using ipinfo/geomax db
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2848829840
Original created: 2026-02-24T18:19:41Z
Original path: web-ng/assets/js/app.js
Original line: 1876
this might be a little ugly to merge in here, i would synchronize this branch against staging here (pull in latest changes) because app.js has been completely refactored, this stuff will just need to go into its own file/directory or whatever (we split app.js up and it is bare bones now as it should be)
Imported GitHub PR review comment.
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2841#discussion_r2848838297
Original created: 2026-02-24T18:21:32Z
Original path: elixir/web-ng/lib/serviceradar_web_ng_web/router.ex
Original line: 348
should this be a new view or should it live under observability?