forked from pivotal-cf/docs-pcf-install
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathmonitoring.html.md.erb
87 lines (70 loc) · 2.95 KB
/
monitoring.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
---
title: Monitoring Virtual Machines in Pivotal Cloud Foundry
owner: Ops Manager
---
<strong><%= modified_date %></strong>
This topic describes strategies for monitoring virtual machine (VM) status and performance in [Pivotal Cloud Foundry](https://network.pivotal.io/products/pivotal-cf) (PCF).
## <a id="interface"></a>Monitoring VMs Using the Ops Manager Interface ##
Click any product tile and select the **Status** tab to view monitoring
information.
<%= image_tag("status-tab.png") %>
The columns display the following information:
<table border="1" class="nice" >
<tr>
<th>VM Data Point</th><th>Details</th>
</tr>
<tr>
<td><strong>Job</strong></td><td>Each job represents a component running on one or more VMs that Ops Manager deployed.</td>
</tr>
<tr>
<td><strong>Index</strong></td><td>For jobs that run across multiple VMs, the <strong>index</strong> value indicates the order in which the job VMs were deployed. For jobs that run on only one VM, the VM has an <strong>index</strong> value of <code>0</code>.</td>
</tr>
<tr>
<td><strong>IPs</strong></td><td>IP address of the job VM.</td>
</tr>
<tr>
<td><strong>CID</strong></td><td>Uniquely identifies the VM.</td>
</tr>
<tr>
<td><strong>Load Avg15</strong></td><td>CPU load average over 15 minutes.</td>
</tr>
<tr>
<td><strong>CPU</strong></td><td>Current CPU usage.</td>
</tr>
<tr>
<td><strong>Memory</strong></td><td>Current memory usage.</td>
</tr>
<tr>
<td><strong>Swap</strong></td><td>Swap file percentage.</td>
</tr>
<tr>
<td><strong>System Disk</strong></td><td>System disk space usage.</td>
</tr>
<tr>
<td><strong>Ephem. Disk</strong></td><td>Ephemeral disk space usage.</td>
</tr>
<tr>
<td><strong>Pers. Disk</strong></td><td>Persistent disk space usage.</td>
</tr>
<tr>
<td><strong>Logs</strong></td><td>Download link for the most recent log files.</td>
</tr>
</table>
### <a id="ops-manager"></a>Operations Manager VM Disk Space ###
The Ops Manager stores its logs on the Ops Manager VM in the `/tmp` directory.
<p class="note"><strong>Note</strong>: The logs collect over time and do not self-delete. To prevent the VM from running out of disk space, restart the VM to clear the
log entries from <code>/tmp</code>.</p>
## <a id="vsphere"></a>Monitoring in vSphere ##
To monitor VMs using the vSphere client:
1. Connect to a vCenter Server instance using the vSphere client.
1. Navigate to the **Hosts And Clusters** or **VMs And Templates** inventory view.
1. In the inventory tree, select a virtual machine.
1. Select the **Performance** tab from the content pane on the right.
VMware vSphere Server provides alarms that monitor VMs, as well as clusters,
hosts, datacenters, datastores, networks, and licensing.
To view preconfigured alarms, including disk usage alarms, related to a
particular VM:
1. In the vSphere client, select the VM you want to monitor.
1. At the bottom left of the client window, click **Alarms**.
1. If a VM starts to run out of disk space, an alarm appears in the bottom
panel.