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
Performance regression in AWS S3 inputs using SQS notification.
15
+
16
+
In 8.12 the default memory queue flush interval was raised from 1 second to 10 seconds. In many configurations this improves performance because it allows the output to batch more events per round trip, which improves efficiency. However, the SQS input has an extra bottleneck that interacts badly with the new value. For more details see {issue}37754[37754].
17
+
18
+
If you are using the Elasticsearch output, and your output configuration uses a performance preset, switch it to `preset: latency`. If you use no preset or use `preset: custom`, then set `queue.mem.flush.timeout: 1s` in your queue or output configuration.
19
+
20
+
==== Breaking changes
21
+
22
+
*Affecting all Beats*
23
+
24
+
- add_cloud_metadata processor: `huawei` provider is now treated as `openstack`. Huawei cloud runs on OpenStack
25
+
platform, and when viewed from a metadata API standpoint, it is impossible to differentiate it from OpenStack. If you
26
+
know that your deployments run on Huawei Cloud exclusively, and you wish to have `cloud.provider` value as `huawei`,
27
+
you can achieve this by overwriting the value using an `add_fields` processor. {pull}35184[35184]
28
+
29
+
==== Bugfixes
30
+
31
+
*Affecting all Beats*
32
+
33
+
- aws: Add credential caching for `AssumeRole` session tokens. {issue}37787[37787]
34
+
- Lower logging level to debug when attempting to configure beats with unknown fields from autodiscovered events/environments. {pull}[37816][37816]
35
+
36
+
*Filebeat*
37
+
38
+
- Fix nil pointer dereference in the httpjson input. {pull}37591[37591]
0 commit comments