Skip to content

[Known Issue][Obs & Sec] Upgrading to 9.3.x fails when a rule action contains oversized content#6554

Merged
nastasha-solomon merged 11 commits into
mainfrom
issue-1196-obs-sec
May 20, 2026
Merged

[Known Issue][Obs & Sec] Upgrading to 9.3.x fails when a rule action contains oversized content#6554
nastasha-solomon merged 11 commits into
mainfrom
issue-1196-obs-sec

Conversation

@nastasha-solomon
Copy link
Copy Markdown
Member

@nastasha-solomon nastasha-solomon commented May 18, 2026

Summary

Contributes to https://github.com/elastic/docs-content-internal/issues/1196 by adding known issue about upgrade failures when users upgrade to 9.3.x with a rule action containing values exceeding 32766 bytes. This PR updates both Observability and Security release notes. The Kibana release notes are being updated via elastic/kibana#269818.

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes - Cursor in auto mode
  • No

@nastasha-solomon nastasha-solomon self-assigned this May 18, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 18, 2026

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 18, 2026

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 18, 2026

Vale Linting Results

Summary: 2 suggestions found

💡 Suggestions (2)
File Line Rule Message
release-notes/elastic-observability/known-issues.md 34 Elastic.WordChoice Consider using 'stop, cancel, end' instead of 'abort', unless the term is in the UI.
release-notes/elastic-security/known-issues.md 32 Elastic.WordChoice Consider using 'stop, cancel, end' instead of 'abort', unless the term is in the UI.

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.

Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

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

Docs review summary

Focus areas

  • Style and clarity: Content is clear, technically precise, and well-structured. The workaround steps are actionable.
  • Jargon: No unexplained jargon. {{stack}}, {{kib}}, and {{es}} substitution variables are used appropriately.
  • Frontmatter and applies_to: No frontmatter changes. Both files lack a description field, but that's pre-existing and out of scope for this PR.
  • Content type fit: Both entries follow the known-issue dropdown convention for their respective files.
  • Parent issue satisfaction: Partially satisfied — the PR adds known issue entries for both Observability and Security as requested in docs-content-internal#1196. Confirms the issue is present in 9.3.0–9.3.4.

Nits

  • Cross-file inconsistency in section labels: The Observability entry uses **Details** while the Security entry uses **Impact** for the equivalent section — despite documenting the same issue. Both follow their file's existing convention, but a reader comparing the two pages sees different labels. Consider aligning both to **Impact** (which matches the template comment in both files).
  • Security file, line 38: **Workaround**<br> is immediately followed by content with no blank line, unlike the existing Security entry at line 58 which has a blank line after the heading. Minor spacing inconsistency.

Notes

  • Vale returned no findings. The PR is still in draft state.

Generated by Docs review agent for issue #6554 · ● 303.6K

Comment thread release-notes/elastic-observability/known-issues.md
nastasha-solomon and others added 3 commits May 18, 2026 16:54
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Comment thread release-notes/elastic-observability/known-issues.md Outdated
Comment thread release-notes/elastic-security/known-issues.md Outdated
@nastasha-solomon nastasha-solomon marked this pull request as ready for review May 20, 2026 19:29
@nastasha-solomon nastasha-solomon requested a review from a team as a code owner May 20, 2026 19:29
Comment thread release-notes/elastic-observability/known-issues.md Outdated
Copy link
Copy Markdown
Contributor

@benironside benironside left a comment

Choose a reason for hiding this comment

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

Approving with a bugfix and a suggestion!

Comment thread release-notes/elastic-observability/known-issues.md Outdated
Comment thread release-notes/elastic-observability/known-issues.md Outdated
Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
Comment thread release-notes/elastic-security/known-issues.md Outdated
@nastasha-solomon nastasha-solomon enabled auto-merge (squash) May 20, 2026 20:03
@nastasha-solomon nastasha-solomon merged commit e9192b2 into main May 20, 2026
7 checks passed
@nastasha-solomon nastasha-solomon deleted the issue-1196-obs-sec branch May 20, 2026 20:04
nastasha-solomon added a commit to elastic/kibana that referenced this pull request May 20, 2026
…ion contains oversized content (#269818)

## Summary

Contributes to
elastic/docs-content-internal#1196 by adding
known issue about upgrade failures when users upgrade to 9.3.x with a
rule action containing values exceeding 32766 bytes. This PR updates
Kibana release notes. The Observability and Security release notes are
being updated via elastic/docs-content#6554.
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.

3 participants