summaryrefslogtreecommitdiffstats
path: root/health/guides/vcsa/vcsa_applmgmt_health.md
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-03-09 13:19:22 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-03-09 13:19:22 +0000
commitc21c3b0befeb46a51b6bf3758ffa30813bea0ff0 (patch)
tree9754ff1ca740f6346cf8483ec915d4054bc5da2d /health/guides/vcsa/vcsa_applmgmt_health.md
parentAdding upstream version 1.43.2. (diff)
downloadnetdata-0d980fd06561f4670f5d8170c5aedd74023e3702.tar.xz
netdata-0d980fd06561f4670f5d8170c5aedd74023e3702.zip
Adding upstream version 1.44.3.upstream/1.44.3
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'health/guides/vcsa/vcsa_applmgmt_health.md')
-rw-r--r--health/guides/vcsa/vcsa_applmgmt_health.md40
1 files changed, 40 insertions, 0 deletions
diff --git a/health/guides/vcsa/vcsa_applmgmt_health.md b/health/guides/vcsa/vcsa_applmgmt_health.md
new file mode 100644
index 000000000..06f391b3d
--- /dev/null
+++ b/health/guides/vcsa/vcsa_applmgmt_health.md
@@ -0,0 +1,40 @@
+### Understand the alert
+
+The `vcsa_applmgmt_health` alert is related to the health of VMware vCenter Server Appliance (VCSA) components. This alert is triggered when the health of one or more components is in a degraded or critical state, meaning that your VMware vCenter Server Appliance may be experiencing issues.
+
+### Troubleshoot the alert
+
+1. Access the vSphere Client for the affected vCenter Server Appliance
+
+ Log in to the vSphere Client to check detailed health information and manage your VCSA.
+
+2. Check the health status of VCSA components
+
+ In the vSphere Client, navigate to `Administration` > `System Configuration` > `Services` and `Nodes` tab. The component health status will be shown in the `Health` column.
+
+3. Inspect the affected component(s)
+
+ If any components show a status other than "green" (healthy), click on the component to view more details and understand the issue.
+
+4. Check logs related to the affected component(s)
+
+ Access the vCenter Server Appliance Management Interface (VAMI) by navigating to `https://<appliance-IP-address-or-FQDN>:5480` and logging in with the administrator account.
+
+ In the VAMI, click on the `Monitoring` tab > `Logs`. Download and inspect the logs to identify the root cause of the issue.
+
+5. Take appropriate actions
+
+ Depending on the nature of the issue identified, perform the necessary actions or modifications to resolve it. Consult the VMware documentation for recommended solutions for specific component health issues.
+
+6. Monitor the component health
+
+ After performing appropriate actions, continue to monitor the VCSA component health in the vSphere Client to ensure they return to a healthy status.
+
+7. Contact VMware support
+
+ If you are unable to resolve the issue, contact VMware support for further assistance.
+
+### Useful resources
+
+1. [VMware vCenter Server 7.0 Documentation](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenter.configuration.doc/GUID-52AF3379-8D78-437F-96EF-25D1A1100BEE.html)
+2. [VMware Support](https://www.vmware.com/support.html)