Skip to content

Adds serverless log entries for March 2, 2026#5339

Open
jmikell821 wants to merge 1 commit intomainfrom
serverless-changelog-030226
Open

Adds serverless log entries for March 2, 2026#5339
jmikell821 wants to merge 1 commit intomainfrom
serverless-changelog-030226

Conversation

@jmikell821
Copy link
Contributor

Summary

Adds serverless log entries for March 2, 2026.

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • [ x] Yes
  • No

Tool(s) and model(s) used:
Claude 4.5 opus-high

@github-actions
Copy link
Contributor

github-actions bot commented Mar 3, 2026

Vale Linting Results

Summary: 1 warning found

⚠️ Warnings (1)
File Line Rule Message
release-notes/elastic-cloud-serverless/index.md 46 Elastic.Spelling 'subfeature' is a possible misspelling.

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 3, 2026

Copy link
Contributor

@yetanothertw yetanothertw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you! 🪴

Left 2 tiny suggestions for your consideration.


**Impact:**

API requests that include `serializer` or `deserializer` parameters (in the Create List API request body or Import List Items API query string) will have those parameters silently ignored, and a warning header is returned in the response. Users who relied on custom parsing logic will need to pre-process their list data before import, as only default parsing behavior is now supported.
Copy link
Contributor

@yetanothertw yetanothertw Mar 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just to maintain parallelism between the two fragments:

Suggested change
API requests that include `serializer` or `deserializer` parameters (in the Create List API request body or Import List Items API query string) will have those parameters silently ignored, and a warning header is returned in the response. Users who relied on custom parsing logic will need to pre-process their list data before import, as only default parsing behavior is now supported.
API requests that include `serializer` or `deserializer` parameters (in the Create List API request body or Import List Items API query string) will have those parameters silently ignored, and a warning header will be returned in the response. Users who relied on custom parsing logic will need to pre-process their list data before import, as only default parsing behavior is now supported.

* Fixes the **Attributes** tab rendering issue in the trace flyout that caused UI glitches [#255173]({{kib-pull}}255173)
* Fixes OOM crashes and {{kib}} restarts caused by the gap auto-fill scheduler creating excessively large saved objects [#254788]({{kib-pull}}254788)
* Fixes a race condition in the Streams data quality controller that caused incorrect Discover navigation [#254139]({{kib-pull}}254139)
* Fixes the processor name overlapping the badge in Streams [#251874]({{kib-pull}}251874)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Fixes the processor name overlapping the badge in Streams [#251874]({{kib-pull}}251874)
* Fixes the processor name overlapping the badge in streams [#251874]({{kib-pull}}251874)

Don't think you need to capitalise streams, unless you're referring to the main Streams page the UI. (Or in this case seems more like the Processing tab of a particular stream.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants