diff --git a/.gitbook.yaml b/.gitbook.yaml index 92c8c8afa..eda7f6a69 100644 --- a/.gitbook.yaml +++ b/.gitbook.yaml @@ -1,6 +1,7 @@ redirects: # Installation installation/upgrade_notes: ./installation/upgrade-notes.md + installation/whats-new-in-fluent-bit-v5.0: ./installation/whats-new-in-fluent-bit-v5.md installation/supported_platforms: ./installation/downloads.md installation/docker: ./installation/downloads/docker.md installation/windows: ./installation/downloads/windows.md diff --git a/.markdownlint.json b/.markdownlint.json index d327637d8..c26ffc758 100644 --- a/.markdownlint.json +++ b/.markdownlint.json @@ -3,6 +3,7 @@ "MD003": { "style": "atx" }, "MD007": { "indent": 2 }, "MD013": false, + "MD024": { "siblings_only": true }, "MD025": { "front_matter_title": "false" }, "MD047": false, "MD049": { "style": "underscore" }, diff --git a/README.md b/README.md index e4bf816c1..072d26c0a 100644 --- a/README.md +++ b/README.md @@ -37,7 +37,7 @@ description: High Performance Telemetry Agent for Logs, Metrics and Traces For more details about changes in each release, refer to the [official release notes](https://fluentbit.io/announcements/). -If you are upgrading from the Fluent Bit `4.2` series, start with [What's new in Fluent Bit v5.0](installation/whats-new-in-fluent-bit-v5.0.md) and [Upgrade notes](installation/upgrade-notes.md). +If you are upgrading from the Fluent Bit `4.2` series, start with [What's new in Fluent Bit v5](installation/whats-new-in-fluent-bit-v5.md) and [Upgrade notes](installation/upgrade-notes.md). ## Fluent Bit, Fluentd, and CNCF diff --git a/SUMMARY.md b/SUMMARY.md index 64eef78bb..c86f24ca7 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -33,7 +33,7 @@ * [Kubernetes](installation/downloads/kubernetes.md) * [macOS](installation/downloads/macos.md) * [Windows](installation/downloads/windows.md) -* [What's new in Fluent Bit v5.0](installation/whats-new-in-fluent-bit-v5.0.md) +* [What's new in Fluent Bit v5](installation/whats-new-in-fluent-bit-v5.md) * [Upgrade notes](installation/upgrade-notes.md) ## Administration diff --git a/installation/upgrade-notes.md b/installation/upgrade-notes.md index 15c97d561..6e761b080 100644 --- a/installation/upgrade-notes.md +++ b/installation/upgrade-notes.md @@ -8,6 +8,20 @@ Release notes will be prepared in advance of a Git tag for a release. An officia The tag drives the binary release process. Release binaries (containers and packages) will appear after a tag and its associated release note. This lets users to expect the new release binary to appear and allow/deny/update it as appropriate in their infrastructure. +## Fluent Bit v5.1 + +### Debian and Ubuntu package upgrades restart the service + +Upgrading the `fluent-bit` package on Debian or Ubuntu now runs `systemctl daemon-reload` and restarts the service as part of the upgrade, but only when the service is already running on a host that uses `systemd`. A stopped service stays stopped, and installing the package for the first time doesn't start it. If an unplanned restart isn't safe, stop the service before upgrading and start it again afterward. See [Debian](downloads/linux/debian.md#upgrade-fluent-bit) and [Ubuntu](downloads/linux/ubuntu.md#upgrade-fluent-bit). + +### Syslog output `mode` accepts `tls` and `dtls` + +The [Syslog output](../pipeline/outputs/syslog.md) `mode` setting now accepts `tls` and `dtls`, both of which automatically enable TLS, in addition to the existing `tcp` and `udp` values. Existing configurations that pair `mode: tcp` with a separate `tls: on` setting are unaffected. + +### 64-bit timestamp handling beyond 2038 + +Event timestamps at or after the 2038 32-bit `time_t` rollover now round-trip correctly through the internal msgpack `EventTime` encoding that Fluent Bit uses. On platforms where `time_t` is still 32-bit, timestamps remain bound by that platform's range. + ## Fluent Bit v5.0 ### `hot_reloaded_times` metric type change @@ -75,6 +89,7 @@ If you send data from Fluent Bit to a Fluentd aggregator using the `forward` out {% tabs %} {% tab title="YAML" %} + ```yaml pipeline: outputs: @@ -84,8 +99,10 @@ pipeline: port: 24224 retain_metadata_in_forward_mode: false ``` + {% endtab %} {% tab title="Classic" %} + ```text [OUTPUT] Name forward @@ -94,12 +111,13 @@ pipeline: Port 24224 Retain_Metadata_In_Forward_Mode false ``` + {% endtab %} {% endtabs %} For more details, see [GitHub issue #11877](https://github.com/fluent/fluent-bit/issues/11877). -For a broader overview of user-visible additions in this release, see [What's new in Fluent Bit v5.0](whats-new-in-fluent-bit-v5.0.md). +For a broader overview of user-visible additions in this release, see [What's new in Fluent Bit v5](whats-new-in-fluent-bit-v5.md). ## Fluent Bit v4.2 @@ -108,7 +126,7 @@ For a broader overview of user-visible additions in this release, see [What's ne The HTTP endpoint paths exposed by the Vivo exporter output plugin have changed. All endpoints now follow an `/api/v1/` prefix: | Signal | Endpoint | -|---|---| +| --- | --- | | Logs | `/api/v1/logs` | | Metrics | `/api/v1/metrics` | | Traces | `/api/v1/traces` | diff --git a/installation/whats-new-in-fluent-bit-v5.0.md b/installation/whats-new-in-fluent-bit-v5.0.md deleted file mode 100644 index e05696167..000000000 --- a/installation/whats-new-in-fluent-bit-v5.0.md +++ /dev/null @@ -1,163 +0,0 @@ -# What's new in Fluent Bit v5.0 - -Fluent Bit `v5.0` adds new inputs and processors, expands authentication and TLS options, and standardizes configuration for HTTP-based plugins. It also delivers an important round of performance and scalability work, especially for pipelines that ingest logs, metrics, and traces through HTTP-based protocols. This page gives a quick user-focused overview of the main changes since Fluent Bit `v4.2`. - -For migration-impacting changes, see [Upgrade notes](upgrade-notes.md). - -## Performance and scalability - -### Unified processing and delivery model - -Fluent Bit `v5.0` continues the move toward a more unified runtime for logs, metrics, and traces. In practice, this means the same core engine improvements benefit more of the pipeline, instead of individual signal paths evolving separately. - -For end users, the result is a more consistent behavior across telemetry types and a better base for high-throughput pipelines that mix logs, metrics, and traces in the same deployment. - -### Refactored HTTP stack - -One of the most important `v5.0` changes is the refactoring of the HTTP listener stack used by several input plugins. Fluent Bit now uses a shared HTTP server implementation across the major HTTP-based receivers instead of maintaining separate code paths. - -This work improves: - -- concurrency through shared listener worker support -- consistency of request handling across HTTP-based inputs -- buffer enforcement and connection handling -- maintainability, which reduces drift between plugin implementations - -The biggest user-facing beneficiaries are: - -- [HTTP input](../pipeline/inputs/http.md) -- [Splunk input](../pipeline/inputs/splunk.md) -- [Elasticsearch input](../pipeline/inputs/elasticsearch.md) -- [OpenTelemetry input](../pipeline/inputs/opentelemetry.md) -- [Prometheus remote write input](../pipeline/inputs/prometheus-remote-write.md) - -If you run large HTTP or OTLP ingestion workloads, `v5.0` is not only a feature release. It is also a meaningful runtime improvement. - -## Configuration and operations - -### Shared HTTP listener settings - -HTTP-based inputs now use a shared listener configuration model. The preferred setting names are: - -- `http_server.http2` -- `http_server.buffer_chunk_size` -- `http_server.buffer_max_size` -- `http_server.max_connections` -- `http_server.workers` -- `http_server.ingress_queue_event_limit` -- `http_server.ingress_queue_byte_limit` - -Legacy aliases such as `http2`, `buffer_chunk_size`, and `buffer_max_size` still work, but new configurations should use the `http_server.*` names. - -Affected plugin families include: - -- [HTTP input](../pipeline/inputs/http.md) -- [Splunk input](../pipeline/inputs/splunk.md) -- [Elasticsearch input](../pipeline/inputs/elasticsearch.md) -- [OpenTelemetry input](../pipeline/inputs/opentelemetry.md) -- [Prometheus remote write input](../pipeline/inputs/prometheus-remote-write.md) - -### Mutual TLS for inputs - -Input plugins that support TLS can now require client certificate verification with `tls.verify_client_cert`. This makes it easier to run mutual TLS (`mTLS`) directly on Fluent Bit listeners. - -See [TLS](../administration/transport-security.md). - -### JSON health endpoint in API v2 - -The built-in HTTP server exposes `/api/v2/health`, which returns health status as JSON and uses the HTTP status code to indicate healthy (`200`) or unhealthy (`500`) state. - -See [Monitoring](../administration/monitoring.md). - -## Inputs - -### New `fluentbit_logs` input - -The [Fluent Bit logs input](../pipeline/inputs/fluentbit-logs.md) routes Fluent Bit internal logs back into the pipeline as structured records. This lets you forward agent diagnostics to any supported destination. - -### HTTP input remote address capture - -The [HTTP input](../pipeline/inputs/http.md) adds: - -- `add_remote_addr` -- `remote_addr_key` - -These settings let you attach the client address from `X-Forwarded-For` to each ingested record. - -### `OAuth 2.0` bearer token validation on HTTP-based inputs - -HTTP-based receivers can validate incoming bearer tokens with: - -- `oauth2.validate` -- `oauth2.issuer` -- `oauth2.jwks_url` -- `oauth2.allowed_audience` -- `oauth2.allowed_clients` -- `oauth2.jwks_refresh_interval` - -This is available on the relevant input plugins, including [HTTP](../pipeline/inputs/http.md) and [OpenTelemetry](../pipeline/inputs/opentelemetry.md). - -### OpenTelemetry input improvements - -The [OpenTelemetry input](../pipeline/inputs/opentelemetry.md) in `v5.0` expands user-visible behavior with: - -- shared HTTP listener worker support -- `OAuth 2.0` bearer token validation -- stable JSON metrics ingestion over `OTLP/HTTP` -- improved JSON trace validation and error reporting - -### Kubernetes events state database controls - -The [Kubernetes events input](../pipeline/inputs/kubernetes-events.md) documents additional SQLite controls: - -- `db.journal_mode` -- `db.locking` - -These settings help tune event cursor persistence and database access behavior. - -## Processors - -### New cumulative-to-delta processor - -The [cumulative to delta processor](../pipeline/processors/cumulative-to-delta.md) converts cumulative monotonic metrics to delta values, which is useful when scraping Prometheus-style metrics but exporting to backends that expect deltas. - -### New topological data analysis processor - -The [topological data analysis processor](../pipeline/processors/tda.md) adds a metrics processor for topology-based analysis workflows. - -### Sampling processor updates - -The [sampling processor](../pipeline/processors/sampling.md) adds `legacy_reconcile` for tail sampling, which helps compare the optimized reconciler with the previous behavior when validating upgrades. - -## Outputs - -### HTTP output `OAuth 2.0` client credentials - -The [HTTP output](../pipeline/outputs/http.md) now supports built-in `OAuth 2.0` client credentials with: - -- `basic` -- `post` -- `private_key_jwt` - -You can configure token acquisition directly in Fluent Bit with the `oauth2.*` settings. - -### More compression options for cloud outputs - -Several outputs gained additional compression support in the `v4.2` to `v5.0` range: - -- [Amazon Kinesis Data Streams](../pipeline/outputs/kinesis.md): `gzip`, `zstd`, `snappy` -- [Amazon Kinesis Data Firehose](../pipeline/outputs/firehose.md): `snappy` added alongside existing codecs -- [Amazon S3](../pipeline/outputs/s3.md): `snappy` added alongside existing codecs -- [Azure Blob](../pipeline/outputs/azure_blob.md): `zstd` support for transfer compression - -## Monitoring changes - -### `fluentbit_hot_reloaded_times` is now a counter - -The `fluentbit_hot_reloaded_times` metric changed from a gauge to a counter, which makes it safe to use with PromQL functions such as `rate()` and `increase()`. - -### New output backpressure visibility - -`v5.0` adds output backpressure duration metrics so you can observe time spent waiting because of downstream pressure. - -See [Monitoring](../administration/monitoring.md). diff --git a/installation/whats-new-in-fluent-bit-v5.md b/installation/whats-new-in-fluent-bit-v5.md new file mode 100644 index 000000000..ee0ffee24 --- /dev/null +++ b/installation/whats-new-in-fluent-bit-v5.md @@ -0,0 +1,255 @@ +# What's new in Fluent Bit v5 + +This page gives a quick user-focused overview of the main changes in the Fluent Bit `v5` line, grouped by minor release with the newest release first. + +For migration-impacting changes, see [Upgrade notes](upgrade-notes.md). + +## Fluent Bit v5.1 + +Fluent Bit `v5.1` focuses on network ingestion throughput, adds several new inputs and outputs, and hardens TLS and FIPS compliance options. + +### Performance and scalability + +#### Multi-worker network ingestion + +The [TCP](../pipeline/inputs/tcp.md), [UDP](../pipeline/inputs/udp.md), and [Forward](../pipeline/inputs/forward.md) inputs add a `workers` setting that lets a single listener accept and decode traffic across multiple worker threads. This mirrors the shared HTTP listener worker support introduced for HTTP-based inputs in `v5.0`. + +#### OpenTelemetry protobuf ingestion + +The [OpenTelemetry input](../pipeline/inputs/opentelemetry.md) reduces allocation overhead when decoding large batched Protobuf payloads, improving throughput for high-volume `OTLP/HTTP` workloads. There's no new configuration setting for this: it applies automatically to payloads over an internal size threshold. + +#### Input rate gate + +Every input plugin can now enable a rate gate to pause ingestion once it exceeds a configured byte or record rate, and resume once the rate falls back under a hysteresis threshold. See `rate_gate` and `rate_window` in [Buffering](../pipeline/buffering.md#per-input-settings). + +### Security + +#### FIPS mode + +Fluent Bit can start in FIPS mode with `--enable-fips`, which validates on startup that the linked OpenSSL library has an active FIPS provider. This blocks non-FIPS-approved hashes, such as MD5, in outputs like [Amazon S3](../pipeline/outputs/s3.md) and [Azure Blob](../pipeline/outputs/azure_blob.md). See [Configuring Fluent Bit](../administration/configuring-fluent-bit.md). + +#### Automatic TLS certificate reload + +TLS-enabled inputs and outputs now detect changes to their configured certificate and key files and reload them automatically, without a restart. See [Certificate reload](../administration/transport-security.md#certificate-reload). + +#### HTTPS proxy TLS settings + +Output plugins connecting through an HTTPS proxy can now configure the proxy leg's certificate verification independently from the destination's own TLS settings, using `tls.proxy.ca_file`, `tls.proxy.ca_path`, `tls.proxy.verify`, and `tls.proxy.verify_hostname`. See [HTTP proxy](../administration/http-proxy.md). + +#### DTLS transport for Syslog output + +The [Syslog output](../pipeline/outputs/syslog.md) `mode` setting now accepts `tls` and `dtls`, both of which automatically enable TLS, in addition to the existing `tcp` and `udp` values. Datagram Transport Layer Security (DTLS) over UDP is supported for the first time. + +### Inputs + +#### New event tracing for Windows (ETW) input + +The [Event Tracing for Windows input](../pipeline/inputs/event-tracing-windows.md) collects events from ETW providers or the Windows kernel logger on Windows hosts. + +#### NVIDIA GPU metrics through NVML + +The [GPU metrics input](../pipeline/inputs/gpu-metrics.md) adds NVIDIA GPU collection through NVML, including automatic discovery of Multi-Instance GPU (MIG) devices, alongside its existing AMD support. + +#### Node exporter metrics collector additions + +The [Node Exporter Metrics input](../pipeline/inputs/node-exporter-metrics.md) adds: + +- a `timex` collector for `adjtimex(2)` system call statistics on Linux, enabled by default +- macOS support for the `filesystem` collector +- `TcpExt` and `IpExt` counters in the `netstat` collector + +### Outputs + +#### New Google Cloud Storage output + +The [Google Cloud Storage output](../pipeline/outputs/gcs.md) uploads records to a GCS bucket with service-account `OAuth 2.0` authentication and optional gzip compression. + +#### Kafka output Confluent Schema Registry support + +The [Kafka output](../pipeline/outputs/kafka.md) can resolve Avro schemas directly from a Confluent Schema Registry with `schema_registry_url` and related settings, instead of requiring a schema to be configured inline. + +#### File output rotation and compression + +The [File output](../pipeline/outputs/file.md) adds size-based log rotation with `rotate`, `rotate_max_size`, and `rotate_max_files`, with optional gzip compression through `rotate_gzip`. + +#### Elasticsearch output alias + +The output name `elasticsearch` is now a built-in alias for the [Elasticsearch output](../pipeline/outputs/elasticsearch.md) plugin `es`, so either name works in configuration files. + +### Packaging + +#### Windows Server 2025 and Nano Server container images + +Windows container images add a Server Core variant for Windows Server 2025 and a new, smaller Nano Server variant. See [Docker](downloads/docker.md). + +#### Debian and Ubuntu package upgrades restart the service + +Upgrading the `fluent-bit` Debian or Ubuntu package now reloads `systemd` unit files and restarts an already-running service. See [Debian](downloads/linux/debian.md#upgrade-fluent-bit) and [Ubuntu](downloads/linux/ubuntu.md#upgrade-fluent-bit). + +### Data correctness + +#### 64-bit timestamp handling beyond 2038 + +Event timestamps at or after the 2038 32-bit `time_t` rollover now round-trip correctly through the internal msgpack `EventTime` encoding that Fluent Bit uses, instead of overflowing. + +## Fluent Bit v5.0 + +Fluent Bit `v5.0` adds new inputs and processors, expands authentication and TLS options, and standardizes configuration for HTTP-based plugins. It also delivers an important round of performance and scalability work, especially for pipelines that ingest logs, metrics, and traces through HTTP-based protocols. This section gives a quick user-focused overview of the main changes since Fluent Bit `v4.2`. + +### Performance and scalability + +#### Unified processing and delivery model + +Fluent Bit `v5.0` continues the move toward a more unified runtime for logs, metrics, and traces. In practice, this means the same core engine improvements benefit more of the pipeline, instead of individual signal paths evolving separately. + +For end users, the result is a more consistent behavior across telemetry types and a better base for high-throughput pipelines that mix logs, metrics, and traces in the same deployment. + +#### Refactored HTTP stack + +One of the most important `v5.0` changes is the refactoring of the HTTP listener stack used by several input plugins. Fluent Bit now uses a shared HTTP server implementation across the major HTTP-based receivers instead of maintaining separate code paths. + +This work improves: + +- concurrency through shared listener worker support +- consistency of request handling across HTTP-based inputs +- buffer enforcement and connection handling +- maintainability, which reduces drift between plugin implementations + +The biggest user-facing beneficiaries are: + +- [HTTP input](../pipeline/inputs/http.md) +- [Splunk input](../pipeline/inputs/splunk.md) +- [Elasticsearch input](../pipeline/inputs/elasticsearch.md) +- [OpenTelemetry input](../pipeline/inputs/opentelemetry.md) +- [Prometheus remote write input](../pipeline/inputs/prometheus-remote-write.md) + +If you run large HTTP or OTLP ingestion workloads, `v5.0` isn't only a feature release. It's also a meaningful runtime improvement. + +### Configuration and operations + +#### Shared HTTP listener settings + +HTTP-based inputs now use a shared listener configuration model. The preferred setting names are: + +- `http_server.http2` +- `http_server.buffer_chunk_size` +- `http_server.buffer_max_size` +- `http_server.max_connections` +- `http_server.workers` +- `http_server.ingress_queue_event_limit` +- `http_server.ingress_queue_byte_limit` + +Legacy aliases such as `http2`, `buffer_chunk_size`, and `buffer_max_size` still work, but new configurations should use the `http_server.*` names. + +Affected plugin families include: + +- [HTTP input](../pipeline/inputs/http.md) +- [Splunk input](../pipeline/inputs/splunk.md) +- [Elasticsearch input](../pipeline/inputs/elasticsearch.md) +- [OpenTelemetry input](../pipeline/inputs/opentelemetry.md) +- [Prometheus remote write input](../pipeline/inputs/prometheus-remote-write.md) + +#### Mutual TLS for inputs + +Input plugins that support TLS can now require client certificate verification with `tls.verify_client_cert`. This makes it easier to run mutual TLS (`mTLS`) directly on Fluent Bit listeners. + +See [TLS](../administration/transport-security.md). + +#### JSON health endpoint in API v2 + +The built-in HTTP server exposes `/api/v2/health`, which returns health status as JSON and uses the HTTP status code to indicate healthy (`200`) or unhealthy (`500`) state. + +See [Monitoring](../administration/monitoring.md). + +### Inputs + +#### New `fluentbit_logs` input + +The [Fluent Bit logs input](../pipeline/inputs/fluentbit-logs.md) routes Fluent Bit internal logs back into the pipeline as structured records. This lets you forward agent diagnostics to any supported destination. + +#### HTTP input remote address capture + +The [HTTP input](../pipeline/inputs/http.md) adds: + +- `add_remote_addr` +- `remote_addr_key` + +These settings let you attach the client address from `X-Forwarded-For` to each ingested record. + +#### `OAuth 2.0` bearer token validation on HTTP-based inputs + +HTTP-based receivers can validate incoming bearer tokens with: + +- `oauth2.validate` +- `oauth2.issuer` +- `oauth2.jwks_url` +- `oauth2.allowed_audience` +- `oauth2.allowed_clients` +- `oauth2.jwks_refresh_interval` + +This is available on the relevant input plugins, including [HTTP](../pipeline/inputs/http.md) and [OpenTelemetry](../pipeline/inputs/opentelemetry.md). + +#### OpenTelemetry input improvements + +The [OpenTelemetry input](../pipeline/inputs/opentelemetry.md) in `v5.0` expands user-visible behavior with: + +- shared HTTP listener worker support +- `OAuth 2.0` bearer token validation +- stable JSON metrics ingestion over `OTLP/HTTP` +- improved JSON trace validation and error reporting + +#### Kubernetes events state database controls + +The [Kubernetes events input](../pipeline/inputs/kubernetes-events.md) documents additional SQLite controls: + +- `db.journal_mode` +- `db.locking` + +These settings help tune event cursor persistence and database access behavior. + +### Processors + +#### New cumulative-to-delta processor + +The [cumulative to delta processor](../pipeline/processors/cumulative-to-delta.md) converts cumulative monotonic metrics to delta values, which helps when scraping Prometheus-style metrics but exporting to backends that expect deltas. + +#### New topological data analysis processor + +The [topological data analysis processor](../pipeline/processors/tda.md) adds a metrics processor for topological data analysis workflows. + +#### Sampling processor updates + +The [sampling processor](../pipeline/processors/sampling.md) adds `legacy_reconcile` for tail sampling, which helps compare the optimized reconciler with the previous behavior when validating upgrades. + +### Outputs + +#### HTTP output `OAuth 2.0` client credentials + +The [HTTP output](../pipeline/outputs/http.md) now supports built-in `OAuth 2.0` client credentials with: + +- `basic` +- `post` +- `private_key_jwt` + +You can configure token acquisition directly in Fluent Bit with the `oauth2.*` settings. + +#### More compression options for cloud outputs + +Several outputs gained additional compression support in the `v4.2` to `v5.0` range: + +- [Amazon Kinesis Data Streams](../pipeline/outputs/kinesis.md): `gzip`, `zstd`, `snappy` +- [Amazon Kinesis Data Firehose](../pipeline/outputs/firehose.md): `snappy` added alongside existing codecs +- [Amazon S3](../pipeline/outputs/s3.md): `snappy` added alongside existing codecs +- [Azure Blob](../pipeline/outputs/azure_blob.md): `zstd` support for transfer compression + +### Monitoring changes + +#### `fluentbit_hot_reloaded_times` is now a counter + +The `fluentbit_hot_reloaded_times` metric changed from a gauge to a counter, which makes it safe to use with PromQL functions such as `rate()` and `increase()`. + +#### New output backpressure visibility + +`v5.0` adds output backpressure duration metrics so you can observe time spent waiting because of downstream pressure. + +See [Monitoring](../administration/monitoring.md). diff --git a/vale-styles/FluentBit/Acronyms.yml b/vale-styles/FluentBit/Acronyms.yml index 066c76d17..d215f8c6e 100644 --- a/vale-styles/FluentBit/Acronyms.yml +++ b/vale-styles/FluentBit/Acronyms.yml @@ -41,6 +41,7 @@ exceptions: - DPI - DPPS - DST + - DTLS - ECR - ECS - EKS @@ -79,6 +80,7 @@ exceptions: - LLVM - LTS - LTSV + - MIG - MIME - MAC - MQTT @@ -91,6 +93,7 @@ exceptions: - NOTE - NSIS - NVDA + - NVML - OAP - OEM - OOM diff --git a/vale-styles/FluentBit/Headings.yml b/vale-styles/FluentBit/Headings.yml index df3393364..9b549c4b2 100644 --- a/vale-styles/FluentBit/Headings.yml +++ b/vale-styles/FluentBit/Headings.yml @@ -42,6 +42,7 @@ exceptions: - CNCF - Code - Collector + - Confluent Schema Registry - Cosmos - CPU - Crowdstrike @@ -113,6 +114,7 @@ exceptions: - MongoDB - MQTT - MSK + - Nano Server - NATS - New Relic - Observability Platform @@ -171,5 +173,6 @@ exceptions: - WebSocket - Windows - Windows Event + - Windows Server - YAML - YUM diff --git a/vale-styles/FluentBit/Spelling-exceptions.txt b/vale-styles/FluentBit/Spelling-exceptions.txt index 19a34ebee..82c7dd30b 100644 --- a/vale-styles/FluentBit/Spelling-exceptions.txt +++ b/vale-styles/FluentBit/Spelling-exceptions.txt @@ -32,6 +32,8 @@ CloudWatch CMake cmdlet cmetrics +codec +codecs collectd Config Coralogix @@ -67,6 +69,7 @@ downscale downscaling downscales dri +DTLS Dynatrace Elasticsearch endcode @@ -132,17 +135,21 @@ markdownlint matchers metacharacter Metricbeat +MIG Minishift minikube MTTx +msgpack multiline multithreading Musl namespace namespaces +Nano netcat Nginx NGINX +NVML OAuth Okta Onigmo