Configure EDR Files for Generation
Use the following sample configuration to generate the EDR events at transaction level.
config
edr file { transaction | transaction-collision }
procedure-id procedure_value
event-id event_value
field-id field_value
end
-
edr file { transaction | transaction-collision } : Specify to generate EDR files with transaction or transaction-collision level details for subscriber sessions.
-
procedure-id procedure_value : Specify the procedure ID or procedure name for which the event reporting must be enabled.
-
event-id event_value : Specify the event ID or event name for which the event reporting must be enabled.
-
field-id field_value : Specify the field ID or field name for which the event reporting must be enabled.
-
All procedure IDs, event IDs, and field IDs registered by application, are enabled by default.
-
If one or more procedures are enabled, then all the other procedures will be disabled and will not be populated in the transaction EDR. Similarly, if one or more events are enabled under a procedure, all other events under that procedure will be disabled and will not be populated in the transaction EDR.
-
If a procedure-id is disabled, no event start, add field, or event-end will be honored for the procedure-id.
-
If an event-id is disabled within a procedure id, then event-start, event-end, or add field will not be honored for the procedure-id and event-id combination.
-
If a field-id is disabled for an event-id, then add-field will not be honored, and a blank entry will be present instead of value in CSV entry.
Example Configuration:
edr file transaction
procedure-id 24 32
procedure-id 25
event-id 5 7 8
event-id 5
field-id 10 12 14
In the preceding example, event-id 5 7 8 means enable the event-id 5, 7, and 8 for procedure-id 25. The field-id 10 12 14 means enable the field-id 10, 12, and 14 for procedure-id 25 and event-id 5.