Skip to content

DOCS-1642 - Add Flex to Tier Migration Report#6728

Open
JV0812 wants to merge 9 commits into
mainfrom
flex-to-tier-migration-report
Open

DOCS-1642 - Add Flex to Tier Migration Report#6728
JV0812 wants to merge 9 commits into
mainfrom
flex-to-tier-migration-report

Conversation

@JV0812

@JV0812 JV0812 commented May 25, 2026

Copy link
Copy Markdown
Collaborator

Purpose of this pull request

Adds a new documentation page for the Flex to Tier Migration Report under the Partitions section. The page covers:

  • Column definitions for all fields in the report
  • Recommendation message logic as a decision table (based on Is Included, Unsupported Features Detected, and SIEM Forwarding values)
  • FAQ section with 5 Q&As addressing common questions about the report, default scope, SIEM forwarding, monitor/SLO impact, and scan cost reduction

New file: docs/manage/partitions/flex-to-tier-migration-report.md

Select the type of change

  • Minor Changes - Typos, formatting, slight revisions
  • Update Content - Revisions, updating sections
  • New Content - New features, sections, pages, tutorials
  • Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

https://sumologic.atlassian.net/browse/DOCS-1642

JV0812 and others added 2 commits May 25, 2026 13:43
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@JV0812 JV0812 self-assigned this May 25, 2026
@cla-bot cla-bot Bot added the cla-signed Contributor approved, listed in .clabot file label May 25, 2026
Comment thread docs/manage/partitions/flex-to-tier-migration-report.md Outdated
Comment thread docs/manage/partitions/flex-to-tier-migration-report.md Outdated

| Is Included | Unsupported Features Detected | SIEM Forwarding | Recommendation |
|:--|:--|:--|:--|
| `true` | `false` | Any | No action needed. |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

does this mean any value? or either true or false?

| `true` | `false` | Any | No action needed. |
| `false` | `false` | `false` | No action needed. |
| `false` | `false` | `true` | Switch to Included (Continuous). SIEM Forwarding will not work correctly on an excluded partition. |
| `false` | `true` | Any | Switch to Included (Continuous). Monitors/SLOs/Scheduled Views will not work correctly on an excluded partition. |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

does this mean any value? or either true or false?

Comment thread docs/manage/partitions/flex-to-tier-migration-report.md Outdated

## Column definitions

| Column | Description |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

The Column definitions table defines a column called Current Scope, but the Recommendation messages table uses Is Included as its column header. The FAQ then asks "What does the Is Included column mean?" and answers as if it's a column — but "Is Included" is never defined in the Column definitions section. These appear to be the same concept with two different names. One name should be chosen and used consistently throughout.

Comment thread docs/manage/partitions/flex-to-tier-migration-report.md Outdated
JV0812 and others added 4 commits June 4, 2026 09:38
Co-authored-by: Kim Pohas <56411016+kimsauce@users.noreply.github.com>
Co-authored-by: Kim Pohas <56411016+kimsauce@users.noreply.github.com>
Co-authored-by: Kim Pohas <56411016+kimsauce@users.noreply.github.com>
Co-authored-by: Kim Pohas <56411016+kimsauce@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed Contributor approved, listed in .clabot file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants