...

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:
>kubectl logs

kubectl logs enrichmentservice-0 --namespace nonrtric

Updating of the configuration file application.yaml

...

The contents of the config map can be retrieved by command:>kubectl describe configmap

kubectl describe configmap enrichmentservice-configmap -n nonrtric

The following lines controls the logging levels (example of the default settings):

logging:

...

  level:

...

    ROOT:

...

 ERROR
    org.springframework:

...

 ERROR
    org.springframework.data:

...

 ERROR
    org.springframework.web.reactive.function.client.ExchangeFunctions:

...

 ERROR
    org.oransc.enrichment: INFO

If this file is put in a directory named config; ./config/application.yaml, the config map can be updated by command: >kubectl create configmap  enrichmentservice

kubectl create configmap  enrichmentservice-configmap --from-file=./config --dry-run=client -n nonrtric -o yaml | kubectl apply -f -

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

...

You can get the IP address and the port of the POD by command:>kubectl describe pod

kubectl describe pod enrichmentservice-0 -n nonrtric

Policy Management Service

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:
>kubectl logs

kubectl logs policymanagementservice-0 --namespace nonrtric

Updating of the configuration file application.yaml

...

You can get the IP address and the port of the POD by command:>kubectl describe pod

kubectl describe pod policymanagementservice-0 -n nonrtric