Describe how to access monitoring cluster via CCS
- Dominant language
- Java
- Stars
- 105
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Description
Per https://github.com/elastic/elasticsearch/pull/42655#pullrequestreview-243954062
> One thing to consider is that technically users can configure filebeat to the production cluster and setup CCS and the monitoring UI will be able to read those indices. Do we want to include this in the docs?
This seems to be another method of configuring monitoring in a production environment, which should be added to:
https://www.elastic.co/guide/en/elastic-stack-overview/master/monitoring-production.html
Contributor guide
No contributing guide indexed for this repository
Research direction
Open the monitoring-production.html page linked in the issue and review the referenced pull request discussion. Document the CCS-based way to let Filebeat use the production cluster for monitoring, including the relevant setup context. Done means the production monitoring documentation describes this alternative clearly and consistently with the existing methods.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, observability-sre
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100