Skip to main content
Skip table of contents

Changing the Log Level of a Docker Container

In the administration application you have the possibility to change the log level for a Docker container. The functionality is currently available for the following service types:

You have two options to open the input form where you can change the log level:

  • Use action Change log level from the quick actions bar in the services' list. This will open a pop-up window.

log_level_quick_action.png
  • Open the details page of the service and scroll down to section Logs:

docker_details_page_logs.png

Changing the log level varies for the different service types. The details are explained below.

Default Retention Time of Log Files

The following retention times are valid for log files of your PAS installation:

  • Container logs: Log files inside all containers are deleted after 7 days.

  • Log Analyzer (OpenSearch) logs:

    • Single cluster: Log files are deleted after 14 days.

    • High Availability cluster: Log files are deleted after 30 days.

  • Integration (Bridge) logs: The default retention time for Bridge logs is 30 days. This is configurable in the UI, refer to Node Instance Preferences.

Log Level for Service Type pas-nestjs

On the details page of a pas-nestjs service, scroll down to section Logs and expand the section:

nestjs_docker_logs.png

If you open the pop-up window via the quick actions, you have the same options for the Configuration of the logs:

chang_nestjs_log_level.png

Available log levels are:

  • verbose

  • trace

  • debug

  • info

  • warn

  • error

If you have turned down the log level to see more logs, do not forget to turn it up again after you have finished your analysis. The performance of the system may deteriorate if a lot of logs are stored for a long time. The log level settings are reset to its default value during a restart of the service.

Save your changes to apply them to the service. Use Reset to “info” to return to the info log level. If you opened the pop-up window from the quick action menu in the service list, you have also a Cancel button. Click Cancel to discard your changes and to close the pop-up window:

save_log_level_change.png

In the Logs section of the service details page, you can also use the link Open Log Analyzer to inspect logs:

nestjs_inspect_logs.png

The Log Analyzer will open, showing you the corresponding logs:

docker_nestjs_log_analyzer.png

For more information about the Log Analyzer, refer to Analyzing Platform Logs.

Log Level for Service Type pas-service

On the details page of a pas-service, scroll down to section Logs and expand the section:

pas-service_docker_logs.png

If you open the pop-up window via the quick actions, you have the same options to change the log level:

choose_log_level.png

Open the drop-down list to select one of the available log levels:

  • TRACE

  • DEBUG

  • INFO

  • WARN

  • ERROR

  • FATAL

If you have turned down the log level to see more logs, do not forget to turn it up again after you have finished your analysis. The performance of the system may deteriorate if a lot of logs are stored for a long time. The log level settings are reset to its default value during a restart of the service.

The chosen log level is kept after a restart of the service. If after a restart of the service you want to return to the previously used log level, disable option Keep after Restart:

keep_after_restart.png

Save your changes to apply them to the service. Click the Reset button to return to the default settings. If you opened the pop-up window by useing the icon in the service list, you have also a Cancel button. Click Cancel to to discard your changes and to close the pop-up window:

save_log_level.png

In the Logs section of the service details page, you can also use the link Open Log Analyzer to inspect logs:

pas-service_inspect_logs.png

The Log Analyzer will open, showing you the corresponding logs:

pas-service_log_analyzer.png

For more information about the Log Analyzer, refer to Analyzing Platform Logs.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.