-
Notifications
You must be signed in to change notification settings - Fork 190
Update 'Upload data files' with steps for the new file import process #4409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Vale Linting ResultsSummary: 3 suggestions found 💡 Suggestions (3)
|
🔍 Preview links for changed docs |
jgowdyelastic
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
c56f840 to
71eabc3
Compare
georgewallace
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updates look good to me. Thanks for removing the screenshots!
| :::{applies-item} serverless: ga | ||
|
|
||
| 1. Choose whether to import the data to a new index or to an existing one. | ||
| 2. Enter a name for the new index or select an existing index from the dropdown. | ||
| 3. Drag one or more files into the upload area or click **Select or drag and drop a file** to choose files from your computer. | ||
|
|
||
| The supported file formats are PDF, TXT, CSV, log files and NDJSON. | ||
|
|
||
| After you upload your files, you can inspect the data and make any necessary changes before importing it. | ||
|
|
||
| 4. Click **Import** to complete the process. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As Stack 9.2 and Serverless are identical, can we combine these into a single tab instead of two? I've seen this pattern elsewhere, for example:
- https://www.elastic.co/docs/solutions/security/ai/attack-discovery#attack-discovery-rbac
- https://www.elastic.co/docs/solutions/security/get-started/automatic-migration
But our cumulative docs guidelines aren't clear about what the recommended pattern is. Do you know? The applies-switch docs also don't cover this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah wait, it is covered here:
You can specify multiple applies_to definitions in a single applies-item using YAML object notation with curly braces {}. This is useful when content applies to multiple deployment types or versions simultaneously.
Summary
This PR:
Resolves #3243
Generative AI disclosure
Preview
manage-data/ingest/sample-data.md
manage-data/ingest/upload-data-files.md