rw-monitor-log - User documentation

Schema Globals

Global Schema Type	rw_ypbc_RwMonitorLog_RwMonitorLog_t_schema
Global Schema Pointer	rw_ypbc_RwMonitorLog_RwMonitorLog_g_schema

rw-monitor-log notification

rw-monitor-log:debug

Generic Debug Log

Key Identifiers:

XPath Path	/rw-monitor-log:debug
XPath Keyed Path	/rw-monitor-log:debug
RW.REST URI Path	/rw-monitor-log:debug

Fields

Name	Type	Description
template_params	CONTAINER
category	STRING
logger	STRING
log	STRING

JSON Sample

{
  "template_params": {
    "event-id": 0,
    "version": 0,
    "sequence": 0,
    "sec": 0,
    "usec": 0,
    "system-id": 0,
    "hostname": "STRING",
    "appname": "STRING",
    "processid": 0,
    "threadid": 0,
    "filename": "STRING",
    "linenumber": 0,
    "severity": "debug",
    "crit-info": "false",
    "call-arrived-time": 0,
    "call-failure": true,
    "call-identifier": { ... },
    "session-params": { ... }
  },
  "category": "STRING",
  "logger": "STRING",
  "log": "STRING"
}

XML Sample

<rw-monitor-log:debug xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:template_params>
    <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
    <rw-monitor-log:version>0</rw-monitor-log:version>
    <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
    <rw-monitor-log:sec>0</rw-monitor-log:sec>
    <rw-monitor-log:usec>0</rw-monitor-log:usec>
    <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
    <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
    <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
    <rw-monitor-log:processid>0</rw-monitor-log:processid>
    <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
    <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
    <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
    <rw-monitor-log:severity>debug</rw-monitor-log:severity>
    <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
    <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
    <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
    <rw-monitor-log:call-identifier>...</rw-monitor-log:call-identifier>
    <rw-monitor-log:session-params>...</rw-monitor-log:session-params>
  </rw-monitor-log:template_params>
  <rw-monitor-log:category>STRING</rw-monitor-log:category>
  <rw-monitor-log:logger>STRING</rw-monitor-log:logger>
  <rw-monitor-log:log>STRING</rw-monitor-log:log>
</rw-monitor-log:debug>

rw-monitor-log:template_params

Key Identifiers:

XPath Path	/rw-monitor-log:debug/rw-monitor-log:template_params
XPath Keyed Path	/rw-monitor-log:debug/rw-monitor-log:template_params
RW.REST URI Path	/rw-monitor-log:debug/template_params

Fields

Name	Type	Description
event-id	UINT32
version	UINT32
sequence	UINT64
sec	UINT32
usec	UINT32
system-id	UINT32
hostname	STRING
appname	STRING
processid	UINT32
threadid	UINT32
filename	STRING
linenumber	UINT32
severity	ENUM
crit-info	ENUM
call-arrived-time	UINT32	Call arrived time
call-failure	BOOLEAN	Call failure status
call-identifier	CONTAINER	Each call in Riftware is assigned a callid which is unique in the context of the entity making the assignment. The same call-id could be assigned by different entities - in which case, the group-call-id is used in conjunction with call id to provide uniqueness
session-params	CONTAINER	Session parametes

JSON Config Sample

{
  "event-id": 0,
  "version": 0,
  "sequence": 0,
  "sec": 0,
  "usec": 0,
  "system-id": 0,
  "hostname": "STRING",
  "appname": "STRING",
  "processid": 0,
  "threadid": 0,
  "filename": "STRING",
  "linenumber": 0,
  "severity": "debug",
  "crit-info": "false",
  "call-arrived-time": 0,
  "call-failure": true,
  "call-identifier": {
    "callid": 0,
    "groupcallid": 0
  },
  "session-params": {
    "imsi": "STRING",
    "ip-address": "UNION_VALUE"
  }
}

JSON Sample

{
  "event-id": 0,
  "version": 0,
  "sequence": 0,
  "sec": 0,
  "usec": 0,
  "system-id": 0,
  "hostname": "STRING",
  "appname": "STRING",
  "processid": 0,
  "threadid": 0,
  "filename": "STRING",
  "linenumber": 0,
  "severity": "debug",
  "crit-info": "false",
  "call-arrived-time": 0,
  "call-failure": true,
  "call-identifier": {
    "callid": 0,
    "groupcallid": 0
  },
  "session-params": {
    "imsi": "STRING",
    "ip-address": "UNION_VALUE"
  }
}

XML Config Sample

<rw-monitor-log:template_params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
  <rw-monitor-log:version>0</rw-monitor-log:version>
  <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
  <rw-monitor-log:sec>0</rw-monitor-log:sec>
  <rw-monitor-log:usec>0</rw-monitor-log:usec>
  <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
  <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
  <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
  <rw-monitor-log:processid>0</rw-monitor-log:processid>
  <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
  <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
  <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
  <rw-monitor-log:severity>debug</rw-monitor-log:severity>
  <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
  <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
  <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
  <rw-monitor-log:call-identifier>
    <rw-monitor-log:callid>0</rw-monitor-log:callid>
    <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
  </rw-monitor-log:call-identifier>
  <rw-monitor-log:session-params>
    <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
    <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
  </rw-monitor-log:session-params>
