mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 07:37:19 -04:00
d039c280af
* (Docs+) Flush out Resource+Task troubleshooting --------- Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Co-authored-by: David Turner <david.turner@elastic.co>
20 lines
1.4 KiB
Text
20 lines
1.4 KiB
Text
// tag::cloud[]
|
|
* (Recommended) Enable {cloud}/ec-monitoring-setup.html[logs and metrics]. When logs and metrics are enabled, monitoring information is visible on {kib}'s {kibana-ref}/xpack-monitoring.html[Stack Monitoring] page.
|
|
+
|
|
You can also enable the {kibana-ref}/kibana-alerts.html[CPU usage threshold alert] to be notified about potential issues through email.
|
|
|
|
* From your deployment menu, view the {cloud}/ec-saas-metrics-accessing.html[**Performance**] page. On this page, you can view two key metrics:
|
|
** **CPU usage**: Your deployment's CPU usage, represented as a percentage.
|
|
** **CPU credits**: Your remaining CPU credits, measured in seconds of CPU time.
|
|
|
|
{ess} grants {cloud}/ec-vcpu-boost-instance.html[CPU credits] per deployment
|
|
to provide smaller clusters with performance boosts when needed. High CPU
|
|
usage can deplete these credits, which might lead to {cloud}/ec-scenario_why_is_performance_degrading_over_time.html[performance degradation] and {cloud}/ec-scenario_why_are_my_cluster_response_times_suddenly_so_much_worse.html[increased cluster response times].
|
|
|
|
// end::cloud[]
|
|
|
|
// tag::self-managed[]
|
|
* Enable <<monitoring-overview,{es} monitoring>>. When logs and metrics are enabled, monitoring information is visible on {kib}'s {kibana-ref}/xpack-monitoring.html[Stack Monitoring] page.
|
|
+
|
|
You can also enable the {kibana-ref}/kibana-alerts.html[CPU usage threshold alert] to be notified about potential issues through email.
|
|
// end::self-managed[]
|