| Page Properties |
|---|
|
| Product Version | 2022 Spring |
|---|
| Report Note |
|
|---|
| Assignee | Antje |
|---|
Resources & Remarks Modification History | Name | Date | Product Version | Action |
|---|
| Antje | 16 DEC 2021 | 2022 Spring | Page created & written. |
|
...
| Code Block |
|---|
|
logging.level.com.os.services: DEBUG |
The target service has to be refreshed or restarted in order to activate the new logging configuration.
'/*/manage/loggers/**' Endpoints
The logger management endpoints are accessible only for users with specific authorization as defined in the authentication-prod.yml file and controlled by the AUTHENTICATION Service.
...
In order to set a log level at runtime, it can be specified in JSON format as shown in the example below and sent as request body to the POST endpoint http://<ip>:<port>/manage/loggers/<packageName>.
| Code Block |
|---|
| language | yml |
|---|
| title | Example request body |
|---|
| collapse | true |
|---|
|
{"configuredLevel":"DEBUG"} |
The change applies immediately to the service instance running on the target port has to be refreshed or restarted in order to activate the new logging configuration. After a restart of this service, the log level is reset to the value configured in a configuration file as described before.
Summary
The configuration of log levels can be adjusted in the service deployment during the installation. For a system in operation, the logging can be configured in configuration files or via an endpoint.
| Info |
|---|
|
Read on
| Section |
|---|
| Column |
|---|
| | Insert excerpt |
|---|
| Configuring Services using Profiles |
|---|
| Configuring Services using Profiles |
|---|
| nopanel | true |
|---|
|
Keep reading
|
| Column |
|---|
| | Insert excerpt |
|---|
| Health Check for Services |
|---|
| Health Check for Services |
|---|
| nopanel | true |
|---|
|
Keep reading
|
| Column |
|---|
| | Insert excerpt |
|---|
| Service Monitoring |
|---|
| Service Monitoring |
|---|
| nopanel | true |
|---|
|
Keep reading
|
|
|
...