-
Notifications
You must be signed in to change notification settings - Fork 68
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
Move section about Logstash to bottom of Kafka output page #1430
Conversation
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
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
(cherry picked from commit b05a3ab)
(cherry picked from commit b05a3ab)
(cherry picked from commit b05a3ab)
…1436) (cherry picked from commit b05a3ab) Co-authored-by: David Kilfoyle <[email protected]>
…1435) (cherry picked from commit b05a3ab) Co-authored-by: David Kilfoyle <[email protected]>
…1434) (cherry picked from commit b05a3ab) Co-authored-by: David Kilfoyle <[email protected]>
At the top of the Kafka output settings page is a section warning users about potential problems when they use use Logstash to modify the Kafka output on its way to Elasticsearch. It's not ideal for all users to start their Kafka output journey with that section.
I think it'd be better to have that section at the bottom of the Kafka output settings page, and to make sure people find the section we can add a warning at the top of the page, like this:
The guidance for Logstash appears just as before, but at the bottom of the page:
@lucabelluccini, @nimarezainia Any thoughts or concerns?