Skip to content
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

Merged
merged 8 commits into from
Jun 17, 2024

Conversation

shainaraskas
Copy link
Collaborator

@shainaraskas shainaraskas commented Jun 7, 2024

This PR:

  • adjusts a faq to reflect current pricing info
  • adds a faq for requesting backups/restores
  • adds info about migrating data to/from es3 with logstash, including a procedure, a faq, and a reference in the technical preview docs
  • fixed H levels on the "what is serverless elastic" page so the anchor icon works on hover
  • removes a stray reference to ILM, which doesn't work in serverless

faq section
new logstash section
technical preview limitations page

@elasticdocs
Copy link
Collaborator

elasticdocs commented Jun 7, 2024

🚀 Built co-preview-docs successfully!

Issues? Visit #next-docs in Slack

@shainaraskas shainaraskas marked this pull request as ready for review June 7, 2024 18:59
@shainaraskas shainaraskas requested a review from a team as a code owner June 7, 2024 18:59
@shainaraskas
Copy link
Collaborator Author

@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

@shainaraskas shainaraskas reopened this Jun 7, 2024
Comment on lines 78 to 89
## 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.

Copy link
Contributor

@karenzone karenzone Jun 7, 2024

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.

Copy link

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

Copy link
Contributor

@karenzone karenzone Jun 11, 2024

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.

Copy link
Contributor

@karenzone karenzone left a 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.

@kilfoyle
Copy link
Contributor

@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

Shaina, I'll defer to Karen for this PR, since she knows far, far more than I do about Logstash. :-)

@shainaraskas shainaraskas requested a review from a team as a code owner June 13, 2024 13:42
@shainaraskas shainaraskas changed the base branch from main to add-missing-files June 13, 2024 13:43
@shainaraskas shainaraskas changed the base branch from add-missing-files to main June 13, 2024 13:43
@shainaraskas shainaraskas requested a review from karenzone June 13, 2024 13:46
@kilfoyle kilfoyle removed their request for review June 13, 2024 13:50
@elasticdocs
Copy link
Collaborator

elasticdocs commented Jun 13, 2024

🚀 Built elastic-dot-co-docs-preview-docs successfully!

Issues? Visit #next-docs in Slack

Copy link
Contributor

@karenzone karenzone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@shainaraskas shainaraskas merged commit 3dc188c into main Jun 17, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants