Rsyslog for containers that are destroyed and recreated regularly
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
We have a fleet of devices running Docker containers. Each container is destroyed and recreated on a regular basis for updates. Programs in the container write logs to a volume that persists between container destroy/create cycles.
I'd like to use rsyslog to send logs in the persistent volume to a log aggregator service, and that part works fine. The problem is that every time we release an update, rsyslog sends the entire contents of the logs, including lines it has already sent.
How can we configure rsyslog to remember what it has sent, maybe in a file inside the persistent volume?
I've done some Googling, read through guides like this, and have skimmed the documentation, and haven't found an obvious solution.
logs raspbian docker rsyslog containers
asked Sep 27 '17 at 0:48
Sheng Wu
11
add a comment |Â
up vote
0
down vote
favorite
We have a fleet of devices running Docker containers. Each container is destroyed and recreated on a regular basis for updates. Programs in the container write logs to a volume that persists between container destroy/create cycles.
I'd like to use rsyslog to send logs in the persistent volume to a log aggregator service, and that part works fine. The problem is that every time we release an update, rsyslog sends the entire contents of the logs, including lines it has already sent.
How can we configure rsyslog to remember what it has sent, maybe in a file inside the persistent volume?
I've done some Googling, read through guides like this, and have skimmed the documentation, and haven't found an obvious solution.
logs raspbian docker rsyslog containers
asked Sep 27 '17 at 0:48
Sheng Wu
11
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We have a fleet of devices running Docker containers. Each container is destroyed and recreated on a regular basis for updates. Programs in the container write logs to a volume that persists between container destroy/create cycles.
I'd like to use rsyslog to send logs in the persistent volume to a log aggregator service, and that part works fine. The problem is that every time we release an update, rsyslog sends the entire contents of the logs, including lines it has already sent.
How can we configure rsyslog to remember what it has sent, maybe in a file inside the persistent volume?
I've done some Googling, read through guides like this, and have skimmed the documentation, and haven't found an obvious solution.
logs raspbian docker rsyslog containers
asked Sep 27 '17 at 0:48
Sheng Wu
11
We have a fleet of devices running Docker containers. Each container is destroyed and recreated on a regular basis for updates. Programs in the container write logs to a volume that persists between container destroy/create cycles.
I'd like to use rsyslog to send logs in the persistent volume to a log aggregator service, and that part works fine. The problem is that every time we release an update, rsyslog sends the entire contents of the logs, including lines it has already sent.
How can we configure rsyslog to remember what it has sent, maybe in a file inside the persistent volume?
I've done some Googling, read through guides like this, and have skimmed the documentation, and haven't found an obvious solution.
logs raspbian docker rsyslog containers
logs raspbian docker rsyslog containers
asked Sep 27 '17 at 0:48
Sheng Wu
11
asked Sep 27 '17 at 0:48
Sheng Wu
11
asked Sep 27 '17 at 0:48
Sheng Wu
11
asked Sep 27 '17 at 0:48
Sheng Wu
11
asked Sep 27 '17 at 0:48
Sheng Wu
11
11
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f394660%2frsyslog-for-containers-that-are-destroyed-and-recreated-regularly%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
