Configure EDR Files for Generation
Use the following sample configuration to generate the EDR events at transaction level.
config
edr file { transaction | transaction-collision }
disable procedure-id procedure_id_value
procedure-id procedure_id_value
disable event-id event_id_value
event-id event_id_value
disable field-id field_id_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_id_value : Specify the procedure ID or procedure name for which the event reporting must be enabled.
-
event-id event_id_value : Specify the event ID or event name for which the event reporting must be enabled.
-
field-id field_id_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 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
disable procedure-id 24 32
procedure-id 25
disable event-id 5 7 8
event-id 5
disable field-id 10 12 14
In the preceding example, disable event-id 5 7 8 means disable the event-id 5, 7, and 8 for procedure-id 25. The disable field-id 10 12 14 means disable the field-id 10, 12, and 14 for procedure-id 25 and event-id 5.