</rw-monitor-log:template_params>

XML Sample

<rw-monitor-log:template_params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
  <rw-monitor-log:version>0</rw-monitor-log:version>
  <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
  <rw-monitor-log:sec>0</rw-monitor-log:sec>
  <rw-monitor-log:usec>0</rw-monitor-log:usec>
  <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
  <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
  <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
  <rw-monitor-log:processid>0</rw-monitor-log:processid>
  <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
  <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
  <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
  <rw-monitor-log:severity>debug</rw-monitor-log:severity>
  <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
  <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
  <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
  <rw-monitor-log:call-identifier>
    <rw-monitor-log:callid>0</rw-monitor-log:callid>
    <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
  </rw-monitor-log:call-identifier>
  <rw-monitor-log:session-params>
    <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
    <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
  </rw-monitor-log:session-params>
</rw-monitor-log:template_params>

rw-monitor-log:call-identifier

Each call in Riftware is assigned a callid which is unique in the context of the entity making the assignment. The same call-id could be assigned by different entities - in which case, the group-call-id is used in conjunction with call id to provide uniqueness

Key Identifiers:

XPath Path

/rw-monitor-log:debug/rw-monitor-log:template_params/rw-monitor-log:call-identifier

XPath Keyed Path

/rw-monitor-log:debug/rw-monitor-log:template_params/rw-monitor-log:call-identifier

RW.REST URI Path

/rw-monitor-log:debug/template_params/call-identifier

Fields

Name	Type	Description
callid	UINT64	The callid is defined as a grouping with a leaf that represents the callid. This helps in RIFTWARE use a common tag for call-id in all further uses of this grouping.
groupcallid	UINT64	The group call id is used to uniquely identify the assigner of a call id. Each entity generating call id within RIFTWARE uses group ids that are different from each other. A single entity could use multiple group ids - The caveat being that none of these group ids should be avaialble for other entities to use

JSON Config Sample

{
  "callid": 0,
  "groupcallid": 0
}

JSON Sample

{
  "callid": 0,
  "groupcallid": 0
}

XML Config Sample

<rw-monitor-log:call-identifier xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:callid>0</rw-monitor-log:callid>
  <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
</rw-monitor-log:call-identifier>

XML Sample

<rw-monitor-log:call-identifier xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:callid>0</rw-monitor-log:callid>
  <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
</rw-monitor-log:call-identifier>

rw-monitor-log:session-params

Session parametes

Key Identifiers:

XPath Path

/rw-monitor-log:debug/rw-monitor-log:template_params/rw-monitor-log:session-params

XPath Keyed Path

/rw-monitor-log:debug/rw-monitor-log:template_params/rw-monitor-log:session-params

RW.REST URI Path

/rw-monitor-log:debug/template_params/session-params

Fields

Name	Type	Description
imsi	STRING	IMSI for the session
ip-address	UNION	IP Address for the session

JSON Config Sample

{
  "imsi": "STRING",
  "ip-address": "UNION_VALUE"
}

JSON Sample

{
  "imsi": "STRING",
  "ip-address": "UNION_VALUE"
}

XML Config Sample

<rw-monitor-log:session-params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
  <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
</rw-monitor-log:session-params>

XML Sample

<rw-monitor-log:session-params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
  <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
</rw-monitor-log:session-params>

rw-monitor-log:info

Generic Info Log

Key Identifiers:

XPath Path	/rw-monitor-log:info
XPath Keyed Path	/rw-monitor-log:info
RW.REST URI Path	/rw-monitor-log:info

Fields

Name	Type	Description
template_params	CONTAINER
category	STRING
logger	STRING
log	STRING

JSON Sample

{
  "template_params": {
    "event-id": 0,
    "version": 0,
    "sequence": 0,
    "sec": 0,
    "usec": 0,
    "system-id": 0,
    "hostname": "STRING",
    "appname": "STRING",
    "processid": 0,
    "threadid": 0,
    "filename": "STRING",
    "linenumber": 0,
    "severity": "info",
    "crit-info": "false",
    "call-arrived-time": 0,
    "call-failure": true,
    "call-identifier": { ... },
    "session-params": { ... }
  },
  "category": "STRING",
  "logger": "STRING",
  "log": "STRING"
}

XML Sample

<rw-monitor-log:info xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:template_params>
    <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
    <rw-monitor-log:version>0</rw-monitor-log:version>
    <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
    <rw-monitor-log:sec>0</rw-monitor-log:sec>
    <rw-monitor-log:usec>0</rw-monitor-log:usec>
    <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
    <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
    <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
    <rw-monitor-log:processid>0</rw-monitor-log:processid>
    <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
    <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
    <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
    <rw-monitor-log:severity>info</rw-monitor-log:severity>
    <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
    <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
    <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
    <rw-monitor-log:call-identifier>...</rw-monitor-log:call-identifier>
    <rw-monitor-log:session-params>...</rw-monitor-log:session-params>
  </rw-monitor-log:template_params>
  <rw-monitor-log:category>STRING</rw-monitor-log:category>
  <rw-monitor-log:logger>STRING</rw-monitor-log:logger>
  <rw-monitor-log:log>STRING</rw-monitor-log:log>
</rw-monitor-log:info>

