Reorganize Fleet Server content #1274
Conversation
|
A documentation preview will be available soon: |
| However, it is off by default in the {ecloud} agent policy because monitoring | ||
| requires additional RAM. | ||
|
|
||
| To turn on {fleet-server} monitoring in the agent policy: |
There was a problem hiding this comment.
@dedemorton I believe the docs are wrong in that we don't allow this. The UI might have *seemed to let you do it, but we've recently fixed that I think. QA logged a bug about it and was confirmed, see notes in this issue:
elastic/kibana#110533 (comment)
and this is the 'question' bug that QA logged: elastic/kibana#117809
There was a problem hiding this comment.
This isn't new content; it's just moved from the long Fleet Server topic. So it has not been tested recently.
@nimarezainia Can you let me know how to proceed here? I can remove the content, but I don't want to make the call without your input.
There was a problem hiding this comment.
@EricDavisX Actually, can you open an issue about this in the observability-docs repo? I don't want this PR to get stalled since the changes are structural, not content.
|
apart from the one section I commented on not being correct, is this mostly then copy / paste rearrangement? Thanks much, I appreciate that you bother as such. It is appreciated by all who use the docs, and many of us do. :) 👍 thanks! |
|
I'm going to merge this now so I can get the links working, and we can follow up on any content changes when there are issues to track them. Thanks everyone! |
* Reorganize Fleet Server content * Fix chicken/egg link problem # Conflicts: # docs/en/ingest-management/fleet/fleet-server.asciidoc
* Reorganize Fleet Server content * Fix chicken/egg link problem # Conflicts: # docs/en/ingest-management/fleet/fleet-server.asciidoc
* Reorganize Fleet Server content * Fix chicken/egg link problem
3 participants
We've added so much content to the Fleet Server topic that it's hard to find the basic steps for adding a Fleet Server, especially in our current doc system. I was using the docs today and felt a bit frustrated scrolling through all the stuff I didn't want to see.
So I propose that we break this page down into multiple pages. WDYT? Any objections?
Feel free to scan the content. The only new parts are the list of links and small tweaking of intros to make the pages work better on their onw.