How change the logging level at runtime for IBM Liberty server?
up vote
0
down vote
favorite
The IBM WAS8 allows changing the logging level at runtime via API.
How to do the same thing for IBM Liberty server without changing the server.xml?
I think this is possible via defining custom API, e.g. REST endpoint that will do this. Is the vendor recommended way to do it?
websphere-liberty open-liberty
asked Nov 7 at 14:41
senleft
213313
add a comment |
up vote
0
down vote
favorite
The IBM WAS8 allows changing the logging level at runtime via API.
How to do the same thing for IBM Liberty server without changing the server.xml?
I think this is possible via defining custom API, e.g. REST endpoint that will do this. Is the vendor recommended way to do it?
websphere-liberty open-liberty
asked Nov 7 at 14:41
senleft
213313
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
The IBM WAS8 allows changing the logging level at runtime via API.
How to do the same thing for IBM Liberty server without changing the server.xml?
I think this is possible via defining custom API, e.g. REST endpoint that will do this. Is the vendor recommended way to do it?
websphere-liberty open-liberty
asked Nov 7 at 14:41
senleft
213313
The IBM WAS8 allows changing the logging level at runtime via API.
How to do the same thing for IBM Liberty server without changing the server.xml?
I think this is possible via defining custom API, e.g. REST endpoint that will do this. Is the vendor recommended way to do it?
websphere-liberty open-liberty
websphere-liberty open-liberty
asked Nov 7 at 14:41
senleft
213313
asked Nov 7 at 14:41
senleft
213313
asked Nov 7 at 14:41
senleft
213313
asked Nov 7 at 14:41
senleft
213313
asked Nov 7 at 14:41
senleft
213313
213313
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Liberty does not provide an API equivalent to change logging levels. You can make the change at runtime (no restart required) by directly changing the server.xml or by changing the server.xml through Admin Center's Server Config tool (available in WebSphere Liberty, but not Open Liberty). I mention the latter because Admin Center uses public APIs for everything including making changes to the server.xml which means you could technically make the same API calls to change the server.xml to include your logging changes at runtime.
However, the drawback with that approach is that you'd have to use the file transfer API to read the server.xml, then make appropriate changes to it, and then use file transfer API again to persist the changes.
If you'd like to see an API for changing log levels, I would recommend opening an RFE (https://developer.ibm.com/wasdev/help/submit-rfe/)
answered Nov 7 at 15:32
M. Broz
35628
Thank you! I will submit RFE. It is a bit strange decision. Someone thought that developer will have access to file system of the prod server to change in runtime the logging level of the specific component.
– senleft
Nov 14 at 15:20
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Liberty does not provide an API equivalent to change logging levels. You can make the change at runtime (no restart required) by directly changing the server.xml or by changing the server.xml through Admin Center's Server Config tool (available in WebSphere Liberty, but not Open Liberty). I mention the latter because Admin Center uses public APIs for everything including making changes to the server.xml which means you could technically make the same API calls to change the server.xml to include your logging changes at runtime.
However, the drawback with that approach is that you'd have to use the file transfer API to read the server.xml, then make appropriate changes to it, and then use file transfer API again to persist the changes.
If you'd like to see an API for changing log levels, I would recommend opening an RFE (https://developer.ibm.com/wasdev/help/submit-rfe/)
answered Nov 7 at 15:32
M. Broz
35628
Thank you! I will submit RFE. It is a bit strange decision. Someone thought that developer will have access to file system of the prod server to change in runtime the logging level of the specific component.
– senleft
Nov 14 at 15:20
add a comment |
up vote
1
down vote
accepted
Liberty does not provide an API equivalent to change logging levels. You can make the change at runtime (no restart required) by directly changing the server.xml or by changing the server.xml through Admin Center's Server Config tool (available in WebSphere Liberty, but not Open Liberty). I mention the latter because Admin Center uses public APIs for everything including making changes to the server.xml which means you could technically make the same API calls to change the server.xml to include your logging changes at runtime.
However, the drawback with that approach is that you'd have to use the file transfer API to read the server.xml, then make appropriate changes to it, and then use file transfer API again to persist the changes.
If you'd like to see an API for changing log levels, I would recommend opening an RFE (https://developer.ibm.com/wasdev/help/submit-rfe/)
answered Nov 7 at 15:32
M. Broz
35628
Thank you! I will submit RFE. It is a bit strange decision. Someone thought that developer will have access to file system of the prod server to change in runtime the logging level of the specific component.
– senleft
Nov 14 at 15:20
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Liberty does not provide an API equivalent to change logging levels. You can make the change at runtime (no restart required) by directly changing the server.xml or by changing the server.xml through Admin Center's Server Config tool (available in WebSphere Liberty, but not Open Liberty). I mention the latter because Admin Center uses public APIs for everything including making changes to the server.xml which means you could technically make the same API calls to change the server.xml to include your logging changes at runtime.
However, the drawback with that approach is that you'd have to use the file transfer API to read the server.xml, then make appropriate changes to it, and then use file transfer API again to persist the changes.
If you'd like to see an API for changing log levels, I would recommend opening an RFE (https://developer.ibm.com/wasdev/help/submit-rfe/)
answered Nov 7 at 15:32
M. Broz
35628
Liberty does not provide an API equivalent to change logging levels. You can make the change at runtime (no restart required) by directly changing the server.xml or by changing the server.xml through Admin Center's Server Config tool (available in WebSphere Liberty, but not Open Liberty). I mention the latter because Admin Center uses public APIs for everything including making changes to the server.xml which means you could technically make the same API calls to change the server.xml to include your logging changes at runtime.
However, the drawback with that approach is that you'd have to use the file transfer API to read the server.xml, then make appropriate changes to it, and then use file transfer API again to persist the changes.
If you'd like to see an API for changing log levels, I would recommend opening an RFE (https://developer.ibm.com/wasdev/help/submit-rfe/)
answered Nov 7 at 15:32
M. Broz
35628
edited Nov 7 at 15:41
answered Nov 7 at 15:32
M. Broz
35628
answered Nov 7 at 15:32
M. Broz
35628
answered Nov 7 at 15:32
M. Broz
35628
35628
Thank you! I will submit RFE. It is a bit strange decision. Someone thought that developer will have access to file system of the prod server to change in runtime the logging level of the specific component.
– senleft
Nov 14 at 15:20
add a comment |
Thank you! I will submit RFE. It is a bit strange decision. Someone thought that developer will have access to file system of the prod server to change in runtime the logging level of the specific component.
– senleft
Nov 14 at 15:20
Thank you! I will submit RFE. It is a bit strange decision. Someone thought that developer will have access to file system of the prod server to change in runtime the logging level of the specific component.
– senleft
Nov 14 at 15:20
Thank you! I will submit RFE. It is a bit strange decision. Someone thought that developer will have access to file system of the prod server to change in runtime the logging level of the specific component.
– senleft
Nov 14 at 15:20
add a comment |
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%2fstackoverflow.com%2fquestions%2f53191687%2fhow-change-the-logging-level-at-runtime-for-ibm-liberty-server%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
