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: pipeline/filters/throttle.md
+12-11
Original file line number
Diff line number
Diff line change
@@ -15,31 +15,33 @@ The plugin supports the following configuration parameters:
15
15
16
16
## Functional description
17
17
18
-
Lets imagine we have configured:
18
+
Using the following configuration:
19
19
20
20
```text
21
21
Rate 5
22
22
Window 5
23
23
Interval 1s
24
24
```
25
25
26
-
we received 1 message first second, 3 messages 2nd, and 5 3rd. As you can see, disregard that Window is actually 5, we use "slow" start to prevent overflooding during the startup.
26
+
You would received 1 message in the first second, 3 messages second, and 5 third.
27
+
Disregard that Window is actually 5, because the configuration uses `slow` start
28
+
to prevent flooding during the startup.
27
29
28
30
```text
29
-
+-------+-+-+-+
30
-
|1|3|5| | | | |
31
-
+-------+-+-+-+
32
-
| 3 | average = 3, and not 1.8 if you calculate 0 for last 2 panes.
31
+
+-------+-+-+-+
32
+
|1|3|5| | | | |
33
+
+-------+-+-+-+
34
+
| 3 | average = 3, and not 1.8 if you calculate 0 for last 2 panes.
33
35
+-----+
34
36
```
35
37
36
38
But as soon as we reached Window size \* Interval, we will have true sliding window with aggregation over complete window.
Copy file name to clipboardExpand all lines: pipeline/inputs/process-exporter-metrics.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ description: >-
9
9
[Prometheus Node Exporter](https://github.com/prometheus/node_exporter) is a popular way to collect system level metrics from operating systems, such as CPU / Disk / Network / Process statistics.
10
10
Fluent Bit 2.2 onwards includes a process exporter plugin that builds off the Prometheus design to collect process level metrics without having to manage two separate processes or agents.
11
11
12
-
The Process Exporter Metrics plugin implements collecting of the various metrics available from [the 3rd party implementation of Prometheus Process Exporter](https://github.com/ncabatoff/process-exporter) and these will be expanded over time as needed.
12
+
The Process Exporter Metrics plugin implements collecting of the various metrics available from [the third party implementation of Prometheus Process Exporter](https://github.com/ncabatoff/process-exporter) and these will be expanded over time as needed.
13
13
14
14
**Important note:** All metrics including those collected with this plugin flow through a separate pipeline from logs and current filters do not operate on top of metrics.
15
15
@@ -103,6 +103,6 @@ docker run -ti -v /proc:/host/proc:ro \
103
103
104
104
## Enhancement Requests
105
105
106
-
Development prioritises a subset of the available collectors in the [the 3rd party implementation of Prometheus Process Exporter](https://github.com/ncabatoff/process-exporter), to request others please open a Github issue by using the following template:\
106
+
Development prioritises a subset of the available collectors in the [the third party implementation of Prometheus Process Exporter](https://github.com/ncabatoff/process-exporter), to request others please open a Github issue by using the following template:\
Copy file name to clipboardExpand all lines: pipeline/outputs/azure_kusto.md
+2-3
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ The Kusto output plugin allows to ingest your logs into an [Azure Data Explorer]
11
11
You can create an Azure Data Explorer cluster in one of the following ways:
12
12
13
13
-[Create a free-tier cluster](https://dataexplorer.azure.com/freecluster)
14
-
-[Create a fully-featured cluster](https://docs.microsoft.com/en-us/azure/data-explorer/create-cluster-database-portal)
14
+
-[Create a fullyfeatured cluster](https://docs.microsoft.com/en-us/azure/data-explorer/create-cluster-database-portal)
15
15
16
16
## For ingesting into Microsoft Fabric Real Time Analytics : Creating an Eventhouse Cluster and KQL Database
17
17
@@ -20,7 +20,6 @@ You can create an Eventhouse cluster and a KQL database follow the following ste
20
20
-[Create an Eventhouse cluster](https://docs.microsoft.com/en-us/azure/data-explorer/eventhouse/create-eventhouse-cluster)
21
21
-[Create a KQL database](https://docs.microsoft.com/en-us/azure/data-explorer/eventhouse/create-database)
22
22
23
-
24
23
## Creating an Azure Registered Application
25
24
26
25
Fluent-Bit will use the application's credentials, to ingest data into your cluster.
@@ -66,7 +65,7 @@ By default, Kusto will insert incoming ingestions into a table by inferring the
66
65
| time_key | The key name of time. If `include_time_key` is false, This property is ignored. |`timestamp`|
67
66
| ingestion_endpoint_connect_timeout | The connection timeout of various Kusto endpoints in seconds. |`60`|
68
67
| compression_enabled | If enabled, sends compressed HTTP payload (gzip) to Kusto. |`true`|
69
-
| ingestion_resources_refresh_interval | The ingestion resources refresh interval of Kusto endpoint in seconds.
68
+
| ingestion_resources_refresh_interval | The ingestion resources refresh interval of Kusto endpoint in seconds.
70
69
| workers | The number of [workers](../../administration/multithreading.md#outputs) to perform flush operations for this output. |`0`|
71
70
| buffering_enabled |_Optional_ - Enable buffering into disk before ingesting into Azure Kusto. |`Off`|
72
71
| buffer_dir |_Optional_ - When buffering is `On`, specifies the location of directory where the buffered data will be stored. |`/tmp/fluent-bit/azure-kusto/`|
0 commit comments