-
Notifications
You must be signed in to change notification settings - Fork 68
/
_host-monitoring.html.md.erb
68 lines (53 loc) · 4.02 KB
/
_host-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
<% if vars.product_version == "COMMENTED" %>
<%# WARNING!!!! %>
<%# DO NOT ADD READBILITY LINE WRAPPING TO THIS CONTENT THE LONG LINES MUSt REMAIN TO CORRECTLY FORMAT THE FOLLOWING SECTION'S MARKDOWN CONTENT %>
<%# <!-- WARNING!!!! --> %>
<% end %>
<% if current_page.data.iaas == "vSphere" || current_page.data.iaas == "vSphere-NSX-T" %>
In **Host Monitoring**, you can configure monitoring of nodes and VMs using Syslog,
VMware vRealize Log Insight (vRLI) Integration, or Telegraf.
<% else %>
In **Host Monitoring**, you can configure monitoring of nodes and VMs using Syslog, or Telegraf.
<% end %>
You can configure one or more of the following:
* **Syslog**: To configure Syslog, see [Syslog](#host-syslog) below. Syslog forwards log messages from all BOSH-deployed VMs to a syslog endpoint.
<% if current_page.data.iaas == "vSphere" || current_page.data.iaas == "vSphere-NSX-T" %>
* **VMware vRealize Log Insight (vRLI) Integration**: To configure VMware vRealize Log Insight (vRLI) Integration, see [VMware vRealize Log Insight Integration](#vrealize-logs) below.
The vRLI integration pulls logs from all BOSH jobs and containers running in the cluster, including node logs from core Kubernetes and BOSH processes, Kubernetes event logs, and pod `stdout` and `stderr`.
<% end %>
* **Telegraf**: To configure Telegraf, see [Configuring Telegraf in TKGI](monitor-etcd.html). The Telegraf agent sends metrics from TKGI API, control plane node, and worker node VMs to a monitoring service, such as Wavefront or Datadog.
For more information about these components, see
[Monitoring TKGI and TKGI-Provisioned Clusters](host-monitoring.html).
####<a id="host-syslog"></a> Syslog
To configure Syslog for all BOSH-deployed VMs in Tanzu Kubernetes Grid Integrated Edition:
1. Click **Host Monitoring**.
1. Under **Enable Syslog for TKGI**, select **Yes**.
1. Under **Address**, enter the destination syslog endpoint.
1. Under **Port**, enter the destination syslog port.
1. Under **Transport Protocol**, select a transport protocol for log forwarding.
1. (Optional) To enable TLS encryption during log forwarding, complete the following steps:
1. Ensure **Enable TLS** is selected.
<p class="note"><strong>Note</strong>: Logs might contain sensitive information, such as cloud provider credentials.
<%= vars.recommended_by %> recommends that you enable TLS encryption for log forwarding.
</p>
1. Under **Permitted Peer**, provide the accepted fingerprint (SHA1) or name of remote peer. For example, `*.YOUR-LOGGING-SYSTEM.com`.
1. Under **TLS Certificate**, provide a TLS certificate for the destination syslog endpoint.
<p class="note"><strong>Note</strong>: You do not need to provide a new certificate if the TLS certificate for the destination syslog endpoint is signed by a Certificate Authority (CA) in your BOSH certificate store.
</p>
1. (Optional) Under **Max Message Size**, enter a maximum message size for logs that are forwarded to a syslog endpoint. By default, the **Max Message Size** field is 10,000 characters.
1. (Optional) Under **Custom Rsyslog Configuration**, enter your RSyslog rules configuration using RainerScript syntax.
For more information, see [RainerScript](https://www.rsyslog.com/doc/v8-stable/rainerscript/index.html#rainerscript) in the RSyslog documentation.
For example RSyslog rule configurations, see [Example Custom Rules](https://github.com/cloudfoundry/syslog-release/blob/main/examples/example-custom-rules.md)
in the Syslog BOSH GitHub repository.
1. Click **Save**.
<% if current_page.data.iaas == "vSphere" || current_page.data.iaas == "vSphere-NSX-T" %>
####<a id="vrealize-logs"></a> VMware vRealize Log Insight Integration
<%= partial 'vrealize-logs' %>
<% end %>
<% if vars.product_version == "COMMENTED" %>
<%# WARNING!!!! %>
<%# <!-- DO NOT ADD READBILITY LINE WRAPPING TO THIS CONTENT THE LONG LINES MUSt REMAIN TO CORRECTLY FORMAT THE FOLLOWING SECTION'S MARKDOWN CONTENT %>
<%# WARNING!!!! %>
<% end %>