feat: normalize IP enrichment data into common schema #1077

New issue

Open

opened 2026-03-28 04:31:27 +00:00 by mfreeman451 · 0 comments

mfreeman451 commented

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

Owner

Imported from GitHub.

Original GitHub issue: #2956
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2956
Original created: 2026-03-01T01:46:57Z

Is your feature request related to a problem?

I believe we have separate schemas to store MMDB, IPInfo, and cloud provider enrichment databases, these should all just be consolidated into one common format/one schema, merge in duplicates etc.

There are quite a few places that rely on this data so if we move it we'll have to make sure we update topology view and MTR and others.

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: #2956 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2956 Original created: 2026-03-01T01:46:57Z --- **Is your feature request related to a problem?** I believe we have separate schemas to store MMDB, IPInfo, and cloud provider enrichment databases, these should all just be consolidated into one common format/one schema, merge in duplicates etc. There are quite a few places that rely on this data so if we move it we'll have to make sure we update topology view and MTR and others. **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.