[9.2] Automatic Migration updates #3497
Conversation
🔍 Preview links for changed docs |
| 6. After you upload your Splunk assets, Automatic Migration will detect whether they use any macros or lookups. If so, follow the instructions which appear to export and upload them. Alternatively, you can complete this step later — however, until you upload them, some of your migrated assets will have a `partially translated` status. If you upload them now, you don't have to wait on this page for them to be processed — a notification will appear when processing is complete. | ||
|
|
||
| 7. Click **Translate** to start the rule translation process. A name for this migration is automatically created, and you can track its progress on this page. The **More actions** ({icon}`boxes_vertical`) button lets you rename or pause the migration. | ||
| 7. Click **Translate** to start the rule translation process. The **Start rules migration** popup appears. Use the dropdown menu to select which AI connector to use. For rule migrations there is a **Match to Elastic prebuilt rules** option, which is enabled by default; when it's enabled, any rules you translate that are similar to Elastic prebuilt rules are converted to those prebuilt rules. When it's disabled, each of your rules will be converted into a new custom rule. |
There was a problem hiding this comment.
Click Translate to start the rule translation process. The Start rules migration popup appears. Use the dropdown menu to select which AI connector to use. For rule migrations there is a Match to Elastic prebuilt rules option, which is enabled by default; when it's enabled, we will check to see if a similar rules already exist within elastic and help match to the rules initially provided. This process uses less tokens overall. When it's disabled, each of your rules will be translated into a new custom rule, but with out matching to out of the box rules.
There was a problem hiding this comment.
I added the additional detail about tokens you included here, and mostly kept my wording around what the option does. I'll leave this comment open so other docs writers can weigh in on which wording is more clear to them.
Co-authored-by: Nastasha Solomon <[email protected]>
3 participants
Fixes elastic/docs-content-internal/issues/389 and fixes elastic/docs-content-internal/issues/390 by updating the Automatic Migration docs to include the new technical preview of dashboard migration, as well as some updates to rule migration.
You can find the preview in this comment