Syslog to console, drawbacks?
I am wondering are there any drawback (performance wise) when output from some software is not logged to a file, but instead to console?
Specific case would be running Docker containers, as some of processes are intentionaly configured to log on stdout.
With files, only problem that can cross my mind is space used by logs, and some IO depending how aggressive logging is.
To give an example, let say I have a webserver app in Docker container that logs access logs to stdout(console), and let's imagine that container stays running for 1y constantly, would that kind of large buffer stay in memory (kernel one?) , for all the time, or kernel would eventually wipe it after some limit?
Should I be potentially affraid of some memory exhaustion in this case and kernel panics, or I misunderstand concept?
( i understand that when app|container|node is down, console is flushed, same as when dmesg is cleared )
Thanks.
linux kernel docker console syslog
asked 3 hours ago
fugitivefugitive
806421
add a comment |
I am wondering are there any drawback (performance wise) when output from some software is not logged to a file, but instead to console?
Specific case would be running Docker containers, as some of processes are intentionaly configured to log on stdout.
With files, only problem that can cross my mind is space used by logs, and some IO depending how aggressive logging is.
To give an example, let say I have a webserver app in Docker container that logs access logs to stdout(console), and let's imagine that container stays running for 1y constantly, would that kind of large buffer stay in memory (kernel one?) , for all the time, or kernel would eventually wipe it after some limit?
Should I be potentially affraid of some memory exhaustion in this case and kernel panics, or I misunderstand concept?
( i understand that when app|container|node is down, console is flushed, same as when dmesg is cleared )
Thanks.
linux kernel docker console syslog
asked 3 hours ago
fugitivefugitive
806421
add a comment |
I am wondering are there any drawback (performance wise) when output from some software is not logged to a file, but instead to console?
Specific case would be running Docker containers, as some of processes are intentionaly configured to log on stdout.
With files, only problem that can cross my mind is space used by logs, and some IO depending how aggressive logging is.
To give an example, let say I have a webserver app in Docker container that logs access logs to stdout(console), and let's imagine that container stays running for 1y constantly, would that kind of large buffer stay in memory (kernel one?) , for all the time, or kernel would eventually wipe it after some limit?
Should I be potentially affraid of some memory exhaustion in this case and kernel panics, or I misunderstand concept?
( i understand that when app|container|node is down, console is flushed, same as when dmesg is cleared )
Thanks.
linux kernel docker console syslog
asked 3 hours ago
fugitivefugitive
806421
I am wondering are there any drawback (performance wise) when output from some software is not logged to a file, but instead to console?
Specific case would be running Docker containers, as some of processes are intentionaly configured to log on stdout.
With files, only problem that can cross my mind is space used by logs, and some IO depending how aggressive logging is.
To give an example, let say I have a webserver app in Docker container that logs access logs to stdout(console), and let's imagine that container stays running for 1y constantly, would that kind of large buffer stay in memory (kernel one?) , for all the time, or kernel would eventually wipe it after some limit?
Should I be potentially affraid of some memory exhaustion in this case and kernel panics, or I misunderstand concept?
( i understand that when app|container|node is down, console is flushed, same as when dmesg is cleared )
Thanks.
linux kernel docker console syslog
linux kernel docker console syslog
asked 3 hours ago
fugitivefugitive
806421
asked 3 hours ago
fugitivefugitive
806421
asked 3 hours ago
fugitivefugitive
806421
asked 3 hours ago
fugitivefugitive
806421
asked 3 hours ago
fugitivefugitive
806421
806421
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506613%2fsyslog-to-console-drawbacks%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506613%2fsyslog-to-console-drawbacks%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
