To fine-tune and make it easier to analyze the logs, you might want to adjust the log
trace of Decision Designer and the decision
runtime services.
About this task
In the Custom Resource (CR) file of the operator, you can set the
log_trace_specification parameter for the following Decision Designer services:
- Credentials service
- Git service
- Parsing service
- Run service
- Runtime service
- REST API
The value that you provide for this parameter determines the level of detail that is returned
in the log traces of the
Decision Designer
services. Follow the syntax of the
traceSpecification attribute described here
Logging and Trace

.
Procedure
-
In the CR file, set the logging level for each Decision Designer service.
- Credentials service
-
spec:
decision_designer:
credentials_service:
log_trace_specification:
The following table lists common logging values for this service.
| Value |
Description |
| *=info |
All loggers are set at the info level |
- Git service
-
spec:
decision_designer:
git_service:
log_trace_specification:
The following table lists common logging values for this service.
| Value |
Description |
| *=info |
All loggers are set at the info level |
- Parsing service
-
spec:
decision_designer:
parsing_service:
log_trace_specification:
The following table lists common logging values for this service.
| Value |
Description |
| *=info |
All loggers are set at the info level |
- Run service
-
spec:
decision_designer:
run_service:
log_trace_specification:
The following table lists common logging values for this service.
| Value |
Description |
| *=info |
All loggers are set at the info level |
- Runtime service
-
spec:
decision_runtime:
decision_runtime_service:
log_trace_specification:
The following table lists common logging values for this service.
| Value |
Description |
| *=info |
All loggers are set at the info level |
- REST API
-
spec:
decision_designer:
rest_api:
log_trace_specification:
The following table lists common logging values for this service.
| Value |
Description |
| *=info |
All loggers are set at the info level |
| *=info:org.apache.httpcomponents=finer |
All HTTP traffic that goes through the HTTP client is logged with a finer level |
- To see the updated logs, wait for the pods to restart automatically after the operator
reconciliation.