rw-monitor-log:template_params

Key Identifiers:

XPath Path	/rw-monitor-log:info/rw-monitor-log:template_params
XPath Keyed Path	/rw-monitor-log:info/rw-monitor-log:template_params
RW.REST URI Path	/rw-monitor-log:info/template_params

Fields

Name	Type	Description
event-id	UINT32
version	UINT32
sequence	UINT64
sec	UINT32
usec	UINT32
system-id	UINT32
hostname	STRING
appname	STRING
processid	UINT32
threadid	UINT32
filename	STRING
linenumber	UINT32
severity	ENUM
crit-info	ENUM
call-arrived-time	UINT32	Call arrived time
call-failure	BOOLEAN	Call failure status
call-identifier	CONTAINER	Each call in Riftware is assigned a callid which is unique in the context of the entity making the assignment. The same call-id could be assigned by different entities - in which case, the group-call-id is used in conjunction with call id to provide uniqueness
session-params	CONTAINER	Session parametes

JSON Config Sample

{
  "event-id": 0,
  "version": 0,
  "sequence": 0,
  "sec": 0,
  "usec": 0,
  "system-id": 0,
  "hostname": "STRING",
  "appname": "STRING",
  "processid": 0,
  "threadid": 0,
  "filename": "STRING",
  "linenumber": 0,
  "severity": "info",
  "crit-info": "false",
  "call-arrived-time": 0,
  "call-failure": true,
  "call-identifier": {
    "callid": 0,
    "groupcallid": 0
  },
  "session-params": {
    "imsi": "STRING",
    "ip-address": "UNION_VALUE"
  }
}

JSON Sample

{
  "event-id": 0,
  "version": 0,
  "sequence": 0,
  "sec": 0,
  "usec": 0,
  "system-id": 0,
  "hostname": "STRING",
  "appname": "STRING",
  "processid": 0,
  "threadid": 0,
  "filename": "STRING",
  "linenumber": 0,
  "severity": "info",
  "crit-info": "false",
  "call-arrived-time": 0,
  "call-failure": true,
  "call-identifier": {
    "callid": 0,
    "groupcallid": 0
  },
  "session-params": {
    "imsi": "STRING",
    "ip-address": "UNION_VALUE"
  }
}

XML Config Sample

<rw-monitor-log:template_params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
  <rw-monitor-log:version>0</rw-monitor-log:version>
  <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
  <rw-monitor-log:sec>0</rw-monitor-log:sec>
  <rw-monitor-log:usec>0</rw-monitor-log:usec>
  <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
  <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
  <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
  <rw-monitor-log:processid>0</rw-monitor-log:processid>
  <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
  <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
  <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
  <rw-monitor-log:severity>info</rw-monitor-log:severity>
  <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
  <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
  <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
  <rw-monitor-log:call-identifier>
    <rw-monitor-log:callid>0</rw-monitor-log:callid>
    <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
  </rw-monitor-log:call-identifier>
  <rw-monitor-log:session-params>
    <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
    <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
  </rw-monitor-log:session-params>
</rw-monitor-log:template_params>

XML Sample

<rw-monitor-log:template_params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
  <rw-monitor-log:version>0</rw-monitor-log:version>
  <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
  <rw-monitor-log:sec>0</rw-monitor-log:sec>
  <rw-monitor-log:usec>0</rw-monitor-log:usec>
  <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
  <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
  <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
  <rw-monitor-log:processid>0</rw-monitor-log:processid>
  <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
  <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
  <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
  <rw-monitor-log:severity>info</rw-monitor-log:severity>
  <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
  <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
  <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
  <rw-monitor-log:call-identifier>
    <rw-monitor-log:callid>0</rw-monitor-log:callid>
    <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
  </rw-monitor-log:call-identifier>
  <rw-monitor-log:session-params>
    <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
    <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
  </rw-monitor-log:session-params>
</rw-monitor-log:template_params>

rw-monitor-log:call-identifier

Key Identifiers:

XPath Path

/rw-monitor-log:info/rw-monitor-log:template_params/rw-monitor-log:call-identifier

XPath Keyed Path

/rw-monitor-log:info/rw-monitor-log:template_params/rw-monitor-log:call-identifier

RW.REST URI Path

/rw-monitor-log:info/template_params/call-identifier

Fields

Name	Type	Description
callid	UINT64	The callid is defined as a grouping with a leaf that represents the callid. This helps in RIFTWARE use a common tag for call-id in all further uses of this grouping.
groupcallid	UINT64	The group call id is used to uniquely identify the assigner of a call id. Each entity generating call id within RIFTWARE uses group ids that are different from each other. A single entity could use multiple group ids - The caveat being that none of these group ids should be avaialble for other entities to use

JSON Config Sample

{
  "callid": 0,
  "groupcallid": 0
}

JSON Sample

{
  "callid": 0,
  "groupcallid": 0
}

XML Config Sample

<rw-monitor-log:call-identifier xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:callid>0</rw-monitor-log:callid>
  <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
</rw-monitor-log:call-identifier>

XML Sample

<rw-monitor-log:call-identifier xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:callid>0</rw-monitor-log:callid>
  <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
</rw-monitor-log:call-identifier>

rw-monitor-log:session-params

