[ Siem Migrations ] Upsell Siem Migrations Start #212607

logeekal · 2025-02-27T09:15:33Z

Summary

This PR adds the Upsell section for SIEM Migration Start section.

Design Source

SIEM migrations has below requirements in ESS and Serverless and if these requirements are not met, We show the upsell sections.

ESS
- Enterprise license.
Serverless
- Complete Product tier

Demo

Instance	Demo
Serverless	siem_migrations_start_upsell_serverless.mp4
ESS	siem_migrations_start_upsell_ess.mp4

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
Documentation was added for features that require explanation or tutorials
Unit or functional tests were updated or added to match the most common scenarios
If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
Flaky Test Runner was used on any tests changed
The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

See some risk examples
...

elasticmachine · 2025-02-27T16:30:33Z

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

semd · 2025-02-27T16:30:42Z

...ents/onboarding_body/cards/siem_migrations/start_migration/start_migration_check_complete.ts

@@ -19,12 +19,11 @@ export const checkStartMigrationCardComplete: OnboardingCardCheckComplete<

  let isComplete = false;

-  if (missingCapabilities.length === 0) {
+  if (siemMigrations.rules.isAvailable() && missingCapabilities.length === 0) {


NIT: The capabilities check is already done internally by the isAvailable, there's no need to check it again here.

Suggested change

if (siemMigrations.rules.isAvailable() && missingCapabilities.length === 0) {

if (siemMigrations.rules.isAvailable()) {

Oh right. you told me exactly that. 🤦 .

done here: 0cac4f3

semd

LGTM! great work @logeekal

bojanasan · 2025-02-27T17:44:45Z

looks great! Thank you @logeekal

elasticmachine · 2025-02-28T03:50:49Z

💚 Build Succeeded

Buildkite Build
Commit: a549610

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
`securitySolutionEss`	86	88	+2
`securitySolutionServerless`	121	123	+2
total			+4

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
`securitySolution`	8.9MB	8.9MB	+463.0B
`securitySolutionEss`	29.2KB	31.9KB	+2.6KB
`securitySolutionServerless`	53.4KB	54.6KB	+1.2KB
total			+4.2KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
`securitySolutionEss`	12.9KB	13.1KB	+182.0B
`securitySolutionServerless`	30.1KB	30.7KB	+646.0B
total			+828.0B

Unknown metric groups

async chunk count

id	before	after	diff
`securitySolutionEss`	4	5	+1
`securitySolutionServerless`	16	17	+1
total			+2

History

💚 Build #279773 succeeded 027c7ad

kibanamachine · 2025-02-28T03:51:46Z

Starting backport for target branches: 8.18, 8.x, 9.0

https://github.com/elastic/kibana/actions/runs/13580968541

kibanamachine · 2025-02-28T03:57:15Z

💔 All backports failed

Status	Branch	Result
❌	8.18	Backport failed because of merge conflicts
❌	8.x	Backport failed because of merge conflicts
❌	9.0	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 212607

Questions ?

Please refer to the Backport tool documentation

## Summary This PR adds the Upsell section for SIEM Migration Start section. - [Design Source](https://www.figma.com/design/BD9GZZz6y8pfSbubAt5H2W/%5B8.18%5D-GenAI-Powered-SIEM-Migration%3A-Rule-translation?node-id=63-81202&p=f&t=8x9RlFegceXzwYQf-0) SIEM migrations has below requirements in ESS and Serverless and if these requirements are not met, We show the upsell sections. - ESS - `Enterprise` license. - Serverless - `Complete` Product tier ## Demo |Instance|Demo| |---|---| |Serverless|<video src="https://github.com/user-attachments/assets/58d3ce98-7108-4d74-9f5c-e270804f2666"/>| |ESS|<video src="https://github.com/user-attachments/assets/85b650a7-fa11-4855-9927-aab89a2ed8ef"/>| ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 44a184c) # Conflicts: # x-pack/solutions/security/plugins/security_solution/public/onboarding/components/onboarding_body/cards/siem_migrations/start_migration/index.ts

kibanamachine · 2025-03-04T04:48:53Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 212607 locally

## Summary This PR adds the Upsell section for SIEM Migration Start section. - [Design Source](https://www.figma.com/design/BD9GZZz6y8pfSbubAt5H2W/%5B8.18%5D-GenAI-Powered-SIEM-Migration%3A-Rule-translation?node-id=63-81202&p=f&t=8x9RlFegceXzwYQf-0) SIEM migrations has below requirements in ESS and Serverless and if these requirements are not met, We show the upsell sections. - ESS - `Enterprise` license. - Serverless - `Complete` Product tier ## Demo |Instance|Demo| |---|---| |Serverless|<video src="https://github.com/user-attachments/assets/58d3ce98-7108-4d74-9f5c-e270804f2666"/>| |ESS|<video src="https://github.com/user-attachments/assets/85b650a7-fa11-4855-9927-aab89a2ed8ef"/>| ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 44a184c)

## Summary This PR adds the Upsell section for SIEM Migration Start section. - [Design Source](https://www.figma.com/design/BD9GZZz6y8pfSbubAt5H2W/%5B8.18%5D-GenAI-Powered-SIEM-Migration%3A-Rule-translation?node-id=63-81202&p=f&t=8x9RlFegceXzwYQf-0) SIEM migrations has below requirements in ESS and Serverless and if these requirements are not met, We show the upsell sections. - ESS - `Enterprise` license. - Serverless - `Complete` Product tier ## Demo |Instance|Demo| |---|---| |Serverless|<video src="https://github.com/user-attachments/assets/58d3ce98-7108-4d74-9f5c-e270804f2666"/>| |ESS|<video src="https://github.com/user-attachments/assets/85b650a7-fa11-4855-9927-aab89a2ed8ef"/>| ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 44a184c) # Conflicts: # x-pack/solutions/security/packages/upselling/service/types.ts # x-pack/solutions/security/plugins/security_solution_serverless/public/upselling/upsellings.tsx

logeekal · 2025-03-04T09:07:57Z

💚 All backports created successfully

Status	Branch	Result
✅	9.0
✅	8.x
✅	8.18

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

## Summary This PR adds the Upsell section for SIEM Migration Start section. - [Design Source](https://www.figma.com/design/BD9GZZz6y8pfSbubAt5H2W/%5B8.18%5D-GenAI-Powered-SIEM-Migration%3A-Rule-translation?node-id=63-81202&p=f&t=8x9RlFegceXzwYQf-0) SIEM migrations has below requirements in ESS and Serverless and if these requirements are not met, We show the upsell sections. - ESS - `Enterprise` license. - Serverless - `Complete` Product tier ## Demo |Instance|Demo| |---|---| |Serverless|<video src="https://github.com/user-attachments/assets/58d3ce98-7108-4d74-9f5c-e270804f2666"/>| |ESS|<video src="https://github.com/user-attachments/assets/85b650a7-fa11-4855-9927-aab89a2ed8ef"/>| ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 44a184c) # Conflicts: # x-pack/solutions/security/packages/upselling/service/types.ts # x-pack/solutions/security/plugins/security_solution_serverless/public/upselling/upsellings.tsx

logeekal · 2025-03-04T09:11:17Z

💚 All backports created successfully

Status	Branch	Result
✅	8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

kibanamachine · 2025-03-05T05:48:47Z

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.

…13047) # Backport This will backport the following commits from `main` to `8.18`: - [[ Siem Migrations ] Upsell Siem Migrations Start (#212607)](#212607)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)

…3044) # Backport This will backport the following commits from `main` to `9.0`: - [[ Siem Migrations ] Upsell Siem Migrations Start (#212607)](#212607)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)

…3048) # Backport This will backport the following commits from `main` to `8.x`: - [[ Siem Migrations ] Upsell Siem Migrations Start (#212607)](#212607)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)  --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

logeekal added 6 commits February 27, 2025 10:14

feat: initial implementation

3716cca

tests

6c1d3b5

fix: Serverless Upsell Message

bf19545

better text

17bc65f

fix: ESS Component name

0991ed2

tests: check Complete

cb1d6f9

logeekal marked this pull request as ready for review February 27, 2025 16:19

logeekal requested review from a team as code owners February 27, 2025 16:19

fix: components

012dc47

logeekal added release_note:skip Skip the PR/issue when compiling release notes v9.0.0 Team:Threat Hunting Security Solution Threat Hunting Team backport:version Backport to applied version labels v8.18.0 v9.1.0 v8.19.0 labels Feb 27, 2025

semd reviewed Feb 27, 2025

View reviewed changes

fix: remove missingCapabilities check

0cac4f3

semd approved these changes Feb 27, 2025

View reviewed changes

Merge branch 'main' into siem_migrations_upselling

027c7ad

Merge branch 'main' into siem_migrations_upselling

a549610

logeekal merged commit 44a184c into elastic:main Feb 28, 2025
9 checks passed

logeekal mentioned this pull request Feb 28, 2025

[9.0] [ Siem Migrations ] Upsell Siem Migrations Start (#212607) #212714

Closed

kibanamachine mentioned this pull request Feb 28, 2025

[Automatic Import] Fixes the CSV header bug #212513

Merged

7 tasks

kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Mar 4, 2025

logeekal mentioned this pull request Mar 4, 2025

[9.0] [ Siem Migrations ] Upsell Siem Migrations Start (#212607) #213044

Merged

logeekal mentioned this pull request Mar 4, 2025

[8.x] [ Siem Migrations ] Upsell Siem Migrations Start (#212607) #213046

Closed

logeekal mentioned this pull request Mar 4, 2025

[8.18] [ Siem Migrations ] Upsell Siem Migrations Start (#212607) #213047

Merged

logeekal mentioned this pull request Mar 4, 2025

[8.x] [ Siem Migrations ] Upsell Siem Migrations Start (#212607) #213048

Merged

kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Mar 5, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[ Siem Migrations ] Upsell Siem Migrations Start #212607

[ Siem Migrations ] Upsell Siem Migrations Start #212607

logeekal commented Feb 27, 2025 •

edited by kibanamachine

Loading

elasticmachine commented Feb 27, 2025

semd Feb 27, 2025

logeekal Feb 27, 2025 •

edited

Loading

logeekal Feb 27, 2025

semd left a comment

bojanasan commented Feb 27, 2025

elasticmachine commented Feb 28, 2025

async chunk count

kibanamachine commented Feb 28, 2025

kibanamachine commented Feb 28, 2025

kibanamachine commented Mar 4, 2025

logeekal commented Mar 4, 2025

logeekal commented Mar 4, 2025

kibanamachine commented Mar 5, 2025

	if (siemMigrations.rules.isAvailable() && missingCapabilities.length === 0) {
	if (siemMigrations.rules.isAvailable()) {

[ Siem Migrations ] Upsell Siem Migrations Start #212607

[ Siem Migrations ] Upsell Siem Migrations Start #212607

Conversation

logeekal commented Feb 27, 2025 • edited by kibanamachine Loading

Summary

Demo

Checklist

Identify risks

elasticmachine commented Feb 27, 2025

semd Feb 27, 2025

Choose a reason for hiding this comment

logeekal Feb 27, 2025 • edited Loading

Choose a reason for hiding this comment

logeekal Feb 27, 2025

Choose a reason for hiding this comment

semd left a comment

Choose a reason for hiding this comment

bojanasan commented Feb 27, 2025

elasticmachine commented Feb 28, 2025

💚 Build Succeeded

Metrics [docs]

Module Count

Async chunks

Page load bundle

async chunk count

History

kibanamachine commented Feb 28, 2025

kibanamachine commented Feb 28, 2025

💔 All backports failed

Manual backport

Questions ?

kibanamachine commented Mar 4, 2025

logeekal commented Mar 4, 2025

💚 All backports created successfully

Questions ?

logeekal commented Mar 4, 2025

💚 All backports created successfully

Questions ?

kibanamachine commented Mar 5, 2025

logeekal commented Feb 27, 2025 •

edited by kibanamachine

Loading

logeekal Feb 27, 2025 •

edited

Loading