_logging.html.md.erb

You can designate an external syslog endpoint for forwarding BOSH-deployed VM logs.

In addition, you can enable sink resources to collect Kubernetes cluster and namespace log messages.

To configure logging in <%= vars.product_tile %>, do the following:

1. Click **Logging**.
1. To enable syslog forwarding for BOSH-deployed VM logs, select **Yes**.

    ![Enable syslog forwarding](images/logging.png)

1. Under **Address**, enter the destination syslog endpoint.
1. Under **Port**, enter the destination syslog port.
1. Select a transport protocol for log forwarding.
1. (Optional) Pivotal strongly recommends that you enable TLS encryption when forwarding logs as they may contain sensitive information. For example, these logs may contain cloud provider credentials. To enable TLS, perform the following steps:
  1. Under **Permitter 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>
<% if current_page.data.iaas == "vSphere" || current_page.data.iaas == "vSphere-NSX-T" %>
1. <%= partial 'vrealize-logs' %>
<% else %>
1. To enable clusters to drain Kubernetes API events and pod logs to sinks, select the **Enable Log Sink Resources** checkbox.
1. To enable clusters to drain Kubernetes node and pod metrics to sinks, select the **Enable Metric Sink Resources** checkbox.
For more information about using sink resources,
see [Creating Sink Resources](create-sinks.html).<br>
    <img src="images/sink-resources.png" width="320" alt="Enable metric sink resources checkbox">
1. Click **Save**.
<% end %>