Session parametes

Key Identifiers:

XPath Path

/rw-monitor-log:info/rw-monitor-log:template_params/rw-monitor-log:session-params

XPath Keyed Path

/rw-monitor-log:info/rw-monitor-log:template_params/rw-monitor-log:session-params

RW.REST URI Path

/rw-monitor-log:info/template_params/session-params

Fields

Name	Type	Description
imsi	STRING	IMSI for the session
ip-address	UNION	IP Address for the session

JSON Config Sample

{
  "imsi": "STRING",
  "ip-address": "UNION_VALUE"
}

JSON Sample

{
  "imsi": "STRING",
  "ip-address": "UNION_VALUE"
}

XML Config Sample

<rw-monitor-log:session-params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
  <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
</rw-monitor-log:session-params>

XML Sample

<rw-monitor-log:session-params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
  <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
</rw-monitor-log:session-params>

rw-monitor-log:warn

Generic Warning Log

Key Identifiers:

XPath Path	/rw-monitor-log:warn
XPath Keyed Path	/rw-monitor-log:warn
RW.REST URI Path	/rw-monitor-log:warn

Fields

Name	Type	Description
template_params	CONTAINER
category	STRING
logger	STRING
log	STRING

JSON Sample

{
  "template_params": {
    "event-id": 0,
    "version": 0,
    "sequence": 0,
    "sec": 0,
    "usec": 0,
    "system-id": 0,
    "hostname": "STRING",
    "appname": "STRING",
    "processid": 0,
    "threadid": 0,
    "filename": "STRING",
    "linenumber": 0,
    "severity": "warning",
    "crit-info": "false",
    "call-arrived-time": 0,
    "call-failure": true,
    "call-identifier": { ... },
    "session-params": { ... }
  },
  "category": "STRING",
  "logger": "STRING",
  "log": "STRING"
}

XML Sample

<rw-monitor-log:warn xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:template_params>
    <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
    <rw-monitor-log:version>0</rw-monitor-log:version>
    <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
    <rw-monitor-log:sec>0</rw-monitor-log:sec>
    <rw-monitor-log:usec>0</rw-monitor-log:usec>
    <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
    <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
    <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
    <rw-monitor-log:processid>0</rw-monitor-log:processid>
    <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
    <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
    <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
    <rw-monitor-log:severity>warning</rw-monitor-log:severity>
    <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
    <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
    <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
    <rw-monitor-log:call-identifier>...</rw-monitor-log:call-identifier>
    <rw-monitor-log:session-params>...</rw-monitor-log:session-params>
  </rw-monitor-log:template_params>
  <rw-monitor-log:category>STRING</rw-monitor-log:category>
  <rw-monitor-log:logger>STRING</rw-monitor-log:logger>
  <rw-monitor-log:log>STRING</rw-monitor-log:log>
</rw-monitor-log:warn>

rw-monitor-log:template_params

Key Identifiers:

XPath Path	/rw-monitor-log:warn/rw-monitor-log:template_params
XPath Keyed Path	/rw-monitor-log:warn/rw-monitor-log:template_params
RW.REST URI Path	/rw-monitor-log:warn/template_params

Fields

Name	Type	Description
event-id	UINT32
version	UINT32
sequence	UINT64
sec	UINT32
usec	UINT32
system-id	UINT32
hostname	STRING
appname	STRING
processid	UINT32
threadid	UINT32
filename	STRING
linenumber	UINT32
severity	ENUM
crit-info	ENUM
call-arrived-time	UINT32	Call arrived time
call-failure	BOOLEAN	Call failure status
call-identifier	CONTAINER	Each call in Riftware is assigned a callid which is unique in the context of the entity making the assignment. The same call-id could be assigned by different entities - in which case, the group-call-id is used in conjunction with call id to provide uniqueness
session-params	CONTAINER	Session parametes

JSON Config Sample

{
  "event-id": 0,
  "version": 0,
  "sequence": 0,
  "sec": 0,
  "usec": 0,
  "system-id": 0,
  "hostname": "STRING",
  "appname": "STRING",
  "processid": 0,
  "threadid": 0,
  "filename": "STRING",
  "linenumber": 0,
  "severity": "warning",
  "crit-info": "false",
  "call-arrived-time": 0,
  "call-failure": true,
  "call-identifier": {
    "callid": 0,
    "groupcallid": 0
  },
  "session-params": {
    "imsi": "STRING",
    "ip-address": "UNION_VALUE"
  }
}

JSON Sample

{
  "event-id": 0,
  "version": 0,
  "sequence": 0,
  "sec": 0,
  "usec": 0,
  "system-id": 0,
  "hostname": "STRING",
  "appname": "STRING",
  "processid": 0,
  "threadid": 0,
  "filename": "STRING",
  "linenumber": 0,
  "severity": "warning",
  "crit-info": "false",
  "call-arrived-time": 0,
  "call-failure": true,
  "call-identifier": {
    "callid": 0,
    "groupcallid": 0
  },
  "session-params": {
    "imsi": "STRING",
    "ip-address": "UNION_VALUE"
  }
}

XML Config Sample

