HRG CDR

The HTTP Resource Generator (HRG) produces a CDR for each attempt to create an HTTP request through the Platform Management Interface (PMI), the user interface on which requests are generated.

This is written by the CDR Handler or by the HRG through logging and is configured in application.properties.
Field Name Description

1

MSISDN

The subscriber’s MSISDN, a unique identifier.

2

serviceId

The CDR service ID; HRG = 87.

3

transactionType

The type of transaction. The following values are possible:

  • 1 = Request Successful

  • 2 = Request Unsuccessful: No Handler Matched

  • 3 = Request Unsuccessful: Server Error

  • 4 = Request Unsuccessful: Internal Error

4

dateStamp

The date when the CDR was produced. Format: YYYY:MM:DD

5

timeStamp

The time when the CDR was produced. Format: hh:mm:ss.

6

calllReference

The reference to the specific call. The call reference is a unique ID produced by the calling system.

7

parametersMatched

The parameters sent by the calling system that triggered a request handler in the HRG to produce the request.

8

requestHandlerName

The name of the request handler that the HRG used to handle the request.

9

requestReceivedTime

The time the request handler was received by the connection server. Format: hh:mm:ss.

10

connectionGroupName

The name of the group of connection servers.

These fields are not present in Transaction Type 2.

11

connectionNames

The name of the individual connection servers.

These fields will not be present in Transaction Type 2. In the case where the first server does not respond but a second server responds on the retry, this CDR field contains the names of both separated by a pipe delimiter character.

12

connectionRetries

The number of retries where the HRG tried to contact the server.

These fields will not be present in Transaction Type 2.

13

serverResponseTimes

The number of times the server responded.

These fields will not be present in Transaction Type 2. In the case where the first server does not respond but a second server responds on the retry, this CDR field contains the response times of both attempts separated by a pipe delimiter character.

14

serverResponseCodes

The server response code.

These fields will not be present in Transaction Type 2. In the case where the first server does not respond but a second server responds on the retry, this CDR field contains the server response codes of both attempts separated by a pipe delimiter character.

15

hrgResponseCode

The HRG Response Code.

16

hrgResponseTime

The time at which the HRG responded. Format: hh:mm:ss.

17

authConnectionGroupName

The name of the group of connection servers used for Pre-Authorization.

18

authConnectionNames

The name of the individual connection servers used for the Pre-Authorization Request.

In the case where the first server does not respond but a second server responds on the retry, this CDR field contains the names of both separated by a | character. For example: HRG|HRG ssrva.

19

authConnectionRetries

The number of retries where the HRG tried to contact the Pre-Authorization Server.

20

authServerResponseTimes

The duration of time in milliseconds it took for the the for the Pre-Authorization Server(s) to respond.

In the case where the server request fails and subsequent requests are attempted, this CDR field contains the response times of all attempts separated by a | character. For example: 3000|23.

21

authserverResponseCodes

The HTTP Status codes returned from the Pre-Authorization Server(s).

In the case where the server request fails and subsequent requests are attempted, this CDR field contains the response codes of all attempts separated by a | character. For example: null|200.