Implement local nProbe storage for Exported Flows
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 1.8k
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
It can happen that due to intermittent communications, nProbe is unable to export flows to the collector that are then lost. This ticket is to request the implementation of a mechanism for storing exported flows locally on the nProbe host so that they are reliably delivered to the remote ntopng instance. The goal is to guarantee that flows are not lost when connective problems happen.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how nProbe exports flows to the remote ntopng collector and where exported flows are handed off for delivery. Define the local storage, retry, ordering, and recovery behavior needed to prevent flow loss during intermittent communication, then validate delivery after connectivity returns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100