umputun/dkll

TCP syslog writer should redial on connection lost (agent)

Open

#10 opened on Aug 4, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (2 forks)github user discovery
help wanted

Repository metrics

Stars
 (69 stars)
PR merge metrics
 (PR metrics pending)

Description

In case if dkll server failed/restarted and communication between agent and server is non-default tcp, agent writers can lose connection quietly. It has a repeater, but this one is on the dial stage only. and works on new container event.

Contributor guide

Research direction
Inspect the syslog writer implementation in the agent and add a reconnection mechanism with exponential backoff for TCP connections.
Tech stack
go
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75