When analyzing traffic-related issues, it may be useful to export the EDRs from the System, which can be done in three interfaces. Each of the interfaces is suitable for different types of exports.
In the Analytics interface, you can use the EDR export by row in top grid button to export a specific number (100, 500, 1000 or 5000) of EDRs from the top table.
The EDR export tasks menu allows viewing export tasks, their progress and task details. The Export random records checkbox allows exporting a predefined number of rows selected randomly. This option is mainly used to analyze EDR for small periods of time: for example, if something disturbing is visible in Analytics during a certain hour (for example, zero DLR), you can immediately export those EDRs and not spend time configuring filters in the EDR export tool interface. However, even if the client sent only 1 message during that hour, the System will need to view all EDRs for that period because the System has no way to know where specifically certain EDRs are located on the hard disk. That is why such exports may take a long time sometimes. When using this option, a limited set of columns is available, each of them can be removed as shown in the screenshot below. Columns that are not present in the default list cannot be added for export.
In the EDR export tool interface, you can export raw EDRs from the database with all the required columns for a detailed analysis (for example, working with disputes). Compared to exporting from the Analytics interface, you can customize the list of exported columns via the EDR fields to export button:
Also, many filters are available for narrowing down the results, all filters operate according to the logical AND which means that the data is exported only if all the chosen filters are TRUE for this data. You can save frequently used filters to a preset:
Regular expressions can be inserted into pattern filters, for example, Mess. ID pattern or Text pattern. You can export EDRs into the web interface (but only up to 1000 EDRs), or to a file with the following restrictions for each of the file types: xls – a maximum of 65,000 lines per sheet, xlsx – up to 1,000,000+ lines, csv – defined only by the Max number of rows to export in CSV/Excel System setting.
In the Reports interface, for example, via the EDR export (SMS) report, you can export EDRs (possibly) more conveniently than via the EDR export tool interface if all columns are needed. However, this method is not suitable if the export period is large or there is a lot of EDRs to export. Narrowing down the report output by choosing precise filters is advised, an automatic EDR export can be configured via the Enable schedule checkbox and the Set schedule parameter (do not forget to save the schedule for the preset using the Save/Save as buttons). It is advised not to configure large-volume automatic EDR exports as it can lead to the draining of free space in the disk partition on the server.
The most common issues include:
- The system struggles to export too many EDRs, which may lead to non-compliance with the line number file limit (XLS – 65,000 lines per sheet, XLSX – 1,000,000 lines, CSV – only regulated by the System setting) or the System performance slows down. Make sure that you use the EDR export tool interface, as this is the most suitable interface for large exports, also exporting EDRs in the CSV format is advised, since it does not have a limit on the number of rows to be uploaded until it does not exceed the Max number of rows to export in CSV/Excel System setting. Setting this parameter to values more than 1000000 is not advised as it may lead to performance issues. To narrow down the amount of resulting data, you can use more precise filters and split the export into shorter periods in the Period parameter (for example, to export a month not entirely, but by weeks). If you need a very large export (for example, a year), which requires automation and direct interaction with the database, you can create a ticket on the Help Desk in order for the export to be performed by the support team, having first coordinated the operation with your account manager.
- The system cannot export the EDRs because they are too far in the past. There is a limit to the date EDR export can go back to, it can be checked in the Active EDR day count System setting which defines the period over which EDRs are easily accessible for operations. After that, EDRs move to an archive partition. You can learn more about this process, including how to export archived EDRs, in the corresponding article.
- The system cannot open old export tasks results from the EDR export tool interface. You can check the Export task store period (days) System setting, most likely the task is outdated and its results are no longer stored on the server, re-running the task is the only option. Changing the storage settings for no good reason is not recommended.
If you have any remaining questions, feel free to contact the support team, creating a ticket via HelpDesk and describing the issue in detail. If applicable, please include EDR export TASK ID and related entities' IDs.
AKBSMS - Alaris Knowledge Base
Related Questions:
EDR export issue
EDR export tool
EDR export is not working
How to export EDRs effectively?
The EDR export (SMS) report fails.
How many EDRs can be exported at once?
Exporting EDRs from Analytics.