From 310edf444908b09ea6d00c03baceb7925f3bb7a2 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Thu, 21 Mar 2024 18:19:04 +0100 Subject: Merging upstream version 1.45.0. Signed-off-by: Daniel Baumann --- .../consul_autopilot_server_health_status.md | 48 ---------------------- 1 file changed, 48 deletions(-) delete mode 100644 health/guides/consul/consul_autopilot_server_health_status.md (limited to 'health/guides/consul/consul_autopilot_server_health_status.md') diff --git a/health/guides/consul/consul_autopilot_server_health_status.md b/health/guides/consul/consul_autopilot_server_health_status.md deleted file mode 100644 index 687c2bb1d..000000000 --- a/health/guides/consul/consul_autopilot_server_health_status.md +++ /dev/null @@ -1,48 +0,0 @@ -### Understand the alert - -The `consul_autopilot_server_health_status` alert triggers when a Consul server in your service mesh is marked `unhealthy`. This can affect the overall stability and performance of the service mesh. Regular monitoring and addressing unhealthy servers are crucial in maintaining a smooth functioning environment. - -### What is Consul? - -`Consul` is a service mesh solution that provides a full-featured control plane with service discovery, configuration, and segmentation functionalities. It is used to connect, secure, and configure services across any runtime platform and public or private cloud. - -### Troubleshoot the alert - -Follow the steps below to identify and resolve the issue of an unhealthy Consul server: - -1. Check Consul server logs - - Inspect the logs of the unhealthy server to identify the root cause of the issue. You can find logs typically in `/var/log/consul` or use `journalctl` with Consul: - - ``` - journalctl -u consul - ``` - -2. Verify connectivity - - Ensure that the unhealthy server can communicate with other servers in the datacenter. Check for any misconfigurations or network issues. - -3. Review server resources - - Monitor the resource usage of the unhealthy server (CPU, memory, disk I/O, network). High resource usage can impact the server's health status. Use tools like `top`, `htop`, `iotop`, or `nload` to monitor the resources. - -4. Restart the Consul server - - If the issue persists and you cannot identify the root cause, try restarting the Consul server: - - ``` - sudo systemctl restart consul - ``` - -5. Refer to Consul's documentation - - Consult the official [Consul troubleshooting documentation](https://developer.hashicorp.com/consul/tutorials/datacenter-operations/troubleshooting) for further assistance. - -6. Inspect the Consul UI - - Check the Consul UI for the server health status and any additional information related to the unhealthy server. You can find the Consul UI at `http://:8500/ui/`. - -### Useful resources - -1. [Consul Documentation](https://www.consul.io/docs) -2. [Running Consul as a Systemd Service](https://learn.hashicorp.com/tutorials/consul/deployment-guide#systemd-service) -- cgit v1.2.3