Skip to content

Commit b091044

Browse files
committed
Update node bootlooping
1 parent b2aafc6 commit b091044

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

troubleshoot/monitoring/node-bootlooping.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,9 @@ Following are some frequent causes of a failed configuration change:
3838
3939
If you’re unable to remediate the failing plan’s root cause, you can attempt to reset the deployment to the latest successful {{es}} configuration by performing a [no-op plan](/troubleshoot/monitoring/deployment-health-warnings.md). For an example, see this [video walkthrough](https://www.youtube.com/watch?v=8MnXZ9egBbQ).
4040
41+
:::{important}
42+
If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md).
43+
:::
4144
4245
## Secure settings [ec-config-change-errors-secure-settings]
4346

0 commit comments

Comments
 (0)