-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Updating monitoring docs with direct monitoring configuration #11678
Updating monitoring docs with direct monitoring configuration #11678
Conversation
Pinging @elastic/stack-monitoring |
I added a few minor updates to the X-Pack terminology and links. Hope that's okay! |
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 and builds successfully
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, too!
Follow up question on this PR. @lcawl, @dedemorton |
Also curious as to if the name "Xpack Monitoring" was purposefully left in the |
@ycombinator is probably the best person to answer @bmorelli25. Incidentally, I'm running 7.0, and Kibana stops displaying Beats monitoring data if I remove |
I'm okay with leaving it and marking it as deprecated in the docs. I guess it depends on what our general policy around documenting deprecated settings is. @lcawl @dedemorton?
This is an interesting one for sure. As this is a comment header in the
I commented on this here: #11329 (comment). |
Beats now have the ability to send their monitoring data directly to the monitoring Elasticsearch cluster (#9260). This PR updates the Beats monitoring documentation with this change.
Resolves #11637.