Skip to content

Commit 521fe42

Browse files
committed
rehome vcpu page"
1 parent 6d5f06a commit 521fe42

File tree

3 files changed

+27
-6
lines changed

3 files changed

+27
-6
lines changed

deploy-manage/monitor/ec-vcpu-boost-instance.md renamed to deploy-manage/deploy/elastic-cloud/ec-vcpu-boost-instance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,5 +49,5 @@ You can check the **Monitoring > Performance > CPU Credits** section of the [{{e
4949

5050
## What to do if my vCPU credits get depleted constantly? [ec_what_to_do_if_my_vcpu_credits_get_depleted_constantly]
5151

52-
If you need your cluster to be able to sustain a certain level of performance, you cannot rely on CPU boosting to handle the workload except temporarily. To ensure that performance can be sustained, consider increasing the size of your cluster. Read [this page](/troubleshoot/monitoring/performance.md) for more guidance.
52+
If you need your cluster to be able to sustain a certain level of performance, you cannot rely on CPU boosting to handle the workload except temporarily. To ensure that performance can be sustained, consider increasing the size of your cluster. Refer to [](/troubleshoot/monitoring/performance.md) for more guidance.
5353

deploy-manage/monitor/cloud-health-perf.md

Lines changed: 25 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ In the normal course of using your {{ech}} and {{ece}} deployments, health warni
6060
#### Cluster restarts after out-of-memory failures [ec_cluster_restarts_after_out_of_memory_failures]
6161
```{applies_to}
6262
deployment:
63-
ech:
63+
ess:
6464
```
6565

6666
For clusters that suffer out-of-memory failures, it can be difficult to determine whether the clusters are in a completely healthy state afterwards. For this reason, {{ech}} automatically reboots clusters that suffer out-of-memory failures.
@@ -82,15 +82,19 @@ The **Performance** page and the out-of-the-box logs allow you to monitor your c
8282

8383
[Learn more about the performance page and the metrics it captures](/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md).
8484

85+
:::{tip}
86+
For {{ece}} deployments, you can use [platform monitoring](/deploy-manage/monitor/orchestrators/ece-platform-monitoring.md) to access preconfigured performance metrics.
87+
:::
88+
8589
## JVM memory pressure indicator
8690

8791
{{ech}} and {{ece}} also provide a [JVM memory pressure indicator](/deploy-manage/monitor/ec-memory-pressure.md) for each node in your cluster in your deployment overview. This indicator can help you to determine when you need to upgrade to a larger cluster.
8892

8993
## Preconfigured logs and metrics [ec-es-health-preconfigured]
9094

91-
Both {{ech}} and {{ece}} offer preconfigured logs and metrics that you can access to get insight into your deployment's performance.
95+
Both {{ech}} and {{ece}} offer out-of-the-box logs and metrics that you can access to get insight into your deployment's performance.
9296

93-
:::{tip} Monitoring in production environments
97+
:::{admonition} Monitoring in production environments
9498
In a production environment, it’s important set up dedicated health monitoring using [stack monitoring](/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md). Stack monitoring allows you to retain the logs and metrics that can be used to troubleshoot any health issues in your deployments. In the event of that you need to [contact our support team](/troubleshoot/index.md#contact-us), they can use the retained data to help diagnose any problems that you may encounter.
9599

96100
You have the option of sending logs and metrics to a separate, specialized monitoring deployment, which ensures that they’re available in the event of a deployment outage. The monitoring deployment also gives you access to {{kib}} stack monitoring features, through which you can view health and performance data for all of your deployment resources.
@@ -104,7 +108,24 @@ The logs capture any activity related to your deployments, their component resou
104108

105109
### In {{ece}}
106110

107-
In {{ece}}, you can use [platform monitoring](/deploy-manage/monitor/orchestrators/ece-platform-monitoring.md) to view deployment logs and metrics as well as proxy logs. From your deployment page, select either the **Elasticsearch**, **Kibana**, and **Integrations Server** components, and use the external links to access each service's logs and metrics, including the associated proxy logs.
111+
In {{ece}}, you can use [platform monitoring](/deploy-manage/monitor/orchestrators/ece-platform-monitoring.md) to view deployment logs and metrics, as well as proxy logs. From your deployment page, select either the **Elasticsearch**, **Kibana**, and **Integrations Server** components, and use the external links to access each service's logs and metrics.
112+
113+
## vCPU credit monitoring
114+
115+
```{applies_to}
116+
deployment:
117+
ess:
118+
```
119+
120+
Elastic Cloud allows smaller instance sizes to get temporarily boosted vCPU when under heavy load. [vCPU boosting](/deploy-manage/deploy/elastic-cloud/ec-vcpu-boost-instance.md) is governed by vCPU credits that instances can earn over time when vCPU usage is less than the assigned amount.
121+
122+
You can check the **Monitoring > Performance > CPU Credits** section of the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), and find the related metrics:
123+
124+
:::{image} /images/cloud-metrics-credits.png
125+
:alt: CPU usage versus CPU credits over time
126+
:::
127+
128+
If you need your cluster to be able to sustain a certain level of performance, you can't rely on CPU boosting to handle the workload except temporarily. To ensure that performance can be sustained, consider increasing the size of your cluster. Refer to [](/troubleshoot/monitoring/performance.md) for more guidance.
108129

109130
## Understanding deployment health [ec-health-best-practices]
110131

deploy-manage/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,7 @@ toc:
8080
children:
8181
- file: deploy/elastic-cloud/switch-from-apm-to-integrations-server-payload.md
8282
- file: deploy/elastic-cloud/find-cloud-id.md
83+
- file: deploy/elastic-cloud/ec-vcpu-boost-instance.md
8384
- file: deploy/elastic-cloud/change-hardware.md
8485
- file: deploy/elastic-cloud/manage-deployments-using-elastic-cloud-api.md
8586
- file: deploy/elastic-cloud/keep-track-of-deployment-activity.md
@@ -710,7 +711,6 @@ toc:
710711
children:
711712
- file: monitor/access-performance-metrics-on-elastic-cloud.md
712713
- file: monitor/ec-memory-pressure.md
713-
- file: monitor/ec-vcpu-boost-instance.md
714714
- file: monitor/orchestrators.md
715715
children:
716716
- file: monitor/orchestrators/eck-metrics-configuration.md

0 commit comments

Comments
 (0)