You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/docs/whats-new/_index.md
+106Lines changed: 106 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,112 @@ title: What's new
3
3
weight: 50
4
4
---
5
5
6
+
## Version 4.9
7
+
8
+
The following are the highlights and main changes of Logging operator 4.9. For a complete list of changes and bugfixes, see the [Logging operator 4.9 releases page](https://github.com/kube-logging/logging-operator/releases/tag/4.9.0)<!-- and the [Logging operator 4.9 release blog post](https://axoflow.com/logging-operator-4.9-release)-->.
9
+
10
+
### OpenTelemetry output
11
+
12
+
When using the [syslog-ng aggretor]({{< relref "/docs/configuration/output/_index.md#syslogngoutput" >}}), you can now send data directly to an OpenTelemetry endpoint. All metadata and the original log record are available. Resource attributes will be available in a future release, when we switch to an OpenTelemetry input and receive standard OTLP logs. For details, see {{% xref "/docs/configuration/plugins/syslog-ng-outputs/opentelemetry.md" %}}.
You can now send messages and metrics to [Elasticsearch data streams](https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams.html) to store your log and metrics data as time series data. You have to use the [syslog-ng aggretor]({{< relref "/docs/configuration/output/_index.md#syslogngoutput" >}}) to use this output. For details, see {{% xref "/docs/configuration/plugins/syslog-ng-outputs/elasticsearch_datastream.md" %}}.
36
+
37
+
### Improved Kafka performance
38
+
39
+
The {{% xref "/docs/configuration/plugins/outputs/kafka.md" %}} Fluentd output now supports using the rdkafka2 client, which offers higher performance than ruby-kafka. Set `use_rdkafka` to `true` to use the rdkafka2 client. (If you're using a custom Fluentd image, note that rdkafka2 requires v1.16-4.9-full or higher.)
40
+
41
+
### Containerd compatibility
42
+
43
+
As many users prefer Containerd instead of Docker as their container runtime, the slight differences between these CRIs are causing some problems. Now you can enable a compatibility layer with the `enableDockerParserCompatibilityForCRI` option of the `logging` CRD, for example:
44
+
45
+
```yaml
46
+
apiVersion: logging.banzaicloud.io/v1beta1
47
+
kind: Logging
48
+
metadata:
49
+
name: containerd
50
+
spec:
51
+
enableDockerParserCompatibilityForCRI: true
52
+
```
53
+
54
+
This option enables a log parser that is compatible with the docker parser. This has the following benefits:
55
+
56
+
- automatically parses JSON logs using the Merge_Log feature
57
+
- downstream parsers can use the `log` field instead of the `message` field, just like with the docker runtime
58
+
- the `concat` and `parser` filters are automatically set back to use the `log` field.
59
+
60
+
Here is a sample log message with the option enabled:
You can now configure `PrometheusRulesOverride` in your [`logging` CRDs]({{< relref "/docs/configuration/crds/v1beta1/common_types.md#PrometheusRulesOverride" >}}). The content of `PrometheusRulesOverride` is identical to the v1.Rule Prometheus rule type. The controller will match overrides by their names with the original rules. All of the override attributes are optional and whenever an attribute is set, it will replace the original attribute.
91
+
92
+
For example, you can change the severity of a rule like this:
93
+
94
+
```yaml
95
+
fluentd:
96
+
metrics:
97
+
prometheusRules: true
98
+
prometheusRulesOverride:
99
+
- alert: FluentdPredictedBufferGrowth
100
+
labels:
101
+
rulegroup: fluentd
102
+
service: fluentd
103
+
severity: none
104
+
```
105
+
106
+
### Other changes
107
+
108
+
- [Fluent Bit hot reload](#fluent-bit-hot-reload) now reloads imagePullSecrets as well.
109
+
- From now on, the entire `spec.Security.SecurityContext` is passed to Fluent Bit.
110
+
- Kubernetes namespace labels are added to the metadata by default. (The default of the `namespace_labels` option in the FluentBitAgent CRD is `on`.)
111
+
6
112
## Version 4.8
7
113
8
114
The following are the highlights and main changes of Logging operator 4.8. For a complete list of changes and bugfixes, see the [Logging operator 4.8 releases page](https://github.com/kube-logging/logging-operator/releases/tag/4.8.0) and the [Logging operator 4.8 release blog post](https://axoflow.com/logging-operator-4.8-release).
0 commit comments