Skip to content

Commit 55b81e4

Browse files
committed
clean up main page
1 parent 32fedef commit 55b81e4

File tree

1 file changed

+11
-13
lines changed

1 file changed

+11
-13
lines changed

deploy-manage/monitor/autoops.md

Lines changed: 11 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -10,27 +10,25 @@ products:
1010

1111
# AutoOps [ec-autoops]
1212

13-
AutoOps diagnoses issues in {{es}} by analyzing hundreds of metrics, providing root-cause analysis and accurate resolution paths. With AutoOps, customers can prevent and resolve issues, cut down administration time, and optimize resource utilization.
13+
AutoOps analyzes a comprehensive set of metrics to diagnose issues in {{es}} and provide you with root-cause analyses and accurate resolution paths. With AutoOps, you can prevent and resolve issues, cut down administration time, and optimize resource utilization.
1414

1515
:::{image} /deploy-manage/images/cloud-autoops-overview-page.png
1616
:alt: The Overview page
1717
:::
1818

19-
2019
## AutoOps key features [ec_autoops_key_features]
2120

22-
* Real-time root-cause analysis for hundreds of issues.
23-
* Accurate resolution paths and customized recommendations.
24-
* Insight into what occurred and detailed views into nodes, index, shards, and templates.
21+
* Real-time root-cause analysis for hundreds of issues
22+
* Accurate resolution paths and customized recommendations
23+
* Insight into what occurred and detailed views into nodes, indices, shards, and templates
2524
* Wide range of insights, including:
26-
27-
* Cluster status, node failures, and shard sizes.
28-
* High CPU, memory, disk usage, and other resource-related metrics.
29-
* Misconfigurations and possible optimizations.
30-
* Insights on data structure, shards, templates, and mapping optimizations.
31-
* Unbalanced loads between nodes.
32-
* Indexing latency, rejections, search latency, high index/search queues, and slow queries.
33-
* Resource utilization.
25+
* Cluster status, node failures, and shard sizes
26+
* High CPU, memory, disk usage, and other resource-related metrics
27+
* Misconfigurations and possible optimizations
28+
* Data structure, templates, and mapping optimizations
29+
* Unbalanced loads between nodes
30+
* Indexing latency, rejections, search latency, high index/search queues, and slow queries
31+
* Resource utilization
3432

3533

3634

0 commit comments

Comments
 (0)