...
| Code Block | ||
|---|---|---|
| ||
kubectl describe pod policymanagementservice-0 -n nonrtric |
DMaaP Adaptor Service
In the same was as the other springboot services, there are two ways to configure logging.
- Updating the application.yaml file, which requires a POD restart.
- By invoking a REST API. The changes takes effect immediately, but the changes will not survive a POD restart.
The contents of the log can be read by command:
| Code Block | ||
|---|---|---|
| ||
kubectl logs dmaapadapterservice-0 --namespace nonrtric |
Updating of the configuration file application.yaml
Debug logging in the the PMS can be configured the same was as for the Enrichment Coordinator Service (described above). The difference is that the name of the config map is dmaapadapterservice-configmap-config.
Configuring logging using the REST API
In the same was for the PMS, debug logging can also be configured by using REST. This does not require a POD restart. The traces 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.oran.dmaapadapter package):
>curl http://172.17.0.6:8081/actuator/loggers/org.oran.dmaapadapter -i -X POST -H 'Content-Type: application/json' -d '{"configuredLevel":"debug"}'
You can get the IP address and the port of the POD by command:
| Code Block | ||
|---|---|---|
| ||
kubectl describe pod dmaapadapterservice-0 -n nonrtric |