Enhancing connection to server/IPFIX collector part of exporting process
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 52
- Forks
- 34
- Avg merge
- 9h 39m
- Merged PRs (30d)
- 7
Description
We do not wait for server/IPFIX collector when exporting process making a connection. We should probably do this connection in a goroutine and have a time out to fail.
In addition, if there is a connection reset, we should try connecting to collector again. This will be helpful in closing the connection gracefully with a timeout.
Contributor guide
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
Trace the exporter’s connection setup in the Go repository and inspect how it currently handles collector connections and shutdown. Define and verify the timeout, connection-reset retry, and graceful-close behavior described in the issue; done means those cases are covered and the existing test suite passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100