Skip to content

Commit 03417ad

Browse files
committed
PR feedback
1 parent bcd525e commit 03417ad

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

deploy-manage/monitor/autoops-vs-stack-monitoring.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ On {{ech}} and {{serverless-full}}, AutoOps is set up and enabled automatically
3737
:alt: Diagram showing AutoOps setup in Elastic Cloud
3838
:::
3939

40-
For {{ece}} (ECE), {{eck}} (ECK), and self-managed clusters, you need to go through a [connection process](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) to connect to AutoOps. This involves installing {{agent}} to ship your monitoring metrics to {{ecloud}} through [](/deploy-manage/cloud-connect.md). Since you can only access AutoOps from the {{ecloud}} UI, you need an {{ecloud}} account for this service.
40+
For {{ece}} (ECE), {{eck}} (ECK), and self-managed clusters, you need to [connect your cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md). This involves installing {{agent}} to ship your monitoring metrics to {{ecloud}} through [](/deploy-manage/cloud-connect.md). Since you can only access AutoOps from the {{ecloud}} UI, you need an {{ecloud}} account for this service.
4141

4242
:::{image} /deploy-manage/images/self-managed-autoops-setup.png
4343
:alt: Diagram showing AutoOps setup for ECE, ECK, and self-managed clusters

deploy-manage/monitor/autoops/ec-autoops-deployment-view.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ The **Events History** panel lists events that happened at some point and that h
3737

3838
## Resources [ec-deployment-resources]
3939

40-
The **Resources** panel provides a quick overview of Elasticsearch cluster resource usage. The resources are presented based on their respective data tiers and include JVM memory usage, CPU usage, and storage usage over time. You can view essential cluster information such as the Elasticsearch version, total number of nodes, total shards, and total used storage.
40+
The **Resources** panel provides a quick overview of {{es}} cluster resource usage. The resources are presented based on their respective data tiers and include JVM memory usage, CPU usage, and storage usage over time. You can view essential cluster information such as the {{es}} version, total number of nodes, total number of shards, and total volume of used storage.
4141

4242
:::{image} /deploy-manage/images/cloud-autoops-deployment-resources.png
4343
:alt: The AutoOps Resources panel

deploy-manage/monitor/autoops/ec-autoops-how-to-access.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ navigation_title: For {{ech}}
1111

1212
# AutoOps for {{ech}}
1313

14-
AutoOps is available in all {{ech}} deployments in supported [regions](ec-autoops-regions.md#autoops-for-ech-regions). More regions are coming soon.
14+
For {{ech}} deployments, AutoOps is set up and enabled automatically in all supported [regions](ec-autoops-regions.md#autoops-for-ech-regions). More regions are coming soon.
1515

1616
## How to access AutoOps [ec-autoops-how-to-access]
1717

0 commit comments

Comments
 (0)