Output
Destinations for your data: databases, cloud services and more!
The output interface allows us to define destinations for the data. Common destinations are remote services, local file system or standard interface with others. Outputs are implemented as plugins and there are many available.
![](https://docs.fluentbit.io/~gitbook/image?url=https%3A%2F%2F2011346993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FpQx3Sex1V1mpQ54zINRe%252Fuploads%252Fgit-blob-5d66005fe346d267ddbc3f5e00a24c07ceca73ee%252Flogging_pipeline_output%2520%281%29.png%3Falt%3Dmedia%26token%3D6a45cfa1-2fa9-4fb3-af5a-0a4f7ae74045&width=768&dpr=4&quality=100&sign=2f8332d1&sv=1)
When an output plugin is loaded, an internal instance is created. Every instance has its own independent configuration. Configuration keys are often called properties.
Every output plugin has its own documentation section specifying how it can be used and what properties are available.
For more details, please refer to the Output Plugins section.
Last updated