<rw-monitor-log:template_params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
  <rw-monitor-log:version>0</rw-monitor-log:version>
  <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
  <rw-monitor-log:sec>0</rw-monitor-log:sec>
  <rw-monitor-log:usec>0</rw-monitor-log:usec>
  <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
  <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
  <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
  <rw-monitor-log:processid>0</rw-monitor-log:processid>
  <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
  <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
  <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
  <rw-monitor-log:severity>warning</rw-monitor-log:severity>
  <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
  <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
  <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
  <rw-monitor-log:call-identifier>
    <rw-monitor-log:callid>0</rw-monitor-log:callid>
    <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
  </rw-monitor-log:call-identifier>
  <rw-monitor-log:session-params>
    <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
    <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
  </rw-monitor-log:session-params>
</rw-monitor-log:template_params>

XML Sample

<rw-monitor-log:template_params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
  <rw-monitor-log:version>0</rw-monitor-log:version>
  <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
  <rw-monitor-log:sec>0</rw-monitor-log:sec>
  <rw-monitor-log:usec>0</rw-monitor-log:usec>
  <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
  <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
  <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
  <rw-monitor-log:processid>0</rw-monitor-log:processid>
  <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
  <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
  <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
  <rw-monitor-log:severity>warning</rw-monitor-log:severity>
  <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
  <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
  <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
  <rw-monitor-log:call-identifier>
    <rw-monitor-log:callid>0</rw-monitor-log:callid>
    <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
  </rw-monitor-log:call-identifier>
  <rw-monitor-log:session-params>
    <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
    <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
  </rw-monitor-log:session-params>
</rw-monitor-log:template_params>

rw-monitor-log:call-identifier

Key Identifiers:

XPath Path

/rw-monitor-log:warn/rw-monitor-log:template_params/rw-monitor-log:call-identifier

XPath Keyed Path

/rw-monitor-log:warn/rw-monitor-log:template_params/rw-monitor-log:call-identifier

RW.REST URI Path

/rw-monitor-log:warn/template_params/call-identifier

Fields

Name	Type	Description
callid	UINT64	The callid is defined as a grouping with a leaf that represents the callid. This helps in RIFTWARE use a common tag for call-id in all further uses of this grouping.
groupcallid	UINT64	The group call id is used to uniquely identify the assigner of a call id. Each entity generating call id within RIFTWARE uses group ids that are different from each other. A single entity could use multiple group ids - The caveat being that none of these group ids should be avaialble for other entities to use

JSON Config Sample

{
  "callid": 0,
  "groupcallid": 0
}

JSON Sample

{
  "callid": 0,
  "groupcallid": 0
}

XML Config Sample

<rw-monitor-log:call-identifier xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:callid>0</rw-monitor-log:callid>
  <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
</rw-monitor-log:call-identifier>

XML Sample

<rw-monitor-log:call-identifier xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:callid>0</rw-monitor-log:callid>
  <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
</rw-monitor-log:call-identifier>

rw-monitor-log:session-params

Session parametes

Key Identifiers:

XPath Path

/rw-monitor-log:warn/rw-monitor-log:template_params/rw-monitor-log:session-params

XPath Keyed Path

/rw-monitor-log:warn/rw-monitor-log:template_params/rw-monitor-log:session-params

RW.REST URI Path

/rw-monitor-log:warn/template_params/session-params

Fields

Name	Type	Description
imsi	STRING	IMSI for the session
ip-address	UNION	IP Address for the session

JSON Config Sample

{
  "imsi": "STRING",
  "ip-address": "UNION_VALUE"
}

JSON Sample

{
  "imsi": "STRING",
  "ip-address": "UNION_VALUE"
}

XML Config Sample

<rw-monitor-log:session-params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
  <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
</rw-monitor-log:session-params>

XML Sample

<rw-monitor-log:session-params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
  <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
</rw-monitor-log:session-params>

rw-monitor-log:error

Generic Error Log

Key Identifiers:

XPath Path	/rw-monitor-log:error
XPath Keyed Path	/rw-monitor-log:error
RW.REST URI Path	/rw-monitor-log:error

Fields

Name	Type	Description
template_params	CONTAINER
category	STRING
logger	STRING
log	STRING

JSON Sample

{
  "template_params": {
    "event-id": 0,
    "version": 0,
    "sequence": 0,
    "sec": 0,
    "usec": 0,
    "system-id": 0,
    "hostname": "STRING",
    "appname": "STRING",
    "processid": 0,
    "threadid": 0,
    "filename": "STRING",
    "linenumber": 0,
    "severity": "error",
    "crit-info": "false",
    "call-arrived-time": 0,
    "call-failure": true,
    "call-identifier": { ... },
    "session-params": { ... }
  },
  "category": "STRING",
  "logger": "STRING",
  "log": "STRING"
}

XML Sample

<rw-monitor-log:error xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:template_params>
    <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
    <rw-monitor-log:version>0</rw-monitor-log:version>
    <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
    <rw-monitor-log:sec>0</rw-monitor-log:sec>
    <rw-monitor-log:usec>0</rw-monitor-log:usec>
    <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
    <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
    <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
    <rw-monitor-log:processid>0</rw-monitor-log:processid>
    <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
    <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
    <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
    <rw-monitor-log:severity>error</rw-monitor-log:severity>
    <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
    <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
    <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
    <rw-monitor-log:call-identifier>...</rw-monitor-log:call-identifier>
    <rw-monitor-log:session-params>...</rw-monitor-log:session-params>
  </rw-monitor-log:template_params>
  <rw-monitor-log:category>STRING</rw-monitor-log:category>
  <rw-monitor-log:logger>STRING</rw-monitor-log:logger>
  <rw-monitor-log:log>STRING</rw-monitor-log:log>
