-
Notifications
You must be signed in to change notification settings - Fork 106
Configure kibana reporting page #799
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
Merged
Merged
Conversation
This file contains hidden or 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
shainaraskas
approved these changes
Mar 18, 2025
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.
this looks great.
I do think the location in the toc is a little strange (it's closer in scope to any of the other feature config sections we have), but we can leave it for now.
Co-authored-by: shainaraskas <[email protected]>
eedugon
added a commit
that referenced
this pull request
Mar 24, 2025
Should close elastic/docs-projects#341 Preview: all content and sub-docs from - [Production guidance](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/802/deploy-manage/production-guidance) Pending items: > Refine Kibana task manager scaling considerations to cover only deployment considerations, link up to the functionality overview in Distributed architecture I haven't done that, but it should be pretty quick and easy if we want to do it at a later stage. This PR requires PR #799 to be merged first, in order to have this link available `/deploy-manage/deploy/kibana-reporting-configuration.md#install-reporting-packages`. --------- Co-authored-by: shainaraskas <[email protected]>
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.
We didn't have an issue to track this page yet, but here it goes.
Content Preview
This page is the migrated and refined version of this original doc.
I had to change a few things to make the flow better. Certain configuration steps are only applicable to self-managed deployments, while others are applicable to all deployment types. Probably I'll need review and guidance here for the
applies_to
tags and how to address that part.Reporting is planned to be a bit spread, as we mentioned in the excel:
Pending: