You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: concepts/data-pipeline/output.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,12 @@
1
1
---
2
-
description: 'Destinations for your data: databases, cloud services and more!'
2
+
description: Learn about destinations for your data, such as databases and cloud services.
3
3
---
4
4
5
5
# Output
6
6
7
-
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.
7
+
The output interface lets you define destinations for your data. Common destinations
8
+
are remote services, local file systems, or other standard interfaces. Outputs are
9
+
implemented as plugins.
8
10
9
11
```mermaid
10
12
graph LR
@@ -22,8 +24,10 @@ graph LR
22
24
style H stroke:darkred,stroke-width:2px;
23
25
```
24
26
25
-
When an output plugin is loaded, an internal _instance_ is created. Every instance has its own independent configuration. Configuration keys are often called **properties**.
27
+
When an output plugin is loaded, an internal _instance_ is created. Every instance
28
+
has its own independent configuration. Configuration keys are often called
29
+
_properties_.
26
30
27
31
Every output plugin has its own documentation section specifying how it can be used and what properties are available.
28
32
29
-
For more details, please refer to the [Output Plugins](https://docs.fluentbit.io/manual/pipeline/outputs) section.
33
+
For more details, see [Output Plugins](https://docs.fluentbit.io/manual/pipeline/outputs).
0 commit comments