</rw-monitor-log:error>

rw-monitor-log:template_params

Key Identifiers:

XPath Path	/rw-monitor-log:error/rw-monitor-log:template_params
XPath Keyed Path	/rw-monitor-log:error/rw-monitor-log:template_params
RW.REST URI Path	/rw-monitor-log:error/template_params

Fields

Name	Type	Description
event-id	UINT32
version	UINT32
sequence	UINT64
sec	UINT32
usec	UINT32
system-id	UINT32
hostname	STRING
appname	STRING
processid	UINT32
threadid	UINT32
filename	STRING
linenumber	UINT32
severity	ENUM
crit-info	ENUM
call-arrived-time	UINT32	Call arrived time
call-failure	BOOLEAN	Call failure status
call-identifier	CONTAINER	Each call in Riftware is assigned a callid which is unique in the context of the entity making the assignment. The same call-id could be assigned by different entities - in which case, the group-call-id is used in conjunction with call id to provide uniqueness
session-params	CONTAINER	Session parametes

JSON Config Sample

{
  "event-id": 0,
  "version": 0,
  "sequence": 0,
  "sec": 0,
  "usec": 0,
  "system-id": 0,
  "hostname": "STRING",
  "appname": "STRING",
  "processid": 0,
  "threadid": 0,
  "filename": "STRING",
  "linenumber": 0,
  "severity": "error",
  "crit-info": "false",
  "call-arrived-time": 0,
  "call-failure": true,
  "call-identifier": {
    "callid": 0,
    "groupcallid": 0
  },
  "session-params": {
    "imsi": "STRING",
    "ip-address": "UNION_VALUE"
  }
}

JSON Sample

{
  "event-id": 0,
  "version": 0,
  "sequence": 0,
  "sec": 0,
  "usec": 0,
  "system-id": 0,
  "hostname": "STRING",
  "appname": "STRING",
  "processid": 0,
  "threadid": 0,
  "filename": "STRING",
  "linenumber": 0,
  "severity": "error",
  "crit-info": "false",
  "call-arrived-time": 0,
  "call-failure": true,
  "call-identifier": {
    "callid": 0,
    "groupcallid": 0
  },
  "session-params": {
    "imsi": "STRING",
    "ip-address": "UNION_VALUE"
  }
}

XML Config Sample

<rw-monitor-log:template_params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
  <rw-monitor-log:version>0</rw-monitor-log:version>
  <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
  <rw-monitor-log:sec>0</rw-monitor-log:sec>
  <rw-monitor-log:usec>0</rw-monitor-log:usec>
  <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
  <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
  <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
  <rw-monitor-log:processid>0</rw-monitor-log:processid>
  <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
  <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
  <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
  <rw-monitor-log:severity>error</rw-monitor-log:severity>
  <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
  <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
  <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
  <rw-monitor-log:call-identifier>
    <rw-monitor-log:callid>0</rw-monitor-log:callid>
    <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
  </rw-monitor-log:call-identifier>
  <rw-monitor-log:session-params>
    <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
    <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
  </rw-monitor-log:session-params>
</rw-monitor-log:template_params>

XML Sample

<rw-monitor-log:template_params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
  <rw-monitor-log:version>0</rw-monitor-log:version>
  <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
  <rw-monitor-log:sec>0</rw-monitor-log:sec>
  <rw-monitor-log:usec>0</rw-monitor-log:usec>
  <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
  <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
  <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
  <rw-monitor-log:processid>0</rw-monitor-log:processid>
  <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
  <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
  <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
  <rw-monitor-log:severity>error</rw-monitor-log:severity>
  <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
  <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
  <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
  <rw-monitor-log:call-identifier>
    <rw-monitor-log:callid>0</rw-monitor-log:callid>
    <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
  </rw-monitor-log:call-identifier>
  <rw-monitor-log:session-params>
    <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
    <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
  </rw-monitor-log:session-params>
</rw-monitor-log:template_params>

rw-monitor-log:call-identifier

Key Identifiers:

XPath Path

/rw-monitor-log:error/rw-monitor-log:template_params/rw-monitor-log:call-identifier

XPath Keyed Path

/rw-monitor-log:error/rw-monitor-log:template_params/rw-monitor-log:call-identifier

RW.REST URI Path

/rw-monitor-log:error/template_params/call-identifier

Fields

Name	Type	Description
callid	UINT64	The callid is defined as a grouping with a leaf that represents the callid. This helps in RIFTWARE use a common tag for call-id in all further uses of this grouping.
groupcallid	UINT64	The group call id is used to uniquely identify the assigner of a call id. Each entity generating call id within RIFTWARE uses group ids that are different from each other. A single entity could use multiple group ids - The caveat being that none of these group ids should be avaialble for other entities to use

JSON Config Sample

{
  "callid": 0,
  "groupcallid": 0
}

JSON Sample

