Log Exporters
Last updated
Last updated
Log Exporters allow admins to stream event data to an outside destination, e.g. a SIEM/SOC. Every few seconds, Reblaze bundles and exports the most recent traffic events from its internal logs.
For details of the protocols and format of the event data, see Log Exporter Output.
Below is a discussion of the console interface for configuring Log Exporters.
Log Exporters operate at the system level. Admins can configure them for specific server groups, or for the entire planet.
The main Log Exporter window lists all currently defined Log Exporters.
The administration (addition/deletion/editing/versioning) of Log Exporters follows the conventions described here.
A unique name for use within Reblaze.
Whether or not this Log Exporter is currently active.
The destination IP to which event data will be sent.
The port to which event data will be sent.
The specific server groups for which event data will be sent.
The protocol to use while streaming the event data. If a TLS protocol is selected, a control will appear for uploading an SSL certificate.
Blocked: Export only the requests blocked by Reblaze.
All: Export all the requests blocked by Reblaze and passed by Reblaze.
Note that currently, Log Exporters can not include requests challenged by Reblaze, or blocked by the origin.
