13 Using Logging for ECE Composable Services

You can review log files to troubleshoot errors and monitor system activity in the Oracle Communications Elastic Charging Engine (ECE) composable services.

Topics in this document:

• About Logging

• Accessing the ECE Composable Service Logs

• Changing the Log Levels

About Logging

The ECE composable services use the Apache Log4j2 Java logging utility to log information and errors about the following:

• Startup and shutdown activity

• Interaction with external applications at integration points, including interactions with the ingress controller and 5G Network Functions (NFs)

• Charging Manager (CHF) and Charging Gateway Function (CGF) composable services

For general information about:

• Java logging, see Java Platform, Standard Edition Core Libraries

• Log4j2, see https://logging.apache.org/log4j/2.x/manual/index.html

When you deploy the ECE composable services, logging is automatically set up and running in your system with default settings.

• To access the log files, see "Accessing the ECE Composable Service Logs".

• To change the default logging levels, see "Changing the Log Levels".

Accessing the ECE Composable Service Logs

You access the logs by using the kubectl command in the ECE composable services namespace.

To access the logs:

1. Retrieve the names of the ECE composable service pods by entering this command:

   kubectl -n EceCompServicesNameSpace get pods

   where EceCompServicesNameSpace is the namespace in which Kubernetes objects for the Helm chart reside.

   The following is an example of the command's output, with the pod names in bold:

   NAME                                       READY  STATUS     RESTARTS    AGE
   cgf-0                                      1/1    Running    0           7h23m
   cgf-coordinator-69f7d75d75-rml48           1/1    Running    0           7h23m
   nchf-converged-charging-65cfd79c6c-nvqb8   1/1    Running    0           7h23m
   nchf-nrf-7598464577-k8w25                  1/1    Running    0           7h23m

2. Access the logs for a pod by entering this command:

   kubectl -n EceCompServicesNameSpace logs PodName

   For example, to access the cgf-0 logs, enter:

   kubectl -n EceCompServicesNameSpace logs cgf-0

The following is an example of the logs for the cgf-0 pod:

2026-05-19T17:58:20,591+00:00 | INFO | | main | r.hikari.HikariDataSource | oracle - Starting...
2026-05-19T17:58:20,993+00:00 | INFO | | main | er.hikari.pool.HikariPool | oracle - Added connection com.mysql.cj.jdbc.ConnectionImpl@620c8641
2026-05-19T17:58:21,687+00:00 | INFO | | main | r.hikari.HikariDataSource | oracle - Start completed.
2026-05-19T17:58:21,797+00:00 | INFO | | main | oracle.cagbu.ccs.cgf.Main | Configured Kafka subscriber lifecycle for 2 messaging service(s).
2026-05-19T17:58:22,102+00:00 | INFO | | main | gging.log4j.Log4jProvider | Logging initialization.

Note:

This task shows how to access logs for a single pod at a time. To tail logs from multiple pods, Oracle recommends using the Kubernetes Stern tool.

Changing the Log Levels

You can change the logging level for each pod at the root level and package level to one of the following:

• TRACE: This log level provides verbose information, including each row loaded into the database.

• DEBUG: This log level provides information about the steps for each loading function.

• WARN: This log level provides non-critical warnings.

• INFO: This log level provides a one-line summary of each file processed.

• ERROR: This log level provides only error information.

To change the log levels for a pod:

1. Create an override-values.yaml file for your ECE composable services Helm chart.

2. To set a pod's root-level logging, set the logging.rootLevel key to the desired logging level.

3. To set a pod's package-level logging, set the following keys:

   • logging.packageLogging.name: The name of the logging package, such as io.helidon or org.jboss.

   • logging.packageLogging.level: The logging level, such as TRACE, DEBUG, WARN, INFO, or ERROR.

4. Save and close your override-values.yaml file.

5. Update your Helm release:

   helm upgrade EceCompServicesReleaseName oc-ccs-version --values override-values.yaml -n EceCompServicesNameSpace

The following shows sample logging settings for the charging-gateway pod.

cgf:
   chargingGateway:
      logging:
         format:          
            type: TEXT          
            pattern: *loggingPattern        
         rootLevel: DEBUG        
         packageLogging:          
            - name: com.oracle.cagbu 
              level: INFO          
            - name: io.helidon            
              level: INFO