Message processing input statistics
The following are message processing input statistics generated by the Diameter Routing Agent (DRA).
|
The total number of Diameter requests that failed to decode encountered by the DRA. |
||
|
The total number of Diameter requests where bindings were not found by the DRA.
|
||
|
The total number of Diameter requests for unsupported applications encountered by the DRA. |
||
|
The total number of Diameter requests with loop detection encountered by the DRA. |
||
|
The total number of invalid request messages. |
||
|
The total number of Diameter request forwarding failures encountered by the DRA. |
||
|
The total number of Diameter answers failed to decode encountered by the DRA. |
||
|
The total number of answers needed that does not match a known Hop-by-Hop Identifier. |
||
|
The total number of invalid Diameter answers message requests encountered by the DRA. |
||
|
The total number of Diameter request forwarding failures encountered by the DRA. |
||
|
The total number of Diameter requests that failed to connect to an agent node (DIR). |
||
|
The total number of Diameter requests received by the DRA(proxy-lite) that failed to forward to a destination DRA (legacy) pair due to the subscriber route being blocked. |
||
|
The total number of Diameter requests that could not be forwarded by the PCRF server peer due to it being manually blocked. |