...
| Code Block | ||
|---|---|---|
| ||
kubectl logs enrichmentserviceinformationservice-0 --namespace nonrtric |
Updating of the configuration file application.yaml
Debug logging can be configured by a file; application.yaml. This file can in turn be updated by means of a config map named enrichmentservicenamed informationservice-configmap.
The contents of the config map can be retrieved by command:
| Code Block | ||
|---|---|---|
| ||
kubectl describe configmap enrichmentserviceinformationservice-configmap -n nonrtric |
The following lines controls the logging levels (example of the default settings):
| Code Block | ||
|---|---|---|
| ||
logging:
level:
ROOT: ERROR
org.springframework: ERROR
org.springframework.data: ERROR
org.springframework.web.reactive.function.client.ExchangeFunctions: ERROR
org.oransc.enrichmentics: INFO |
If this file is put in a directory named config; ./config/application.yaml, the config map can be updated by command:
| Code Block | ||
|---|---|---|
| ||
kubectl create configmap enrichmentserviceinformationservice-configmap --from-file=./config --dry-run=client -n nonrtric -o yaml | kubectl apply -f - |
...
Debug logging can also be configured by using REST. This does not require a POD restart. The configuration will on the other hand revert to the default after a POD restart. Here follows an example on how to enable debug level tracing on the whole component (all classes in the org.oransc.enrichmentics package):
>curl http://172.17.0.7:8083/actuator/loggers/org.oransc.enrichmentics -i -X POST -H 'Content-Type: application/json' -d '{"configuredLevel":"debug"}'
...