-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Doc: Group central mgmt and configuring central mgmt topics #14050
Conversation
++++ | ||
<titleabbrev>Centralized Pipeline Management</titleabbrev> | ||
++++ |
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.
Removing this (at least for now) to avoid having two subsections called "Centralized Pipeline Management" back to back. :-)
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!
@logstashmachine backport 8.2 |
(cherry picked from commit 2c5cc00)
@logstashmachine backport 8.1 |
(cherry picked from commit 2c5cc00)
* main: Fix geoip database download does not respect http_proxy setting (elastic#14048) Doc: Group central mgmt and configuring central mgmt topics (elastic#14050) Implements DLQ storage policy (elastic#13923)
Our central management topics are split across two sections with links back and forth. The central management content needs some work (see meta issue #14049), but grouping these similar topics is a good first step.
Before

And then two sections later...After