[comment]: # ({c9644d91-9ed83090})
# 4 Real-time export of events, values, trends

[comment]: # ({/c9644d91-9ed83090})

[comment]: # ({2c3ba6c5-aa4ff5c3})
#### Overview

It is possible to configure real-time exporting of trigger events, item
values and trends in a newline-delimited JSON format.

Exporting is done into files, where each line of the export file is a
JSON object. Value mappings are not applied.

In case data cannot be written to the export file or the export file
cannot be renamed or new one cannot be created after renaming it, Zabbix
will retry with 10 second interval until success.

For precise details on what information is exported, see the [export
protocol](/manual/appendix/protocols/real_time_export) page.

Note that host/item can have no metadata (host groups, host name, item
name) if the host/item was removed after the data was received, but
before server exported data.

[comment]: # ({/2c3ba6c5-aa4ff5c3})

[comment]: # ({7b737706-7b737706})
#### Configuration

Real-time export of trigger events, item values and trends is configured
by specifying a directory for the export files - see the `ExportDir`
parameter in server
[configuration](/manual/appendix/config/zabbix_server).

Another parameter - `ExportFileSize` may be used to set the maximum
allowed size of an individual export file. When a process needs to write
to a file it checks the size of the file first. If it exceeds the
configured size limit, the file is renamed by appending .old to its name
and a new file with the original name is created.

::: noteimportant
A file will be created per each process that will
write data (i.e. approximately 4-30 files). As the default size per
export file is 1G, keeping large export files may drain the disk space
fast.
:::

[comment]: # ({/7b737706-7b737706})