Enrichment Coordinator Service

There are two ways to configure logging. Updating the application.yaml file, requires a POD restart and the changes survives a POD restart. There is also a REST API, where the changes does not require a POD restart, but the changes will not survive a POD restart.

Updating 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 enrichmentservice-configmap.

...

A POD restart is required for the change to take place.

Configuring logging using the REST API

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.enrichment  package):

...

>kubectl describe pod enrichmentservice-0 -n nonrtric

Policy Management Service

There are two ways to configure logging. Updating the application.yaml file, requires a POD restart and the changes survives a POD restart. There is also a REST API, where the changes does not require a POD restart, but the changes will not survive a POD restart.

Updating 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 policymanagementservice-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.onap.ccsdk.oran.a1policymanagementservice package):

...