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

Streamline steps in the Filebeat Getting started guide #10640

Closed
dedemorton opened this issue Feb 7, 2019 · 8 comments
Closed

Streamline steps in the Filebeat Getting started guide #10640

dedemorton opened this issue Feb 7, 2019 · 8 comments
Assignees
Labels

Comments

@dedemorton
Copy link
Contributor

Input from Ron Cohen:

We recently discussed ideas to make the getting started steps even simpler/shorter.

For example, as a new-comer, it could look like setting up Logstash is part of the necessary or recommended workflow. We could perhaps move the Logstash part out so it's not a step?

More details about required changes to be added later...

@dedemorton dedemorton added the docs label Feb 7, 2019
@dedemorton dedemorton self-assigned this Feb 7, 2019
@dedemorton
Copy link
Contributor Author

dedemorton commented Feb 12, 2019

Capturing some other things I want to fix:

  • Make the logstash config optional.
  • Users should load the Beats assets (dashboards, pipelines, etc) before changing the output configuration to LS.
  • We've used the getting started guide to teach some basic concepts (what is an index, what are dashboards, etc), but that means users need to read a lot of detail that is not really required just to get started. Does this still make sense, or should we cover the details somewhere else (maybe even more fully) and use the getting started as a "Quick Start". We do have the Add Data tutorials which serve as a quick start, too, but this idea is worth considering.

@dedemorton
Copy link
Contributor Author

More thoughts on the notion of having a Quick Start Guide. What if we were to have a one-page quick start guide that distills the content down to just what you need to know to get started evaluating Beats. Then we could move the other content to "Setting up and running" and add more detail, where required, without having the getting started cover all the things.

@bmorelli25 Curious to hear your thoughts on this ^^.

@bmorelli25
Copy link
Member

We've used the getting started guide to teach some basic concepts (what is an index, what are dashboards, etc), but that means users need to read a lot of detail that is not really required just to get started.

I see why that information is included in the Getting Started section, but I don't think it makes the most sense. I think your Quick Start Guide solution is spot on. Simplify and get the consumer up and running as easily as possible.

@roncohen
Copy link
Contributor

absolutely agree regarding "Quick Start Guide" versus "Getting started Guide" 👍
I would make the quick start guide as short as possible and include links from there to more information for users who want to do something out of the ordinary.

@roncohen
Copy link
Contributor

Any progress on this? Let me know if i can help

@dedemorton
Copy link
Contributor Author

@roncohen Not yet...really sorry. Unfortunately, I keep needing to bump the priority of this work in favor of other things on the doc roadmap. It would be very easy for me to remove Logstash as a main step in the getting started (would take a few minutes). If it helps, I can move that forward now.

@dedemorton
Copy link
Contributor Author

Part of this effort involves restructuring the Beats docs so we have someplace where the extra content (stuff that doesn't belong in the GS) lives. To kick off this effort, I've started restructuring the Beats docs by dividing the config content into two sections: reference and how-to. After I've finalized the PR, I'll work on ripping out the excess content and moving it to the how-to section, as appropriate. See in-progress PR for the restructuring effort: #16825

@dedemorton
Copy link
Contributor Author

Closed by #17007.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants