-
Notifications
You must be signed in to change notification settings - Fork 20
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
Enhancements to common questions, migrate with logstash, fix heading order #22
Conversation
🚀 Built co-preview-docs successfully!
|
@kilfoyle / @karenzone when one of you has a few min can you look at the logstash change in this PR? I don't know if I'm using the right language around turning on / using a logstash pipeline tyty |
## Migrating Elasticsearch data using ((ls)) | ||
|
||
You can also use ((ls)) to migrate data into and out of ((es3)) environments with the ((es)) [input plugin](((logstash-ref))/plugins-inputs-elasticsearch.html) and [output plugin](((logstash-ref))/plugins-outputs-elasticsearch.html). | ||
|
||
For each index to be migrated, do the following: | ||
|
||
1. Create the index in the destination environment. | ||
2. Add the desired [settings](((ref))/indices-get-settings.html) and [mappings](((ref))/indices-get-mapping.html) to the destination index based on the origin index. | ||
|
||
If you're migrating into an ((es3)) environment, then you might need to adjust your index settings if your origin index is using <DocLink id="serverlessDifferences">settings that aren't supported in Serverless</DocLink>. | ||
3. Run your ((ls)) pipeline to migrate from the origin index to the destination index. | ||
|
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.
We've been super careful about how we talk about Logstash in serverless. We want users to know that Logstash is an option, but it brings a lot more overhead than will be appropriate for most of our serverless audience. I'm also not sure that we want to emphasize the ability to migrate data out of serverless. Logstash users would automatically assume that, and it would likely confuse others.
If you're going for a quick win, how about if we take this out for now and rework it in a separate PR? What's here isn't right.
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.
@karenzone we're cognizant needing to careful about positioning around Logstash, however as of this time we need alternatives for users who want to either consolidate project data in Serverless or migrate it back to ESS Hosted (based on support cases).
See this discussion for the rationale around adding this section
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.
@linyaru Absolutely! I'm totally on board with this approach. I had some comments and suggestions teed up, but had not submitted them. They're submitted now.
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.
Yes, @shainaraskas, these comments were sitting in a pending review. Thanks for the nudge.
Please let me know what you think.
serverless/pages/ingest-your-data-ingest-data-through-integrations-logstash.mdx
Outdated
Show resolved
Hide resolved
Shaina, I'll defer to Karen for this PR, since she knows far, far more than I do about Logstash. :-) |
…ions-logstash.mdx
🚀 Built elastic-dot-co-docs-preview-docs successfully!
|
serverless/pages/ingest-your-data-ingest-data-through-integrations-logstash.mdx
Show resolved
Hide resolved
…ions-logstash.mdx Co-authored-by: Karen Metts <[email protected]>
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
This PR:
faq section
new logstash section
technical preview limitations page