Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Enrichment Coordinator Service

Debug logging can be enabled by a file; application.yaml. This file can in turn be updated by means of a config map named enrichmentservice-configmap.

The contents of the config map can be retrieved by command:
>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-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.


Policy Management Service

Debug logging in the the PMS can be done in 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.

  • No labels