A connector specifies how to exchange raw bytes with an underlying resource, such as a file, a network socket, or a third-party library. A connector provides a loader and/or saver:
- Loader: translates raw bytes into structured event data
- Saver: translates structured events into raw bytes
Loaders and savers interact with their corresponding dual from a format:
from <connector> [read <format>]
to <connector> [write <format>]
If the format is omitted, the default depends on the connector.
Tenzir ships with the following connectors:
The dash connector (written as -) is an alias for the stdin
Saves bytes to one file per schema into a directory.
Loads bytes from a file. Saves bytes to a file.
Loads bytes via FTP.
Loads bytes via FTPS.
Loads bytes from a Google Cloud Service object. Saves bytes to a Google Cloud
Loads bytes via HTTP.
Loads bytes via HTTPS.
Loads bytes from and saves bytes to Kafka.
Reads bytes from a network interface card (NIC).
Loads bytes from an Amazon S3 object. Saves bytes to an Amazon S3 object.
The stdin loader is a shorthand for file with argument -.
The stdout saver is a shorthand for file with argument -.
Loads bytes from and saves bytes to ZeroMQ messages.