Add Data Filebeat Installation Screen #6017
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(cherry picked from commit 8cbf211)
(cherry picked from commit 1fc754b)
(cherry picked from commit 4975f57)
(cherry picked from commit 599e012)
(cherry picked from commit 36dc443)
(cherry picked from commit ad25d24)
(cherry picked from commit 4bcc5a1)
…ome light styling
…rls for the new ingest wizards
… a way to get back to the landing page
Create new Add Data landing page
| @@ -0,0 +1,34 @@ | |||
| <div class="wizard-step-title"> | |||
| <h3>Follow these instructions to install Filebeat</h3> | |||
| Now that you've got a fresh pipeline and index pattern, let's throw some data at it! | |||
There was a problem hiding this comment.
should we be more explicit about what we just indexed into Elasticsearch? For example, it would be useful to know what the pipeline was indexed as (pipeline name) and instructions on where to find it
There was a problem hiding this comment.
Yeah, this is an interesting question. I think in an ideal world, the user would never have to know anything about how the pipeline actually gets persisted to Elasticsearch. But given that we won't have the ability to manage pipelines right off the bat, advanced users will probably benefit from this kind of information. Maybe we could have a collapsed by default section on this page that provides additional info like this?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Requires #5790
WIP PR to implement the install filebeat screen in #5974