kibana/docs/user/monitoring/xpack-monitoring.asciidoc
DeDe Morton 9ff847dec7
[DOCS] Describe how to use Elastic Agent to monitor Kibana (#152634)
## Summary

Add Elastic Agent as another way to collect monitoring data.

This work is tracked by
https://github.com/elastic/observability-docs/issues/2602.

There will be additional PRs to address changes required to monitoring
docs for other stack components. TBH, it pains me a bit to see how many
places users need to go to find info about stack monitoring, but fixing
that problem is not in scope for these updates unfortunately. :-/

Please respond to questions addressed to reviewers.

### Checklist

Delete any items that are not applicable to this PR.

- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)

### To Do before merging

- [x] Remove questions to reviewers.

---------

Co-authored-by: Kevin Lacabane <klacabane@gmail.com>
2023-03-23 11:00:13 -07:00

26 lines
No EOL
910 B
Text

[role="xpack"]
[[xpack-monitoring]]
= Stack Monitoring
[partintro]
--
The {kib} {monitor-features} serve two separate purposes:
. To visualize monitoring data from across the {stack}. You can view health and
performance data for {es}, {ls}, {ents}, APM, and Beats in real time,
as well as analyze past performance.
. To monitor {kib} itself and route that data to the monitoring cluster.
If you enable monitoring across the {stack}, each monitored component is
considered unique based on its persistent UUID, which is written to the
<<settings,`path.data`>> directory when the node or instance starts.
For more information, see <<configuring-monitoring>> and
{ref}/monitor-elasticsearch-cluster.html[Monitor a cluster].
Want to monitor your fleet of {agent}s, too? Use {fleet} instead of the Stack
Monitoring UI. To learn more, refer to
{fleet-guide}/monitor-elastic-agent.html[Monitor {agent}s].
--