+
+- They are not routable. Instead, they are attached directly to an input plugin and run one after the other.
+- If the plugin is running in threaded mode, meaning that it runs in a separate thread, the processor will run there too, significantly reducing the contention that Filters used to generate in the main event loop and thread, as a side effect: better performance.
+
+In this new version we are adding three new processors:
+
+#### Content Modifier
+
+Similar to the functionality exposed by filters, this new processor aims to unify the logic to manipulate content in Logs and Traces; it also can explicitly operate only on metadata/attributes or the content of the messages itself.
+
+The following example creates a simple pipeline that generates a dummy message with 2 keys, then the content\_modifier processor is loaded to work over the logs stream where it will insert a new key called `color` with value `blue`. Once the key has been inserted, the next action is to extract and decompose the value of the key `http.url` in multiple keys by using a regular expression pattern:
+
+```yaml
+pipeline:
+ inputs:
+ - name: dummy
+ dummy: '{"key1": "123.4", "http.url": "https://www.google.com/search?q=example"}'
+ rate: 1
+
+ processors:
+ logs:
+ - name: content_modifier
+ action: insert
+ key: "color"
+ value: "blue"
+
+ - name: content_modifier
+ action: extract
+ key: "http.url"
+ pattern: ^(?https?):\/\/(?[^\/\?]+)(?\/[^?]*)?(?:\?(?.*))?
+ outputs:
+ - name: stdout
+ match: '*'
+ format: json_lines
+```
+
+
+
+#### Metrics Selector
+
+When collecting metrics from the host, receiving or scrapping them from a remote endpoint, there are many cases where you are not interested in everything that has been collected, metrics selector allows you to specify what metrics to include and what to exclude by using patterns on it name.
+
+In the following example data, generated in a macOS system where Fluent Bit is gathering metrics from the host by using the the `node_exporter_metrics` input plugin, we have attached a simple processor that will only include metrics that it name starts with `node_disk_w` (we are using a regular expression to perform further match):
+
+```yaml
+pipeline:
+ inputs:
+ - name: node_exporter_metrics
+ processors:
+ metrics:
+ - name: metrics_selector
+ action: include
+ metric_name: /^node_disk_w.*/
+ outputs:
+ - name: stdout
+ match: "*"
+ format: json_lines
+```
+
+
+Instead of getting the hundreds of metrics generated, the following will only available in the pipeline for processing and delivery:
+
+
+
+```txt
+2024-03-21T21:45:39.028335270Z node_disk_writes_completed_total{device="disk0"} = 21667544
+2024-03-21T21:45:39.028342061Z node_disk_written_sectors_total{device="disk0"} = 5289.927734375
+2024-03-21T21:45:39.028362895Z node_disk_write_time_seconds_total{device="disk0"} = 1728.3985221549999
+2024-03-21T21:45:39.028352270Z node_disk_written_bytes_total{device="disk0"} = 404240666624
+2024-03-21T21:45:39.028373228Z node_disk_write_errors_total{device="disk0"} = 0
+2024-03-21T21:45:39.028383186Z node_disk_write_retries_total{device="disk0"} = 0
+```
+
+
+
+#### SQL
+
+We don’t believe everybody needs to learn every single processor or filter provided by Fluent Bit to achieve data selection however many of you have some knowledge of SQL (Structured Query Language).The new SQL processor, allows you to define queries by using SQL expressions to select parts of your Logs and Traces which can also be used with conditionals. Here is a simple example of it:
+
+
+```yaml
+pipeline:
+ inputs:
+ - name: dummy
+ dummy: '{"key1": "123.4", "http.url": "https://fluentbit.io/search?q=docs"}'
+
+ processors:
+ logs:
+ - name: content_modifier
+ action: extract
+ key: "http.url"
+ pattern: ^(?https?):\/\/(?[^\/\?]+)(?\/[^?]*)?(?:\?(?.*))?
+
+ - name: sql
+ query: "SELECT new_key AS key, http_domain FROM STREAM;"
+
+ outputs:
+ - name : stdout
+ match: '*'
+ format: json_lines
+```
+
+
+
+The dummy plugin, will generate a sample message with two keys `key1` and `http.url` , then the new processor content\_modifier will extract the content of the key `http.url` as a series of key/value pairs by using the regular expression defined in `pattern`, finally the SQL processor will only select the new key ingested with a new name and only the key `http_domain`as part of the result:
+
+
+
+```json
+{
+ "date": 1711059261.630668,
+ "http_domain": "fluentbit.io"
+}
+```
+
+{{< contributor-list >}}
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.0/v3.0.1.md b/content/announcements/v3.0/v3.0.1.md
new file mode 100644
index 0000000..c55e4c8
--- /dev/null
+++ b/content/announcements/v3.0/v3.0.1.md
@@ -0,0 +1,59 @@
+---
+title: 'v3.0.1'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.0.1/"
+release_date: 2024-03-29
+publishdate: 2024-03-29
+ver: v3.0.1
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.0.1
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.0.1**.
+
+For people upgrading from previous versions you **must read** the Upgrading Notes section of our documentation:
+
+[https://docs.fluentbit.io/manual/installation/upgrade_notes](https://docs.fluentbit.io/manual/installation/upgrade_notes)
+
+### What's new ?
+
+In this maintenance release, we are including a couple of fixes which are listed below:
+
+ - Core
+ - http_server: added parser reset code to prevent use after free
+
+ - Libraries:
+ - CMetrics: upgrade to v0.7.1
+
+ - Plugins
+ - [Tail (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/tail/)
+ - Add support for CRLF when `skip_empty_line` is `on`.
+ - [SQL (Processor)](https://docs.fluentbit.io/manual/pipeline/processors/sql)
+ - add missing handling of conditionals for unsigned values
+ - parser: add missing tokens for conditional operations
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+
+- [Eduardo Silva](https://github.com/edsiper)
+- [Leonardo Alminana](https://github.com/leonardo-albertovich)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+- [Takahiro Yamashita](https://github.com/nokute78)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.0/v3.0.2.md b/content/announcements/v3.0/v3.0.2.md
new file mode 100644
index 0000000..8a360a7
--- /dev/null
+++ b/content/announcements/v3.0/v3.0.2.md
@@ -0,0 +1,107 @@
+---
+title: 'v3.0.2'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.0.2/"
+release_date: 2024-04-15
+publishdate: 2024-04-15
+ver: v3.0.2
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.0.2
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.0.2**.
+
+For people upgrading from previous versions you **must read** the Upgrading Notes section of our documentation:
+
+[https://docs.fluentbit.io/manual/installation/upgrade_notes](https://docs.fluentbit.io/manual/installation/upgrade_notes)
+
+### What's new ?
+
+In this maintenance release, we are including a couple of fixes which are listed below:
+
+
+
+ - Core
+ - input: Add missing input resume message This commit will add a resume message, when a paused input plugin is resumed.
+ - engine_dispatch: remove chunks from memory if the task fails to be created
+ - task: on retry, only put chunk down if there are no users (fix #8691)
+ - input_metric: fixed a double free
+ - input_chunk: handle some chunk size debug messages as trace messages
+ - config: fix compilation with `FLB_HAVE_STATIC_CONF` (#7536)
+
+
+
+ - Plugins
+ - [HTTP (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/http/)
+ - Fix buffer addresses on reallocation when processing headers (#8643)
+ - [Winevtlog (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/winevtlog/)
+ - Make configurable for the size of collecting threshold per a cycle (#8677)
+ - [Opentelemetry (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/opentelemetry/)
+ - Fixed the URIs used to detect gRPC requests
+ - [Tail (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/tail/)
+ - Introducing the `compare_filename` option to db_file_exists (#8025)(2/2)
+ - Delete unmanaged inodes from database file during startup (#8025) (1/2)
+ - [Forward (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/forward/)
+ - Handle multiply concatenated gzip payloads (#8665)
+ - [Emitter (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/emitter/)
+ - Pause source input plugins on in_emitter pause. This will pause all known inputs (sending to multiline) to not loose any in-flight records. in_emitter will keep track of all sending input plugins and actively pause/resume them in case in_emitter is paused/resumed.
+ - Fix to prevent single record chunks and do pause on `mem_buf_limit`
+ - [Rewrite_Tag (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/rewrite_tag/)
+ - Pause source input plugins on filter pause this commit will pause the inputs (sending to rewrite_tag) to not loose any in-flight records.
+ - [Multiline (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/multiline/)
+ - Pause source input plugins on filter pause this commit will pause the inputs (sending to multiline) to not loose any in-flight records.
+ - [Kubernetes (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/kubernetes/)
+ - Add new configuration property `namespace_metadata_only` (#8695)
+ - [Opentelemetry (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/opentelemetry/)
+ - Add support to set OpenTelemetry fields from the event body based on keys (#8644)
+ - [Websocket (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/websocket/)
+ - Add ability to provide additional headers in the HTTP request.
+ - [Loki (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/loki/)
+ - Change loglevel for non-existing label in record accessor.
+ - [Oracle_Log_Analytics (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/oracle_log_analytics/)
+ - Fix 400 bad request
+
+
+
+ - Libraries:
+ - sqlite: upgrade to v3.45.2
+ - cmetrics: upgrade to v0.7.3
+ - chunkio: upgrade to v1.5.2
+ - monkey: upgrade to v1.7.4
+ - cmetrics: upgrade to v0.7.2
+ - ctraces: upgrade to v0.4.1
+ - cfl: upgrade to v0.4.1
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+- [Richard Treu](https://github.com/drbugfinder-work)
+- [Eduardo Silva](https://github.com/edsiper)
+- [Phillip Whelan](https://github.com/pwhelan)
+- [Leonardo Alminana](https://github.com/leonardo-albertovich)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+- maflcko
+- [Ryan Ohnemus](https://github.com/ryanohnemus)
+- [bglimepoint](https://github.com/bglimepoint)
+- [cb645j](https://github.com/cb645j)
+- hc
+- jinyong.choi
+- [Markus Thömmes](https://github.com/markusthoemmes)
+- [seblaz](https://github.com/seblaz)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.0/v3.0.3.md b/content/announcements/v3.0/v3.0.3.md
new file mode 100644
index 0000000..e3eb5e1
--- /dev/null
+++ b/content/announcements/v3.0/v3.0.3.md
@@ -0,0 +1,80 @@
+---
+title: 'v3.0.3'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.0.3/"
+release_date: 2024-04-27
+publishdate: 2024-04-27
+ver: v3.0.3
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.0.3
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.0.3**.
+
+For people upgrading from previous versions you **must read** the Upgrading Notes section of our documentation:
+
+[https://docs.fluentbit.io/manual/installation/upgrade_notes](https://docs.fluentbit.io/manual/installation/upgrade_notes)
+
+### What's new ?
+
+In a few words, this release add fixes for OpenTelemetry handling for Traces and Metrics, provides better performance for processors and add enhance some connectors (listed below).
+
+Specific fixes per component:
+
+
+
+ - Core
+ - mp: use referenced values when composing CFL object
+ - processor_content_modifier: use copied values for referenced values when converting
+ - processor_content_modifier: use new CFL API to reference strings and bytes
+
+
+
+ - Plugins
+ - [HTTP (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/http/)
+ - Fix URL decoder by unifying normal interface with the one used in http/1.x
+ - [Splunk (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/splunk/)
+ - Store ingested HEC token as metadata
+ - [HTTP (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/http/)
+ - Use `x-ndjson` content type for `json_lines`
+ - [Chronicle (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/chronicle/)
+ - Allow to handle 1MB or larger chunks
+ - [Splunk (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/splunk/)
+ - Migrate to use record_accesor pattern for extracting token
+ - Handle HEC token from metadata
+
+
+
+ - Libraries:
+ - [CMetrics](https://github.com/fluent/cmetrics): upgrade to v0.9.0
+ - [CTraces](https://github.com/fluent/ctraces): upgrade to v0.5.1
+ - [CFL](https://github.com/fluent/cfl): upgrade to v0.5.0
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+
+- [Aidan Leuck](https://github.com/aidanleuck)
+- [Manuel Rüger](https://github.com/mrueg)
+- [Eduardo Silva](https://github.com/edsiper)
+- [Leonardo Alminana](https://github.com/leonardo-albertovich)
+- [lecaros](https://github.com/lecaros)
+- [Pat](https://github.com/patrick-stephens)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.0/v3.0.4.md b/content/announcements/v3.0/v3.0.4.md
new file mode 100644
index 0000000..f492a8b
--- /dev/null
+++ b/content/announcements/v3.0/v3.0.4.md
@@ -0,0 +1,85 @@
+---
+title: 'v3.0.4'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.0.4/"
+release_date: 2024-05-20
+publishdate: 2024-05-20
+ver: v3.0.4
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.0.4
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.0.4**.
+
+
+
+### Security updates and other improvements
+
+__Important__: This release addresses a critical security vulnerability in the interface handling trace requests. The identified issue involves memory corruption, which could potentially be exploited to cause denial of service (DoS) conditions. Note that this issue is related to the internal tracing interface and __NOT__ Traces telemetry data handling. It is highly recommended to update to this version immediately to ensure the stability and security of your system.
+
+
+
+
+ - __Core__
+ - http_server: api: v1: trace: fix memory corruption ([#9311b43a](https://github.com/fluent/fluent-bit/commit/9311b43a258352797af40749ab31a63c32acfd04))
+ - kernel: fix incorrect assignment of Linux Kernel version between major and minor (#8797)
+ - http_server: fix keep-alive for HTTP/1.1 requests
+ - config: fix error message grammar (#8818)
+
+
+
+ - __Pipeline Plugins__
+ - [AWS (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/aws-metadata/)
+ - add support for `metadata_group`
+ - [Premetheus_Remote_Write (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/premetheus_remote_write/)
+ - New (EXPERIMENTAL) input plugin to receive Prometheus Remote Write prototol (#8725)
+ - [Opentelemetry (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/opentelemetry/)
+ - Enable keep-alive
+ - Add a function to store metadata
+ - Support to add resource of log
+ - [Elasticsearch (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/elasticsearch/)
+ - Enable keep-alive on HTTP/1.1
+ - [HTTP (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/http/)
+ - Enable keep-alive on HTTP/1.1
+ - [Splunk (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/splunk/)
+ - Enable keep-alive on HTTP/1.1
+ - [Datadog (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/datadog/)
+ - Update the descriptions of special field options #8751
+ - [Kafka (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/kafka/)
+ - Increase max kafka dynamic topic length to 249 characters
+ - [Splunk (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/splunk/)
+ - Fix record accessor key for `hec_token` (#8793)
+
+
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+- [Phillip Whelan](https://github.com/pwhelan)
+- [Eduardo Silva](https://github.com/edsiper)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+- [Takahiro Yamashita](https://github.com/nokute78)
+- [Braydon Kains](https://github.com/braydonk)
+- [Jesse Szwedko](https://github.com/jszwedko)
+- [Maneesh Singh](https://github.com/mannbiher)
+- [xiaobaowen](https://github.com/thenamehasbeentake)
+- Michael Meunier
+- [Mateusz Warzyński](https://github.com/mwarzynski)
+- [Andrew Titmuss](https://github.com/iandrewt)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.0/v3.0.5.md b/content/announcements/v3.0/v3.0.5.md
new file mode 100644
index 0000000..81db163
--- /dev/null
+++ b/content/announcements/v3.0/v3.0.5.md
@@ -0,0 +1,57 @@
+---
+title: 'v3.0.5'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.0.5/"
+release_date: 2024-05-24
+publishdate: 2024-05-24
+ver: v3.0.5
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.0.5
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.0.5**.
+
+
+
+### What's new ?
+
+
+
+ - __Core__
+ - engine: log worker context thread once it has been stopped
+ - output: Fix handling of metrics in output processor
+
+
+
+ - __Pipeline Plugins__
+ - [Winevtlog (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/winevtlog/)
+ - Change total_size_threshold to size_t (#8853)
+ - [Splunk (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/splunk/)
+ - Reduce noise and fix `hec_token` handling (fix #8859)
+
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+- [Braydon Kains](https://github.com/braydonk)
+- [Thiago Padilha](https://github.com/tarruda)
+- [Eduardo Silva](https://github.com/edsiper)
+- Hiroyuki Hasebe
+- [Pat](https://github.com/patrick-stephens)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.0/v3.0.6.md b/content/announcements/v3.0/v3.0.6.md
new file mode 100644
index 0000000..7fe9bee
--- /dev/null
+++ b/content/announcements/v3.0/v3.0.6.md
@@ -0,0 +1,58 @@
+---
+title: 'v3.0.6'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.0.6/"
+release_date: 2024-05-26
+publishdate: 2024-05-26
+ver: v3.0.6
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.0.6
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.0.6**.
+
+
+
+### What's new ?
+
+
+
+ - __Core__
+ - core: fix crash when running dry test mode (#8872)
+
+
+
+ - __Pipeline Plugins__
+
+ - [Stackdriver (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/stackdriver/)
+ - support writing to textPayload field of Cloud Logging LogEntry. (#8850)
+
+ - [Splunk (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/splunk/)
+ - Fix metadata `hec_token` bug that overrides default splunk_token behavior
+
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+- [Holger Freyther](https://github.com/zecke)
+- [Markus Bergholz](https://github.com/markuman)
+- [Eduardo Silva](https://github.com/edsiper)
+- [shuaichen](https://github.com/shuaich)
+
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.0/v3.0.7.md b/content/announcements/v3.0/v3.0.7.md
new file mode 100644
index 0000000..b8d3fdc
--- /dev/null
+++ b/content/announcements/v3.0/v3.0.7.md
@@ -0,0 +1,91 @@
+---
+title: 'v3.0.7'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.0.7/"
+release_date: 2024-06-11
+publishdate: 2024-06-11
+ver: v3.0.7
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.0.7
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.0.7**.
+
+
+
+### What's new ?
+
+
+
+ - __Core__
+ - tls: fix virtual host verification when `tls.verify` is enabled
+ - build: fix cmake build with ninja (#8835)
+ - http_server: api: v1: traces: fix finding inputs by alias.
+ - dockerfiles:
+ - windows: Update to use vcpkg instead of chocolatey
+ - dockerfile: update to bookworm base image (#8916)
+
+
+
+- __Libraries__
+ - CMetrics: upgrade to v0.9.1
+
+
+
+ - __Pipeline Plugins__
+
+ - [Systemd (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/systemd/)
+ - Move one record back after skipping to the end
+ - [HTTP (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/http/)
+ - Add tests for 400 responses to bad requests and buffer write errors.
+ - Return a 400 error when unable to receive a message.
+ - [Prometheus_Scrape (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/prometheus_scrape/)
+ - Add user-agent http header (#8880)
+ - [Winevtlog (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/winevtlog/)
+ - Fix threshold condition to avoid unnecessary warning
+ - [Splunk (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/splunk/)
+ - Add switch for storing Splunk token in metadata or records
+ - Store HEC token on enabled HTTP2 and raw endpoints
+ - [Kubernetes_Events (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/kubernetes_events/)
+ - Type cast explicitly
+ - Refactor time check to use struct flb_time.
+ - [Metrics Selector (Processor)](https://docs.fluentbit.io/manual/pipeline/processors/metrics-selector)
+ - Implement delete by label key-value pair feature
+ - [Cloudwatch_Logs (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/cloudwatch_logs/)
+ - Support `log_group_class` option
+ - [Calyptia (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/calyptia/)
+ - Move debug payload to debug level (less noise).
+
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+- Thomas Devoogdt
+- [Phillip Whelan](https://github.com/pwhelan)
+- [Eduardo Silva](https://github.com/edsiper)
+- [Pat Stephens](https://github.com/patrick-stephens)
+- Meet
+- Ardavast Dayleryan
+- javex
+- [Phil Whelan](https://github.com/pwhelan)
+- [lecaros](https://github.com/lecaros)
+- [Wesley Pettit](https://github.com/PettitWesley)
+- Enderson Maia
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.1/_index.md b/content/announcements/v3.1/_index.md
new file mode 100644
index 0000000..9173bd0
--- /dev/null
+++ b/content/announcements/v3.1/_index.md
@@ -0,0 +1,15 @@
+---
+title: 'Fluent Bit v3.1 Series'
+description: "[Fluent Bit v1.9](https://github.com/fluent/fluent-bit/tree/master) is the new **stable branch** for production usage. Based on bug reports or
+specific minor feature requests, we do quick releases upon demand. Below is a list of the notes for each version."
+url: "/announcements/v3.1/"
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+releaseNotes:
+ heading: "Release Notes v3.1.0"
+ version: "v3.1.0"
+ text: "Fluent Bit is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD and OSX. We are proud to announce the availability of Fluent Bit v1.9.9.
+ For people upgrading from previous versions you must read the Upgrading Notes section of our documentation:
+ https://docs.fluentbit.io/manual/installation/upgrade_notes"
+---
+
diff --git a/content/announcements/v3.1/v3.1.0.md b/content/announcements/v3.1/v3.1.0.md
new file mode 100644
index 0000000..ec0b135
--- /dev/null
+++ b/content/announcements/v3.1/v3.1.0.md
@@ -0,0 +1,256 @@
+---
+title: 'v3.1.0'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.1.0/"
+release_date: 2024-07-08
+publishdate: 2024-07-08
+ver: v3.1.0
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.1.0
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Telemetry Agent for Linux, BSD, MacOS and Windows. We are proud to announce the availability of **Fluent Bit v3.1**.
+
+```
+ Fluent Bit v3.1.0
+ * Copyright (C) 2015-2024 The Fluent Bit Authors
+ * Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
+ * https://fluentbit.io
+ ______ _ _ ______ _ _ _____ __
+ | ___| | | | | ___ (_) | |____ |/ |
+ | |_ | |_ _ ___ _ __ | |_ | |_/ /_| |_ __ __ / /`| |
+ | _| | | | | |/ _ \ '_ \| __| | ___ \ | __| \ \ / / \ \ | |
+ | | | | |_| | __/ | | | |_ | |_/ / | |_ \ V /.___/ /_| |_
+ \_| |_|\__,_|\___|_| |_|\__| \____/|_|\__| \_/ \____(_)___/
+
+ [2024/07/09 12:55:40] [ info] [fluent bit] version=3.1.0, commit=8ed2e80a9e, pid=51082
+ [2024/07/09 12:55:40] [ info] [storage] ver=1.5.2, type=memory, sync=normal, checksum=off, max_chunks_up=128
+ [2024/07/09 12:55:40] [ info] [cmetrics] version=0.9.1
+ [2024/07/09 12:55:40] [ info] [ctraces ] version=0.5.1
+ [2024/07/09 12:55:40] [ info] [sp] stream processor started
+```
+
+For people upgrading from previous versions you **must read** the Upgrading Notes section of our documentation:
+
+[https://docs.fluentbit.io/manual/installation/upgrade_notes](https://docs.fluentbit.io/manual/installation/upgrade_notes)
+
+### Introduction
+
+Fluent Bit, a CNCF graduated project under the umbrella of Fluentd, announces the availability of v3.1.
+
+In every release, there are many improvements and fixes, on this notes we will refer to the major changes that will make your infrastructure happier ;)
+
+Below a list of the highlights of this release:
+
+### LuaJIT Upgrade (scripting)
+
+One of the powerful features of Fluent Bit, is the ability to provide the user an interface to control how to modify their telemetry data by using a very simple, but powerful, scripting language: [Lua](https://docs.fluentbit.io/manual/pipeline/filters/lua). Our Lua interface is powered by [LuaJIT](https://github.com/LuaJIT/LuaJIT) library, this has not been upgraded in the last two years, primary because it has been very stable for a long time.
+
+In this release, we are upgrading to the latest of LuaJIT which brings overall architecture improvements and extended support for Windows on ARM.
+
+If you are curious to learn how to use Lua, just copy the following configuration file and see how a simple dumy message can be modified inline in the config with some embedded Lua code:
+
+```yaml
+service:
+ flush: 1
+ log_level: info
+
+pipeline:
+ inputs:
+ - name: dummy
+ dummy: '{"project": "Fluent Bit", "version": "v3.1"}'
+
+ processors:
+ logs:
+ - name: lua
+ call: cb_replace
+ code: |
+ function cb_replace(tag, timestamp, record)
+ record['tag'] = tag
+ record['new_key'] = 'new value'
+
+ -- Record modified, so 'code' return value (first parameter) is 1
+ return 1, timestamp, record
+ end
+ outputs:
+ - name: stdout
+ match: '*'
+```
+
+
+
+> You can also have your Lua code in a separate file, just read more about the [Lua](https://docs.fluentbit.io/manual/pipeline/filters/lua) in our documentation.
+
+
+
+### Add support for local/system timezone on parsing
+
+When parsing log record dates, there are cases when the date string don't contain any relevant information about the timezone it was generated, however is ideal to assume those records were generated in the local system so it parsing should assume the local timezone set in the operating system.
+
+This change introduces a new configuration flag for the parsers section called `time_system_timezone` (default: off) that allows to use system timezone (`mktime(3)`) for date representation.
+
+The following configuration snippet provides an example of it (note this is in classic config mode):
+
+```python
+[PARSER]
+ Name no_timezone
+ Format json
+ Time_Key time
+ Time_Format %Y-%m-%d:%H:%M:%S
+ Time_System_Timezone true
+```
+
+
+
+### Networking
+
+In this release we did some small changes to our networking stack.
+
+#### Configurable KeepAlive for Downstream based input plugins
+
+Downstream is an internal interface to allow to recieve TCP connections. In this release we added a new configuration flag to control manually the keepalive functionality (this allows to have persistent TCP connection), the new option available is `net.keepalive` (default: on).
+
+Users of this interface are the __input__ plugins such as [HTTP](https://docs.fluentbit.io/manual/pipeline/inputs/http), [OpenTelemetry](https://docs.fluentbit.io/manual/pipeline/inputs/opentelemetry), [Elasticsearch](https://docs.fluentbit.io/manual/pipeline/inputs/elasticsearch), [Splunk](https://docs.fluentbit.io/manual/pipeline/inputs/splunk), etc.
+
+
+
+#### TLS Hostname verification
+
+When performing TLS connections, the default verification is for the certificates. In this new release, we added a new check to verify the hostname associated to the certificates through the new option `tls.verify_hostname` (default: off).
+
+Note that some plugins that uses TLS might have a different default for `tls.verify_hostname`.
+
+
+
+#### OpenSSL: reduce log noise
+
+A small change to reduce the noise in the TLS logger make sure you don't get false positives when doing secured sessions backed by OpenSSL.
+
+
+
+### Core: Log Groups
+
+When input plugins collects or generate log records, usually those are serialized one after each other, the only shared information that existed for records grouped inside a Chunk is the `Tag`. This simple metadata field is used for routing through the pipeline, however there are cases where we need to set metadata for a group of records, this is where we have implemented the concept of Groups.
+
+A Group is a special record definition that aims to share specific information for all records under that group.
+
+```
+ :---+--------------+---------------------------------------------:
+ | 1 | Group | [ [Group Start, {METADATA}], {GROUP_INFO} ] |
+ :---+--------------+---------------------------------------------:
+ | 2 | Log Record 1 | [ [TIMESTAMP, {METADATA}], {RECORD} ] |
+ :---+--------------+---------------------------------------------:
+ | 3 | Log Record 2 | [ [TIMESTAMP, {METADATA}], {RECORD} ] |
+ :---+--------------+---------------------------------------------:
+ | 4 | Log Record N | [ [TIMESTAMP, {METADATA}], {RECORD} ] |
+ :---+--------------+---------------------------------------------:
+ | 5 | Group | [ [Group End, {}], {} ] |
+ '---'--------------'---------------------------------------------'
+```
+
+As of now, the only components of plugins generating or consuming those groups are [OpenTelemetry input](https://docs.fluentbit.io/manual/pipeline/inputs/opentelemetry) and [OpenTelemetry output](https://docs.fluentbit.io/manual/pipeline/outputs/opentelemetry). This aims to address some issues we had handling OTel Logs metadata.
+
+
+
+### Processors
+
+Processors are the new way to do data processing or filtering. In this release we are announcing the following changes for end users interested in OpenTelemetry log processing:
+
+
+
+- OpenTelemetry Envelope
+- Content Modifier contexts for OpenTelemetry logs
+
+
+
+#### OpenTelemetry Envelope
+
+When the source of data generated comes from an OpenTelemetry SDK, it comes already formatted with the expected schema, however for majority of cases where the data __does not come from__ an OTel instrumented application and the destination is an OpenTelemetry endpoint, we need to format the data accordingly.
+
+OpenTelemetry Envelope is a new processor that puts in place the minimum data structure for Log records that are not coming from a native OTel instrumented application, making it easier to process it and deliver it to an OpenTelemetry endpoint.
+
+
+
+Here is a simple example on how to use it:
+
+```yaml
+pipeline:
+ inputs:
+ - name: dummy
+ samples: 1
+
+ processors:
+ logs:
+ - name: opentelemetry_envelope
+
+ outputs:
+ - name : stdout
+ match: '*'
+```
+
+
+
+#### Content Modifier for OpenTelemetry
+
+This new processor introduced recently in v3 series, provides similar functionality exposed by filters to modify or alter the content of records. This time we have extended [Content Modifier](https://docs.fluentbit.io/manual/pipeline/processors/content-modifier) processor to allow to perform modifications on different parts of OpenTelemetry Logs schema, the following new contexts are supported
+
+| Context | Description |
+|--|--|
+| ```otel_resource_attributes``` | alter resource attributes |
+| ```otel_scope_name``` | manipulate the scope name |
+| ```otel_scope_version``` | manipulate the scope version |
+| ```otel_scope_attributes``` | alter the scope attributes |
+
+
+
+In this example, we are using OpenTelemetry Envelope processor and Content Modifier, to alter the Log resource and Scope attributes:
+
+```yaml
+service:
+ flush: 1
+ log_level: info
+
+pipeline:
+ inputs:
+ - name: dummy
+ samples: 1
+
+ processors:
+ logs:
+ - name: opentelemetry_envelope
+
+ - name: content_modifier
+ context: otel_resource_attributes
+ action: upsert
+ key: "new_key"
+ value: "some value"
+
+ - name: content_modifier
+ context: otel_scope_attributes
+ action: upsert
+ key: "new_span_key"
+ value: "abc"
+
+ outputs:
+ - name : stdout
+ match: '*'
+```
+
+{{< contributor-list >}}
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.1/v3.1.1.md b/content/announcements/v3.1/v3.1.1.md
new file mode 100644
index 0000000..233a2df
--- /dev/null
+++ b/content/announcements/v3.1/v3.1.1.md
@@ -0,0 +1,258 @@
+---
+title: 'v3.1.1'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.1.1/"
+release_date: 2024-07-10
+publishdate: 2024-07-10
+ver: v3.1.1
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.1
+
+> FYI: v3.1.1 is just a minor update that fixes some build system issues found in v3.1.0
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Telemetry Agent for Linux, BSD, MacOS and Windows. We are proud to announce the availability of **Fluent Bit v3.1**.
+
+```
+ Fluent Bit v3.1.1
+ * Copyright (C) 2015-2024 The Fluent Bit Authors
+ * Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
+ * https://fluentbit.io
+ ______ _ _ ______ _ _ _____ __
+ | ___| | | | | ___ (_) | |____ |/ |
+ | |_ | |_ _ ___ _ __ | |_ | |_/ /_| |_ __ __ / /`| |
+ | _| | | | | |/ _ \ '_ \| __| | ___ \ | __| \ \ / / \ \ | |
+ | | | | |_| | __/ | | | |_ | |_/ / | |_ \ V /.___/ /_| |_
+ \_| |_|\__,_|\___|_| |_|\__| \____/|_|\__| \_/ \____(_)___/
+
+ [2024/07/09 12:55:40] [ info] [fluent bit] version=3.1.1, commit=8ed2e80a9e, pid=51082
+ [2024/07/09 12:55:40] [ info] [storage] ver=1.5.2, type=memory, sync=normal, checksum=off, max_chunks_up=128
+ [2024/07/09 12:55:40] [ info] [cmetrics] version=0.9.1
+ [2024/07/09 12:55:40] [ info] [ctraces ] version=0.5.1
+ [2024/07/09 12:55:40] [ info] [sp] stream processor started
+```
+
+For people upgrading from previous versions you **must read** the Upgrading Notes section of our documentation:
+
+[https://docs.fluentbit.io/manual/installation/upgrade_notes](https://docs.fluentbit.io/manual/installation/upgrade_notes)
+
+### Introduction
+
+Fluent Bit, a CNCF graduated project under the umbrella of Fluentd, announces the availability of v3.1.
+
+In every release, there are many improvements and fixes, on this notes we will refer to the major changes that will make your infrastructure happier ;)
+
+Below a list of the highlights of this release:
+
+### LuaJIT Upgrade (scripting)
+
+One of the powerful features of Fluent Bit, is the ability to provide the user an interface to control how to modify their telemetry data by using a very simple, but powerful, scripting language: [Lua](https://docs.fluentbit.io/manual/pipeline/filters/lua). Our Lua interface is powered by [LuaJIT](https://github.com/LuaJIT/LuaJIT) library, this has not been upgraded in the last two years, primary because it has been very stable for a long time.
+
+In this release, we are upgrading to the latest of LuaJIT which brings overall architecture improvements and extended support for Windows on ARM.
+
+If you are curious to learn how to use Lua, just copy the following configuration file and see how a simple dumy message can be modified inline in the config with some embedded Lua code:
+
+```yaml
+service:
+ flush: 1
+ log_level: info
+
+pipeline:
+ inputs:
+ - name: dummy
+ dummy: '{"project": "Fluent Bit", "version": "v3.1"}'
+
+ processors:
+ logs:
+ - name: lua
+ call: cb_replace
+ code: |
+ function cb_replace(tag, timestamp, record)
+ record['tag'] = tag
+ record['new_key'] = 'new value'
+
+ -- Record modified, so 'code' return value (first parameter) is 1
+ return 1, timestamp, record
+ end
+ outputs:
+ - name: stdout
+ match: '*'
+```
+
+
+
+> You can also have your Lua code in a separate file, just read more about the [Lua](https://docs.fluentbit.io/manual/pipeline/filters/lua) in our documentation.
+
+
+
+### Add support for local/system timezone on parsing
+
+When parsing log record dates, there are cases when the date string don't contain any relevant information about the timezone it was generated, however is ideal to assume those records were generated in the local system so it parsing should assume the local timezone set in the operating system.
+
+This change introduces a new configuration flag for the parsers section called `time_system_timezone` (default: off) that allows to use system timezone (`mktime(3)`) for date representation.
+
+The following configuration snippet provides an example of it (note this is in classic config mode):
+
+```python
+[PARSER]
+ Name no_timezone
+ Format json
+ Time_Key time
+ Time_Format %Y-%m-%d:%H:%M:%S
+ Time_System_Timezone true
+```
+
+
+
+### Networking
+
+In this release we did some small changes to our networking stack.
+
+#### Configurable KeepAlive for Downstream based input plugins
+
+Downstream is an internal interface to allow to recieve TCP connections. In this release we added a new configuration flag to control manually the keepalive functionality (this allows to have persistent TCP connection), the new option available is `net.keepalive` (default: on).
+
+Users of this interface are the __input__ plugins such as [HTTP](https://docs.fluentbit.io/manual/pipeline/inputs/http), [OpenTelemetry](https://docs.fluentbit.io/manual/pipeline/inputs/opentelemetry), [Elasticsearch](https://docs.fluentbit.io/manual/pipeline/inputs/elasticsearch), [Splunk](https://docs.fluentbit.io/manual/pipeline/inputs/splunk), etc.
+
+
+
+#### TLS Hostname verification
+
+When performing TLS connections, the default verification is for the certificates. In this new release, we added a new check to verify the hostname associated to the certificates through the new option `tls.verify_hostname` (default: off).
+
+Note that some plugins that uses TLS might have a different default for `tls.verify_hostname`.
+
+
+
+#### OpenSSL: reduce log noise
+
+A small change to reduce the noise in the TLS logger make sure you don't get false positives when doing secured sessions backed by OpenSSL.
+
+
+
+### Core: Log Groups
+
+When input plugins collects or generate log records, usually those are serialized one after each other, the only shared information that existed for records grouped inside a Chunk is the `Tag`. This simple metadata field is used for routing through the pipeline, however there are cases where we need to set metadata for a group of records, this is where we have implemented the concept of Groups.
+
+A Group is a special record definition that aims to share specific information for all records under that group.
+
+```
+ :---+--------------+---------------------------------------------:
+ | 1 | Group | [ [Group Start, {METADATA}], {GROUP_INFO} ] |
+ :---+--------------+---------------------------------------------:
+ | 2 | Log Record 1 | [ [TIMESTAMP, {METADATA}], {RECORD} ] |
+ :---+--------------+---------------------------------------------:
+ | 3 | Log Record 2 | [ [TIMESTAMP, {METADATA}], {RECORD} ] |
+ :---+--------------+---------------------------------------------:
+ | 4 | Log Record N | [ [TIMESTAMP, {METADATA}], {RECORD} ] |
+ :---+--------------+---------------------------------------------:
+ | 5 | Group | [ [Group End, {}], {} ] |
+ '---'--------------'---------------------------------------------'
+```
+
+As of now, the only components of plugins generating or consuming those groups are [OpenTelemetry input](https://docs.fluentbit.io/manual/pipeline/inputs/opentelemetry) and [OpenTelemetry output](https://docs.fluentbit.io/manual/pipeline/outputs/opentelemetry). This aims to address some issues we had handling OTel Logs metadata.
+
+
+
+### Processors
+
+Processors are the new way to do data processing or filtering. In this release we are announcing the following changes for end users interested in OpenTelemetry log processing:
+
+
+
+- OpenTelemetry Envelope
+- Content Modifier contexts for OpenTelemetry logs
+
+
+
+#### OpenTelemetry Envelope
+
+When the source of data generated comes from an OpenTelemetry SDK, it comes already formatted with the expected schema, however for majority of cases where the data __does not come from__ an OTel instrumented application and the destination is an OpenTelemetry endpoint, we need to format the data accordingly.
+
+OpenTelemetry Envelope is a new processor that puts in place the minimum data structure for Log records that are not coming from a native OTel instrumented application, making it easier to process it and deliver it to an OpenTelemetry endpoint.
+
+
+
+Here is a simple example on how to use it:
+
+```yaml
+pipeline:
+ inputs:
+ - name: dummy
+ samples: 1
+
+ processors:
+ logs:
+ - name: opentelemetry_envelope
+
+ outputs:
+ - name : stdout
+ match: '*'
+```
+
+
+
+#### Content Modifier for OpenTelemetry
+
+This new processor introduced recently in v3 series, provides similar functionality exposed by filters to modify or alter the content of records. This time we have extended [Content Modifier](https://docs.fluentbit.io/manual/pipeline/processors/content-modifier) processor to allow to perform modifications on different parts of OpenTelemetry Logs schema, the following new contexts are supported
+
+| Context | Description |
+|--|--|
+| ```otel_resource_attributes``` | alter resource attributes |
+| ```otel_scope_name``` | manipulate the scope name |
+| ```otel_scope_version``` | manipulate the scope version |
+| ```otel_scope_attributes``` | alter the scope attributes |
+
+
+
+In this example, we are using OpenTelemetry Envelope processor and Content Modifier, to alter the Log resource and Scope attributes:
+
+```yaml
+service:
+ flush: 1
+ log_level: info
+
+pipeline:
+ inputs:
+ - name: dummy
+ samples: 1
+
+ processors:
+ logs:
+ - name: opentelemetry_envelope
+
+ - name: content_modifier
+ context: otel_resource_attributes
+ action: upsert
+ key: "new_key"
+ value: "some value"
+
+ - name: content_modifier
+ context: otel_scope_attributes
+ action: upsert
+ key: "new_span_key"
+ value: "abc"
+
+ outputs:
+ - name : stdout
+ match: '*'
+```
+
+{{< contributor-list >}}
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.1/v3.1.10.md b/content/announcements/v3.1/v3.1.10.md
new file mode 100644
index 0000000..46e53ae
--- /dev/null
+++ b/content/announcements/v3.1/v3.1.10.md
@@ -0,0 +1,60 @@
+---
+title: 'v3.1.10'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.1.10/"
+release_date: 2024-11-04
+publishdate: 2024-11-04
+ver: v3.1.10
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.1.10
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.1.10**.
+
+
+
+### What's new ?
+
+
+
+ - __Libraries__
+ - cmetrics: upgrade to v0.9.7
+
+
+
+ - __Pipeline Plugins__
+
+ - [Forward (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/forward/)
+ - Fixed incorrect shared key length in authentication (#9551)
+ - [Opentelemetry (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/opentelemetry/)
+ - Add `tag_from_uri` support to http2 codepath
+ - [Http (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/http/)
+ - Fix parsing of root json object
+ - [Opentelemetry (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/opentelemetry/)
+ - Fix check for uri sanitization when exiting
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+
+- [Patrick Stephens](https://github.com/patrick-stephens)
+- [Leonardo Alminana](https://github.com/leonardo-albertovich)
+- [Eduardo Silva](https://github.com/edsiper)
+- [Stewart Webb](https://github.com/nuclearpidgeon)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.1/v3.1.2.md b/content/announcements/v3.1/v3.1.2.md
new file mode 100644
index 0000000..7ffdab1
--- /dev/null
+++ b/content/announcements/v3.1/v3.1.2.md
@@ -0,0 +1,61 @@
+---
+title: 'v3.1.2'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.1.2/"
+release_date: 2024-07-12
+publishdate: 2024-07-12
+ver: v3.1.2
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.1.2
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.1.2**.
+
+
+
+### What's new ?
+
+
+
+ - __Core__
+ - build: correctly fetch FLB_GIT_HASH from signed commit (#9070)
+ - input: Config parsing order fixed for FS storage pause parameter (#8720)
+
+
+
+ - __Pipeline Plugins__
+
+ - [Forward (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/forward/)
+ - Add plugin pause/resume mechanism
+ - [Tail (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/tail/)
+ - Add option `file_cache_advise` (default: on) to reduce file cache usage (less memory)
+ - [Log_To_Metric (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/log_to_metric/)
+ - Add emitter alias and mem limit
+ - [Opentelemetry (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/opentelemetry/)
+ - Restore manual parsing for log record fields (fix #9071)
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+- [Richard Treu](https://github.com/drbugfinder-work)
+- [Eduardo Silva](https://github.com/edsiper)
+- [xl-sec](https://github.com/xl-sec)
+- [Erik Bledsoe](https://github.com/erikbledsoe)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.1/v3.1.3.md b/content/announcements/v3.1/v3.1.3.md
new file mode 100644
index 0000000..1cb1589
--- /dev/null
+++ b/content/announcements/v3.1/v3.1.3.md
@@ -0,0 +1,63 @@
+---
+title: 'v3.1.3'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.1.3/"
+release_date: 2024-07-17
+publishdate: 2024-07-17
+ver: v3.1.3
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.1.3
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.1.3**.
+
+
+
+### What's new ?
+
+
+
+ - __Core__
+ - metrics: fix dynamic composing of old metric names (fix #9086)
+
+
+
+ - __Libraries__
+ - [CTraces](https://github.com/fluent/ctraces): upgrade to v0.5.2
+
+
+
+ - __Pipeline Plugins__
+ - [Winevtlog (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/winevtlog/)
+ - Retrieve messages of forwarded events correctly
+ - [Splunk (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/splunk/)
+ - Downgrade from error response to debug message when content-type is not set
+ - Fix issues when processing credentials and content-type
+ - [Datadog (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/datadog/)
+ - Fix default message key remapping (#9085)
+ - Fix typo for `dd_hostname` helper (#9032)
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+- [Philip Meier](https://github.com/pmeier)
+- [Eduardo Silva](https://github.com/edsiper)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+- [Jesse Szwedko](https://github.com/jszwedko)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.1/v3.1.4.md b/content/announcements/v3.1/v3.1.4.md
new file mode 100644
index 0000000..0eb1316
--- /dev/null
+++ b/content/announcements/v3.1/v3.1.4.md
@@ -0,0 +1,52 @@
+---
+title: 'v3.1.4'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.1.4/"
+release_date: 2024-07-25
+publishdate: 2024-07-25
+ver: v3.1.4
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.1.4
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.1.4**.
+
+
+
+### What's new ?
+
+
+
+ - __Core__
+ - input_chunk: do not `exit(0)` if cannot release old chunks
+ - log_to_metrics: allow custom namespace and subsystem (#9101)
+
+
+
+ - __Pipeline Plugins__
+ - [Stdout (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/stdout/)
+ - Consume entire metrics type of buffers (#9118)
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+- [Eduardo Silva](https://github.com/edsiper)
+- [Florian BEZANNIER](https://github.com/flobz)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.1/v3.1.5.md b/content/announcements/v3.1/v3.1.5.md
new file mode 100644
index 0000000..3c3318d
--- /dev/null
+++ b/content/announcements/v3.1/v3.1.5.md
@@ -0,0 +1,99 @@
+---
+title: 'v3.1.5'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.1.5/"
+release_date: 2024-08-09
+publishdate: 2024-08-09
+ver: v3.1.5
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.1.5
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.1.5**.
+
+
+
+### What's new ?
+
+
+
+ - __Core__
+ - log_event_decoder: updated code to use aligned memory reads
+ - gzip: add support for concatenated GZip payloads
+ - wasm: Make configurable heap and stack sizes with a struct type
+ - core: add new `FLB_ENFORCE_ALIGNMENT` cmake option for old targets
+ - core: add new option `FLB_PREFER_SYSTEM_LIB_LUAJIT` to use system provided (external) LuaJIT
+
+
+
+ - __Libraries__
+ - ctraces: upgrade to v0.5.4
+ - cmetrics: upgrade to v0.9.3
+ - cfl: upgrade to v0.5.2
+ - c-ares: ugprade to v1.32.3
+
+
+
+ - __Pipeline Plugins__
+ - [MQTT (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/mqtt/)
+ - Add `buffer_size` setting and fixed a leak (#9163)
+ - [Tail (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/tail/)
+ - Fix double-free on exception (cid 507963)
+ - [Node_Exporter_Metrics (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/node_exporter_metrics/)
+ - Align the collecting metrics of unit statuses (#9134)
+ - [Forward (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/forward/)
+ - Fix leak on exception (cid 507786)
+ - Fix leak on exception (cid 508219)
+ - Add support for concatenated GZip payloads
+ - [Kubernetes_Events (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/kubernetes_events/)
+ - Fix end of chunked stream deadlock
+ - Add chunked streaming test
+ - [Exec_Wasi (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/exec_wasi/)
+ - Provide configurable stack and heap sizes for wasm
+ - [Emitter (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/emitter/)
+ - Fix use-after-free on exception (cid 507860)
+ - [Wasm (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/wasm/)
+ - Provide configurable heap and stack sizes for WASM
+ - [Log_To_Metrics (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/log_to_metrics/)
+ - Add new option `discard_logs`
+ - [Opensearch (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/opensearch/)
+ - Fixed wrong payload buffer usage for traces
+ - [S3 (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/s3/)
+ - Plug memory leaks on gzipped buffer during the swapping contents
+ - [Oracle_Log_Analytics (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/oracle_log_analytics/)
+ - Fix to prevent double free
+ - [Kafka (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/kafka/)
+ - Add missing initialization (cid 507783)
+ - [Prometheus_Exporter (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/prometheus_exporter/)
+ - Handle multiply concatenated metrics type of events (#9122)
+ - [Stackdriver (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/stackdriver/)
+ - Fix leak on exception (cid 508239)
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+- [Ryan Ohnemus](https://github.com/ryanohnemus)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+- [Leonardo Alminana](https://github.com/leonardo-albertovich)
+- [Eduardo Silva](https://github.com/edsiper)
+- [Thomas Devoogdt](https://github.com/ThomasDevoogdt)
+- [kangaechu](https://github.com/kangaechu)
+- [Pat](https://github.com/patrick-stephens)
+- [Takahiro Yamashita](https://github.com/nokute78)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.1/v3.1.6.md b/content/announcements/v3.1/v3.1.6.md
new file mode 100644
index 0000000..2fcb0c7
--- /dev/null
+++ b/content/announcements/v3.1/v3.1.6.md
@@ -0,0 +1,87 @@
+---
+title: 'v3.1.6'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.1.6/"
+release_date: 2024-08-09
+publishdate: 2024-08-09
+ver: v3.1.6
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.1.6
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.1.6**.
+
+
+
+### What's new ?
+
+
+
+ - __Core__
+ - parser: declare ambiguous DST
+ - upstream_ha: fix memory leaks
+ - upstream_node: process `tls.verify_hostname` parameter
+ - azure_blob_http: use sds_cat variant (CID 306764 306765)
+ - pack: do not multiply out_size by realloc_size (#9193)
+
+
+
+ - __Libraries__
+ - ctraces: upgrade to v0.5.5
+ - cmetrics: upgrade to v0.9.4
+
+
+
+ - __Pipeline Plugins__
+ - [StatsD (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/statsd/)
+ - Implement statsd decoder to translate metrics type of events
+ - [HTTP (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/http/)
+ - Add flexible handling of content-type for application/json* (#9190)
+ - Use cat_safe on tag handling
+ - [Splunk (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/splunk/)
+ - Release uri on exception (cid 507867)
+ - [Forward (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/forward/)
+ - Fix resource leak on exception (cid 508219) (#9209)
+ - Fix leaks when processing metrics and traces (#9199)
+ - [Kubernetes_Events (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/kubernetes_events/)
+ - Use time_t for time(null) returned value (cid 507947)
+ - [Exec_Wasi (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/exec_wasi/)
+ - Fix resource leak on exception (cid 508347) (#9208)
+ - [Cloudwatch_Logs (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/cloudwatch_logs/)
+ - Fix disabling of `auto_create_group` config option
+ - [Datadog (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/datadog/)
+ - Use cat_safe for remapped tags (cid 253605)
+ - [Azure_Kusto (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/azure_kusto/)
+ - Follow the creating node function change
+ - [Stackdriver (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/stackdriver/)
+ - Release `log_name` on exception (cid 313112)
+ - Add latency metric for write log entries http request. (#9182)
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+- [Ryan Ohnemus](https://github.com/ryanohnemus)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+- [Leonardo Alminana](https://github.com/leonardo-albertovich)
+- [Eduardo Silva](https://github.com/edsiper)
+- [Thomas Devoogdt](https://github.com/ThomasDevoogdt)
+- [kangaechu](https://github.com/kangaechu)
+- [Pat](https://github.com/patrick-stephens)
+- [Takahiro Yamashita](https://github.com/nokute78)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.1/v3.1.7.md b/content/announcements/v3.1/v3.1.7.md
new file mode 100644
index 0000000..4527929
--- /dev/null
+++ b/content/announcements/v3.1/v3.1.7.md
@@ -0,0 +1,164 @@
+---
+title: 'v3.1.7'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.1.7/"
+release_date: 2024-08-09
+publishdate: 2024-08-09
+ver: v3.1.7
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.1.7
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.1.7**.
+
+
+
+### What's new ?
+
+
+
+ - __Core__
+ - config_map: fix configuration type cast issue found on s390x (#8904)
+ - utils:
+ - fix compatibility for macOS < 12 (#9217)
+ - use MachineGUID correctly on Windows
+ - output_thread: add simple conditional on event handling
+ - examples: filter_wasm_go: Upgrade to support Go 1.22.5 and TinyGo 0.32
+ - network: fixed a wrong data type used for an option
+ - build: use the system provided lib luajit for s390x (#9172)
+ - build: added cpu byte order detection (same as msgpack-c)
+ - build: add build time event loop selection
+ - upstream_ht: added support for inherited property lookup
+ - upstream_ht: added environment variable support
+ - bin: fix memory leaks (#9310)
+ - scheduler: new wrapper for timers to consume notification byte
+ - sp: changed property type to prevent lossy cast
+ - static analysis related fixes:
+ - regex: check return of strchr (CID 507956)
+ - aws: release resource on exception (CID 50 8048)
+ - record_accessor: Plug a resource leak on exception (CID 508119)
+ - processor_content_modifier: logs: do not remove object on type excepcion (CID 507615)
+ - aws_util: release resource on exception (CID 507694 507588)
+ - reload: added appropriate type cast (CID 508209)
+ - output: Remove a needless calling of flb_output_instance_destroy() (CID 507809)
+ - log_event_encoder: log_event_decoder: enhanced byte order handling for timestamps (#9196)
+
+
+
+ - __Libraries__
+ - lib: cmetrics: upgrade to v0.9.5
+ - lib: c-ares: upgrade to v1.33.1
+ - lib: monkey: sync poll(2) new backend support
+
+
+
+ - __Pipeline Plugins__
+ - [Nginx_Exporter_Metrics (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/nginx_exporter_metrics/)
+ - Fixed a wrong data type used for an option
+ - [Dummy (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/dummy/)
+ - Fix the timestamp issue on s390x
+ - [Head (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/head/)
+ - Fix cannot allocate memory on big endian system
+ - [Process_Exporter_Metrics (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/process_exporter_metrics/)
+ - Initialize with null for flb_sds_t pointer variables (cid 507975)
+ - [Event_Type (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/event_type/)
+ - Fix a resource leak on exception (cid 507968) (#9235)
+ - [Prometheus_Remote_Write (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/prometheus_remote_write/)
+ - Use sds_cat_safe (cid 508087)
+ - [Winevtlog (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/winevtlog/)
+ - Remove a needless third argument
+ - Add a describing link for capability sids
+ - Skip to translate sid for capability sids
+ - [Podman_Metrics (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/podman_metrics/)
+ - Plug a resource leak on exception (cid 507805)
+ - [Collectd (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/collectd/)
+ - Fixed out of bounds read
+ - [Opentelemetry (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/opentelemetry/)
+ - Fixed a wrong data type used for an option
+ - [Node_Exporter_Metrics (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/node_exporter_metrics/)
+ - Fixed possible invalid dereference
+ - [Elasticsearch (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/elasticsearch/)
+ - Fix string in http response code 400 (#8977)
+ - Store log_encoder pointer (cid 508245)
+ - [Splunk (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/splunk/)
+ - handle 1.0 suffixed endpoints
+ - [Forward (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/forward/)
+ - Release resource on exception (cid 508219)
+ - Rel resources on exception (cid 507596 507786 507954 508064 508123)
+ - [Docker (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/docker/)
+ - Release resource on exception (cid 507574)
+ - [Emitter (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/emitter/)
+ - Plug a possible resource leak on exception (cid 508193)
+ - [Kubernetes (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/kubernetes/)
+ - Fix data type for token creation (cid 507947)
+ - [Aws (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/aws/)
+ - Fixed group metadata fetch issue and addressed (cid 507941)
+ - [Logs_To_Metrics (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/logs_to_metrics/)
+ - Fixed memory corruption issue
+ - [Multiline (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/multiline/)
+ - Fix conditional after allocation (cid 507750)
+ - [Tensorflow (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/tensorflow/)
+ - Fixed a wrong data type used for a boolean option
+ - [Alter_Size (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/alter_size/)
+ - Fixed memory leak
+ - [Logdna (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/logdna/)
+ - Refactored logdna uri formation to support configurable endpoints (#8051)
+ - [Opensearch (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/opensearch/)
+ - Fix a use-after-free issue (cid 508013) (#9233)
+ - Fixed a wrong data type used for a boolean option (#9221)
+ - [Chronicle (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/chronicle/)
+ - Use flb_sds_cat_safe (cid 507603)
+ - Fix a resource leak on exception (cid 508008) (#9234)
+ - [S3 (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/s3/)
+ - Plug an error for too many argument for mkdir
+ - Fix double free (cid 508202)
+ - [Opentelemetry (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/opentelemetry/)
+ - Prevent null dereference on memcpy (cid 507910)
+ - Skip ra_trace_flags_metadata check (cid 508199)
+ - Fix record accessor pattern (cid 507960)
+ - Release buf on exception (cid 507777)
+ - logs: release scope on exception (cid 507600)
+ - On proxy config check status
+ - [Azure_Blob (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/azure_blob/)
+ - Fixed double free
+ - [Elasticsearch (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/elasticsearch/)
+ - Process error information properly
+ - [Cloudwatch_Logs (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/cloudwatch_logs/)
+ - Release resources on exception (cid 507707)
+ - [Stackdriver (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/stackdriver/)
+ - Fixed a wrong data type used for two boolean options
+ - [Loki (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/loki/)
+ - Use sds_cat_safe (cid 507977 311957)
+ - [Calyptia (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/calyptia/)
+ - Initialize return and http context (cid 507836)
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+- [Leonardo Alminana](https://github.com/leonardo-albertovich)
+- [Eduardo Silva](https://github.com/edsiper)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+- Sergey Fedorov
+- Mirko Lazarevic
+- rightblank (IBM)
+- José Lecaros
+- JinXinWang
+- [Phillip Whelan](https://github.com/pwhelan)
+- YingJie Fu (IBM)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.1/v3.1.8.md b/content/announcements/v3.1/v3.1.8.md
new file mode 100644
index 0000000..07ab876
--- /dev/null
+++ b/content/announcements/v3.1/v3.1.8.md
@@ -0,0 +1,71 @@
+---
+title: 'v3.1.8'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.1.8/"
+release_date: 2024-09-16
+publishdate: 2024-09-16
+ver: v3.1.8
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.1.8
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.1.8**.
+
+
+
+### What's new ?
+
+
+
+ - __Core__
+ - tls: check async status before using coroutines in flb_tls_session_create.
+ - io: use connection flags when setting async in flb_io_net_connect.
+ - input: added missing initializer (CID 508207) (#9332)
+
+
+
+ - __Libraries__
+ - lib: cmetrics: upgrade to v0.9.6
+
+
+
+ - __Pipeline Plugins__
+ - [Calyptia_Fleet (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/calyptia_fleet/)
+ - Fixed memory leaks (cid 508187) (#9347)
+ - [Elasticsearch (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/elasticsearch/)
+ - Fixed potential memory leak
+ - Improved buffer size check
+ - [Opentelemetry (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/opentelemetry/)
+ - Fixed memory leaks on exception
+ - [HTTP (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/http/)
+ - Request timed out(408) to be treated as retry (#9379)
+ - [Influxdb (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/influxdb/)
+ - Handle signed/unsigned integer as influx's integer of that representation (#9361)
+ - [Splunk (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/splunk/)
+ - Extend retrying http status code (#9380)
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+
+- [Eduardo Silva](https://github.com/edsiper)
+- [Phillip Whelan](https://github.com/pwhelan)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+- [Leonardo Alminana](https://github.com/leonardo-albertovich)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.1/v3.1.9.md b/content/announcements/v3.1/v3.1.9.md
new file mode 100644
index 0000000..571b2b9
--- /dev/null
+++ b/content/announcements/v3.1/v3.1.9.md
@@ -0,0 +1,71 @@
+---
+title: 'v3.1.9'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.1.9/"
+release_date: 2024-09-27
+publishdate: 2024-09-27
+ver: v3.1.9
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.1.9
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.1.9**.
+
+
+
+### What's new ?
+
+
+
+ - __Core__
+ - multiline: reset group metadata buffer on flush (fix high CPU issue)
+ - reload: do not call `flb_stop()` when `flb_start()` fails (fix crash on RHEL)
+ - utils: improve error messaging inside the `flb_utils_proxy_url_split()`
+ - config_format: yaml: cleanup variants only if occurred an exception
+ - config_format: yaml: Plug memory leaks on exception for variants on plugin elements
+ - upstream: remove call to `flb_errno()` when is not needed.
+
+
+
+ - __Libraries__
+ - lib: ctraces: upgrade to v0.5.6
+
+
+
+ - __Pipeline Plugins__
+ - [Calyptia_Fleet (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/calyptia_fleet/)
+ - Fix 'unable to find fleet by name' (backport of #9410).
+ - [Elasticsearch (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/elasticsearch/)
+ - Fix potential issue caused by ingored reallocation
+ - [Multiline (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/multiline/)
+ - Reset group metadata buffer on flush
+ - [Calyptia (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/calyptia/)
+ - Add missing parameter for msgpack_str for windows os field.
+ - Register os and architecture for agents.
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+- [Richard Treu](https://github.com/drbugfinder-work)
+- [Jose Lecaros](https://github.com/lecaros)
+- [Phillip Whelan](https://github.com/pwhelan)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+- [Leonardo Alminana](https://github.com/leonardo-albertovich)
+- [Eduardo Silva](https://github.com/edsiper)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.2/_index.md b/content/announcements/v3.2/_index.md
new file mode 100644
index 0000000..e438caa
--- /dev/null
+++ b/content/announcements/v3.2/_index.md
@@ -0,0 +1,15 @@
+---
+title: 'Fluent Bit v3.2 Series'
+description: "[Fluent Bit v3.2](https://github.com/fluent/fluent-bit/tree/master) is the new **stable branch** for production usage. Based on bug reports or
+specific minor feature requests, we do quick releases upon demand. Below is a list of the notes for each version."
+url: "/announcements/v3.2/"
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+releaseNotes:
+ heading: "Release Notes v3.2.0"
+ version: "v3.2.0"
+ text: "Fluent Bit is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD and OSX. We are proud to announce the availability of Fluent Bit v1.9.9.
+ For people upgrading from previous versions you must read the Upgrading Notes section of our documentation:
+ https://docs.fluentbit.io/manual/installation/upgrade_notes"
+---
+
diff --git a/content/announcements/v3.2/v3.2.0.md b/content/announcements/v3.2/v3.2.0.md
new file mode 100644
index 0000000..96d5f55
--- /dev/null
+++ b/content/announcements/v3.2/v3.2.0.md
@@ -0,0 +1,182 @@
+---
+title: 'v3.2.0'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.2.0/"
+release_date: 2024-11-12
+publishdate: 2024-11-12
+ver: v3.2.0
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.2.0
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Telemetry Agent for Linux, BSD, MacOS and Windows. We are proud to announce the availability of **Fluent Bit v3.1**.
+
+```
+Fluent Bit v3.2.0
+* Copyright (C) 2015-2024 The Fluent Bit Authors
+* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
+* https://fluentbit.io
+
+______ _ _ ______ _ _ _____ _____
+| ___| | | | | ___ (_) | |____ |/ __ \
+| |_ | |_ _ ___ _ __ | |_ | |_/ /_| |_ __ __ / /`' / /'
+| _| | | | | |/ _ \ '_ \| __| | ___ \ | __| \ \ / / \ \ / /
+| | | | |_| | __/ | | | |_ | |_/ / | |_ \ V /.___/ /./ /___
+\_| |_|\__,_|\___|_| |_|\__| \____/|_|\__| \_/ \____(_)_____/
+
+
+[2024/11/11 20:40:02] [ info] [fluent bit] version=3.2.0, commit=58cc2d5944, pid=3050130
+[2024/11/11 20:40:02] [ info] [storage] ver=1.5.2, type=memory, sync=normal, checksum=off, max_chunks_up=128
+[2024/11/11 20:40:02] [ info] [simd ] SSE2
+[2024/11/11 20:40:02] [ info] [cmetrics] version=0.9.9
+[2024/11/11 20:40:02] [ info] [ctraces ] version=0.5.7
+[2024/11/11 20:40:02] [ info] [sp] stream processor started
+```
+
+For people upgrading from previous versions you **must read** the Upgrading Notes section of our documentation:
+
+[https://docs.fluentbit.io/manual/installation/upgrade_notes](https://docs.fluentbit.io/manual/installation/upgrade_notes)
+
+### Introduction
+
+Fluent Bit, a CNCF graduated project under the umbrella of Fluentd, announces the availability of v3.2.
+
+In every release, there are many improvements and fixes, on this notes we will refer to the major changes that will make your infrastructure happier ;)
+
+Below a list of the highlights of this release:
+
+### Complete YAML Support
+
+Fluent Bit is moving away from its classic configuration mode, which only supports basic key-value pairs and lacks advanced features. YAML, now fully supported in Fluent Bit v3.2, offers a more intuitive and flexible configuration experience, essential for modern cloud environments. We encourage users to transition to YAML to take advantage of features like processors.
+
+For more details refer to the official documentation:
+
+
+- [YAML Configuration](https://docs.fluentbit.io/manual/administration/configuring-fluent-bit/yaml)
+
+
+### SIMD Support
+
+The JSON encoder now supports SIMD operations which helps to improve the performance of JSON encoding. SIMD is a set of instructions that can be executed in parallel on multiple data points. This feature is disabled by default, but can be enabled by setting the CMake `FLB_SIMD` option to `on`.
+
+
+- [SIMD for JSON encoding](https://docs.fluentbit.io/manual/3.2-dev/administration/performance#fluent-bit-and-simd-for-json-encoding)
+
+### Blob Support
+
+Fluent Bit now supports the `blob` data type, which is a binary large object that can store large amounts of data. This feature is useful for storing large log messages, binary data, or other large data types that needs to be delivered in order.
+
+For this implementation the following plugins are supported:
+
+- Blob input: read data from a file or a stream and send it to the pipeline.
+- Azure Blob: extended support to handle Blob data type.
+
+### Experimental Features
+
+The following experimental features, are still under active development and are not recommended for production use. However, we encourage you to try them out and provide feedback to help us improve them.
+
+Note that experimental features are disabled by default, but can be enabled at build time.
+
+#### eBPF
+
+Fluent Bit now supports eBPF, a powerful technology that allows you to run custom code in the Linux kernel. The plugin, allows to load eBPF programs and attach them to kernel probes, which can be used to collect data from the kernel.
+
+This feature is experimental and disabled by default, but can be enabled by setting the CMake `FLB_EBPF` option to `on`.
+
+#### Profiles (signal types)
+
+Following the development version of OpenTelemetry Profile specification, Fluent Bit now supports profiles signal types.
+
+### Libraries
+ - cmetrics: upgrade to v0.9.9
+ - fluent-otel-proto: update files for latest profiles support
+ - ctraces: upgrade to v0.5.7
+ - monkey: upgrade to v1.8.1
+
+### Plugins
+
+ - Plugins
+ - [Opentelemetry (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/opentelemetry/)
+ - Adjust HTTP/1.1 buffer based on the request size
+ - Add support for HTTP/1.1 chunked transfer encoding
+ - Add `tag_from_uri` support to HTTP/2 code path
+ - [HTTP (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/http/)
+ - Adjust HTTP/1.1 buffer based on the request size
+ - Add support for HTTP/1.1 chunked transfer encoding
+ - [eBPF (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/ebpf/)
+ - Initial version of the plugin (experimental)
+ - [Calyptia_Fleet (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/calyptia_fleet/)
+ - Fix registering agent after first invocation.
+ - Increase max http buffer size and make it configurable.
+ - Fleet id search by name must use exact name. (#9561)
+ - Fix `unable to find fleet by name`.
+ - Fixed memory leaks (cid 508187) (#9346)
+ - [Elasticsearch (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/elasticsearch/)
+ - Add support for chunked transfer encoding
+ - Fixed potential issue caused by ingored reallocation
+ - Improved buffer size check
+ - [Blob (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/blob/)
+ - New plugin to read binary/large files and process them as Blob data type
+ - [Splunk (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/splunk/)
+ - Small fixes on return values (cid 508015 508060 510619)
+ - Adjust HTTP/1.1 buffer based on the request size
+ - Add support for HTTP/1.1 chunked transfer encoding
+ - [Forward (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/forward/)
+ - Fixed incorrect `shared key` length in authentication (#9550)
+ - Fix leaks on exception (cid 507786 507954 508064)
+ - Validate return value when ingesting data (cid 507683)
+ - Release shared salt on exception (cid 507596)
+ - [Multiline (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/multiline/)
+ - Add support for Processors
+ - Reset group metadata buffer on flush
+ - [Log_To_Metrics (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/log_to_metrics/)
+ - Add timer callback for emitting metrics this commit will change the log_to_metrics filter to use a timer based metric inject and not directly inject metrics on every incoming log record anymore. this will lower the overall load and memory consumption especially in high-volume and high-cardinality situations.
+ - [Datadog (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/datadog/)
+ - Custom added ability to set custom HTTP headers
+ - [HTTP (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/http/)
+ - Request timed out(408) to be treated as retry
+ - [Stdout (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/stdout/)
+ - Support blob type (print targe file name)
+ - [S3 (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/s3/)
+ - Release context on mock client exception (cid 310831)
+ - Fix buffered data on exception (cid 309438)
+ - [Influxdb (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/influxdb/)
+ - Test: follow the change of parameter name
+ - Use `add_integer_suffix` name for adding integer suffix on the line protocol
+ - Provide a way to turn on to use integer type on influxdb's line protocol
+ - Handle signed/unsigned integer as influx's integer of that representation
+ - [Kafka (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/kafka/)
+ - Fix invalid free of the message_key
+ - Introduce the raw_log_key option raw format
+ - [Opentelemetry (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/opentelemetry/)
+ - Added HTTP/2 and gRPC support
+ - Fix check for uri sanitization when exiting
+ - [Azure_Blob (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/azure_blob/)
+ - Add support for Blob data type
+ - [Splunk (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/splunk/)
+ - Extend retrying http status code
+ - [Calyptia (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/calyptia/)
+ - Add missing parameter for msgpack_str for windows os field.
+ - Register os and architecture for agents.
+ - [Kinesis_Streams (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/kinesis_streams/)
+ - Add custom port support for kinesis output plugin
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.2/v3.2.1.md b/content/announcements/v3.2/v3.2.1.md
new file mode 100644
index 0000000..921b87a
--- /dev/null
+++ b/content/announcements/v3.2/v3.2.1.md
@@ -0,0 +1,61 @@
+---
+title: 'v3.2.1'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.2.1/"
+release_date: 2024-11-16
+publishdate: 2024-11-16
+ver: v3.2.1
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.2.1
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.2.1**.
+
+
+
+### What's new ?
+
+
+
+ - __Core__
+ - tls: removed alpn selector requirement
+ - config_format: cf_yaml: Follow the change of variable name
+ - config_format: cf_fluentbit: Handle static config correctly
+
+
+
+ - __Pipeline Plugins__
+ - [Splunk (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/splunk/)
+ - Splunk token validation must be case-insensitive, since that's the behavior from splunk hec
+ - [eBPF (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/ebpf/)
+ - Handle debian like systems' signal probes (#9596)
+ - Prepare build directory for building ebpf objects (#9592)
+ - [Kubernetes (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/kubernetes/)
+ - Retrieve kubernetes pod ip address if it is set in status.podip (#2783)
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+- [Richard Treu](https://github.com/drbugfinder-work)
+- [Jose Lecaros](https://github.com/lecaros)
+- [Phillip Whelan](https://github.com/pwhelan)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+- [Leonardo Alminana](https://github.com/leonardo-albertovich)
+- [Eduardo Silva](https://github.com/edsiper)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.2/v3.2.2.md b/content/announcements/v3.2/v3.2.2.md
new file mode 100644
index 0000000..ed441eb
--- /dev/null
+++ b/content/announcements/v3.2/v3.2.2.md
@@ -0,0 +1,108 @@
+---
+title: 'v3.2.2'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.2.2/"
+release_date: 2024-11-27
+publishdate: 2024-11-27
+ver: v3.2.2
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.2.2
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.2.2**.
+
+
+
+### What's new ?
+
+
+
+#### Core
+- http_client
+ - added missing exit path ([PR #9607](https://github.com/fluent/fluent-bit/pull/9607))
+ - fixed potential memory corruption ([PR #9611](https://github.com/fluent/fluent-bit/pull/9611))
+ - added missing exit path ([PR #9612](https://github.com/fluent/fluent-bit/pull/9612))
+ - added per client temporary buffer ([PR #9645](https://github.com/fluent/fluent-bit/pull/9645))
+ - added per session temporary buffer ([PR #9645](https://github.com/fluent/fluent-bit/pull/9645))
+ - Implement response testing framework ([PR #9401](https://github.com/fluent/fluent-bit/pull/9401))
+- http_common
+ - added missing initializers ([PR #9608](https://github.com/fluent/fluent-bit/pull/9608))
+ - moved initializers to correct a bug introduced in PR 9608 ([PR #9619](https://github.com/fluent/fluent-bit/pull/9619))
+ - added guards to prevent leaks ([PR #9645](https://github.com/fluent/fluent-bit/pull/9645))
+ - added pre-generated authority field ([PR #9645](https://github.com/fluent/fluent-bit/pull/9645))
+- signv4: added missing length calculation ([PR #9606](https://github.com/fluent/fluent-bit/pull/9606))
+- plugin: Plug a use-after-free issue (CID 514582) ([PR #9639](https://github.com/fluent/fluent-bit/pull/9639))
+- build: made FLB_DEV detectable from code ([PR #9645](https://github.com/fluent/fluent-bit/pull/9645))
+- tls: openssl: added support for SSLKEYLOGFILE on DEV builds ([PR #9645](https://github.com/fluent/fluent-bit/pull/9645))
+- http_client_http2
+ - improved protocol compliance ([PR #9645](https://github.com/fluent/fluent-bit/pull/9645))
+ - added missing header ([PR #9645](https://github.com/fluent/fluent-bit/pull/9645))
+- output: Add a capability to inject HTTP response testing environment ([PR #9401](https://github.com/fluent/fluent-bit/pull/9401))
+- lib: Implement injecting HTTP response mechanism ([PR #9401](https://github.com/fluent/fluent-bit/pull/9401))
+- network
+ - Update struct type for sock_addr ([PR #9404](https://github.com/fluent/fluent-bit/pull/9404))
+ - Update struct type being passed into accept ([PR #9404](https://github.com/fluent/fluent-bit/pull/9404))
+
+
+
+
+ #### Pipeline Plugins
+
+- **[Forward (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/forward)**
+ - Plug a resource leak on exception (CID 508064) ([PR #9616](https://github.com/fluent/fluent-bit/pull/9616))
+- **[Opentelemetry (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/opentelemetry)**
+ - Propogate tag in http2 metrics and trace handlers ([PR #9635](https://github.com/fluent/fluent-bit/pull/9635))
+- **[Calyptia_fleet (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/calyptia_fleet)**
+ - improved interval handling ([PR #9648](https://github.com/fluent/fluent-bit/pull/9648))
+- **[HTTP (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/http)**
+ - use 'tag_key' option when json array is received ([PR #9590](https://github.com/fluent/fluent-bit/pull/9590))
+- **[Lua (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/lua)**
+ - expose env variables in FLB_ENV Lua table ([PR #9617](https://github.com/fluent/fluent-bit/pull/9617))
+- **[Labels (Processor)](https://docs.fluentbit.io/manual/pipeline/processors/labels)**
+ - Process operations for output purposed contexts of metrics instead of the original one ([PR #9632](https://github.com/fluent/fluent-bit/pull/9632))
+- **[Opentelemetry (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/opentelemetry)**
+ - added missing result checks and fixed leaks ([PR #9609](https://github.com/fluent/fluent-bit/pull/9609))
+ - decoupled HTTP/2 and gRPC ([PR #9645](https://github.com/fluent/fluent-bit/pull/9645))
+- **[Azure_kusto (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/azure_kusto )**
+ - fix multiple files tail issue and timeout issue (#8430) ([PR #8430](https://github.com/fluent/fluent-bit/pull/8430))
+- **[Stackdriver (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/stackdriver)**
+ - return cached token when current_timestamp is less than cached_expiration (#9652) ([PR #9652](https://github.com/fluent/fluent-bit/pull/9652))
+- **[Elasticsearch (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/es)**
+ - tests: Add HTTP response testing ([PR #9401](https://github.com/fluent/fluent-bit/pull/9401))
+- **[Calyptia (Custom)](https://docs.fluentbit.io/manual/pipeline/customs/calyptia)**
+ - added interval handling and tests ([PR #9648](https://github.com/fluent/fluent-bit/pull/9648))
+
+- **[Node Exporter Metrics](https://docs.fluentbit.io/manual/pipeline/inputs/node_exporter_metrics)** :
+ - Use real_path for complaining on glob(3) error ([PR #9618](https://github.com/fluent/fluent-bit/pull/9618))
+
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+
+- [leonardo-albertovich](https://github.com/leonardo-albertovich)
+- [Marat Abrarov](https://github.com/mabrarov)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+- [Tanmaya Panda](https://github.com/tanmaya-panda1)
+- [Stewart Webb](https://github.com/nuclearpidgeon)
+- [Eduardo Silva Pereira](https://github.com/edsiper)
+- [shuaichen](https://github.com/shuaich)
+- [Ankur Patel](https://github.com/imankurpatel000)
+- [jomillerOpen](https://github.com/jomillerOpen)
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/announcements/v3.2/v3.2.3.md b/content/announcements/v3.2/v3.2.3.md
new file mode 100644
index 0000000..fcf38a4
--- /dev/null
+++ b/content/announcements/v3.2/v3.2.3.md
@@ -0,0 +1,108 @@
+---
+title: 'v3.2.3'
+description: 'Next generation Telemetry Agent for Logs, Metrics and Traces. '
+url: "/announcements/v3.2.3/"
+release_date: 2024-12-19
+publishdate: 2024-12-19
+ver: v3.2.3
+herobg: "/images/hero@2x.jpg"
+latestVer: true
+---
+
+###### KNOWLEDGE BASE
+
+## Release Notes v3.2.3
+
+[Fluent Bit](https://fluentbit.io) is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD, Windows and macOS. We are proud to announce the availability of **Fluent Bit v3.2.3**.
+
+
+
+### What's new ?
+
+
+
+#### Core
+
+- http_server: hs: Handle IPv4 and IPv6 addresses ([PR #9449](https://github.com/fluent/fluent-bit/pull/9449))
+- utf8
+ - enhance handling of multibyte sequences ([PR #9687](https://github.com/fluent/fluent-bit/pull/9687))
+ - remove lookup table ([PR #9687](https://github.com/fluent/fluent-bit/pull/9687))
+- build
+ - cmake: fix UNICODE-escaped characters on aarch64 (#8851) ([PR #8851](https://github.com/fluent/fluent-bit/pull/8851))
+ - Use signed char in RISC-V 64bit (#9524) ([PR #9524](https://github.com/fluent/fluent-bit/pull/9524))
+ - add flb_utf8.c ([PR #9687](https://github.com/fluent/fluent-bit/pull/9687))
+ - added include path for the headers cprofiles generates ([PR #9747](https://github.com/fluent/fluent-bit/pull/9747))
+- wasm: Plug a resource leak on exception (CID 508177) (#9615) ([PR #9615](https://github.com/fluent/fluent-bit/pull/9615))
+- input: Add callback member for testing input format ([PR #9291](https://github.com/fluent/fluent-bit/pull/9291))
+- cfl_ra_key: Implement generic CFL based RA key functionality ([PR #9566](https://github.com/fluent/fluent-bit/pull/9566))
+- cfl_record_accessor
+ - Implement generic CFL based record accessor ([PR #9566](https://github.com/fluent/fluent-bit/pull/9566))
+ - tests: internal: Add internal test cases for generic CFL based RA ([PR #9566](https://github.com/fluent/fluent-bit/pull/9566))
+ - Plug resource leaks (CID 516097) ([PR #9728](https://github.com/fluent/fluent-bit/pull/9728))
+- utils
+ - Detect machine_id corruption and fill out a dummy value ([PR #9690](https://github.com/fluent/fluent-bit/pull/9690))
+ - use new utf8 decoder API ([PR #9687](https://github.com/fluent/fluent-bit/pull/9687))
+ - add utf8 encoding for codepoints beyond BMP ([PR #9687](https://github.com/fluent/fluent-bit/pull/9687))
+- sds
+ - use new utf8 decoder for sds_cat_utf8 ([PR #9687](https://github.com/fluent/fluent-bit/pull/9687))
+- plugin: Detect config format and use a proper loader ([PR #9738](https://github.com/fluent/fluent-bit/pull/9738))
+- plugin_proxy: Allow to execute flush callback on Golang side during hot-reloading (#9734) ([PR #9734](https://github.com/fluent/fluent-bit/pull/9734))
+
+#### Libraries
+ - c-ares: upgrade to v1.34.4 ([PR #9747](https://github.com/fluent/fluent-bit/pull/9747))
+ - cprofiles: upgrade to v0.1.0 ([PR #9747](https://github.com/fluent/fluent-bit/pull/9747))
+ - wasm-micro-runtime: Bump up wasm-micro-runtime to v1.3.3 ([PR #9643](https://github.com/fluent/fluent-bit/pull/9643))
+
+#### Plugins
+
+- **[Winevtlog (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/winevtlog)**
+ - Use correct flag for EvtRender ([PR #9659](https://github.com/fluent/fluent-bit/pull/9659))
+- **[Process_exporter_metrics (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/process_exporter_metrics)**
+ - fix error logic when directory cannot be opened (#9549) ([PR #9549](https://github.com/fluent/fluent-bit/pull/9549))
+- **[Systemd (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/systemd)**
+ - Process enumerated data as cfl_kvlist(s) at first ([PR #9291](https://github.com/fluent/fluent-bit/pull/9291))
+ - test: Add a format test case for duplicated keys ([PR #9291](https://github.com/fluent/fluent-bit/pull/9291))
+- **[Forward (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/forward)**
+ - Support `empty_shared_key` parameter (#9681) ([PR #9681](https://github.com/fluent/fluent-bit/pull/9681))
+ - Recreate connection when resumed ([PR #9605](https://github.com/fluent/fluent-bit/pull/9605))
+- **[Opentelemetry (Input)](https://docs.fluentbit.io/manual/pipeline/inputs/opentelemetry)**
+ - logs: add support for OTel resource/scope metadata in JSON payload ([PR #9724](https://github.com/fluent/fluent-bit/pull/9724))
+- **[Parser (Filter)](https://docs.fluentbit.io/manual/pipeline/filters/parser)**
+ - fix reserve data and preserve key handling (#9675) ([PR #9675](https://github.com/fluent/fluent-bit/pull/9675))
+- **[Calyptia (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/calyptia)**
+ - retry agent registration on flush callback (#9656) ([PR #9656](https://github.com/fluent/fluent-bit/pull/9656))
+- **[Opentelemetry (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/opentelemetry)**
+ - remove strict check on severityText value ([PR #9724](https://github.com/fluent/fluent-bit/pull/9724))
+- **[Lib (Output)](https://docs.fluentbit.io/manual/pipeline/outputs/lib)**
+ - add new option `data_mode` ([PR #9724](https://github.com/fluent/fluent-bit/pull/9724))
+
+{{< contributor-list >}}
+
+#### Contributors
+
+On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
+
+## Contributors
+
+- [Jorge Niedbalski](https://github.com/niedbalski)
+- [Rama Malladi](https://github.com/RamaMalladiAWS)
+- [quocbao](https://github.com/baonq-me)
+- [Hiroshi Hatake](https://github.com/cosmo0920)
+- [Pat](https://github.com/patrick-stephens)
+- [Markus Frey](https://github.com/mkfrey)
+- [Lars](https://github.com/PromyLOPh)
+- [Erik Bledsoe](https://github.com/erikbledsoe)
+- [Eduardo Silva Pereira](https://github.com/edsiper)
+- [leonardo-albertovich](https://github.com/leonardo-albertovich)
+- [Ankur Patel](https://github.com/imankurpatel000)
+
+
+{{< /contributor-list >}}
+
+#### Join us
+
+We want to hear about you, our community is growing and you can be part of it!, you can contact us at:
+
+* Github: [http://github.com/fluent/fluent-bit](https://github.com/fluent/fluent-bit)
+* Slack: [http://slack.fluentd.org](http://slack.fluentd.org)
+* Twitter: [@fluentbit](https://twitter.com/fluentbit)
diff --git a/content/enterprise.md b/content/enterprise.md
index 0be6079..8c9ad31 100644
--- a/content/enterprise.md
+++ b/content/enterprise.md
@@ -10,16 +10,24 @@ enterprise:
enabled: true
position: 0
list:
- - title: Calyptia
- description: Support services and Enterprise features from the creators and maintainers of Fluentd and Fluent Bit.
- logo: /images/calyptia.svg
- buttonUrl: "https://calyptia.com/"
- buttonText: "read More"
+ - title: Chronosphere
+ description: Enterprise telemetry pipeline solution and support services from the creators of Fluent Bit and Calyptia. Recognized as a leader by major analyst firms, Chronosphere also offers a full observability platform.
+ logo: /images/chronosphere-logo-vertical.png
+ buttonUrl: "https://chronosphere.io/platform/telemetry-pipeline/?utm_source=fluent-bit&utm_medium=referral&utm_content=enterprise-tile"
+ buttonText: "Learn more"
tabOpen: "_blank"
- title: ITOCHU Techno-Solutions America, Inc.
description: "Enterprise services from a global IT solution provider. Services include: consulting, technology enablement, and a global service desk."
logo: /images/fluentd.svg
buttonUrl: "https://fluentd.ctc-america.com/"
- buttonText: "read More"
+ buttonText: "Learn more"
tabOpen: "_blank"
----
\ No newline at end of file
+ - title: ClearCode
+ description: >
+ ClearCode is a core maintainer of Fluentd since 2014, based in Japan.
+ クリアコードは、日本国内において航空会社、官公庁、通信事業者をはじめとした大規模ユーザーに対する支援を行ってきました。 ご相談にはFluentd/Fluent Bitのコアメンテナが対応いたしますので、まずはお気軽にお問い合わせください。
+ logo: /images/ClearCode.svg
+ buttonUrl: "https://www.clear-code.com/services/fluentd.html"
+ buttonText: "Learn more"
+ tabOpen: "_blank"
+---
diff --git a/content/how-it-works.md b/content/how-it-works.md
index 343c469..aee5fe8 100644
--- a/content/how-it-works.md
+++ b/content/how-it-works.md
@@ -1,10 +1,10 @@
---
title: 'How It Works'
-description: 'Works for Logs and Metrics'
+description: 'Works for Logs, Metrics and Traces'
type: how-it-works
hero:
heading: |
- Works for Logs and Metrics
+ Works for Logs, Metrics & Traces
desc: |
Fluent Bit was designed for speed, scale, and flexibility in a very lightweight, efficient package.
image: "/images/overview-new.svg"
diff --git a/content/opentelemetry.md b/content/opentelemetry.md
new file mode 100644
index 0000000..e667b59
--- /dev/null
+++ b/content/opentelemetry.md
@@ -0,0 +1,81 @@
+---
+title: 'OpenTelemetry with Fluent Bit'
+description: >
+ Fluent Bit is a vendor-agnostic Telemetry agent with full support for
+ OpenTelemetry Protocol (OTLP) and overall processing capabilities.
+date: 2024-11-12
+headerTheme: light
+#herobg: "/images/hero@2x.jpg"
+herobg: "/images/hero@2x.jpg"
+---
+
+## OpenTelemetry
+
+
+
+OpenTelemetry provides an open-source, vendor-neutral standard for Logs, Metrics, and Traces. It defines an open source schema for these telemetry data types, collectively known as signals, ensuring consistency and compatibility across diverse implementations. Because of its vendor-neutral approach, OpenTelemetry has been widely adopted and supported by numerous platforms and tools in the observability ecosystem. __Fluent Bit__ is one such implementation, offering a __lightweight__ and efficient solution for __processing__ and forwarding telemetry data in line with OpenTelemetry standards.
+
+Each telemetry type in OpenTelemetry has a specific schema that defines the structure and format of the data. This schema ensures that telemetry data is consistent and interoperable across different systems, enabling seamless integration:
+
+
+
+While schemas ensure consistency and interoperability of telemetry data, the OTLP (OpenTelemetry Protocol) handles the transport.
+
+#### OTLP - Transport Protocol
+
+A key component of OpenTelemetry is __OTLP__ (OpenTelemetry Protocol), a gRPC-based transport protocol designed for the structured transmission and reception of telemetry data like logs, metrics, and traces. OTLP ensures data consistency and interoperability across different systems:
+
+
+
+
+
+#### Instrumentation Libraries
+
+OpenTelemetry offers instrumentation libraries for a wide range of programming languages and frameworks. These libraries make it easy for developers to instrument their applications, collecting telemetry data in the OpenTelemetry format and seamlessly sending it to the desired backend using the OTLP protocol:
+
+
+
+While instrumentation libraries are essential for collecting telemetry data within applications, a telemetry agent is needed to process and forward this data to the desired backend: Fluent Bit.
+
+## Fluent Bit
+
+In the OpenTelemetry ecosystem Fluent Bit is a high-performance, vendor-agnostic telemetry agent that fully supports the OpenTelemetry Protocol (OTLP). As an alternative to the OpenTelemetry Collector, Fluent Bit offers robust processing capabilities, efficient resource utilization, and seamless integration with various backends.
+
+
+
+
+
+### Why Choose Fluent Bit for OpenTelemetry Collector ?
+
+
+
+- **High Performance**: Designed for high throughput and low resource usage, Fluent Bit can handle large volumes of data with minimal overhead.
+
+- **Extensive Plugin Ecosystem**: With a rich set of input, processors and output plugins, Fluent Bit can easily integrate with diverse data sources and destinations.
+
+- **Flexible and Scalable**: Fluent Bit is lightweight and can be deployed in various environments, from edge devices to cloud infrastructures.
+
+
+
+### Getting Started with Fluent Bit and OpenTelemetry
+
+To get started with Fluent Bit and OpenTelemetry, follow these steps:
+
+1. **Install Fluent Bit**: Follow the [installation guide](https://docs.fluentbit.io/manual/installation) for your platform.
+
+2. **Configure OpenTelemetry**: Set up Fluent Bit to use the OpenTelemetry Protocol by configuring the appropriate [input (source)](https://docs.fluentbit.io/manual/pipeline/inputs/opentelemetry) and [output (destination)](https://docs.fluentbit.io/manual/pipeline/outputs/opentelemetry) plugins.
+
+3. **Run Fluent Bit**: Start Fluent Bit and verify that it's collecting and forwarding telemetry data as expected.
+
+For detailed configuration instructions, visit the [Fluent Bit documentation](https://docs.fluentbit.io/manual/pipeline/outputs/opentelemetry).
+
+### Community and Support
+
+Join our community to stay updated, share your experiences, and get support from other Fluent Bit users:
+
+- **[Slack](https://launchpass.com/fluent-all)**: Engage with experts and other community members.
+- **[Twitter](https://twitter.com/fluentbit)**: Follow us for the latest news and announcements.
+- **[Newsletter](https://www.fluentd.org/newsletter)**: Sign up for updates on product information, events, and contributions.
+
+---
+
diff --git a/content/posts/_index.md b/content/posts/_index.md
index 61f4ad4..da1046c 100644
--- a/content/posts/_index.md
+++ b/content/posts/_index.md
@@ -1,7 +1,7 @@
---
title: 'News & insights'
description: 'Explore the latest news from Fluent Bit. Research analysis, and perspectives for our latest projects'
-date: 2021-02-10
+# date: 2021-02-10
url: 'blog'
herobg: "/images/hero@2x.jpg"
diff --git a/content/posts/avoiding-data-loss-and-backpressure-problems-with-fluent-bit.md b/content/posts/avoiding-data-loss-and-backpressure-problems-with-fluent-bit.md
new file mode 100644
index 0000000..af81583
--- /dev/null
+++ b/content/posts/avoiding-data-loss-and-backpressure-problems-with-fluent-bit.md
@@ -0,0 +1,311 @@
+---
+title: "A practical guide for avoiding data loss and backpressure problems with
+Fluent Bit"
+date: "2024-01-29"
+description: "A practical guide on how to detect and avoid backpressure problems
+with Fluent Bit by balancing memory-based and filesystem-based buffering."
+image: "/images/blog/1701353456-general-fluent-bit-preview-card.png"
+author: "Sharad Regoti"
+canonicalUrl: "https://chronosphere.io/learn/avoiding-data-loss-and-backpressure-problems-with-fluent-bit/"
+herobg: "/images/blog/1689182792-background-fluent-bit.png"
+---
+*This post is [republished from the Chronosphere blog](https://chronosphere.io/learn/avoiding-data-loss-and-backpressure-problems-with-fluent-bit/). With [Chronosphere’s acquisition of Calyptia](https://chronosphere.io/news/chronosphere-acquires-calyptia/) in 2024, Chronosphere became the [primary corporate sponsor of Fluent Bit](https://chronosphere.io/fluent-bit/). Eduardo Silva — the original creator of Fluent Bit and co-founder of Calyptia — leads a team of Chronosphere engineers dedicated full-time to the project, ensuring its continuous development and improvement.*
+
+## Introduction
+
+Fluent Bit is a widely used open-source data collection agent, processor, and forwarder
+that enables you to collect logs, metrics, and traces from various sources, filter and
+transform them, and then forward them to multiple destinations. With over
+[ten billion Docker](https://chronosphere.io/learn/fluent-bit-surpasses-10-billion-docker-pulls/)
+pulls, Fluent Bit has established itself as a preferred choice for log processing,
+collecting, and shipping.
+
+At its core, Fluent Bit is a simple data pipeline consisting of various stages,
+as depicted below.
+
+Most data pipelines eventually suffer from backpressure, which is when data is ingested at a higher rate than the ability to flush it. Backpressure causes problems such as high memory usage, service downtime, and data loss. Network failures, latency, or third-party service failures are common scenarios where backpressure occurs.
+
+Fluent Bit offers special strategies to deal with [backpressure](https://www.notion.so/manual/administration/backpressure) to help ensure data safety and reduce downtime. Recognizing when Fluent Bit is experiencing backpressure and knowing how to address it is crucial for maintaining a healthy data pipeline.
+
+This post provides a practical guide on how to detect and avoid backpressure
+problems with Fluent Bit.
+
+## Prerequisites
+
+* **Docker**: Installed on your local machine.
+* **Familiarity with Fluent Bit concepts:** Such as, inputs, outputs, parsers,
+and filters. If you’re not familiar with these concepts, please refer to the
+[official documentation](https://docs.fluentbit.io/manual/concepts/data-pipeline).
+
+## The default: memory-based buffering
+
+In Fluent Bit, [records](https://docs.fluentbit.io/manual/concepts/key-concepts#event-or-record)
+are emitted by an [input plugin](https://docs.fluentbit.io/manual/concepts/data-pipeline/input).
+These records are then grouped together by the engine into a unit called a **Chunk**,
+which typically has a size of around 2MB. Based on the configuration, the engine determines
+where to store these **Chunks**. By default, all **Chunks** are created in memory.
+
+With the default mechanism, Fluent Bit will store data in memory as much as
+possible. This is the fastest mechanism with the least system overhead, but in
+certain scenarios, data can be ingested at a higher rate than the ability to
+flush it to some destinations. This generates backpressure, leading to high
+memory consumption in the service.
+
+Network failures, latency, or unresponsive third-party services are common
+scenarios where we cannot deliver data fast enough as we receive new data to
+process, which leads to backpressure.
+
+In a high-load environment with backpressure, there's a risk of increased memory
+usage, which leads to the termination of the Fluent Bit process by the Kernel.
+
+Let’s see a demo where Fluent Bit is running in a constrained environment, which
+causes backpressure, leading to getting killed by **Kernel (OOM)**.
+
+### **Instructions**
+
+**Clone the Samples Git Repository:**
+
+This repository contains all the required configuration files. Use the command
+below to clone the repository.
+
+
+```bash
+git clone git@github.com:calyptia/blog-posts.git
+cd blog-posts
+```
+
+**Evaluating Default RAM Consumption:**
+
+```bash
+docker run -v $(pwd)/fluent-bit-empty.conf:/fluent-bit/etc/fluent-bit.conf:ro -ti cr.fluentbit.io/fluent/fluent-bit:2.2
+```
+The above command runs Fluent Bit in a docker container with an empty
+configuration file; this lets us evaluate what the default memory consumption
+and memory limits for the container.
+
+Use the `docker ps` command to get the name or container ID of the newly created
+container and use that value in the below command to get its stats.
+
+
+```bash
+docker stats
+```
+
+The image below shows that by default, the container consumes 10MB of RAM and
+can take up to 8GB of system RAM.
+
+**Fluent Bit Configuration**
+
+
+```yaml
+[INPUT]
+ Name dummy
+ copies 1500
+ dummy {"host":"31.163.219.152"...} # A large JSON object, refer git repository
+ tag dummy-a
+
+[OUTPUT]
+ name stdout
+ match *
+```
+
+The above configuration uses the [dummy](https://docs.fluentbit.io/manual/pipeline/inputs/dummy)
+input plugin to generate large amounts of data for test purposes. We have configured it
+to generate 1500 records per second. This data is then printed to the console using the
+[stdout](https://docs.fluentbit.io/manual/pipeline/outputs/standard-output) output plugin.
+
+**Simulating Backpressure**
+
+To simulate OOM kill behavior caused due to backpressure, we will generate data
+at a higher rate while restricting the container RAM to just 20MB. With this
+configuration as Fluent Bit tries to buffer more data in memory it will
+eventually hit the imposed RAM limit of the container and the service will
+crash.
+
+Execute the below command and observe the result.
+
+
+```bash
+docker run --memory 20MB -v $(pwd)/fluent-bit-oom.conf:/fluent-bit/etc/fluent-bit.conf:ro -ti cr.fluentbit.io/fluent/fluent-bit:2.2
+```
+
+After a few seconds, the container will stop automatically. Once it stops, grab
+the container ID using `docker ps -a` and inspect the container—you should
+observe that it was killed due to a container `Out Of Memory` error.
+
+
+This demonstrates how backpressure in Fluent Bit leads to increased memory usage, resulting in the Kernel terminating the application upon reaching memory limits, which causes downtime and data loss.
+
+If your Fluent Bit process is continuously getting killed, it is likely an
+indication that Fluent Bit is experiencing backpressure. In the following
+section, we'll explore a solution to this problem.
+
+## A quick fix: limiting memory-based buffering
+
+A workaround for backpressure scenarios like the above is to limit the amount of
+memory in records that an input plugin can register. This can be configured
+using the `mem_buf_limit` property. If a plugin has enqueued more than the
+`mem_buf_limit`, it won't be able to ingest more until that buffered data is
+delivered.
+
+When the set limit is reached, the specific input plugin gets paused, halting
+record ingestion until resumed, which inevitably leads to data loss.
+
+When an input plugin is paused, Fluent Bit logs the information on the console
+with an example shown below:
+
+
+```bash
+[input] tail.1 paused (mem buf overlimit)
+[input] tail.1 resume (mem buf overlimit)
+```
+
+The workaround of `mem_buf_limit` is good for certain scenarios and
+environments, it helps to control the memory usage of the service, but at the
+cost of data loss. This can happen with any input plugin.
+
+The goal of `mem_buf_limit` is memory control and survival of the service. Let’s
+see what happens when we modify our Fluent Bit configuration by adding the
+`mem_buf_limit` property to our input plugin.
+
+
+```yaml
+[INPUT]
+ Name dummy
+ copies 1500
+ dummy {"host":"31.163.219.152"...} # A large JSON object, refer git repository
+ tag dummy-a
+ Mem_Buf_Limit 10MB
+
+[OUTPUT]
+ name stdout
+ match *
+```
+
+We've set a 20MB memory limit for the container. With Fluent Bit using 10MB in
+its default configuration, we allocated an additional 10MB as mem\_buf\_limit.
+
+**Note:** The combined memory limit assigned to each input plugin, must be lower
+than the resource restriction placed on the container.
+
+Execute the below command and observe the result.
+
+
+```bash
+docker run --memory 20MB -v $(pwd)/fluent-bit-memory-limit.conf:/fluent-bit/etc/fluent-bit.conf:ro -ti cr.fluentbit.io/fluent/fluent-bit:2.2
+```
+
+Unlike the previous scenario, the container is not killed and continues to emit
+dummy records on the console. Grab the container ID using `docker ps` and
+execute the below command.
+
+
+```bash
+docker logs | grep -i "pausing\\|resume"
+```
+
+The above image indicates that as Fluent Bit reaches the 10MB buffer limit of the input plugin, **it pauses ingesting new records, potentially leading to data loss, but this pause prevents the service from getting terminated due to high memory usage**. Upon buffer clearance, the ingestion of new records resumes.
+
+If you are observing the above logs in Fluent Bit, it is a sign of Fluent Bit hitting the
+configured memory limits at input plugins due to backpressure. Check out this blog post
+on [how to configure alerts from logs using Fluent Bit](https://chronosphere.io/learn/fluent-bit-alerting-slack/).
+
+In the upcoming section, we will see how to achieve both data safety and memory
+safety.
+
+## A permanent fix: filesystem-based buffering
+
+[`Filesystem buffering`](https://docs.fluentbit.io/manual/administration/buffering-and-storage#filesystem-buffering-to-the-rescue) provides control over backpressure and can help guarantee data safety. Memory and filesystem buffering approaches are **not** mutually exclusive. When filesystem buffering is enabled for your input plugin, you are getting the best of both worlds: performance and data safety.
+
+When Filesystem buffering is enabled, the behavior of the engine is different. Upon
+Chunk creation, the engine stores the content in memory and also maps a copy on disk
+(through [`mmap(2)`](https://man7.org/linux/man-pages/man2/mmap.2.html)`).` The newly
+created Chunk is (1) active in memory, (2) backed up on disk.
+
+**How does the Filesystem buffering mechanism deal with high memory usage and
+backpressure?** Fluent Bit controls the number of Chunks that are `up` in
+memory. By default, the engine allows us to have 128 Chunks `up` in memory, this
+value is controlled by service property `storage.max_chunks_up`. The active
+Chunks that are up are ready for delivery.
+
+Any other remaining Chunk is in a `down` state, which means that it is only in
+the filesystem and won't be up in memory unless it is ready to be delivered.
+Remember, chunks are never much larger than 2 MB, thus the default
+`storage.max_chunks_up` value of 128, each input is limited to roughly 256 MB of
+memory.
+
+If the input plugin has enabled `storage.type` as `filesystem`, when reaching
+the `storage.max_chunks_up` threshold, instead of the plugin being paused, all
+new data will go to Chunks that are `down` in the filesystem. This allows us to
+control the memory usage of the service and also provides a guarantee that the
+service won't lose any data.
+
+Let’s modify our Fluent Bit configuration by enabling filesystem buffering.
+
+
+```yaml
+[SERVICE]
+ flush 1
+ log_Level info
+ storage.path /var/log/flb-storage/
+ storage.sync normal
+ storage.checksum off
+ storage.storage.max_chunks_up 5
+
+[INPUT]
+ Name dummy
+ copies 1500
+ dummy {"host":"31.163.219.152"...} # A large JSON object, refer git repository
+ tag dummy-a
+ storage.type filesystem
+
+[OUTPUT]
+ name stdout
+ match *
+```
+
+In the above configuration, we have added `storage.type` as `filesystem` in our
+input plugin and a `[SERVICE]` block to configure
+`storage.storage.max_chunks_up` to `5` (~10MB)
+
+Execute the below command and observe the result.
+
+
+```bash
+docker run --memory 20MB -v $(pwd)/fluent-bit-filesystem.conf:/fluent-bit/etc/fluent-bit.conf:ro -ti cr.fluentbit.io/fluent/fluent-bit:2.2
+```
+
+Unlike the default scenario, the container does not crash and continues to emit
+dummy records on the console. When the `storage.storage.max_chunks_up` limit is
+reached, the chunks are backed up in the filesystem and delivered once the
+memory is free.
+
+**Note:** While file system-based buffering helps prevent container crashes due
+to backpressure, it introduces new considerations related to filesystem limits.
+It's important to know that just as memory can be exhausted, so can filesystem
+storage. When opting for filesystem-based buffering, it is essential to
+incorporate a plan that addresses potential filesystem-related challenges.
+
+## Conclusion
+
+This guide has explored effective strategies to manage backpressure and prevent
+data loss in Fluent Bit. We've highlighted the limitations of default
+memory-based buffering and how `Mem_Buf_Limit` is a quick fix to balance memory
+usage. The ultimate solution, filesystem-based buffering, offers a comprehensive
+approach, ensuring data safety and efficient memory management. These techniques
+are essential for optimizing Fluent Bit in high-throughput environments,
+ensuring robust and reliable log processing.
+
+For more information on this topic, refer to the documentation below
+
+* [Administrating Backpressure In Fluent Bit](https://docs.fluentbit.io/manual/administration/backpressure)
+* [How to configure buffering & storage in Fluent Bit](https://docs.fluentbit.io/manual/administration/buffering-and-storage)
+
+## You may also be interested in
+
+To continue expanding your Fluent Bit knowledge, check out [Fluent Bit Academy](https://chronosphere.io/fluent-bit-academy/).
+It’s filled with on-demand videos guiding you through all things Fluent Bit — best
+practices and how-to’s on advanced processing rules, routing to multiple destinations,
+and much more.
+
+
\ No newline at end of file
diff --git a/content/posts/common-architecture-patterns-with-fluentd.md b/content/posts/common-architecture-patterns-with-fluentd.md
index 2fb4427..5fa0d8c 100644
--- a/content/posts/common-architecture-patterns-with-fluentd.md
+++ b/content/posts/common-architecture-patterns-with-fluentd.md
@@ -1,5 +1,5 @@
---
-title: '3 Common Architecture Patterns with Fluentd and Fluent Bit'
+title: 'Common Architecture Patterns with Fluentd and Fluent Bit'
date: "2020-12-03"
description: "Learn common ways to deploy Fluent Bit and Fluentd. Including forwarder-aggregator, side-car/agent, and network device aggregator pattern"
image: "/images/3 Common Architecture Patterns with Fluentd and Fluent Bit.jpg"
diff --git a/content/posts/convert-logs-to-metrics-in-legacy-applications-using-fluent-bit.md b/content/posts/convert-logs-to-metrics-in-legacy-applications-using-fluent-bit.md
new file mode 100644
index 0000000..3acc7ee
--- /dev/null
+++ b/content/posts/convert-logs-to-metrics-in-legacy-applications-using-fluent-bit.md
@@ -0,0 +1,404 @@
+---
+title: "Convert Logs To Metrics in Legacy Applications Using Fluent Bit"
+date: "2023-11-13"
+description: "Learn how Fluent Bit can derive metrics from application logs, helping to bridge the gap between limited telemetry sources and comprehensive observability."
+image: "/images/blog/1699633863-logs-to-metrics-social.png"
+author: "Sharad Regoti"
+canonicalUrl: "https://chronosphere.io/learn/convert-logs-to-metrics-using-fluent-bit/"
+herobg: "/images/blog/1689182792-background-fluent-bit.png"
+---
+*This post is [republished from the Chronosphere blog](https://chronosphere.io/learn/convert-logs-to-metrics-using-fluent-bit/). With [Chronosphere’s acquisition of Calyptia](https://chronosphere.io/news/chronosphere-acquires-calyptia/) in 2024, Chronosphere became the [primary corporate sponsor of Fluent Bit](https://chronosphere.io/fluent-bit/). Eduardo Silva — the original creator of Fluent Bit and co-founder of Calyptia — leads a team of Chronosphere engineers dedicated full-time to the project, ensuring its continuous development and improvement.*
+
+In software development, observability allows us to understand a system from the outside, by asking questions about the system without knowing its inner workings. Furthermore, it allows us to easily troubleshoot and helps answer the question, “Why is this happening?”
+
+To be able to ask those questions to a system, the application must be instrumented. That is, the application code must emit signals such as traces, metrics, and logs.
+
+Most modern applications are instrumented to output telemetry signals. However, at times you may find yourself working with systems that may not provide all the telemetry data you need. This is often the case when working with legacy applications, which may offer only a subset of the essential telemetry signals and whose codebase cannot be instrumented to provide more.
+
+In such challenging situations, innovative solutions become imperative. You may have to derive telemetry data from other means.
+
+This is where Fluent Bit comes into play. Fluent Bit is a widely used open-source data collection agent, processor, and forwarder that enables you to collect logs, metrics, and traces from various sources, filter and transform them, and then forward them to multiple destinations. It also addresses the aforementioned issues ingeniously.
+
+In this blog , we will demonstrate how Fluent Bit can derive metrics from application logs, helping to bridge the gap between limited telemetry sources and comprehensive system observability.
+
+## **Use Case: Getting Metrics from Legacy Applications**
+
+Consider a legacy application that logs HTTP requests and their corresponding status codes during processing. Here is an example log:
+
+
+```json
+{
+ "host": "31.163.219.152",
+ "user-identifier": "-",
+ "datetime": "31/Oct/2023:04:30:04 +0000",
+ "method": "GET",
+ "request": "/optimize/exploit/architect",
+ "protocol": "HTTP/2.0",
+ "status": 201,
+ "bytes": 21985,
+ "referer": ""
+}
+```
+
+The challenge is to identify the **HTTP Request Rate** and **Error Rate.** However, instrumenting the application to generate metrics is not feasible, as it was developed using an outdated programming language version, and the existing instrumentation libraries do not support this older version.
+
+However, the application log already contains status and request information. We can extract this data and convert it into metrics.
+
+## **Prerequisites**
+
+* **Kubernetes Cluster:** We will deploy Fluent Bit in a Kubernetes cluster. We will be using an EKS cluster, but any cluster will suffice.
+* **Kubectl and Helm CLI:** Installed on your local machine.
+* **Familiarity with Fluent Bit concepts:** Such as, inputs, outputs, parsers, and filters. If you’re not familiar with these concepts, please refer to the [official documentation](https://docs.fluentbit.io/manual/concepts/data-pipeline).
+
+## **Deploying a Sample Legacy Application**
+
+Let’s deploy our legacy application into Kubernetes. For demonstration purposes, we’ll use [a fake log generator](https://hub.docker.com/r/mingrammer/flog).
+
+### **Instructions:**
+
+1) Save the below deployment configuration in a file called `application.yaml`.
+
+
+
+```yaml
+
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+ labels:
+ app: legacy-application
+ name: legacy-application
+ namespace: default
+spec:
+ replicas: 1
+ selector:
+ matchLabels:
+ app: legacy-application
+ template:
+ metadata:
+ labels:
+ app: legacy-application
+ spec:
+ containers:
+ - image: mingrammer/flog:0.4.3
+ name: legacy-application
+ args: ["--loop", "--delay", "2", "--format", "json"]
+```
+
+2) Now, apply the configuration using the below command:
+
+
+```bash
+kubectl apply -f application.yaml
+```
+
+3) View the Application Logs
+
+
+```bash
+kubectl logs deploy/legacy-application
+```
+
+## **Converting Logs To Metrics**
+
+Metrics are stored in a [Time Series Database](https://en.wikipedia.org/wiki/Time_series_database) such as Prometheus, InfluxDB, VictoriaMetrics etc. These databases require metrics to be stored in particular data types such as counter, gauge and histogram. Converting raw logs into structured metrics involves a systematic approach, the below rules give a brief outline.
+
+### **Rules for Converting Logs to Metrics**
+
+1. **List the Required Metrics:**
+
+As discussed above, We want two metrics HTTP request rate and HTTP error rate.
+2. **Identify Corresponding Log Values:**
+
+From application logs, the request field contains the endpoint path for HTTP requests which can be mapped to the HTTP request rate metric while the status field indicates the HTTP status code. It ranges from 200 to 599. We are particularly interested in monitoring status codes greater than 500, indicating server errors that can be mapped to the HTTP error rate.
+3. **Determine the Metric Type:**
+* **HTTP Request Rate (e.g., Requests Per Second):**
+
+
+ + **Appropriate Metric Type:** Counter
+ + **Explanation:** Counters are ideal for measuring rates, such as the total number of HTTP requests served. To calculate the request rate, take the derivative of the counter value over time. This yields metrics like requests per second (RPS) or requests per minute (RPM), based on our preference.
+* **Error Rate (Based on HTTP Status Codes):**
+
+
+ + **Appropriate Metric Type:** Counter or Gauge
+ + **Explanation:** For error rates derived from HTTP status codes, counters are commonly used. You can create counters like `http_errors_total{status="4xx"}` to tally 4xx client errors or `http_errors_total{status="5xx"}` for 5xx server errors. Counters are suitable because they steadily increase, providing a cumulative count of errors over time.
+
+With the prerequisites for metrics now elucidated, let’s implement it in practice.
+
+Converting Logs to Metrics with Fluent BitHere’s the Fluent Bit configuration that enables the log processing pipeline depicted above:
+
+
+```yaml
+config:
+ customParsers: |
+ [PARSER]
+ Name crijsonparser
+ Format regex
+ Regex ^(?