{
  "callid": 0,
  "groupcallid": 0
}

XML Config Sample

<rw-monitor-log:call-identifier xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:callid>0</rw-monitor-log:callid>
  <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
</rw-monitor-log:call-identifier>

XML Sample

<rw-monitor-log:call-identifier xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:callid>0</rw-monitor-log:callid>
  <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
</rw-monitor-log:call-identifier>

rw-monitor-log:session-params

Session parametes

Key Identifiers:

XPath Path

/rw-monitor-log:error/rw-monitor-log:template_params/rw-monitor-log:session-params

XPath Keyed Path

/rw-monitor-log:error/rw-monitor-log:template_params/rw-monitor-log:session-params

RW.REST URI Path

/rw-monitor-log:error/template_params/session-params

Fields

Name	Type	Description
imsi	STRING	IMSI for the session
ip-address	UNION	IP Address for the session

JSON Config Sample

{
  "imsi": "STRING",
  "ip-address": "UNION_VALUE"
}

JSON Sample

{
  "imsi": "STRING",
  "ip-address": "UNION_VALUE"
}

XML Config Sample

<rw-monitor-log:session-params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
  <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
</rw-monitor-log:session-params>

XML Sample

<rw-monitor-log:session-params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
  <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
</rw-monitor-log:session-params>

rw-monitor-log:critical

Generic Critical Log

Key Identifiers:

XPath Path	/rw-monitor-log:critical
XPath Keyed Path	/rw-monitor-log:critical
RW.REST URI Path	/rw-monitor-log:critical

Fields

Name	Type	Description
template_params	CONTAINER
category	STRING
logger	STRING
log	STRING

JSON Sample

{
  "template_params": {
    "event-id": 0,
    "version": 0,
    "sequence": 0,
    "sec": 0,
    "usec": 0,
    "system-id": 0,
    "hostname": "STRING",
    "appname": "STRING",
    "processid": 0,
    "threadid": 0,
    "filename": "STRING",
    "linenumber": 0,
    "severity": "critical",
    "crit-info": "false",
    "call-arrived-time": 0,
    "call-failure": true,
    "call-identifier": { ... },
    "session-params": { ... }
  },
  "category": "STRING",
  "logger": "STRING",
  "log": "STRING"
}

XML Sample

<rw-monitor-log:critical xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:template_params>
    <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
    <rw-monitor-log:version>0</rw-monitor-log:version>
    <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
    <rw-monitor-log:sec>0</rw-monitor-log:sec>
    <rw-monitor-log:usec>0</rw-monitor-log:usec>
    <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
    <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
    <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
    <rw-monitor-log:processid>0</rw-monitor-log:processid>
    <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
    <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
    <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
    <rw-monitor-log:severity>critical</rw-monitor-log:severity>
    <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
    <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
    <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
    <rw-monitor-log:call-identifier>...</rw-monitor-log:call-identifier>
    <rw-monitor-log:session-params>...</rw-monitor-log:session-params>
  </rw-monitor-log:template_params>
  <rw-monitor-log:category>STRING</rw-monitor-log:category>
  <rw-monitor-log:logger>STRING</rw-monitor-log:logger>
  <rw-monitor-log:log>STRING</rw-monitor-log:log>
</rw-monitor-log:critical>

rw-monitor-log:template_params

Key Identifiers:

XPath Path	/rw-monitor-log:critical/rw-monitor-log:template_params
XPath Keyed Path	/rw-monitor-log:critical/rw-monitor-log:template_params
RW.REST URI Path	/rw-monitor-log:critical/template_params

Fields

Name	Type	Description
event-id	UINT32
version	UINT32
sequence	UINT64
sec	UINT32
usec	UINT32
system-id	UINT32
hostname	STRING
appname	STRING
processid	UINT32
threadid	UINT32
filename	STRING
linenumber	UINT32
severity	ENUM
crit-info	ENUM
call-arrived-time	UINT32	Call arrived time
call-failure	BOOLEAN	Call failure status
call-identifier	CONTAINER	Each call in Riftware is assigned a callid which is unique in the context of the entity making the assignment. The same call-id could be assigned by different entities - in which case, the group-call-id is used in conjunction with call id to provide uniqueness
session-params	CONTAINER	Session parametes

JSON Config Sample

{
  "event-id": 0,
  "version": 0,
  "sequence": 0,
  "sec": 0,
  "usec": 0,
  "system-id": 0,
  "hostname": "STRING",
  "appname": "STRING",
  "processid": 0,
  "threadid": 0,
  "filename": "STRING",
  "linenumber": 0,
  "severity": "critical",
  "crit-info": "false",
  "call-arrived-time": 0,
  "call-failure": true,
  "call-identifier": {
    "callid": 0,
    "groupcallid": 0
  },
  "session-params": {
    "imsi": "STRING",
    "ip-address": "UNION_VALUE"
  }
}

JSON Sample

{
  "event-id": 0,
  "version": 0,
  "sequence": 0,
  "sec": 0,
  "usec": 0,
  "system-id": 0,
  "hostname": "STRING",
  "appname": "STRING",
  "processid": 0,
  "threadid": 0,
  "filename": "STRING",
  "linenumber": 0,
  "severity": "critical",
  "crit-info": "false",
  "call-arrived-time": 0,
  "call-failure": true,
  "call-identifier": {
    "callid": 0,
    "groupcallid": 0
  },
  "session-params": {
    "imsi": "STRING",
    "ip-address": "UNION_VALUE"
  }
}

