Issues Related to Selective Tracing Based on Subscriber

(Doc ID 2380725.1)

Last updated on APRIL 13, 2018

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On Elastic Charging Engine (ECE) version 11.3.0.6.0 :

Scenario:

  1. Add the subscriber in the subscriber-trace.xml
    <subscriber id="096234271" config-class="oracle.communication.brm.charging.subscribertrace.configuration.internal.SubscriberImpl"/>
  2. Invoke the updateSubscriberTraceConfiguration from jconsole
  3. Verify ECE Subscriber Tracing from jconsole
  4. Send the following diameter messages through seagull:
      SLR -> CCR(I) -> CCR(U) -> STR -> CCR(T)


Observations:

  1. From the ece log directory, diameterGateway1.096234271.SLR_1000348.log and ecs1.096234271.SLR_1000348.log have been generated for tracing, but no separate log has been generated for
    CCR.
  2. There is no documentation for below parameters:
        logExpiryWaitTime = "1"
        logCleanupInterval = "2"
  3. If there is any error in execution of updateSubscriberTraceConfiguration, jconsole is not reporting the same, the error is visible in logs only.
    So after invoking the updateSubscriberTraceConfiguration procedure, one needs to go and check the logs for the confirmation every time. This behavior is not correct because one will use the log to debug the error, but application has to tell the end-user whether it has run successfully or not, and only then one could look into the logs for debugging if necessary.

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms