You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deploy-manage/deploy/elastic-cloud/ec-vcpu-boost-instance.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,5 +49,5 @@ You can check the **Monitoring > Performance > CPU Credits** section of the [{{e
49
49
50
50
## What to do if my vCPU credits get depleted constantly? [ec_what_to_do_if_my_vcpu_credits_get_depleted_constantly]
51
51
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.
Copy file name to clipboardExpand all lines: deploy-manage/monitor/cloud-health-perf.md
+25-4Lines changed: 25 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ In the normal course of using your {{ech}} and {{ece}} deployments, health warni
60
60
#### Cluster restarts after out-of-memory failures [ec_cluster_restarts_after_out_of_memory_failures]
61
61
```{applies_to}
62
62
deployment:
63
-
ech:
63
+
ess:
64
64
```
65
65
66
66
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
82
82
83
83
[Learn more about the performance page and the metrics it captures](/deploy-manage/monitor/access-performance-metrics-on-elastic-cloud.md).
84
84
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
+
85
89
## JVM memory pressure indicator
86
90
87
91
{{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.
88
92
89
93
## Preconfigured logs and metrics [ec-es-health-preconfigured]
90
94
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.
92
96
93
-
:::{tip} Monitoring in production environments
97
+
:::{admonition} Monitoring in production environments
94
98
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.
95
99
96
100
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
104
108
105
109
### In {{ece}}
106
110
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.
108
129
109
130
## Understanding deployment health [ec-health-best-practices]
0 commit comments