XML Config Sample

<rw-monitor-log:template_params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
  <rw-monitor-log:version>0</rw-monitor-log:version>
  <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
  <rw-monitor-log:sec>0</rw-monitor-log:sec>
  <rw-monitor-log:usec>0</rw-monitor-log:usec>
  <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
  <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
  <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
  <rw-monitor-log:processid>0</rw-monitor-log:processid>
  <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
  <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
  <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
  <rw-monitor-log:severity>critical</rw-monitor-log:severity>
  <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
  <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
  <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
  <rw-monitor-log:call-identifier>
    <rw-monitor-log:callid>0</rw-monitor-log:callid>
    <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
  </rw-monitor-log:call-identifier>
  <rw-monitor-log:session-params>
    <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
    <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
  </rw-monitor-log:session-params>
</rw-monitor-log:template_params>

XML Sample

<rw-monitor-log:template_params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:event-id>0</rw-monitor-log:event-id>
  <rw-monitor-log:version>0</rw-monitor-log:version>
  <rw-monitor-log:sequence>0</rw-monitor-log:sequence>
  <rw-monitor-log:sec>0</rw-monitor-log:sec>
  <rw-monitor-log:usec>0</rw-monitor-log:usec>
  <rw-monitor-log:system-id>0</rw-monitor-log:system-id>
  <rw-monitor-log:hostname>STRING</rw-monitor-log:hostname>
  <rw-monitor-log:appname>STRING</rw-monitor-log:appname>
  <rw-monitor-log:processid>0</rw-monitor-log:processid>
  <rw-monitor-log:threadid>0</rw-monitor-log:threadid>
  <rw-monitor-log:filename>STRING</rw-monitor-log:filename>
  <rw-monitor-log:linenumber>0</rw-monitor-log:linenumber>
  <rw-monitor-log:severity>critical</rw-monitor-log:severity>
  <rw-monitor-log:crit-info>false</rw-monitor-log:crit-info>
  <rw-monitor-log:call-arrived-time>0</rw-monitor-log:call-arrived-time>
  <rw-monitor-log:call-failure>true</rw-monitor-log:call-failure>
  <rw-monitor-log:call-identifier>
    <rw-monitor-log:callid>0</rw-monitor-log:callid>
    <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
  </rw-monitor-log:call-identifier>
  <rw-monitor-log:session-params>
    <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
    <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
  </rw-monitor-log:session-params>
</rw-monitor-log:template_params>

rw-monitor-log:call-identifier

Key Identifiers:

XPath Path

/rw-monitor-log:critical/rw-monitor-log:template_params/rw-monitor-log:call-identifier

XPath Keyed Path

/rw-monitor-log:critical/rw-monitor-log:template_params/rw-monitor-log:call-identifier

RW.REST URI Path

/rw-monitor-log:critical/template_params/call-identifier

Fields

Name	Type	Description
callid	UINT64	The callid is defined as a grouping with a leaf that represents the callid. This helps in RIFTWARE use a common tag for call-id in all further uses of this grouping.
groupcallid	UINT64	The group call id is used to uniquely identify the assigner of a call id. Each entity generating call id within RIFTWARE uses group ids that are different from each other. A single entity could use multiple group ids - The caveat being that none of these group ids should be avaialble for other entities to use

JSON Config Sample

{
  "callid": 0,
  "groupcallid": 0
}

JSON Sample

{
  "callid": 0,
  "groupcallid": 0
}

XML Config Sample

<rw-monitor-log:call-identifier xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:callid>0</rw-monitor-log:callid>
  <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
</rw-monitor-log:call-identifier>

XML Sample

<rw-monitor-log:call-identifier xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:callid>0</rw-monitor-log:callid>
  <rw-monitor-log:groupcallid>0</rw-monitor-log:groupcallid>
</rw-monitor-log:call-identifier>

rw-monitor-log:session-params

Session parametes

Key Identifiers:

XPath Path

/rw-monitor-log:critical/rw-monitor-log:template_params/rw-monitor-log:session-params

XPath Keyed Path

/rw-monitor-log:critical/rw-monitor-log:template_params/rw-monitor-log:session-params

RW.REST URI Path

/rw-monitor-log:critical/template_params/session-params

Fields

Name	Type	Description
imsi	STRING	IMSI for the session
ip-address	UNION	IP Address for the session

JSON Config Sample

{
  "imsi": "STRING",
  "ip-address": "UNION_VALUE"
}

JSON Sample

{
  "imsi": "STRING",
  "ip-address": "UNION_VALUE"
}

XML Config Sample

<rw-monitor-log:session-params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
  <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
</rw-monitor-log:session-params>

XML Sample

<rw-monitor-log:session-params xmlns:rw-monitor-log="http://riftio.com/ns/riftware-1.0/rw-monitor-log">
  <rw-monitor-log:imsi>STRING</rw-monitor-log:imsi>
  <rw-monitor-log:ip-address>UNION_VALUE</rw-monitor-log:ip-address>
</rw-monitor-log:session-params>