kpm_mon_xapp doesn't send metrics after upgrade of srsRAN in June

[robert-200]

Hello,

When using "old" (before update in June) version of srsRAN_Project (DU and CU), I could run kpm_mon_xapp and got the expected results. However, as pointed in this forum, this version of srsRAN_Project had some problems to work correctly with simple_rc_ho_xapp.py. In June a new version of srsRAN_Project was issued that corrected the problem with simple_rc_ho_xapp.py - I can confirm it works. However, this new version no longer works with kpm_mon_xapp. The problem is the lack of information about the metrics from DU. I enclose two zipped pcaps documenting the signalling traffic exchange between E2 node and nearRTRIC. In the file du_e2ap-correct.pcap you can observe RICIndication messages that carry the metric values from E2 node to nearRTRIC (the “old” version of srsRAN_Project was used in this case). In the file du_e2ap - incorrect.pcap there is no RICindication messages, despite the successful subscription to E2 node for information about the metrics (the new version of srsRAN_Project was used in this case). I was using kpm_mon_xapp to periodically collect the values of DRB.UEThpUl and DRB.UEThpDl metrics.

Regards
Robert

du_e2ap - incorrect.zip

du_e2ap-correct.zip

[pgawlowicz]

Hi,

The E2 metric are based on the internal stack metric. Did you enable internal stack metric reporting?

metrics:
  layers:
    enable_rlc: true                # Enable RLC metrics
    enable_sched: true              # Enable DU scheduler metrics
    enable_mac: true                # Enables MAC metrics.
  periodicity:
    cu_cp_report_period: 1000           # Optional UINT (1000). CU-CP metrics report period in milliseconds.
    cu_up_report_period: 1000           # Optional UINT (1000). CU-UP metrics report period in milliseconds.
    du_report_period: 1000              # Optional UINT (1000). DU statistics report period in milliseconds. Supported: [0 - 10485760].

BR,
Piotr

[victorpdiniz]

I was having the same problem and it worked perfectly after enabling the internal stack metric reporting. Thanks!