From 1e7d1cd27812a3421e42c9b234d56a9ad0beeceb Mon Sep 17 00:00:00 2001 From: Jagadisha V Date: Mon, 25 May 2026 13:43:29 +0530 Subject: [PATCH 1/7] DOCS - Add Flex to Tier Migration Report doc Co-Authored-By: Claude Sonnet 4.6 --- .../flex-to-tier-migration-report.md | 41 +++++++++++++++++++ sidebars.ts | 1 + 2 files changed, 42 insertions(+) create mode 100644 docs/manage/manage-subscription/flex-to-tier-migration-report.md diff --git a/docs/manage/manage-subscription/flex-to-tier-migration-report.md b/docs/manage/manage-subscription/flex-to-tier-migration-report.md new file mode 100644 index 0000000000..932caf12c2 --- /dev/null +++ b/docs/manage/manage-subscription/flex-to-tier-migration-report.md @@ -0,0 +1,41 @@ +--- +id: flex-to-tier-migration-report +title: Flex to Tier Migration Report +sidebar_label: Flex to Tier Migration Report +description: Learn how to use the Flex to Tier Migration Report to assess partition readiness, understand column definitions, and act on migration recommendations. +keywords: + - flex + - tier migration + - partition + - tiered storage + - migration report +--- + +import useBaseUrl from '@docusaurus/useBaseUrl'; + +The Flex to Tier Migration Report shows your partitions and their readiness for migration to Tiered storage. It includes current recommendation messages and the status of any unsupported features that may be affected by migration. + +## Column definitions + +| Column | Description | +|:--|:--| +| **Partition Name** | Name of the partition. | +| **Ingestion Volume** | Total ingestion volume associated with the partition. | +| **Current Scope** | Indicates whether the partition is currently included or excluded from the migration scope. | +| **SIEM Forwarding** | Indicates whether SIEM forwarding is enabled for the partition (`true` / `false`). | +| **Unsupported Features Detected When Moving Towards Tiered** | Displays whether any unsupported dependencies are detected for the partition after migration to Tiered storage. For example, `true [monitor, slo]`. | +| **Unsupported Monitor** | Lists monitor names currently using the partition that may not function after migration. | +| **Unsupported SLO** | Lists SLO names associated with the partition that may become unsupported after migration. | +| **Unsupported Scheduled Views** | Lists scheduled view names dependent on the partition that may not work after migration. | +| **Recommendation** | Provides the recommended action based on dependency analysis and migration readiness. | + +## Recommendation messages + +The **Recommendation** column displays one of the following messages based on the partition's scope, unsupported feature status, and SIEM forwarding configuration. + +| Is Included | Unsupported Features Detected | SIEM Forwarding | Recommendation | +|:--|:--|:--|:--| +| `true` | `false` | Any | No action needed — No feature conflicts detected. Excluding this partition can reduce scan cost. | +| `false` | `false` | `false` | No action needed — No feature conflicts detected. | +| `false` | `false` | `true` | Switch to Included — SIEM Forwarding will not work correctly on an excluded partition. | +| `false` | `true` | Any | Switch to Included — Monitors/SLOs/Scheduled Views will not work correctly on an excluded partition. | diff --git a/sidebars.ts b/sidebars.ts index 9b6d93d72e..282d46242d 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -1064,6 +1064,7 @@ module.exports = { 'manage/manage-subscription/manage-billing-information', 'manage/manage-subscription/organization-usage-limits', 'manage/manage-subscription/scan-budgets', + 'manage/manage-subscription/flex-to-tier-migration-report', 'manage/manage-subscription/fedramp-capabilities', 'manage/manage-subscription/close-cancel-sumo-account', ] From 0b6e1a4efe35e0306dadf1b0d9d485b02f82c37a Mon Sep 17 00:00:00 2001 From: Jagadisha V Date: Mon, 25 May 2026 13:56:51 +0530 Subject: [PATCH 2/7] DOCS-1642 - Move Flex to Tier Migration Report to partitions section Co-Authored-By: Claude Sonnet 4.6 --- .../flex-to-tier-migration-report.md | 41 ------------ .../flex-to-tier-migration-report.md | 63 +++++++++++++++++++ sidebars.ts | 2 +- 3 files changed, 64 insertions(+), 42 deletions(-) delete mode 100644 docs/manage/manage-subscription/flex-to-tier-migration-report.md create mode 100644 docs/manage/partitions/flex-to-tier-migration-report.md diff --git a/docs/manage/manage-subscription/flex-to-tier-migration-report.md b/docs/manage/manage-subscription/flex-to-tier-migration-report.md deleted file mode 100644 index 932caf12c2..0000000000 --- a/docs/manage/manage-subscription/flex-to-tier-migration-report.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -id: flex-to-tier-migration-report -title: Flex to Tier Migration Report -sidebar_label: Flex to Tier Migration Report -description: Learn how to use the Flex to Tier Migration Report to assess partition readiness, understand column definitions, and act on migration recommendations. -keywords: - - flex - - tier migration - - partition - - tiered storage - - migration report ---- - -import useBaseUrl from '@docusaurus/useBaseUrl'; - -The Flex to Tier Migration Report shows your partitions and their readiness for migration to Tiered storage. It includes current recommendation messages and the status of any unsupported features that may be affected by migration. - -## Column definitions - -| Column | Description | -|:--|:--| -| **Partition Name** | Name of the partition. | -| **Ingestion Volume** | Total ingestion volume associated with the partition. | -| **Current Scope** | Indicates whether the partition is currently included or excluded from the migration scope. | -| **SIEM Forwarding** | Indicates whether SIEM forwarding is enabled for the partition (`true` / `false`). | -| **Unsupported Features Detected When Moving Towards Tiered** | Displays whether any unsupported dependencies are detected for the partition after migration to Tiered storage. For example, `true [monitor, slo]`. | -| **Unsupported Monitor** | Lists monitor names currently using the partition that may not function after migration. | -| **Unsupported SLO** | Lists SLO names associated with the partition that may become unsupported after migration. | -| **Unsupported Scheduled Views** | Lists scheduled view names dependent on the partition that may not work after migration. | -| **Recommendation** | Provides the recommended action based on dependency analysis and migration readiness. | - -## Recommendation messages - -The **Recommendation** column displays one of the following messages based on the partition's scope, unsupported feature status, and SIEM forwarding configuration. - -| Is Included | Unsupported Features Detected | SIEM Forwarding | Recommendation | -|:--|:--|:--|:--| -| `true` | `false` | Any | No action needed — No feature conflicts detected. Excluding this partition can reduce scan cost. | -| `false` | `false` | `false` | No action needed — No feature conflicts detected. | -| `false` | `false` | `true` | Switch to Included — SIEM Forwarding will not work correctly on an excluded partition. | -| `false` | `true` | Any | Switch to Included — Monitors/SLOs/Scheduled Views will not work correctly on an excluded partition. | diff --git a/docs/manage/partitions/flex-to-tier-migration-report.md b/docs/manage/partitions/flex-to-tier-migration-report.md new file mode 100644 index 0000000000..bf686f83b7 --- /dev/null +++ b/docs/manage/partitions/flex-to-tier-migration-report.md @@ -0,0 +1,63 @@ +--- +id: flex-to-tier-migration-report +title: Flex to Tier Migration Report +sidebar_label: Flex to Tier Migration Report +description: Learn how to use the Flex to Tier Migration Report to assess partition readiness, understand column definitions, and act on migration recommendations. +keywords: + - flex + - tier migration + - partition + - tiered storage + - migration report +--- + +import useBaseUrl from '@docusaurus/useBaseUrl'; + +The Flex to Tier Migration Report shows your partitions and their readiness for migration to Tiered storage. It includes current recommendation messages and the status of any unsupported features that may be affected by migration. + +## Column definitions + +| Column | Description | +|:--|:--| +| **Partition Name** | Name of the partition. | +| **Ingestion Volume** | Total ingestion volume associated with the partition. | +| **Current Scope** | Indicates whether the partition is currently included or excluded from the migration scope. | +| **SIEM Forwarding** | Indicates whether SIEM forwarding is enabled for the partition (`true` / `false`). | +| **Unsupported Features Detected When Moving Towards Tiered** | Displays whether any unsupported dependencies are detected for the partition after migration to Tiered storage. For example, `true [monitor, slo]`. | +| **Unsupported Monitor** | Lists monitor names currently using the partition that may not function after migration. | +| **Unsupported SLO** | Lists SLO names associated with the partition that may become unsupported after migration. | +| **Unsupported Scheduled Views** | Lists scheduled view names dependent on the partition that may not work after migration. | +| **Recommendation** | Provides the recommended action based on dependency analysis and migration readiness. | + +## Recommendation messages + +The **Recommendation** column displays one of the following messages based on the partition's scope, unsupported feature status, and SIEM forwarding configuration. + +| Is Included | Unsupported Features Detected | SIEM Forwarding | Recommendation | +|:--|:--|:--|:--| +| `true` | `false` | Any | No action needed. No feature conflicts detected. Excluding this partition can reduce scan cost. | +| `false` | `false` | `false` | No action needed. No feature conflicts detected. | +| `false` | `false` | `true` | Switch to Included. SIEM Forwarding will not work correctly on an excluded partition. | +| `false` | `true` | Any | Switch to Included. Monitors, SLOs, and Scheduled Views will not work correctly on an excluded partition. | + +## FAQ + +### What is the Flex to Tier Migration Report? + +The Flex to Tier Migration Report is a tool that shows each partition in your organization and whether it is ready to migrate from Flex to Tiered storage. It evaluates each partition against a set of dependency checks, including monitors, SLOs, scheduled views, and SIEM forwarding, and provides a recommended action for each. + +### What does the Is Included column mean? + +The Is Included column indicates whether a partition is part of the [default scope](/docs/manage/partitions/flex/faq/#how-can-i-optimize-my-query-using-default-scope). A value of `true` means the partition is included in the default scope; `false` means it is excluded. Excluded partitions may need to be switched to included if they have active SIEM forwarding or unsupported feature dependencies. + +### What happens to monitors and SLOs after migration to Tiered storage? + +Monitors and SLOs that rely on a partition excluded from Tiered storage may stop functioning correctly after migration. The report lists the affected monitor and SLO names in the **Unsupported Monitor** and **Unsupported SLO** columns so you can take action before migration. + +### What should you do if my partition has SIEM Forwarding enabled? + +If SIEM Forwarding is enabled and the partition is currently excluded from the migration scope, the recommendation is to switch it to Included. SIEM Forwarding does not work correctly on excluded partitions, and leaving it excluded can result in data not being forwarded after migration. + +### How can you reduce scan costs during migration? + +If a partition is already included in the migration scope and no feature conflicts are detected, you can consider excluding it to reduce scan costs. The report surfaces this opportunity with the message: "No action needed. No feature conflicts detected. Excluding this partition can reduce scan cost." diff --git a/sidebars.ts b/sidebars.ts index 282d46242d..f3a146a401 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -962,6 +962,7 @@ module.exports = { 'manage/partitions/edit-data-forwarding-destinations-partition', 'manage/partitions/manage-indexes-variable-retention', 'manage/partitions/decommission-partition', + 'manage/partitions/flex-to-tier-migration-report', 'manage/partitions/faq', ] }, @@ -1064,7 +1065,6 @@ module.exports = { 'manage/manage-subscription/manage-billing-information', 'manage/manage-subscription/organization-usage-limits', 'manage/manage-subscription/scan-budgets', - 'manage/manage-subscription/flex-to-tier-migration-report', 'manage/manage-subscription/fedramp-capabilities', 'manage/manage-subscription/close-cancel-sumo-account', ] From c8eb1fb7c6692d721e5f0a33b234b66e55bb0a61 Mon Sep 17 00:00:00 2001 From: Jagadisha V Date: Mon, 1 Jun 2026 19:10:07 +0530 Subject: [PATCH 3/7] Update flex-to-tier migration report based on GDoc feedback Co-Authored-By: Claude Sonnet 4.6 --- .../flex-to-tier-migration-report.md | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/docs/manage/partitions/flex-to-tier-migration-report.md b/docs/manage/partitions/flex-to-tier-migration-report.md index bf686f83b7..88966acd05 100644 --- a/docs/manage/partitions/flex-to-tier-migration-report.md +++ b/docs/manage/partitions/flex-to-tier-migration-report.md @@ -13,7 +13,7 @@ keywords: import useBaseUrl from '@docusaurus/useBaseUrl'; -The Flex to Tier Migration Report shows your partitions and their readiness for migration to Tiered storage. It includes current recommendation messages and the status of any unsupported features that may be affected by migration. +The Flex to Tier Migration Report shows your partitions and their readiness for migration from a flex licensing model for log ingestion to a tiered licensing model for log ingestion. It includes recommendation messages and the status of any unsupported features that may be affected by migration. ## Column definitions @@ -23,7 +23,7 @@ The Flex to Tier Migration Report shows your partitions and their readiness for | **Ingestion Volume** | Total ingestion volume associated with the partition. | | **Current Scope** | Indicates whether the partition is currently included or excluded from the migration scope. | | **SIEM Forwarding** | Indicates whether SIEM forwarding is enabled for the partition (`true` / `false`). | -| **Unsupported Features Detected When Moving Towards Tiered** | Displays whether any unsupported dependencies are detected for the partition after migration to Tiered storage. For example, `true [monitor, slo]`. | +| **Unsupported Features Detected When Moving Towards Tiered** | Displays any unsupported dependencies detected for the partition after migration to Tiered storage. For example, `true [monitor, slo]`. | | **Unsupported Monitor** | Lists monitor names currently using the partition that may not function after migration. | | **Unsupported SLO** | Lists SLO names associated with the partition that may become unsupported after migration. | | **Unsupported Scheduled Views** | Lists scheduled view names dependent on the partition that may not work after migration. | @@ -35,10 +35,10 @@ The **Recommendation** column displays one of the following messages based on th | Is Included | Unsupported Features Detected | SIEM Forwarding | Recommendation | |:--|:--|:--|:--| -| `true` | `false` | Any | No action needed. No feature conflicts detected. Excluding this partition can reduce scan cost. | -| `false` | `false` | `false` | No action needed. No feature conflicts detected. | -| `false` | `false` | `true` | Switch to Included. SIEM Forwarding will not work correctly on an excluded partition. | -| `false` | `true` | Any | Switch to Included. Monitors, SLOs, and Scheduled Views will not work correctly on an excluded partition. | +| `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. | ## FAQ @@ -56,8 +56,4 @@ Monitors and SLOs that rely on a partition excluded from Tiered storage may stop ### What should you do if my partition has SIEM Forwarding enabled? -If SIEM Forwarding is enabled and the partition is currently excluded from the migration scope, the recommendation is to switch it to Included. SIEM Forwarding does not work correctly on excluded partitions, and leaving it excluded can result in data not being forwarded after migration. - -### How can you reduce scan costs during migration? - -If a partition is already included in the migration scope and no feature conflicts are detected, you can consider excluding it to reduce scan costs. The report surfaces this opportunity with the message: "No action needed. No feature conflicts detected. Excluding this partition can reduce scan cost." +If SIEM Forwarding is enabled and the partition is currently excluded from the migration scope, the recommendation is to switch it to Included (Continuous). SIEM Forwarding does not work correctly on excluded partitions, and leaving it excluded can result in data not being forwarded after migration. From c38bec8180a8cdd4fc2764eaa5ac5afc5f692b11 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Thu, 4 Jun 2026 09:38:37 +0530 Subject: [PATCH 4/7] Update docs/manage/partitions/flex-to-tier-migration-report.md Co-authored-by: Kim Pohas <56411016+kimsauce@users.noreply.github.com> --- docs/manage/partitions/flex-to-tier-migration-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manage/partitions/flex-to-tier-migration-report.md b/docs/manage/partitions/flex-to-tier-migration-report.md index 88966acd05..c34f48376d 100644 --- a/docs/manage/partitions/flex-to-tier-migration-report.md +++ b/docs/manage/partitions/flex-to-tier-migration-report.md @@ -48,7 +48,7 @@ The Flex to Tier Migration Report is a tool that shows each partition in your or ### What does the Is Included column mean? -The Is Included column indicates whether a partition is part of the [default scope](/docs/manage/partitions/flex/faq/#how-can-i-optimize-my-query-using-default-scope). A value of `true` means the partition is included in the default scope; `false` means it is excluded. Excluded partitions may need to be switched to included if they have active SIEM forwarding or unsupported feature dependencies. +The **Is Included** column indicates whether a partition is part of the [default scope](/docs/manage/partitions/flex/faq/#how-can-i-optimize-my-query-using-default-scope). A value of `true` means the partition is included in the default scope; `false` means it is excluded. Excluded partitions may need to be switched to **Included** if they have active SIEM forwarding or unsupported feature dependencies. ### What happens to monitors and SLOs after migration to Tiered storage? From b003e6bc8fba41b10d19a708a73c3cc771024a9b Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Fri, 12 Jun 2026 07:10:28 +0530 Subject: [PATCH 5/7] Update docs/manage/partitions/flex-to-tier-migration-report.md Co-authored-by: Kim Pohas <56411016+kimsauce@users.noreply.github.com> --- docs/manage/partitions/flex-to-tier-migration-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manage/partitions/flex-to-tier-migration-report.md b/docs/manage/partitions/flex-to-tier-migration-report.md index c34f48376d..9343782905 100644 --- a/docs/manage/partitions/flex-to-tier-migration-report.md +++ b/docs/manage/partitions/flex-to-tier-migration-report.md @@ -54,6 +54,6 @@ The **Is Included** column indicates whether a partition is part of the [default Monitors and SLOs that rely on a partition excluded from Tiered storage may stop functioning correctly after migration. The report lists the affected monitor and SLO names in the **Unsupported Monitor** and **Unsupported SLO** columns so you can take action before migration. -### What should you do if my partition has SIEM Forwarding enabled? +### What should I do if my partition has SIEM Forwarding enabled? If SIEM Forwarding is enabled and the partition is currently excluded from the migration scope, the recommendation is to switch it to Included (Continuous). SIEM Forwarding does not work correctly on excluded partitions, and leaving it excluded can result in data not being forwarded after migration. From 5f40abd36b65fbc2c95311b1df448d072f7231fd Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Fri, 12 Jun 2026 07:10:37 +0530 Subject: [PATCH 6/7] Update docs/manage/partitions/flex-to-tier-migration-report.md Co-authored-by: Kim Pohas <56411016+kimsauce@users.noreply.github.com> --- docs/manage/partitions/flex-to-tier-migration-report.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/manage/partitions/flex-to-tier-migration-report.md b/docs/manage/partitions/flex-to-tier-migration-report.md index 9343782905..d156be9903 100644 --- a/docs/manage/partitions/flex-to-tier-migration-report.md +++ b/docs/manage/partitions/flex-to-tier-migration-report.md @@ -1,7 +1,6 @@ --- id: flex-to-tier-migration-report title: Flex to Tier Migration Report -sidebar_label: Flex to Tier Migration Report description: Learn how to use the Flex to Tier Migration Report to assess partition readiness, understand column definitions, and act on migration recommendations. keywords: - flex From 096b0b4c1fc93bd5252a2be4700729875f5a2a35 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Fri, 12 Jun 2026 07:11:16 +0530 Subject: [PATCH 7/7] Update docs/manage/partitions/flex-to-tier-migration-report.md Co-authored-by: Kim Pohas <56411016+kimsauce@users.noreply.github.com> --- docs/manage/partitions/flex-to-tier-migration-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manage/partitions/flex-to-tier-migration-report.md b/docs/manage/partitions/flex-to-tier-migration-report.md index d156be9903..49ec8fa1e8 100644 --- a/docs/manage/partitions/flex-to-tier-migration-report.md +++ b/docs/manage/partitions/flex-to-tier-migration-report.md @@ -12,7 +12,7 @@ keywords: import useBaseUrl from '@docusaurus/useBaseUrl'; -The Flex to Tier Migration Report shows your partitions and their readiness for migration from a flex licensing model for log ingestion to a tiered licensing model for log ingestion. It includes recommendation messages and the status of any unsupported features that may be affected by migration. +The Flex to Tier Migration Report shows your partitions and their readiness for migration from a flex licensing model to a tiered licensing model for log ingestion. It includes recommendation messages and the status of any unsupported features that may be affected by migration. ## Column definitions