[Stack Monitoring] Deprecate internal collection topics
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- elasticsearch
- Domain
- documentation, observability-sre
Research direction
Start with the unchecked Beats monitoring page at https://www.elastic.co/guide/en/beats/heartbeat/current/monitoring.html and compare it with the checked Stack, Elasticsearch, and Kibana documentation links. Update the applicable Beats and APM Server documentation to reflect the deprecation of internal collection topics; determine the Logstash documentation location once the referenced PR is no longer WIP.
Written by the indexing model from the issue text.
Description
We now have the ability to monitor Elasticsearch, Kibana, Logstash, Beats, and APM Server with Metricbeat. The previous method of monitoring stack products, using collection code internal to each product that shipped monitoring data to a custom Monitoring Bulk API endpoint, is now deprecated.
We should reflect this deprecation in documentation as well, specifically in these areas:
- Stack docs: https://www.elastic.co/guide/en/elastic-stack-overview/current/xpack-monitoring.html
- Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/current/monitor-elasticsearch-cluster.html
- Kibana: https://www.elastic.co/guide/en/kibana/current/configuring-monitoring.html
- Beats: https://www.elastic.co/guide/en/beats/heartbeat/current/monitoring.html (Using Heartbeat as a sample here, but applicable to all Beats and APM Server documentation)
- Logstash: TBD; PR introducing Metricbeat collection is currently WIP: https://github.com/elastic/logstash/pull/11033
- Dominant language
- Java
- Stars
- 105
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from elastic/stack-docs
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
elastic/stack-docs#2749 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
elastic/stack-docs#2395 ·
-
discussion help wanted
Difficulty 5/5 Over a week Newbie friendliness 25/100
elastic/stack-docs#2291 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
elastic/stack-docs#2263 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
elastic/stack-docs#2224 ·
All issues in elastic/stack-docs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cryptomator/hub#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
johanhaleby/occurrent#1120 ·