Changing log level at runtime in a clustered Spring Boot application











up vote
0
down vote

favorite












We have a Spring Boot application that runs clustered in an OpenShift environment. We can dynamically scale the application up and down, so we have as many instances as we need to handle the load.



This application uses SLF4J and Logback for logging. Now we would like to dynamically change the log level of all cluster members. Currently we do this by changing some system property in the deployment configuration (e.g. adding -Dlogging.level.com.example=DEBUG) and then performing a rolling re-deploy of the application. Since the application is clustered and the update is performed in a rolling fashion there is no perceived downtime for the consumers of the app. However the app also runs background tasks which could be interrupted by a rolling deployment. Therefore we would rather have a way of updating the logging configuration of all cluster members without having to restart the application.



We know that logback supports monitoring a file, but we cannot replace files in the docker containers at runtime and even if we could we would need some way of ensuring that this happens simultaneously on all cluster members.



What would be a good way of achieving this?










share|improve this question






















  • Enable the actuator and you can switch the loglevel at runtime by doing a POST to the logger endpoint. Or use Spring Cloud Config and refresh the configuration after changing it.
    – M. Deinum
    Nov 22 at 18:57

















up vote
0
down vote

favorite












We have a Spring Boot application that runs clustered in an OpenShift environment. We can dynamically scale the application up and down, so we have as many instances as we need to handle the load.



This application uses SLF4J and Logback for logging. Now we would like to dynamically change the log level of all cluster members. Currently we do this by changing some system property in the deployment configuration (e.g. adding -Dlogging.level.com.example=DEBUG) and then performing a rolling re-deploy of the application. Since the application is clustered and the update is performed in a rolling fashion there is no perceived downtime for the consumers of the app. However the app also runs background tasks which could be interrupted by a rolling deployment. Therefore we would rather have a way of updating the logging configuration of all cluster members without having to restart the application.



We know that logback supports monitoring a file, but we cannot replace files in the docker containers at runtime and even if we could we would need some way of ensuring that this happens simultaneously on all cluster members.



What would be a good way of achieving this?










share|improve this question






















  • Enable the actuator and you can switch the loglevel at runtime by doing a POST to the logger endpoint. Or use Spring Cloud Config and refresh the configuration after changing it.
    – M. Deinum
    Nov 22 at 18:57















up vote
0
down vote

favorite









up vote
0
down vote

favorite











We have a Spring Boot application that runs clustered in an OpenShift environment. We can dynamically scale the application up and down, so we have as many instances as we need to handle the load.



This application uses SLF4J and Logback for logging. Now we would like to dynamically change the log level of all cluster members. Currently we do this by changing some system property in the deployment configuration (e.g. adding -Dlogging.level.com.example=DEBUG) and then performing a rolling re-deploy of the application. Since the application is clustered and the update is performed in a rolling fashion there is no perceived downtime for the consumers of the app. However the app also runs background tasks which could be interrupted by a rolling deployment. Therefore we would rather have a way of updating the logging configuration of all cluster members without having to restart the application.



We know that logback supports monitoring a file, but we cannot replace files in the docker containers at runtime and even if we could we would need some way of ensuring that this happens simultaneously on all cluster members.



What would be a good way of achieving this?










share|improve this question













We have a Spring Boot application that runs clustered in an OpenShift environment. We can dynamically scale the application up and down, so we have as many instances as we need to handle the load.



This application uses SLF4J and Logback for logging. Now we would like to dynamically change the log level of all cluster members. Currently we do this by changing some system property in the deployment configuration (e.g. adding -Dlogging.level.com.example=DEBUG) and then performing a rolling re-deploy of the application. Since the application is clustered and the update is performed in a rolling fashion there is no perceived downtime for the consumers of the app. However the app also runs background tasks which could be interrupted by a rolling deployment. Therefore we would rather have a way of updating the logging configuration of all cluster members without having to restart the application.



We know that logback supports monitoring a file, but we cannot replace files in the docker containers at runtime and even if we could we would need some way of ensuring that this happens simultaneously on all cluster members.



What would be a good way of achieving this?







spring-boot configuration logback






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 at 15:09









Jan Thomä

9,12943468




9,12943468












  • Enable the actuator and you can switch the loglevel at runtime by doing a POST to the logger endpoint. Or use Spring Cloud Config and refresh the configuration after changing it.
    – M. Deinum
    Nov 22 at 18:57




















  • Enable the actuator and you can switch the loglevel at runtime by doing a POST to the logger endpoint. Or use Spring Cloud Config and refresh the configuration after changing it.
    – M. Deinum
    Nov 22 at 18:57


















Enable the actuator and you can switch the loglevel at runtime by doing a POST to the logger endpoint. Or use Spring Cloud Config and refresh the configuration after changing it.
– M. Deinum
Nov 22 at 18:57






Enable the actuator and you can switch the loglevel at runtime by doing a POST to the logger endpoint. Or use Spring Cloud Config and refresh the configuration after changing it.
– M. Deinum
Nov 22 at 18:57



















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433804%2fchanging-log-level-at-runtime-in-a-clustered-spring-boot-application%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • 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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433804%2fchanging-log-level-at-runtime-in-a-clustered-spring-boot-application%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

What visual should I use to simply compare current year value vs last year in Power BI desktop

How to ignore python UserWarning in pytest?

Alexandru Averescu