Adding Fields to Event Detail Records

You can add fields to an Event Detail Record (EDR) that is generated for usage and non-usage event types. The process is different for usage and non-usage EDRs. The process includes creating a new event type, creating a custom MATRIXX Data Container (MDC) to hold the extended EDRs, and specifying the fields to map into the extended EDR.

To map fields from the message MDC that do not exist in the standard message MDC, you also must add the necessary Diameter AVP to the Diameter Dictionary and map the AVP to a field in the message MDC.

Note: The Source Field and the Destination Field must have compatible data types. For example, you can copy an integer source field to an integer destination field, or a string source field to a string destination field.

For non-aggregated usage events, the Source Field and the Destination Field can be a list or an array. For example, you can copy a list of strings from the source container to a list of strings in the destination container. However, for aggregated usage events, the Source Field and the Destination Field cannot be lists or arrays.

For a detailed description of EDR contents, see the discussion about MATRIXX event detail records in MATRIXX Integration.