Monitor Subscriber (MonSub) Logs
The following are the synopsis of the Monitor Subscriber (MonSub) Logs to trigger session management policies towards the SMF:
-
The logs help to control the logging level of transaction logs, when the monitor subscriber CLI gets enabled.
-
The Monitor Subscriber CLI captures the transaction logs for a given SUPI or IMSI.
-
The Monitor Subscriber Logger uses a specific logging level, used for the subscriber, for which the monitor subscriber CLI gets triggered.
-
The SMF must support per-subscriber monitoring activities. If required, it must be used to monitor a particular subscriber based on the appropriate configurable parameters, such as SUPI or IMSI.
-
As a default value, the monitor subscriber functionality is disabled. It gets enabled manually by specifying the appropriate configurable parameters.
Logging a Message for MonSub Logs
The following is a sample example of a LogTag for MonSub Logs:
smf# monitor subscriber imsi 123456789012345 capture-duration 3600 transaction-logs yes internal-messages yes Fri Oct 14 09:05:53.902 UTC+00:00 supi: imsi-123456789012345 captureDuration: 3600 enableInternalMsg: true enableTxnLog: true namespace(deprecated. Use nf-service instead.): none nf-service: none gr-instance: 0 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 318 100 116 100 202 12888 22444 --:--:-- --:--:-- --:--:-- 35333 Command: --header Content-type:application/json --request POST --data
{"commandname":"mon_sub", "parameters":{"supi":"imsi-123456789012345", "duration":3600,"enableTxnLog":true,"enableInternalMsg":true, "action":"start","namespace":"none","nf-service":"none", "grInstance":0}} http://oam-pod:8879/commands Result start mon_sub, fileName ->logs/monsublogs/none.imsi-123456789012345_WithTxnLogs_TS_2022-10-14T09:05:53.926268924.txt Starting to tail the monsub messages from file: logs/monsublogs/none.imsi-123456789012345_WithTxnLogs_TS_2022-10-14T09:05:53.926268924.txt Defaulted container "oam-pod" out of: oam-pod, apache Transaction Log received from Instance: SMF.nodemgr.DC.SMF.1 ************* TRANSACTION: 00166 *************
TRANSACTION SUCCESS: Start Time : 2022/10/14 09:07:24.449 GR Instance ID : 1 Txn Type : GtpcAssocEstReq(2114) Priority : 1 Session Namespace : none(0) CDL Slice Name : 1 LOG MESSAGES: 2022/10/14 09:07:24.449 [TRACE] [infra.message_log.core] >>>>>>>> IPC message Name: GtpcAssocEstReq MessageType: GtpcAssocEstReq Key: --body--
{"IPv4address":167844075,"restart_counter":65535, "nodemgr_instance_id":1,"timestamp":1665738444, "gtpcPathStatus":2,"gtpcInterfaceType":4,"ddnInfo":{}, "gr_instance_id":1,"isNodeStarted":true} 2022/10/14 09:07:24.449 [DEBUG] [nodemgr1.app.Int] GetSessionNamespace for txn id: 166, Type: 2114 2022/10/14 09:07:24.449 [DEBUG] [nodemgr.gtpmgr.gtp] Received New GTP Peer info [&GtpcAssocEstReq{IPv4Address:167844075,IPv6Address:[],SupportedFeatures:0,RestartCounter:65535, NodemgrInstanceId:1,Timestamp:1665738444,OverloadControl:nil,GtpcPathStatus:GTPC_PATH_UP, GtpcInterfaceType:4,DdnInfo:&DdnInfo{DelayValid:false,ThrottleValRcvd:false,ThrottleActive:false, DelayValue:0,ThrottleDelayValue:0,ThrottleDelayUnit:0,ThrottleFactor:0,},GrInstanceId:1, IsNodeStarted:true,SelfRCVal:0,PeerType:0,DeletedAt:0,}] 2022/10/14 09:07:24.449 [INFO] [nodemgr.gtpmgr.gtp] GTPC Path Mgmt Disabled for interface [4] 2022/10/14 09:07:24.449 [INFO] [nodemgr.gtpmgr.gtp] Rcvd timestamp 1665738444, stored timestamp 1665738177 peer 10.1.24.235 2022/10/14 09:07:24.449 [DEBUG] [nodemgr.gtpmgr.gtp] Assoc req for already present peer [10.1.24.235] 2022/10/14 09:07:24.449 [DEBUG] [nodemgr.gtpmgr.gtp] stop timer for existing gtp-peer [10.1.24.235] 2022/10/14 09:07:24.451 [TRACE] [infra.message_log.core] <<<<<<<<
*********************************************** Transaction Log received from Instance: SMF.nodemgr.DC.SMF.1 ************* TRANSACTION: 00167 ************* TRANSACTION SUCCESS: Start Time : 2022/10/14 09:07:34.061 GR Instance ID : 1 Txn Type : GtpcAssocEstReq(2114) Priority : 1 Session Namespace : none(0) CDL Slice Name : 1 LOG MESSAGES: 2022/10/14 09:07:34.062 [TRACE] [infra.message_log.core] >>>>>>>> IPC message Name: GtpcAssocEstReq MessageType: GtpcAssocEstReq Key: --body--
{"IPv4address":167844075,"restart_counter":100,"timestamp":1665738454,"gtpcInterfaceType":4, "ddnInfo":{},"isNodeStarted":true} 2022/10/14 09:07:34.062 [DEBUG] [nodemgr1.app.Int] GetSessionNamespace for txn id: 167, Type: 2114 2022/10/14 09:07:34.062 [DEBUG] [nodemgr.gtpmgr.gtp] Received New GTP Peer info [&GtpcAssocEstReq{IPv4Address:167844075,IPv6Address:[],SupportedFeatures:0,RestartCounter:100, NodemgrInstanceId:0,Timestamp:1665738454,OverloadControl:nil,GtpcPathStatus:GTP_PATH_INVALID, GtpcInterfaceType:4,DdnInfo:&DdnInfo{DelayValid:false,ThrottleValRcvd:false,ThrottleActive:false, DelayValue:0,ThrottleDelayValue:0,ThrottleDelayUnit:0,ThrottleFactor:0,},GrInstanceId:0, IsNodeStarted:true,SelfRCVal:0,PeerType:0,DeletedAt:0,}] 2022/10/14 09:07:34.062 [INFO] [nodemgr.gtpmgr.gtp] GTPC Path Mgmt Disabled for interface [4] 2022/10/14 09:07:34.062 [INFO] [nodemgr.gtpmgr.gtp] Rcvd timestamp 1665738454, stored timestamp 1665738444 peer 10.1.24.235 2022/10/14 09:07:34.062 [DEBUG] [nodemgr.gtpmgr.gtp] Assoc req for already present peer [10.1.24.235] 2022/10/14 09:07:34.062 [DEBUG] [nodemgr.gtpmgr.gtp] stop timer for existing gtp-peer [10.1.24.235] 2022/10/14 09:07:34.065 [TRACE] [infra.message_log.core] <<<<<<<< ***********************************************