From c67f1c7bd18fa79a578e3ee952a11ce40d1c51f8 Mon Sep 17 00:00:00 2001 From: Laxman Patel <88871793+Imlucky883@users.noreply.github.com> Date: Mon, 4 Dec 2023 11:38:31 +0530 Subject: [PATCH 1/2] "pipeline: outputs: influxdb: updated influxdb and elasticsearch redirection link" "https://docs.fluentbit.io/manual/administration/memory-management" IN the above link, when clicked on the influxdb and elasticsearch link, Error 404 was shown. Signed-off-by: Laxman Patel <88871793+Imlucky883@users.noreply.github.com> --- administration/memory-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/administration/memory-management.md b/administration/memory-management.md index fd8ab60e5..430457145 100644 --- a/administration/memory-management.md +++ b/administration/memory-management.md @@ -8,7 +8,7 @@ In order to that we will assume that the input plugins have set the **Mem\_Buf\_ Input plugins append data independently, so in order to do an estimation, a limit should be imposed through the **Mem\_Buf\_Limit** option. If the limit was set to _10MB_ we need to estimate that in the worse case, the output plugin likely could use _20MB_. -Fluent Bit has an internal binary representation for the data being processed, but when this data reaches an output plugin, it will likely create its own representation in a new memory buffer for processing. The best examples are the [InfluxDB](https://github.com/fluent/fluent-bit-docs/tree/b78cfe98123e74e165f2b6669229da009258f34e/output/influxdb.md) and [Elasticsearch](https://github.com/fluent/fluent-bit-docs/tree/b78cfe98123e74e165f2b6669229da009258f34e/output/elasticsearch.md) output plugins, both need to convert the binary representation to their respective custom JSON formats before it can be sent to the backend servers. +Fluent Bit has an internal binary representation for the data being processed, but when this data reaches an output plugin, it will likely create its own representation in a new memory buffer for processing. The best examples are the [InfluxDB](https://github.com/fluent/fluent-bit-docs/blob/master/pipeline/outputs/influxdb.md) and [Elasticsearch](https://github.com/fluent/fluent-bit-docs/blob/master/pipeline/outputs/elasticsearch.md) output plugins, both need to convert the binary representation to their respective custom JSON formats before it can be sent to the backend servers. So, if we impose a limit of _10MB_ for the input plugins and consider the worse case scenario of the output plugin consuming _20MB_ extra, as a minimum we need \(_30MB_ x 1.2\) = **36MB**. From 55911bda245d5622f7d8e67c01b0ee615a0a54e6 Mon Sep 17 00:00:00 2001 From: Laxman Patel <88871793+Imlucky883@users.noreply.github.com> Date: Sat, 9 Dec 2023 23:26:54 +0530 Subject: [PATCH 2/2] Update administration/memory-management.md Thanks for your feedback and suggested changes. Co-authored-by: Pat Signed-off-by: Laxman Patel <88871793+Imlucky883@users.noreply.github.com> --- administration/memory-management.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/administration/memory-management.md b/administration/memory-management.md index 430457145..dd8d33f4c 100644 --- a/administration/memory-management.md +++ b/administration/memory-management.md @@ -8,7 +8,8 @@ In order to that we will assume that the input plugins have set the **Mem\_Buf\_ Input plugins append data independently, so in order to do an estimation, a limit should be imposed through the **Mem\_Buf\_Limit** option. If the limit was set to _10MB_ we need to estimate that in the worse case, the output plugin likely could use _20MB_. -Fluent Bit has an internal binary representation for the data being processed, but when this data reaches an output plugin, it will likely create its own representation in a new memory buffer for processing. The best examples are the [InfluxDB](https://github.com/fluent/fluent-bit-docs/blob/master/pipeline/outputs/influxdb.md) and [Elasticsearch](https://github.com/fluent/fluent-bit-docs/blob/master/pipeline/outputs/elasticsearch.md) output plugins, both need to convert the binary representation to their respective custom JSON formats before it can be sent to the backend servers. +Fluent Bit has an internal binary representation for the data being processed, but when this data reaches an output plugin, it will likely create its own representation in a new memory buffer for processing. +The best examples are the [InfluxDB](../pipeline/outputs/influxdb.md) and [Elasticsearch](../pipeline/outputs/elasticsearch.md) output plugins, both need to convert the binary representation to their respective custom JSON formats before it can be sent to the backend servers. So, if we impose a limit of _10MB_ for the input plugins and consider the worse case scenario of the output plugin consuming _20MB_ extra, as a minimum we need \(_30MB_ x 1.2\) = **36MB**.